Related
After updating to FRF91, I notice two things.
1) My phone froze at least 3 times since the update when I tried to make a phone call. I had to remove the battery and restart it.
2) My calls are now less clear even with my blue-tooth. When I call someone, they and I will hear static. Sometimes the static is really bad. (no, I am not holding it the wrong way )
Anyone have similar issues?
My Nexus One is NOT rooted.
stock 2.1 to FRF50(manual install)->FRF83(manual install)->FRF91(OTA install)
No issues here. Clean install.
I would agree it seems buggy to me also; it could be the manual update path of updating, but im def getting some wonkyness.
When im on edge at my house, it always seems like WIFI is on demand and not connected (This differs from what my phone used to do and i also have wifi to never sleep); so when i try to access something intially i get a network error then the Wifi connects; then i connect even though im on edge which used to connect albeit slow.
A slight jerkiness when I longpress to remove widgets; don't remember that one previously.
Very erratic battery life; seems to be due to network switching from 3g to edge to wifi; can't really confirm that though; not real rogue apps on my device that are running, but who knows.
Car dock has been giving some force close issues from time to time which didn't really occur previously.
FRF83 more stable
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Falen said:
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Click to expand...
Click to collapse
let me know how that works out; I may do the same. Maybe go back and ota update.
I applied the full FRF85B when I did mine, and wiped cache / format user data from the boot loader. That cleared up issues.
gmail stopped working properly for me.
I have had some issues with my phone freezing up too but my trackball would still flash when i got alerts. I think it might be related to trackball alert because now that I have uninstalled it i haven't gotten any freezes.
I did the factory reset and I no longer have any problems. I am still waiting to see if my dialing still freezes randomly though.
Sent from my Nexus One using XDA App
I'm still on frf83 and found that flashing the frf91 gapps has somewhat reduced the freezes/reboots.
My XDA app freezes for a couple of seconds before it responds. Is this app up to date for frf91?
Sent from my Nexus One using XDA App
1. Going into Gmail it takes forever to display emails (usually shows the "loading icon" for 10-20 seconds) as if it is only then connecting to the server and downloading new/old emails.
2. Caller ID still does not keep settings when rebooting.
3. Task Managers don't actually seem to kill tasks anymore. Have tried multiple with settings to auto-kill 10 minutes after the screen goes off ... 5 hours later the programs are still running. Obviously just KILLS battery life.
nexusdue said:
Obviously just KILLS battery life.
Click to expand...
Click to collapse
Yeah, obviously, you're using auto-kill, it probably tries over and over and over when they don't actually close.
Stop using auto-kill. Even if it worked you will get less battery life by killing tasks. Read up about it. Only reason to EVER kill something is if it isn't acting nicely and has a bug that keeps using CPU or keeps the phone awake.
Factory Reset works almost all the time
If you got problems after update you should allways wipe (factory reset)
Sometimes I'm in areas where I don't get the best reception (i.e. some lecture halls during school hours) and I choose to put my phone in airplane mode so as to conserve battery when the class is over. However I find after trying to come out of Airplane Mode my Revo always reboots. As far as I can remember this issue has also happened in Decrapped 1.0. The same thing happens when I turn on GPS and choose to go to Google Navigation I get rebooted. After the reboot occurs I can turn on the gps/airplane mode etc without any problems. But does this issue happen to anyone else or is it perhaps just my phone? Thanks!!
I find that my revo does the same thing with google nav beta, it will sometimes hang and reboot too. I am running stock rom with a root. When I rotate phone the landscape view is sometimes corrupted with tiny blocks instead of the maps drawn correctly. I have to exit nav app and reload
I've had the same thing happen with airplane mode. I don't really use it often so I figure I can live with it.
Same here. The Revo doesn't seem to like hardware mode changes at times. I get reboots when switching into Bluetooth occasionally.
[I'm Revolting -- are you? Beamed directly into your brain by Revolt 1.3]
I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!
Cryofalcon said:
I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm only adding this due to the fact that I was constantly having issues when tethering with the Verizon 4g Hot Spot app. When running it, I found myself needing to reboot because the data connection would get lost and sometimes go into 3g, causing all sorts of headaches with doing things on my computer, such as redesigning websites, including my own.
What I found, though, related to this post, is using the airplane mode to kill the data connection and restart it, was getting me 4g and a few minutes to a few hours of Internet again until the next glitch.
Overall, modded, ota updated, downgraded, whatever, using that method never rebooted my phone. My thoughts are that it's possible some app might be causing that. I don't use Nav anymore, except as a last resort because it is so buggy, it would cause my phone to crash over and over, and rebooting. So, as for LG or Verizon coming up with a fix for this issue, I don't know if they would see it as one because it's not something everyone is experiencing and with as much as I use(d) that method, it never once happened to me. Please don't take that wrongly, just wanted to point out that it might be a certain app and allow those having this issue to seek another solution, maybe comparing apps installed to see a common denominator.
And, because I see a lot of posts relating to tethering issues with Internet freezing or dropping out, I found, on my LINUX machine (so far), that setting the MTU to 1300 seems to have solved that issue. I know this last part isn't directly related to the original post, but is the reason I kept using the airplane mode method and thought this added information might help someone doing what I was...
-Cybie
Sorry for the bump, but as of flashing Revolt 1.5, the issue in my original post seems to have been corrected as I was able to go from airplane mode to google nav multiple times and didn't reboot at all. so whatever the issue was seems to have been corrected. Thanks MT!!
I had 2 VZW Moto Xs and they rocked. About 10 days ago I switched to TMO Moto Xs and the GPS loses lock on both of them. Much like the first set, they get lock very quickly, but both the TMO units acted strangely during nav and when I installed GPS Status I see that the GPS gets lock, the coordinates are displayed, then about 10 sec later it searches for lock again, the coordinates aren't returned, and then it relocks.
This causes a real usability issue when it comes to navigation. If it was one of these I'd think I had a dud, but the VZW units worked fine and the TMO units both have this bug.
Has anyone seen similar issues?
Sent from my XT1053 using xda app-developers app
I use gps daily and i've only come across an issue with it 2x when i went to New York City. basically, it was putting my location all over the map, as if it couldnt find me. Im guessing the high rise buildings had something to do with it.
as far as gps losing lock, I have notice that as well. I never toggle it off and yet I have to turn it maybe once/twice a month
The lock problem I have is pretty continuous, and restarting doesn't seem to help. Wondering I'd there was a bad run somehow.
Sent from my XT1053 using xda app-developers app
I also encountered this issue.
I reset the phone and it went back normal; however, it occasionally still acts weird. I'm on tmobile as well.
Hope someone can figure this out
Sent from my XT1053 using xda app-developers app
For those of you seeing this issue, when it pops up, go into settings > location and see if you see LocationServices listed twice... One with a size of 120k, and the other 136k.
Solutions Etcetera said:
For those of you seeing this issue, when it pops up, go into settings > location and see if you see LocationServices listed twice... One with a size of 120k, and the other 136k.
Click to expand...
Click to collapse
As a matter of fact I do see this. Any idea what might be going on?
Sent from my XT1053 using xda app-developers app
Not yet... but it seems out of place.
My history with GPS "not quite working" was about it being extremely hit and miss about detecting me driving. When this would happen, I'd notice problems with Maps as well.
After a factory reset, it all worked fine. But as soon as I reinstalled Yelp, the issue returned. I'm not certain that yelp is the culprit as in hindsight, I really didn't confirm proper operation after the reset for a long enough period of time given the intermittent nature of the problem.
Next step is to try and determine if two of these same processes is normal, and if not, which one doesn't belong, and where it's coming from. There is a thread in the Moto forums I started. One person there who sees only one occurrence of the process stated his is 120k in size. One of my posts also has a list of all my third party apps that use location services. It would be helpful to know which apps are in common with folks having this issue. The thread is at:
https://forums.motorola.com/posts/8a2bf78f04?page=1
monorailmedic said:
I had 2 VZW Moto Xs and they rocked. About 10 days ago I switched to TMO Moto Xs and the GPS loses lock on both of them. Much like the first set, they get lock very quickly, but both the TMO units acted strangely during nav and when I installed GPS Status I see that the GPS gets lock, the coordinates are displayed, then about 10 sec later it searches for lock again, the coordinates aren't returned, and then it relocks.
This causes a real usability issue when it comes to navigation. If it was one of these I'd think I had a dud, but the VZW units worked fine and the TMO units both have this bug.
Has anyone seen similar issues?
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
So you are saying this can be software issue? I have a T-Mobile Moto X and I use the phone mostly for Navigation and this is driving me crazy. I am thinking that my phone is defective and been on the phone for 30+ min trying to get support.
I have the same issue
Sent from my XT1053 using Tapatalk
Solutions Etcetera said:
Not yet... but it seems out of place.
My history with GPS "not quite working" was about it being extremely hit and miss about detecting me driving. When this would happen, I'd notice problems with Maps as well.
After a factory reset, it all worked fine. But as soon as I reinstalled Yelp, the issue returned. I'm not certain that yelp is the culprit as in hindsight, I really didn't confirm proper operation after the reset for a long enough period of time given the intermittent nature of the problem.
Next step is to try and determine if two of these same processes is normal, and if not, which one doesn't belong, and where it's coming from. There is a thread in the Moto forums I started. One person there who sees only one occurrence of the process stated his is 120k in size. One of my posts also has a list of all my third party apps that use location services. It would be helpful to know which apps are in common with folks having this issue. The thread is at:
https://forums.motorola.com/posts/8a2bf78f04?page=1
Click to expand...
Click to collapse
I went ahead and posted my situation to https://forums.motorola.com/posts/8a2bf78f04?commentId=755612#755612. There are no apps in common with all three devices (yours, mine, my wife's). The quest continues.
I must add that I also had this problem on my previous phones, Note 2 and Galaxy Mega 6.3. The problem started around the past summer.
Sent from my XT1053 using Tapatalk 2
I confirm that I force stop the 120 k location service file, and the problem is gone. Need to do that again after a reset though.
Sent from my XT1053 using Tapatalk 2
x2h said:
I confirm that I force stop the 120 k location service file, and the problem is gone. Need to do that again after a reset though.
Click to expand...
Click to collapse
When you say 'reset', do you mean reset or just rebooting your phone?
BTW, I have no LocationServices on my Nexus 4, so these seem to be Moto's binaries, which makes sense.
Would appreciate you keeping us posted if this continues to address the issue and causes no additional problems.
Solutions Etcetera said:
When you say 'reset', do you mean reset or just rebooting your phone?
BTW, I have no LocationServices on my Nexus 4, so these seem to be Moto's binaries, which makes sense.
Would appreciate you keeping us posted if this continues to address the issue and causes no additional problems.
Click to expand...
Click to collapse
I mean rebooting the phone. I use Waze everyday for commuting. I will report back if this fix doesn't work.
In terms of side effects, I have not seen any yet.
Sent from my XT1053 using Tapatalk 2
I see both, and if I stop one, I get no better GPS lock.
I've been getting g terrible GPS lock recently and also posted a thread.
Driving me nuts.
Sent from my XT1060 using XDA Premium 4 mobile app
monorailmedic said:
I went ahead and posted my situation to ... There are no apps in common with all three devices (yours, mine, my wife's). The quest continues.
Click to expand...
Click to collapse
I have the same problem. XT1053 on T-Mobile constantly loses GPS signal while driving. Happens in wide open areas with no buildings. I have tried wiping the device and not installing any additional apps and have the same results. I can be sitting at a traffic light have GPS signal, lose it for a few seconds then get it back without having moved.
Here is a poorly shot video of this happening. I will try and get something more clear tomorrow.
http://www.youtube.com/watch?v=N5MeEVS1DW0
Sent from my XT1053 using xda app-developers app
I returned my phone for this issue yesterday. I had navigation issues along with the drive assist problem. While driving maps world just stop. If I was at a turn and turned left the map would stay stuck at the turn long after I turned. It eventually would catch up. Loosing and gaining lock would perfectly explain this.
Update: I got a replacement phone. The new phone has the same problems. May be a bit worse.
Sent from my XT1053 using Tapatalk
Been chasing this one for a while and still think this isn't hardware related (lots of Nexus 5 users seeing this on KK as well).
My latest theory, which I have yet to disprove, is that the GPS data downloaded from some cell towers (this is the A in AGPS) is either wrong, or is somehow getting corrupted.
When this happens to me, turning on airplane mode immediately restores a quick and persistent lock. And using GPS Status to reset/erase the AGPS data returns normal operation... for a while.
It's like the initial fix info is fighting with the actual GPS readings. As soon as you turn off the cell towers, or clear the data they are providing, all is well.
I am in T-Mobile fringe area and see it fairly often. So far it has always cleared up by trying the above.
This is am interesting theory. I will check it out a bit. Most interesting is the idea that the agps data structure may be slightly different for kitkat v ICS, and that it may also be different for TMO. The main idea supporting this (though purely anecdotal) is that it does happen on both my tmo Xs but neither of my VZW Xs.
Sent from my XT1053 using xda app-developers app
After searching extensively on the whole Nexus 6 signal debacle. I've gotten some observations and studies to share and a couple questions.
I recently obtained a Nexus 6, which I already knew had the ! no data connection problem. (I tried to help the previous owner with the issue before, calls/texts would work, but data wouldn't) They were naturally on T-Mobile, so I assume it was related to the project Fi launch. Googling the issue recently states mostly T-Mobile and Sprint users having the issue, so I decided eh can't pass up a good deal! A like-new Nexus 6 for only $70, who can resist? I figured even if I get the no data issue, I can just turn on airplane mode, use as a mini-tab.
Here's where it gets interesting: I use Cricket (which is AT&T of course), popping the sim in results in good signal, LTE, etc as expected. Randomly (sometimes within 2 minutes) instead of the "!" on service problem, it drops to No Service completely. A reboot and it comes back fine, this wouldn't be too much of an issue except it happens EVERY 2-10 minutes. The only way to get it back is a reboot, airplane mode toggle doesn't help.
Which leads into the second part of the conundrum: Airplane mode doesn't help.
I figured I might just keep it in airplane mode and use as a tablet... The phone said no, Was fully charged before going to bed, by morning 17%. In airplane mode no less, which is of course is abnormal. Looking into it, it seems the phone never went into Deep Sleep, which I immediately delved into the cause. At this time I was running CM13 latest nightly, naturally I went for a fresh stock flash... Same issue. I even stock flashed to 5.0.0 and the same issue... Looks like hardware, but the randomness is the confusing part and you'd think if it was hardware a simple reboot wouldn't fix.
The phone never slept because when it would "No service" on me, I'd get wakelocks for "msm_hsic_host" which would keep the phone awake EVEN IN AIRPLANE MODE, which also in the battery settings showed the red bar for "bad" signal. This happens with AND without a sim, airplane mode or not. I'm currently on Pure Nexus and Franco's kernel to disable hsic wakelocks, and I'm seeing another one for "qcril_pre_client_init" when the issue happens. Which would be the Qualcomm radio interface layer, by the name, I'm assuming android is trying to turn on the radio and keeping the phone awake. This shouldn't happen in airplane mode, I've also tried "Toggle Cell Radio 5.0" to directly turn off the cell radio; Issue remains.
The randomness of when it happens, how it's "resolved" by a simple reboot, and the fact that airplane mode has zero effect on when it happens basically cripples it as a tablet as well, it never sleeps so the battery life is pretty crap (about 18%/hour screen off). After a reboot the thing is great as long as the thing has signal, runs cold, great life, charges fast, sleeps deep. Befuddled that it still does it without a sim card and airplane mode...
My question to the users here: If anyone else has any insight on this, and if anyone knows how to completely disable the cellular interface and literally turn it into a tablet. Is there any rom or such that doesn't try to wake/use the cellular radio and keep the thing awake.
EDIT: Yes, I've run the factory images from google, 5.0.0, 6.0, and 6.0.1 during testing.
The sim card is new, I've already changed it.
Yes the device is actually an XT1103, not a knockoff.
Sorry if any of this information wasn't clear enough.
Further Observations:
During the night I had zero reboots (It's setup to reboot on signal loss, so from here reboot == signal loss), then after taking it off of charge and turning the screen off, then back on after about 5 seconds the signal was lost and it rebooted.
This got me thinking, so on the way to work, I streamed music and had zero problems, not on the charger. After reaching work, I moved some offline music onto my phone and it acted fine as well. The phone never reboots if the screen is kept on as well.
This tells me it's something about how android switches to low-power on the cellular radio. Perhaps the radio cannot wake up properly from the low-voltage sleep state.
tl;dr
When phone is 'active' and not sleeping, problem doesn't arise.
Acts normal with screen off: Streaming music, Regular music, Plugged in.
Acts normal with screen on always.
If doing nothing and phone sleeps: reboots, usually on wake up (i.e. turning screen on to check time)
Likely issue with sleeping/low-power to the cellular radio.
Current bad "solution" play music with phone muted.
However, this doesn't seem to be too bad an impact on battery life, music player has used a total of 1% in the last two hours, screen is top again, where it was android os.
EDIT: Went all day without dropping signal by keeping music playing muted. At 52% after about 12 hours, 3 hours screen on, an hour VOIP call, wifi on the entire time. Not the best solution, but it's livable.
Further testing: I've tried a couple "keep awake" apps that set wakelocks and they do not seem to help, but this might be that they are not designed for marshmallow.
I've also "unoptimized" anything related to phone/cellular in the battery settings to prevent doze from sleeping them, no effect, double the apps directly hit the radio.
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
simms22 said:
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
Click to expand...
Click to collapse
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
zelendel said:
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
Click to expand...
Click to collapse
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
like was said, kinda sounded like you flashed a stockish kinda ROM. if not factory image, I recommend it.
Skreelink said:
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Click to expand...
Click to collapse
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
zelendel said:
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
Click to expand...
Click to collapse
Yes it is a legit device directly from tmobile. I'll do more testing tomorrow.
Maybe try a new sim card,only thing I can't think of
holeindalip said:
Maybe try a new sim card,only thing I can't think of
Click to expand...
Click to collapse
Already got a new sim, updated info in original post.
Attached a screen with battery info, from testing it's pretty accurate.
After implementing my "solution" for a couple days, it seems to sleep fine now without losing signal. Remember, I have tasker setup to reboot on signal loss so this is informative that it actually sleeps now...
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Jnewell05 said:
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Phone has never been wet or suffered any trauma such as a drop or high temps. It's an odd little thing.
Try flashing a different modem?
dcrews said:
Try flashing a different modem?
Click to expand...
Click to collapse
I have, I think it's a hardware problem where the modem can't wake up from low power state similar to some cpus unable to wake if set too low.
Seemingly a breakthrough
Did a few more things and testing and I seem to have gotten onto something. I've attached screenshots showing just over 3 hours deep sleep and included battery info page. As a recap I couldn't get 10 seconds of deep sleep before tasker would wakeup the phone because it lost signal, then wait 30 seconds before rebooting it to get signal again, unless I was playing music (which kept the phone awake and thus never lost signal). You may notice on the upper left the carrier symbol, I'm on Project Fi and using Signal Spy to show which carrier I'm currently on. After doing my tests today it swaps carriers fine without ever completely dropping the radio and requiring a reboot to regain signal.
I'll do more tests and see how long, if it does to act up. If I seem to have actually found a real solution, I'll post what I did to resolve the issue just incase any other Nexus 6 users are experiencing problems.
Edit: Small note worth mentioning, wifi seems more stable as well. I'm able to keep AndroIRC connected with the screen off whereas I was having issues with it disconnecting randomly. This MAY just be due to something else, but still noting it here.
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.