Database Users

Alarm doesn't work properly

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.

Official 2.3.4 - Alarms not working

I've set two alarms during the day ("wake up" and "finish to work") but they doesn't works.
Lock screen says, for example, "Friday 6:30pm" but at 6:40 nothing have ringed, and lock screen continues to show "Friday 6:30pm" even if the date and time is passed.
I have waited 30 minutes but nothing changed...
With Stock Froyo 2.2.2 Alarms worked well.
Now I'll risk to not wake up in time!!!!!
PS: I'm talking about STOCK 2.3.4 without root, CustomROM or others hacks.

emandt said:
I've set two alarms during the day ("wake up" and "finish to work") but they doesn't works.
Lock screen says, for example, "Friday 6:30pm" but at 6:40 nothing have ringed, and lock screen continues to show "Friday 6:30pm" even if the date and time is passed.
I have waited 30 minutes but nothing changed...
With Stock Froyo 2.2.2 Alarms worked well.
Now I'll risk to not wake up in time!!!!!
PS: I'm talking about STOCK 2.3.4 without root, CustomROM or others hacks.
Click to expand...
Click to collapse
It should work. Do you have an alarm sound picked, the correct day picked for the alarm, and check mark checked for the alarm?
Sent from my Atrix 4G with XDA Premium App

Sure.
For example we can take Today (friday): lock screen shows "Friday 7:50am" but now it's "Friday 10:16am"....That alarm is enabled from Monday to Friday at that time.
To avoid restart, I need to go to Alarm app, uncheck and check "Alarm active" checkbox, and then the Alarm will be active ONCE for next time.....

Mine are working they just went off this morning. 2.3.4 on ken's rom here.

My alarms are working fine after the Official 2.3.4 OTA
Didn't need to alter anything after it updated from Froyo.

Mine work also

This has also happened to me. When I try to change the volume, only the alarm volume is silent, no matter what sound I choose. After the alarm fails to sound, if I touch the volume, my phonr reboots?

Dismissing alarm disables current day from alarm settings

Not sure if this is specific to my ROM, but probably not, as it's a TouchWiz ROM, so I'm guessing someone could see this issue with the stock ROM as well.
I've got a T-Mobile S5 (SM-G900T), running XtreSoLite 2.1 Lollipop XXU1BOC7.
When I dismiss my alarm in the morning as it's going off, it "unchecks" the current day from the alarm settings. So I have my work alarm set to go off at 7am, monday thru friday. Today (thurdsay), it goes off, I wake up, swipe it to turn it off. Go into the alarm app and see that now my work alarm is only set for mon, tues, weds, and friday. It's been doing this every day for about 2 weeks. It definitely worked for months after I installed the ROM, so I'm not sure what the hell happened to make this start.
Any ideas?

Alarm Issues since update?

I use SleepBot for my alarm. It's always worked just fine. As I go to bed I switch my profile to alarm only. Since the update it doesn't work as it should. I'll set the alarm the night before, wake up (after the alarm should have gone off) and unlock my phone and the alarm starts going off as if it should have been already. Just wondering if anyone else has these issues. I pull down notification bar and it says Alarms Only which it should.

try excluding the app from battery optimization.
Sent from my Nexus 5 using Tapatalk

Thank you.

Alarm app won't wake phone

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.