alarm issues?

[Guest AlunJ]

Anyone have any alarm issues with mcr3.1??

I was 1.5 hours late for work this morning because it didnt go off, I had checked the time, day and alarm volume last night and all was set correctly, the only difference to previous days was that last night I left in on charge as it was a bit low.

:)

[Guest Marcony0]

Anyone have any alarm issues with mcr3.1??

I was 1.5 hours late for work this morning because it didnt go off, I had checked the time, day and alarm volume last night and all was set correctly, the only difference to previous days was that last night I left in on charge as it was a bit low.

:)

Did you kill by any chance the clock application by some task manager ? keep that im mind that if you do so, there is no alarm to set on! just in case you did, put it on ignore list :)

[Guest AlunJ]

ah you may be onto something :)

i just assumed as the alarm icon was shown in the notification bar that it was still running, but now you mention it I do tend to clear running apps with advanced task killer.

Edited January 19, 2010 by AlunJ

[Guest uk786]

yep you've killed it :)

happened to me before..

[Guest keef319]

Be careful not to assume that if it's not killed by TasKiller (or similar app) it'll still go off.

My clock is in the ignore list but the alarm STILL can't be relied on. I've had this problem since the stock T-mob ROM, so wouldn't blame MCR3.1 (or any other ROM).

It'd be worth trying a different clock app from the market, or not using the Hero.

That's my advice.

Others may find the alarm totally fine...

[Guest Olatho]

Mine was completely unreliable the first weeks I had the phone, but it's been fine for a while now.

- Until this morning. Fortunately I usually wake up by myself at the right time, so I guess I'm lucky that way, but highly annoying anyway.

I think there are several issues related to this "common" problem

1) You have killed the clock applet (as other have mentioned).

Even if the time in the taskbar is correct and the alarm icon is visible, the clock-app might not run, so the alarm never triggers.

2) Some other app have force closed and that blocks the alarm.

I believe this is what happened to me this morning. Another app had force closed diring the night and the warning was still open when I unlocked the phone when I woke up.

3) The clock applet is either not updating at all, or getting delayed.

This has happened to me on a few occations. When I unlock the phone, I can se the time jumps from something like 04:36 to 08:07 and the alarm that should have gone off an hour earlier goes off.

It is a shame, as the clock should be one of the most basic thing to get "correct" on any electronc device these days.

On a completely unrelated note - it also annoys me that I have 3 or 4 digital clocks in my kitchen, and none of them runs correctly over time. The one on the micro oven actually delays itself with about 2 minutes every week...

=;-)

[Guest pulser]

On a completely unrelated note - it also annoys me that I have 3 or 4 digital clocks in my kitchen, and none of them runs correctly over time. The one on the micro oven actually delays itself with about 2 minutes every week...

=;-)

On a similarly completely unrelated note, I guess those clocks aren't using quartz for their timing. If they are mains devices, they often rely on the frequency of the mains signal (50Hz in UK/EU, 60Hz in US) to keep to time.

But it doesn't take a genius to realise that the issue with mains timing is that the power companies have to keep the *average* frequency at 50/60Hz with a tolerance. So if it drops for a bit, they just push it up later on. Normally this evens it out, but it's not guaranteed. If it is cheaper to always come in at the lower end of the tolerance, they'll likely do it. Over a week, 2 minutes is equal to only 6000 cycles (in UK/EU) lag. That might explain it, but there's no point in worrying about it. It could also be an issue with internal electronics being 'cheap' if the mains is OK but it still doesn't keep time.

Quartz on the other hand uses a 32,768 Hz signal. A hell of a lot more accurate.

So, apologies for the random, probably boring info about clocks. Probably the least interesting post I've made on these forums. Sorry for the off-topic.

[Guest Marcony0]

On a similarly completely unrelated note, I guess those clocks aren't using quartz for their timing. If they are mains devices, they often rely on the frequency of the mains signal (50Hz in UK/EU, 60Hz in US) to keep to time.

But it doesn't take a genius to realise that the issue with mains timing is that the power companies have to keep the *average* frequency at 50/60Hz with a tolerance. So if it drops for a bit, they just push it up later on. Normally this evens it out, but it's not guaranteed. If it is cheaper to always come in at the lower end of the tolerance, they'll likely do it. Over a week, 2 minutes is equal to only 6000 cycles (in UK/EU) lag. That might explain it, but there's no point in worrying about it. It could also be an issue with internal electronics being 'cheap' if the mains is OK but it still doesn't keep time.

Quartz on the other hand uses a 32,768 Hz signal. A hell of a lot more accurate.

So, apologies for the random, probably boring info about clocks. Probably the least interesting post I've made on these forums. Sorry for the off-topic.

