Database Develop

Disconnected...

OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?

I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?

Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app

skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty

I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?

shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.

I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification

disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...

Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.

I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.

[Q] My Nexus 6 is almost always awake. What to do?

My Nexus 6 is compeletely stock and untouched software. I have attached screenshots from Nexus 6 (5.0.1) and Note 3 (5.0) to show the point I'm talking about.
When I'm sleeping as you can see on the Note 3 it has very few awakes. But Nexus 6 on the other hand is almost always awake. It drains about 20-25% battery overnight.
I have performed factory reset 3 times and now it has almost no additional apps installed but still the same. (don't judge by the facebook on the screenshot it's just installed and the problem is the same with or without it) I'm not rooted so i can't use the wakelock detector. I've installed GSam and it shows Android OS and Android system as biggest drainers for the current situation (16%, 6%) which i suspect nothing extraordinary.
I have play services 6.7.76 on both devices if it has anything to do with it. I tried something like turning the ambient display off and some other settings to see if theyre waking it but no luck yet. Do you think it is a software thing and Google will eventually fix it and I should wait or what should i do?
I really want to keep this phone but the battery is a big concern for me right now. every morning seeing the battery down without touching the phone is a big problem. Any help and information on the subject is appreciated.
Edit: I have added a screenshot from safe mode. I restarted in safe mode to see if any 3rd party is the cause of the problem. But the problem persists. And I have noticed that when the wifi is compeletely off (Keep awake, Always scanning etc.) the problem is solved. But whenever i turn on the wifi, even when it is not connected to any network, it starts draining battery and keeping phone awake like on the graphics. Can anyone give me a hint if this can be a hardware related issue with the wifi receiver? Or it looks like a software issue and can be solved with the 5.1 update? I have 3 days to return the phone if its a hardware thing. Thanks

You should probably update to 5.1 and see if that helps.

biggiestuff said:
You should probably update to 5.1 and see if that helps.
Click to expand...
Click to collapse
Do you know if it is a common issue and 5.1 fixes it? I've checked the updates but nothing showed up so far. I'm close to 14 day window for my T-Mobile purchase so i need info on 5.1 about this issue and i didn't see anything related :/

HKNRN said:
Do you know if it is a common issue and 5.1 fixes it? I've checked the updates but nothing showed up so far. I'm close to 14 day window for my T-Mobile purchase so i need info on 5.1 about this issue and i didn't see anything related :/
Click to expand...
Click to collapse
You might have the sensor ind bug that was in 5.01 that kept the phone from sleeping properly. From my short experience with 5.1, it's gone. Hard to tell about your situation without screenshots from better battery stats and the app list.

biggiestuff said:
You might have the sensor ind bug that was in 5.01 that kept the phone from sleeping properly. From my short experience with 5.1, it's gone. Hard to tell about your situation without screenshots from better battery stats and the app list.
Click to expand...
Click to collapse
Thank you for the info. Root is not an option on the Nexus 6 cause my sister will be using it and she's not a techie. Without root I can't properly see what keeps it awake :/ As i said, besides the screen, biggest consumers are the Android OS and Android system in Battery settings list. But they're similiar on the Note 3 too so i dont think i can get somewhere with them.
I guess i will have to wait for 5.1 and hope it is fixed as you've said. Do you know what sensor is causing the sensor ind error? Does it have anything with the Ambient display?

HKNRN said:
My Nexus 6 is compeletely stock and untouched software. I have attached screenshots from Nexus 6 (5.0.1) and Note 3 (5.0) to show the point I'm talking about.
When I'm sleeping as you can see on the Note 3 it has very few awakes. But Nexus 6 on the other hand is almost always awake. It drains about 20-25% battery overnight.
I have performed factory reset 3 times and now it has almost no additional apps installed but still the same. (don't judge by the facebook on the screenshot it's just installed and the problem is the same with or without it) I'm not rooted so i can't use the wakelock detector. I've installed GSam and it shows Android OS and Android system as biggest drainers for the current situation (16%, 6%) which i suspect nothing extraordinary.
I have play services 6.7.76 on both devices if it has anything to do with it. I tried something like turning the ambient display off and some other settings to see if theyre waking it but no luck yet. Do you think it is a software thing and Google will eventually fix it and I should wait or what should i do?
I really want to keep this phone but the battery is a big concern for me right now. every morning seeing the battery down without touching the phone is a big problem. Any help and information on the subject is appreciated.
Click to expand...
Click to collapse
Do you use Microsoft Exchange services?
I mean, did you setup other e-mail accounts. Like- Outlook, hotmail .etc??
Because last time I found, that service kept my phone to always wake up..

