@Wichall: Can you try to repeat this? Make more alarms, do another backup/restore..?
I want to see if its a one-time (or dst) glitch, or an actual problem.
I will at some point Robbie, it was a restore to a different phone so my guess is the active alarms are stored somewhere outside of the opt and rootfs which is why they can turn the N900 on...
I had that too. Very odd, after a restore all my alarms were disabled, was late as well. I simply assumed I have defined the alarms, backed up, enabled and then restored. Makes little sense, all newly created alarms are enabled by default.
I only restored rootfs, though. Might have been a desync?
I had that too. Very odd, after a restore all my alarms were disabled, was late as well. I simply assumed I have defined the alarms, backed up, enabled and then restored. Makes little sense, all newly created alarms are enabled by default.
I only restored rootfs, though. Might have been a desync?
Presumably the alarms need registering somehow, otherwise they wouldn't be able to fire when the phone is switched off. No idea how to retrigger this registration though
I know the wake function's handled by the onboard RTC(real time clock). I don't know anything about this chip, however. I'd assume that this should be set during boot... but it looks like it's not. I'll have to ask stskeeps.
In the meantime though, a fix is what... Just remember to enable all alarms after restore?