Never knew.

----

My default clock in my Hero never failed me unless i messed it up, like silenced the volume of the alarm - killed the app by Task Killing widget - or simply forgetting to mark to wake me up or selected wrong days :) so i dunno how you guys manage to blame the clock :)

[Guest wedgelol]

I had major issues with the alarm that came with the stock Hero ROM, was late to work twice because of it. Have been using Klaxon for the last month and have had zero issues with it so far.

[Guest ibbessi]

I have the same problem. I thought the alarm didn't work because I usually put my Hero in 'fly mode' during the night. Unfortunately, the alarm didn't work even if the phone is connected (wi-fi and 3G). :)

I'm still trying to figure out how fix this bug.. in the meantime I'll search for an app in the market.

Sorry for my poor english and cheers from Italy. :)

[Guest darkskiez]

I had a problem with the alarm, and it turned out the alarm volume had set itself to 0, and its pretty non obvious how to find out what the alarm volume is set to, and to change it.

Go into the alarm set up screen and then adjust the volume from within that screen with the side buttons and check its not at 0.

[Guest Andcr]

yep, I also had the issue that the volume was at 0

took me a long time to find out what caused the alarm to not go off

I installed Volume Control to easily change the alarm volume

thanks for the button tip darkskiez, didn't know that :)

[Guest ibbessi]

I'm pretty sure the problem was Task Panel that killed the process during the night! Without Task Panel the alarm works :)

P.S. to raise the volume of the alarm, use the volume keys on the side of the phone while you're choosing the ringtone of the alarm! :)

[Guest Nesousx]

Mine was completely unreliable the first weeks I had the phone, but it's been fine for a while now.

- Until this morning. Fortunately I usually wake up by myself at the right time, so I guess I'm lucky that way, but highly annoying anyway.

I think there are several issues related to this "common" problem

1) You have killed the clock applet (as other have mentioned).

Even if the time in the taskbar is correct and the alarm icon is visible, the clock-app might not run, so the alarm never triggers.

2) Some other app have force closed and that blocks the alarm.

I believe this is what happened to me this morning. Another app had force closed diring the night and the warning was still open when I unlocked the phone when I woke up.

3) The clock applet is either not updating at all, or getting delayed.

This has happened to me on a few occations. When I unlock the phone, I can se the time jumps from something like 04:36 to 08:07 and the alarm that should have gone off an hour earlier goes off.

It is a shame, as the clock should be one of the most basic thing to get "correct" on any electronc device these days.

On a completely unrelated note - it also annoys me that I have 3 or 4 digital clocks in my kitchen, and none of them runs correctly over time. The one on the micro oven actually delays itself with about 2 minutes every week...

=;-)

I noticed exactly the same using stock rom and MCR. Even if I can wake up "alone" most of the time, I keep using an alarm clock, but definetly not the Hero!

[Guest bazzawhite]

I noticed exactly the same using stock rom and MCR. Even if I can wake up "alone" most of the time, I keep using an alarm clock, but definetly not the Hero!

Yep that happens to me too (clock jumping from one time to another) but the alarm works as intended and on time. I too have been stupid by killing the clock applet using other apps. I have since left the clock app running and it works fine.

[Guest GaardenZwerch]

Yep that happens to me too (clock jumping from one time to another) but the alarm works as intended and on time. I too have been stupid by killing the clock applet using other apps. I have since left the clock app running and it works fine.

How does one restart com.htc.android.worldclock?

I find that it dies occasionally and I don't know how to restart it short of rebooting my phone.

BTW: I have 3.2b5, and uninstalled all task killers but worldclock disappears every few days anyway..

Thanks,

Frank

[Guest Dreaming Sheep]

Had similar issues too, been trhough most of those as I work shifts that can change daily and stay at two different houses on a regular basis, so a normal alarm clock's a pain in the arse.

I've had the volume set to 0 (phone on silent/vibrate), killed the app and switched it off while on auto-pilot. Solution:

1. Install a seperate app, I'm currently using Alarming! as you can set it to ask a maths question or to press on all the white dots on screen before it will switch off (lots of other apps are available too). It also has an option to play the alarm audio even if the phone is on silent.

2. Added the alarm app to my ignore list.

3. Installed Locale (was much better when it was a free beta, very buggy now so be careful) and the All Volume plugin and set a condition that at 05:00 in the morning all my volumes are set to 80%.

4. Added a second condition that when I get to work all the volumes are set to 0.

You can also set Locale to open the app at a certain time (if your alarm is set for 06:00, set Locale to open the app at 05:50 for example) which can then sort out any force close errors on that app or if it's accidentally killed by an app or system, then it's open.