IssueTracker

I'm experiencing this as well, and while I could be wrong, I *THINK* I remember having this issue on M as well. (On the PureNexus ROM)

Cool Tool and OS Monitor worked fine for me with stock (bootloader locked, no root) Android 6.0.1 June 2016 security patch here on my Nexus 6P. Honestly cannot remember as far as the Developer Options "Show CPU usage" described here since I had no need for it. In any case, nothing works in N Dev Preview 4 (NPD56N).

Hi,

Thanks for reporting the issue. We are working on this issue and will provide updates as they are available.

Thanks...

[Comment deleted]

Since it's been months since the last mention of this and N is out in the public now, is there a status update on the situation?

Same issue here on Nexus 6P using Android 7.0 build NRD90T.

I had the opportunity to test this on an unmodified Nexus 6 running Android M with the September security update (MOB31E) and it has the same problem.

The problem persists in the latest 7.1.1 beta (NPF10C).
This issue makes it very difficult to troubleshoot runaway CPU usage (which, of course, leads to excessive heat and battery drain) on devices without root, unless one tethers oneself to a computer with ADB, which is not realistic usage. For that reason, I would consider this a high-priority issue.

This issue is fixed internally and fix will be available in future releases.

Praise Duarte!

@10 Can you please consider adding this as API, and also allow to show other stats, such as RAM, heap, network usage? I've written about it here:
https://code.google.com/p/android/issues/detail?id=226257

@10 Can you be more precise about "future releases"?
I'm using build NPF26F and still not OK.
It actually even got worse, I don't see the "Show CPU usage" feature in the Dev options anymore??!!
Am I the only one?

@10 Any news on this ? is the fix Removing "Show CPU usage" or it will be back in a future minor or major release ?

Can we please have an update if this will be back. It's troublesome to test apps without this feature without going through hard lines. For those who do not wish to use third party apps or root a device exposing vulnerability this is key. Especially considering it hinders observation throughout a full day of general usage and observation for issues that sneak through the cracks.

Also the post from number twelve is definitely worthwhile. Especially to observe for potential security breaches considering new threats. With that said an internal quarantine and some sort of safe mode added would be of great use to general users and developers.Of course with some limitations.. but nonetheless worthwhile to consider. Personally a feature like that would be a game changer for giving peace of mind to users and a great selling point for a flagship...Food for thought.

[Comment deleted]

Update to Nougat, my phone drained battery like hell. Its still a new phone , Lge g5 se

Still not fixed, why are you closed??? I'm very angry with this arrogant "I-close-evefything-even-if-its-still-a-bug-and-I-dont-feel-like-fixing-it". :-(

I interpreted this issue is caused by paradigm change of activity size in KITKAT.
I handled this issue by using ViewCompat.setOnApplyWindowInsetsListener() and setting paddingBottom by myself if windowTranslucentStatus is true.
This comment is interesting http://stackoverflow.com/a/28434211/4052730

Created new issue which is related: https://code.google.com/p/android/issues/detail?id=230855

There is a workaround can solve this bug: https://github.com/mikepenz/MaterialDrawer/issues/95
Code address: https://github.com/mikepenz/MaterialDrawer/blob/aa9136fb4f5b3a80460fe5f47213985026d20c88/library/src/main/java/com/mikepenz/materialdrawer/util/KeyboardUtil.java