yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
This is NOT an Android bug. This is *possibly* a BAD SOFTWARE issue, or PERFECTLY NORMAL.

Every application that transfers ANYTHING over the network, will cause mobile data activity, which REQUIRES activity on the radio, and DOES draw battery power.

If an application transfers too much, or too often, or too slow, or anything else that will cause the radio to activate frequently or for longer periods of time, then you will see this mobile radio active timer increase.

And the MORE applications you have doing this, again, the more battery it will suck down.

Edit: Your example of pushbullet.... in order for that program to work, it needs to maintain persistent connections between each device you are using that program on, and the vendor's server. In order to maintain a persistent connection, packets have to be transferred across the route on a timed basis, where the time is less than the timeout on all of the routers along the route.

Conclusion: everything is working correctly as intended.
[Nexus 6 Q&A, Help & Troubleshooting] tysonwald:
really? thats normal? then how come noone else is really seeing this "issue" other people say they dont have this so how would it be "normal" ? not saying it isnt because I dont know enough to know, but i would imagine if it was normal behavior then it would be on everyone's phone.
[Nexus 6 Q&A, Help & Troubleshooting] therisinghippo:
No way it's normal. I use chrome beta and it clocked over 3 hours of Mobile Radio Active today. I still got great battery life, but when Chrome Beta takes 20% and your screen takes 10%, something is wrong. It's not continuously updating as someone above suggested. It's a bug. The mobile radio is being kept active for no reason by seemingly random apps. I really hope someone figures out how to fix this.
[Nexus 6 Q&A, Help & Troubleshooting] zer0xp:
Any update on this?

I've tried 5.1 e, l and now I builds and they're all doing the same thing.

I've tried chroma ROM as well, along with stock, lean, Franco and code blue kernels.

I've never been able to shake this problem.

Anyone know what its about?
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
No one has even confirmed it is a problem yet. Unlikely anyone is working on it.
[Nexus 6 Q&A, Help & Troubleshooting] thomas.raines:
At first, I was thinking this was app related, but after looking at all my background and running apps, it seems they all have this "bug". However, mine don't seem to be running that as long, which in turn isn't showing a big battery drain. Hence the fact that I never noticed it.

I am guessing that it is some wakelock that is set by the app, but all apps that connect to the internet are using it. However, I looked on my flo which is running BrokenOs 5.0.1 and it doesn't have this mobile radio active process. I will be updating it to BrokenOs 5.1.0 here in a bit to see if it appears. If not, then we can limit it to just the shamu. If that is the case, then we just need to locate it, probably in the kernel, and decide what to do with it...

I'll follow up with my findings later...
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
I hope there is a solution!

For me it is the problem with Android 5 or the nexus 6. although i dont think it is a problem with the nexus 6. After my recognition are different models (nexus 4, 5, some Samsung devices, moto x...) affected after updating to lollipop.

I have also test different (stock-)roms/ different kernels/ disabled some services/ tested different radios/ factory resets and freezed some system- or deinstalled all 3rd Party apps/ changed the messenger...

No problem in wlan but with 4g/3g is the value of mobile radio active to high that some "apps" (gpservices, android os, hangouts, telegram, sometimes chrome) now are on top of the battery stats. With bbs or wld i cant find the reason.
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
It *IS* on everyones phone.

Nobody is 'seeing' this, because there is nothing *TO* see. There is nothing *TO* see, because it is PERFECTLY NORMAL.

You can't seriously expect mobile data transfer to be done free of battery consumption, can you? It takes electricity to produce the electrical impulses that generate the radio waves that carry data to the remote cell tower. It takes electricity to run the radio processor cpu to receive and interpret the electrical impulses in the receiving antenna that are generated by the radio waves sent by the remote cell tower.
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
There is nothing to see when some apps on top of the battery stats (with 3g/4g) because of the high mobile radio active? Why are this value not so high on other devices with KitKat and then higher with lollipop?
[Nexus 6 Q&A, Help & Troubleshooting] xdadevnube:
Being connected to wifi for a period of time may help reveal more info.

Also, try using a whitelist firewall to only allow apps that you need to allow data. Or even block all traffic for a while and see what happens.

You could even block traffic on only cellular, and let only wifi pass traffic.

