Insane number of wakeups from com.google.android.gms - Nexus 5X Q&A, Help & Troubleshooting

I'm rooted and running stock rom & firmware with TWRP as my recovery. I'm getting a little over 3H of on screen time, which is decent, but I wonder if it could be better if Google Play Services wasn't causing so many wakeups. BetterBatteryStats is reporting between 2.5 and 3.0 wakeups per minute for com.google.android.gms. I tried uninstalling and reapplying its update but saw no improvement. Anyone know how to fix it?
Anyone else running factory software with root have the same issue? I don't have much interest in going with a custom ROM but good battery life is nice.
TIA,
Magnus

insane you say?
if you go to the BetterBatteryStats thread, and see the screenshots you would see 2.7 wakes per minute on the author's phone from the same application. So I would say it is the normal rate (as much as I dont like it). So please change the title to something less bombastic than "insane".

Related

Telus Desire HD running CyanogenMod 7.0.3 - 150-300mA battery drain on idle - HELP!

Hi everyone,
I just recently rooted, and flashed CM 7.0.3 to my Telus Desire HD (signature has phone details), and after the first day noticed SIGNIFICANT battery drain; overnight on Standby it would drain 50-70%!
I installed the Current Widget and it showed throughout most of the night it would average 140-360mA of drain! Checked the Battery Info, and it showed ADWLauncher to be the highest source of drain, along with Sensors.
I'm just re-conditioning the battery now, but this has gotten me concerned. The phone is brand-new, along with the battery.
ADWLauncher is key to the ROM, so can't really disable it. I wiped Dalvik, Cache, User, before and after installing CM, so not sure what else I can do...
I didn't want to install any ROM that has HTC Sense components because their app permissions give me goose bumps (Sense UI = asking to be hacked), so that's why I went with CM. Also used it on a Moto Milestone, and it ran beautifully on that phone.
Can anyone help please? I'm at my wits end
I am unable to directly solve your problem, but I have some thoughts that could potentially solve this problem.
Firstly, what is the state of your ADW desktop at the moment? Try clearing all but the Current widget and see what happens. Another thing to try is disabling all of the 3D effects and such in the menu.
On a final note, ADW is not a core part of cyanogen-mod, you can just install Go Launcher, for example, and it will completely replace ADW. That is another thing to try.
Let us know how you get on.
I'd suggest installing a very lite launcher from market..even lighter than Go Launcher or Launcher Pro, setting it as default and uninstalling AWD with Root Uninstaller.
However, that's the not-curious way of dealing with the problem. AWD should not be consuming that much in CM. I remember Kalabdan had done a great job on the Milestone. Try to find out if your AWD can be upgraded. If all else fails try out the CM RC1 which has been out for a while.
I'd recommend wiping data+cache and formatting the system partition before flashing a rom.
KrisDouglas said:
I am unable to directly solve your problem, but I have some thoughts that could potentially solve this problem.
Firstly, what is the state of your ADW desktop at the moment? Try clearing all but the Current widget and see what happens. Another thing to try is disabling all of the 3D effects and such in the menu.
On a final note, ADW is not a core part of cyanogen-mod, you can just install Go Launcher, for example, and it will completely replace ADW. That is another thing to try.
Let us know how you get on.
Click to expand...
Click to collapse
So far I just finished fully re-conditioning the battery, and have wiped the batterystats.conf file via ClockworkMod Recovery, and also wiped out the cache just to let it re-build just in case.
I checked out reviews on Go Launcher for Desire HD users, and a lot of people report seeing a higher battery drain with that one, than others like ADW. I think I'll wait to see how it behaves after re-conditioning first, and see if there is any improvement. If that fails, I'll give Go Launcher a try.
Do you think I should install one of the new CM7.1.0 nightly builds to see if it helps? I've read a lot of forum postings claiming to see marked improvement in performance and battery life after upgrading to it...
Cheers!
Well, after doing everything in my last post, battery life has improved, but it's still draining faster than what I think it should be...
I've attached my currentwidget.log file to this post so you can see for yourself the drain I'm experiencing.

Do you think Samsung will fix the horrid battery life some experience in ICS?

