Root DST time change issue

[Zoandroid]

So I'm sitting here with my Ally and Droid X, both of which are 'stuck' on it being 12:59AM now for the last 22 minutes. I'm in the EST zone of the US, so we are 'falling back' from DST tonight. Anyone else seeing this?

AFAIK, the 'official' change to lose an hour is supposed to happen at 2AM. I wonder if Verizon's method of falling back an hour is simply to 'hold' the time on the phone's clock for 60 minutes? I guess I'll find out at the top of the hour in about 36 minutes.

 

[Zoandroid]

Around 1:24 first the Droid X suddenly updated its clock, then the Ally about 1:32. But neither has 'lost an hour' yet. As of 1:44 they still show 1:24 and 1:32 respectively on their notification bar clocks, but when I turn the screens of and back on, the correct time shows. I would have thought the device's clock was singularly controlled, so the notification bar clock and the power on clock would have to be the same. Apparently not the case on either phone.

 

[cr5315]

I recommend rebooting both of them. That should have the Droid X check with Verizon's servers to check the time, and I presume the Ally does something similar since mine still gets the right time. (I then proceed to check my EVO and Ally)

The EVO says 1:38 on the lockscreen but 1:08 in the status bar.
The Ally says 1:38 on the lockscreen but 1:06 in the status bar.

Ima reboot them and see what they say.

EDIT
After rebooting:
EVO says 1:40 on lockscreen and 1:40 in status
Ally says 1:40 on lockscreen and 1:39 in status

I am very confused.

 

[Zoandroid]

I've dealt with DST frustrations in handheld devices dating back to the glory days of Palm OS. When Bush decided to arbitrarily change the dates of US DST he just took an existing nightmare and turned it into a total cluster_. I use 10 daily repeating alarms which will do anything from simply never sounding at all to sounding at the wrong times, and get changed forward our backward an hour in the battle between the original DST and Bush DST dates as waged between the devices own software, aftermarket calendar apps, Google calendar, and who knows what other invisible forces. This week has been a nightmare of daily alarm fixing attempts with no lasting success, as usual. Only after tomorrow will things usually settle down..........until March. :/

I've even tried forcing the Ally to use a non-DST time zone. Even that can't stop the nightmare that arrives the last Sunday in October.

Hopefully our devices will return to normal operation tomorrow.