IssueTracker

Absolutely same thing, that occurs either on  5 (literally every version from preview to 5.1.1) and on 6.

So here are some observations:
each app, that uses internet, has high mobile radio active rate. If it is some sort of browser or maps, that doesn't use  internet all the time, MRA is not extremely high, it is just surprising (like you do 10 minutes of web-surfing with some pauses (open browser, reload page, close, wait, repeat) and you  expect MRA close to 10 minutes (actually close to ~page load/reload time), but you have something about 40 minutes). It is ok in comparison with Google Play Services with all build in stuff like back-up, sync, geo and so on which can easily have up to 10 hours of MRA for a day.

I have installed Android M factory image on my Nexus 5, do not activate any Now or Fit features (even Wear and my watches) and do some measurements.

Situation 1. Standing by on wi-fi with high signal range:
Average battery consumption: 1-2 percents per hour.
Situation 2. Absolutely the same situation with same chatter level on hangouts, but wi-fi is turned off:

[Comment deleted]

+1.  Same issue here.  can't get to my screenshots at the moment, but rest assured my 5X is having the EXACT same problem that's been documented for so long with the mobile radio wake times.  I think yestreday I had, for example, facebook and google play services apps both reporting over 90 minutes of Mobile Radio Active time, and Facebook only had 4mins of actual CPU usage (from the one time i used the app in the AM).

In other words, the problem persists in M.  I hope we hear of resoution soon, because I have another 13 days before i make the call on returning this 5X outright.

[Comment deleted]

I can confirm this.

I've made a couple of tests while my phone has been on stand-by, and after a while of it been idle I get a message in Whatsapp. Both tests show that If no apps have used the radio, I get pretty good stand-by drains (less than 1%/h), but as soon (or a few minutes later) after I get a message in Whatsapp, the drain goes up. The drain values or not always consistent, but the increase of the rate of consumption coincides with the arrival of the message and hence the activation of the radio. I'm using Battery Monitor Widget to register the usage every 5 minutes. Here are the screenshots, take a look at the times:

Also note that Whatsapp shows 32m and 14s of mobile radio active time, while the CPU in the foreground is only 2m and 53 (by the time I took this screenshot, I had been on WIFI for a While)

Hi,
Thank you for reporting this issue. We have passed this on to the development team and will update this issue with more information as it becomes available.

He're we are again...

One of the most important features of Marshmallow, as Google says, is battery life improvements... But the most important and guilty bug that causes battery drainage is still here. Incredible.

Please Google, solve this bug once and for all!!!!!!!!!!!!!!

Again it is considered as a small priority.... Still on kitkat, was hoping to finally update to something higher.

The issue happens in both Google and non-google apps, so the software bug is concerning. It's already caused me to RMA a device and is only going to cost Google more $$ until its addressed. Can we at least get acknowledgement if this is software or hardware?

I said it before and I say it again:

It's pathetic this issue gets ignored for 2 years.

Android lost me as a user. This bug has been around for so long, since lolipop, and was also spotted in android m preview, and was promised to be fixed. I'd like to check iphone or windows phone for my next device.

Here's chrome today using 1hr 40mins of mobile radio active time, even though Ive spent barely 20mins using the app.

Stupid move from Google.
Now i won't buy a chromecast and a Googlewear SmartWatch as my next smartphone won't be an Android device anymore... It is a chain reaction.

Apple....here i come!!!

@dnaga@googlr.com any updates on this? Can you confirm it's the same issue discussed extensively in defect 22287469 / issue 36907694 of the developers build? This is murdering my nexus experience and I'm considering returning my nexus 5x outright before my 11/15 deadline. Quite a shame.

I think someone from Google should clarify this issue with the community. Be open and transparent about the status of this long time battery drain issue (since the first version of Lollipop). This will help regain the faith of the Nexus or Android users.

I am a Nexus 6 owner and was once severely impacted by this issue in Lollipop. Since I upgraded to Marshmallow, this issue no longer happens any more. So I suppose Google has put some effort in fixing, just not good enough to fix it once and for all.

It´s the same than this two. All over again....
https://code.google.com/p/android/issues/detail?id=165558
https://code.google.com/p/android-developer-preview/issues/detail?id=2556

