fix: slowdowns on Auto cpu speed#727
Merged
Merged
Conversation
The 'ondemand' governor that was being used for Auto cpu speed seems to behave randomly/erratically. After a lot of testing I have changed it to schedutil. This performs much better on a wide variety of games and emulator cores, often outperforming even the Powersave profile (which uses the 'conservative' governor), resulting in lower cpu frequency and similar core temperatures while maintaining solid performance. That leaves the Performance cpu speed option as being a copy of Auto but just enabling the highest (overclocked) CPU speed. Instead of that, I thought it's worthwhile to have a locked-to-max CPU speed option free from any autoscaling for the truly demanding games (MSDOS games, OMF2097 being one example). Finally, the Powersave profile is now obsolete but it's left in for now. Auto now performs better than Powersave, providing lower clock speeds than Powersave. A future change should probably remove Powersave profile entirely.
Author
|
Those who want to test the fix and provide feedback now, please copy this .pakz file to the root of your SDCARD and restart your device. https://dsh.re/2d760d6a9ce4904f I can't attach .pakz files directly here so I uploaded it on S3. |
Member
|
lgtm, this is pretty much what I had in mind for #497. Does the performance governor still scale down at all, or is it locked to maximum frequency? |
|
@frysee for my testing the peformance governor will lock down the highest freq and never scale down |
frysee
approved these changes
May 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 'ondemand' governor that was being used for Auto cpu speed seems to behave randomly/erratically. After a lot of testing I have changed it to schedutil. This performs much better on a wide variety of games and emulator cores, often outperforming even the Powersave profile (which uses the 'conservative' governor), resulting in lower cpu frequency and similar core temperatures while maintaining solid performance.
That leaves the Performance cpu speed option as being a copy of Auto but just enabling the highest (overclocked) CPU speed. Instead of that, I thought it's worthwhile to have a locked-to-max CPU speed option free from any autoscaling for the truly demanding games (MSDOS games, OMF2097 being one example).
Finally, the Powersave profile is now obsolete but it's left in for now. Auto now performs better than Powersave, providing lower clock speeds than Powersave. A future change should probably remove Powersave profile entirely.
Closes #726