Another thing to verify would be whether airplane mode (wifi could be on) indeed causes the issue to completely go away as one would expect.
[Nexus 6 Q&A, Help & Troubleshooting] thomas.raines:
You're argument, although correct, is totally missing the point that we are trying to express. I currently have 8 different devices in front of me. All running Broken)s 5.1 with banks' gapps. All have the same profile and, other than my N7, have the exact same apps on them. Only 1 of those devices, the N6, has this "issue". Which is leaving me to believe that something with the radio/modem, could be causing a wakelock condition, Mobile Radio Active. Now, I have searched my device and kernel trees for any indication of this event, but have not turned up any results yet.

My next step is to search the hardware trees, and if that is inconclusive, I will compare the vendor blobs with similar devices.

I stopped here as I just found some information, and I don't know why I didn't think of this first. But, after running top|grep radio, I found there are only 3 process running that have to do with radio itself.

362 3 0% S 22 49732K 8560K fg radio /system/bin/rild
414 2 0% S 5 19732K 1184K fg radio /system/bin/bridgemgrd
590 3 0% S 4 18684K 1348K fg radio /system/bin/qmi_motext_hook

2 of these processes originate in vendor blobs ( bridgemgrd and qmi_motext_hook).

Since I don't have the original source for vendor blobs, I cannot dig into their code to see if the mobile radio active is there or not. But I can pour over the code for rild, but I don't think that is where it lies. More to come later folks..

However, in response to your argument doitright, this in-fact could be considered normal. As I just posted above, there is no indication of the radio truly holding any kind of wakelock. So the true question is, what apps are holding this "process" open for extended periods of time? Since the apps that I have installed on my N6 all connect to the internet at some time or another, but only report the Mobile Radio Active for a few minutes. To test this, one would need to figure out which apps are using the Mobile Radio Active longest and either freeze or uninstall them, then compare the battery life and the amount of time the Mobile Radio Active is showing with other apps, i.e. google services.
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
Thank you for the tests and your thoughts.

To the things that you wrote in the conclusion: I have already freezed or uninstalled these apps as far as possible. Also i have disabled 50 of the gpservices, location is off, sync is off, background mobile data of gpservices is off. Gpservices and hangouts now dont appear in the battery stats (and now not for hours with mobile radio active). This is the result of experiments and my settings now. But for instance the messenger (telegram or any other) with background data "on" hold the mobile radio active for hours. At least more is not possible. In other way the system is not really usable.
[Nexus 6 Q&A, Help & Troubleshooting] thomas.raines:
Well, something to also consider is the ROM/kernel and GAPPS you are using. I personally don't like a lot of GAPPS so I use banks' GAPPS. Very minimal, but that's what I like...lol

As for the ROM/kernel you are using, there certainly plenty to choose from, but make sure you flash one that fits your needs. I would offer you BrokenOs with my Lightning Zap! kernel, but we are not ready for a 5.1 release of BrokenOs, and I haven't decided if I'm going to release a standalone flashable of my Lightning Zap! kernel for the Shamu.

One of the best and most important features to any rom that I use is the long press back to kill feature. Enabling and using this features allows users to kill the app instead of just closing it, ensuring that the app is truly closed and not just running in the background. Unfortunately, there are still some core apps that you cannot kill. But this does help battery life and functionality. We in the Dysfunctional family, are also working on giving the users the ability to open a process, see what other processes they are holding active, and being able to kill some of those held processes, i.e. the stay awake wakelock in google services. Though this was a feature in previous roms, we haven't quite gotten broken back up to par with 5.1.

As far as the Lightning Zap! kernel is concerned, it is typically a minimalistic. I say typically, because on the mako (N4) I added a ton more features than what I would normally. None the less, the Lightning Zap! kernel is geared towards exceptional performance without sacrificing battery life. Ask anyone that has ever used any of my LZ kernels.... although it will come native with BrokenOs 5.1, I'm still not sure if I want to release it as a standalone.

To put it simpler, I took my phone off the charger at 6 am today. Haven't used it alot, but I have 4, 30 ish minute calls, about 100 texts, 1 1/2 hours of playing the game XTreme 10, and some lite web browsing since my day started. I am now at 86% and projected 2 days left of charge...