Masum56k said:
Do you use Microsoft Exchange services?
I mean, did you setup other e-mail accounts. Like- Outlook, hotmail .etc??
Because last time I found, that service kept my phone to always wake up..
Click to expand...
Click to collapse
Oh yeah it has a hotmail account set up besides gmail. I will remove the hotmail account and restart the phone at night and observe in the morning again. Thanks for the suggestion!
If it is the problem, how did you overcome the issue? Are you using browser for your exchange mail account? If so, it will be a pain not getting mails to the app :/

Made some edits on the original post. If it helps..

WiFi keeps turning on and off on its own

I don't know what might have happened, but this morning, I tried to connect my Phone to WiFi, and for some reason, it wouldn't. The WiFi toggle button that you see when you pull down the Notification Bar, now that WiFi button keeps turning on and off constantly. The time it takes between each toggle (on to off or off to on) is just about 0.5 - 1 sec. This is crazy. I can't connect to my WiFi.
I googled for solutions, no luck. I hard reset my Phone, no luck still. I wiped Partition Cache too. I entered into the Safe Mode, the same behavior happened. It's weird. It's like my Phone is possessed or something. A virus maybe?
Any input would be much appreciated. My phone is running the latest Firmware from T-mobile. And I got the update maybe 1-2 weeks ago and it had been working fine until this morning the issue started.

My phone just started doing this as well. Wifi keeps turning off and on. If I want to keep it off I have to restart my phone. If I want to use the wifi I have to manually toggle it from the wifi settings. Just weird it started doing this just recently. Maybe an app we both have installed?

I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.

febzz88 said:
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
Click to expand...
Click to collapse
Haha I was about to post this solution as well! Turning off the wifi in location accuracy fixed it. You're right about probably some Google app is causing this as this hadn't happened before yesterday. Sorry you had to format your phone to find this out...hopefully google or samsung can fix this from their end.

Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?

muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
I just uninstalled wear and same issue persist. Last app from Google that I did an update on was Google home...formally known as chromecast.
---------- Post added at 10:30 AM ---------- Previous post was at 10:04 AM ----------
I just uninstalled Google home and the issue went away.

I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.

febzz88 said:
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
Click to expand...
Click to collapse
Yup that was me leaving a comment haha

i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!

androidschmandroid said:
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
Click to expand...
Click to collapse
Do you have Google Home installed? After I uninstalled that the wifi issue stopped

alanmv567 said:
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
Click to expand...
Click to collapse
no, i do not.

muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.

Go to location>improve location>unchecked wifi scanning. It just worked for me

Uninstalling android wear seems to have worked for me.

febzz88 said:
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Click to expand...
Click to collapse
Definitely not the compass, been through the calibration process. Attempted many fixes including special GPS settings and utilities. At times the phone can sit there with screen on for over 10 minutes without acquiring a single satellite. I'm thinking hardware issue, possibly contacts for the antenna. In any case, not relevant to this thread...

I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.

DirtySant0 said:
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
Click to expand...
Click to collapse
I had tried this prior to reformatting my phone and it didn't help. I then wiped the cache again and reformatted the phone; in fact I reformatted and cleared cache 3x because the issue kept coming back after I reinstalled apps again. This is weird, the situation and resolution vary a lot from one user to another. Then I simply turned off WiFi Scanning under Improve Accuracy in Location, and the issue went away.

WHEW! Uninstalling Wear and Home did it for me. For now, anyway. I "fixed" it this morning by toggling Ultra Power Saver on and off, and it worked all day until I came home from work. Then nothing helped until I found this thread. Changing GPS settings didn't do it for me, but I'm still on Lollipop so my location settings are a little different.
Thank you, Febzz and Alan!

Google home was the issue!!
Sent from my SM-N910T using Tapatalk

