OxygenOS 10.0.7 unexplainable heating and battery drain

  1. kKoI1233
    Gingerbread Dec 15, 2019

    kKoI1233 , Dec 15, 2019 :
    To explain what kind of user I am, let me start off by saying that the battery life on 10.0.6 and prior was just fine by me.
    Yes you hear me correctly I'm not some random user with spoiled complains about battery life.

    Okay, having that out of the way I noticed some weird things since the new update:

    1. The phone is warmer than usual (not just judging by feeling, screenshot below)
    2. The phone drained all the way to 0% overnight (this never happened to me before)

    just noticed this one,
    3. For some reason the phone is using the prime core of the SD 855+ during medial tasks.

    In the screenshot below, I have not many apps running, only have EX kernel manager and YouTube running yet for some reason the CPU prime core (this highest clocked core, u know the one reserved for very demand loads such as playing CODM or benchmarks)

    I am almost sure that that's why the phone is warmer than usual and drains battery faster than usual

    My second screenshot shows how the prime core is indeed the one being ran at it's max max frequency for the past 6 hours (even though i haven't used my phone for at least 4 hours this evening)



    Ebojager likes this.
  2. kKoI1233
    Gingerbread Dec 15, 2019

    kKoI1233 , Dec 15, 2019 :
    Temporary fix for this can be manually setting the max frequency for cluster 3 (the prime core) to the lowest value possible, my CPU temperature went down by 15 degrees Celsius simply doing that and probably saves the battery too

    This alone doesn't work, for optimal results you need to lock all cores to their lowest values

    The moment you lock the prime core to lowest value (845mhz) the big cores max out (2400mhz) and then when you lock those down to their lowest value (710mhz) then the little cores will max out until you locl those down to their lowest value (300mhz) and then they boost up to 1500mhz when you touch the screen for a less than a second which is normal
    Last edited: Dec 15, 2019

  3. kKoI1233
    Gingerbread Dec 15, 2019

  4. Deathwish217
    Eclair Dec 15, 2019

  5. kKoI1233
    Gingerbread Dec 15, 2019

    kKoI1233 , Dec 15, 2019 :
    I used the app EX Kernel manager, but I am also using Franco Kernel manager now to see if my readings are accurate or not.

    I believe CPU-Z also shows the current frequencies but haven't checked

  6. kKoI1233
    Gingerbread Dec 15, 2019

    kKoI1233 , Dec 15, 2019 :
    Yesterday i stayed up all night trying to figure it out

    Here is a list of everything I tried:
    Wiping Dalvik cache
    Changing CPU governor
    Locking max CPU frequencies (works!)

    Factory reset
    Local upgrade AFTER factory reset (works!, until trying to root)

    after local upgrade it works fine but the second you boot up a patched boot.img to root the issue will be back and after rooting the issue will still be present

    That said, CPU usage isn't particularly high but the frequencies stay maxed out

  7. Deathwish217
    Eclair Dec 15, 2019

    Deathwish217 , Dec 15, 2019 :
    does phone have to be rooted for it haven't gotten around to doing it

  8. kKoI1233
    Gingerbread Dec 15, 2019

    kKoI1233 , Dec 15, 2019 :
    In order to check the frequencies you don't have to be rooted but in order to lock them to certain values you will need to be rooted and have a custom kernel.

    The issues only seem to be present when rooted, so if you are on 10.0.7 don't root i guess? 10.0.6 root works fine, so fine i wish i could downgrade

    M1571074916431 likes this.
  9. kKoI1233
    Gingerbread Dec 17, 2019

    kKoI1233 , Dec 17, 2019 :
    I figured i would update this thread with my newfound information

    vendor.oneplus.hardware.brain@1.0-service using up that CPU, THAT is the process that is pushing the phone into heating and draining

    oh yea and killing it doesn't work

    Attached Files: