1. 88horizon5speed's Avatar
    I have to wake up at 2:30 this morning because 10 minutes later an ebay bid is ending (6 hrs xx minutes from now). I went to set an alarm for 2:30 and it saves and has the pop up saying 7 hrs xx minutes and the alarm says 3:30. I kept trying to set for 2:30 and same thing keeps happening. For experiment sake I set one successfully to 1 am, and 1:55 but as soon as the hour is 2 it goes to 3am...

    Can others try this to see if its a widespread bug or just a hiccup for me right now? Seems really stupid.
    03-08-2015 07:19 PM
  2. Rukbat's Avatar
    Sunday night? 2:30 Monday morning? Or is this from last night? The clock went ahead last night, so if you set it for 2:30 before 2 AM Sunday, the alarm would compensate for that (and probably be wrong, so it might be bug.)
    03-08-2015 08:08 PM
  3. jem9777's Avatar
    In the US? There was no 2:30 this morning. Clocks went right from 1:59 to 3:00. What you are describing is how I would expect it to behave.
    03-08-2015 08:39 PM
  4. 88horizon5speed's Avatar
    Right now its 9:50 pm on the east coast of the US, daylight savings time has already happened last night. Im trying to make the alarm for monday morning at 2:30 and it will accept anytime but if the hour is set to 2 it jumps it to 3 instantly

    Edit- My bad, I said this morning, I meant tomorrow morning lol
    03-08-2015 08:51 PM
  5. MA2GA28's Avatar
    Actually, happening to me and my wife as well. Appears to be a bug, possibly and issue with DST adjustment. I'd set an alternate alarm if I were you.
    03-08-2015 09:27 PM
  6. doogald's Avatar
    The same thing happens on a droid maxx. I assume it's a bug and it's not allowing you to set the alarm because there was no 2:30 am *this* morning.

    There is a free app in the play store called timely alarm clock. That will let you set a 2:30 am alarm.
    03-08-2015 09:42 PM
  7. tdelfie03's Avatar
    My turbo does the same thing. Must be a bug due to the time change

    Posted via the Android Central App
    03-08-2015 09:44 PM
  8. jinx626's Avatar
    Happened to me this morning a day after daylight savings time. Running a Nexus 5 on Vanilla Lolipop. Set alarm for 255am and it rang at 355am. Thanks to this bug i was late for work. Seems that the time period between 2-3am simply doesnt exist for the alarm function.
    03-09-2015 08:09 AM
  9. doogald's Avatar
    Fwiw, if the turbo is like the Maxx, you should be able to set an alarm between 2 and 3 am today going forward.

    We'll have to see if there is a way to pass along this bug to Motorola...
    03-09-2015 09:08 AM
  10. 88horizon5speed's Avatar
    Ok glad it wasnt just me. I just checked and it allowed an alarm for 2:30 again
    03-10-2015 07:18 AM

Similar Threads

  1. Replies: 3
    Last Post: 09-29-2015, 12:03 PM
  2. What came in this update of the system today?
    By Kleyton Coimbra in forum Legacy Android & Other OS's
    Replies: 4
    Last Post: 03-15-2015, 07:08 AM
  3. Replies: 3
    Last Post: 03-12-2015, 08:00 PM
  4. Gaps in Phone
    By Noah Martin in forum Moto X
    Replies: 2
    Last Post: 03-09-2015, 02:18 PM
  5. Any problems with your OPO? for who bought this in 2015
    By khainguyen97 in forum OnePlus One
    Replies: 4
    Last Post: 03-09-2015, 05:28 AM