[ROM][13][POLARIS] Pixel Experience BETA [AOSP][2022/09/14]

Search This thread

dRm42

Senior Member
Aug 17, 2011
123
86
Xiaomi Mi Mix 2S
My CPU core frequencies do fluctuate. They might be a bit higher than I'd expect but they're definitely not stuck at peak. However, the logs are flooded with IllegalStateException entries, at the rate of about 30 exceptions per second. I'm wondering if it's the exception handling that drives the frequency higher than it should be. That is, if this is common and isn't unique to my device only. Might be a red herring though.

Code:
06-17 10:11:39.548  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.03 seconds.
06-17 10:11:39.554  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
06-17 10:11:39.559  3572  7429 W SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
06-17 10:11:39.559  3572  7429 W SystemUpdate: java.lang.IllegalStateException
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at wjj.j(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at bkgz.f(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at bkfs.a(:[email protected]@22.18.59 (190400-453522955):10)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):12)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at com.google.android.chimera.IntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at uim.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):4)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at ewd.run(:[email protected]@22.18.59 (190400-453522955):3)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at ewc.run(:[email protected]@22.18.59 (190400-453522955):11)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at cdgo.run(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.lang.Thread.run(Thread.java:920)
06-17 10:11:39.585  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.03 seconds.
06-17 10:11:39.590  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
06-17 10:11:39.595  3572  7429 W SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
06-17 10:11:39.595  3572  7429 W SystemUpdate: java.lang.IllegalStateException
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at wjj.j(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at bkgz.f(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at bkfs.a(:[email protected]@22.18.59 (190400-453522955):10)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):12)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at com.google.android.chimera.IntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at uim.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):4)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at ewd.run(:[email protected]@22.18.59 (190400-453522955):3)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at ewc.run(:[email protected]@22.18.59 (190400-453522955):11)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at cdgo.run(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.lang.Thread.run(Thread.java:920)
 

Attachments

  • screen-20220617-102331.mp4
    5.2 MB · Views: 0
  • logcat.log
    10.5 MB · Views: 7

Gookmk

Member
Jul 1, 2021
38
1
It seems to be this is problem (stuck frequency) not only mine. The last time it continued about few days and then I'm updated and all was ok but now it doesn't help. It's definitely software problem i think.
 
Last edited:

jjpprrrr

Senior Member
Nov 27, 2018
965
881
jjpprrrr.com
My CPU core frequencies do fluctuate. They might be a bit higher than I'd expect but they're definitely not stuck at peak. However, the logs are flooded with IllegalStateException entries, at the rate of about 30 exceptions per second. I'm wondering if it's the exception handling that drives the frequency higher than it should be. That is, if this is common and isn't unique to my device only. Might be a red herring though.

Code:
06-17 10:11:39.548  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.03 seconds.
06-17 10:11:39.554  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
06-17 10:11:39.559  3572  7429 W SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
06-17 10:11:39.559  3572  7429 W SystemUpdate: java.lang.IllegalStateException
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at wjj.j(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at bkgz.f(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at bkfs.a(:[email protected]@22.18.59 (190400-453522955):10)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):12)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at com.google.android.chimera.IntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at uim.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):4)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at ewd.run(:[email protected]@22.18.59 (190400-453522955):3)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at ewc.run(:[email protected]@22.18.59 (190400-453522955):11)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at cdgo.run(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.lang.Thread.run(Thread.java:920)
06-17 10:11:39.585  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.03 seconds.
06-17 10:11:39.590  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
06-17 10:11:39.595  3572  7429 W SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
06-17 10:11:39.595  3572  7429 W SystemUpdate: java.lang.IllegalStateException
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at wjj.j(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at bkgz.f(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at bkfs.a(:[email protected]@22.18.59 (190400-453522955):10)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):12)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at com.google.android.chimera.IntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at uim.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):4)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at ewd.run(:[email protected]@22.18.59 (190400-453522955):3)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at ewc.run(:[email protected]@22.18.59 (190400-453522955):11)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at cdgo.run(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.lang.Thread.run(Thread.java:920)
Here is the thing. The cpu frequency is governed automatically according to the load. If the kernel sees a heavy load, it will temporarily raise the frequency to finish the tasks more quickly. This is the essence of "Energy Aware Scheduling".

When raising the frequency, the governor calculates the potential "cost of energy" after the frequency change, and will try to minimize the cost. Sometimes the situation is counter-intuitive: running at lower frequency does not always save energy. If say a task can be done at a higher frequency within 100ms, but needs 2000ms at a the minimum frequency. Raising the frequency may actually save power compared to letting the cpu stay at the minimum frequency.

Now back to the topic. Why do you see more "2.8GHz" on the big cluster? There can be many reasons.

1. SDM845 is an old SoC. Its overall performance is about 40% of 888 (taking both single-threaded and multi-threaded into account). This is the year of 2022, not 2018. Apps are significantly heavier than 4 years ago. The CPU is more likely to see a relatively heavy load, so it will raise the frequency more often to match the load.

2. Android has some mechanisms to boost the CPU frequency even higher for certain tasks. Some tasks are latency sensitive, which means they are better to be completed as soon as possible. Such tasks include real-time audio processing, UI rendering, radio stuff, etc.. When these types of tasks are running, the android system will give the kernel a "hint" to boost the frequency even higher than normal.

In conclusion, the kernel does not lie. As long as the frequency is not hard stuck at a certain level, it is not a bug. If you see high frequencies very often, it only means your phone is running heavy tasks.

The kernel scheduler and frequency governor have not been changed for months, or even years, so there shouldn't be any regression suddenly happening recently.
 

Gookmk

Member
Jul 1, 2021
38
1
I think it's definitely software problem. Btw, the much older phones works fine on PE12 without problem with stuck frequency. It started randomly but definitely something wrong with personally PE12 on Mix 2s, don't heard about the same problem at Mi 8
 
Last edited:

jjpprrrr

Senior Member
Nov 27, 2018
965
881
jjpprrrr.com
I think it's definitely software problem. Btw, the much older phones works fine on PE12 without problem with stuck frequency. It started randomly but definitely something wrong with personally PE12 on Mix 2s, don't here about the same problem at Mi 8
Lol both Mi 8 and Mix 2s are using the same code from me. They should behave exactly the same.
 

dRm42

Senior Member
Aug 17, 2011
123
86
Xiaomi Mi Mix 2S
Here is the thing. The cpu frequency is governed automatically according to the load. If the kernel sees a heavy load, it will temporarily raise the frequency to finish the tasks more quickly. This is the essence of "Energy Aware Scheduling"....
I think you've misunderstood me. What I'm saying is essentially the same as what you're saying. My CPU frequencies do fluctuate - ie they go up and down as they should. They're definitely not stuck at peak for me. The point I was trying to make with the lots of exceptions is that if there are 30 exceptions per second, and exception handling is done in "race to idle" (handle it as fast as possible then go back to normal frequency) then it could potentially drive the CPU frequencies higher. If, in addition to that, guys use more demanding apps, the higher base line freq (due to the exceptions) might cause the CPU frequency to stay close to peak most of the time and might give them the impression that it's stuck and buggy when it isn't.

Then again, no one else complained about similar amount of exceptions so it's probably just my phone, or something that I use. Now that I'm writing this, I'm thinking it might be Vanced MicroG that YouTube Vanced uses. It just presents itself as GMS in the logs.
 

Gookmk

Member
Jul 1, 2021
38
1
I think you've misunderstood me. What I'm saying is essentially the same as what you're saying. My CPU frequencies do fluctuate - ie they go up and down as they should. They're definitely not stuck at peak for me. The point I was trying to make with the lots of exceptions is that if there are 30 exceptions per second, and exception handling is done in "race to idle" (handle it as fast as possible then go back to normal frequency) then it could potentially drive the CPU frequencies higher. If, in addition to that, guys use more demanding apps, the higher base line freq (due to the exceptions) might cause the CPU frequency to stay close to peak most of the time and might give them the impression that it's stuck and buggy when it isn't.

Then again, no one else complained about similar amount of exceptions so it's probably just my phone, or something that I use. Now that I'm writing this, I'm thinking it might be Vanced MicroG that YouTube Vanced uses. It just presents itself as GMS in the logs.
Look at big cores frequency, it's max 2803 always, everytime and the phone don't drop the frequency, i don't use any 3rd kernel, any root or any heavy apps, all stock. It's just started randomly. The phone always hold the max frequency of cores, first little (1766) and then big (2803) all the time. And because of that there is battery drain so fast, and the phone is hot.
 

Attachments

  • Screenshot_20220618-081720_AIDA64.png
    Screenshot_20220618-081720_AIDA64.png
    223.2 KB · Views: 15

JaggerPrincess

New member
Jun 18, 2022
2
0
My CPU core frequencies do fluctuate. They might be a bit higher than I'd expect but they're definitely not stuck at peak. However, the logs are flooded with IllegalStateException entries, at the rate of about 30 exceptions per second. I'm wondering if it's the exception handling that drives the frequency higher than it should be. That is, if this is common and isn't unique to my device only. Might be a red herring though.

Code:
06-17 10:11:39.548  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.03 seconds.
06-17 10:11:39.554  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
06-17 10:11:39.559  3572  7429 W SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
06-17 10:11:39.559  3572  7429 W SystemUpdate: java.lang.IllegalStateException
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at wjj.j(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at bkgz.f(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at bkfs.a(:[email protected]@22.18.59 (190400-453522955):10)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):12)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at com.google.android.chimera.IntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at uim.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):4)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at ewd.run(:[email protected]@22.18.59 (190400-453522955):3)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at ewc.run(:[email protected]@22.18.59 (190400-453522955):11)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at cdgo.run(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.lang.Thread.run(Thread.java:920)
06-17 10:11:39.585  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.03 seconds.
06-17 10:11:39.590  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
06-17 10:11:39.595  3572  7429 W SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
06-17 10:11:39.595  3572  7429 W SystemUpdate: java.lang.IllegalStateException
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at wjj.j(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at bkgz.f(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at bkfs.a(:[email protected]@22.18.59 (190400-453522955):10)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):12)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at com.google.android.chimera.IntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at uim.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):4)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at ewd.run(:[email protected]@22.18.59 (190400-453522955):3)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at ewc.run(:[email protected]@22.18.59 (190400-453522955):11)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at cdgo.run(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.lang.Thread.run(Thread.java:920)
[/
[QUOTE="dRm42, post: 87033455, member: 4221224"]
My CPU core frequencies do fluctuate. They might be a bit higher than I'd expect but they're definitely not stuck at peak. However, the logs are flooded with IllegalStateException entries, at the rate of about 30 exceptions per second. I'm wondering if it's the exception handling that drives the frequency higher than it should be. That is, if this is common and isn't unique to my device only. Might be a red herring though.

[CODE]06-17 10:11:39.548  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.03 seconds.
06-17 10:11:39.554  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
06-17 10:11:39.559  3572  7429 W SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
06-17 10:11:39.559  3572  7429 W SystemUpdate: java.lang.IllegalStateException
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at wjj.j(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at bkgz.f(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at bkfs.a(:[email protected]@22.18.59 (190400-453522955):10)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):12)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at com.google.android.chimera.IntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at uim.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):4)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at ewd.run(:[email protected]@22.18.59 (190400-453522955):3)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at ewc.run(:[email protected]@22.18.59 (190400-453522955):11)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at cdgo.run(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-17 10:11:39.559  3572  7429 W SystemUpdate:     at java.lang.Thread.run(Thread.java:920)
06-17 10:11:39.585  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pending executed for 0.03 seconds.
06-17 10:11:39.590  3572  7429 I SystemUpdate: [Execution,ExecutionManager] Action pre-download-validate executed for 0.00 seconds.
06-17 10:11:39.595  3572  7429 W SystemUpdate: [Execution,ExecutionManager] Unable to create the action. Restart the execution from the scratch.
06-17 10:11:39.595  3572  7429 W SystemUpdate: java.lang.IllegalStateException
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at wjj.j(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at bkgz.f(:[email protected]@22.18.59 (190400-453522955):0)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at bkfs.a(:[email protected]@22.18.59 (190400-453522955):10)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):12)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at com.google.android.chimera.IntentOperation.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at uim.onHandleIntent(:[email protected]@22.18.59 (190400-453522955):4)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at ewd.run(:[email protected]@22.18.59 (190400-453522955):3)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at ewc.run(:[email protected]@22.18.59 (190400-453522955):11)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at cdgo.run(:[email protected]@22.18.59 (190400-453522955):2)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-17 10:11:39.595  3572  7429 W SystemUpdate:     at java.lang.Thread.run(Thread.java:920)
i have exactly the same problem, i already tried to delete vanced yt, but the problem is still the same. Im testing with Play Services, when I force stop, the requests change
[/QUOTE]
 