I really think this will never be solved....

I think you are right.
Google made some design decission in lollipop on which they can't seem to go back on.
The batterydrain is a fact of lollipop and now marshmallow.
And as long Google keep their mouth shut they are pushing away their customers.

Don't think i will advise Android to friends,  family and so on....

Here are stats from yesterday, where ib had almost 3 hours if screen time, yet it wasn't even close to the biggest battery consumer...

I don´t have battery drain using 6.0. Battery stats however are just wrong when i use mobile data. If i keep mobile data disabled(with or without wifi) the stats are nice and make sense with screen on top and the apps i actually used the most; if i turn on mobile data however, i get pretty much the same battery out of my phone but the stats are wrong, show google play services and third party apps i didn´t used with big numbers on mobile active counter despite them not consuming battery given my experience. So for me it´s not a drain, it´s useless battery stats since android tells me that some app consumed more battery than 3 hours of screen time on a single day, which is just not true. Some users are reporting battery drain, i don´t have any battery drain, i just have worthless battery stats if i use mobile data.

Mi wife's Nexus 5 with latest Marshmallow to date suffered from this bug on friday. Battery went to zero in almost two hours.
Google Play Services was the culprit this time.

Screenshots attached.

Seriously? The only reason I didn't buy an iPhone was because 6 was supposed to fix this bug. But it's clearly still here.  Goodye Android. Maybe one day you'll get some priorities.

#22,

From what I can tell, it's fixed.

LOL. One hour of Google Play is taking over twice the battery of the screen being on the same time. The second screen shot didn't upload...  

#23 If it was fixed by Google, it wouldnt be still labeled as assigned here, but as "future release" and the thread would close. So it just isn't.

Can we expect this to be fixed on any close release? This is making me think go to iOS.. and I really love Android. Please fix this asap.

Same issue for me. 2 hours of SOT full battery, because of mobile radio active (with different app in stats, but frequently "google play services" or Chrome)

Cmon Google, get your devs onto it as a priority! For now I'm moving to a different browser. Google Chrome will be disabled.

Same here. It's ridiculous how the battery is drained by this stupid service. We need a fix ASAP!!!

-> Priority-Small
Unbelievable. This is the most irritating bug since Lollipop. Maybe we all can downgrade to the best Android version ever!! -> KITKAT.

Really Google? I bought Android phone but gave it back to store. It drained whole battery in few hours. I'm going back to Apple. At least they treat customers more seriously. Android is a joke.

Well now you're just being ridiculous. I'd say apple does anything BUT great their customers seriously. That company has ripped off everyone they've crossed for the past decade+, and has been lying about their "innovations" since basically every iPhone post-3G. Get back to me about being treat seriously next time you pay less than $100 upcharge for 32GB additional flash memory...

/rantoff

I'm not noticing this bug in 6.0.1 (Nexus 5).

People mistake mobile radio uptime for unnecessary high power state.

Seriously, posting that you don't have this bug and that you *think* people mistake this bug for something else doesn't help at all.  Just be glad that you are able to use your phone away from WiFi.  

For me, I have nothing but minimal GApps installed and on 4G, my phone drains 2-3x faster than having the screen on while it sits in my pocket due to this mobile radio active bug.  This most definitely did not happen with KitKat on the same device.  Nor does it happen on my wife's KitKat phone.

@Garret
I guess you are not talking about google nexus ripping off money on extra 16 GB and maximum 32 GB forcing users to use "cloud" services. Well apple is evil, but at least their stuff usually works. More seriously doesn't mean serious. Another thing is vulnerability to stagefright 2.0 in even new phones (which is not exactly google's fault, but general problem in Android's architecture).

For the love of god Google, fix this fuking irritating bug. It's forcing me to stay on kitkat and i really want to move on to Marshmallow, knowing it's is just a flash away for my device, OnePlus One. This is a major bug and you guys have been acknowledging it as a small defect. Please give it a priority guys.

Google, you must give high priority for this bug because I'm having this issue since LP

I'm worried this bug isn't going to be fixed until they're no longer making updates for my phone. Flashing a ROM is always an option, but I shouldn't have to flash an old or custom OS so that my phone is usable away from Wi-Fi.

