Google Android 6.0 to restrict OEM -related hidden battery usage stats

Google just released some interesting news regarding Android 6.0 and its relation to OEMs. Things are getting pretty restrictive around here and manufacturers will not be able to change whatever they want just to bloat smartphones with unnecessary apps that also drain battery life without us knowing about it.


Android usage



Up until now, OEMs were able to hide or even remove certain stats, but with Marshmallow that will not be possible anymore because the OS will account for power consumption better.


According to the Marshmallow Compatibility Definition Document, or the CDD, devices running on Android 6.0 will have more accurate accounting and reporting of power consumption for each and every app. Below you can read the whole matter:


Power Consumption Accounting

[box type=”shadow”]A more accurate accounting and reporting of the power consumption provides the app developer both the incentives and the tools to optimize the power usage pattern of the application.

  • Therefore, device implementations MUST be able to track hardware component power usage and attribute that power usage to specific applications. Specifically, implementations:
    • MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site [Resources, 123].
    • MUST report all power consumption values in milliampere hours (mAh)
    • SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
    • MUST report CPU power consumption per each process’s UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
  • MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer [Resources, 124].
  • MUST honor the android.intent.action.POWER_USAGE_SUMMARY intent and display a settings menu that shows this power usage [Resources, 125].[/box]


The full battery stats will be available and they will make things much easier to compare and find out which devices use the most power inefficiently. OEMs could be hiding the way they drain battery life through apps and services but, with Marshmallow, things are going to change. This is, assuming they all want Google certification, which will not happen unless they comply to these terms and others.


Source: AndroidPolice

News Updates/Software

Android Marshmallow Preview 3 allows granular battery consumption per apps

Android Marshmallow Preview 3 allows users to see just how much energy each active app consumes on a given time. Even if Android’s battery stats and features have always been one step ahead on, let’s say, iOS, there’s always room for improvement. If you wanted even more detailed and granular statistics for your phone when it comes to power consumption, Marshmallow show much promise as its preview 3 allows users to see individual app usage or battery capacity in mAh.




This new feature uses miliamp-hours (mAh) to measure power consumption because this is how batteries are rated to users. This unit is appropriate to use because it measures consumption as specific as possible. Since we are talking about computed usage, readings are not 100% correct. We do not know just how meaningful and accurate these readings are, but they do offer good statistics to base your numbers on.


This Marshmallow preview 3 feature is a bit abstract when it comes to measuring power consumption because, instead of showing a proportion of 100, you get a number that you can compare to the total capacity of your smartphone battery. You can find this feature in the Battery stats section. Let’s hope this function gets developed or at least included in the final Marshmallow version.


Media file source: AndroidPolice