Anyone else getting this or know how to fix it?
Running aaronpoweruser's cm10
Sent from my Nexus 7 using Tapatalk 2
I get this as well and have been for a while it seems.
EDIT:
Ups, I get it for my Galaxy Nexus.
I'm having the same wakelock issue on my xoom. Seems that AudioOut_2 is holding partial wakelock ~20% of the time. Someone on google+ said they thought it was related to the clicking sounds with the keyboard and screen on/off, but that doesn't seem to make a whole lot of sense to me. Have you found anything else useful?
On my galaxy nexus (also running jelly bean) the time AudioOut_2 occupies is insignificant
I experienced this last week for my N7 and couldn't find any useful post regarding the issue. It was training my battery pretty fast and I find it running for hours often under BetterBattery. It's definitely not the clicking sound as I've disabled all keyboard and screen touch sound since day 1.
After couple of days playing around I was able to find the problem is caused by the game GTA3. When I exit the game, I didn't close it completely and it's still running in the background. As soon as I end the game process, the AudioOut_2 stopped running. It since the AudioOut_2 is associated with games. I notice this process shows up when running numerous games but so far GTA3 is the only one that kept this process running if not exiting completely.
Hope this helps.
I've been getting this on several different ROMs and still haven't figured it out. Not much about it on Google. I have it even when I don't have games installed so not sure what it could be.
i dont have GTA 3 and i still get the wakelocks. on stock and modaco roms. =\ also have keyboard on silent as well as screen off and touch sounds.
anyone got a clue?
well, not necessarily caused by gta. it could be any game or app. my dungeon hunter 3 also triggers audioout_2 process, but when i go back to home screen the process wont be running unlike gta3.
Hello, I have a Galaxy Nexus with a great (5,6%) percentage of AudioOut_2 wakelocks. Never installed GTA3.
I flashed faux kernel this morning and the wakelock is completely gone. Been about 7 hours with no issue
Sent from my Nexus 7 using XDA Premium HD app
Any app that uses audio can cause this. Play movie didn't close properly and caused audio out wake lock for me as well as leaving mob atbat runnng . as well as some games. You need to figure out what app didn't close properly that is leaving audio running
Sent from my Nexus 7 using xda app-developers app
I have this as #1 on my N7 as well, no games or keyboard sounds. I wish bbs listed the app which was responsible.
this is not related with any application AudioOut_2 itself, and it starts only if you open data connection or wifi and never stop again if you not restart the phone without internet. i use nexus s and i have it too.
After doing a bit of investigation, I'm pretty sure this wakelock is lingering after using either MX Player or BS Player. I haven't used either on my current charge and the battery is still at 75% after 1d 20h, with just over 1 hr screen time. The AudioOut_2 wakelock time is only 46 seconds. With media player usage and similar screen on time the wakelock time would be over 30 minutes and the battery would be below 50%.
I don't know enough about how all this works to tell whether it's a problem with the apps themselves or the Android media server. It would be great to get to the bottom of this as I really think it's contributing a great deal to my battery use.
sladflob said:
After doing a bit of investigation, I'm pretty sure this wakelock is lingering after using either MX Player or BS Player. I haven't used either on my current charge and the battery is still at 75% after 1d 20h, with just over 1 hr screen time. The AudioOut_2 wakelock time is only 46 seconds. With media player usage and similar screen on time the wakelock time would be over 30 minutes and the battery would be below 50%.
I don't know enough about how all this works to tell whether it's a problem with the apps themselves or the Android media server. It would be great to get to the bottom of this as I really think it's contributing a great deal to my battery use.
Click to expand...
Click to collapse
Had this been confirmed?
Also have it here, about 25 to 40% wakelock.
After cancelling all hiptick sounds and rebooting this seems to be all over for me.
Hope it's still relevent for someone.
16 hours uptime, 2 percent / 20 minutes wakelock audioout_2 ... Feck! I know thats not toooo much but I still hate when this stuff isnt linked to an appropriate app ...
after doing some investigation with betterbatterystats, i kept getting the same wakelocks. I pretty much was able to pin point it by seeing what apps were generally running in the background, then disabling 1 app at a time until I found what was causing mine.
sirgoob said:
after doing some investigation with betterbatterystats, i kept getting the same wakelocks. I pretty much was able to pin point it by seeing what apps were generally running in the background, then disabling 1 app at a time until I found what was causing mine.
Click to expand...
Click to collapse
which was...?
mine was dice with buddies, every time a notification came in it would cause a wakelock. i turned off all sound notifications and audioout2 went from 10% down to 2%
Related
This mystery process called "sensorserver_ya" is killing my battery, between 50% and 150% of what my screen is using (which is, of course, a lot).
Anyone have any idea what it is? Tried googling things for awhile and found nothing other than people listing their battery processes, and a couple other people asking what it is also...
TimeWalker pedometer widget was the culprit in my case, see details near bottom of thread.
Shane112358 said:
This mystery process called "sensorserver_ya" is killing my battery, between 50% and 150% of what my screen is using (which is, of course, a lot).
Anyone have any idea what it is? Tried googling things for awhile and found nothing other than people listing their battery processes, and a couple other people asking what it is also...
Click to expand...
Click to collapse
How did you find this info?
icantdrawanime said:
How did you find this info?
Click to expand...
Click to collapse
By going to the stock battery statistics in the settings, about phone.
Very Strange... I have no clue what that is. Sorry
It doesn't show up in my task manager, or as an app in Titanium or anywhere else.
I have quite a few widgets installed (Weather Channel, Buzz Box, Agenda Widget, Battery Widget, Facebook, Pandora, TimeWalker, Twitter) as well as Tasker running. Could it be one of those? I might try removing them one by one to see if it goes away.
Do you have any games installed? I found this on some Swedish site. They were talking about the same process.
Originally Posted by Double Barrel
Now, added that the phone has been on the table all night. Had an app called Labyrinth started. Could be it. Now I'm down to 13%.
Labyrinth Games that are heavy users of the sensors so it is not surprising.
Click to expand...
Click to collapse
Pops_G said:
Do you have any games installed? I found this on some Swedish site. They were talking about the same process.
Click to expand...
Click to collapse
No, although one of my tasker profiles is set to turn the alarm off if I put the phone face down at night. I might try deactivating that and seeing what happens.
I disabled the Tasker profiles and let the phone sit for almost 2 hours.
Sensorserver_ya :40%
Cell standby: 22%
Phone idle: 16%
Bluetooth: 9%
Display: 7%
Android OS: 3%
WiFi: 3%
Android System: 2%
TimeWalker (pedometer widget): 2%
What. The. Cuss. ???
I have the same thing but it only takes 3-4%
Sent from my SPH-D700 using XDA App
same thing here, used 27% of battery in few hours and 1hr 18m CPU usage time.
Galaxy S Vibrant user
sparkling said:
same thing here, used 27% of battery in few hours and 1hr 18m CPU usage time.
Galaxy S Vibrant user
Click to expand...
Click to collapse
What widgets are you running?
Sensorly app?
Weird, I dont even have that process in mine....
I disabled the TimeWalker widget (pedometer) and the process hasn't appeared yet. I think this may have fixed it. Anyone else?
At least in my case, the TimeWalker widget was the culprit. "Sensorserver_ya" didn't show up for days. This morning, I reactivated it and all of a sudden it showed up again, shooting up to 9% of battery usage (and draining 2% of my total battery) in less than 10 minutes. The widget itself took another 1/3 of that.
Too bad, I had a pedometer built into my Sony Ericsson w580i and it was awesome. Battery rocked. Not sure what the problem is here.
I see that process on occasion and I've never run the widget that you are referring to.
It is probably triggered by running a compass or other app that uses the position sensors.
Sent from Samsung Vibrant
Since not everybody is seeing this power drain, I think it is not likely to be the system setting to check orientation and adjust the screen from portrait to landscape automatically, although that seems a likely suspect to me. I also suspect a screen management tool called Screebl. I have disabled Screebl now to see if that makes a difference. (Even though I had Screebl configured to not work when power is applied, my system didn't have any period of Suspend through the night last night, despite being plugged in for about half the night.)
Shane112358 said:
This mystery process called "sensorserver_ya" is killing my battery, between 50% and 150% of what my screen is using (which is, of course, a lot).
Anyone have any idea what it is? Tried googling things for awhile and found nothing other than people listing their battery processes, and a couple other people asking what it is also...
TimeWalker pedometer widget was the culprit in my case, see details near bottom of thread.
Click to expand...
Click to collapse
***************
I observed that besides the mystery process sensorserver_ya and the shortened battery life, if I watched the phone go into power saver mode with no apps running it would dim then kill my display as expected, but then after 3 to 5 seconds it would light it up again as if I had pressed the activate button.
I tried uninstalling two apps ACIDR and PowerAmp. This behavior stopped after
that. I reinstalled PowerAmp and the behavior did not recur. ACIDR had been on my GalaxyS for some time PowerAmp was recently added. Both were up to date.
I know, old thread, but...
Just to add to the possible causes for others, I found that CardioTrainer had frozen up while trying to post my workout to Facebook. Several hours later I saw the sensorserver process sucking my battery at 14% of total usage according to "About Phone". When this thread mentioned pedometer and labyrinth I checked and found that CardioTrainer was hung. It didn't show in the normal "Active Applications" but TitaniumBackup told me it was running.
Hope that helps anyone else with the problem.
Seeing that process means that you have something that is making use of the accelerometer on a frequent basis. You should figure out which of your apps are using the accelerometer and either uninstall or make sure they remain closed.
Making use of the accelerometer in a way that is using it at nearly all times is the fastest way to burn through your battery.
Well I've solved my issues with battery life on the SII. It may not be a solution for everyone, but for me Tweetdeck was the issue:
http://www.smartphonegurus.com/forums/topic/13669-samsung-galaxy-sii-battery-life-issues-solved/
Oh well, you should have posted in another battery thread instead of starting a new one. It all comes down to certain apps, besides all the android system apps that run in the background. I had problems with Phantom Music Control, which drained my battery like crazy when being in stand-by.
I set Tweetdeck to manual sync a while ago when my battery issues began. I was barely getting 8 hours with almost no use. The culprit in my case turned out to be Qik. I had to download OS Monitor from the market and really watch the activity. Qik was hitting the CPU regularly, despite the fact that it wasn't actually running. I think it must check for new video mail or something in the background.
Anyway, since removing Qik, I'm back to comfortably getting 15 hours with heavy use and over 24 hours with light use. Go figure. I was about ready to switch phones again. It just goes to show that all it takes is one app to ruin your day.
So, yesterday I noticed a sudden battery drain on my nexus 4. After checking battery it showed that AndroidOS takes over about 50% of the battery usage. It also showed that time awake was pretty much the same as the amount of time since I unplugged the phone, even though I kept my phone in sleep mode for the most of the day. After some research I downloaded better battery stats and it showed that from the moment I turn the screen off a process called suspend_backoff runs pretty much the entire time. Eventually I got it down to wifi. If I turn off wifi there are no processes running after the screen is turned off (or if there are they are 30 seconds tops), but the moment I turn wifi on suspend_backoff runs pretty much the entire time screen is off. I tried removing all of my apps, as well as doing factory reset but nothing helps. The moment I turn wifi ON this suspend_backoff consumes pretty much all the time during screen off period. Is anyone experiencing anything like this ? I have 4.2.2 on the phone and I havent' seen this extreme drain until just yesterday.
I experience the samething. Android OS would drain as much as the screen time.
I narrowed it down to the suspend_backoff. But the weird thing is that when i'm at home on my home wifi, suspend_backoff doesn't seem to drain anything at all. But when I'm at school, suspend_backoff kicks in.
Anyone help?
hihihoho said:
I experience the samething. Android OS would drain as much as the screen time.
I narrowed it down to the suspend_backoff. But the weird thing is that when i'm at home on my home wifi, suspend_backoff doesn't seem to drain anything at all. But when I'm at school, suspend_backoff kicks in.
Anyone help?
Click to expand...
Click to collapse
how did you narrow it down? Im having the same problem!
This is caused by a kernel wakelock. A bad mobile connection make battery drain worse... using WLAN nearly fixes this problem.
Thought this problem has got fixed in 4.2.2, at least battery life got improved and the wakelock reduced.
If it is appearing since yesterday, it is triggered by a app often waking the phone up using mobile data (that's why fixed with WLAN) and prevent the phone from getting into deep sleep as fast as it should.
hope i could help.
I use Greenify to hibernate every single user installed apps, then I release them one by one to see which one cause suspend backoff. But suspend backoff still occurs. So I think it's the kernel itself.
AW: Battery drain on nexus 4 since yesterday
hihihoho said:
I use Greenify to hibernate every single user installed apps, then I release them one by one to see which one cause suspend backoff. But suspend backoff still occurs. So I think it's the kernel itself.
Click to expand...
Click to collapse
as i said before, an app needs data, so it starts callung the kernel wakelock... this one causes tje drain, not the app itself
Sent from my Nexus 7 using xda app-developers app
hihihoho said:
I use Greenify to hibernate every single user installed apps, then I release them one by one to see which one cause suspend backoff. But suspend backoff still occurs. So I think it's the kernel itself.
Click to expand...
Click to collapse
Yeah, definitely not user apps. I did full reset on the phone to factory settings, no user apps. Even tried disabling Google Play and Google store after the reset. Still the same. The only thing that gets rid of it is disabling WiFi.
hihihoho said:
I experience the samething. Android OS would drain as much as the screen time.
I narrowed it down to the suspend_backoff. But the weird thing is that when i'm at home on my home wifi, suspend_backoff doesn't seem to drain anything at all. But when I'm at school, suspend_backoff kicks in.
Anyone help?
Click to expand...
Click to collapse
When did you start noticing this ? Has it been for a while or just recently ? I first noticed it yesterday (had the phone for a bit over a month now, didn't see any issues until just yesterday)
hihihoho said:
I use Greenify to hibernate every single user installed apps, then I release them one by one to see which one cause suspend backoff. But suspend backoff still occurs. So I think it's the kernel itself.
Click to expand...
Click to collapse
What is the difference between greenify and limit background apps in developers options?
AW: Battery drain on nexus 4 since yesterday
stop discussing, use search instead... http://forum.xda-developers.com/showthread.php?t=1999368
like i told you 3times now.... it's the wakelock
Sent from my Nexus 7 using xda app-developers app
indoh said:
stop discussing, use search instead... http://forum.xda-developers.com/showthread.php?t=1999368
like i told you 3times now.... it's the wakelock
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah, it's clear that it's the wakelock. What's not clear is why. Also it's not the msm_hsic_host that the forum link you sent refers to. I don't have a problem with msm_hsic, that one barely takes any time during the day (maybe 30 seconds during several hours of standby). The wakelock causing this particular issue is "suspend_backoff" wakelock which supposedly happens when there is a sequence of sleep/wake calls too close together so the system decides to keep it awake. I was unable to find what exactly is causing the issue, even after restoring to the factory settings I kept seeing the same problem.
Anyway, I was able to "resolve" it by installing JuiceGuard app and setting it so it disables wifi when the screen is off. wakelock is gone now and my battery usage is back to normal.
I only get the suspend backoff wake lock when I'm connected to the university Wifi. When I'm at home, everything is fine, no suspend backoff. So my guess is that the Wifi encryption at university is different and causing a succession of close "awake" and cause wake lock.
I did factory reset like 3 times and it still there.
I'll try disable Wifi on Monday and see how it goes.
Same here, when wifi disabled the wakelock doesn't occur.
I have tried almost all of the kernels and non of them seem to help.
hihihoho said:
I only get the suspend backoff wake lock when I'm connected to the university Wifi. When I'm at home, everything is fine, no suspend backoff. So my guess is that the Wifi encryption at university is different and causing a succession of close "awake" and cause wake lock.
I did factory reset like 3 times and it still there.
I'll try disable Wifi on Monday and see how it goes.
Click to expand...
Click to collapse
Interesting... Maybe it is encryption. One thing with my Wifi is that it doesn't use password, but MAC list instead. It may indeed be an issue with different wifi encryption types.
OP do you have maps 6.14 on your phone? Mine kept switching on location reporting for a while and it woke my phone 344 times last night. I've been struggling with the same wake lock issues. I'm going to recharge (again) with maps disabled and see if that helps.
Sent from my Nexus 4 using Tapatalk 2
Check your Google account sync settings... In settings
The clowns may have left you a lovely gift there without telling you or asking any kind of permission.
The latest Maps was giving me horrible battery drain, on WiFi. I'd sleep for six hours with a fully charged phone and wake up with 10% left. it even enabled itself when. I disabled it in settings. I converted it to a user app by moving it to /data/app and greenified it. Seemed to have solved all of my issues with the suspend back off wake lock.
Download greenify
Sent from my Nexus 7 using Tapatalk 2
For some weird reason, I was also having serious battery drain suddenly since yesterday.
Turned out it was maps, and disabling Google network locations hugely increased battery life
Sent from my Nexus 4
Hey guys, I'm having some wakelock issues.
I run greenify on draining apps and have some unused apps/processes frozen, but still have these issues.
So my questions are:
1) Could my battery drain be wifi/3g related? sometime it seems so, sometimes not.
2) Are these immense amounts of wakelocks normal? Audiomix could possibly be because of broken mp3 songs, have them already checked but not deleted. but i didn't even listen to music on this battery cycle.
3) WLD seems to lack some processes. What could cause it to not display the missing ones?
I highly doubt you have an issue here. Your battery doesn't look to be draining much at all. You're at 1 day and 3 hours according to BBS, 1 day and 18 hours according to your phone, and your highest wake lock is less than 30 minutes. That looks like Media, probably from music. That's pretty damn good for 27 hours or more I'd say. There's this misconception that all wake locks are bad. That's not the case. Wake locks are going to happen. Its unavoidable. If you had a wake lock that was at 3 hours or more I'd worry. But you don't, so I don't think you have an issue. Just enjoy your phone.
Never said, that i think they are bad
I just wondered, because 3k+ is quite a high number and i didn't find something i could compare it too. So i didnt know if it was normal or not.
Battery life is ok, but not that great. On the posted cycle, screen on time was just around 2-3 hours. Im getting some drains here and there and havent been able to figure it out yet.
But thanks mate
Hi guys,
I have been having an issue with my Motorola X Play (UK Single Sim) I have only owned it for a few months from new.... The battery is draining fast and I can see in the battery stats that it's not sleeping, otherwise the battery usage page shows nothing of interest, apart from perhaps Mobile Standby which is quite high, above the screen but the signal bar is all green...
I rooted my phone to better find out what was causing these issues, otherwise stock Marshmallow. Unfortunately Motorola now are not interested as they say my phone is rooted and now has no warranty - useless idiots!
Using GS Sam battery monitor (rooted) I can see that the following is keeping the phone awake, no other app is.
48.3% of battery consumed by Kernel (Android OS)
Keep awake over 2 hours
CPU usage 59m 53s
Number of Wake Locks: 1
Byes sent: 246.21KB
Bytes Received: 5.70MB
App UID: 0
Wakelock Detail:
Google_C2DM 0.0s (1)
I have tried safe mode but it appears to be the same, I have hardly any apps installed apart from Facebook and Facebook messenger and I have even tried it without them...
I have tried turning off/on WiFi / Location / GPS is now disabled. WiFi Scanning is off. Restarts make no difference... I have even done a factory reset about a month ago.
Any ideas, this phone is having the same battery life or less than my Nexus 5 which had a much smaller battery...
Many thanks
here's a way to avoid it http://forum.xda-developers.com/galaxy-s2/help/google-c2dm-checkin-services-t1321520
i'll update if i find anything else.
don't tell them your device is rooted. if you go to service center just re-lock the bootloader and its back to normal.[it won't get your warranty back but they don't check that much]
can you post a screenshot of gs sam.
1 - Install BetterBatteryStats (BBS) - this will give you detailed information on what is draining your battery. Get it from XDA v2.2.0.0B6 - this gives you the detailed breakdown in the UI that you are after, the google play version doesn't do it in the UI (older version).
Get baseline results (charge it full, don't touch it for 5-6 hours) I like to do this while sleeping.
2 - Install Greenify (you don't need the Xposed module if you don't want to fiddle with that yet, alto I highly recommend it) set the working mode to root. If applications are still not sleeping, add the widget and force sleep everything before you turn off your screen
Get BBS results (do the 5-6 hours while sleeping) - improved?
3 - Install Naptime from the google play store (by Fransico Franco)
Get BBS results - improved?
Getting anal about battery usage?
4- Read up on Amplify - this yielded even more results for me. But this can take a bit of work to get right. There's a lot of great threads on XDA for setting this up.
5 -Smart network - allows you to control data, networks, wifi, bluetooh, nfc, gps on/off with a ton of great features for auto. management.
I have all the above and yield a 0.4%/hr drain on stand by (see signature for phone build).
Amplify is a god sent app. It has been 4 hours now, and I have been using whatsapp on and off (about 20 seconds each time) and I still have 97% left in the tank.
LaurenceGough said:
Hi guys,
I have been having an issue with my Motorola X Play (UK Single Sim) I have only owned it for a few months from new.... The battery is draining fast and I can see in the battery stats that it's not sleeping, otherwise the battery usage page shows nothing of interest, apart from perhaps Mobile Standby which is quite high, above the screen but the signal bar is all green...
I rooted my phone to better find out what was causing these issues, otherwise stock Marshmallow. Unfortunately Motorola now are not interested as they say my phone is rooted and now has no warranty - useless idiots!
Using GS Sam battery monitor (rooted) I can see that the following is keeping the phone awake, no other app is.
48.3% of battery consumed by Kernel (Android OS)
Keep awake over 2 hours
CPU usage 59m 53s
Number of Wake Locks: 1
Byes sent: 246.21KB
Bytes Received: 5.70MB
App UID: 0
Wakelock Detail:
Google_C2DM 0.0s (1)
I have tried safe mode but it appears to be the same, I have hardly any apps installed apart from Facebook and Facebook messenger and I have even tried it without them...
I have tried turning off/on WiFi / Location / GPS is now disabled. WiFi Scanning is off. Restarts make no difference... I have even done a factory reset about a month ago.
Any ideas, this phone is having the same battery life or less than my Nexus 5 which had a much smaller battery...
Many thanks
Click to expand...
Click to collapse
Facebook app has been known to cause serious battery drain in the past. Uninstall it and test again.
In 99% of the cases it is caused by an app. Try to find out which one is causing the drain.
Hi all,
Sorry for the delay and thanks for the replies. I performed a factory reset again, after clearing the cache etc, the same as I did last time. The only difference is I then installed Android 6.0.1
The battery drain has now gone. I didn't perform a restore of apps etc, and the only apps I have installed so far in addition have been Facebook and Facebook messenger but I have found these have had no effect at all on the battery drain. I haven't even updated the stock apps (apart from the security ones).
I now get two days of use easy. It also seems to be running slightly faster. I will update apps one by one, over the course of a few days to make sure nothing causes it again...
http://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
I use this guide, works really great to limit wake locks.
And I don't use Fb app but use the browser instead, battery lasts easily two days of "heavy" usage !
I found the problem, or at least a major bug. Whenever you cast to Google Chromecast Audio and then stop casting completely there is a massive wakelock until you next restart the phone. My phone was awake all night and down to 20% battery life. Android OS takes a massive portion of the battery life and under keep awake stats it's 9 hours +. It seems that when it says disconnected it is not. A major bug! I'll try and report it using Google's bug reporter...
LaurenceGough said:
I found the problem, or at least a major bug. Whenever you cast to Google Chromecast Audio and then stop casting completely there is a massive wakelock until you next restart the phone. My phone was awake all night and down to 20% battery life. Android OS takes a massive portion of the battery life and under keep awake stats it's 9 hours +. It seems that when it says disconnected it is not. A major bug! I'll try and report it using Google's bug reporter...
Click to expand...
Click to collapse
not even Doze could kill it? perhaps you could try Servicely and see if it could stop the thing from running.
pijes said:
not even Doze could kill it? perhaps you could try Servicely and see if it could stop the thing from running.
Click to expand...
Click to collapse
Nope, Doze had no affect at all but it should be as it was sitting stationary overnight - normally the drain overnight is a few percent at the most, last night it was around 65% and I was left with 20% in the morning and this was I think the first time I had used Google Chromecast Audio since the factory reset with great battery life up to last night... I could try Servicely but I am not sure on the service to kill and I'd like to keep it 100% stock for now so I can help out Google to fix the bug (or Motorola if they bother)... What a pain as I just bought 4x Google Chromecast Audios!!
I have reported it here in the Android bug tracker, feel free to comment / star the issue to bring it to Google's attention.
https://code.google.com/p/android/issues/detail?id=208324
However I am not sure if this is a Motorola Issue or a Google Marshmallow / Chromecast issue?? Motorola support have been very unhelpful so no luck if that is the case...
If anyone else with Chromecast Audio could confirm the bug that would be great.
Thanks
Laurence
There's a post on reddit about battery drain with chromecast audio about a year ago, not sure if it's the same issue though.
Sent from my XT1562 using XDA-Developers mobile app
https://forum.xda-developers.com/general/general/fix-fix-systemupdateservice-wakelock-t3060548
maybe this help, on moto g this helped
apart from greenify and naptime...i dont think we have something like amplify yet for nougat devices, also with the governor scripts they are providing better results now
yep
miss5tability said:
i dont have root etc but on my just buy moto x play with stock android 6 i dont have 2 sensors working and deep sleep is gone so battery drain... even after cler cache. reset etc, this phone is pure ****
Click to expand...
Click to collapse
If you bought it brand new just go back to the shop for replacement
pijes said:
If you bought it brand new just go back to the shop for replacement
Click to expand...
Click to collapse
yep