dRm42

Senior Member
Aug 17, 2011
123
86
Xiaomi Mi Mix 2S
Look at big cores frequency, it's max 2803 always, everytime and the phone don't drop the frequency, i don't use any 3rd kernel, any root or any heavy apps, all stock. It's just started randomly. The phone always hold the max frequency of cores, first little (1766) and then big (2803) all the time. And because of that there is battery drain so fast, and the phone is hot.
It's not like that for me. Perhaps, try formatting your cache partition from recovery, then give it a day to settle and see if the issue persists. It's more than likely that it's something with your device or your software environment (ie apps that you're running).
 

Gookmk

Member
Jul 1, 2021
38
1
Some people say that on latest Evolution (Mix 2S) it's the same problem. It's started about 2-3 days ago.
 
Last edited:

Gookmk

Member
Jul 1, 2021
38
1
It's not like that for me. Perhaps, try formatting your cache partition from recovery, then give it a day to settle and see if the issue persists. It's more than likely that it's something with your device or your software environment (ie apps that you're running).
I'm doing this (formatting cache partition) at this moment nothing is change. At this moment there is 5 people say that they have the same problem on PE12 and Evolution. So this is definitely not only mine problem. Maybe something wrong in between googles apps/services updates and PE12/Evo/
 
Last edited:

