[2013] Having a bit of an issue with "cell standby" battery drain
![[2013] Having a bit of an issue with "cell standby" battery drain](/api/ImgurImages?id=PIOkmVz.png)
Posted Mar 23, 2015, 10:44 PM UTC
4515
That's really odd. Post any issues/bugs you have here:http://forum.xda-developers.com/showthread.php?t=3059171
3
Will do! I just want to give it a full charge + reboot first and see if it persists.
1
careful, the guys here do not like us insinuating bad things about the soak test
2
Yeah it's like people signed a non-disclosure agreement..
1
Not everyone....
1
Same thing here. I have never got 102% but something like 75% happens a lot.
1
Disabling cell data when not using it helps a lot.
1
Shouldn't this be done automatically? If I'm using wifi, why is data on?
3
It should be, but it's not. That's 100% the issue with lollipop on the moto x right now.
5
Gotcha
1
I just remember to keep either wifi on or data on but never at the same time for now while using this build.
1
Well...at least we know its a bug and they have time to fix it before the initial release...hopefully.
1
How are you on lollipop?
1
It's a handover issue with Lollipop on the Moto X. It's supposed to be improved, for example Skype calls don't get interrupted when you switch from WiFi to Data by keeping Data on, but that's causing issues for the Moto X. All Lollipop ROMs for the Moto X have this issue. For now, just turn off Data when you're connected to WiFi and you'e good to go. It's a bit of a hassle, but it's the only way. Also, Lollipop tends to display battery usage inaccurately, so Cell Standby might not be the highest battery draining process, or at least not over 100% like in the screenshot.
The weird thing is that I do keep data off the vast majority of the time. On that screenshot, it had been ~34h since the last full charge (I charged it to 90% inbetween) and data was on for probably less than an hour. Cell standby usage just kept creeping up during the day even with data off.
I installed the Lollipop soak test when it popped up a week ago, but this issue only started this Sunday.