Obsolete
Status Update
No update yet.
Comments
lb...@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)
lb...@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).
lb...@gmail.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...
he...@gmail.com
[Comment deleted]
lb...@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?
he...@gmail.com
Same issue here on Nexus 6P using Android 7.0 build NRD90T.
lb...@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.
he...@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.
lb...@gmail.com
This issue is fixed internally and fix will be available in future releases.
he...@gmail.com
Praise Duarte!
ni...@google.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
Description
Version used:
compile 'com.android.support:appcompat-v7:25.3.1'
compile 'com.android.support:design:25.3.1'
Theme used:
default
Devices/Android versions reproduced on:
Nexus 5 with Android 6.0.1. Also on emulator with Android 7.0.
- Relevant code to trigger the issue.
Code is too large so I've attached a sample project, but in short, it has :CoordinatorLayout, AppBarLayout,CollapsingToolbarLayout, and a RecyclerView.
Under some cases, when we call setNestedScrollingEnabled(false) , the scrolling inside the RecyclerView is being semi-blocked. Meaning: if you try to scroll slowly, it tries to go back like a spring.
On the emulator, what I did get it to do is that when I scroll down or scroll up, it still scrolls down.
The purpose I used this function is to only (temporarily) avoid the expanding/collapsing of the CollapsingToolbarLayout upon scrolling in the RecyclerView. It works, but it also has this issue sometimes.
It's a bit hard to reproduce, but once it occurs, it becomes easy.
- A screenrecord or screenshots showing the issue (if UI related).
Attached for both device and emulator. Notice that the issue is shown only on the end of the videos.