jjpprrrr

Senior Member
Nov 27, 2018
965
881
jjpprrrr.com
Some people say that on latest Evolution (Mix 2S) it's the same problem. It's started about 2-3 days ago.
I haven't confirmed yet, but I suspect it has something to do with Google pushing system updates to Pixels. Basically PE (and evox) spoofs the system as a Pixel device, so naturally Google might try to push a system update to it. Previously PE blocked certain Google domains so the update will either never arrive, or fail peacefully. I suspect Google probably changed the mechanism, and a process in the background was stuck there trying to access a domain to get the update.
 
  • Like
Reactions: dRm42

wizerspoon13

Member
Oct 20, 2015
12
4
Uh the frequency was switching rapidly in your screenshot. I wouldn't call that "stuck at maximum".
Its bug. Because two weeks ago the frequency did not jump, and did not stuck it at the maximum frequency all the time. If I reinstall this firmware, then everything will work correctly. But in two weeks this bug will appear again. The frequency of my device in idle time on all firmwares: small cluster - 576mHz, big cluster - 824mHz.
 

Gookmk

Member
Jul 1, 2021
38
1
I haven't confirmed yet, but I suspect it has something to do with Google pushing system updates to Pixels. Basically PE (and evox) spoofs the system as a Pixel device, so naturally Google might try to push a system update to it. Previously PE blocked certain Google domains so the update will either never arrive, or fail peacefully. I suspect Google probably changed the mechanism, and a process in the background was stuck there trying to access a domain to get the update.
Sounds bad. So what we need to do to fix it? Cause it's very uncomfortable. Maybe some quick fix? P.S. In 4pda forum there is many people with this problem at this time.
 
Last edited:

wizerspoon13

Member
Oct 20, 2015
12
4
Sounds bad. So what we need to do to fix it? Cause it's very uncomfortable. Maybe some quick fix? P.S. In 4pda forum there is many people with this problem at this time.
Ok guys, I found a fix for the problem. You need to go to the permission settings of Google services, and disable / ask every time:
1. access to the camera
2. microphone access
3. body sensors
4. nearby devices.
And you need to prohibit google services from changing system settings.

P.s. now let the developer make his move
 