You know, I just don't get it.. I see some folks getting 4.5+ hours of screen on time which I can get from Calkulins EL29, but I am lucky to get over 2 hours of screen on time on ANY ICS ROM.. Folks say it must be rogue apps that are causing wakelocks. My question is why do wakelocks seem to be so rampant on ICS, yet on EL29 I had no issues? I reinstall the same apps with every ROM installation. Same settings, no additional apps, no less apps than what I had on the last ROM. So I have to ask, what gives? Is this purely an optimization problem on the software to hardware end of things that varies by device? Bad luck? ect?
PaulB007 said:
You know, I just don't get it.. I see some folks getting 4.5+ hours of screen on time which I can get from Calkulins EL29, but I am lucky to get over 2 hours of screen on time on ANY ICS ROM.. Folks say it must be rogue apps that are causing wakelocks. My question is why do wakelocks seem to be so rampant on ICS, yet on EL29 I had no issues? I reinstall the same apps with every ROM installation. Same settings, no additional apps, no less apps than what I had on the last ROM. So I have to ask, what gives? Is this purely an optimization problem on the software to hardware end of things that varies by device? Bad luck? ect?
Click to expand...
Click to collapse
Are you restoring data? that can have issues. Also some of the apps you use might not work the best on ICS. I would say install them 1 and a time and see when you battery drops. I can easily go all day with ICS
rujelus22 said:
Are you restoring data? that can have issues. Also some of the apps you use might not work the best on ICS. I would say install them 1 and a time and see when you battery drops. I can easily go all day with ICS
Click to expand...
Click to collapse
I am, yeah. Honestly I hardly use most of the apps on my phone. I use Opera, stock sms app, navigation sometimes, I use Mr. number which is a call blocking program, the stock music app and youtube. Pretty basic stuff really, I have a few other apps but rarely if ever open them.
Im not a dev or anything, so my understanding of this stuff is limited.
What would Samsung do to fix battery life that the devs on this board can't? srs question
magnumtripod said:
Im not a dev or anything, so my understanding of this stuff is limited.
What would Samsung do to fix battery life that the devs on this board can't? srs question
Click to expand...
Click to collapse
They could do what HTC did with their latest phone and install an auto task killer which kills running apps. I hope they don't because I was reading in the one x forums that if you just switch apps real quick say from the internet to messaging and try to go back to the internet 20 seconds later it has been closed and reopening it takes you to the homepage. that's one idea
Sent from my iPhone killer.
Probably ICS is not reading screen on time right. They last almost the same to me but ya ICS screen time is half of gingerbread but I've used them the same amount, I do the same thing everyday at work so my usage of the phone is always almost the same.
Sent from my SPH-D710 using Tapatalk 2

Memory consumption with lollipop

My lollipop experience is this: battery life seems OK but less than I was getting with the elementalx kernel, the sound stutters especially when the screen is locked. Its pretty random but the buffer is underrunning at times. Which leads me to what's bugging me the most. With KitKat and the same apps installed I was getting roughly 800mb-1gb free of memory. With lollipop it starts out OK at boot but quickly starts eating up ram like candy. I've had Pandora force close in the background which is probably why I'm getting sound stutters because something is using memory and force closing services in the background. I'm using apex launcher and that constantly has to reload to. Before it very rarely reloaded. Also various widgets are having their services killed and I have to go and manually restart them. I've gone from 1gb free typically to like 3-400 mb free. Does L really use that much more ram? Also what about the damned "focus" on battery life they claimed? Its definitely worse here. Looks like this update was half baked if you ask me. I'm at least not getting horrible fps in games like some are claiming. And yeah the YouTube bug is really random and annoying. Anyone else have low memory issues??
Sent from my Nexus 7 using XDA Free mobile app
Same issue. But found the soultion
Facing the same issue. But what i came across is that maximum people who updated to lollipop via OTA are facing these.
Others who have side loaded it or flashed the new lollipop image are all fine. There are bugs in lollipop but atleast they are not facing the terrible issues like us. That battery life is insane , i cant use it as my daily driver with such pathetic battery life. But people who have updated it other than OTA are infact getting better battery than KitKat what Google claimed it to be.
Also the memory issue. Yes this is the main problem what we all OTA updaters are facing. This is called memory leak. I founded it over here. Few developers have explained it in detail - You should have a look.
They have suggested for a clean install of lollipop by complete flash or a factory reset. I have not done it yet. Too lazy to get the backup and all.
But have to try it as we are left with no other option. Check out this link for memory leak - tinyurl.com/pmjlol2
If you decide to install it yourself, use one of the current builds instead of the factory image. Google has pushed a few revisions out.

Battery left getting worse.

