[QUESTION/NEED HELP] maxed out cpu usage (little core) stays at 1593 mhz

[kingbri]

I need help because my phone is maxed out at 1593 mhz which is the max clock speed for the cpu small cluster. The big cluster is working fine. This is NOT a result of KingKernel, it happens on any kernel I run. The cpu usage goes up to 95 or sometimes 100%. I think the task is play services through a battery historian I took, but I'm not sure.

I am currently on Android P preview 5 and it is a literal hot mess. I have reported this to google, but I need some immediate help. Thanks in advance

 

[kingbri]

This happened randomly, it wasn't right after I flashed P, it worked properly before

 

[Bryanx86]

This happened randomly, it wasn't right after I flashed P, it worked properly before

Doing the same thing on my phone, I've been trying to troubleshoot it, also on dp5. Tried setting it lower in ex kernel manager and resets to 1593 every time. Without even rebooting. Probably play services needs an update....

---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------

I flashed thedp5 to the b slot and it seems to be trying to settle down now. I had the wrong bb and bl on that slot.

 

[kingbri]

Doing the same thing on my phone, I've been trying to troubleshoot it, also on dp5. Tried setting it lower in ex kernel manager and resets to 1593 every time. Without even rebooting. Probably play services needs an update....

---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------

I flashed thedp5 to the b slot and it seems to be trying to settle down now. I had the wrong bb and bl on that slot.

It's starting to settle down when flashing from B to A (I had it on B before) good to hear that this isn't happening to only me.

 

[kingbri]

deleted

 

[Bryanx86]

It's starting to settle down when flashing from B to A (I had it on B before) good to hear that this isn't happening to only me.

Yeah, and it seems my fast charge isn't working as well. Gamn doogle!

 

[Dragon Kumera]

Has anyone fixed this? I had this issue since forever and am on lineage os 17.1