Attachments

  • Screenshot_20220619-000746_Pixel Launcher.png
    Screenshot_20220619-000746_Pixel Launcher.png
    415 KB · Views: 38
  • Screenshot_20220619-001202_Контролер разрешений.png
    Screenshot_20220619-001202_Контролер разрешений.png
    163.2 KB · Views: 37
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    2022/09/14
    Initial android 13 release.
    Flash guide, changelog, and known issues: https://jjpprrrr.com/pe/20220914-1603/
    2
    Since the last rom update, my Google Messages chat features have been stuck in conneting.
    After wiping the application data, it went back to the good old infinite "setting up...".

    I finally found a workaround for this. Turn on wifi and off mobile data, disable and reenable chat features and it should connect.
    2
    When can we expect stable and plus versions? Greetings
    The beta is pretty much already stable.
    The plus version I think is still being worked on in the main Pixel Experience project. When it finishes there, it can be ported here.
    1
    I have that unchecked and it still does the same.
    I think the issue is the light sensor reading 0 lux when there's light in the room albeit only a little.
    Just fyi this issue only happens on this ROM, LOS18.1 doesn't do this.
    Either fix sensor readings or raise default minimum screen brightness.
    On adaptive brightness, I think it's not working well because every time the screen is dim I raise the brightness level manually, but it does not seem to remember my settings.
    Now that I'm reading this, I probably had the same issue earlier, I just didn't dig deep enough to get to the sensor readings. In the end I solved it with a very simple Tasker task. When the light is dim, I disable adaptive brightness and set brightness to a fixed value of my liking. This basically overrides the minimum, as brightness level can never go lower than my set value. When the readings go back up, I re-enable adaptive brightness so that the screen can auto-adjust as normal. This has been working fine for many months now.
    1
    Thank you for the update.
    Unfortunately I install the new Recovery without problem but when I try to instal the ROM (the unofficial one first) I receive this message:

    PS C:\adb> adb devices List of devices attached 2b38ca01 sideload PS C:\adb> adb sideload ROM1.zip * cannot read 'ROM1.zip' *
    You need to update your platform-tools (the one that contains adb, fastboot, etc.).
  • 52

    GtwTyCR.png


    PixelExperience for Xiaomi Mi Mix 2s [polaris]

    What is this?
    Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)

    Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device

    Based on Android 13


    Whats working?
    Wifi
    RIL
    Mobile data
    GPS
    Camera
    Flashlight
    Bluetooth
    Fingerprint reader
    NFC
    Lights
    Sound / vibration


    Known issues
    Refer to the changelog for known issues.

    DO NOT FLASH GAPPS, ALREADY INCLUDED
    Download from Pixel Experience website

    Translation
    Help with project translation

    Stay tuned
    Our Telegram channel
    Our blog
    Donate me
    My personal website for build updates and flash guide




    Android OS version: 13.0.0_r4
    Security patch level: September, 2022
    Build author/Device Maintainer: jjpprrrr
    Device and Kernel Source code: https://github.com/PixelExperience-Devices
    Source code: https://github.com/PixelExperience
    ROM Developer: jhenrique09
    15
    Reserved

    2022/09/14

    Initial android 13 release.
    Flash guide, changelog, and known issues: https://jjpprrrr.com/pe/20220914-1603/

    2022/08/28
    Changelog: https://jjpprrrr.com/pe/20220828-0030/

    2022/08/16

    2022/07/13

    2022/06/28
    Changelog: https://jjpprrrr.com/pe/20220628-1638/

    2022/05/21
    Changelog: https://jjpprrrr.com/pe/20220521-0400/

    2022/04/15
    Changelog: https://jjpprrrr.com/pe/20220415-1325/

    2022/03/31
    Changelog: https://jjpprrrr.com/pe/20220331-1355/

    2022/02/24
    Changelog: https://jjpprrrr.com/pe/20220224-1209/

    2022/01/22
    PE 12 Changelog: https://jjpprrrr.com/pe/20220122-0913/

    2022/01/21
    PE 12 Changelog: https://jjpprrrr.com/pe/20220121-0407/

    2021/12/23
    PE 12 Stable:
    Changelog: https://jjpprrrr.com/pe/20211223-0300/
    PE 11 / 11 Pus:
    Changelog: https://jjpprrrr.com/pep/20211223-0443/

    2021/11/28
    Initial PE 12 BETA official release.
    Changelog: https://jjpprrrr.com/pe/20211128-0611/

    2021/10/20
    Unofficial ALPHA PE 12 builds are available on my website: https://jjpprrrr.com/

    2021/10/11
    PE changelog: https://jjpprrrr.com/pe/20211011-2303/
    PE Plus changelog: https://jjpprrrr.com/pep/20211012-0004/

    2021/09/11
    PE changelog: https://jjpprrrr.com/pe/20210911-0532/
    PE Plus changelog: https://jjpprrrr.com/pep/20210911-0606/

    2021/08/18
    PE changelog: https://jjpprrrr.com/pe/20210818-0017/
    PE Plus changelog: https://jjpprrrr.com/pep/20210818-0016/

    2021/07/20
    PE changelog: https://jjpprrrr.com/pe/20210720-1512/
    PE Plus changelog: https://jjpprrrr.com/pep/20210720-1512/

    2021/07/17
    PE changelog: https://jjpprrrr.com/pe/20210717-2122/
    PE Plus changelog: https://jjpprrrr.com/pep/20210717-2122/

    2021/06/25
    PE changelog: https://jjpprrrr.com/pe/20210625-2017/
    PE Plus changelog: https://jjpprrrr.com/pep/20210625-2017/

    2021/06/19
    PE changelog: https://jjpprrrr.com/pe/20210619-0238/
    PE Plus changelog: https://jjpprrrr.com/pep/20210619-0241/

    2021/05/26
    PE changelog: https://jjpprrrr.com/pe/20210526-0015/
    PE Plus changelog: https://jjpprrrr.com/pep/20210526-0010/

    2021/05/14
    PE changelog: https://jjpprrrr.com/pe/20210514-0431/
    PE Plus changelog: https://jjpprrrr.com/pep/20210514-0428/
    Note: The official PE website is migrating to a new storage provider, and the download may be slow in some regions. Please be patient and try again later if you encounter any download issues.

    2021/04/17
    PE changelog: https://jjpprrrr.com/pe/20210417-0245/
    PE Plus changelog: https://jjpprrrr.com/pep/20210417-0245/

    2021/03/27
    PE changelog: https://jjpprrrr.com/pe/20210327-1844/
    PE Plus changelog: https://jjpprrrr.com/pep/20210327-1844/

    2021/03/10
    PE changelog: https://jjpprrrr.com/pe/20210310-2136/
    PE Plus changelog: https://jjpprrrr.com/pep/20210310-2347/

    2021/02/18
    Changelog: https://jjpprrrr.com/pe/20210218-1327/

    2021/02/07
    Changelog: https://jjpprrrr.com/pe/20210207-0205/

    2021/01/19
    Changelog: my website

    2021/01/07
    Changelog: my website

    2020/12/23
    Changelog: My Website

    2020/11/29
    Changelog: my website

    **Device Specific Changes:**
    - Etude kernel:
    * DO NOT use a third party kernel without proper support for Pixel thermal hal
    * Linux 4.9.246
    * merged CAF R tag LA.UM.9.8.r1-03000-SDM710.0
    * modified DT bindings for Pixel thermal hal
    * enabled zram writeback
    * fixed zram idle and writeback string compare
    * added a killable freezer to kill frozen tasks similar to cgroups v2
    * increased top-app boost
    - Switched to Pixel thermal 2.0
    * also updated thermal engine from Pixel 3 XL android 11 build
    - Updated HDR, SDM, Adreno, Vulkan, Snapdragon CVE, WFD vendor, media, configstore, dpm vendor, DRM, msm_irqbalance, peripheral manager, power-off alarm, time service, TEE, TUI, ESE power manager, CNE, IMS, QMI, and RIL from LA.UM.9.8.r1-02700-SDM710.0
    - Updated WFD system, dpm system, and Widevine blobs from OnePlus8Pro android 11 image
    - Updated the following hal versions
    * Secure Element --> 1.2
    * wfdhdcp --> 1.3
    * health --> 2.1
    * ESE power manager --> 1.1
    * QTI Health implementation --> 2.1
    * IRadio --> 1.5
    * uceservice --> 2.2
    * ims factory --> 1.0
    * qti radio --> 2.4
    * ims rtp service --> 3.0
    * removed qdutils_disp
    * added IVr
    - Switched to CAF R display and media hal
    * screen brightness is now controlled by hwc instead of light HAL, which offers a smooth and accurate brightness adjustment without weird hacks I did on android 10
    * display config 2.0
    * set higher priority to c2 than OMX
    * removed deprecated divx/xvid software codecs
    * cleaned up and merged redundant media codec configs
    - Switched to stable aidl Pixel power hal
    * removed UfsHibern8Enable and clkgate_enable hints in launch and interaction because it may freak out ufshc
    - Switched to AOSP NFC 1.2
    - Switched to AOSP BT stack for now
    - Enabled IORap
    * IORap is a new feature in android 11 that greatly improves app startup time by predicting and prefetching potentially blocking I/O
    - Enabled zram writeback in fstab and job scheduler
    - Added AOSP RCS packages and removed deprecated RCS
    - Bumped audio hal to 6.0
    - Enabled the option to turn on blur in developer settings (defaults to disabled)
    * Note: blur is very expensive on rendering and may incur jank frames
    - Added WifiOverlay
    - Added TetheringOverlay
    - Enabled dex2oat64
    - SELinux enforcing and SafetyNet passes out of the box
    * if you use Magisk, you may need to turn on MagiskHide

    **Feature update highlights:**
    - Initial android 11 release with many Pixel features from Pixel 5.

    **Known issues:**
    - "OK Google" hot word does not work yet


    ====================================
    Old changelogs on android 10 builds:

    2020/11/22
    **Device Specific Changes:**
    - Etude kernel:
    * Linux 4.9.243
    * wireguard 1.0.20201112
    * merged upstream fix on ipv6, vsoc, tee, and thermal from android common kernel
    - Fixed audio stuttering in video playback, when you are also in a voice call using BlueTooth headset
    - Removed unused vndk-sp
    - Added AOSP RCS package and removed deprecated packages
    - Added vendor manifest entry for CACert HAL
    - Added default BTSAR HAL entry
    - Parts: updated API of getting focused stack info
    - Removed some ims entries from init script because they are included in vendor

    **Feature update highlights:**
    - November security patch
    - Translation update
    - Some under the hood fixes and improvements to make your experience even better

    2020/10/15
    **Device Specific Changes:**
    - Etude kernel:
    * Linux 4.9.239
    * fixed a camera memory leak
    * disabled unused wsa881x codecs
    * changed China regulatory domain

    **Feature update highlights:**
    - October security patch (bumped the version string)
    - Translation update

    Note: Incremental update for 20201015 build has been removed from server, due to unknown issue causing error 7 in recovery. The system updater will grab the full package instead. If you had issue flashing incremental update, download the full package and flash it in recovery.

    2020/09/16
    **Device Specific Changes:**
    - Etude kernel:
    * wireguard 1.0.20200908
    - Fixed an issue where the screen has extremely low brightness when woken up by notifications

    **Feature update highlights:**
    - Fixed missing security patch in Settings - Security
    - Fixed potentially duplicated Styles package
    - More translation updates

    2020/09/15
    **Device Specific Changes:**
    - Etude kernel:
    * Linux 4.9.236
    * fpc and goodix fingerprint: use qcom drm notifier instead of the generic one
    * fixed xbl_region reserved memory
    - Reworked screen panel backlight
    * in previous builds
    - adjusting brightness slider in the lower range resulted in uneven brightness transition
    - previous builds did not allow screen to dim to the lowest possible value
    - auto-brightness had slow reaction to ambient light changes
    * patched frameworks/base to use linear brightness slider instead of the log scale one
    * ported gamma-linear conversion to light HAL
    * re-calculated auto brightness curve to fit new light HAL changes
    * reduced light sensor debounce time to stay in-line with MIUI
    * the result:
    - smooth backlight brightness transition when moving brightness slider
    - screen can dim to the lowest possible value the panel allows
    - auto-brightness reacts faster to ambient light changes
    - auto-brightness is no longer jumpy
    - screen dimming caused by no user action has proper transitions

    **Feature update highlights:**
    - September security patch
    - PE Plus: Added pocket lock
    - Improved face unlock
    - Updated translations
    - Under-the-hood fixes and improvements

    2020/08/31
    **Device Specific Changes:**
    - Etude kernel:
    * Linux 4.9.234
    * built with latest Clang 12
    * improved suspend/resume latency
    * some misc fixes on arm64 and mm
    - updated firmware and vendor from MIUI 12 Global Stable V12.0.1.0
    - use qti-telephony-common from polaris dump for injection
    - fixed an issue where mobile data on one SIM may be broken after the other SIM receives a phone call or SMS
    - fixed a few sepolicy issues for sched_boost and sysfs_batteryinfo
    - cleaned up Google specific hints from powerhint

    **Feature update highlights:**
    - Misc fixes

    2020/08/18
    - Etude kernel:
    * Linux 4.9.232
    * built with latest Clang 12
    * wireguard 1.0.20200729
    * disabled LLVM Polly
    * merged some loop device backports from upstream
    * some scheduler changes on idle load
    * upstream on mm, qspinlock, and arm/arm64 specific libs
    - created dummy perfd client so that proprietary perfd blobs can be removed while keeping goodix fingerprint sensor functioning
    - disabled kpi_optimize in audio extension because it tries to call perfd and spams logs when failed
    - re-introduced an updated qti-telephony-common injection to polaris
    * this fixed mms issue on some Korean carriers
    - dropped wifi-ext
    - Updated APNs for Chinese carriers and fixed "HD" capable notification spam
    - Bumped Vulkan feature level to 1
    - Enabled 802.11r Fast BSS Transition and increased max BSS count
    - Enabled unspecialized app process pool

    **Feature update highlights:**
    - August security patch (android-10.0.0_r41)
    - Reworked incremental update so that now it should work no matter which version of recovery you use and whether it supports system-as-root or not.
    - PE Plus: Introduced expanded volume panel

    2020/07/19
    - Etude kernel:
    * cleaned up some previous scheduler changes
    * built with Clang 11’s ThinLTO and more LLVM Polly optimization options. ThinLTO greatly improves build times over full LTO while retaining most of the performance benefits.
    * some upstream for rbtree and arm64 memory assembly
    * reverted back to 100HZ tick rate for better battery life
    * wireguard 1.0.20200712
    * exposed calculated FPS through sysfs. Now you can monitor your frame rates through supported apps (tested on Franco Kernel Manager)
    - Switched to QTI BlueTooth stack

    2020/07/11
    - Etude kernel: Op.10 No.2, "Allegro"
    * Linux 4.9.230 and CAF tag "LA.UM.8.3.r1-08100-sdm845.0"
    * built with Clang LTO(Link Time Optimization) and Polly(Polyhedral Optimization)
    * more scheduler and schedtune upstream
    * enabled CONFIG_HZ_300 and disabled core rotation for better load tracking and EAS task placement
    * fixed an issue on ebbg touchscreen
    - Disabled backpressure propagation due to slight increase in rate of jank frames
    - Dropped qti telephony injection
    * let me know if on some carriers mobile data is still broken after a phone call
    - If you use OrangeFox recovery and have error installing incremental package, please update your OrangeFox to R10.1_3 Stable
    * R10.1_3 Stable offers better compatibility with non system-as-root scripts
    * link: https://files.orangefox.tech/OrangeFox-Stable/polaris/OrangeFox-R10.1_3-Stable-polaris.zip
    * if your partition is not encrypted, make sure to tick "Disable forced encryption" again after updating OrangeFox, because the option will be reset after an OrangeFox update.

    PE: July's security patch
    PE Plus:
    - Brought back color calibration in Livedisplay
    - Per-app network isolation

    2020/06/27
    - Etude kernel:
    * some scheduler change from Pixel 3/XL kernel to improve UI responsiveness and jitter
    * Shadow Call Stack support
    * Wireguard 1.0.20200623
    * built with AOSP Clang 11.0.3 (r383902c)
    - Fully enabled backpressure propagation in SurfaceFlinger
    - Enabled Seamless Transfer
    * now you can switch between different audio output devices by tapping the music note icon on the notification of music apps
    * if you are not sure where it is, check screenshots: https://jjpprrrr.com/pep/20200627-0839/
    - Tweaked powerhint to improve IO latency on UFS
    - If you use OrangeFox recovery and have error installing incremental package, please update your OrangeFox to R10.1_3 Stable
    * R10.1_3 Stable offers better compatibility with non system-as-root scripts
    * link: https://files.orangefox.tech/OrangeFox-Stable/polaris/OrangeFox-R10.1_3-Stable-polaris.zip
    * if your partition is not encrypted, make sure to tick "Disable forced encryption" again after updating OrangeFox, because the option will get reset after an OrangeFox update.

    For PE Plus:
    Known issue: color calibration in Livedisplay is temporarily unavailable due to some changes on ROM source

    2020/06/21
    PE:
    - jjpprrrr's Etude kernel: Op.10 No.1
    * the built-in Etude kernel aims to offer smoother experience and better battery life for users who do not feel like flashing a custom kernel
    * special thanks to palaych for commits of new Xiaomi changes
    * Linux 4.9.228 & LA.UM.8.3.r1-07900-sdm845.0, compiled with AOSP Clang 11.0.1 (r383902)
    * upstreamed lz4 to v1.8.3 and enabled lz4 crypto for zram
    * simple_lmk, sound control, f2fs rapid GC (by arter97), Wireguard 1.0.20200611...
    - Updated Qualcomm Adreno and Vulkan drivers from Pixel 3 XL android 11 beta
    * OpenGL ES 3.2 [email protected] (was @415) and Vulkan 1.1.128
    - Fixed an SELinux denial of vendor_init writing to blkio on boot
    - Increased amount of visible notification icons
    - Increased minimum frequency for expensive rendering
    - Per-app optimization profile under Settings/Battery
    - If you use OrangeFox recovery and have error installing incremental package, please update your OrangeFox to R10.1_3 Stable
    * R10.1_3 Stable offers better compatibility with non system-as-root scripts
    * link: https://files.orangefox.tech/OrangeFox-Stable/polaris/OrangeFox-R10.1_3-Stable-polaris.zip
    * If your partition are not encrypted, make sure to tick "Disable forced encryption" again after updating OrangeFox, because the option will get reset after an OrangeFox update.

    PE Plus:
    - jjpprrrr's Etude kernel: Op.10 No.1
    * the built-in Etude kernel aims to offer smoother experience and better battery life for users who do not feel like flashing a custom kernel
    * special thanks to palaych for commits of new Xiaomi changes
    * Linux 4.9.228 & LA.UM.8.3.r1-07900-sdm845.0, compiled with AOSP Clang 11.0.1 (r383902)
    * upstreamed lz4 to v1.8.3 and enabled lz4 crypto for zram
    * simple_lmk, sound control, f2fs rapid GC (by arter97), Wireguard 1.0.20200611...
    - Updated Qualcomm Adreno and Vulkan drivers from Pixel 3 XL android 11 beta
    * OpenGL ES 3.2 [email protected] (was @415) and Vulkan 1.1.128
    - Fixed an SELinux denial of vendor_init writing to blkio
    - Increased amount of visible notification icons
    - Enabled and improved color profiles in Livedisplay
    * you can now choose between Standard, Reading, and sRGB profile
    - Increased minimum frequency for expensive rendering
    - Per-app optimization profile under Settings/Battery
    - If you use OrangeFox recovery and have error installing incremental package, please update your OrangeFox to R10.1_3 Stable
    * R10.1_3 Stable offers better compatibility with non system-as-root scripts
    * link: https://files.orangefox.tech/OrangeFox-Stable/polaris/OrangeFox-R10.1_3-Stable-polaris.zip
    * If your partition are not encrypted, make sure to tick "Disable forced encryption" again after updating OrangeFox, because the option will get reset after an OrangeFox update.
    - Known issue: color calibration in Livedisplay is temporarily unavailable due to a ROM source side change.

    2020/06/06
    **Device Specific Changes:**
    - Kernel: merged Linux 4.9.226 and LA.UM.8.3.r1-07900-sdm845.0
    - Switched to OSS fingerprint HIDL
    - Updated firmware and blobs from MIUI Global Stable V11.0.5.0 for polaris
    - Fixed APN related issues in May builds and removed CarrierSettings from vendor
    - If you use the latest OrangeFox recovery and see errors flashing incremental package, please
    * run "rm /system" in OrangeFox's terminal (or connect to a computer and run it in adb shell)
    * then install the incremental package
    * you will NOT lose any data. This is simply deleting a symlink for SAR support.

    **Feature update highlights:**
    - June security patch
    - Improved network traffic indicator
    - Fixed vibration when battery saver is enabled
    - Implemented quick QS brightness slider
    - Updated gapps and Pixel Launcher

    2020/05/28
    **Device Specific Changes:**
    - Upstreamed kernel to Linux 4.9.225
    - Shipped CarrierSettings in vendor
    * This should help users who experienced mobile data issue on the first two builds of May (e.g. Vodafone PT)
    - Tweaked power hint a bit to improve battery life
    - If you use the latest OrangeFox recovery and see errors flashing incremental package, please
    * run "rm /system" in OrangeFox's terminal (or connect to a computer and run it in adb shell)
    * then install the incremental package
    * you will NOT lose any data. This is simply deleting a symlink for SAR support.

    **PE side changes**
    - Minor improvements
    - Known issue: network traffic indicator will show up briefly in some scenarios despite disabled in settings.

    2020/05/24
    **Device Specific Changes:**
    - Upstreamed kernel to Linux 4.9.224
    - Brought back CarrierConfig
    - Fixed aux camera (telephoto)
    * now gcam with properly implemented aux support can use telephoto camera (tested on PitbulL gcam)
    - Merged display HAL from CAF LA.UM.8.3.r1-07200-sdm845.0
    * bumped vendor.display.config to 1.9
    * increased max_frame_buffer_acquired_buffers to 3
    * for the buttery smooth experience
    - If you use the latest OrangeFox recovery and see errors flashing incremental package, please
    * run "rm /system" in OrangeFox's terminal (or connect to a computer and run it in adb shell)
    * then install the incremental package
    * you will NOT lose any data. This is simply deleting a symlink for SAR support.
    - Known issue: some carriers may not have APN auto selected

    2020/05/13
    **Device Specific Changes:**
    - Upstreamed kernel to Linux 4.9.223
    - Fixed frequent charging disconnections and screen wakeups when battery is warm (46C)
    - Removed CarrierConfig overlay that is no longer needed
    - Raised background blkio weight
    - Enabled Rich-Communication Services
    - Removed CAF power HAL and imported power-libperfmgr from hardware/google/pixel
    - Imported powerhint.json and powerstats from crosshatch
    - Updated power profile from crosshatch
    - zram: lz4 for compression, size increase as recommended by CAF, and other optimizations
    - Enabled Pixel atrace HAL
    - Switched to 24 bit for primary audio output
    - Removed IO prefetcher, some perf blobs and configs
    - If you use the latest OrangeFox recovery and see errors flashing incremental package, please
    * run "rm /system" in OrangeFox's terminal (or connect to a computer and run it in adb shell)
    * then install the incremental package
    * you will NOT lose any data. This is simply deleting a symlink for SAR support.
    - If your partition is not encrypted, your phone may not boot properly after flashing the update. This is because the zram optimizations changes fstab, so the previous fstab patched by the "disable forced encryption patch" you had on your phone is overwritten. Therefore, you need to flash the patch to disable forced encryption again. If you use OrangeFox, you can also flash the full package, because OrangeFox will automatically patch your phone after flashing full package.

    Pixel Experience 10
    - May security patch
    - Fixed frame drops and random closes on screen recorder
    - Fixed Android Auto flickering
    - Fixed random closes on Settings app

    Pixel Experience 10 Plus
    - May security patch
    - Fixed frame drops and random closes on screen recorder
    - Fixed Android Auto flickering
    - Fixed random closes on Settings app
    - Improved long screenshot
    - Known issue: network traffic indicator may overlap or disappear if too many icons exist in statubar

    2020/04/17
    Device Specific Changes:
    - Upstreamed kernel to Linux 4.9.218
    - If you use the latest OrangeFox recovery and see errors flashing incremental package, please
    * run "rm /system" in OrangeFox's terminal (or connect to a computer and run it in adb shell)
    * then install the incremental package
    * you will NOT lose any data. This is simply deleting a symlink for SAR support.
    - Known issue: Android Auto will cause screen flickering. I am still waiting for PE to merge caf surfaceflinger related commits.

    Pixel Experience 10
    - Fixed abnormal behaviors of elements on lockscreen when enabling "Skip lock screen" in face unlock

    Pixel Experience 10 Plus
    - Fixed abnormal behaviors of elements on lockscreen when enabling "Skip lock screen" in face unlock
    - Long screenshots are now saved to the same folder as normal screenshots

    2020/04/07
    Device Specific Changes:
    - Switched to PE kernel (Linux 4.9.217)
    - Merged firmware and blobs from latest MIUI Global Stable V11.0.4.0
    * Volume adjustment in video calls has been fixed.
    * Firmware is included. No need to flash it manually when installing the ROM.
    - Fixed abnormal screen color and brightness behaviors after HDR video playback
    - If you use the latest OrangeFox recovery and see errors flashing incremental package, please
    * run "rm /system" in OrangeFox's terminal (or connect to a computer and run it in adb shell)
    * then install the incremental package
    * you will NOT lose any data. This is simply deleting a symlink for SAR support.

    Pixel Experience 10
    - April security patch (android-10.0.0_r33)
    - Face unlock
    - Screen recorder with internal audio recording
    - Android Auto is fixed

    Pixel Experience 10 Plus
    - April security patch (android-10.0.0_r33)
    - Face unlock
    - Screen recorder with internal audio recording
    - Long screenshot
    - Android Auto is fixed

    2020/03/13
    Pixel Experience 10
    - Upstreamed kernel to 4.9.214
    - Boosted microphone volume in different use cases
    - March Security Patch (android-10.0.0_r31)
    - Some features from Pixel features drop added, as they were included in the security patch
    - The navbar home button circle (A.K.A OPA Layout) is finally there
    - Added the ability of disabling pocketmode on settings (It’s enabled by default)

    Pixel Experience 10 Plus
    - Initial Release
    - Clean flash is highly recommended.

    2020/02/14 - 0240
    - Merged February security patch
    - Merged blobs from MIUI 20.1.16
    - Firmware 20.1.16 is recommended, although the old firmware 9.11.7 may work for most cases
    - Kernel has merged latest source from Xiaomi
    - If you would like to change kernel, please only use kernels that have new camera drivers
    - Fixed A2DP on new BT stack 2
    - Enabled ViLTE for all Indian carriers
    - Force enabled VoWIFI for any carrier
    - Due to a key signing change on PE server, you may have to download the full package to install in recovery manually.

    2020/01/31 - 1907
    * Fixed double tap to wake on Mix 2s with ebbg screens
    * Reduced LED blinking frequency under low battery, without interfering with notification LED
    Note: PE has been improving their OTA updater recently and some work is still in progress. Clicking "install" in the updater may cause install error for now. You might need to manually flash the incremental package in recovery.
    Update: Updater is only supposed to work with encrypted device. If your phone is not encrypted (OrangeFox disables forced encryption by default), you need permissive SELinux to be able to use the updater.

    Here is a quick way to change SELinux status if you have root:
    Code:
    abd shell
    su
    setenforce 0
    getenforce
    You should then see "Permissive" being printed in the shell.

    2020/01/25 - 1422
    Fixed audio distortion and out-of-sync when recording videos in Snapchat

    2020/01/25 - 0052
    Fixed Bluetooth call audio on Bluetooth headsets.

    2020/01/22
    Initial official polaris release by jjpprrrr.
    Everything is working except for BT calls on some BT headsets.
    13
    Reserved

    - PE recovery is REQUIRED
    * DO NOT use any other recovery
    * Partition scheme has been switched to retrofit dynamic partitioning because polaris is running out of system partition space. No actual re-partition is involved. Instead, the physical system and vendor partition is mapped together to form a logical "super" partition. The size of super partition equals the sum of the physical system and vendor partitions. After that, logical system and vendor partitions are created on top of this super partition. In this way, we are essentially redistributing space between the physical system and vendor partition to accommodate for the increase in size of system libraries and prebuilt apps.
    * The firmware is included with a different keymaster.img from perseus. DO NOT flash your own firmware.
    * To switch to other ROMs, format data in PE recovery first, and then install another recovery. You may need to re-flash the required firmware, if the ROM you are going to flash does not include one.
    - You cannot upgrade from android 12 builds. Formatting data is required.

    ==============================
    Old guide for android 12 builds:

    - Formatting data with PE recovery is REQUIRED for clean flash
    * DO NOT use any other recovery
    * The firmware is included with a different keymaster.img from perseus. DO NOT flash your own firmware.
    * Keymaster is bumped to 4.0 for encryption, and cust partition is mounted as /metadata. You WILL NOT be able to boot TWRP on PE 12.1. OrangeFox R11.1_1 or newer can boot but is not capable of decrypting the data partition.
    * To switch to other ROMs, format data in PE recovery first, and then install another recovery. You may need to re-flash the required firmware, if the ROM you are going to flash does not include one.
    - You can dirty flash from my previous PE 12 or 12.1 builds. You can dirty flash the Plus edition on top of PE 12 / 12.1 regular builds.
    - You cannot upgrade from android 11 directly. Formatting data is required.

    PE recovery flash guide
    - Download PE recovery from the official PE website
    - Boot your phone into fastboot mode. You can either
    * hold power + volume down button
    * or `adb reboot bootloader`
    * or use the `Reboot to bootloader` option in TWRP/OrangeFox
    - Connect your phone to a computer
    - Run `fastboot flash recovery pe_recovery_file_name.img` in your cmd/powershell/terminal
    - Hold power + volume up to boot into recovery

    PE 12 flash guide
    - Boot into PE recovery
    - Select `Factory reset" --> "Format data/factory reset`. You phone should say that /data, /cache, and /metadata have been formatted.
    - Go back to main menu and select "Apply update" --> "Apply from ADB"
    - Connect your phone to a computer
    - Run `adb sideload pe_rom_file_name.zip` in your cmd/powershell/terminal and wait until it finishes
    - Reboot to system


    ==============================
    Old guide for android 11 builds:

    Note: The latest TWRP and OrangeFox are able to DECRYPT the /data partition on android11. However, during our testing process, formatting data to bootstrap the ENCRYPTION is still a hit or miss. Some users will get working encryption upon the initial format and boot, but others will have a broken encryption and may need another data format. /data will appear to be encrypted, the recovery will prompt you to enter password, but if you skip/cancel the password prompt, you may see that files are not actually encrypted. This does not happen to everyone using TWRP/OrangeFox, and the cause is still being investigated.
    Therefore, format data with PE recovery is still required for clean flash.
    If you are already on the previous PE 11 build, OTA or dirty flash is fine.


    PE recovery flash guide[Required]:
    - Download PE recovery from the the polaris device page of official PE website
    - Boot your phone into fastboot mode. You can either
    * Hold power + volume down button
    * or `adb reboot bootloader`
    * or use the `Reboot to bootloader` option in TWRP/OrangeFox
    - Connect your phone to a computer
    - Run `fastboot flash recovery pe_recovery_file_name.img` in your cmd/powershell/terminal
    - Hold power + volume up to boot into recovery

    If you have a custom recovery (TWRP/OrangeFox) installed already, you can use that to flash the .img file of PE recovery into the recovery partition.

    PE 11 ROM flash guide[Required]:
    - Boot into PE recovery
    - Select `Factory reset" --> "Format data/factory reset`
    - Go back to main menu and select "Apply update" --> "Apply from ADB"
    - Connect your phone to a computer
    - Run `adb sideload pe_rom_file_name.zip` in your cmd/powershell/terminal and wait until it finishes
    - Reboot to system

    ==============================
    Old guide for android 10 builds:

    Flash guide:
    1. Use latest OrangeFox recovery R11.0 (or newer) or TWRP 3.3.1-1 (or newer)
    2. If you have been using MIUI or any of its variants, you have to format data.
    - you may have to reboot to recovery again after formatting data
    3. Wipe system & data & cache & dalvik cache
    4. Install ROM
    5. Reboot to system

    Note: Official maintainer of PE for polaris has been changed. Clean flash is highly recommended for those coming from the deprecated official build from Oct 2019. I will not offer any help if you've dirty flashed.


    Download: https://download.pixelexperience.org/polaris
    12
    2022/09/14
    Initial android 13 release.
    Flash guide, changelog, and known issues: https://jjpprrrr.com/pe/20220914-1603/
    11
    Update

    2020/03/13
    Pixel Experience 10
    - Upstreamed kernel to 4.9.214
    - Boosted microphone volume in different use cases
    - March Security Patch (android-10.0.0_r31)
    - Some features from Pixel features drop added, as they were included in the security patch
    - The navbar home button circle (A.K.A OPA Layout) is finally there
    - Added the ability of disabling pocketmode on settings (It’s enabled by default)

    Pixel Experience 10 Plus
    - Initial Release
    - Clean flash is highly recommended.

    Download: https://download.pixelexperience.org/polaris