Develop Bugs

Media = 87.9% Of Battery Usage WTF

Hey Guys - I recently loaded a JB rom (aokp build 1) and lean kernel (much better than the included one) and my battery life has been crappy. I just installed GSam Battery Monitor and it shows App Usage @ 94.9%, more specifically, Media is using 87.9% of my battery!
Included packages:
Download Manager
Downloads
Included Processes:
*wakelock*
android.process.media
What can I do about this? I tried disabling Google Now & Google music sync... still no luck.

I had a problem similar to this, it was caused by a widget I had on my homescreen. It was constantly fetching info and running my data up and my battery down.
lilfleck said:
Hey Guys - I recently loaded a JB rom (aokp build 1) and lean kernel (much better than the included one) and my battery life has been crappy. I just installed GSam Battery Monitor and it shows App Usage @ 94.9%, more specifically, Media is using 87.9% of my battery!
Included packages:
Download Manager
Downloads
Included Processes:
*wakelock*
android.process.media
What can I do about this? I tried disabling Google Now & Google music sync... still no luck.
Click to expand...
Click to collapse

Can you please provide details? I am still experiencing this drainage on VZ galaxy nexus , android 4.1

lilfleck said:
Hey Guys - I recently loaded a JB rom (aokp build 1) and lean kernel (much better than the included one) and my battery life has been crappy. I just installed GSam Battery Monitor and it shows App Usage @ 94.9%, more specifically, Media is using 87.9% of my battery!
Included packages:
Download Manager
Downloads
Included Processes:
*wakelock*
android.process.media
What can I do about this? I tried disabling Google Now & Google music sync... still no luck.
Click to expand...
Click to collapse
Try disabling currents...this helped a ton on my phone...what widgets do you have on your home screens and what accounts do you have syncing?
---------- Post added at 09:26 PM ---------- Previous post was at 08:57 PM ----------
[email protected] said:
Try disabling currents...this helped a ton on my phone...what widgets do you have on your home screens and what accounts do you have syncing? Also turn screen to auto brightness, turn wifi off if not in a wifi area as it will be constantly searching and make sure gps is only on if you are using navigation as this will eat up battery. I always like having the power widget on one of my home screens so I can quickly click them off and on.
Click to expand...
Click to collapse

[Q] A solution for Play Services nlp wakelocks on Lollipop, without using Xposed

Hi.
Everything seems awesome on Lollipop, apart from the crappy crazy Play Services wakelocks. I've greenified Google Play Services, and although it fixes the mad battery drain, it doesn't seem to like it, and after a few hours, the phone gets absurdly slow. Removing it from Greenify results in normal speeds, but increased battery drain.
I remember using Amplify, and Xposed module, to fix the high battery drain, by increasing the Play Services location polling time, but now we don't have Xposed anymore.
Is there any known way to fix this?

I've noticed the same thing and also used to use Amplify.

I have the exact same problem, used to use wakelock terminator too, but that requires xpsed framework as well....
Any solutions welcome...!

Maybe you can find a ROM that has a wakelock blocker baked in. Illusion for Verizon does.
Sent from my G3, rockin Illusion

I used wakelock terminator for kitkat as well. I just installed lollipop today and am actually pretty happy with the battery life so far, but the play services is still near the top. Would be nice to have even BETTER life by preventing these wakelocks. I'll be keeping an eye on this thread. Hope someone can find solution! I'll keep looking around.

Heads up! http://www.droid-life.com/2015/02/10/xposed-developer-nears-release-for-android-5-0/

Fusion v5.0 has wakelock blocker.

[FIX] Cell standby/mobile radio active time issue