Changes in router's Wireless Security had caused it in my case
This is old thread but still I am posting this solution as it could be useful tip for someone in future.
I had this issue and was causing me real headache. I initially thought it was hardware failure of my phone but later I found reason is something else.
For some reason I had changed Wireless Security of my WiFi router from WPA2 Personal to something else (I guess WEP).
That was causing my phone (intex cloud 4g) often to turn on and off WiFi on its own. I changed the Wireless Security back to WPA2 Personal and phone is now back to normal (not turning WiFi on and off on its own)

[FIX available] Bottom part of the touchscreen stops working

Solution:
Go to Settings (if you're stuck in an app, use the button in your notification panel)
Go to 'System' (try tapping above the broken screen area)
Go to 'About this phone'
That should be all that has to be done! Do note: this fix isn't permanent. Let's hope Nokia fixes this.
Old thread:
Hello all!
When i woke up today and unlocked my phone (while an app is open) the bottom part (starting just above the nav-buttons) of my touchscreen just stops working.
I've had this problem a couple times (at most once per day) since updating from Oreo.
The solution to this problem seems to just to reboot the phone.. (This won't fix it permanently, sadly)
I'm asking if anyone else has this same problem, because i don't know the source of this problem.. (Maybe its because of the app not being P compatible?)
Thanks!

Hi, I have the same problem after the last update (september). Android Pie beta. Almost every morning i have to restart ..
Before the update was enough to just torn off/on the screen .

i don't have this problem on TA-1046 with Pie DP2-DP4.1 or Pie stable... maybe some incompatible apps? you use some for changing NavBar/Gesture area?
although i use XDA NavigationGesture what replace NavBar/Gesture with own, still not having problem, maybe you can try too this replacement, have many more function/settings that stock Pie gesture

for u its bottom touch screen is not working , but for me top of my touch screen isnt working .. and iam facing some serious problems after updating to pie . my phone restarts all of a sudden while charging , app crashes and more , hope hmd fixes this kind of issues in upcoming oct security patch update .

k3dar7 said:
i don't have this problem on TA-1046 with Pie DP2-DP4.1 or Pie stable... maybe some incompatible apps? you use some for changing NavBar/Gesture area?
although i use XDA NavigationGesture what replace NavBar/Gesture with own, still not having problem, maybe you can try too this replacement, have many more function/settings that stock Pie gesture
Click to expand...
Click to collapse
The app i left open last when it happened was "Boost For Reddit"
I'm using the old navbar layout (so no swipe)
dexterboon said:
for u its bottom touch screen is not working , but for me top of my touch screen isnt working .. and iam facing some serious problems after updating to pie . my phone restarts all of a sudden while charging , app crashes and more , hope hmd fixes this kind of issues in upcoming oct security patch update .
Click to expand...
Click to collapse
That's soo weird! I really hope HMD will release a patch soon.. I don't want to downgrade back to oreo

Issue with charging
I am having a charging issue. My phone usb and adapter is working fine with other phones. But when I connect my Nokia 7 Plus below 50%,My phone shows charging And when I tap the screen it doesn't charge. It occurs couple of time. And then It becomes normal and shows rapid charge after 55%. My charging port is fine when I connect it with my Pc usb port. some how the rapid charge doesn't respond. Does anyone have this problem?

Rahul Deshmukh21 said:
I am having a charging issue. [...]
Click to expand...
Click to collapse
What is real time for charge? Rapidcharging is disabled while you activated LCD

Yeah I'm facing similar issues, or did... I'm not sure... but it's been a non-issue for the past ~36 hours now. Here's to hoping it's not an issue any longer. I speculated it might be adaptive battery related somehow, so I tried rebooting my phone just before going to bed Sunday night, but my navbar still worked Monday morning, and this Tuesday it's still working in fact. I did this to test if it stopped working based on time since last reboot, or because some background process being killed due to adaptive battery/doze putting the phone to sleep. But based on my recent experience I think my hypothesis can be rejected. And I'm still not sure what caused it.

STcraft said:
Hello all!
When i woke up today and unlocked my phone (while an app is open) the bottom part (starting just above the nav-buttons) of my touchscreen just stops working.
I've had this problem a couple times (at most once per day) since updating from Oreo.
The solution to this problem seems to just to reboot the phone.. (This won't fix it permanently, sadly)
I'm asking if anyone else has this same problem, because i don't know the source of this problem.. (Maybe its because of the app not being P compatible?)
Thanks!
Click to expand...
Click to collapse
Same for me ta-1046, happened to me twice now. bottom part of screen stops reacting to touch. reboot fixes it.

Hmm... After playing around in the settings while having this problem active, for some reason, going to the phone info section just fixed it... I'm not sure if going there actually did that. needs more testing, I suppose.

+1 I use navigation gestures

STcraft said:
Hmm... After playing around in the settings while having this problem active, for some reason, going to the phone info section just fixed it... I'm not sure if going there actually did that. needs more testing, I suppose.
Click to expand...
Click to collapse
Huh, I'll be damned. When my nav bar was frozen this morning I went into the "about phone" section in the menu, and, lo and behold, my nav bar sprang back to life instantly. Now it might still just be a coincident of course, but it's certainly interesting, and could potentially be a fix where you don't have to reboot.

​
silverphoenix87 said:
Huh, I'll be damned. When my nav bar was frozen this morning I went into the "about phone" section in the menu, and, lo and behold, my nav bar sprang back to life instantly. Now it might still just be a coincident of course, but it's certainly interesting, and could potentially be a fix where you don't have to reboot.
Click to expand...
Click to collapse
surprised me as well that it worked. He could be a good beta tester. lol

Capture of
I managed to capture a video of the bounds of the touch-registration when the bottom 1,5 centimeter of the screen stops registering.
https://imgur.com/xrRB906

Same problem for me after upgrading a couple of days ago. Bottom of the screen (navbar and a bit more) is not accessible. Always happens after a night charging.
Going to the "About phone" menu fixes it. Thanks!
I have seen reports of people with other phones saying this is due to the setup wizard being active and preventing using the navigation bar. Tried some suggested adb commands without success. I will still try to disable the setup wizard app and report back.

IT ACTUALLY WORKS!!
AssKiRK said:
​
surprised me as well that it worked. He could be a good beta tester. lol
Click to expand...
Click to collapse
oh thank you! XD

Updated the OP

Please put a comment here as well: https://community.phones.nokia.com/support/discussions/topics/7000036457?page=1
This might help getting a quicker fix from Nokia.

Looks like the recent October patch still has this issue.
Would be nice if i can get a logcat this issue, but given this issue gets triggered after hours of inactivity, it would take a looong time to sift through the log.
Maybe there's a way to trigger it without waiting?
I can try logging when i do the "about phone" fix, will come back to this.

same isue here.. after chsrging at night nav bar bottom inch not responsive.. will try the phone info thing in the morning... is this software related ? will there be a patch??

Notifications Issue

Is anyone having issues with their notifications not coming through, or coming in super late, or having the same notifications coming up over and over? I'm expecting all three problems, it seems to be happening with every app for me except for calls and text. I factory reset the phone but that didn't fix the issue. If I restart the phone, then all my notifications that haven't physically gone into the app to check start pouring in. No idea what could be causing the issue and it's really starting to piss me off. I have already sent my phone in for repair cause my LTE data stopped working for no reason. I don't think both issues are related as I do have LTE data after they replaced some part.
Would appreciate if anyone has any ideas.
Thanks.

The Stig 04 said:
Is anyone having issues with their notifications not coming through, or coming in super late, or having the same notifications coming up over and over? I'm expecting all three problems, it seems to be happening with every app for me except for calls and text. I factory reset the phone but that didn't fix the issue. If I restart the phone, then all my notifications that haven't physically gone into the app to check start pouring in. No idea what could be causing the issue and it's really starting to piss me off. I have already sent my phone in for repair cause my LTE data stopped working for no reason. I don't think both issues are related as I do have LTE data after they replaced some part.
Would appreciate if anyone has any ideas.
Thanks.
Click to expand...
Click to collapse
I had notification delays with gmail app, fixed it by turning off battery optimization for this specific app.

The Stig 04 said:
Is anyone having issues with their notifications not coming through, or coming in super late, or having the same notifications coming up over and over? I'm expecting all three problems, it seems to be happening with every app for me except for calls and text. I factory reset the phone but that didn't fix the issue. If I restart the phone, then all my notifications that haven't physically gone into the app to check start pouring in. No idea what could be causing the issue and it's really starting to piss me off. I have already sent my phone in for repair cause my LTE data stopped working for no reason. I don't think both issues are related as I do have LTE data after they replaced some part.
Would appreciate if anyone has any ideas.
Thanks.
Click to expand...
Click to collapse
Some people may have battery saver on and this may cause late notifications. Also check in settings "auto sync", under accounts. I did have some late notifications issue with Gmail app and do know battery optimization usually is the cause, but it went away in couple of days after I bought the phone.

Thank you for the suggestions. I ended up turning on high performance mode. Let's see if that helps.

The Stig 04 said:
Thank you for the suggestions. I ended up turning on high performance mode. Let's see if that helps.
Click to expand...
Click to collapse
How'd this work out for you? This phone is horrible for notifications for me. It constantly doesn't send them until I actually pick up my phone, then suddenly I'll get 5-10 notifications at once. I've turned off EVERY bit of power saving that I can find. I only run in high performance mode 24/7 with all adaptive battery, power optimization, auto app sleep, etc turned completely off. I've also tried disabling all power saving and sleep in the specific app pages as well. I need to be more observant, but I think this is mostly with push notifications (ex, my 2FA app for work) rather than apps with timers to check for updates occasionally. I also have an issue with my wifi disconnecting while the screen is off sometimes which is highly annoying since my home presence detection is based on my phone being on the wifi, though last time it started doing that a reboot fixed it.
Unfortunately, a search proves that this is a widespread issue. At this point I've pretty much given up on this phone and am looking to replace it as soon as I find a suitable alternative. I'm just curious if it's a Samsung issue or a Pie issue that will occur on other phones as well.

The Stig 04 said:
Is anyone having issues with their notifications not coming through, or coming in super late, or having the same notifications coming up over and over? I'm expecting all three problems, it seems to be happening with every app for me except for calls and text. I factory reset the phone but that didn't fix the issue. If I restart the phone, then all my notifications that haven't physically gone into the app to check start pouring in. No idea what could be causing the issue and it's really starting to piss me off. I have already sent my phone in for repair cause my LTE data stopped working for no reason. I don't think both issues are related as I do have LTE data after they replaced some part.
Would appreciate if anyone has any ideas.
Thanks.
Click to expand...
Click to collapse
Seems to be a general issue with android. Mine have gotten better recently. In addition to turning off battery optimization for any apps I want notifications for, i have done the following:
1. Wiped cache (under settings/app/storage), then rebooted into recovery mode and wiped the cache partition.
2. Gone into the setting and made sure apps I want notifications for are allowed to run in the background (settings/apps/select app for notifications/battery).
3. Allowed to run in background when on mobile networks (settings/apps/select app/mobile data/Allow Background Data Usage.
4. Gone into messages/settings/more settings/push message/changed toggle from "Prompt" to "Always".
Hope that helps.

David Dee said:
Seems to be a general issue with android. Mine have gotten better recently. In addition to turning off battery optimization for any apps I want notifications for, i have done the following:
1. Wiped cache (under settings/app/storage), then rebooted into recovery mode and wiped the cache partition.
2. Gone into the setting and made sure apps I want notifications for are allowed to run in the background (settings/apps/select app for notifications/battery).
3. Allowed to run in background when on mobile networks (settings/apps/select app/mobile data/Allow Background Data Usage.
4. Gone into messages/settings/more settings/push message/changed toggle from "Prompt" to "Always".
Hope that helps.
Click to expand...
Click to collapse
Thanks, I'll give some of those a try. I also got a VZW update with the May security patch among other things right after I posted that, so we'll see if that helps at all also.

AJerman said:
Thanks, I'll give some of those a try. I also got a VZW update with the May security patch among other things right after I posted that, so we'll see if that helps at all also.
Click to expand...
Click to collapse
It's gotten better for me. I enabled high performance mode but I had to keep going in and checking it a couple days after still even though it was enabled. Been a couple weeks now and the notifications I was missing before all seems to be coming in fine now. Time will tell though I guess lol
Are you also having trouble with apps updating? That was another problem I was having where I'd see apps needing to update, I'd start "update all" one app would download and then get stuck at 99% and it would just stay like that for about 40mins and prevent the other apps from updating. Then finally when it would finish the next one would do the same. It would literally take hours upon hours for 12 apps to update when it should only take a couple mins. That issue seems to be fixed for me now too.