I love Android, but I will not recommend it to others until Google makes it a priority to fix bugs like this. This has been the single worst bug in the OS since 5.0, and it has received no attention from Google. Features bring in new users, but good software keeps existing users. If you don't address this, it's going to push existing users, like me, away.

It is insane that this problem still persists, it's ruining my experience since my phone got the upgrade to lollipop almost a year ago. I don't want to root my phone and install 3rd party modules to fix this, I have other things to do and other hobbies. I shouldn't have to constantly take care of my phone, it just should work. If the bug isn't fixed during M releases (which seems to be the case given its small priority) my next phone in fall 2016 will not be an android.

@berkano, actually there's no 3rd party module fix for this.

@rauldzma yes, there is. you can install it via Xposed, it´s called "MobileActiveRadioFix".

It´s available in xda forums.
I´m using it here for a while and it's ok in 5.0.2.

@sadd the last I read about that module, all it did was hide the stats from the battery report and not actually fix the drain.

#41 it doesn't fix the core issue behind the battery drain https://forums.oneplus.net/threads/mobile-radio-active-bug-fix.352434/#post-12901265 http://forum.xda-developers.com/xperia-zl/general/cm12-1-cell-standby-mobile-radio-active-t3188147 as #42 stated.

To be honest, since 6.0, I've not been bothered by this anymore.

Don't mistake active time for this bug.

In Lollipop, the radio was ins high power state for much longer than necessary, thus killing your battery.

In 6.0, Google stated to have solved the issue, in the last preview.

New n5x has this bug too. Google play services devour battery when mobile data is on. It's ridiculous Google hasn't fix this bug yet. I've been noticed it for a long time since lollipop update on my old nexus 4. Unfortunately, there's no way out without lose of usability.

I wonder if this will ever get fixed in a timely manner. I was forced to downgrade to kitkat on my OnePlus One to get by battery life back.

[Comment deleted]

I don't understand how Google is behaving like a complete brat about this entire bug. Let alone fixing it, they haven't spoken anything about it, or even the fact that they are up for fixing this. Its been more than a year since this bug is crippling all android devices. They are all for "new features" "new names" "new design" but FIRST MAKE THINGS WORK PROPERLY WHICH IS ALREADY THERE !!

I'm facing this on my n6p. The mobile radio active data keeps spiking up. Google should adress the public really soon. This is a nasty bug to live with. Even 6.0.1 doesn't solve it

Seeing this reported by people on the NEXUS SIX P, a GOOGLE DEVICE is bewildering to say the least.I'm glad more people are reporting on it from a wide array of devices. For a time I was thinking of selling my device because of this bug. Now I know for certain (after talking to a bunch of custom rom makers) that it's a really deep issue that needs Google's attention asap.

I can confirm its on every device I know of on Marshmallow - Nexus 5, Nexus 6 & OnePlus One. My sincere request is to have this bug fixed. Begin with changing the priority from "SMALL". Do you know why a lot of people haven't posted here claiming it to be a defect? Because if you ask people to say post here if you have "Ataxia telangiectasia", you will probably die seeing the notice board empty !! Got it .. More than majority of people don't understand its a bug because of lack of technical know how. For the ones who know, many have given up hope on Google to do anything about it and have started looking at alternate ways to solve it. Stop acting as BIG HEAD and giving a cold shoulder to something that is highly evident as a bug. Please do something - Give an update, engage testers/Devs and eventually resolve it. But you got to start somewhere don't you?

I honestly think google ignores this because they don't want people to realize that they could have a much better battery life. They let average users be content with batteries that are being drained twice as fast on mobile data. Thus forcing said users to buy new devices sooner in hopes of getting a device with better battery life.

Let's begin blaming ourselves. First for being a deliberate noob by not identifying the issue and cursing the phone, Android on whole, OEM, the handset, etc. Secondly giving up early so Google can have a free run. Look at the activity on this thread. People post once and forget forever. How many ever tried to follow up? I will follow up on it every week asking for update. If every poster here asks for a followup it should make some noise in the deaf ears of Google.

