3 ms·
And a fun fact: it even calculates it correctly across a daylight savings time change. I noticed that when the clocks went back; instead of just subtracting th
by jedc 14y ago
And a fun fact: it even calculates it correctly across a daylight savings time change. I noticed that when the clocks went back; instead of just subtracting the times, my Android phone accounted for the change and added the hour that I was getting back. Awesome!
- zhoutong 14y agoI'm sure it's using the UTC time to calculate this. The UTC never goes back.
- pronoiac 14y agoThat's a sarcastic "awesome," right? Because that sounds like a bug. If you need to do something after x hours, this is useful. If you have to do something at a certain clock time, then this could be infuriating.
- brian_cloutier 14y agoI'm sorry? He said he wanted to do something at a certain clock time, and the phone correctly told him how many hours away that time was.
- pronoiac 14y agoOh! I thought it changed the alarm time. A technically adept friend recently complained about this happening with his Android phone - the 8am alarm went off at 7am - so I had that in mind, though it seems like I was misreading here. Sorry about that.
- drivebyacct2 14y agoHaha, if it adjusted the clock time, that would be double or triple bad depending on how it was implemented. The alarm would be wrong unless it were shifted back when the time changed again, thus defeating the point of having altered it in the first place.
- tspiteri 14y agoThis happened to me too; the alarm went off at both 7 am and 8 am instead of just 8.