I've been experiencing a weird issue where when an alarm is supposed to go off it beeps once and then silences itself immediately. I tried changing the Maximum alarm duration but it still silences itself after one beep.
I'm on CM6 RC3. This didn't happen on CM6 RC2 or the 8/01 and earlier Nightlies.
I have the exact same problem as yours.
Mine is Motorola android and the system was updated 3 weeks ago. There were some problems after the update but I reset the phone and fixed everything.
The alarm is always working fine until today.
No matter what I set the alarm, it always has one ring tone (the one I set) and then a notification shown as 'Alarm silenced after 0 minutes'.
Related
Hallo,
I seem to have the following problem with WM5.
it happens sometimes that the alarm rings, however the notification message does not appear and I can't turn the alarm off. So it keeps ringing a lot of time, even if I disable alarms and notifications. If I turn off the volume (which is not a solution anyway) it still vibrates. Also, the red light in the upper right corner keeps on flashing. Soft resetting the device doesn't solve the problem: after reloading, the alarm is still ringing.
I have 3 alarms that are set to ring at an interval of 10 minutes, like 7 am, 7.10 am, 7.20 am.
It looks like this happen when the third alarm rings and the device is turned off.
Has anyone experienced the same problems?
any clue?
thanks
I am now running on wm6 does anyone have any alarm issues, my alarm just plays the alert once (about 2 sec) which is really useless wm5 would play the tune for 1 min or so
No notification
Mine is different. The alarm sounds but I cannot dismiss it, since no notification is show. It just stays there and beep FOREVER... Annoying.
I am searching this now and it seems it is a notification queue issue.
I've got a very strange problem with my alarm clock.
Let's say, i set the alarm at 9:30am, but i wake up at 9am and turn the alarm off, the alarm will still start to ring at 9:30am, even though i turned it off. That small icon with the alarm clock disappears as well, but anyways the alarm starts to ring.
It is espacially annoying when you're in uni and your phone starts to ring (even though the alarm is off and it is in silent mode).
Has anyone experienced a similar issue?
I'm on JP6 with JPM Modem and SpeedMod Kernel.
skyworxx said:
I've got a very strange problem with my alarm clock.
Let's say, i set the alarm at 9:30am, but i wake up at 9am and turn the alarm off, the alarm will still start to ring at 9:30am, even though i turned it off. That small icon with the alarm clock disappears as well, but anyways the alarm starts to ring.
It is espacially annoying when you're in uni and your phone starts to ring (even though the alarm is off and it is in silent mode).
Has anyone experienced a similar issue?
I'm on JP6 with JPM Modem and SpeedMod Kernel.
Click to expand...
Click to collapse
I had the same issue on a stock eclair, however I never tried it on Froyo.
But it's indeed very annoying.
Is there no way to fix this issue, or has it already been resolved in newer firmwares?
Is anyone else experiencing these bugs?
This usually happens after an alarm has went off or if i have not noticed that one has been going off.
* The bottom speaker just turns off, no sound is received. So i'll get a phone call and i answer but no one can hear me, reboot fixes the issue but wtf.
* just 10 min ago the alarm went off to remind me of something and i hit dismiss and the phone went back to the main tiles. I tried to lock the phone and it didn't do anything. I hit the back button and nothing happened, i then try to navigate and the screen is frozen. Live tiles are still moving but no input is read. The power button doesn't work as well, i had to pull the battery.
Anyone have these problems?
I have the same issue about the alarm. I have multiple alarm setup and then if one of them alarms go off and i didn't turn it off the screen just froze, there is no input from the touchscreen but the tiles are working. I guess it is a bug in the programming that disables the touchscreen if the alarm that goes off wasn't turn off.
Hopefully this is fixed with the rumored update on thursday.
Alarm Bug
+1 with the alarm bug. Hope the software update fixes the poor sound level as well, as a working alarm would be nice but a working alarm that i can hear is much better
+1
Same problem
I use Nokia X2 for alarm clock
Alarm Problems
I use an app called Nightstand clock from the Marketplace. The sound of the alarm tones is much louder than wp7 alarm tones. Give it a try it hasn't let me down yet & more importantly has never froze. It can even run under the lockscreen. It hasn't affected the sound on my HD7 either.
Well i have the same problem and for now i download alarm clock 7 and only works if the phone its not lock cause in lock status the alarm does not sound.
I also have this problem
alarm goes off, and if i don't hit dismiss and let it run, the mic gets turned off
grrr
+1, i am also having the same issue
+1, i am also having the same issue. :laugh:
I have HTC HD7
Hi I was wondering if I was alone on this but ever since the new update, my alarm would not sound (but screen turns on) if the alarm is using either the Snooze or Dismiss 'Side keys behaviour'. The alarm does sound when the side keys behaviour is set to none though! I've tried both using mp3 files and the default ringtones.
Extra details:
I found that using default ringtones will make the alarm sound BUT for only half a second and never again.
Phone is not on silent mode and alarm volume is up.
Phone is up to date, tried restarting but no differences.
edit: I found that the alarm will not sound as long as the global volume slider for alarms is less than or equal to that of the volume slider on the individual set alarm! this is a weird occurrence
edit: scratch that
Thanks for reading!.
Hello there,
having same issues with alarm since 5.1.1 update. Last 4 days alarm worked fine for 2 days, did not work for other 2 days. Screen is lit up, but there is no sound.
Did not really check what causes it, but I have side keys behaviour on dismiss for sure.
Guess I'll try to increase the global volume slider and see what's up.
Thanks for the post!
temptemperance said:
Hi I was wondering if I was alone on this but ever since the new update, my alarm would not sound (but screen turns on) if the alarm is using either the Snooze or Dismiss 'Side keys behaviour'. The alarm does sound when the side keys behaviour is set to none though! I've tried both using mp3 files and the default ringtones.
Extra details:
I found that using default ringtones will make the alarm sound BUT for only half a second and never again.
Phone is not on silent mode and alarm volume is up.
Phone is up to date, tried restarting but no differences.
edit: I found that the alarm will not sound as long as the global volume slider for alarms is less than or equal to that of the volume slider on the individual set alarm! this is a weird occurrence
Thanks for reading!.
Click to expand...
Click to collapse
I've had this problem since day 1 of upgrading to 5.1.1 from 4.4.4.
If I set the side keys action to "none" then everything works just fine, but as you mentioned, if set to dismiss or snooze, then the phone seems to automatically perform the action without me touching it. That's why we only hear the alarm for a split second. I was late to work two days in a row before I figured this out.
Though, what exactly do you mean by the global volume dictates whether or not the alarm will sound? I'm not sure I understood. I may need to try this.
PuffDaddy_d said:
I've had this problem since day 1 of upgrading to 5.1.1 from 4.4.4.
If I set the side keys action to "none" then everything works just fine, but as you mentioned, if set to dismiss or snooze, then the phone seems to automatically perform the action without me touching it. That's why we only hear the alarm for a split second. I was late to work two days in a row before I figured this out.
Though, what exactly do you mean by the global volume dictates whether or not the alarm will sound? I'm not sure I understood. I may need to try this.
Click to expand...
Click to collapse
You know when you press the side volume button that dropdown pops up at the top of the screen? If you click the button on the right of that dropdown, you get options to change the volume of Ringtone, Media, and Alarm volume; I called this the global volume. Then in our alarm edit there is a "Alarm volume" slider for each alarm. So I think I found that as long as the individual alarm volume is greater than that global alarm volume setting, the alarm will sound.
Could test this with a quick alarm one minute from now
I caught my bus late twice because of this I thought I was just getting used to my loud neighbour's 5 am parties.
I'm just glad I'm not the only one having this issue. I posted about it nearly 2 weeks ago and got no response. I did a full wipe before upgrading, then re-wiped again, then flashed the US firmware from two different members. Nothing solved the problem. Now I have to use the screen to snooze or cancel the alarm, which is harder to do when you're half-asleep.
The global volume slider thingie works... kind of...
if the global volume slider for alarms is higher than volume slider for specific alarm, it will sound even with side keys behaviour set to dismiss.
However, once the alarm sounds, it sets the global slider to the same level as is the alarm slider that just triggered. This means on the next day alarm won't sound, bcs global and specific alarm sliders are even (and even is not good enough, global just has to be higher).
Cheers
seerixx said:
The global volume slider thingie works... kind of...
if the global volume slider for alarms is higher than volume slider for specific alarm, it will sound even with side keys behaviour set to dismiss.
However, once the alarm sounds, it sets the global slider to the same level as is the alarm slider that just triggered. This means on the next day alarm won't sound, bcs global and specific alarm sliders are even (and even is not good enough, global just has to be higher).
Cheers
Click to expand...
Click to collapse
Geeze - that sucks. I can't believe only a hand-full of us have this problem. What's the deal and how can we fix it?