Fixed
Status Update
No update yet.
Comments
ze...@gmail.com
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)
tw...@gmail.com
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).
sy...@google.com
Hi,
Thanks for reporting the issue. We are working on this issue and will provide updates as they are available.
Thanks...
Thanks for reporting the issue. We are working on this issue and will provide updates as they are available.
Thanks...
sy...@google.com
[Comment deleted]
ze...@gmail.com
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?
th...@gmail.com
Same issue here on Nexus 6P using Android 7.0 build NRD90T.
tw...@gmail.com
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.
tw...@gmail.com
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 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.
sy...@google.com
This issue is fixed internally and fix will be available in future releases.
ar...@gmail.com
Praise Duarte!
lb...@gmail.com
@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
th...@gmail.com
@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?
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?
da...@gokarumi.com
@10 Any news on this ? is the fix Removing "Show CPU usage" or it will be back in a future minor or major release ?
sa...@gmail.com
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.
sa...@gmail.com
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.
sy...@google.com
[Comment deleted]
mo...@gmail.com
Update to Nougat, my phone drained battery like hell. Its still a new phone , Lge g5 se
Description
You can see in the screenshot that the "Show CPU usage" feature from Developer Options only shows processes involving com.android.systemui, instead of a list of all top processes. This is likely a result of security enhancements related to isolation. It seems to me that the built-in developer tool should be allowed to break the rule. However, if this is the new normal, I suggest the list be removed from this overlay, since seeing only com.android.systemui processes is not useful.
Third-party applications cannot see any other processes either. In the screenshot, you can see Cool Tool at the top reporting that it is the highest-usage process, and OS Monitor reports only itself as well.
Due to API finalization it is probably too late to fix the problem by creating an API to allow such information access, so third-party process monitors are screwed, but in my opinion, the built-in developer option feature should be fixed.
Bug report (private):