Fixed
Status Update
Comments
el...@google.com <el...@google.com> #2
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)
el...@google.com <el...@google.com> #3
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).
el...@google.com <el...@google.com> #4
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...
gi...@gmail.com <gi...@gmail.com> #5
[Comment deleted]
[Deleted User] <[Deleted User]> #6
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?
el...@google.com <el...@google.com> #7
Same issue here on Nexus 6P using Android 7.0 build NRD90T.
gi...@gmail.com <gi...@gmail.com> #8
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.
[Deleted User] <[Deleted User]> #9
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.
el...@google.com <el...@google.com> #10
This issue is fixed internally and fix will be available in future releases.
[Deleted User] <[Deleted User]> #11
Praise Duarte!
Description
We recently migrated our queries to standard SQL syntax. Everything was going pretty well until we realise the HASH method from the legacy SQL syntax was not available anymore in standard SQL.
Is there a HASH (sha1) function available in the standard SQL syntax? If not, is there a workaround to this issue or any feature development scheduled in the roadmap?
Thanks,
Pierre