Introduction
If you think there is a drain in Lollipop this is not that fix. This fix the "high cell standby mobile radio active time" bug. You can still test this if you want.
Some people are writing that this patch "only" fix the battery radio active time counter. I say that if you know java and take a look on the code you will note that the side effects of this bug includes, among others, not calling various NetworkManagementEvent observers that will have role in other modules of the inner core of Android, and not only the battery stats. So you say me what are the other side effects fixed.
Other people are saying that this patch doesnt fix the "cell standy radio active time" bug, so take your chances, or wait until Marshmallow :fingers-crossed:.
If after the patch you see a "miscellaneous" item in the battery stats, I am sorry for you but this indicates a bug in your RIL module (or other module) which this patch not solve. The bug in the RIL module was only masked by the Lollipop radio active time bug.
Hi,
I'm working on a fix to the Cell standby / Mobile radio active time issue. The bug manifests as a high mobile radio active time on the Cell Standby in the battery stats.
I think I found the bug in the inner core of Android, and I made some fix to test if it works.
In this thread you will find a Cyanogenmod 12.1 (Android 5.1) build for Odin/Xperia ZL with the fix applied. I already flashed this build onto my odin device and the bug seems to be fixed.
So now I want some of you to test this build and see if the bug is definitely gone.
NOTES
- Your device must have bootloader unlocked.
- CyanogenMod and my work comes with NO WARRANTY as usual. Don't blame me for anything you think I deserve.
- This is my other work on fixing droids: http://forum.xda-developers.com/showthread.php?t=1312398
Patches
I submitted the fix patches to AOSP/Google and CM.
https://android-review.googlesource.com/#/c/168231/
http://review.cyanogenmod.org/#/c/107828/
FAQ
How to install
-Make a backup (using recovery or your preferred tool)
-Download .zip and copy to the phone external sd card
-Boot into recovery (TWRP recommended)
-Install zip cm-12.1-20150827-UNOFFICIAL-odin.zip
-Wipe dalvik/cache
-If you was not on CM12.1 before then Wipe Data
-Reboot
-Wait Android installing apps
How to test
-Enable mobile data (with wifi off)
-Use mobile data (now the bug was triggered)
-Disable mobile data
-Use your device normally and then some hours later look for the mobile radio active time on the battery stats.
-On normal circumstances the display should be the bigger drain. The bug manifests as the Cell Standby being the bigger drain with a high mobile radio active time.
-Please report in this thread if it works or not for you. Thank you!
Can I have a Xposed module of this
- Yes. Thanks to @pyler
http://forum.xda-developers.com/xpo...oactivefix-t3189393/post62570773#post62570773
Download: flashable ZIP
- 2015-08-27 v1 (new)
http://www.mediafire.com/download/2f0igf17ixs52zc/cm-12.1-20150827-UNOFFICIAL-odin.zip
MD5: 3c3641ad6738fad953a90a5d3e745f75
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/platform/frameworks/base/+/2ffa11e4b71c545e34533ef827bdc1a07fbe8246
Change that triggered the bug:
-Uncommenting the code that calls notifyInterfaceClassActivity
with fromRadio=true
https://android.googlesource.com/platform/frameworks/base/+/2d4b4ed681efcfb64c4d2b4d2a2d236aae1dc7ee
Instructions on how to make an Xposed Module from this patch
XDA member pyler is working on a Xposed module to apply thish patch:
http://forum.xda-developers.com/xpo...oactivefix-t3189393/post62570773#post62570773
---
You can use and Xposed module to apply this fix on-the-fly. If you decide to make an Xposed module from this patch, please credit my work and put a link to this thread.
How to do:
- on package com.android.server class NetworkManagementService (NetworkManagementService.java)
- verify if the method assinature for notifyInterfaceClassActivity method is correct (have the fromRadio parameter)
- intercept the call for the notifyInterfaceClassActivity method
- change the value of the fromRadio parameter to true
- and then call the original method
package com.android.server
class NetworkManagementService
private void notifyInterfaceClassActivity(int type, int powerState, long tsNanos, boolean fromRadio)
For devs
- CyanogenMod: you can repopick the patch 107828 before building.
- Other ROMS: apply the patch manually, it's tiny. The project is frameworks_base.
- There is no APK alone that solves this, only the xposed module.
Supporters
Unexpected but not least important, the following people appreciated my work and made ​​a donation or special thanks:
phoneturf

I submitted the fix patches to AOSP/Google and CM.
https://android-review.googlesource.com/#/c/168231/
http://review.cyanogenmod.org/#/c/107828/

good work! finally a patch

Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek

This is what Android has become, the bug second most stared on their tracker is fixed by volunteers on XDA.
In general that does not make me very happy, but the work you did for them is awesome, thank you!

I'm a little confused now... Does this really fix the battery drain or is it just a fix for false measurement in batterystats? Because battery life on mobile data is much worse than on wifi for me since Android 5/5.1

It appears from your patch that this is only a reporting issue in the battery stats, and that the mobile radio IS being shut down, it just isn't being reported properly. If this is the case, do you have any idea why the battery performance in Lollipop is som much worse than KitKat?

