I've read a lot about people having issues with their alarms. This morning, I had the first one of those.
Alarm was set for 7.30, when I woke up around 8.30 and picked up the phone, it seemed the clock was stuck at 4.30 am and took about 3 seconds to update (not the fancy HTC clock, the one in the notification bar!). I went to bed last night around midnight and didn't touch the phone all night.
Alarm did not go off even belatedly once the clock updated. This is also not a recurring alarm issue since I only set this one last night. Also not a sound issue, the volume was up quite high and not mistakenly set to silent as has happened to some people.
Has anyone else experienced this?
(and yes, I'm still running a T-Mobile G2 stock ROM, too much of a chicken to update to the new leaked ROM! Hoping HTC will roll it out officially ASAP!))
Thanks for any input!
I've had the same problem with my Hero, and I had the same problem with my old XDA Orbit (also made by HTC) that was running Windows Mobile.
I wonder if it's a hardware issue with the way HTC interfaces their firmware with the hardware clock or something like that.
i do also have the same problem, sometimes. it helps to simply reboot the phone. i don't know why it goes in some kind of "deep-sleep", but i hope it will be fixed in the next update.
I've had the same thing (ish) but it was just a crash - I'd been installing and uninstalling apps all night, didn't reboot my phone before going to bed at 11pm. When my alarm failed to go off, I looked at the clock and it was stuck on 11.03pm and the screen wouldn't slide down to unlock, so it had crashed just after I'd gone to bed.
Since then, if ever I'm installing and uninstalling and testing apps and fiddling with settings, I always reboot when I'm done just to make sure nothing's misbehaving. Not had the problem since.
I tend to turn on the alarm each night and turn it off in the morning.
Not had an issue with it failing yet.
Not that that is the right way around it as it should go off at the same time each day when left on all the time.
But it may help if some are having a recurring issue.
Related
hi!
i have a small problem, namely that as soon as i turn on my alarm to wake me up in the next morning, the alarm always goes off at every full hour beginning from 10 o'clock and it doesn't matter at which time i set the alarm. so for example if i set the alarm for 11:30 the alarm will start at 10 o'clock, then again at 11 o'clock and then at 11:30. I already had the same problem when i was using FInixNOver 3.2 so i upgraded to 3.3. it worked for one day or so but then the problem came back. does anyone have a clue to what's going on in my trinity ?
Hi.
I don't know if this well help but as far as I know, relying on the inbuilt system's alarm clock to work properly is a waste of time. Mine used to go off intermittently. In the end I did a hard reset and bought a 3rd party time software (I recommend Spb Time). No more problems.
thankyou very much for your help. unfortunately i haven't tried it out yet, because the problem somehow seems to have resolved itself for no apparent reason. i will see how long this will go on and once the problem occurs again i will do the same thing you died.
thx very much again tho for your reply!
this morning, my g alarm went off and woke me up...i snoozed it as normal, and it rewoke me at the correct interval HOWEVER, after i turned it OFF it kept going off every three seconds. No sooner had the alarm interface dropped it was back on again :S i had to snooze it and uninstall the program entirely as even a soft reset didn't resolve it!
I'm going to reinstall later today, but has anyone else had hassle like this? i've never heard of it!
..IB a n e
I think it should be better to report this to ageye on the thread of G-alarm instead of creating a new thread, no ?
It has some issues with the S2U2, try the latest versions of both (if this is the case)
You're both probably right. sorry, i was just confused by it this morning lol.
The title pretty much says it all......
After a hard reset 2 days ago, I set my phone up as per usual, few reg tweaks, few apps, nothing I hadnt done or used before......
Tested the alarm as I always do, set to go off in a few mins and waited, it worked fine so I set it to wake me up the next morning (whch it did).
However......... when it got to 10.38pm the next day (the time I used to test the alarm) the alarm started going off .........
Checked the settings to make sure I hadnt left it set at that time......I hadnt.....
I only ever use the first alarm and that was set to 4.20am...
I dismissed it as just a bug and forgot about it, last night 10.38pm stupid alarm goes off again (still set to 4.20am and not even turned on...)
Then..... heres the really good bit.... 4.20am this morning, despite the alarm being turned off....... guess what happened......... yup
Ive been through the reg and couldnt see any reason why this is happening...
Its never happened before after any one of numerous HR's.......
Anyone else ever had this problem / know of a fix??
No suggestions to use g-alarm please.........
Cheers.......
Just a small advice
I've had similar problem in past on stock ROM with several official patches. Also another problem when alarm did not started at all.
I got advice from HTC to check and set alarms direcly in WM environment, without using HTC aplication. I did it ones at it was really a help for me.
I think there can sometimes happend some sync issue which is not resolved with simple restart.
What you can do imediatelly: just try to check and set alarms directly in Settings-> Menu-> All Settings -> Clock&Alarms
(In my case I saw here a different time settings than in HTC Sence)
What you can do later: I am on custom ROM without this issue, but maybe it is already solved in latest official ROM releases. So if you did not update it yet, you should
Thanks man, I already went though the WM settings and it didnt work.
Ive never had a problem with the alarm before even when I was on a stock rom...
Ill try clearing everything and resetting it all through WM to see if that helps.....
If not........... hard reset
Thanks again.......
Hello all,
the weirdest thing started happening a few days ago...
first off, let me start off by saying that i am using the default alarm clock. i have already gone throgh the problem of the default alarm clock not going off from time to time... but i seem to have fixed this issue.
so... the other evening i told my girlfriend to lock my legend after she had been using it. the alarm clock was set (i have it set on "daily"). Ok, so morning comes and the alarm clock goes off. Then i realized something was wrong. The phone was turned off. In order to stop the alarm clock I first had to go through the standard procedure of entering the pin code etc. Then once the OS was loaded and all, there was no way to stop the alarm. So I had to shut the phone down again. As frustrating as it was, I though this was my or my girlfriends mistake, as one of us surely had to turn the phone off by mistake before we went to sleep. But this problem keeps on bugging me for the third morning now...
I am positive it's not me... it's the phone.
Has anyone else had the same problem on their legend/android based phone?
If so, does anyone have a solution to it? Before, the alarm clock worked just fine... now, for the last couple of days it seems it has a mind of it's own.
Thanks in advance,
jlasic
Another thing I should have probably mentioned... this happens when i have the phone plugged into the computer via usb cable. dont know if this is of any importance but i thought it would be best to let you guys know.
ps. the darn thing happened again this morning.
hope someone can help me out.
Hey there,
Not sure why it would cause the phone to shutdown, but I recently wondered why my alarm wasn't going off sometimes..it turned out that Task Killer was ending it..dunno if that helps, but thought I'd let you know .
Hey guys, so this has happened the last two nights -- at exactly 2:02am my Droid X locks hard. Just did it again. I have no idea what is going on here but I have to pull the battery.
Last night it was on the charger (And the screen was on) so when I picked it up this morning it said 2:02 on the lock screen. Just now I was listening to music and dead stop -- screen was off but I looked at the clock on my computer and sure enough: 2:02.
Just set the clock manually to 2:01 and started a song -- let us see what happens in one minute.
*SIGH*
My phone has been working generally well..... but then I had a strange issue last night where the phone became super unresponsive accessing the SD, so I rebooted. Then the 2:02 lockup .. and then today the battery drained really quickly. A check of CPU spy and the phone never entered deep sleep. Battery manager showed the phone never going to sleep as the "awake" bar went across the whole screen even though Screen on was less than 1 hour total.
Manual clock set to 2:01 did not result in a freeze as I let it go to 2:03... I just set it to 1:59 to see if that makes a difference.
Stock latest GB, root, debloat done myself (fresh install and debloat a couple weeks ago) .... really at my wit's end with Motorola phones. I have a Droid X2 but find that phone generally unusable due to the extremely lackluster performance including the constant audio dropouts, even with the latest GB release.
Anyone else ever seen this 2:02 thing? Or have any idea where I can even begin to look to fix it? I don't see a crontab file on here. I haven't installed any new apps other than the usual updates that seem to happen every day.
....Manual clock is now at 2:04 (from 1:59) with no freeze. So I don't know WTF is happening. I had rebooted the phone around 8pm tonight .. actually had to pull the battery. Did a "reboot" from the Terminal Emulator and the phone went black and never started rebooting.
I'm so fed up with this damn phone!!
That's not happening to mines
Hard reset your phone n back up SMS, files, etc.
Try different battery!
Sent from my DROIDX