I set an alarm on Saturday (7th) for 8:30am, but now the alarm keeps repeating everyday, even if the alarms at set for a different time, or even when no alarms are turned on.
I checked notifications using the ScaryBear app, there was only 12 things in the list, and no duplicates.
Anyone know how to stop this? It keeps waking me up everyday
http://forum.xda-developers.com/showthread.php?t=302420
I managed to slove this issue (on my xda at least!) See my previous post...
http://forum.xda-developers.com/showthread.php?t=302420
TOM
It seemed to have fixed itself, but I found another problem. If I set an alarm, and then disable it, it still goes off :s
Hi guys,
The past few days, I have been having some issues with the alarm clock on my phone. I have 4 alarms set...12:00, 12:30, 1:00 and 1:30 with no snooze. I have noticed the past couple of days that it seems like not all of the alarms are going off. Yesterday it seemed that the 12 and 1 alarms went off, but not the others. Today, only the 12:00 alarm went off. I ended that one and decided to wake up to the 12:30 alarm. Well, 1:10 rolled around and I woke up, but not to an alarm. I looked at my phone, and it was stuck on the lock pattern screen, and the phone was hot. I could not get the phone to respond, so I powered it off and back on.
I am a little concerned about this, and wondered if anyone could offer any insight. I am stock android, and running openhome for my home. I also have advanced task killer, paid, installed if that might make a difference.
Thanks in advance!
I haven't messed around with the alarm clock yet, but did you make sure your phone wasn't on silent/vibrate only mode? Kind of a stupid response, it seems like a phone's alarm would work even with those modes on anyways.
Hopefully you can get another answer.
Do you have a task killer? If so, uninstall. That will be my bet on why.
Sent from my iPhone with the bigger Gee Bees.
bparkerson04 said:
Hi guys,
The past few days, I have been having some issues with the alarm clock on my phone. I have 4 alarms set...12:00, 12:30, 1:00 and 1:30 with no snooze. I have noticed the past couple of days that it seems like not all of the alarms are going off. Yesterday it seemed that the 12 and 1 alarms went off, but not the others. Today, only the 12:00 alarm went off. I ended that one and decided to wake up to the 12:30 alarm. Well, 1:10 rolled around and I woke up, but not to an alarm. I looked at my phone, and it was stuck on the lock pattern screen, and the phone was hot. I could not get the phone to respond, so I powered it off and back on.
I am a little concerned about this, and wondered if anyone could offer any insight. I am stock android, and running openhome for my home. I also have advanced task killer, paid, installed if that might make a difference.
Thanks in advance!
Click to expand...
Click to collapse
The same thing happened to me this morning, and I was late to work! My alarm did not go off and I woke up seeing my phone showing the lock pattern screen, and I could not turn off the display. I had to turn it off and back on to get it to work normally again.
One thing I did notice was that I received a text message while I was sleeping. It was from AT&T notifying me that I'm close to my data limit. I don't know if either (receiving a text message in general or receiving a text message from AT&T) matters.
bparkerson04, did you resolve the problem or figure out what was causing it?
Using the Alarm Clock Plus app, since I got the Marshmallow update, alarms in the morning have been hit or miss. Seems like it used to go off within a minute (which is also not really very accurate). This morning it was 4 minutes late. Yesterday, the alarm didn't go off at all. Has Marshmallow gone too far with power savings or something? Anyone else having alarm problems?
Using stock alarm app, works fine herw
Sent from my Nexus 5 using Tapatalk
I've been using Timely for its "early rise" function which kicks in 30 minutes before the alarm time with a very quiet tone rising over the course of the 30 minutes. I'm a light sleeper, so I've been setting the alarm time for 30 minutes later so that it goes off very quietly; if "early rise" is off it starts at full volume, which I don't like.
But since I upgraded to Marshmallow the function doesn't work - regardless of whether "early rise" is ticked or not it goes off at the alarm set time.
Coincidence...?
There's obviously something going on with time settings in Marshmallow, since Clocksync doesn't work properly either - a fact recogised by the developer, who has posted a note on his Google Play entry asking for help or advice:
"WARNING: Android 6.0 devices may not work correctly at the moment, even with custom permissive kernel and SuperSU installed. I'm looking for the solution at the moment. Please contact me if you know how to fix it."
Doze will be cutting it's sync times down. Just use stock alarm clock
Sent from my Xperia z5 by Tapatalk
Stock ^^ ☝?
This morning, it didn't go off at all again. Only when I waked up on my own 20 minutes late, wondered what time it was, and turned on the phone did the alarm go off. The Med Helper app reminder also didn't go off till I turned it on, so now two different apps with alarms have failed to work. I think I need to read up on how to re-install Lollipop .
Have you tried turning doze off for your alarm based apps?
What they said ^^^^ tap the 3 dots in battery setting and pick optimizations the select all apps and un-optimize your alarm app.
Sent from my SHIELD Tablet using Tapatalk
OK, I'm trying with battery optimization turned off for the two apps I had a problem with, but I see battery optimization is turned on for the stock "Clock" app, and an alarm I set with it went off on time, so there must be some magic apps can do to make timers work on Marshmallow even if they are battery optimized. If I knew what it was I could write the developers and ask them to include it .
dahawthorne said:
I've been using Timely for its "early rise" function which kicks in 30 minutes before the alarm time with a very quiet tone rising over the course of the 30 minutes. I'm a light sleeper, so I've been setting the alarm time for 30 minutes later so that it goes off very quietly; if "early rise" is off it starts at full volume, which I don't like.
But since I upgraded to Marshmallow the function doesn't work - regardless of whether "early rise" is ticked or not it goes off at the alarm set time.
Coincidence...?
There's obviously something going on with time settings in Marshmallow, since Clocksync doesn't work properly either - a fact recogised by the developer, who has posted a note on his Google Play entry asking for help or advice:
"WARNING: Android 6.0 devices may not work correctly at the moment, even with custom permissive kernel and SuperSU installed. I'm looking for the solution at the moment. Please contact me if you know how to fix it."
Click to expand...
Click to collapse
I use timely and haven't had or noticed any issues. Just this morning I used Smart Rise with alarm set for 11:45am, and on time the music started very quietly at 11:15 am. I love the smart rise feature, however it is terrible if you are already kinda awake, because it's so soothing it will put you to sleep! However to be woken up by it after it had been slowly increasing in volume is a good way to wake up.
Sent from my Nexus 5 using Tapatalk
The Alarm Clock Plus alarm I set after disabling battery optimization for that app just went off on time, so perhaps that is a work around for now, but I'd still love to know how the stock Clock app manages to work even though it has battery optimization enabled.
Nope, it was a false alarm. This morning Alarm Clock Plus did not go off at all, even with the battery optimization turned off for it. However, the Med Helper notification did go off, so the battery optimization change seemed to work for it. Perhaps it has something to do with Med Help using notifications, and Alarm Clock Plus trying to completely wake the phone and display on the full screen?
Alarm Issues
I've experienced the same issues with Alarm Clock Plus. I don't have any battery optimization turned on. It seems to be tied to silent mode and not being able to be silent without do not disturb turned on for me.
For the second time since I've installed marshmallow, my alarm didn't go off. I'm a very light sleeper and today, as with most days, I woke up before my alarm. So I checked my alarm and it was set for just about an hour from then. I drifted back off and woke a half hour after my alarm was set to go off. Everything was set right and I took a couple minutes to reset my alarm two minutes after the current time. It went off. I did the same thing the first time my alarm didn't go off, same results. I've actually tested it several times and it always went off, maybe from not being asleep for that long. I've also been waiting for text replies a few times before and not hear anything, then I check and see I have two or three. Volumes checked, everything's right. Either I'm going crazy or something is wrong with the new update. Just thought I'd add my two cents.
---------- Post added at 10:33 PM ---------- Previous post was at 10:02 PM ----------
Aaronroni said:
For the second time since I've installed marshmallow, my alarm didn't go off. I'm a very light sleeper and today, as with most days, I woke up before my alarm. So I checked my alarm and it was set for just about an hour from then. I drifted back off and woke a half hour after my alarm was set to go off. Everything was set right and I took a couple minutes to reset my alarm two minutes after the current time. It went off. I did the same thing the first time my alarm didn't go off, same results. I've actually tested it several times and it always went off, maybe from not being asleep for that long. I've also been waiting for text replies a few times before and not hear anything, then I check and see I have two or three. Volumes checked, everything's right. Either I'm going crazy or something is wrong with the new update. Just thought I'd add my two cents.
Click to expand...
Click to collapse
androidauthority dot com
I should have read the dates but Google brought this up first. So if anyone happens upon this thread, the above link explains it. The fix is 6.0.1 and is being worked on and even released for some phones already. :good:
Ok can't post links yet but that website has answers
Having the same issue with S7 edge on 6.0.1 using Alarm Clock Xtreme. Won't wake the phone even tho power save is off and auto power save for the at app is off as well. Works if I set it for only a few min from now, doesn't work after the screen being off all night.
I have the exact same problem. It's been three times now that I've been late to class because the alarm didn't go off. Last time Itried setting two alarms five minutes from each other and the iPad alarm. iPad worked, phone didn't. It seems to happen especially often of I place the alarms earlier than usual for some reason, and I only do that when I have an exam to study for, so It's been a fun couple of days.
At first I shrugged it off convincing myself that I had rose in the middle of the night somehow, turned it off and continued on sleeping, without remembering anything in the morning, but after using the iPad to check on the third time I'm pretty sure that it isn't my problem.
Anyway, I use the STOCK alarm clock ALWAYS. I haven't tried it with the doze mode off, I'll try it today, but still. The fact that I might have to purchase an analogical clock because Android isn't working properly it's just disappointing.
I've been having the same problem on my Galaxy Note 5 since updating to 6.0 Marshmallow, and it persists even with today's update to 6.0.1.
The notification tab for the alarm seems to indicate that it thinks it's still 5:28PM, two minutes before the 5:30 alarm time, even though it's well past 6PM now. The last couple missed alarms DID notify me that I'd missed an alarm, about an hour after the alarm time had come and gone. It won't sound the alarm though.
At first I thought it might have just lost touch with the custom tone I've set for my alarms, but now it seems to be that the alarm clock gets stuck a couple minutes before the alarm, even while the system clock goes on as normal.
This is the default clock's alarm feature, not a third party app, so it should not need any developer updates to work right, if Google is doing their job before pushing out system updates.
UncleSim said:
I've been having the same problem on my Galaxy Note 5 since updating to 6.0 Marshmallow, and it persists even with today's update to 6.0.1.
The notification tab for the alarm seems to indicate that it thinks it's still 5:28PM, two minutes before the 5:30 alarm time, even though it's well past 6PM now. The last couple missed alarms DID notify me that I'd missed an alarm, about an hour after the alarm time had come and gone. It won't sound the alarm though.
At first I thought it might have just lost touch with the custom tone I've set for my alarms, but now it seems to be that the alarm clock gets stuck a couple minutes before the alarm, even while the system clock goes on as normal.
This is the default clock's alarm feature, not a third party app, so it should not need any developer updates to work right, if Google is doing their job before pushing out system updates.
Click to expand...
Click to collapse
I had been using darker themes since the update, not liking all the whiteness of the new default theme, but I reverted to the default long enough to test, and the alarm went off today as normal. So it seems that , at least in my case, the themes are impeding the default clock's alarm function somehow, even those I've used that say they're Marshmallow compatible.
Even with CM13's or OmniROM 6's system alarm app, the alarm will not start and be shown as missed when the phone is longer in standby..alarm clock is set as "non optimized" under the battery settings...I hate doze!
Well, since reverting to the default theme, I've enjoyed the calendar widget keeping the current date. But every time since the first time, the alarms still don't go off.
Again, I am using the STOCK alarm and calendar app that came with the Samsung Galaxy Note 5 and its updates, NOT any third-party app. I had been using third-party themes to avoid the stupid whiteness of the new Marshmallow icons (What if I don't want Marshmallow to look like a bunch of marshmallows? What if I liked the Lollipop icons and colors just fine? Eff me.) but reverted to default in a mostly vain attempt to avoid the alarm issues, but the issues persist.
There remains a notification in my taskbar that there is an upcoming alarm at 5:30, even though it's now well past 5:30. The time on the right of the notification is 4:40. So it seems that the clock/calendar's alarm feature is getting stuck in time a little less than an hour before the alarm, and sticks there for hours sometimes, until well past the alarm time. Then sometime far later in time it will suddenly catch up, and HELPFULLY (haha) notify me that I've missed an alarm.
Am I the only one on xdadev that is having this problem with the default app, and default theme? I really wish I could easily revert to Lollipop, since Marshmallow really seems to be a hot mess. I also miss having ADB to push stuff to my FireTV.
I think I always forget about the niggles I have with the CN version of Xiaomi phones and then still buy another. Currently got the EU firmware, and still the same issue.
Common problem for me anyway is the Google Clock app. The alarm fails to go off and the widget still displays the alarm time of the missed alarm, e.g. it says Tue 6am when I do finally wake up, and not display Wed 6am as expected.
I've turned off battery optimisation, and it still fails to go off. If I test it by setting an alarm for a few mins time it works every time.
Similar to Gmail notifications and other apps. When the phone is not used for a while, notifications don't come through until the phone is used.
Any idea how I get the alarm clock to wake up and then wake me up?
Have you tried to lock the app using the recents menu? Open recents using the 3 lined or menu button and then hold the clock app, then select the padlock.
Might keep it active for you
Thanks. Will report back tomorrow if I wake up in time
On top of the memory-lock mentioned above, I'd also recommend turning on autostart for the app
wizpizz said:
On top of the memory-lock mentioned above, I'd also recommend turning on Autostart for the Google Clock app
Click to expand...
Click to collapse
Thanks. I can now see it's tried to autostart several times and been denied so set that to allow. Cheers.
Sadly I didn't wake up this morning (until my iPhone alarm went off.)
The phone just seems fast asleep until I wake it, then it starts receiving all the overnight notifications that my old phone would have just got silently and be there waiting when I look.
I will set an alarm for the morning and report back.
Thanks! I'll try the pre-installed clock app and see if that works.
The Xiaomi clock app works, so seems to be just the Google apps that fall asleep.
Mine went off as planned. Attached screenshot shows it being set off from notifications. Maybe check your notification settings?
Thanks. It goes off if I test it and set it to say 5 mins time, it seems to only be when the phone has not been used for some time, say midnight to 6am, then it seems to have gone to sleep itself. If I wake up early and check the phone, the alarm goes off, so notifications should be ok in that case?
Mine was set night before and in the screenshot you can see that I checked it after 6 and then the phone was left on charge with the screen off as it would normally be over night.
I think I may have fixed it. My alarm has gone off the last two days at least.
I turned off "sleep mode" in battery settings, hidden away under smart scenes.