Seeing something that has made my phone go from 7-8 hour screen times to 3-4 hour screen times labeled as "priority small" makes me want to switch to Apple. At this point I don't even think google bothers reading half the issues here. I keep a hopeful eye on this thread but my hope is dwindling with every passing day. This has been going on since lollipop. We were promised a fix in Marshmellow. We were lied to. Simple as that.

I can't understand how Google can't fix this, while a random ROM/Xposed module developer can.

This HAS NOT been fixed via xposed. It is a common misunderstanding. The only thing the current available fixes do is mask the usage. I have talked with some prominent ROM makers in the custom android community and they all have agreed that at this point a fix from google is the only way to get this sorted.

Yes. I confirm the Xposed module is at best a placebo. It solves nothing. Unless Google fixes this this is not going away.

Are you guys complaining about the mobile radio state solely (how long it's been up for) or the high power state lasting much longer than intended?

Because I think the later has been fixed in M.

Yes the former. The latter too is a hit or a miss in certain conditions because of the former. 4% drain an hour on cellular data vs. 4% drain in 7 hrs on WiFi during idle times is way too much of a gap to live with. Doze works fine when on WiFi. When not on WiFi I don't see it working any better than lollipop. In fact hard to say its there even. This bug is the primary reason I have a charger in my car for emergency situations. Else I should never need one. Shifting from high power state to low power state is shitty patchwork not a resolution. Its a stop gap being termed as a solution by Google.

If it were fixed I wouldn't be seeing real world screen on times be halved on lollipop and later. From 7 hours to 3-4. I can verify this because my phone came with kitkat so I am fortunate enough to have kitkat to downgrade to. Others aren't so lucky.

As a side-note, I would love to know who this has been assigned to (if anybody). Obviously we'll probably never know but still, I'd love to get a google employee's take on this.

From lollipop to marshmallow... after nearly a year we are still here with this bug!
It is truly amazing!!!

To quote one of the developers I've grilled about this nasty issue: "if google were to point me in the right direction I'd probably have this fixed in no time."

Also, allow me to point you in the direction of this issue tracker https://code.google.com/p/android/issues/detail?id=165558

It's the same issue but it has a much bigger number of stars. In fact it is the number one "priority small" issue on the tracker. It too is labeled as "assigned" but has not been fixed even though it is full of complaints. I would urge all of you to express your distaste for this nonsense in that thread as well. Lets try and illicit at least some kind of response from a google employee.

I'm still following both posts, but I have given up hope that Google addresses this issue or will ever treat battery life seriously.  It may take a law suit at some point to get them to do anything.

My wife and I have since switched to iPhones as this appears to be the only way to recover ones battery life.

Hi guys. This a new user of motor x play, coming from a moto g 1st generation. When I updatedo the moto g from kit kat to lollipop, I started to notice a worse battery performance. But I didn't take care because I thought the moto g's battery was old and useless. NO WAY! I bought this year a brand new moto x play with lollipop 5.1.1 with its great battery of 3670mah. After several days of use I noticed a very poor performance of the battery life with less than 2 days, and i'm not a social networks user, no Facebook, no twitter. Only whatsapp and mail and chrome. I started to study the mobile and the stats from the battery with the same result known from everybody, when the device is connected to the mobile network, the battery is drain by Google pay services and the radio modem is always active. When you use wifi,this doesn't happen. Unbelievable this issue is not fixed by Google since lollipop was released. Because this is a bug from the os,  since I ve disconnected all the features that makes a mobile to be a smart phone. No gps, no synchronisation, no now cards, nothing. It is a pity because moto x play is a great phone and I'm considering to return it bacK to amazon. My problem is the options I have:windows phone, I don't like them, ios, too expensive. THIS IS A PROBLEM OF GOOGLE AND ANDROID SYSTEM AND WE NEED SOLUTIONS!

#66 please copy/paste your comment here as well https://code.google.com/p/android/issues/detail?id=165558

#42 and #43
For me, the xposed module really fixed  the drain.

I´m using 4.4.4 now for testing purposes, and got the same battery time than the 5.0.2 with the fix.
My battery (Xperia ZQ) lasts around 8h (clash of clans, many podcasts and spotify) with the fix and in 4.4.4.

Without the fix it lasts around 3-4h.

As said before I'm returning here to again ask Google developers to update us on the progress if any made. If not started reminder to not not piss a lot of people who hate this bug.

Everyone else. Stop being a bystander. It takes a min to come here comment and voice yourself in support of getting this bug fixed. Let's make some noise.

Here here ( also here https://code.google.com/p/android/issues/detail?id=165558 )
Cant wait for google to continue ignoring us! It's so exciting!

yeah post #72 still counting

Piling on to say please fix this, stop ignoring it - there are lots of people affected. I'm hoping cyanogenmod will fix it before google  do as usual, but prove me wrong, Google!

Please fix this, it simply should not be an issue like this. Not sure why
we don't have an xposed hack fixing this like we had in lollipop.

Priority-Small

*mind blown*

@#75 that's just code for "we really can't be assed" or "we dont actually know how we fucked up and we can't be assed"

I can confirm. Bug present on Android 6.0 on my LG G4. I'd get even better battery life if it wasn't for this damn issue. Since i got the newer google play services update I've had this issue. This should be a higher priority than Google makes it to be. Peace.

Wtf Google. Sort this out

Same here, 6.0.1 Nexus 5.

Unbelievable, fix it google

This is a huge issue. My usage is low yet my battery has gotten way poorer on 5.1.1. It was amazing on 4.4.4. Google fix this please. If XDA can do it, I'm sure you can.

#81 nobody has been able to fix this. Most they were able to do is mask the issue.

I am amazed this still isn't fixed, especially considering how important battery life is for users. It is a terrible bug.

android 6.0 on lg g4. still this bug .....

Same error on 6.0.1 over N5X. :(

[Comment deleted]

Same on Nexus 5 6.0.1 (stock 6.0.1 (MMB29S))
It started after OTA update from 6.0.1 (MMB29K) to 6.0.1 (MMB29S).

I will try to flash 6.0.0 (MRA58N) and report if I will get rid of the bug after downgrade

#87

What is wrong in your screenshot?

#88

Mobile Radio Active 1h50m 34s

I didn't even open the app (Telegram). It just drains battery like crazy. Same with other apps, which use cellular data (e.g Google Play Music, Apple Music (yes, I use both), VK (Russian analog of Facebook)). My battery drains from 100 to 0 in 2 hours.

Bug is triggered when I go away from home (which means I disable WiFi) and one of the apps starts to use cellular data (e.g Play Music in the car. I have unlimited cellular data, so I don't download music to device). On the weekend, when I'm in home for a whole day and use WiFi everything is okay, but once I use cellular all apps just keep mobile radio active for some reason, which drains battery.

#87 most interesting post.

[Comment deleted]

#89

But Telegram is an app that is always pinging the server to fetch new messages. Logically, it'll keep the radio on most of the time.

How long has your device been on mobile data? The exact same amount of time as the radio usage for Telegram? Don't think so.

People don't understand. The bug is not about how long the radio is kept on, but how long it stays in high-power state after being called for.

#92 not the same as #89 but look at my screenshots.

Mobile radio from metal is pretty active but notofications are disabled.
https://goo.gl/photos/YT3bcM6m2ggHd9Kk8

As a telegram user, can confirm mobile radio is active and in high power state constantly on 5.x 6.0.1. Now on kitkat and this issue has disappeared. The battery life related to telegram alone is night and day from kitkat to lollipop and marshmellow. There's no denying it, the battery is being brought to its knees by the mobile radio active time.

So, this issue is getting hotter and hotter. And still the priority is set to "small". What the heck?

Apparently, xda-developers and custom-mod developers are doing a better job than Google developers.

Doesn't really take a whole lot to do a better job when the party responsible for fixing this isn't actually doing anything.

Just chiming in here... I have a Moto X (2014) and I just updated to Android M 6.0 (the latest release for my phone) and I have the same problem.

My primary reason for finding this issue wasn't necessarily under high battery usage, but high data usage. "Android OS" has used over 500 mb of data in just 10 days. That's not normal, is it?

My phone is new, and the warranty is still in effect, and I like Motorola custom software, so it's keeping me from just installing Cyanogenmod. Very, very poor move by Google on this. I don't think I've ever been more disappointed in a development team before.

For now, I'd say instead of moving to iOS, our best bet is installing a custom ROM. I guess I'll be working on that this weekend...

Custom roms still have the obscenely high mobile radio active times, but at least they don't have the massive data usage.

So does this problem affect every handset with Lollipop or Marshmallow?

Does a factory reset fix the problem or am i stuck with this?

This bug has been reported since Oct 2015 and the Lollipop one since April 2015. I've starred both reports from the beginning but I'm thinking of coming here weekly and post a comment until they are fixed. There's not much we can do as users, only star the report and make a comment.

I encourage other users to post a comment (star the issue if you haven't already) every week until we see the priority change or a fix. Google hasn't bothered to even acknowledge this is a serious problem that impacts every aspect of our devices.

any way to contact the assigned developer working on this?

For the love of god, provide OEMs an update that can actually fix this dreaded bug for lollipop and marshmallow devices, especially now that they provide updates more than ever.
Please, I have been experiencing this bug ever since I started using Lollipop on every device that has it or even custom-installed with it...

I guess it may be only effective to pressure through devices vendors, as finally they lose money, but not Google (and they have access to mighty Goo).
Not sure about press... Most of them suspiciously silent about this bug and refuse to discuss on it.

Exact same scenario as described in post #89 :
I'm not even using the telegram app but same battery drain occurs regularly with other "online" apps exactly when leaving home and switching off Wifi: in that situation the battery stats are always showing a nearly linear drop in capacity AND it seems the doze mode stops working (...that lovely horizontal line just disappears) !
Nexus 5, Android 6.0.1, sync deactived, 3G, GPS device only, etc.

My chrome is keeping the radio active for long periods of time. Like hours. It is the biggest contributor to battery drain. I switched to chrome dev and it seemed a bit improved. It happens more the longer your phone stays on. I find a reboot makes it summer down for a while.

This is very poor behavior! I like nexus devices and now I am forced to use custom ROMs (Marshmallow) in order to avoid this battery drain. What is the point of using and buying new devices that are affected by this? Who would buy new car that is pretty awsome, but the fuel tank is only 5 liters? Seems pretty unusable for me...

Luckily my Z5 has pretty good battery life, but this bug kills it when I use Chrome. I can use it for a couple minutes and still end up with 5+ hours of mobile radio active in Chrome throughout the day. I'm tempted to just change browsers...

[Comment deleted]

Have this issue with my Z5c, unusual battery drain and high "Mobile radio active" time.

Highest consuming apps are Google Services and chrome.

[Comment deleted]

#111  doesnt sound sober... KK had ~36 hours of lifetime, LP ~8. It cant be explained only by measurement methodology changing.

Same issue on my Lollipop Xperia Z5. Need to disable the data and only use WiFi so that I can get decent battery. This issue needs to be fixed, and fast.

Come on google please please please. Why do you do this :-(

seems ridiculous to incorporate a counter and calculation that doesn't work. Why would anyone do that, seems illogical. This is clearly an issue, as indicated by the battery drain / lifetimes in KK vs. LP stated by many users above.

Please fix the battery draining mobile radio active bug Google. I was really hoping it would be fixed in Android 6.0. Can it be fixed in Android 6.1, maybe?

The bug is still there, especially with Play Services.

I have that too when i turn on data on Samsung Galaxy S6, Google has always been the tech giant in my eyes and i really dont understand why they dont bother fixing this bug with all the engineers working there.

google spit on us ... and to our problems

Please fix this bug. It is irritating.

Really? I mean REALLY??? Is there even a person monitoring these bugs anymore??? Because I can't believe something so badly broken is COMPLETELY IGNORED for so long! Damn you Android Team just fix this already!!!

This is an issue and there is no way around it unless you use mobile radio whenever you want it and switch it off when you switch to Wifi. Should be high priority.

#111
I think u are right on mobile data the total connection time get high values... for google services, i belive there is a problem with total connection time showing wrong values and percentages. On my s4 battery lasts 2 days medium usage and 4g always on.
Maybe there is a problem with the app that displays battery usage.

Same issue, particularly with Chrome, running on Lollipop 5.1
CPU time, foreground time is 5 minutes, but Mobile Radio Active time is 1H 46min...

Using moto X Play XT 1562 dual sim, on stock MM 6.0, rooted, xposed, amplified, greenified and what not, mobile radio active still draining battery when in standby. Any custom ROM with a fix for this as google is least intrested.

[Comment deleted]

Only solution I've found working so far is use 'Smart Network' module by Wanam to turn off the Mobile data once screen is locked and periodically turn it on once in an hour to allow sync and notification through. Hope it helps someone.

The bug has been on my Moto X Style since I bought it. Factory reset didn't fix. Spotify, Google Play Services and Chrome drain an insane amount of battery if I don't close them! We need a fix! Quickly!
"Priority - Small" Gosh...

I just updated my Sony Xperia Z5 to MM 6.0 and this stupid bug is BACK. I am do mad right now.

Even under 5.1.1 I get this same issue...randomly, Play Services just uses mobile data for hours straight draining my battery.  Today is started around 4pm, and the entire time the phone was stationary with screen off, yet Play Services was using up mobile data and causing significant drain for an hour and 18 minutes before I rebooted.

I have the 6P with latest build MHC19J, andddd the bug is still here.

Attention! Here comes a BIG question! Google ignores this bug, XDA has released a patch that fixes the statistics, there are regular posts that active time has nothing to do with battery drain and it is all about stats. Are we SO sure that our batteries are not wasted or something else is wrong?

This service 33% battery
Screen 2%
...yeah makes "sense" - jesus!
I tried uninstalling all google apps, which restores them to factory default versions. This restores my battery life to 9days, like it used to be! Updating them again drops battery life to 3½days, but if I use old outdated versions there is likely a security risk.
However the fact that I didn't notice any issues on my phone when running with the factory default versions means, essentially, that whatever new stuff was added are design failures as the net experience is Much worse with no essential benefit! It's sooo frustrating!

Nice work, Google. I have 1-2% per night with wi-fi and 10% with 4g or 3g.

Been enjoying my Nexus 6p, until the battery drains for no reason.

Google: WHY are you failing here?  At least post some sort of tool that I can manually invoke to kill the process.  Re-booting the ^&%&*&* phone is NOT an acceptable solution!  

Also, the problem goes away overnight while recharging - what changes?  It only re-starts if I start using an app the next day that is accessing the web via cell...

Just chiming in to add my voice to the crowd. My Chrome process has kept mobile radio active for 50 minutes so far today (halfway through the day) but I've only used my browser for about ~15 minutes).

This has happened to me for a long time on various roms (including COS) on my oneplus one, ever since Android 5.

[Comment deleted]

Does N has good news for us here???
I dont have a nexus any one tried....

Hi, I've noticed the same issue on my galaxy s7 as well running Android MM. The Skype app was showing mobile radio active even if I did not use Skype that day at all. The Skype app was showing 2nd in my battery usage stats. But the battery lasted me whole day regardless.

The funny thing is that when I uninstalled the Skype app now the samsung browser shows mobile radio active for hours. The browser was only used for abut 20 minutes.

So my questions is that is this bug really causing any battery drains or is it just causing some false stats?

Considering that I have a normal Galaxy s7 and I use it for about 2-3 hours of calling every day and 2-3 hours of screen time, I don't have to charge my phone during the day and I have 20-30% juice left at bed time. Coming from iPhone 6, the battery life seems ok to me.

just my thoughts

I've got a S7 Edge and I also started experiencing this issue after 3 weeks of use. Overall at the end of the day I lose roughly 20% of the battery due to the Cell Standby Issue, and its very noticeable compared to how the battery was the first 2 weeks. I've tried all possible solutions posted online and none have worked so far. I just moved from iPhone and I was so excited about finally having a big-ass battery... and it all went to hell. The phone is making me anxious more than I am able to enjoy it just because of this frustrating battery drain. I cannot believe for how long they have been ignoring this issue, it's just absurd!

Just bought a Galaxy S7 Edge last week - thinking to finally have awesome battery life, that is - and I too am experiencing this. What a travesty. Whatsapp has been on for 6 minutes and it's been using mobile radio active for almost 2 hours. And you can add Cell Standby and Play Services to the list as well. It's killing my battery life. Way to go Google, fix this. Quickly.