Related
Anyone experience this issue? It seems to be random. The only way I'm getting around this is to use a silent alarm ring tone. It seems to have occurred after I used the Alarm once. Since then the Alarm goes off even though the old one has long been deleted. I've tried deleting ALL alarms and clearing the cache to no avail.
stock or custom?whichever it is try this
cleared data??disable and re-enabled yet??try it or set 4 alarms at once with intervel of 1 sec after all has alarmed delete em all clear cach disable re-enable ....
EDIT:if you have root or custom rom kill the app and get a new one from play store
I'm on Chuppa Rom (latest build) and I seem to be having an issue with my notifications and my alarm.
My alarms: I have timely and Alarm Clock Xtreme on because I've had bad experiences with the stock alarm app in the past. Timely still rings the alarm but not at the time I set. Maybe a few minutes later after the time I've set it to. My Alarm Clock Xtreme doesn't even ring. I have the notification of the next alarm on my notification tray as do I have the widget on the home screen. Also, my WhatsApp notifications too come in late (sometimes by half an hour!!). My sync is turned on so I don't know what else I can do.
Please advise,
trippinz said:
I'm on Chuppa Rom (latest build) and I seem to be having an issue with my notifications and my alarm.
My alarms: I have timely and Alarm Clock Xtreme on because I've had bad experiences with the stock alarm app in the past. Timely still rings the alarm but not at the time I set. Maybe a few minutes later after the time I've set it to. My Alarm Clock Xtreme doesn't even ring. I have the notification of the next alarm on my notification tray as do I have the widget on the home screen. Also, my WhatsApp notifications too come in late (sometimes by half an hour!!). My sync is turned on so I don't know what else I can do.
Please advise,
Click to expand...
Click to collapse
Did your greenify those apps?
Also, the new "Quiet mode" seems to silence alarms as well so make sure it isn't turned on during your alarms or give them priority.
BWolf56 said:
Did your greenify those apps?
Also, the new "Quiet mode" seems to silence alarms as well so make sure it isn't turned on during your alarms or give them priority.
Click to expand...
Click to collapse
Greenify?
Yeah, I was quite 'alarmed' cool by that feature, lol. I've made sure it's always turned off.
trippinz said:
Greenify? [Edit: I googled the app. Thanks, I'll try it out. Update soon.]
Yeah, I was quite 'alarmed' cool by that feature, lol. I've made sure it's always turned off.
Click to expand...
Click to collapse
Greenify is amazing, just don't use it on alarms app as they might not 'wake' to wake you up
There's also a notification setting (for wakelocks) which you should go over, make sure those apps aren't turned off or limited.
BWolf56 said:
Greenify is amazing, just don't use it on alarms app as they might not 'wake' to wake you up
There's also a notification setting (for wakelocks) which you should go over, make sure those apps aren't turned off or limited.
Click to expand...
Click to collapse
I just realised that Greenify hibernates app and not keeps them 'awake, lol.
That won't fix the issue of it always forgetting to wake me up.
Any idea how to proceed?
trippinz said:
I just realised that Greenify hibernates app and not keeps them 'awake, lol.
That won't fix the issue of it always forgetting to wake me up.
Any idea how to proceed?
Click to expand...
Click to collapse
Greenify was more of a side note. I only mentioned it cause I did greenify my alarms before without thinking that it wouldn't go off.
But you should check your app notification settings (in your phone settings). It's a wakelock control that was added with Lollipop.
BWolf56 said:
Greenify was more of a side note. I only mentioned it cause I did greenify my alarms before without thinking that it wouldn't go off.
But you should check your app notification settings (in your phone settings). It's a wakelock control that was added with Lollipop.
Click to expand...
Click to collapse
I'm sorry, I seem to be a little lost. I tried looking for the wakelock control but to no avail :\
What does the wakelock control do? Does it keep apps awake (that I need to apply it to my alarm app)?
trippinz said:
I'm sorry, I seem to be a little lost. I tried looking for the wakelock control but to no avail :\
What does the wakelock control do? Does it keep apps awake (that I need to apply it to my alarm app)?
Click to expand...
Click to collapse
If you don't know what/were it is, chances are the it's not the issue. It is used to turn off wakelock notifications but by default, they should be activated. More details here
Do you have any app that help you phone's battery or 'speed boosters'?
Here, try this:
Settings, sound then notifications and clock, checked the priority option, then selected turned on priority sound profile.
did you find out what was causing it not to ring? Im always paranoid my alarm is going to fail lol
cntower said:
did you find out what was causing it not to ring? Im always paranoid my alarm is going to fail lol
Click to expand...
Click to collapse
Sorry for the late reply. I just noticed my notifications now. I don't tend to login too often.
My UI seems to be on sleep mode for some reason. As in, I'll unlock the phone wondering why no alarm went off and notice that the 3 different clocks I have on my homescreen as widgets all show the time from a few hours back and then after a couple of seconds refresh and show the correct time at which the alarm from 10 minutes ago now begins to ring. I still don't know what's causing this. All this time I've been using my old phone as my alarm. I'm thinking of moving onto another ROM. Maybe an AOSP one despite the bugs just because of this bug. If anyone has any ideas on how to fix this problem it would be much appreciated.
trippinz said:
Sorry for the late reply. I just noticed my notifications now. I don't tend to login too often.
My UI seems to be on sleep mode for some reason. As in, I'll unlock the phone wondering why no alarm went off and notice that the 3 different clocks I have on my homescreen as widgets all show the time from a few hours back and then after a couple of seconds refresh and show the correct time at which the alarm from 10 minutes ago now begins to ring. I still don't know what's causing this. All this time I've been using my old phone as my alarm. I'm thinking of moving onto another ROM. Maybe an AOSP one despite the bugs just because of this bug. If anyone has any ideas on how to fix this problem it would be much appreciated.
Click to expand...
Click to collapse
Did you greenify your alarm/clock app?
---------- Post added at 08:24 AM ---------- Previous post was at 08:21 AM ----------
trippinz said:
Sorry for the late reply. I just noticed my notifications now. I don't tend to login too often.
My UI seems to be on sleep mode for some reason. As in, I'll unlock the phone wondering why no alarm went off and notice that the 3 different clocks I have on my homescreen as widgets all show the time from a few hours back and then after a couple of seconds refresh and show the correct time at which the alarm from 10 minutes ago now begins to ring. I still don't know what's causing this. All this time I've been using my old phone as my alarm. I'm thinking of moving onto another ROM. Maybe an AOSP one despite the bugs just because of this bug. If anyone has any ideas on how to fix this problem it would be much appreciated.
Click to expand...
Click to collapse
Is your phone profile set to silent?
BWolf56 said:
Did you greenify your alarm/clock app?
---------- Post added at 08:24 AM ---------- Previous post was at 08:21 AM ----------
Is your phone profile set to silent?
Click to expand...
Click to collapse
No, and no. Sometimes it'll ring like usual. Other times it won't even ring. I suspect it's because the clock function sometimes tends to lag out and go unresponsive. You know how sometimes if you've got multiple windows open then later on you go back to one of them and everything has to be drawn up again as though it wasn't running at all in the background and that it was turned off for the time being? That's how my clock seems to operate. I can see that when I unlock my phone for a short moment the time is the time a few hours ago and it needs to resync for a second before it displays the correct time. Other times it's responsive and it tells the correct time and in those instances the alarm rings without issue. But every 3 or 4 times, it turns unresponsive on me and my alarm doesn't kick in.
trippinz said:
No, and no. Sometimes it'll ring like usual. Other times it won't even ring. I suspect it's because the clock function sometimes tends to lag out and go unresponsive. You know how sometimes if you've got multiple windows open then later on you go back to one of them and everything has to be drawn up again as though it wasn't running at all in the background and that it was turned off for the time being? That's how my clock seems to operate. I can see that when I unlock my phone for a short moment the time is the time a few hours ago and it needs to resync for a second before it displays the correct time. Other times it's responsive and it tells the correct time and in those instances the alarm rings without issue. But every 3 or 4 times, it turns unresponsive on me and my alarm doesn't kick in.
Click to expand...
Click to collapse
Do you have a App ops in your settings? Where you could give the clock app priority or whitelist it.
Otherwise, I remember reading about someone fixing that issue setting his alarms with the calendar app, not ideal but it's a workaround.
So, I already tried everything, I cannot get my alarm clock working properly no matter what app I am using, stock, Timely, 5 more apps, nothing is working. Only when I set alarm to next <2 hours but this is useless to me. I was looking for this problem on xda or 1+ forum, no solutions for my case.
- I tried changing volume for alarm - no difference
- disabled battery optimization for alarm clock apps + clock stock app - nothing
- factory reset to wipe all data and cache - nothing
- newest oos
- my phone isn't in silent mode
I think I know where is problem, when I unlock phone every morning I need to put PIN there ( I have fingerprint unlock as default) so my phone reboot every night.
Possible solutions:
Disable PIN after start so stock alarm can wake me up (because it has that function in application) - I tried disable PIN, not working (any ideas?)
Remove these random reboots - newest oos fixed this they said, but not in my case.
Don't get me wrong, I am happy with this phone, however in a few days I need to wake up exactly in right time.
Btw. I had exactly this problem on my old Sony Xperia U if it is worth mentioning. But on that phone that started maybe after 2 years, not in day 1 like in this case.
As you can see, My english is not my native language but I am trying to do my best
Do you have your phone shutting off at night by any chance and you have your security set to require PIN entry when device boots?
Or if your phone is randomly rebooting in the middle of the night and you have your security set to require a PIN entry when booting the device, this is most likely the reason why your alarm clock is not working. Lock screen PIN or fingerprint should make no difference.
No, I already disable it.
Today I perform some tests about this thing and I discovered this. When I enable setting in clock stock app for 1+3 "Wake if device is powered off" . It doesn't wake or ring when phone is off (with full battery of course). Anyone can check this if it is working for some people?
Anything else, I tried set alarm for next 5 minutes and reboot device. After phone is booted up, it require pin (lockscreen, so no pre-boot stage) BUT alarm is working! So from my side it looks like when doze mode is activated itself, it cause problems with alarm, even stock one.
///EDIT: Wake if power off is now working! I just enabled smartlock with my current location and now phone is turned on itself 2 minutes before alarm. I will test this correctly next morning (here is 21:13). I hope I can bypass doze mode this way.
Interesting...I took a little cat nap yesterday and set my alarm for 1 hour...when I woke up, I woke the phone (it was on) and the alarm sounded as soon as it woke, but at 1 hour and 23min (23min past when I set it). So possibility dose works too well? BTW I'm stock with 3.2.4 and function on with wake device for alarm.
It works! After not touching the phone for +-8 hours, phone wake up itself and start ringing in right time. So solution is:
-Using stock app,
-Enable "Wake if device is powered off"
- Turn off phone when you go to bed
This will bypass doze mode as I correctly predicted
But still, if doze mode is blocking stock alarm, it needs to be fixed soon as possible. For broken notifications too.
Have you tried Deskclock by Google ( Clock app ) on play store
Nope, I don't need to try any apps anymore. It is still working
It might be an idea to not optimize the clock app under the battery optimization settings. I have it as not optimized and it works fine for me
Sent from my ONEPLUS A3003 using Tapatalk
"- disabled battery optimization for alarm clock apps + clock stock app - nothing"
I already do that.
I have the same problem like viktorino. Stock alarm works while phone is not in doze mode, but once the mode starts the alarm does not produce any sound although it manages to turn the display on… Anyone has any more ideas? Don't want to turn my phone off every night.
My alarm does not work after latest updates it is not giving sound
Vinodcrasto said:
My alarm does not work after latest updates it is not giving sound
Click to expand...
Click to collapse
Same here.. did you come across with any fix?
Only solution for me was to use google clock.
Weird thing.. Everytime I open google clock apk, an alert message is shown telling that alarm is silenced by default.
I can't understand why the haven't solved this yet.. it seams a quite simple bug to fix..
hi, what I am thinking is that it's not a alarm app problem, rather a sound problem, my op3 sometimes looses sound and when I try to play something from any app, that app stops responding. only thing temporary working is a reboot.
I've used alarmdroid reliably for years on many different devices. Works consistently on op as well. Using OB13 currently
lautta10 said:
Same here.. did you come across with any fix?
Only solution for me was to use google clock.
Weird thing.. Everytime I open google clock apk, an alert message is shown telling that alarm is silenced by default.
I can't understand why the haven't solved this yet.. it seams a quite simple bug to fix..
Click to expand...
Click to collapse
Checkout my alarm app Alarm + Task Logger FREE.
Playstore Link https://play.google.com/store/apps/details?id=com.mobitronix.gauravchauhan.alarmplus.free
I have developed this app post Marshmallow update and have circumvented the problem of missfiring alarms due to doze mode.
Besides this it offers more features & customizable options than other apps of this genre. Check playstore description for available app features.
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
viktorino said:
So, I already tried everything, I cannot get my alarm clock working properly no matter what app I am using, stock, Timely, 5 more apps, nothing is working. Only when I set alarm to next <2 hours but this is useless to me. I was looking for this problem on xda or 1+ forum, no solutions for my case.
- I tried changing volume for alarm - no difference
- disabled battery optimization for alarm clock apps + clock stock app - nothing
- factory reset to wipe all data and cache - nothing
- newest oos
- my phone isn't in silent mode
I think I know where is problem, when I unlock phone every morning I need to put PIN there ( I have fingerprint unlock as default) so my phone reboot every night.
Possible solutions:
Disable PIN after start so stock alarm can wake me up (because it has that function in application) - I tried disable PIN, not working (any ideas?)
Remove these random reboots - newest oos fixed this they said, but not in my case.
Don't get me wrong, I am happy with this phone, however in a few days I need to wake up exactly in right time.
Btw. I had exactly this problem on my old Sony Xperia U if it is worth mentioning. But on that phone that started maybe after 2 years, not in day 1 like in this case.
As you can see, My english is not my native language but I am trying to do my best
Click to expand...
Click to collapse
Checkout my alarm app Alarm + Task Logger FREE.
Playstore link - https://play.google.com/store/apps/details?id=com.mobitronix.gauravchauhan.alarmplus.free
I have developed this app post Marshmallow update and have circumvented the problem of missfiring alarms due to doze mode.
Besides this it offers more features & customizable options than other apps of this genre. Check playstore description for available app features.
I don't believe that the stock alarm clock can be optimized, at least by doze. Do you have root or done any mods such as wakelock blockers?
Did cleaned up the whole device. Only then stock alarm started working.
Has anyone had it where your alarm hasn't gone off? I've tried several apps (including the main Google one), changed battery optimisation, uninstalled and reinstalled but sometimes it just doesn't work. It's not every time and most of the time it works normally. I'm on Pie, but it was the same on Oreo. Not faced this before with any other phone.
It's very frustrating as I use it frequently to keep awake during the night!
Turn off Adaptive Battery.
I have the exactly same issue since I've upgraded my device to Pie. Even turning off the Adaptive Battery doen't help. Is someone has a fix ?
Anyone else have this problem with their G7 ThinQ? Sometimes it works and sometimes it doesn't. I checked the alarm before going to sleep and it even said the alarm would go off in 8 hours and 7 minutes, but then it doesn't go off. The alarm worked perfectly for over a year and only recently stopped working intermittently. I've double checked the days, the time, AM/PM, that the alarm is enabled, DND, etc. Everything is set correctly.
Is there a way to fix this?
Try bforce stoping and erasing the data and cache of the app .
If you're using the google clock app try updating it