acwest said:
It appears from your patch that this is only a reporting issue in the battery stats, and that the mobile radio IS being shut down, it just isn't being reported properly. If this is the case, do you have any idea why the battery performance in Lollipop is som much worse than KitKat?
Click to expand...
Click to collapse
Yes. In my device the radio IS being shut down properly. But in fact the code is a mess and I think there are many other bugs in the networking module.
I was on stock Kitkat and now I'm getting the same battery duration on CM12.1 (4h display on + 30m GPS/3G). Need more tests to detect more issues.
Anyway, I found another issue that I want to investigate that is the mobile data radio being activated and deactivated for a few seconds every time the wifi is connected.

Bazoocaze said:
Yes. In my device the radio IS being shut down properly. But in fact the code is a mess and I think there are many other bugs in the networking module.
I was on stock Kitkat and now I'm getting the same battery duration on CM12.1 (4h display on + 30m GPS/3G). Need more tests to detect more issues.
Anyway, I found another issue that I want to investigate that is the mobile data radio being activated and deactivated for a few seconds every time the wifi is connected.
Click to expand...
Click to collapse
Interesting. I was beginning to suspect that the Radio active time being displayed was a reporting issue, if the radio was really turned on as much as it claims, I think battery life would be much worse. Your patch is useful in that I now have a good idea of where to add logging statements to try see if there ARE issues with the actual radio active time.

reaper90 said:
I'm a little confused now... Does this really fix the battery drain or is it just a fix for false measurement in batterystats? Because battery life on mobile data is much worse than on wifi for me since Android 5/5.1
Click to expand...
Click to collapse
I do not know for sure. This will only solve the "mobile radio active time" issue on my device, where there is not a drain, but only the false measurement.
But if there is a problem in the RIL module of your device this patch will not solve the drain.

acwest said:
Interesting. I was beginning to suspect that the Radio active time being displayed was a reporting issue, if the radio was really turned on as much as it claims, I think battery life would be much worse. Your patch is useful in that I now have a good idea of where to add logging statements to try see if there ARE issues with the actual radio active time.
Click to expand...
Click to collapse
You ARE CORRECT.
I concluded the same when I put the decice in ariplane mode for several hours: the battery percent was the same at the end, but the mobile radio active counter keeps running for several hours, indicanting that the radio was turned of properly (same battery percent) but the timer keeps running.

Bazoocaze said:
You ARE CORRECT.
I concluded the same when I put the decice in ariplane mode for several hours: the battery percent was the same at the end, but the mobile radio active counter keeps running for several hours, indicanting that the radio was turned of properly (same battery percent) but the timer keeps running.
Click to expand...
Click to collapse
This is a good news/bad news situation. Good news, you have found the cause of the high radio active times. Bad news, something is still draining the battery. At least now we have better information...
Excellent work on pathing the issue, by the way...

abhibnl said:
Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek
Click to expand...
Click to collapse
Concept seems interesting. Lemme look at the commits first before we go as far as building :good:

abhibnl said:
Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek
Click to expand...
Click to collapse
Done

jgcaap said:
Done
Click to expand...
Click to collapse
Nice!

Still trying to put this into an xposed module, gonna take ages for me to do it

merewood bebox said:
Still trying to put this into an xposed module, gonna take ages for me to do it
Click to expand...
Click to collapse
I will make an detailed explanation on the first topic.
----
EDIT: done

So anyone here has made the module for xposed?
Sent from my Oneplus One using Tapatalk
---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------
jgcaap said:
Done
Click to expand...
Click to collapse
@jgcaap would you like to share link for your build that has this patch?
Thanks
Sent from my Oneplus One using Tapatalk

Bazoocaze said:
I will make an detailed explanation on the first topic.
----
EDIT: done
Click to expand...
Click to collapse
thank you very much

Could anyone make either a xposed module or a flashable zip that we can use on bacon OnePlus One 5.1.1 to fix the mobile radio active issue? Thanks

I love ElementalX (EX) Kernel, but...

Snapchat, other camera apps, and even sometimes stuff like Mixcloud/Soundcloud crash at various frequencies. Are there any known workarounds? If not, is there another kernel that has the battery saving potential of EX Kernel that doesn't cause these issues?

This shouldn't be kernel related and if you are 100% sure it is, grab a log and post it in @flar2's thread so he can identify the issue and fix it.

