So I set an alarm on my GN last night for 7:15am this morning. This was before the daylight savings time change.
Well, this morning no alarm went off at 7:15am as the alarm moved to 8:15am.
What a terrible bug or "feature " perhaps. Alarm times should never be affected by DST.
Sent from my Galaxy Nexus using Tapatalk
My alarm went off at 9am as usual.
Sent from my Nexus in Texas.
YES.. >< i was late to work from this stupid **** !
I had the same issue. I set the alarm for 8:00 and I woke up on my own at 8:15. I turned the alarm off afterwards, but I assume it was pushed to 9:00 because of DST.
Mine went off at the right time, maybe you should check your clock settings?
This is not just a phone - Galaxy Nexus
I use alarm clock extreme and it went off at the correct time
Mine worked fine. If you're not on a stock ROM, it could be a ROM issue.
Related
Guys,
My BA (running on WM5) has the alarm 'stuck' at a very awkward hour.
The surprising thing is that this time, 4 am, is not set on the alarm settings. And no matter what I do, it still wakes me up at 4 am.
If I set the alarm to another time, it will still get off at 4, and at the other time.
How do I sort this out?
Thanks,
Celzo
I have got the similar problem, alarm set to 8.15 AM but ringing at 9.15 AM on XDA||s. Any help?
I'm using the stock alarm program and 3/5 times I've set an alarm nothing has happened when the alarm is supposed to go off. It always works when I set it to go off the next minute as a test case, but it's very unreliable for overnight use.
Any similar experiences or thoughts on why this happens?
Mines never not worked used it every day since I had the phone - I assume you are leaving the phone switched on right?
Did you kill the alarm&clock app (with Taskiller for example) ? This app needs to be active if you want it to work.
Mine works. Screen goes to sleep, alarm wakes it and me up no sweat.
Sorry, I actually figured it out right after posting, but yes the app is probably being closed sometime during the night. I put it on my ignore lists, it's too bad the alarm isn't some sort of a system service.
Sent from my MB525 using XDA App
Try using alarm clock plus from market. It's a much improved alarm.
This all started yesterday morning. I had my alarm set, woke up later than I needed to with a notification on the phone that said Alarm Turned Off After 10 Minutes, telling me the alarm had gone off for 10 minutes and was automatically turned off.
I thought it was weird so I did some digging and it turned out that NONE of my sounds were working. The volume was up, silent mode was off, but I was getting nothing whatsoever from the phone speaker. Even speaker phone wasn't working. Headphones worked fine. It seemed my speaker had blown.
Well, later in the day (as I was preparing to take it back to Verizon) it just randomly starts working again. All sounds now seem fine.
So I set my alarm this morning. And this time, it didn't even go off, at all! I woke up 5 minutes after it was supposed to go off, and when I unlocked my phone, THEN the alarm started going off. It's almost like it isn't coming our of deep sleep to sound the alarm.
Are these two issues related; the sound issue yesterday and the alarm issues both days? Has anyone else experienced this? It seems to be random...sometimes I can replicate it, other times I cannot.
There's another thread about this somewhere...try a search for "alarm". It's happened to me often enough that I can't rely on my Gnex as an alarm clock...I have to use my old SGS instead. I've also had loss of sound occasionally, but a reboot always fixes it.
Wish someone would figure out a solution, it's pretty annoying to have a bug like this in the alarm. Even the cheapest, crappiest dumbphone you can buy comes with a reliable alarm app, but my expensive smartphone does not? (and yes, I've tried other alarm apps besides the stock one...they all fail to go off intermittently.)
Sent from my Galaxy Nexus using XDA
Thanks for the input. I use my alarm daily and this is the first time I've had this issue.
As an aside (but perhaps related issue?), my gmail app has uninstalled itself and I can't get it reinstalled. Looks like it's time for a reflash.
cmcfalls said:
Thanks for the input. I use my alarm daily and this is the first time I've had this issue.
As an aside (but perhaps related issue?), my gmail app has uninstalled itself and I can't get it reinstalled. Looks like it's time for a reflash.
Click to expand...
Click to collapse
Yes I would reflash before you miss a flight or the interview to your dream job!
One thing I miss about my old blackberry is the alarm. Put it in the cradle and the time would dim, all notifications would turn off and the alarm would fire every time, every when the battery had been drained and switched off. Pity everything else sucked...
I've yet to have a problem.
Maybe you're getting SOD's (or close-to) in the middle of the night and the phone is having trouble waking itself up?
Try adjusting your governor and turn your undervolts up if they're enabled.
I am, however, fairly OCD about my alarms...
I reboot my phone before opening the alarm app and ONLY the alarm app...
Make sure the alarm is enabled...
And turn the screen off.
I've done this since my OGDroid days.
I also have the trusty DX as a backup...set 10 minutes later; just in case.
Since the upgrade to Android 6.0.1 my alarm clock(Alarm Clock Plus) does not go off when it is supposed to. It worked fine until the update. I don't know if Doze is causing this or if it's the new Samsung app power saving setup? I have the alarm clock app excluded from ever saving power but it still doesn't go off. It seems like the hours that I'm sleep puts the app in deep sleep because when I pick the phone up and cut on the screen it went off which was about 11 minutes after it was scheduled one day and 8 the next. Also if I set an alarm, say 5 minutes from now as an example, it will go off though.
The stock alarm is working for me. .. It could be just a problem with alarm clock plus. .
Sent from my SM-N910P using Tapatalk
if I set an alarm clock this always rings 1 day early. Have it tested with other apps but everywhere the same problem.
Test mine right now,everything ok
Don't have that problem either but then again I set the alarm for morning before I go to bed. I can't say that I have ever set an alarm so far ahead that it can go off a day early.
I use FreedomOS Rom. I test with stock again.
I have make a Video from the problem: https://drive.google.com/file/d/1OiCXRb6Gu5A_hrG_zTeCTINgO5VMXkwH/view?usp=drivesdk