Just some suggestions...
[Nexus 6 Q&A, Help & Troubleshooting] tysonwald:
I haven't really had any luck with other gapps, kernels or roms. I used to flash different things to try and get the best battery life as possible, but all resulted in mobile radio active for hours on multiple apps. I never saw any real difference in SOT and believe its because when I leave wifi my commonly used apps are holding this wake lock.

As stated, I've tried different roms, kernels and Gapp packages. Currently i run Chroma rom with the stock franco kernel shipped with the rom. I use banks gapps because i like minimal.
[Nexus 6 Q&A, Help & Troubleshooting] MWilkenson:
After a ton of searching on google, I finally came across someone who's looking into this issue thoroughly. Much appreicated more than you know. While I do not have a Nexus 6, I have the One Plus and the issue is very prevalent on 5.0.x and 5.1 roms. I feel like I am in the select few with this issue unfortunately.
[Nexus 6 Q&A, Help & Troubleshooting] hypern0va:
I'm facing this same problem on my OnePlus One since I upgraded to Lollipop, battery performance became really poor in idle and I think that this is the main reason since I don't have any particular wakelock.. Is there any news about a possible fix? I tried changing modem and WhatsApp, that was one of the apps that showed more this problem, went from 3+ hours/day of Mobile Radio Active to 40 min/day with similiar usage and radio signal. But others, like Telegram, AquaMail and Google Play Services remained very high, on 2+ hours/day.
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
I have found something (See the links)

Someone any idea or can someone explain? Is this even possible with the nexus 6 with what consequences? And sure, is this a solution for the problem?

http://xdaforums.com/z3/general/son...olling-min-t3082941/post60243587#post60243587

http://xdaforums.com/google-nexus-5...ation-mark-t2939694/post58252752#post58252752
[Nexus 6 Q&A, Help & Troubleshooting] hypern0va:
Very interesting, but he mentions that the problem is probably caused by a field left blank by Sony where there should be the Google server for the HTTP 204 status code. I don't think that Google made the same mistake writing the code for the N6's ROM, I mean, it's their own server! While in the "Chinese thread" the problem is the reachability of the server from China.

It would be interesting to see if there is a command to check how is set that field before running the shell script.

EDIT: ok pretty simple, the command is "sudo settings get global captive_portal_server". On my OnePlus One it was NULL, now i set it to clients3.google.com/generate_204, let's see ;)
[Nexus 6 Q&A, Help & Troubleshooting] tatoniss:
Hmmm so I tried this on my nexus 6 on sprint. Now I have an exclamation mark by WiFi and mobile network always. Data still works on both though. I tried changing it back to NULL and that didn't fix it. Any ideas?
[Nexus 6 Q&A, Help & Troubleshooting] hypern0va:
Possible mistake: you have to write "sudo settings put global captive_portal_server clients3.google.com" and not "sudo settings put global captive_portal_server clients3.google.com/generate_204". I expressed myself badly in the previous post, the /generate_204 is what the phone will call but the "/generate_204" will be automatically added, you just have to specify the server.
[Nexus 6 Q&A, Help & Troubleshooting] tatoniss:
Thank you! That was it. Cant wait to see if this tweak makes a difference.
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
...and are there improvements for the mobile active Problem now?
[Nexus 6 Q&A, Help & Troubleshooting] hypern0va:
I'm sorry man but I've been without data connection today, I'll report if tomorrow something changes!
[Nexus 6 Q&A, Help & Troubleshooting] stevemw:
I only see "Mobile radio active" listed for cell standby and it's 2m 57s with the phone uptime over 112 hours. What carrier are you on?

Edit: Oh, AT&T. I think it's a carrier feature. My Nexus 5 is on AT&T and it shows Mobile radio active for every app also.
[Nexus 6 Q&A, Help & Troubleshooting] jeffwei8:
Thank god someone else other than me is complaining about this.

I hate this mobile radio active bug, if indeed it is a bug and not just something new that's being reported in Lollipop now which wasn't in Kit Kat before (which I seriously doubt).

I've noticed it since I first got my Nexus 6 and I've now personally seen it consistently on a Nexus 5 (android 5.0, 5.0.1, 5.0.2, 5.1), Galaxy Note 4 (running cm12), and a Sony Xperia Z3 Compact (stock Sony Lollipop 5.0.2 rom).

