I upgraded a Google Pixel 6 to Android 16, and something truly weird is happening. Typically, in the afternoon, out of nowhere, the battery QUICKLY descends to 0%. I set up a Tracker app task to catch this early on, and I am sitting there watching the percentages drop by about two percent every second. Something is very aggressively eating CPU. I don't even understand how that level of battery use is possible. Even if a system routine got stuck and looped, how could it use up battery that way?
I enabled developer mode, and I have a Perfetto trace file of CPU usage during a two-minute period after this problem started. I catch the problem, plug the phone into power so that I don't lose my environment from power loss, and then I do the trace. I don't understand what to look for in the trace output that I get from the Perfetto Dev UI. Can someone point me to a video that would explain how I can use this trace to identify a rogue process? I'm not trying to learn every feature in Perfetto. I am trying to focus on identifying which process is consuming all the CPU.
I did use the Battery Usage feature, and I don't see any application there taking more than 25% of CPU. And even if an application was taking 90%, I don't see how it could run the battery down this quickly.
Is the behavior I am describing possibly a hardware failure in the battery?
I enabled developer mode, and I have a Perfetto trace file of CPU usage during a two-minute period after this problem started. I catch the problem, plug the phone into power so that I don't lose my environment from power loss, and then I do the trace. I don't understand what to look for in the trace output that I get from the Perfetto Dev UI. Can someone point me to a video that would explain how I can use this trace to identify a rogue process? I'm not trying to learn every feature in Perfetto. I am trying to focus on identifying which process is consuming all the CPU.
I did use the Battery Usage feature, and I don't see any application there taking more than 25% of CPU. And even if an application was taking 90%, I don't see how it could run the battery down this quickly.
Is the behavior I am describing possibly a hardware failure in the battery?
