Related
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 had this on 4.4.2 but 4.4.3 fixed it. I'm on 4.4.4 now and have been since it came out, but all of a sudden last week, mm-qcamera-daemon came back and I'm not alone.
With L just around the corner, I doubt there will be any fix for this from Google, so what's the best way of finding out which app is keeping this service alive?
P.S. I have neither Skype, Instagram, nor Snapchat installed - and never have done - so it's not them.
Did you have a camera app running in the background? ie. minimized it without swiping it away.
Nah, nothing like that. I'll even get it when I boot my phone, open no apps at all, and charge to 100% before unplugging from the charger - this action seems to be the cause of the daemon, like some of the other users on that issue report are saying. Never mind, I guess I'll just wait it out until L.
I have never had this problem on my nexus 5 until today (I bought the Nexus 5 on day one)!
This process is draining all my battery!!
The only app I installed in the past week is "Google Opinion Rewards" which was installed 6 hours ago.
Please help if you find a solution
UPDATE 1: I just noticed, via CPU-Z, that all 4 cores are continuously active at high frequency and the phone is overheating
UPDATE 2: Problem is still there even after removing "Google Opinion Rewards"
Just reflash the stock firmware and see if it continues.
Best thing to do with any issue that a solution can't be found for easily. ?
skttrbrain said:
Nah, nothing like that. I'll even get it when I boot my phone, open no apps at all, and charge to 100% before unplugging from the charger - this action seems to be the cause of the daemon, like some of the other users on that issue report are saying. Never mind, I guess I'll just wait it out until L.
Click to expand...
Click to collapse
the camera daemon is supposed to appear. its not supposed to stay around, draining battery. especially at 100%, you will see it, as the phone uses it a little bit, and you havent used the phone at all. it will show up. the question is, if you dont use the camera at all, and it appears in your battery stats, after a full cycle of use, how much battery does it take? chances are that by the end of your battery cycle, it wont even be in your battery stats.
simms22 said:
the camera daemon is supposed to appear. its not supposed to stay around, draining battery. especially at 100%, you will see it, as the phone uses it a little bit, and you havent used the phone at all. it will show up. the question is, if you dont use the camera at all, and it appears in your battery stats, after a full cycle of use, how much battery does it take? chances are that by the end of your battery cycle, it wont even be in your battery stats.
Click to expand...
Click to collapse
I actually fixed it now by flashing the system image and restoring all my apps via Titanium Backup, but I swear I'd never even open Camera for it to occur, and I don't have any third party camera apps. It would constantly be active without opening any camera apps at all.
edit- also Google have restated that they're looking into this bug and have marked it urgent, so anyone else getting it - don't panic too much, it's most likely not a problem you've caused.
I suspect the Hangouts/Hangouts dialer. I updated the app few days ago (no other installs), today was the first time that I got this issue (got my Nexus in February). Also first time since updating I used the camera, followed by battery drain/ daemon/ "failed to connect camera" etc.
I think its because of android wear
With android wear u can access the camera, hence u will be seeing the camera drain for sure. i unpaired my watch for few days and i didnt have this problem till now
I had this problema today morning, my android version is 4.4.4, In my case I used yesterday the camera to attach a photo inside the facebook messenger, maybe this buggy app make this mess in my case.
I reboot and waiting for the results
Same here
Everything was ok from 4.4.2 till 4.4.4. But suddenly week ago discovered mm-qcamera-daemon issue, tried many things without success. I am using phone in safe mode (facepalm).
Waiting official Android L or fix from google.
I got the same issue now!
Started today, what the hell?
Some apps will keep the camera wakelocks going. Freeze anything that can possibly use the camera and see what happens.
Or just clean flash stock, and see if its OK. If so... Install a handful of apps per day.... Then if it goes nuts you know it's an app you've just installed.
https://code.google.com/p/android/issues/detail?id=70755#c171
I think i had this fixed. Ihave a rooted nexus 5 stock rom. Installed greenify, pirchased the donate version and had the camera app greenified. No more mm-qcamera-daemon showing up on my battery stats. No more "cannot connect to camera" issues. (So far it's been 2days without it.
camera block app
i see this issue occurs when i use skype or any camera related app in my grand 2 4.4.2 / only way i keep the issue at bay is use camera block app.. which i keep it turned on when i am not really using the camera.
this seem to keep this daemon under control and not drain my battery .
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.
Hi everyone,
My OnePlus 7 was perfectly fine even after updating to latest stable 10 other than the play store bug, I now have even more problems
1. Notifications - I don't get push notifications. Gmail and WhatsApp remain stuck unless I open them. I've disabled battery optimization for them both and have also disabled the deep sleep optimization to no avail. I keep missing calls and messages because I didn't open the app.
2. Poor battery - my battery keeps draining a lot. Just listening to Spotify at work I went through 40% battery in a few hours. I used to get 7-8 hours SoT now it's around 4 hours. I tried looking into apps to get some stats but all have bad latest reviews. I even went through my apps to see if there was something rogue or one that I installed and removed all unwanted apps but still the same.
3. Downloads (including Play store) - playstore won't download files or will stay stuck at 99/100%. The only way to get it to work is to either disable the Google app and reboot or turn off Bluetooth and then reboot. I rely on Bluetooth for my wristband and my earphones so that sucks. Google app is also useful and it doesn't make sense to disable it to get downloads. Even for normal downloads e.g. in gmail, attachments won't download and are at 0% constantly.
Any help around this would be appreciated. I just dropped from 53-51% while writing this thread (took 3-4 minutes).
Anyone else with similar problems or solutions? Thanks.
whisky_ said:
Hi everyone,
My OnePlus 7 was perfectly fine even after updating to latest stable 10 other than the play store bug, I now have even more problems
1. Notifications - I don't get push notifications. Gmail and WhatsApp remain stuck unless I open them. I've disabled battery optimization for them both and have also disabled the deep sleep optimization to no avail. I keep missing calls and messages because I didn't open the app.
2. Poor battery - my battery keeps draining a lot. Just listening to Spotify at work I went through 40% battery in a few hours. I used to get 7-8 hours SoT now it's around 4 hours. I tried looking into apps to get some stats but all have bad latest reviews. I even went through my apps to see if there was something rogue or one that I installed and removed all unwanted apps but still the same.
3. Downloads (including Play store) - playstore won't download files or will stay stuck at 99/100%. The only way to get it to work is to either disable the Google app and reboot or turn off Bluetooth and then reboot. I rely on Bluetooth for my wristband and my earphones so that sucks. Google app is also useful and it doesn't make sense to disable it to get downloads. Even for normal downloads e.g. in gmail, attachments won't download and are at 0% constantly.
Any help around this would be appreciated. I just dropped from 53-51% while writing this thread (took 3-4 minutes).
Anyone else with similar problems or solutions? Thanks.
Click to expand...
Click to collapse
Just to clear, this is the oneplus 7 PRO forum mate. You have the standard or the pro?
hallo dare said:
Just to clear, this is the oneplus 7 PRO forum mate. You have the standard or the pro?
Click to expand...
Click to collapse
Hey, it's the 7 Pro, 256GB Nebula Blue
Anyone with any suggestions on any of these problems?
whisky_ said:
Anyone with any suggestions on any of these problems?
Click to expand...
Click to collapse
Did you wipe the cache?
My unit is OP7 (not Pro), had similar problems, dreadful awful atrocious battery life.
Basically the latest Pie was great, why did I ever upgrade?
My tip for you: if you downgrade to Pie (as I did), do NOT do it via TWRP backup. This is what I did and ended up with a hard brick that took me all day to solve. There are threads about ways to downgrade, and TWRP is not the way to do it.
After all this mess, though, can't tell you how glad I am to be rid of Android 10 and back on Pie.
I don't have these issues being on OOS 10.0.1. Never did. Must be doing something wrong. Also, I've downgraded to Pie many times using TWRP. If you do it correctly, meaning use the proper downgrade zip provided by OnePlus, then you shouldn't have any issues downgrading to Pie.
TheKnux said:
I don't have these issues being on OOS 10.0.1. Never did. Must be doing something wrong. Also, I've downgraded to Pie many times using TWRP. If you do it correctly, meaning use the proper downgrade zip provided by OnePlus, then you shouldn't have any issues downgrading to Pie.
Click to expand...
Click to collapse
Great to hear. How do you do it correctly using TWRP?
Here's how to do it wrong (what I did): I just did a restore with TWRP, without looking at any downgrade zips. For anyone interested, what is that process please?
I've cleaned install and did a factory reset and the problems in Android 10 still exists. It's been more than a month and OnePlus hasn't even fixed it. It's great that OnePlus provides updates to the older devices(3/3T) but if it delays and slows down the update of the latest ones, then it's really bad. I shifted from an iPhone and that's the only thing I miss, the software updates and quick fixes with the updates.
nitishanand said:
I've cleaned install and did a factory reset and the problems in Android 10 still exists. It's been more than a month and OnePlus hasn't even fixed it. It's great that OnePlus provides updates to the older devices(3/3T) but if it delays and slows down the update of the latest ones, then it's really bad. I shifted from an iPhone and that's the only thing I miss, the software updates and quick fixes with the updates.
Click to expand...
Click to collapse
That's why I'm concerned about doing a clean install. I don't want to go through the trouble and have the same issues again.
Has anyone found a solution at all? I've tried installing xxx no limits via Magisk and I might have noticed a 5% improvement in battery life but overall experience is still terrible.
whisky_ said:
That's why I'm concerned about doing a clean install. I don't want to go through the trouble and have the same issues again.
Has anyone found a solution at all? I've tried installing xxx no limits via Magisk and I might have noticed a 5% improvement in battery life but overall experience is still terrible.
Click to expand...
Click to collapse
I'm using the latest xXx module and it's running great. I've heard WhatsApp drains huge battery on Android 10. Also I went back to Pie with a clean install, both A and B
Download unofficial TWRP for PIE by mauronofrio
- Reboot to TWRP
- Install Recovery Ramdisk for TWRP Pie
- Reboot recovery
- Flash Pie update
- Flash unofficial TWRP zip
- reboot to recovery
- Flash Pie update again
- Flash unofficial TWRP zip again
- reboot to recovery again
- Flash magisk if you like, but you can skip since your just going to update to Android 10
- Reboot to system
- Finish initial setup for Android Pie
- Go to TWRP again
- Install Recovery Ramdisk for TWRP Q A10
- Reboot recovery
- Flash Android 10 update
- Flash unofficial TWRP zip
- reboot to recovery
- Flash Android 10 update again
- Flash unofficial TWRP zip again
- reboot to recovery again
- Flash Magisk
- Reboot to system
You should have a very stable OOS 10 update.
whisky_ said:
Has anyone found a solution at all?
Click to expand...
Click to collapse
Can't tell you how happy I am to be back on Pie.
For me, Android 9 was a major upgrade from Android 10.
Battery drain at 0.3% per hour on the idle BBS test… Life is good.
Also realized that Greenify was causing some problems with fingerprint, uninstalled with no negative effect on battery.
im on 10.0.1 xxx rom on Smurf kernel with no issues turn deep sleep off, OnePlus ram boost also adaptive battery and it will stop shutting down playstore and developer setting keep mobile data active. i think it was ram boost doing it and my battery is way better on Android 10 xda devs are getting better with system on 10 smurf kernel is the best thats my battery running 40 min only 5% gone and using browser the whole time
ecompton59 said:
running 40 min only 5% gone and using browser the whole time
Click to expand...
Click to collapse
Are you sure that's a good?
Doesn't seem that spectacular to me. Of course it depends on what you're doing in the browser.
It would be interesting to have a less subjective test (a benchmark).
the benchmark on Smurf thread shows 500,000 its oc 850mhz like it was on 9 Android 11 is about to be out i hated 10 at first takes a second to get used to it
Hi , iam on Android 10 xXx with stock kernel, but I don't have any of your Problems. My Phone runs approximately 2,5 days without charging and normal using.
You can update your Phone to Android 10 and then make factory reset and try with stock settings. If you have again Problems, the Problem is maybe somewhere else ?
Just saw news blurb that Beta 5 ( with fixes ! ! ! ) is out next week.
You guys know how to fix the color scheme on my notification they appear inverted or will either be black with black text
Jed!Master said:
You guys know how to fix the color scheme on my notification they appear inverted or will either be black with black text
Click to expand...
Click to collapse
Edit: fixed by toggling on and off force dark mode in Dev settings
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.