It ONLY happens when on mobile 2g/3g/LTE (obviously) and for anyone that says they don't see the bug, they're likely on wifi most/all of the day. The moment you connect to a wifi network it obviously stops the drain.

I have my N6 in my pocket at work on LTE (no wifi at work) and it's idling almost the whole time. At the end of my 8 hour shift, Google Play Services is always at 1.5-2 hours of mobile radio active, WhatsApp is at 45m-1 hour, Hangouts is at 1 hour or more, etc. The key point here is that I barely even used these apps while at work and maybe sent one or two sporadic messages every hour or so. For instance, my Hangouts is at: CPU total 1m22s, CPU foreground 48s, keep awake 13s, mobile radio active 1h 11m 31s. WhatsApp is similar with minimal foreground time and minimal keep awake time (because I barely used them), yet mobile radio active is 50m 29s. My screen on-time at the end of my shift is frequently something stupidly low like 5 minutes, yet my battery has drained from these apps according to the battery usage list. It's not a wakelock issue either since I have them under control and have never had this issue on Kit Kat. Happens regardless what Rom I'm on and what kernel I've tried since Lollipop.

With this bug, I honestly hesitate to even open Gmail, chrome, youtube, or any app that uses data while I'm not connected to wifi simply because I know opening them even ONCE will cause this bug to occur.
[Nexus 6 Q&A, Help & Troubleshooting] hypern0va:
I've left data connection on during the night to see if this still happens after having the HTTP 204 server set and yes, the problem is definitely still here.
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
:(

thank you
[Nexus 6 Q&A, Help & Troubleshooting] kino1122:
I too have this issue on the OnePlus One (ever since CM12 and now CM12.1) and it's driving me nuts. I did some searching last night and saw that this was recently posted on the Android issue tracker: https://code.google.com/p/android/issues/detail?id=165558
[Nexus 6 Q&A, Help & Troubleshooting] tysonwald:
lets hope this will help shed some light and we get somewhere
[Nexus 6 Q&A, Help & Troubleshooting] soare_body:
on N4 too...

I got this also on my Nexus4. I've tried clean flashing, factory resetting, custom roms, custom kernels, shutting down permissions with app ops. Nothing seems to help and my N4 doesn't last the day. I've got this issue with most apps that require internet (including apps like Gmail, Chrome etc.). On Wi-Fi everything seems normal. I can't stand it anymore...
[Nexus 6 Q&A, Help & Troubleshooting] Jezz_man:
I thought of a possible solution to the problem, a tasker task that quickly disables then reenables mobile data when not on wifi and the screen is off to cut off the 'mobile radio active' bug. Only problem is I'm far from a tasker expert, wondering if you reckon this would work? And if yes whether someone could write this task then share it?
[Nexus 6 Q&A, Help & Troubleshooting] Gage_Hero:
You can use this toggle http://www.xda-developers.com/toggle-data-5-lollipop/ it's a plugin...... Event screen off..... task plugin... select toggle..... set to off ..... task... wait... use 10 seconds (I guess) next plugin... toggle set on.... I did play around with turning data off during the night but it seemed to consume more battery then leaving it on, also tried toggling it off while screen was off then on when screen unlocked but that also consumed more. Killing apps during sleep and turning off bluetooth and wifi during sleep hours seems to help using the app kill function but then you need the KC processes plugin to turn them back on in the morning.... You might also want to check your signal strength, mine at work is poor on LTE so I have a task to drop it back to 3G while I'm at work....
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
Some news...Has anyone test this?http://www.reddit.com/r/Android/comments/36vsla/xposed_module_to_fix_mobile_radio_active_bug/
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
No. I've just installed it but in github it says it disables account sync.
[Nexus 6 Q&A, Help & Troubleshooting] MultiKoopa:
Seriously? Apart from disabling account sync, nobody has figured this bug out yet? :\
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
It doesn't actually stop my accounts syncing so no idea whatnots doing if anything.
[Nexus 6 Q&A, Help & Troubleshooting] MultiKoopa:
Hmm. I don't have xposed framework, though... Is there really no other solution?

Or even an idea on what CAUSES the bug?
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
We don't know the root cause.

---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------

Haha 30 minutes on keyboard.
[Nexus 6 Q&A, Help & Troubleshooting] VincentTZ:
Dear devs, are these any updates of this annoying issue? I just can't bear it anymore:(
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Waiting for you to fix it for everyone
[Nexus 6 Q&A, Help & Troubleshooting] StewieTech:
This issue is also present on my moto g 2014, doesn´t matter which rom as long it´s 5.X. I´m using pure AOSP rom, google just released r5 of 5.1.1 with tons of commits and the problem is still there; meanwhile this issue on goole tracker has over 2200 stars and yet no one from google acknowledged the problem. It is also present on android M preview. At this point, i´m getting angry...
[Nexus 6 Q&A, Help & Troubleshooting] randy6644:
Its been forever since lollipop was first introduced. The bug considered minor priority is sill there. I have three phones suffering the same bug , my patience is gone.I tried a fix it didn't work. Google screwed it up!
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
maybe a interim solution:

http://www.androidscout.com/more-goodies-new/mobile-radio-pwn/

Are there improvements? (Can not test it at the moment.)
[Nexus 6 Q&A, Help & Troubleshooting] erk1725:
I installed the .apk from above and gave it a quick spin. It seemed to work as advertised as far as switching on and off the cell radio when connected or disconnected to WiFi. Can't speak for lost lasting effects I saw it shows up as a service in /settings/apps/running and I don't like that. Even if you disable the service through the app it still runs.

I appreciate the link. I'm gonna pay more attention to this in the stats and see how bad it is and maybe give it a longer spin if necessary

Thank you
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
The problem for me and I'm guessing some others too, is this bug (or exceptionally high usage) only occurs when NOT connected to wifi.
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
Sure...I know. Is also the problem at my device.
[Nexus 6 Q&A, Help & Troubleshooting] Smallsmx3:
Im wondering if this is a LP bug? Anyone know if this affects the nexus 4 or 5?
[Nexus 6 Q&A, Help & Troubleshooting] graydiggy:
It is a well known bug on LP. It wouldn't be in the N6 forums if it wasn't.
[Nexus 6 Q&A, Help & Troubleshooting] Smallsmx3:
I don't lurk in the other nexus forums, could be nexus 6 specific, which would mean not an LP issue, which would make sense with all the issues that are being reported with signal problems, SMS/MMS problems, 3g to LTE handover, and anything else radio related. I've had the last 5 nexus phones. With the 4 and 5 I had problems losing signal but it always immediately came back. I've never been more frustrated with this device when it comes to working as a phone. But this has been my favorite device in every other aspect.
[Nexus 6 Q&A, Help & Troubleshooting] graydiggy:
The reason I say that it wouldn't be here is because the N6 doesn't have anything but LP and M preview. The bug is also in M preview as well.
[Nexus 6 Q&A, Help & Troubleshooting] tmrma:
It is a LP Problem and not device-specific:

https://code.google.com/p/android/issues/detail?id=165558

https://code.google.com/p/android-developer-preview/issues/detail?id=2556
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
This bug is nothing to do with signal. Its when you look in app usage and certain apps have high "mobile radio active" values.
[Nexus 6 Q&A, Help & Troubleshooting] Smallsmx3:
Yes I know, but I. Had those devices on JB and KK..... Separate issues
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
OK, not really following your point then.
[Nexus 6 Q&A, Help & Troubleshooting] Smallsmx3:
I just think that there has always been an issue with radio and aosp. It's gotten worse with LP, I don't think it's extended to other android devices because carriers spend time tweaking software to function on their network where as a nexus device has to function across carriers
[Nexus 6 Q&A, Help & Troubleshooting] graydiggy:
Nah. It's on other devices well. It's prominent on my S5 and had issues with it on both my Note 4s. They were AT&T and Verizon. Other people are seeing it on other devices such as the G3 and even The Sony devices for instance. I've been doing a lot of reading the last day about it.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
I see. Well this issue is an android issue not a radio issue per se. The radio is just doing what it is told.
[Nexus 6 Q&A, Help & Troubleshooting] BatDroid:
[MENTION=5064841]pyler[/MENTION] made a xposed module to get rid of it in Lp+
[Nexus 6 Q&A, Help & Troubleshooting] michaelclark07:
Certain apps or services on your device could be causing excessive battery drain or triggering the bug. Try uninstalling recently installed apps or apps that you suspect might be causing the issue. Restart your device and see if the problem persists.