OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: ToneBlind on January 23, 2010, 02:24:07 pm
-
I know this has been an ongoing problem for many people under pdaXrom, and I hope this fix will encourage some users to get back to using pdaXrom in their Zaurii.
The issue involved general unreliability with KOPI alarms due to failure to wake up the Zaurus before an alarm would take place. Additionally, I found a bug in one of the scripts which was preventing suspended alarms from being considered under certain conditions. This has been thoroughly tested under pdaXii13, and should work equally well with pdaXrom. As always, I advise you to perform a NAND backup before installing.
The hwclock script saves and retrieves the time in UTC format. In my testing, I have found that it is the only way to maintain consistent times across reboots. If your hardware clock was last set using a different time zone, the time will be wrong on your first resume after installing the package. It suffices to set the time via datentime.py again, and it should remain consistent after that. This is due to the fact that hwclock keeps time in a raw format without timezone information. The only requirement is consistency in specifying a time zone for interpretation of the raw value between writes and reads.
Without further ado, I'm attaching the packages. I include:
KDEPIM/PI (Not needed if your KDEPIM/PI version is already capable of playing sound alarms.)
kopi-apm (A revision which fixes the logic which was preventing suspended alarms from kicking in.)
atd (You need this if you don't already have atd installed.)
hwclock-atd (This modifies the /etc/apm/scripts.d/hwclock script to work with atd.)
Let me know if you have any questions!
Cheers,
ToneBlind