[ONE Original Android Development] taufiqs:
1. Mobile radio PWN

What MRP is designed to do is correct the ‘Mobile Radio Active Bug’ meaning, in this case, a commonly experienced bug in which an app utilizes or ‘hooks’ your Mobile Data to perform an internet related task while not connected to WiFi. This is normal, however, the bug is caused by the app that initiated that ‘hook’ failing to release it when reconnected to a WiFi Network, thus your devices Mobile Radio ‘sticks’ on when it doesn’t need to be causing astronomical Mobile Radio Activity and excess power consumption. When using Mobile Data, you will always generate some Mobile Radio Activity, the problem occurs when Mobile Radio Activity continues to be generated after having established a WiFi connection. That is what this app aims to prevent.

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

2. Xposed module Mobile radio active fix

Info about the patches

How to reproduce the bug:

-Enable mobile data (with wifi off)

-Use some mobile data (radio active timer starts in battery stats)

-Disable mobile data (radio active timer keeps running in battery stats)

After some investigation on the issue I found that the BatteryStats

service was not receiving the radio power down notification. The

investigation lead me to the NetworkManagementService.java, where

I found that some code was discarding the radio power change

notifications after the first radio power on.

The problem is that in NetworkManagementServer.java the

notifyInterfaceClassActivity method is discarding the notifications

of radio power change to the BatteryStats (via noteMobileRadioPowerState)

if the fromRadio parameter is false after it's being true some time before.

Even after a detailed analysis, it was unclear what is the real role of

the fromRadio parameter. Changing it to true in the calling methods

solved the issue in the testing unit (Sony Xperia ZL).

Change that introduced the code with the potential to trigger the bug:

-Introduction of "boolean fromRadio" in

NetworkManagementService.java / notifyInterfaceClassActivity()

https://android.googlesource.com/pla...bdc1a07fbe8246

Change that triggered the bug:

-Uncommenting the code that calls notifyInterfaceClassActivity

with fromRadio=true

https://android.googlesource.com/pla...2d236aae1dc7ee

quoted again from

http://xdaforums.com/xperia-zl/general/cm12-1-cell-standby-mobile-radio-active-t3188147

You've have to try one of it to identify which one is the most suitable fixing your MRA bug.

For me, none of those solution completely fix the battery drain where MRA bug was being suspected. At least, they have following advantages/function for me:

1. mobile radio pwn ensures that when my office wifi (secure proxy and username+password) doesnt have good internet, my mobile data quota wont be reduced because MRPWN disable my mobile data (which is impossible using Tasker + Secure Setting in lolipop)

2. MRA fix in xpose module really pressed down the MRA counter (from before using it, it was always bigger than CPU time and almost the same with run time of my OPO).

I have tried and the battery drain is there. No wakelocks, deepsleep when sleep, no rouge apps yet the battery drain is still there. I'll wait for M then while using KK instead of Lolipop.