I've been having this issue a lot lately. When I unlock my phone there will be a missed event for an alarm for that exact time when I first woke up the phone that day. It's nothing major, but I have to clear the missed event every time. It usually happens the first time I check the phone in the morning. I haven't seen it happen any other time of the day, which is just weird...
For example: I turn the phone on at 9:38AM. S2U2 will show a missed event for an alarm showing the time 9:38AM. It will also show in the notification box a missed alarm until I clear it. Doesn't matter what time I wake it up, theres usually a missed alarm for whatever time I woke up the phone that day.
Phone: Sprint Touch Pro CDMA
Rom: Newest Energy Rom
No alarm apps installed. Pretty clean install
It seems to persist between rom flashes too. I'm pretty sure it was doing this when running Jucys roms as well. Any ideas?
Related
I've had a problem with my XDA Exec since last Friday. I use it as my alarm clock on a morning normally - the 3 alarms are better than a snooze button cos it eases me in gently by reducing the snooze time each time. But on Friday I was late for work when it didn't go off at all. When I woke up and switched it on, all 3 notifications came through at once. Same has happened yesterday and today (though luckily I was already awake both times).
I did a reset over the weekend, and I know its not a sound issue as it just doesn't go off until you switch it on and they all come through at once. If I receive a text or phone call that wakes the phone up so I know its not that either.
Any thoughts/ideas?
alarm problem
hey buddy even i m facing same problem, it oesnt goes off, i mean even if we uncheck it in notification it doesnt goes off, even after soft reset it doesnt...whats the problem
After a few days it decided to rectify itself. Still no idea what exactly when wrong, but its working now at least.
Sounds like a silly title, but it's the first thing that came to mind.
Hi! I've had my Gear S2 Sport for a couple of months now, paired to a Galaxy S7 Edge. Everything has been working fine, except the alarms from time to time. I usually set an alarm directly on my watch to go off at 7:45 am. Now this would work fine for a few weeks, and then I noticed the alarm wasn't going off anymore - the watch's screen would light up and it would vibrate once, very shortly, at 7:45. Now since it's such a short vibration, it's very easy to miss, especially if I'm walking or something, so you can see why this would be a problem.
I checked my settings, the vibration options are all just fine and everything seems in place. I deleted the alarm and created it again, but it was still just giving me the one short nudge instead of going off entirely, the screen doesn't even show the dismiss/snooze dialog. So I deleted the alarm and set another one for 7:50 am. This one worked fine for a while, but I noticed that the watch was still lighting up and giving me one vibration at 7:45, even though that alarm doesn't exist anymore... And a couple of weeks later, the 7:50 alarm went away as well, leaving behind just a nudge at that time (even though I've since deleted it.)
So yeah, now I'm stuck with two "phantom" alarms at 7:45 and 7:50, with a new alarm shortly after that JUST stopped working this week... I'm about to just reset it to factory settings, but wanted to know if anyone else has any similar issues.
Sorry for the length of the post, I'd appreciate any suggestions!
Wow I can't believe I have spent so much time on this simple issue which even old phones were able to do flawlessly.
Brand new Nokia 2.1 running oreo go 8.1. Alarms would suddenly disappear from the lock screen or the top notification bar and then won't go off on the time specified.
Apparently a lot of people are facing this issue as it turns out by google search and I have tried the latest version of the google clock and another 3rd party alarm clock and it happens to both. Contacted support and they ask to clear cache and do things like a soft reset neither of which work at all.
I'm lost for solution as I can't get my alarms to keep running in the background until I open my clock app every now and then again and reset the alarm.
It happens to any other app that can run in the background 'auto silence scheduler' app the notification disappears and the app fails to start the scheduled silent time.
Seems like oreo is force closing apps that are running in the background when the phone is put to sleep for a while. Then those apps wont start until they are manually started.
Alarms is the worst because if it will happen during the night and I won't wake up at the time in the morning.
Exact same issue with my Nokia 2.1, Alarm's are a hit or miss scenario these days.
After April update I bumped several times into new strange behavior of Clock app in Alarm section - it shows blank screen and it stops creating new alarms until reboot. I tried to switch between screens of the App, shot it down and relaunched, but with no luck. It happens not every time, but at least a couple times. At least twice after a message that Stand App stopped work. I put my P3 at stand and when I needed to set alarm, it did two things in different order - showed blank Alarm screen and a message that Stand App stopped working. Can not say for sure it's connected. I don't use Assistant for setting alarms after it sets alarm for the next day. Luckily I woke up myself and decided not to take risks with artificial intelligence - look like it tries to be too smart for such a simple task, so not sure if the same problem can arise with Assistant.
Just wondering if anybody's got similar problem and fixed it?
The notifications are generally not showing on the lock screen and only appear when the phone is unlocked. The alarm exhibits similar behavior and does not always go off in the morning and only after unlocking the phone and am I told that I have missed an alarm.
I got the phone last week and did not initially have this problem, but it is becoming quite frustrating in recent days. The notifications sometimes work and the behavior is not consistent, despite playing around with notification and sound settings.
Does anyone else have this problem or is aware of a fix for it?