Had amazing battery life when running the stock kitkat ROM and even when running early stock Lollipop builds. Now I'm struggling to get 5 hours out of the device with moderate usage - Streaming music, scrolling on social media apps and the occasional browse on the internet. Been having this issue for a while now but it's starting to get irritating when I have to carry a charger around with me like an Apple user, issue has been present on pretty much every ROM ranging from CM based and stock based which leads me to thinking it's a device problem.
Anyone know how I can check what's draining my battery as the battery stats doesn't really help, downloaded a wakelock detector but I can't make sense of it. Currently running ChupaChups 4.1 on a D855 model.
Cheers.
CurtisAndroid5 said:
Had amazing battery life when running the stock kitkat ROM and even when running early stock Lollipop builds. Now I'm struggling to get 5 hours out of the device with moderate usage - Streaming music, scrolling on social media apps and the occasional browse on the internet. Been having this issue for a while now but it's starting to get irritating when I have to carry a charger around with me like an Apple user, issue has been present on pretty much every ROM ranging from CM based and stock based which leads me to thinking it's a device problem.
Anyone know how I can check what's draining my battery as the battery stats doesn't really help, downloaded a wakelock detector but I can't make sense of it. Currently running ChupaChups 4.1 on a D855 model.
Cheers.
Click to expand...
Click to collapse
I get 6/6.:30h of sot with 16h on battery(with cc 4.1) in wakelock detector the apps that are on thee top off thelist keep your device awake the longest the x(number) represents how much time your phone has been wokken and the minutes/seconds is how long an app used the cpu. all non system apps on top off the list are popential drainers

Massive wakelock in Android OS proccess on H815 MM roms. Please help !

Helo to everyone,
I'm facing a serious problem lately. No matter which stock MM rom I flash I get wakelock on Android OS proccess. Let me explain all in details. The way I flash a new rom is as everybody - I wipe all partitions except internal memory and external sd card. Then I flash the new rom and later I restore my apps using titanium backup pro. I find it very usefull as with it I can restore my programs the way they were setup before the rom change/update. It's very usefull if somebody like me is doing some tweaks for battery life with amplify, greenify and etc. in which there are a lot of tweaks and settings that are needed to be applied. There are several several nice guides on xda on how to get a nice battery like my favorite one from our member v7 - ✭[GUIDE][07-02-2016]Extreme Battery Life Thread(Greenify+Amplify+Power Nap)✭ It's very time consuming to make all the tweaks on this guide on a new rom one by one so I use titanium to restore the amplify app with the setup. Anyway all was working fine and I was able to get very nice SOT and great battery life and almost no drain if I don't touch my phone - here is a screenshot what batterylife I was getting before - screenshot 1
In a few days before a new versions from our favorite modified stock roms were posted and I decided to update my rom with one of them and then after setting my phone as usual I noticed extremely hard wakelock on Android OS process. Now my phone cannot enter on deepsleep and if it enters it doesn't sleeps long enough. I did some research and the only thing I found was it maybe from Google play services. I made some screenshots from BetterBattery stats program to show for what I'm talking about. Please check all the screenshots and they speak for themselfs. I tried several guides on how to fix playstore and services but with no luck. I'm almost pretty sure that the problems are in google playstore and google play services as it seems they are running 99% of the time and are preventing my phone to enter deepsleep. I tried to freeze and remove them and my phone entered deepsleep with no problems. I don't play games and don't use any battery hog programs - the only program that is running all the time is facebook which I moded to use without messenger and it was working fine. From the screenshots it is clearly visible that it is not draining my battery. Please if anybody can help me fix this problem please write me what I'm missing or doing wrong.
I had uploaded all the screenshots on my dropbox that I made to help you guys find what my problem is. They are uploaded here also. Thank you for your time ! Wish you all to have the best battery life that is possible
Hi guys,
Today I noticed that the developer of genesys rom found about this wakelock in Android OS proccess and he removed the links to his rom until he fixes it and release a fixed version. I also read that other guys are experiencing the same issue. That is some kind of good news for me because I started thinking that I was doing something wrong, but now after I read that other people are experiencing the same issue on the new version of the genesys rom (3.9) I feel better as the problem is not at my phone and apps setup. So now all we have to do is wait till the problem gets fixed. There wasn't any responses to my thread maybe because all is looking good from my screenshots but it is acting wierd and maybe nobody wasn't able to give me a solution for this problem. But I'm sure that the developers are doing their job and they will get it fixed. Anyway I'm very interesed why this happened and would like to know more about it but we will see this in future. So if somebody else is experiencing the same problem - let's wait patiently till it get's fixed. Thank you all for spending some time to check the thread. Good luck.
A better tool that can help figure what is causing these problems is battery historian.
https://www.reddit.com/r/nexus5x/comments/3y8144/guide_finding_battery_issues_with_googles_battery
Generate a bugreport, check it in a txt editor and remove any sensitive info, then upload to the server setup.
You want to do this at the end of a charge cycle so you can closely examine where the drain is happening and maybe get more clues as to why.
Your case is more complicated since you are using a rom. But maybe this can still help.
Varna ? you come from gsmarena country

Categories

Resources