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.
Ok so first I've had this issue on two phones and across three different roms so I'm not sure what if any app is causing the issue or if it's some hidden setting I've screwed up somewhere. It first started on my Nexus 5 when I was running Paranoid Android. I was having issues with that ROM and my weather app FCing so I switched over to catalyst. The issue would come up more when I switched over to catalyst. I thought maybe it was just an issue with the phone/ROM and I recently purchased the Moto X Pure. When I first got the phone I did a straight transfer of settings and things but the issue persisted on the new phone. So I did a factory reset, deleted EVERYTHING and started over. This time I manually added my google account and re-added all my apps from a backup. I made sure to exclude every app that might cause an issue (anything like automate, tasker, etc).
The problem is, seemingly randomly my phone will set itself to lock. For example my phone was on ring when I went to dinner, I put the phone in my purse, it was in ring when I got home (I got a facebook notification) and I set it on the table. I just picked it up to make a phone call and it was on vibrate, I never touched the phone. This happens randomly throughout the day, at home, away from home, there doesn't seem to be a pattern. IT can happen at night, it can happen in the morning or afternoon. When I try to turn the volume back up it doesn't let me. It will only let me change from vibrate to silent, and the different notification override settings, but I cannot turn the ringer back on. If I reboot the phone the ringer comes back just fine. Sometimes it stays for a day or two sometimes it goes right back into the 'locked' vibrate mode within an hour.
I've removed every app from my phone that could cause it, I have no automation apps or anything that has a mode that sets stuff like that. I've checked moto's settings (which wouldn't account for ths happening on my Nexus), and I've checked the Google settings in Interruptions and there is nothing set there that seems to cause this issue. Thoughts?
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.
I use Timely as my timer for my breaks at work. Also I use it as my alarm to wake up. At first I couldn't get the countdown timer to show in the notifications or update as it counted down.
After going into power managagement and turning off all power saving policies, I could see the timer countdown but only until the phone locks. Once locked it won't show the timer at all. The alarm I set is the same way it didn't go off or wake up phone, but as soon as I hit the power button to turn on the lock screen then alarm went off.
I've tried turning off smart power-save all together as well with no luck. I use smart lock so my phone shouldn't even lock when I'm at home but still didn't work.
Any other ideas or features to that I could try ? I've been using Timely for the past couple years on multiple android devices and never had this issue before. Any help would be appreciated.
I use Timely without any issue and it wakes me up every morning . What device are you using? What ROM? root? Xposed? Any battery saving app?
Yep.
Yes, I've been using Timely on every Android for the past 3 or 4 years. It miserably failed on the Axon 7. Every measure I took came to no avail. Uninstalled. Anyway, they stopped updating it on February 2015. Using "Alarm Clock Xtreme Free" currently.
Yurik46 said:
I use Timely as my timer for my breaks at work. Also I use it as my alarm to wake up. At first I couldn't get the countdown timer to show in the notifications or update as it counted down.
After going into power managagement and turning off all power saving policies, I could see the timer countdown but only until the phone locks. Once locked it won't show the timer at all. The alarm I set is the same way it didn't go off or wake up phone, but as soon as I hit the power button to turn on the lock screen then alarm went off.
I've tried turning off smart power-save all together as well with no luck. I use smart lock so my phone shouldn't even lock when I'm at home but still didn't work.
Any other ideas or features to that I could try ? I've been using Timely for the past couple years on multiple android devices and never had this issue before. Any help would be appreciated.
Click to expand...
Click to collapse
ohc1492 said:
Yes, I've been using Timely on every Android for the past 3 or 4 years. It miserably failed on the Axon 7. Every measure I took came to no avail. Uninstalled. Anyway, they stopped updating it on February 2015. Using "Alarm Clock Xtreme Free" currently.
Click to expand...
Click to collapse
I have the Axon 7, stock with b29 software, not rooted. I'm going to give Alarm Clock Xtreme a try tonight and see what happens.
I use Timely and it's randomly off by as much as 8 minutes. Usually it's 4 minutes late when the alarm goes off. And no I'm not sleeping through 4+ minutes of an alarm, my alarm is a song and I wake up right from the start of it. This is annoying since it forces me to set my alarm to earlier to make sure I'm not late, but then sometimes it does work on time so I've woken up a little early for nothing.
It's always been like this for me, before bootloader unlocking, before root, before Xposed or anything. Now I'm BL unlocked, rooted, with Xposed, etc, installed and I'm still having the exact same issue. B29 of course, prior versions had the same issue.
Alarm clock Xtreme did work for me last night with no issues. Woke the phone right up even with Smart power save enabled, and allow deep sleep in the power management features turned on. (That's how it was configured at install, and I didn't change anything)
I will miss some of the features of Timely, but I guess it's time to move on if they're no longer supporting it.
Hello!
I'm running a stock Verizon HTC 10 with the latest OTA updates. This phone seems to have a problem with push notifications after it has been "sleeping" or idle for awhile. I don't know exactly what that time period is, but it seems to be about 30 minutes. Once the screen goes black and the phone has been idle in this state for this time period, the phone stops getting (or checking for-however that works) push notifications. There is no blinking LED or sound notification that mail has come for gmail or Outlook. The phone will still answer calls and notify upon receipt of text messages. Usually within a few seconds of turning the screen on from the idle state, the gmail and Outlook notifications come. When the phone screen is on, or within a few minutes of turning the screen off, the push notifications will still come, but then stop.
I googled about this, and there seems to be quite a bit of discussion about it. I have tried the suggested remedies, but they don't work (unsync/sync gmail, clear data/cache for the apps, turn battery optimization off, delete/re-add accounts, along with some others). For work, I have a Samsung Galaxy S7, and it doesn't have this problem. Furthermore, my wife also has an HTC 10, and her phone doesn't seem to have the problem either (although I have not tested it thoroughly).
I've been through various settings, checked the do not disturb settings, but I can't seem to figure this out. I am probably missing some setting. It seems that the phone is going into some deep sleep mode after a period of time and disabling these apps, but keeping others, like the phone and SMS functions, alive.
Any suggestions?
Thanks!
jbhtexas said:
Hello!
I'm running a stock Verizon HTC 10 with the latest OTA updates. This phone seems to have a problem with push notifications after it has been "sleeping" or idle for awhile. I don't know exactly what that time period is, but it seems to be about 30 minutes. Once the screen goes black and the phone has been idle in this state for this time period, the phone stops getting (or checking for-however that works) push notifications. There is no blinking LED or sound notification that mail has come for gmail or Outlook. The phone will still answer calls and notify upon receipt of text messages. Usually within a few seconds of turning the screen on from the idle state, the gmail and Outlook notifications come. When the phone screen is on, or within a few minutes of turning the screen off, the push notifications will still come, but then stop.
I googled about this, and there seems to be quite a bit of discussion about it. I have tried the suggested remedies, but they don't work (unsync/sync gmail, clear data/cache for the apps, turn battery optimization off, delete/re-add accounts, along with some others). For work, I have a Samsung Galaxy S7, and it doesn't have this problem. Furthermore, my wife also has an HTC 10, and her phone doesn't seem to have the problem either (although I have not tested it thoroughly).
I've been through various settings, checked the do not disturb settings, but I can't seem to figure this out. I am probably missing some setting. It seems that the phone is going into some deep sleep mode after a period of time and disabling these apps, but keeping others, like the phone and SMS functions, alive.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Are you using power saver mode? What about the boost+ app?
Also a lot of people started having similar issues after the first update to Nougat for U.S Unlocked. Later updates fixed the issue, but it sometimes still happening with Gmail for me.
Tarima said:
Are you using power saver mode? What about the boost+ app?
Also a lot of people started having similar issues after the first update to Nougat for U.S Unlocked. Later updates fixed the issue, but it sometimes still happening with Gmail for me.
Click to expand...
Click to collapse
I am not using power saver mode, and the Verizon version doesn't have the boost+ app installed.