My phone is greenified (Google Search and Google Play Services as well) and a lot of apps are frozen through Titanium Backup. I also have Wakelock Terminator installed and set to terminate wakelocks coming from Google Play Services. The wakelocks I have set are:
NlpCollectorWakeLock
com.google.android.gms
AudioIn
I've recently noticed that quite often, I won't receive notifications until I turn on my screen. Just now I turned on my screen and received a WhatsApp notification from 40 minutes prior.
WhatsApp is NOT greenified on my phone so I'm not really sure what is causing the notifications to sleep until I turn on my screen. Would anyone have a clue as to what might be causing this?
Same here
I too started noticing the exact same issues you mention, probably about a month ago now. At first I thought it was greenify too, even though I have pro and gcm push enabled which never caused issues in the past.
But temporarily disabling greenify didn't solve anything.
Then I thought it was unbounce xposed module, now called lion tamer. But disabling that made no difference either.
I assumed I had messed the phone up with various mods and had to live with consequences. But recently I stumbled across an app on the playstore called "Push Notification Fixer"
It appears that these delays in notifications are due to a problem at Google end. And I have a feeling one of the recent firmware update from LG has made the problem more apparent to us. I still don't understand why more users aren't noticing and reporting this though....
RichardW1992 said:
I too started noticing the exact same issues you mention, probably about a month ago now. At first I thought it was greenify too, even though I have pro and gcm push enabled which never caused issues in the past.
But temporarily disabling greenify didn't solve anything.
Then I thought it was unbounce xposed module, now called lion tamer. But disabling that made no difference either.
I assumed I had messed the phone up with various mods and had to live with consequences. But recently I stumbled across an app on the playstore called "Push Notification Fixer"
It appears that these delays in notifications are due to a problem at Google end. And I have a feeling one of the recent firmware update from LG has made the problem more apparent to us. I still don't understand why more users aren't noticing and reporting this though....
Click to expand...
Click to collapse
Use the "Root Push Notification Fixer". it's a fantastic app that makes push notifications so much more reliable.
Hypercore said:
Use the "Root Push Notification Fixer". it's a fantastic app that makes push notifications so much more reliable.
Click to expand...
Click to collapse
Just did a wipe but if I notice this happening again, I'll try this. Thanks!
Related
The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.
Just to maybe assist you in finding the culprit I'm on 4.6.3 with google apps but no root. I've not experienced any wake locks. Perhaps clearing Google's cache and data?
Sorry I meant I was on 4.6.1 still. Will clear data and see.
adam.nox said:
The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.
Click to expand...
Click to collapse
Probably one of those glitches that can be solved by a reboot. However, you can disable updates using hdxposed module for xposed if you want.
Done both of those things plus much more. Anyone else having this issue?
try taking a titanium backup of everything and then factory reset.. with everything backed up to your PC. then root and start restoring everything gradually.. start by social apps and call log and messages.. then your essential apps.. and see.. then add the rest of the apps bit by bit till you find the offending application or maybe something just got screwed will be fixed when the data clears..
just make sure there is nothing out of the norm in your essential apps, meaning they are all tried and tested by everyone.. facebook, whatsapp, keep, launcher.. that stuff. and also make sure in these apps to limit their ability to check every X minutes as they can really drain your battery.
I've disabled wakelock on anything that has reported to use it by wake lock detector that I don't absolutely need to have it. I've uninstalled any non-essential apps. I've done too much tinkering and have too much important app data to risk doing a reset when it may not work.
I need a way to actually get to the bottom of it first.
Why is google play services waking the phone 2000+ times per day? Wake lock detector says the phone has been awake 5 hours out of 10, but then the list of times for each app only adds up to 20 minutes. How do I find out what was keeping it awake the rest of the time?
Possibly some kind of location based frippery. Try removing location access from troublesome app. And turn off auto sync if it's on
Location services are completely disabled. Auto sync is off. Both have been since this started happening.
Used app quarantine to disable almost every app I put on here, and Fire OS is still 51%.
Possible culprits, though I'm not sure if I find it likely: Ultimate dynamic navbar, lightning chat, foscam viewer, google apps, xposed mods (have a few). greenify (that would be ironic), flixter, es file explorer, buildprop editor, calculator, jellybean keyboard, multi timer, skana battery alerts, nova launcher, power toggles, slacker radio, bank app, super user, terminal emulator, outlook, wakelock detector.
Get better battery stats from xda, it gives a better breakdown of wake locks.
Alright what should I look for in there?
Ok here is what I believe I have found out, using network log along with better battery stats.
The phone is waking up constantly due to netbios pings (I know not technically pings), from various computers on my network, mostly my main PC. I don't know why it's doing this. Could be one of many background processes. In my opinion, it shouldn't matter. The phone shouldn't be that stupid.
I was able to... I think, mitigate a lot of this by doing a few things.
The first is editing qcom's ini inside etc/wifi so that if it says offload, I put a 0, I assume it's offloading to the cpu, which causes it to wake for pointless crap. The second thing I did was re-enable optimized wifi. This is probably already on, on everyone else's phone. I turned it off because I was trying to figure out how to tether while connected to a vpn through the phone. Still can't get that to work. And I know how to, because I did it on my nexus prime, but something in the fire OS is f'ing that method up (iptable configs).
I'm considering seeking an app to turn off wifi when the phone sleeps, because better battery shows wifi on 100%, and even with the changes above, I was still responding to some netbios pings in the network (about 1/5th as many). I imagine most networks will have noise like this.
However, even after all this, fire OS is still the main battery draw. Better Battery doesn't account for all the wake time, not even by half.
For now I've put enough time into this.
I got my Pixel XL (unbranded) earlier this month, and as much as I wanted to love the phone, two consistent issues keep happening which are making me despise it.
The first issue is my phone refuses to retrieve Push notifications while it's on standby. I will get no notifications from any app until I physically wake my phone. As soon as I pick the phone up and turn on the screen, BAM, a billion notifications. This is true even for Google apps like gmail and hangouts. I have seen lots of threads on this subject dating back years for various devices, and none of the 'solutions' fixes my situation. Battery Optimization isn't on, and even when I toggle it on and exempt all my apps, it still does it. IPv6 is disabled at my home network level. I disabled the Connectivity service. I enabled notification importances and set all apps to high. I turned off WiFi while on standby. I begrudgingly did a full reset. Nothing has worked.
The second issue is related to bluetooth. I cannot get it to stay on. It turns itself off whenever it feels like, so whenever I get into my truck and expect my GPM to start playing, all I get is "The bluetooth stereo device is not connected." I take pride in my attentive driving, which means if I forget to reconnect everything while still in my driveway, I now have to pull over just to get some tunes playing. Getting infuriating...
So, I'm at my last nerve. I turn to the Gods of XDA for your advice before I return this thing. Is there any fix to all this? I'm not opposed to rooting or using custom images. I just want my phone to work.
Thanks in advance for any info you can provide.
Google is aware if the Bluetooth issue, the Feb update caused it. They are working on a fix.
I got nothing on the notifications. Gmail doing that is quite common and goes beyond the Pixel. Never heard of anyone having issues with other apps.
You running any doze programs or task killers?
TonikJDK said:
Google is aware if the Bluetooth issue, the Feb update caused it. They are working on a fix.
I got nothing on the notifications. Gmail doing that is quite common and goes beyond the Pixel. Never heard of anyone having issues with other apps.
You running any doze programs or task killers?
Click to expand...
Click to collapse
It wasn't the Feb update. Bluetooth got bugged in the 7.1.1 update for me personally.
TonikJDK said:
Google is aware if the Bluetooth issue, the Feb update caused it. They are working on a fix.
I got nothing on the notifications. Gmail doing that is quite common and goes beyond the Pixel. Never heard of anyone having issues with other apps.
You running any doze programs or task killers?
Click to expand...
Click to collapse
No, the phone is pretty much stock. I have Skype and a couple games on it, but nothing that would interfere with network connectivity while on standby. Just to be sure, Doze is Battery Optimization in the settings, right? It's default to off, but after experiencing issues, I turned it on and exempted all apps. Didn't work, so I turned it off again.
I've never had this issue with GMail. The latest I have ever been notified of a new email from gmail is about 5 mins. Now, I go hours without them up until I wake my phone. And again, this is for all apps that have actual push notifications. I'll pick up my phone, then get a slew of new emails, skype messages, hangouts, etc...
Helllo there!
Since a long time, I am experiencing issue with push notifications on my device. Especially when an app is not used for few days, the notifications stops appearing from the app. The frequently used app are displaying notifications.
Is it common? Anyone experiencing this? Is there a setting which I can change to get this fixed?
Tired searching the forum but could not find any info.
This was happening when I was running OxygenOS 4.1.6 and even after recently upgrading to Open Beta 20, the problem still exists.
Any info would be helpful.
Thanks!
Turn off the Battery Optimization for the apps... it is part of Android's "Doze" functionality.
I had this issue when I chose "deep clear" in recent app management and cleared the tasks. After switching to "normal clear", and re-starting apps everything started working as normal again.
So I've been having this issue for quite some time, but i guess i got used to it so it didn't pose much of a problem untill now. All of my Whatsapp messages are delayed when screen off and WiFi on, and they come through from 2-4 all the way up to 20+ min after they are sent. As soon as i turn screen on, they pop up on screen.
I assumed that it was due to greenifys rigorous doze settings, so i uninstalled it. Some threads suggested Titanium backup may be culprit, so i uninstalled it too. I also added Whatsapp to battery optimization whitelist and ticked on run in background and unrestricted data usage, but with no success, and also completely reinstalling Whatsapp.
I even reflashed stock pie and oreo, but same thing happens. I suspected that deep sleep might be interfering with cloud messaging services, but even on stock pie device enters deep sleep even with WiFi on in minutes after screen off, so im pretty confused with it all.
I am running Pie v10.0.9.0.PLDMIXM with magisk, busybox, xposed, substratum, gravitybox installed. Apart from that there are no other apps interfering with the system whatsoever.
Any help would be much appreciated.
CrimosUmbro said:
So I've been having this issue for quite some time, but i guess i got used to it so it didn't pose much of a problem untill now. All of my Whatsapp messages are delayed when screen off and WiFi on, and they come through from 2-4 all the way up to 20+ min after they are sent. As soon as i turn screen on, they pop up on screen.
I assumed that it was due to greenifys rigorous doze settings, so i uninstalled it. Some threads suggested Titanium backup may be culprit, so i uninstalled it too. I also added Whatsapp to battery optimization whitelist and ticked on run in background and unrestricted data usage, but with no success, and also completely reinstalling Whatsapp.
I even reflashed stock pie and oreo, but same thing happens. I suspected that deep sleep might be interfering with cloud messaging services, but even on stock pie device enters deep sleep even with WiFi on in minutes after screen off, so im pretty confused with it all.
I am running Pie v10.0.9.0.PLDMIXM with magisk, busybox, xposed, substratum, gravitybox installed. Apart from that there are no other apps interfering with the system whatsoever.
Any help would be much appreciated.
Click to expand...
Click to collapse
It's the system power and ram management. That system kills the processes and doesn't allow them to revive for instant notification. Same happens with facebook and facebook messenger, not only watsapp. Instagram does this also. I receive a follow notification on my iPhone and the notification appears on the Mi A2 Lite only after the screen is on and unlocked.
TheoXSD said:
It's the system power and ram management. That system kills the processes and doesn't allow them to revive for instant notification. Same happens with facebook and facebook messenger, not only watsapp. Instagram does this also. I receive a follow notification on my iPhone and the notification appears on the Mi A2 Lite only after the screen is on and unlocked.
Click to expand...
Click to collapse
Oh i see. i totally get that over agressive ram managment, because even with 4 tabs open, it kills them very soon, to a no avail have i tried to fix it, it seems to be rooted issue...
Do you know any possible fix or workaround for this? Maybe to convert these apps to privileged, e.g. system apps or something? There must be some kind of solution for this.
CrimosUmbro said:
Oh i see. i totally get that over agressive ram managment, because even with 4 tabs open, it kills them very soon, to a no avail have i tried to fix it, it seems to be rooted issue...
Do you know any possible fix or workaround for this? Maybe to convert these apps to privileged, e.g. system apps or something? There must be some kind of solution for this.
Click to expand...
Click to collapse
Nope. Some said that this is purely Xiaomi's fault. But no. I have another Allview phone doing the exact same stuff. This may be an unmodified kernel for the said chipset. Companies like Samsung, Sony, HTC etc. may edit that kernel to be more mild, while Xiaomi, to reduce the costs doesn't.
Anyone know how I might go about diagnosing why my phone has been running much warmer than usual? Just browsing Facebook (posts, not video) for about 5 minutes with brightness around 25% the temp was up to 41 degrees. It happened earlier today when I was just using Chrome, and it happens most days now. The issue began when I updated to 11.2.8.8 (the very next day), and the phone overheated several times the first few days, evidenced by the system warning about temperature, then recovering several minutes later. I haven't seen the system warning since then, but it's frequently above 40 degrees just doing everyday tasks. Oddly, I haven't noticed it overheating when playing games.
I usually run Omega kernel, which has always run cooler than stock during both normal use and heavy gaming, but this issue has occurred with both stock and Omega, so it's not kernel-related. The only magisk modules I have installed are debloater (for YouTube only), font manager, and systemless hosts, so that's not it either.
Maybe some app going haywire (how to find it? Nothing in battery usage) or some system behavior that changed in 11.2.8.8? Anyone else have this issue or find what's causing it?
That's just how this phone is. It was worse when the phone released before all of the updates. They've been slowly trying to fix it with each update. The 888 is a hot *****.
TheKnux said:
That's just how this phone is. It was worse when the phone released before all of the updates. They've been slowly trying to fix it with each update. The 888 is a hot *****.
Click to expand...
Click to collapse
I remember having that complaint when I first got it, especially when gaming, but it's been fine for me since like April, until this last update. And with Omega several degrees cooler. So there has to be something new causing it....
terlynn4 said:
I remember having that complaint when I first got it, especially when gaming, but it's been fine for me since like April, until this last update. And with Omega several degrees cooler. So there has to be something new causing it....
Click to expand...
Click to collapse
What version of Omega are you on? What build of OOS? AA, BA, DA? Are there any unusual rogue apps that you've noticed running more than usual?
TheKnux said:
What version of Omega are you on? What build of OOS? AA, BA, DA? Are there any unusual rogue apps that you've noticed running more than usual?
Click to expand...
Click to collapse
Latest version of Omega (8/7) since yesterday, but was having the same issue on the previous build (7/30). I'm on OOS 11.2.8.8 BA.
I haven't noticed any apps using more battery than expected, but I guess that might be part of my question... If there are any, what's the best way to find them? I'm not seeing any useful info in BBS or anything in GSam I wouldn't expect, except overall battery drain is a bit higher when it's been running hot. I do have a lot of apps installed and should probably clean up what I don't use, so I guess that's a place to start.
Find which apks are using the battery.
Google system apks are prime suspects.
Trash apps like FB, WhatsApp, LinkedIn... none of that junkware runs on my device, ever.
Examine all startup apks closely, take out the trash.
Power management can end up causing excessive battery usage, try turning it off.
Track down each battery hog and deal with it on a case by case basis rather than the flip a switch shotgun approach.
I use Karma Firewall's logging feature to help track down offenders.
Dependencies... sometimes the source of the high usage is hidden. What apks and services are running? What apks are using what services and why? What's apks are getting cached first when you clear them all? Any memory leaks?
Play with it... Androids wuv attention
blackhawk said:
Find which apks are using the battery.
Google system apks are prime suspects.
Trash apps like FB, WhatsApp, LinkedIn... none of that junkware runs on my device, ever.
Examine all startup apks closely, take out the trash.
Power management can end up causing excessive battery usage, try turning it off.
Track down each battery hog and deal with it on a case by case basis rather than the flip a switch shotgun approach.
I use Karma Firewall's logging feature to help track down offenders.
Dependencies... sometimes the source of the high usage is hidden. What apks and services are running? What apks are using what services and why? What's apks are getting cached first when you clear them all? Any memory leaks?
Play with it... Androids wuv attention
Click to expand...
Click to collapse
Good ideas. I just installed Karma Firewall and will see if it turns up anything.
How do you manage startup apps and running services? I used to use Servicely, but with Android 11 I find that even when I disable apps at startup they still start on their own, and it seems to use more battery than it saves. I've since disabled all apps of that kind and just let Android manage things itself. The only thing I do is go to individual apps and turn on battery optimization and disable background data if not needed, and I keep apps I don't use often in Icebox, including Facebook, which is the only social media type app I have. (Uninstalling FB isn't an option unfortunately.)
What do you mean by "which apps are getting cached first when you clear them all?" and how might I find it there are memory leaks?
terlynn4 said:
Good ideas. I just installed Karma Firewall and will see if it turns up anything.
How do you manage startup apps and running services? I used to use Servicely, but with Android 11 I find that even when I disable apps at startup they still start on their own, and it seems to use more battery than it saves. I've since disabled all apps of that kind and just let Android manage things itself. The only thing I do is go to individual apps and turn on battery optimization and disable background data if not needed, and I keep apps I don't use often in Icebox, including Facebook, which is the only social media type app I have. (Uninstalling FB isn't an option unfortunately.)
What do you mean by "which apps are getting cached first when you clear them all?" and how might I find it there are memory leaks?
Click to expand...
Click to collapse
Karma's logging feature doesn't work in 10 and above I believe, I run Pie. See what you got though. It will still block apk internet access though and uses almost no battery.
The battery optimization option can cause erratic behavior and I never use it. Close apps when done with them. Brave browser for instance will run in the background until closed.
Developer options>running services memory leaks show up as an apk who's memory usage just keeps increasing with time. It can get quit large. These are rare and poorly coded programs. More common on Windows.
Keep an eye though for memory hungry apps as they may be using excessive power but not always. Small memory users can be worse. Dependencies, sometimes a apk or service keeps making repeated requests because of a disabled apk or service.
Killing Goggle play Services and Playstore when not needed will help battery life.
Google backup Transport, Framework and Firebase are always disabled on my device.
All carrier, manufacturer, and Google feedback are disabled.
I have a Samsung device and I use its Device Care app to clear the cached apks. Then watch as they repopulate. You'll need an app that does this. In running services you can disable a suspect apk and see how long it takes to come back. I find that Device Care is more effective though and that ability has let me track down some misbehaving system apks saving me a reload.
FB is weaponized and a proven liability. Known data miner. Purveyor of disinformation and dissent. It has ruined countless lives and careers. It deliberately makes you have load the app to be able to send messages. If this last year hasn't taught you what you need to know...
I used it for one month 15 years ago and knew what it was back then. It's far worse today.
Don't feed the beast.
blackhawk said:
Karma's logging feature doesn't work in 10 and above I believe, I run Pie. See what you got though. It will still block apk internet access though and uses almost no battery.
The battery optimization option can cause erratic behavior and I never use it. Close apps when done with them. Brave browser for instance will run in the background until closed.
Developer options>running services memory leaks show up as an apk who's memory usage just keeps increasing with time. It can get quit large. These are rare and poorly coded programs. More common on Windows.
Keep an eye though for memory hungry apps as they may be using excessive power but not always. Small memory users can be worse. Dependencies, sometimes a apk or service keeps making repeated requests because of a disabled apk or service.
Killing Goggle play Services and Playstore when not needed will help battery life.
Google backup Transport, Framework and Firebase are always disabled on my device.
All carrier, manufacturer, and Google feedback are disabled.
I have a Samsung device and I use its Device Care app to clear the cached apks. Then watch as they repopulate. You'll need an app that does this. In running services you can disable a suspect apk and see how long it takes to come back. I find that Device Care is more effective though and that ability has let me track down some misbehaving system apks saving me a reload.
FB is weaponized and a proven liability. Known data miner. Purveyor of disinformation and dissent. It has ruined countless lives and careers. It deliberately makes you have load the app to be able to send messages. If this last year hasn't taught you what you need to know...
I used it for one month 15 years ago and knew what it was back then. It's far worse today.
Don't feed the beast.
Click to expand...
Click to collapse
Thanks for the info, it's interesting. However, if you're running Pie & not even using a OnePlus device, none of this is going to be applicable to my issue which is specific to OOS 11.2.8.8 on this particular device, only present since last month's update.
Re: FB - I'm required to use it for my job (well, second job), and I need it on my mobile device in order to do that job, so it's not going away. Freezing it when not in use is the best I can do.
terlynn4 said:
Thanks for the info, it's interesting. However, if you're running Pie & not even using a OnePlus device, none of this is going to be applicable to my issue which is specific to OOS 11.2.8.8 on this particular device, only present since last month's update.
Re: FB - I'm required to use it for my job (well, second job), and I need it on my mobile device in order to do that job, so it's not going away. Freezing it when not in use is the best I can do.
Click to expand...
Click to collapse
You cross platform OS version and manufacturer to find solutions. I have a lot of posts here but few asking for help because I do the above or just keeps at it until I work it out as it's my issue.
*shakes head*
You've painted yourself into a corner.
@terlynn4 I use BatteryGuru because it uses root to find rogue apps that are draining battery unnecessarily. Give it a go and see if that helps pinpoint the problem at all.