Hello guys,
First, I'm somewhat noob in all of this.
After keep on waiting for the cm12 OTA, I finally decided to root. Since I am very new to rooting game, I have done long and hard research about everything related to root, twrp, unlocking bootloader and supersu. Then I followed this guide step by step without missing a bit:
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
I downloaded and flashed these (following the guide)
cm-12-20150329-NIGHTLY-bacon - directly from cm website
and
gapps-lp-20150222-signed - from basketbuid
Everything went smooth without any problems.
But the battery started giving me the worse time ever I had with OPO. The culprit seems to be the 'Android System' which was taking my whole battery to sh*t even when the phone was idle with wifi and mobile data being turned off. It was keeping my phone (specially the CPU) awake the whole time. Then I downloaded Wakelock detector, greenify and tried everything that i found anywhere and everywhere, including the privacy guard with play services and others wake up feature being turned off, but nothing helped.
Here are some screenshots of bettery life
http://i.imgur.com/ygcx1al.png
http://i.imgur.com/fe2hQaL.png
http://i.imgur.com/dmY8Hs2.png
http://i.imgur.com/fC17Yfc.png
I newly re flashed CM 12s nightly (after wiping everything as a new OS) which is
cm-12-20150402-NIGHTLY-bacon
I left the phone as it is without installing the Gapps after installing the rom for couple hours and saw the battery was not draining while the phone was idle neither it was draining while the screen was on as it drained with Gapps being installed. Then I installed the Gapps from here -
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330.
And then it started again being "Android System" on the top of the list of battery usage.
What should I do now?
Anyone had/having the same issue?
Did I do anything wrong?
Thank you very much for reading this long post and any help in advance.
It's probably Google Play Services that's draining your battery, try this:
http://forum.xda-developers.com/showthread.php?t=2832525
Transmitted via Bacon
Better than AppOpps:
It's most likely the "SystemUpdateService" which constantly runs in the background with custom Roms. If your phone is rooted, download and install 'DisableService' app from Google Play and navigate to System>Google Play Services>SystemUpdateService and disable it. You have to do this everytime you reboot since it just tells you which services autostart and then you're able to disable them. This is a better fix than the AppOps option as you still need Google Play Services to run in the background. I had this same issue and this fixed it.
joshklee said:
It's most likely the "SystemUpdateService" which constantly runs in the background with custom Roms. If your phone is rooted, download and install 'DisableService' app from Google Play and navigate to System>Google Play Services>SystemUpdateService and disable it. You have to do this everytime you reboot since it just tells you which services autostart and then you're able to disable them. This is a better fix than the AppOps option as you still need Google Play Services to run in the background. I had this same issue and this fixed it.
Click to expand...
Click to collapse
The only reason you need Play Services to run in the background is if you need your location updated every minute for Google Now cards. Every single other Google service runs perfectly being pulled instead of pushed.
Transmitted via Bacon
This is more of a specific fix for a specific problem. This solution is like fixing the leak instead of turning off the water.
joshklee said:
This is more of a specific fix for a specific problem. This solution is like fixing the leak instead of turning off the water.
Click to expand...
Click to collapse
If you say so.
Transmitted via Bacon
joshklee said:
It's most likely the "SystemUpdateService" which constantly runs in the background with custom Roms. If your phone is rooted, download and install 'DisableService' app from Google Play and navigate to System>Google Play Services>SystemUpdateService and disable it. You have to do this everytime you reboot since it just tells you which services autostart and then you're able to disable them. This is a better fix than the AppOps option as you still need Google Play Services to run in the background. I had this same issue and this fixed it.
Click to expand...
Click to collapse
will try it now and post update if anything changes.
timmaaa said:
It's probably Google Play Services that's draining your battery, try this:
http://forum.xda-developers.com/showthread.php?t=2832525
Transmitted via Bacon
Click to expand...
Click to collapse
I have tried it, but nothing happens.
Thanks for the reply everyone.
what if i disable all the packages with 'Disable Service' app that is found under android system in the battery details page?
i.e
quickboot
pppreference
fused location
key chain
ant hal services
locationservices
dev tools
etc.
is that going to interrupt anything or damage the os in anyway?
have the same problem with cm12, tried different gapps, nothing helps.
Related
I've been troubleshooting my NS, trying to find out what's been causing my Android OS battery stats to constantly go around 50%, which causes major battery drain; I usually get 3+ hours of screen on time with my rasbeeanjelly ROM + Trinity kernel combo, but I now only get less than 1 hour.
I tried uninstalling most of my recently updated apps, but Android OS is still at ~50%; until I uninstalled the updates for Google Play Services. And now, my Android OS is back down to 4%.
Anyone had/having this issue? There's your solution.
havent met this issue yet
IIIV said:
I've been troubleshooting my NS, trying to find out what's been causing my Android OS battery stats to constantly go around 50%, which causes major battery drain; I usually get 3+ hours of screen on time with my rasbeeanjelly ROM + Trinity kernel combo, but I now only get less than 1 hour.
I tried uninstalling most of my recently updated apps, but Android OS is still at ~50%; until I uninstalled the updates for Google Play Services. And now, my Android OS is back down to 4%.
Anyone had/having this issue? There's your solution.
Click to expand...
Click to collapse
The Google Play Services will auto update itself and your problem might come back, though. Are you using inverted gapps per chance?
polobunny said:
The Google Play Services will auto update itself and your problem might come back, though. Are you using inverted gapps per chance?
Click to expand...
Click to collapse
I'm using stock gapps. I believe that the Google Play Services update that I initially installed was a manual update, not auto.
IIIV said:
I'm using stock gapps. I believe that the Google Play Services update that I initially installed was a manual update, not auto.
Click to expand...
Click to collapse
That might explain it.
Hey guyz...need some help,
Google now is eating hell lot of battery and is not allowing my device to go in deep sleep mode. I don't want to disable google now but its wake ups in stand by mode are just killing my battery......I have installed appopsxposed and turned off the wake ups, it did work for some days but now it is now back again & taking too much battery.
Also I did tried clearing the cache and data but no help and hotword detection is also turned off.
I m now sick and tired of this thing but don't wanna disable it as it lets me check scores.
What you are experiencing is not normal. I keep all Google services, including Google Now, Location Reporting, Google Plus, etc., enabled all of the time, and still get 1-2%/hr. when idle.
Any BBS log would help. Are you using the newly released Gapps?
ickoicko said:
... re you using the newly released Gapps?
Click to expand...
Click to collapse
What's the latest version, please?
PhilipTD said:
What's the latest version, please?
Click to expand...
Click to collapse
4.1 that's supposed to fix the battery problem of Location Reporting. Here it is
PhilipTD said:
What you are experiencing is not normal. I keep all Google services, including Google Now, Location Reporting, Google Plus, etc., enabled all of the time, and still get 1-2%/hr. when idle.
Click to expand...
Click to collapse
ickoicko said:
Any BBS log would help. Are you using the newly released Gapps?
Click to expand...
Click to collapse
ickoicko said:
4.1 that's supposed to fix the battery problem of Location Reporting. Here it is
Click to expand...
Click to collapse
I m on rooted stock rom with gravity box, elemantal x kernel and even the location settings are turned off
and google play services 4.1.31
Most of the apps are also greenified.....so I tried my best to get max. battery on stand by but this google search.
Is it doing it constantly? I once had the same problem, but it got fixed with rebooting the phone. Google Now drained about 30% in less than 6 hours in my case.
I have a Galaxy Note running stock 4.1.2 Android. Over the last couple of days my battery usage has gone mad and only lasting 8-9 hours. I thought it was a duff battery and put my spare in but same result. When I looked at the battery usage I found that Package Access Helper was top of the list with 35% when it never shows usually. I Googled the problem but there was nothing very helpful.
I am also having trouble downloading any apps or deleting cache. I have rebooted several times, done a battery pull and have re-enabled all the apps I had disabled. It has made no difference and the PAH continues to hammer my battery. I would really like to avoid a factory reset if possible especially as this doesn't necessarily fix the problem apparently.
Please does anyone have any suggestions?
Pinmac said:
I have a Galaxy Note running stock 4.1.2 Android. Over the last couple of days my battery usage has gone mad and only lasting 8-9 hours. I thought it was a duff battery and put my spare in but same result. When I looked at the battery usage I found that Package Access Helper was top of the list with 35% when it never shows usually. I Googled the problem but there was nothing very helpful.
I am also having trouble downloading any apps or deleting cache. I have rebooted several times, done a battery pull and have re-enabled all the apps I had disabled. It has made no difference and the PAH continues to hammer my battery. I would really like to avoid a factory reset if possible especially as this doesn't necessarily fix the problem apparently.
Please does anyone have any suggestions?
Click to expand...
Click to collapse
Have you already flashed the stock rom via Odin?
No, TBH, I wouldn't have a clue how to. I've never done anything to my phones in the way of rooting or flashing.
Does anyone have any thoughts on this please as it is still the same and I'm trying to avoid a factory reset?
Try this
Package Access Helper is the service which helps in installing and uninstalling of apps.
There are many posts of it draining battery.
Are there any software updates available in your phone, install it.
If no open play store and update all available apps.
If not fixed then clear caches using app manager 3 or any other.
Uninstall any recently installed apps when the problem started.
And pull out battery wait for 2 mins reinsert the battery and boot up phone it may be fixed..
Hit thanks if I helped..
kill cached process in developer options
open the developer's options via the last option in your settings (about phone) then scroll down to your build number spam tap the crap out of it then go back to your settings open the development tab open running services and in the top right should say something cached processes and kill process Package access helper.
The package access helper is draining my battery. Is there another app to use
My battery randomly drains excessively. And sometimes I am unable to unlock the device, i need to do a soft reset. Any help?
More information required. What ROM? What modem? What firmware?
timmaaa said:
More information required. What ROM? What modem? What firmware?
Click to expand...
Click to collapse
All stock cm11s 05Q
That's why I went back to 44s
usvimal said:
All stock cm11s 05Q
Click to expand...
Click to collapse
It might be an idea to roll back to the 44S build, test and see if it continues.
Ok thanks!
I had the same problem. Switched to 44s and seemed to be better. However what fixed the problem was not allowing Google play services wake up the device etc. In privacy guard! Also blocked Facebook messanger and right now I'm on 20h on battery and 59% battery left) with mid use. Nothing too heavy.
dav-rmd said:
I had the same problem. Switched to 44s and seemed to be better. However what fixed the problem was not allowing Google play services wake up the device etc. In privacy guard! Also blocked Facebook messanger and right now I'm on 20h on battery and 59% battery left) with mid use. Nothing too heavy.
Click to expand...
Click to collapse
may i know how do you roll back to the old 44s kind sir?
iamzacky said:
may i know how do you roll back to the old 44s kind sir?
Click to expand...
Click to collapse
Restore the nandroid backup you made before you updated
Disable wake lock and keep awake for Google play services via settings>privacy>privacy guard and check if it solves the batter issue. For the phone not unlocking at times, check if you've enabled "Prevent accidental wake up" in Display. Having this turned on was a little buggy and what caused this problem for me back on cm11s.
Cheers
The issue with Play Services 7.x and CM11 is that it causes a SystemUpdateService update. This issue affects ALL custom ROMs with the SystemUpdateService disabled (I believe CM addressed this during the CM11 M4-M5 era).
You have 3 options.
1. This is a fix that many have proposed but I feel is a terrible idea
- Use Privacy Guard to disable Wake for Play Services
Rationale: Play services needs to wake up for other reasons too besides this ridiculous wakelock. It's used for background location when your phone screen is off for things like Google Now and location reminders. Disabling wake for Play Services is like cutting off the water main for a faucet leak. Sure the leak is no more but you can't flush the toilet or shower either.
Click to expand...
Click to collapse
2. This is a better fix proposed by me, but it requires Root and Xposed:
Download Wakelock Terminator
Filter for ONLY the SystemUpdateService wakelock for Play Services
Click to expand...
Click to collapse
3. IDEAL FIX:
Since CM11 has already had commits merged to address this Play Services 7.x issue, (see commits http://review.cyanogenmod.org/#/c/91881/ and http://review.cyanogenmod.org/#/c/91882/), the best Corrective and Preventative Action that you can take is to build a fresh copy of CM11. Unfortunately, we haven't had nightly builds since January 5th, so if someone could undertake that task, it would be much appreciated.
CM12 has already implemented the necessary commits as well (see commits http://review.cyanogenmod.org/#/c/91021/ and http://review.cyanogenmod.org/#/c/91579/), so an option if you're on CM12 nightlies is to move to something newer than the March 20th nightlies.
Click to expand...
Click to collapse
I'm using a Pixel, still on Android 9, and my orientation sensor (and accelerometer) have suddenly stopped working. However, it appears that it's a software issue as the auto-rotation still works when in Safe Mode. I've uninstalled every app that's been updated in the past two days (roughly when I think this problem began) but it's still a no-go. I've also installed a sensor test app and I find the sensors do work initially on boot, but freeze after 5 seconds or so.
Any ideas of how I might fix this?
Clear system cache.
You update, install or uninstall any apps recently?
I tried clearing the cache but it didn't change anything. I also uninstalled all the apps that had recently updated, restarting the phone each time, but the sensor is still frozen unfortunately.
ppuzzlerr said:
I tried clearing the cache but it didn't change anything. I also uninstalled all the apps that had recently updated, restarting the phone each time, but the sensor is still frozen unfortunately.
Click to expand...
Click to collapse
Factory reset time...
I have the same problem also with Pixel 1 and it happened on the same day (Oct 20)! The difference is I'm on Android 10.
After factory reset and backup restore it works.
After updating all apps, it still works.
After restart once all apps are updated... No work.
R
BHZero said:
I have the same problem also with Pixel 1 and it happened on the same day (Oct 20)! The difference is I'm on Android 10.
After factory reset and backup restore it works.
After updating all apps, it still works.
After restart once all apps are updated... No work.
Click to expand...
Click to collapse
Roll back to factory settings, one by one and find the culprit(s). Sounds like a rogue 3rd party app.
Once I have a device running well I almost never update anything. I'll run on the factory loaded versions for years many times. Result, no issues.
blackhawk said:
R
Roll back to factory settings, one by one and find the culprit(s). Sounds like a rogue 3rd party app.
Once I have a device running well I almost never update anything. I'll run on the factory loaded versions for years many times. Result, no issues.
Click to expand...
Click to collapse
Thanks for the help! How do I do this?
The return to factory settings is in the app under settings.
You can try uninstalling it otherwise.
I don't see that option all the time and you may have to hit uninstall for it to appear.
A forced stop might be enough for troubleshooting.
Typically I use my package disabler for things like this.
So I've done a factory reset with no restore (to keep it clean). Updated every app individually and restarted the device each time.
Updated GOOGLE MAPS. Rebooted.
Presto! All sensors are now locking up and battery starts burning away.
Disabled Google Maps, cleared cache + data, and rebooted. Problem did NOT go away. Now I'm doing one more (hopefully last) restore and will disable Google Maps right away.
Wow... did not expect it to be Maps...
BHZero said:
So I've done a factory reset with no restore (to keep it clean). Updated every app individually and restarted the device each time.
Updated GOOGLE MAPS. Rebooted.
Presto! All sensors are now locking up and battery starts burning away.
Disabled Google Maps, cleared cache + data, and rebooted. Problem did NOT go away. Now I'm doing one more (hopefully last) restore and will disable Google Maps right away.
Wow... did not expect it to be Maps...
Click to expand...
Click to collapse
I'm not, Gmaps updates are a back street abortion.
So it was the update that trashed it?
I always keep gmail and maps on the factory load version. Invariably updates make them less user friendly on a Samsung
I set Playstore settings for auto updates by wifi only.
I always keep wifi disabled, effectively preventing any auto updating. I also firewall block and disable Playstore unless I need it. It's a background pocket hog.
Updates generally cause more harm than good if the app is already running well...
I have the same issue, and after guessing which app was causing the problem I found out it's the Google app. I disabled it and all the sensors started working back and also automatic brightness. Also I tried leaving the beta updates of the Google app and whenever the Google app is active the sensors stops working. Probably Google trying to kill the pixel 1 or a new function conflicting with the sensors
Oh my god! I have the same issue! Stock Android 10.
Sensors work fine on Safe Mode, but on normal mode they sometimes don't work.
Same problem here, since a couple of days ago, some sensors (gyro, light, accelerometer, compas) stop working after a couple of seconds after reboot. I factory reset my pixel, I tried uninstalling GMaps, I tried deactivating Wifi and Bluetooth,... but nothing is working.
Proximity sensor still work though.
gmsalomao2 said:
Oh my god! I have the same issue! Stock Android 10.
Sensors work fine on Safe Mode, but on normal mode they sometimes don't work.
Click to expand...
Click to collapse
Have you tried disabling Google app as mentioned by cristejeda33 above?
I have the same issues, it happens when one or more apps get updated, don't now which one is causing it exactly, but the issue goes away after the next update, and comes back at the next update and so on ..., features like, adaptive brightness, tap to wake, lift to wake, display rotation os and in camera, youtube video rotation....... stopped working and the battery is draining a lot faster. thinking of getting rid of the good old pixel ..
blackhawk said:
Have you tried disabling Google app as mentioned by cristejeda33 above?
Click to expand...
Click to collapse
I stopped the services from the Google app and the sensors started working. And kept on working for some time after that. They keep stopping and coming back.
gmsalomao2 said:
I stopped the services from the Google app and the sensors started working. And kept on working for some time after that. They keep stopping and coming back.
Click to expand...
Click to collapse
Try disabling Google play Services... just a wild guess.
It's a dependency or a parent app of Google App that's maybe causing the trouble. These can be hard to ferret out... play with it.
You could just go shotgun and revert all Google apps to factory load version -if- it wasn't a system wide firmware update that triggered it.
I've experienced this too many times, updates break things.
On my N10+ I lock down all updates, especially firmware. I'm rarely updated anything because it causes trouble. Result is a very fast and stable operating platform with minimum maintenance required. When there is an issue it's much easier to track down as the system is a known and familiar quantity. My current load is over a year and a half old... still running strong.
Wife and I are using OG Pixels and a couple of weeks ago we both noticed massive battery degradation. Then we both realized that auto rotate is extremely slow as are a bunch of sensors. Skymap doesn't track anymore. Both our phones also get extremely hot.
Google brought us here and we see that stopping the Google app makes the sensors work normally again. Lots of issues being reported in the playstore for this app also. Would love to hear if anyone has made any headway working around this or are we screwed until an update comes out?
What's the best way we can report this to Google publicly? And put the link here
All accelerometer, compass, gyroscope and proximity sensors turned off a few days ago on my og pixel and after disabling the google app all the sensors are working again.
I had a look on the play store and the last update for the google app was on the 21st October, which is exactly when it broke.
I disabled google maps first, then the google app, then sensors worked, so i re-enabled the maps app, I then cleared the cache on the google app and re-enabled that too, and all is still working.
Thank you very, very much for finding the cause of this, I was about to factory reset the phone and then have to reload everything which may or may not have worked anyway. Your efforts are much appreciated, long may your technology function correctly.