djdadi said:
Snapchat, other camera apps, and even sometimes stuff like Mixcloud/Soundcloud crash at various frequencies. Are there any known workarounds? If not, is there another kernel that has the battery saving potential of EX Kernel that doesn't cause these issues?
Click to expand...
Click to collapse
This is not a elementalX problem. A kernel has nothing to do this at the beginning. And I don't have any issues at all.

Need to Know about the Best Custom Kernel for CM13 build

i am using CM13 build , i am not satisfied with the battery backup , also battery drains very quick while wifi ON but not in use , my battery is all right , i almost get around 4 hours of SOT on MIUI 8 .
Please anyone suggest me the best custom kernel for cm13 build with it's settings
thankyou

Looking forward for replies.

My Opinions - So far I've got great results especially battery and performance
ROM: XOSP - Latest Final Marshmallow Version
KERNEL: Gods Kernel
with FS Trim, Greenify, Battery Calibration and Xposed Installed
Results:
NORMAL USE: 12-16 hours of SOT
GAMING: 5-6 hours
STANDBYE: Almost 2-3 days
Kernel Settings: Default
I also disable USB FAST Charge
MinFree Manager:
FS Trim
All checked except for System
Automatic Fstrimming "enabled" - interval "Every 8 Hours"
Greenify Settings:
Working Mode:
Root + Boost (Xposed)
Shallow Hibernation:
Disabled
Aggressive Doze:
Disabled
Automatic Hibernation:
Checked
-- XPOSED BASED Features --
Enabled: Telephony Wakeup and Block App State Abuse
Others are Unchecked and Disabled
Apps that are accompanied by manual hibernation:
GMAIL
SHAREIT
MESSENGER
BROWSER (stock browser, chrome, chromium, UC browser, and etc)
GOOGLE DRIVE
GOOGLE MAPS
GOOGLE APP
YOUTUBE
ALL GAMES (except server sided games like CoC, CR, and etc

Harry_00s.HS said:
i am using CM13 build , i am not satisfied with the battery backup , also battery drains very quick while wifi ON but not in use , my battery is all right , i almost get around 4 hours of SOT on MIUI 8 .
Please anyone suggest me the best custom kernel for cm13 build with it's settings
thankyou
Click to expand...
Click to collapse
The kernel that comes with CM13 works reasonably well. A few things can cause excessive battery drain and its not just the kernel that is at fault. We don't know all the settings and installed apps of the people who have claimed long battery life for their phones after flashing this rom or that kernel, or even if their testing methods are reliable and can be compared with others. So any claims about long battery life is very suspect.
Google services has always had a big problem with power drain because of bugs. Google's location data gathering is not only bad for privacy but for draining power as well. And many free apps tend to use too many non-related permissions and they may misuse google play services which also drains power. So the easiest thing is install the bare minimum of google apps (start with google pico package) and use xprivacy to tighten up permissions. I think nothing can be can be done with rogue apps that use google play services.

barrack1 said:
The kernel that comes with CM13 works reasonably well. A few things can cause excessive battery drain and its not just the kernel that is at fault. We don't know all the settings and installed apps of the people who have claimed long battery life for their phones after flashing this rom or that kernel, or even if their testing methods are reliable and can be compared with others. So any claims about long battery life is very suspect.
Google services has always had a big problem with power drain because of bugs. Google's location data gathering is not only bad for privacy but for draining power as well. And many free apps tend to use too many non-related permissions and they may misuse google play services which also drains power. So the easiest thing is install the bare minimum of google apps (start with google pico package) and use xprivacy to tighten up permissions. I think nothing can be can be done with rogue apps that use google play services.
Click to expand...
Click to collapse
i don't use google play services or GAPPS , now can you tell me about custom kernel which can give me good output at battery status

Harry_00s.HS said:
i don't use google play services or GAPPS , now can you tell me about custom kernel which can give me good output at battery status
Click to expand...
Click to collapse
What do you use your phone for if you don't install google play and gapps? Many people including some reputable posters liked Kairi's Xcelerate for increasing battery life but there isn't a version yet for MM. You could try the God's kernel which works with CM13 but it looks buggy from the looks of things.
I doubt any kernel (Xcelerate included) can instantly transform the redmi 1s and give it good battery life. 4-5 hours of SOT is reasonably good and believable. Claims of 12-16 hours otoh......
http://elementalx.org/the-truth-about-kernels-and-battery-life/