I have started having issues with the Alarm on my 6P. I have three reoccurring alarms set up throughout the week. Sometimes they work sometimes they don't. It's as if the time is not being recognized because it could be 6:39am and the alarm was set to go off at 6:30am and it'll say upcoming alarm at 6:30am. I do not think this is inherent to the 6P as it seems like others are having issues on other devices running Marshmallow. Is anyone else experiencing this and have any solutions?
There is an issue with 6.0 and the doze feature that puts the alarm to sleep. The only fix is to have it plugged in
zelendel said:
There is an issue with 6.0 and the doze feature that puts the alarm to sleep. The only fix is to have it plugged in
Click to expand...
Click to collapse
I will have to make a note to check. I'm 75% positive my phone was plugged into the charger when the alarm failed to go off. I was also playing a game one of the times and I still had an issue so I'm not sure the doze feature is the culprit.
Macleod52 said:
I will have to make a note to check. I'm 75% positive my phone was plugged into the charger when the alarm failed to go off. I was also playing a game one of the times and I still had an issue so I'm not sure the doze feature is the culprit.
Click to expand...
Click to collapse
Then im really not sure as I have never had an issue with my alarm, but I charge my phone over night and was only recently told about the alarm bug in 6.0. I also use alarm millennium plus.
zelendel said:
Then im really not sure as I have never had an issue with my alarm, but I charge my phone over night and was only recently told about the alarm bug in 6.0. I also use alarm millennium plus.
Click to expand...
Click to collapse
I, too, charge my phone overnight but I'm using the stock clock app. What's weird is that I was running 6.0 on my Nexus 5 for a month or two prior to getting my 6P and I never had a problem. I also just started experiencing this issue within the last week.
Maybe change the clock app to not optimised in the battery settings?
Do you use any app like greenify with aggressive doze? That would sometimes make my clock stop working which could mess up alarms.
__NBH__ said:
Maybe change the clock app to not optimised in the battery settings?
Do you use any app like greenify with aggressive doze? That would sometimes make my clock stop working which could mess up alarms.
Click to expand...
Click to collapse
I'll have to try changing the optimization settings. I don't use any apps that would modify system features like doze or anything like that.
Same issue here. Even tried to not optimize my alarm app. Only way to consistently have the alarm go off was to create an alarm in the stock alarm app to go off a little after. For now, I'm just using stock until this is fixed. Late for work too many times recently.
Sent from my Nexus 6P using Tapatalk
Related
The alarm on the handset does not go off? Has anyone else had this experience.. I've set it for the whole week.. and not once has it set off the alarm?? Luckily i had a backup alarm incase this one did not work.. Surley this must have a fully working sounding alarm!!!
fojis1982 said:
The alarm on the handset does not go off? Has anyone else had this experience.. I've set it for the whole week.. and not once has it set off the alarm?? Luckily i had a backup alarm incase this one did not work.. Surley this must have a fully working sounding alarm!!!
Click to expand...
Click to collapse
I have not had any problems with the alarm... have used it almost every day for three weeks now...
... But keep in mind that the alarm does not go off if you turn the device off... (that is a bit annoying, since other SonyEricsson phones support alarm while being turned off!.. However.. just set it to flight-mode instead.. problem solved!)
Regards // OwL
Are you using a task manager and killing the alarm clock?
OwLOwLOwL said:
I have not had any problems with the alarm... have used it almost every day for three weeks now...
... But keep in mind that the alarm does not go off if you turn the device off... (that is a bit annoying, since other SonyEricsson phones support alarm while being turned off!.. However.. just set it to flight-mode instead.. problem solved!)
Regards // OwL
Click to expand...
Click to collapse
If i set it to flight mode overnight how can i receive phone calls. My job involves me being on call on some nights.. So if the display of the phone is off you saying i can not get the alarm to sound off in the morning?
fojis1982 said:
If i set it to flight mode overnight how can i receive phone calls. My job involves me being on call on some nights.. So if the display of the phone is off you saying i can not get the alarm to sound off in the morning?
Click to expand...
Click to collapse
No... That was not what I meant... ofcourse having the phone on (normal, non-flight-mode) works just aswell too!.. I meant, if you usually switch off your phone at night, then the alarm wont go off!.. and instead of switching the phone completely off, one can use flight-mode instead...
Leaving the phone on (either in flight-mode or non-flight-mode) causes my alarm to work as it should.
Regards // OwL
I also had a similar issue and tracked it down to the Task-killer killing the alarm application. It took me a while to realise that the 'Clock' on my homescreen had also been stopped when using the 'task manager'. I added the clock to the ignore list and everything has worked fine since then...
fojis1982 said:
The alarm on the handset does not go off? Has anyone else had this experience.. I've set it for the whole week.. and not once has it set off the alarm?? Luckily i had a backup alarm incase this one did not work.. Surley this must have a fully working sounding alarm!!!
Click to expand...
Click to collapse
I had the same problem all last week - and yeah it was my own fault as i was killing all apps with advanced task killer. Only realised that this mornig So don't kill the alarm app.....i wonder what the battery drain is by leaving it on?
cashaw said:
I also had a similar issue and tracked it down to the Task-killer killing the alarm application. It took me a while to realise that the 'Clock' on my homescreen had also been stopped when using the 'task manager'. I added the clock to the ignore list and everything has worked fine since then...
Click to expand...
Click to collapse
Thanks.. Will give this a try tonight.. Hopefully I wont be late for work tmrw
cashaw said:
I also had a similar issue and tracked it down to the Task-killer killing the alarm application. It took me a while to realise that the 'Clock' on my homescreen had also been stopped when using the 'task manager'. I added the clock to the ignore list and everything has worked fine since then...
Click to expand...
Click to collapse
Nice one cashaw.. this has worked a treat!
For me alarm is working but i don't know how to set up the phone to start the alarm when an event in calendar is about to start
Any ideas?
The alarm on my X10 is not working properly. There is a bug somewhere. On at least three occassions it failed to wake me up in the morning. This morning as well and the last thing I did before going to bed was making sure the alarm function was running. I have now tested the alarm a couple of times by creating new alarms and they all work.
btw: The one not working was set to go off every day at 07:00. It did work the first morning.
Phone: Model x10i, Firmware:1.6, Baseband:1.0.14, Kernel:2.6.26-rel [email protected] #2, Build no.:R1FA014
The Doc said:
The alarm on my X10 is not working properly. There is a bug somewhere. On at least three occassions it failed to wake me up in the morning. This morning as well and the last thing I did before going to bed was making sure the alarm function was running. I have now tested the alarm a couple of times by creating new alarms and they all work.
btw: The one not working was set to go off every day at 07:00. It did work the first morning.
Phone: Model x10i, Firmware:1.6, Baseband:1.0.14, Kernel:2.6.26-rel [email protected] #2, Build no.:R1FA014
Click to expand...
Click to collapse
Did you try to ignore alarm in task killer/manager? Since i did that my alarm works fine and it's set to go off every day at 7 like yours.
Ya had the same problem and task killer was to blame. Would definetly start there.
-------------------------------------
Sent via the XDA Tapatalk App
That sounds about right! I think,you should use kaloer clock, much much cooler than the original one!
-------------------------------------
Sent via the XDA Tapatalk App
Hi,
the clock component has got a nasty bug:
1. Set alarm to now + a few minutes
2. Wait for screen to turn off
3. Press home button to look at the current time
4. Let screen go off again
5. THE ALARM DOES NOT SOUND!!
This could cause major chaos - luckily for me I just woke up half an hour later than was planned - I didn´t have to catch a plane or anything thankfully.
Phone is not rooted etc. original out of the box with a few extra apps and widgets installed.
Info. (from Android System Info. App):
1. Build: 2.1-update 1
2. Release codename: REL
3. Running Launcher Pro
Anybody else noticed this?
Cheers,
Mark
I´ve been scanning some forums and it has been suggested that using a taskkiller is a no-go. If that is right then something is badly amiss with the architecture - a non-rooted taskkiller should have no permission to kill, what I would expect to be root tasks such as the alarm.
MoWa22 said:
Yikes - that was a bit harsh. Just got an e-mail from the WSPA demanding me to apologize. I'm sorry, I'm very sorry, that I suggested that Korean mountain monkeys should be responsible for the coding at Samsung.
Click to expand...
Click to collapse
The monkies got really pissed off by your post. They don't give a **** about your phone, and you shouldn't imply that they do.
Sent from my personal Dis-organizer GT-I9000
Using it everyday and I tried several FW no issue
If you have a auto-task killer or you kill a lot clock it's sure that it won't work properly
get this one it's awesome
Alarm Clock PlusV2
http://forum.xda-developers.com/showthread.php?t=765081
it will turn on your speakers, no matter what
it can even TALK to you
it's fantastic!!!
markwil said:
Hi,
the clock component has got a nasty bug:
1. Set alarm to now + a few minutes
2. Wait for screen to turn off
3. Press home button to look at the current time
4. Let screen go off again
5. THE ALARM DOES NOT SOUND!!
This could cause major chaos - luckily for me I just woke up half an hour later than was planned - I didn´t have to catch a plane or anything thankfully.
Phone is not rooted etc. original out of the box with a few extra apps and widgets installed.
Info. (from Android System Info. App):
1. Build: 2.1-update 1
2. Release codename: REL
3. Running Launcher Pro
Anybody else noticed this?
Cheers,
Mark
Click to expand...
Click to collapse
Are you sure that the alarm is the problem?
Lately I experienced problems with the alarm, but the real problem is that the clock doesn't update! It freezes and then suddenly jumps forward to the right time.
My alarm was set to 0700, but when I woke up I immediately understood that I overslept. I looked at my phone and the clock showed 06:48 and I was confused. A few seconds later the clock changed to 1003 which was the right time.
This problems has encountered many times, which makes the phone useless as an alarm clock.
Been using the alarm every morning for the past 2 months now, without any problems.
I also use launcher pro, and have advanced task killer set to aggressive, though with alarm in ignore list. I can press home button to check time after alarm is set, and the alarm will go off as planned.
The only minor thing I'm encountering is that I sometimes find myself turning off the alarm completely by pressing the stop button when the smooth alarm goes off, while still half asleep, when in fact I want to snooze until the real alarm goes off. I somehow need to train myself to press the home button when waking up at the first alarm...
Sent from my GT-I9000 using XDA App
iammichel said:
The only minor thing I'm encountering is that I sometimes find myself turning off the alarm completely by pressing the stop button when the smooth alarm goes off, while still half asleep, when in fact I want to snooze until the real alarm goes off. I somehow need to train myself to press the home button when waking up at the first alarm...
Click to expand...
Click to collapse
I used to do this myself, so I now have three alarms set to go off within five minutes of each other. So far I haven't managed to stop all three.
The bug that i have experienced is that If i wake before the alarm rings and i off it manually by going into "clock" the alarm still rings on the time ive set. Happened to me twice so far and i'm very sure that i have offed the alarm as the alarm sign in the taskbar was not there. The bug only occurs when i set the alarm overnight, If i set it for 2 mins from now and off it halfway, it deosn't ring which is correct.. but leaving it overnight, then waking up myself and offing it, it still rings when the time ive set the night before has reached...
I have this nasty bug with alarm. If I didnt dismiss the alarm, after awhile the alarm screen disappear. After that the screen wont turn off even if I press the power button. Have to klill the clock.
Itsme87 said:
Are you sure that the alarm is the problem?
Lately I experienced problems with the alarm, but the real problem is that the clock doesn't update! It freezes and then suddenly jumps forward to the right time.
My alarm was set to 0700, but when I woke up I immediately understood that I overslept. I looked at my phone and the clock showed 06:48 and I was confused. A few seconds later the clock changed to 1003 which was the right time.
This problems has encountered many times, which makes the phone useless as an alarm clock.
Click to expand...
Click to collapse
Had the same issue, but after disabling "Automatic (Use network provided values)" it's worked fine.
The only reasons that I found that could freeze your phone is too low cpu with setcpu or auto task killer ...
Alarm
Hi,
I disabled all task killers etc. yesterday and set the alarm (with my old mobile as backup!). It worked - I pressed snooze but the alarm did not sound again....
A colleague experienced my original problem this morning and arrived late for work...
My main issue with the sgs is that a "root"-system task like the alarm should not be killable by any other app. not posessing root rights.
Sure I could add the alarm app. to the ignore list of my task killer but it feels wrong and should be unnecessary.
I´ll try the other alarm apps. recommended (and add them to the ignore list of my task killer as they are not native sgs "system" apps.).
Cheers,
Mark
i use the alarm every single day and i dont think i have your issue, and by that i mean i dont ever do the steps that you listed.
the only time i had the alarm not come back on after hitting snooze is when i used the smart alarm. since i dont use check the smart alarm box i have no issues, and i hit snooze 3-5 times every morning!
i did have an issue with the alarm not going off at all and i figured out that if i set an alarm, then pressed the back key while in the alarm app it would close the app and the alarm wouldnt work. just before i go to bed i open the alarm app then press the home button (while the screen is still on) and i have not had an issue in over two weeks.
i do not use task killers any more. i do use the built-in task killer to kill the music player or any streaming apps or i just press the back key while in any other app that i dont want running in the background and my device runs great
No problems here.. Been using my SGS for 3 Months, I've set 3 alarms in the morning M-F.
using Stock FW XJF4 and TaskPanel (task killer)
Hi,
I am also experiencing the same alarm bug.
When i set it and leave the phone unused for a couple of hours it doesn't go off in the scheduled time (and not even after I turn on the screen).
Also the clock doesn't update....for 1-2 seconds after turning on the screen it shows a past time!
I 've searched elsewhere and the problem might be that the phone goes into a deep sleep/suspend state and the alarm app cannot wake it, only by manually turning on the screen.
One solution is to leave it connected to the charger all night, so it doesn't go to deep sleep.
The thing is that i cannot recall having this problem before rooting the phone with OCLF 2.0.
I am wondering if RyanZA's minfree has to do something, and if it is possible to exclude the alarm/clock app from ever being killed.
I am using the latest standard firmware JF5 and Android 2.1 update 1
I've not had that issue, but I'll tell you one thing I've had happen once or twice... if I set the countdown timer, the lock screen sometimes appears over the top of it when it goes off and then when you unlock it, you are just greeted by the home screen and not the clock, despite the thing going off, so you can't turn off, and you can't even switch to the task because trying to do so opens another clock - so you end up having to kill it with the task manager.
I'd actually forgotten about that little bug when I was ranting in another thread.
I've said it before though - I would NOT rely on this phone for anything mission critical.
the stock alarm is crap, don't use it at all
use the app i suggested above, it beats all any other alarm apps hands down
http://forum.xda-developers.com/showpost.php?p=8124064&postcount=44
AllGamer said:
the stock alarm is crap, don't use it at all
use the app i suggested above, it beats all any other alarm apps hands down
Click to expand...
Click to collapse
No good...
Clock still doesn't update during deep sleep/suspend mode and AlarmClock rings only when you switch-on the screen.
Any other help/suggestions?
PDA: JG1
PHONE: JF5
CSC: JF9
OCLF: 2.0
minfree: moderate
i also have the alarm clock problem since day 1 ..
now it's better with fw jm8 anyway...
i don't use taskkillers etc..btw..
but still i had 2 alarm occations that it missed..
i'm thinking it maybe could be amount of available ram that is the cause?
the 2 times alarm have missed is when i have i have forgotten to clear ram using the samsung task manager..
u who have problems....how much available free ram u have?
and have you changed the snooze settings?..(i'm thinking this also could be the problem.... hmmm )
cheers!/H
Right, my alarm seems to be playing up on the HD2. I have the alarm set in the week only Monday - Friday.
As I don't work weekends, I turn the alarm off, and DID double check this last night. But this morning @ 3,40am the Alarm went off?
How is this possible, when I physically turn the alarm off? Getting really on my nerves now if im honest.
happens to me too, seems to come and go.....
hard reset wont resolve it either....
edit;
hard reset probably did resolve it but it occured again after reinstalling all the stuff that I deem "essential"
so its probably caused by something in there....
I really cant think of any link between what I have installed and the alarm function......
That's why I use the old free version of gAlarm still. Windows alarm is unreliable. gAlarm wakes me up every time I want it to, and never when I don't.
Since the old version that I have is freeware, but the app has since become payware, I'm not sure if I can post the cab.
If I can get confirmation from a mod, I'd be happy to attach it for you
I've no answer to this other than to use SPB Time,G-alarm or Klaxon
All 3 work just fine...
I solved the problem with a £3.99 clock radio
I have NO issues at all with the alarm, BUT I set it up using the control panel not via the Manila home page, It's not failed me in months, the snooze (every 5 minutes) works, and if I leave it on it repeats every 45 seconds until I get fed up with it (normaly between 3 and 7 times)
All three alarms work, and I can set a different alarm for each of the 3
I also suffer this problem, the alarm is unreliable.
I heard you can fix it by turning off sense and setting it in windows because these values would become out of sync, but have not tried.
Klaxon resulted in crashes for me, resulting in the alarm (an mp3 file) not going off.
Just be warned in advance.
reijkelhof said:
I also suffer this problem, the alarm is unreliable.
I heard you can fix it by turning off sense and setting it in windows because these values would become out of sync, but have not tried.
Klaxon resulted in crashes for me, resulting in the alarm (an mp3 file) not going off.
Just be warned in advance.
Click to expand...
Click to collapse
There's another alarm bug thread here where it has been tested and confirmed that it's not a sense related issue. It's Windows.
It has been said that changing volume settings after setting your alarms has a big effect on whether the alarms will behave as expected, or go off at all.
Seems changing your volume after setting the alarms messes things up, and so does having pending appointments, as Windows will play your reminder right before the alarm goes off, messing things up too.
I'm gonna go ahead and post gAlarm v1.51 in a while,after my kids go to bed. If any mods/admin have a problem with it, I'll take it down. I think it should be ok, since that version is freeware
EDIT: Here ya go guys. Hope I'm not breaking any rules here.
You might need .netFW3.5 to install/run it.
So I have been using Timely for quite a while on my HTC One m7 and Nexus 5, but ever since I started using my Nexus 6P as my daily phone, I have noticed that the alarm is hit or miss. I tried the suggestions from here, but that does not seem to have made much of a difference. I have also tried going to the stock Clock app, it seems to be a bit better, but not by much.
What I have been noticing is that the alarm I have set for 5:30AM it will either go off or it will just not go off at all and I will get a notification that the alarm was missed at 5:30AM. If the alarm does go off, I usually hit snooze and just lay in bed until it goes off again checking email or something on my tablet (so the phone should still be locked). When I realize that I have been awake longer than 10 minutes, I look at my phone and there is a notification that the alarm for 5:30AM was missed... So it realized the alarm should have went off, but didn't.
I also have 2 later alarms (9:35AM and 10:20AM) and both of them are still in Timely and they work just fine, so maybe there is something with the deep sleep in Marshmallow?
I am running the stock image, updated to 6.0.1 via OTA, no root, no custom kernel, nothing that IMO should be affecting the operation of this type of stuff.
Just wondering if anybody else is having similar issues or if somebody can recommend an alarm app that is not suffering from this issue.
It seems that any alarm other than stock has issues. I see the post you referenced mentioned adding exceptions for those apps to prevent battery optimization. Did you try that with no luck? I don't know if there has been much luck other than just using the stock alarm if you really need to depend on it to wake up for work or other important events. I have never had stock alarm not go off, but I don't use any other apps.
fury683 said:
It seems that any alarm other than stock has issues. I see the post you referenced mentioned adding exceptions for those apps to prevent battery optimization. Did you try that with no luck? I don't know if there has been much luck other than just using the stock alarm if you really need to depend on it to wake up for work or other important events. I have never had stock alarm not go off, but I don't use any other apps.
Click to expand...
Click to collapse
I did try turning off optimizations for Timely, that did not seem to help much. The funny thing is that the stock alarm is also having similar issues, so either I am that heavy of a sleeper or maybe I just need to try flashing the factory image back to it, which, like I mentioned, I do not think I did anything to cause this type of issue, but it is an OS after all, so who knows what could anger it.
I did just tonight try setting the auto dismissal time to Never as well as maxing out the volume (it was down by about 10%), so maybe that will wake me up.
I'll see what happens tomorrow morning and will report my findings a little later. In the mean time, if anybody can think of something that I could try, it would be greatly appreciated, although a restore is not the end of the world, I would like it if I didn't have to spend the time restoring the apps and accounts and what not.
Does this apply to you?
gotzaDroid said:
Like Red said, you need to have an alarm set first. AND... Any automatic "do no disturb" settings like, "every day from xx : xx to xx : xx" will override the "do not disturb until next alarm". So if you have the phone automatically do not disturb until 8am every day, but you need to wake up at 6am and set the do not disturb to until next alarm before your usual rules kick in... at 6am, do not disturb will not automatically turn off with the alarm. It'll stay on until 8am. Just FYI.
Click to expand...
Click to collapse
Sent from my Nexus 5X using Tapatalk
I'm on 6.0.1 stock and I use Timely, have no issues at all...
For what it is worth, after I set it that the Stock Clock Alarm Never gets dismissed and made sure the alarm volume was set to 100%, it has been going off like... umm, clock work. I tried doing Timely last night and made sure I had another alarm setup just in case, I noticed the Stock Clock alarm went off on the other device, but my 6P with Timely, did not go off.
I'm just going to give up on Timely for now, maybe they will release an update and I will give that a shot, but for now, Stock it is.
The new doze mode will impact any alarms apps that are not updated for android M to use GCS etc. that's why your alarms are not firing.
For now you have to use the stock google alarm which correctly works with doze mode.
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.