Related
The whole point of setting the alarm is that you can just leave it and know that it will go off at the assigned day and time. Unfortunately, it is just not reliable at the moment. I have already been late for work once, and have gone back to using my WinMo phone for the alarm, as at least that works every time.
It does seem to be an Android issue, I have seen it mentioned on other forums for other handsets, but I want to track down exactly what might be causing it on the Hero, and if there is a work around until HTC/Android releases fix it.
First off, the screen is switched off, but the phone is stil powered on, just like any other phone when you have the alarm set.
When I got the phone on Thursday, I set the alarm for Monday through to Friday, 10.30am.
Friday morning, the phone wakes and the alarm goes off at 10.30. Fine.
Monday morning, nothing happens. Go into the settings, check alarm set for the correct time and day, all is fine, it just didnt go off.
Tuesday morning, it works fine, phone wakes and alarm goes off at 10.30.
Wednesday morning, nothing. WinMo phone alarm wakes me at 10.34. I switch on the Hero's screen, and immediately the alarm goes off, 4 minutes late!
Last night I didnt charge it, thinking it may be an issue when being charged. But this morning it didnt work, so it is not an charging issue.
The Alarm icon was showing the top corner, so the alarm was obviously set, and the Clock App was still running (I checked in Advanced Task Killer). I will try to set it again tonight from scratch, and see if that works.
Having to set it every night would be a pain, but at least it would actually work like it is supposed to.
I've got the same issue and was about to get late for work this very morning just because of it. Luckily me I've got some sleeping disorders so I woke up before the clock should have went of either way...
HTC Needs to fix the clock in their TouchFLO..
Got somewhat the same problem...
Could a hard reset help?
A hard reset didn't do the trick for me. I really need the alarm clock to work so I think I'll buy an alarm clock app on the market, but I shouldn't have to ...
If you are using taskiller or advanced task manager, make sure you exclude the clock app from killed processes. I had this problem, when the clock came back after being killed the alarm wouldn't work even though the icon was there. Excluding it fixed it.
Cheers Ewans, i was killing the clock process and it was this that stopped my alarm this morning. Made me late! Still, i forwarded my boss this link so he could read himself. (Not that he was mad. He's a great boss!)
We should maybe think about making a list of processes, what they do and what you can/can't kill.
For instance, i don't use the Twitter widget as i find the notification bar and having Peep on my home screen just as quick and less resourceful hungry. But if you kill Peep sitting in the background, it will stop any notifications, so this needs to be left alone.
Even if I don't kill it (noticed that too), it still fails to go off sometimes.
Yes, it is not totally obvious what is going on yet.
The fix (based on one days trial!) seems to just before I sleep to go into the clock app, disable the alarm, then immediately enable it again.
This results in the "Your alarm will sound in 7 hours 10 minutes" type message.
That worked this morning, the question is if I leave it alone now, and dont kill the clock app, will it still work tomorrow? And if I restart the phone, will the Clock app and then the alarm still be running or do I have have to go into the Clock App manually?
If my clock is showing on the home page, and the alarm icon is in the top bar, I expect the alarm to go off.
It should not be possible to kill the alarm process, it shouldnt be part of the clock app at all, but a separate background process with settings controlled by the clock app, but not reliant on the clock app running.
This is what I've found out.
When you program your alarm for multiple days, it only sounds the first day.
If you uncheck and check your alarm, it will go of the next day.
This is without using TasKiller or something similar and without resetting. (just did nothing)
It looks like the multiple day option is a fake and you will have to set it every day. Allthough I haven't tried out multiple alarms, thinking about seven alarms, but you'll have to reset at least once a week.
Good luck waking up
Alarm works fine for me now, I use one for weekdays that goes off everyday, and another just on Sundays at a different time. I'm using a standard G2.
Check out the alarm volume settings.
The alarm has its own volume setting which can be change when you are inside the clock app and select the ringtone for an alarm (by pressing the standard volume up/down keys).
By accident mine was set to lowest value so it didn't go off but just vibrated.
Ok, after a week of testing, it seems that if you dont bugger around with killing the clock app via Task Killer or something else, it is fine.
I havent yet seen whether it will still be set if I completely switch off and switch on again. I will try that tonight. Even though alarm icon is shown, will the alarm be set without me going into the Clock app explicitly?
Works for for me, 2 alarms set for 6:15 & 6:30am mon - fri, never had an issue.
Has anyone else had an issue with their alarm clock not working. Made me late to work this morning.
I tested it by setting the alarm to go off in 5 minutes. This works. But for the last 2 mornings it won't go off. Is the phone in some sort of sleep mode and won't wake for the alarm?
Sent from my SM-G900V using xda app-developers app
wakerash said:
Has anyone else had an issue with their alarm clock not working. Made me late to work this morning.
I tested it by setting the alarm to go off in 5 minutes. This works. But for the last 2 mornings it won't go off. Is the phone in some sort of sleep mode and won't wake for the alarm?
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
I have had the same problem for 3 days in a row now. The phone says that the alarm was silenced after 1 minute. I know it was not.
Today I had it on snooze, three times at 5 min interval. It should have started at 05.15. I woke up at 05.22 turned on the phone, got up. At 05.25 the third snooze started without the first two sounding at all.
It must be in some kind of deep sleep or something... As OP says, it works if I set it to go off in a few minutes.
Any ideas someone?
I have started having issues with the Alarm on my 6P. I have three reoccurring alarms set up throughout the week. Sometimes they work sometimes they don't. It's as if the time is not being recognized because it could be 6:39am and the alarm was set to go off at 6:30am and it'll say upcoming alarm at 6:30am. I do not think this is inherent to the 6P as it seems like others are having issues on other devices running Marshmallow. Is anyone else experiencing this and have any solutions?
There is an issue with 6.0 and the doze feature that puts the alarm to sleep. The only fix is to have it plugged in
zelendel said:
There is an issue with 6.0 and the doze feature that puts the alarm to sleep. The only fix is to have it plugged in
Click to expand...
Click to collapse
I will have to make a note to check. I'm 75% positive my phone was plugged into the charger when the alarm failed to go off. I was also playing a game one of the times and I still had an issue so I'm not sure the doze feature is the culprit.
Macleod52 said:
I will have to make a note to check. I'm 75% positive my phone was plugged into the charger when the alarm failed to go off. I was also playing a game one of the times and I still had an issue so I'm not sure the doze feature is the culprit.
Click to expand...
Click to collapse
Then im really not sure as I have never had an issue with my alarm, but I charge my phone over night and was only recently told about the alarm bug in 6.0. I also use alarm millennium plus.
zelendel said:
Then im really not sure as I have never had an issue with my alarm, but I charge my phone over night and was only recently told about the alarm bug in 6.0. I also use alarm millennium plus.
Click to expand...
Click to collapse
I, too, charge my phone overnight but I'm using the stock clock app. What's weird is that I was running 6.0 on my Nexus 5 for a month or two prior to getting my 6P and I never had a problem. I also just started experiencing this issue within the last week.
Maybe change the clock app to not optimised in the battery settings?
Do you use any app like greenify with aggressive doze? That would sometimes make my clock stop working which could mess up alarms.
__NBH__ said:
Maybe change the clock app to not optimised in the battery settings?
Do you use any app like greenify with aggressive doze? That would sometimes make my clock stop working which could mess up alarms.
Click to expand...
Click to collapse
I'll have to try changing the optimization settings. I don't use any apps that would modify system features like doze or anything like that.
Same issue here. Even tried to not optimize my alarm app. Only way to consistently have the alarm go off was to create an alarm in the stock alarm app to go off a little after. For now, I'm just using stock until this is fixed. Late for work too many times recently.
Sent from my Nexus 6P using Tapatalk
So I have been using Timely for quite a while on my HTC One m7 and Nexus 5, but ever since I started using my Nexus 6P as my daily phone, I have noticed that the alarm is hit or miss. I tried the suggestions from here, but that does not seem to have made much of a difference. I have also tried going to the stock Clock app, it seems to be a bit better, but not by much.
What I have been noticing is that the alarm I have set for 5:30AM it will either go off or it will just not go off at all and I will get a notification that the alarm was missed at 5:30AM. If the alarm does go off, I usually hit snooze and just lay in bed until it goes off again checking email or something on my tablet (so the phone should still be locked). When I realize that I have been awake longer than 10 minutes, I look at my phone and there is a notification that the alarm for 5:30AM was missed... So it realized the alarm should have went off, but didn't.
I also have 2 later alarms (9:35AM and 10:20AM) and both of them are still in Timely and they work just fine, so maybe there is something with the deep sleep in Marshmallow?
I am running the stock image, updated to 6.0.1 via OTA, no root, no custom kernel, nothing that IMO should be affecting the operation of this type of stuff.
Just wondering if anybody else is having similar issues or if somebody can recommend an alarm app that is not suffering from this issue.
It seems that any alarm other than stock has issues. I see the post you referenced mentioned adding exceptions for those apps to prevent battery optimization. Did you try that with no luck? I don't know if there has been much luck other than just using the stock alarm if you really need to depend on it to wake up for work or other important events. I have never had stock alarm not go off, but I don't use any other apps.
fury683 said:
It seems that any alarm other than stock has issues. I see the post you referenced mentioned adding exceptions for those apps to prevent battery optimization. Did you try that with no luck? I don't know if there has been much luck other than just using the stock alarm if you really need to depend on it to wake up for work or other important events. I have never had stock alarm not go off, but I don't use any other apps.
Click to expand...
Click to collapse
I did try turning off optimizations for Timely, that did not seem to help much. The funny thing is that the stock alarm is also having similar issues, so either I am that heavy of a sleeper or maybe I just need to try flashing the factory image back to it, which, like I mentioned, I do not think I did anything to cause this type of issue, but it is an OS after all, so who knows what could anger it.
I did just tonight try setting the auto dismissal time to Never as well as maxing out the volume (it was down by about 10%), so maybe that will wake me up.
I'll see what happens tomorrow morning and will report my findings a little later. In the mean time, if anybody can think of something that I could try, it would be greatly appreciated, although a restore is not the end of the world, I would like it if I didn't have to spend the time restoring the apps and accounts and what not.
Does this apply to you?
gotzaDroid said:
Like Red said, you need to have an alarm set first. AND... Any automatic "do no disturb" settings like, "every day from xx : xx to xx : xx" will override the "do not disturb until next alarm". So if you have the phone automatically do not disturb until 8am every day, but you need to wake up at 6am and set the do not disturb to until next alarm before your usual rules kick in... at 6am, do not disturb will not automatically turn off with the alarm. It'll stay on until 8am. Just FYI.
Click to expand...
Click to collapse
Sent from my Nexus 5X using Tapatalk
I'm on 6.0.1 stock and I use Timely, have no issues at all...
For what it is worth, after I set it that the Stock Clock Alarm Never gets dismissed and made sure the alarm volume was set to 100%, it has been going off like... umm, clock work. I tried doing Timely last night and made sure I had another alarm setup just in case, I noticed the Stock Clock alarm went off on the other device, but my 6P with Timely, did not go off.
I'm just going to give up on Timely for now, maybe they will release an update and I will give that a shot, but for now, Stock it is.
The new doze mode will impact any alarms apps that are not updated for android M to use GCS etc. that's why your alarms are not firing.
For now you have to use the stock google alarm which correctly works with doze mode.
Hi guys. I am running everything stock (not rooted etc.) and this morning my alarm did not go off and I got a missed alarm notification. I'm on the latest 6.0.1 build MHC19Q with the latest 4/2/16 security update. I checked multiple times by setting up the alarm again, and again another missed alarm notification with the screen off and the phone locked. I did have DND set to Alarms only, and I checked the alarm volume was fine. I powered off the phone and then back on, and now everything is fine. I hope this was a fluke! Luckily today was my day off, but now I'm VERY nervous about being late to work. I am using the stock clock version 4.3 app, and the phone was plugged in to charge.
Mine got diff issue. My alarm went off this morning but now I can't disable the alarm disturb mode.
It just fixed itself
Spoke too soon. Broken again.
mhajii210 said:
Hi guys. I am running everything stock (not rooted etc.) and this morning my alarm did not go off and I got a missed alarm notification. I'm on the latest 6.0.1 build MHC19Q with the latest 4/2/16 security update. I checked multiple times by setting up the alarm again, and again another missed alarm notification with the screen off and the phone locked. I did have DND set to Alarms only, and I checked the alarm volume was fine. I powered off the phone and then back on, and now everything is fine. I hope this was a fluke! Luckily today was my day off, but now I'm VERY nervous about being late to work. I am using the stock clock version 4.3 app, and the phone was plugged in to charge.
Click to expand...
Click to collapse
I had the same experience this morning. Stock Mate 9 (Australian edition?) with DND and alarms enabled. Alarm volume was up.
The alarm just did not go off (no vibrate, no noise, nothing). After unlocking the phone and checking alarm settings (same as yesterday) I got a notification that I had "missed an alarm". I've had alarms not go off in the past, but usually because an update had shut down the phone or something similar.
I did install 27 app updates yesterday... and uninstalled updates for Huawei Mobile Services which I was attempting to disable (trying to remove Huawei crap from my device). Perhaps that is related?
nacayoda said:
I had the same experience this morning. Stock Mate 9 (Australian edition?) with DND and alarms enabled. Alarm volume was up.
The alarm just did not go off (no vibrate, no noise, nothing). After unlocking the phone and checking alarm settings (same as yesterday) I got a notification that I had "missed an alarm". I've had alarms not go off in the past, but usually because an update had shut down the phone or something similar.
I did install 27 app updates yesterday... and uninstalled updates for Huawei Mobile Services which I was attempting to disable (trying to remove Huawei crap from my device). Perhaps that is related?
Click to expand...
Click to collapse
Alarm failed again this morning, even after updating all apps earlier in the week.
This time I've power-cycled and once back in, I got the "alarm missed" notice.
The alarm feature on this phone CANNOT be trusted.