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?
Related
Hi all,
So I manually updated to FW 12070 on my Lumia 800 yesterday (Telus in Canada). The battery life issue seems to be fixed, or at least much improved. I'm getting the annoying volume bug, including in games with music - it's completely messed up. Sounds in games are normal it seems, but the music is all over the place. Hard to describe.
Nonetheless, my question is about toasts. I can't remember if I was getting them before or not, but no matter where I am in the OS (start screen, messaging hub, etc) I get the 2 vibrates for a gmail message notification (and sound if it's turned on), but no toast notification. I can't honestly remember if I did/didn't get this before, but I was wondering if anyone else can chime in on this. Messaging toasts work fine. My live tiles all update just fine.
Thoughts?
Oliver
I've just received my Nexus 5 earlier today and, coming from my old Samsung Galaxy Nexus, I'm really loving it so far. However, I've noticed that, at random, my Nexus 5 will vibrate and the screen will wake, sometimes once, sometimes twice in a row. There are no notifications following the vibration and screen wake, and no real indication at all as to why this may be happening.
At first, it started with Hangouts vibrating and waking the screen four to five times after each new text message I would receive, until I finally unlocked the phone and opened the Hangouts app. I would get an SMS text, the phone would vibrate and the screen would wake. Then, just after the screen would go back off on its own, the device would vibrate and the screen would wake again. This was a recurring issue today, so I had assumed it was just a bug with the Hangouts app (which did not at all surprise me).
However, for the past several hours, I have not received any text messages or Hangouts messages at all, yet at random times my phone will vibrate and the screen will wake with no notifications or other indications as to why. Sometimes it will happen once, followed by a second occurrence of this behavior about a minute later. Other times, it will happen twice in succession. I was wondering if maybe it was Google Now, but I had disabled vibration on notifications for Google Now. I also considered Gmail, but notifications are turned off entirely for my Gmail app.
I'm at a loss here, and I'd really appreciate any insight into this issue. For those wondering if it might have something to do with the battery overheating and the system trying to notify me about it, the battery has been keeping below or around 80 degrees Fahrenheit for the vast majority of the day, so I doubt this is the case, though I'm open to any and all possibilities.
Other helpful information:
My Nexus 5 is running stock Android KitKat 4.4.2, purchased new directly from the Google Play store online.
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?