Phone slow after idle - how to setup governor - Android Q&A, Help & Troubleshooting

I have a rooted honor 5x with cm13. When I go to kernel adiutor and make sure all cores are running the phone is fast. after being idle it starts to be unresponsive but than gets better I think. I use interactive governor for both types of cores but can not change governor settings on little. How can I eliminate the lagging after idle? I have default governor settings. Is there a bnchmarking app which can set optimal settings?

Related

App: cpu clock scheduler and governor settings to higher when call

Hi.
Is there a simple cpu speed governor and scheduler settings tool which clocks to higher speeds when there is a phone call whilst stays on normal when there is no call?
Thanks in Advance
I am using SetCPU now.
I stopped using it because there was no development.

[Q] Using Setcpu on razr xt910.

Hi all,
I couldn't find the relevant information anywhere else, so thought I should ask if someone has experienced this.
Well I'm using setcpu on my razr and it is quite a brilliant app to be honest, helps me save battery quite alot by setting up profiles.
But recently I've been having crashing problems with the phone whenever i set the scaling to hotplug.
Previously, i was just using the default scaling, I guess Interactive it was, and was working quite happily. And, then i read about advantages of using Hotplug scaling, that it enables/disables cores depending on the amount of load on the cpu, which is really good for saving battery.
And before how I was using the phone, was to set a profile for screen off to drop the cpu down to 300MHz, using the default scaling.
But as soon as I changed from default scaling to Hotplug, it starts crashing randomly, and I've to restart the phone using keys.
Scenarios tried:
- Main scaling: Hotplug -- Screen off scaling: Interactive, Ondemand, Performance, Hotplug -- Processor Max: 300MHz
Result: crashing as soon as u turn the screen on, or sometimes while the screen is off.
- Main scaling: Hotplug -- Screen off scaling: Interactive, Ondemand, Performance, Hotplug -- Processor Max: 600MHz
Result: crashing as soon as u turn the screen on, or sometimes while the screen is off.
- Main scaling: Interactive -- Screen off scaling: Hotplug -- Processor Max: 300MHz
Result: In process of checking, hasn't crashed yet for more than an hour. :fingers-crossed:
Can someone kindly point out the obvious mistake I'm making here?
I really want to use hotplug, both as main and screen off.
FYI: I haven't done anything else to the phone apart from gaining root access.
i had issues with setcpu, i recommend no frills cpu control, and setting it down that low more then likely is also an issue, the second core i couldn't see turning off at a low clock and also i think it would max out easily causing instability (especially ICS) and above id say. uninstall setcpu give no frills a try and let me know would be glad to help with what i can!
Thanks for ur reply, yes I'll try no frills, but
mr4r4n said:
setting it down that low more then likely is also an issue
Click to expand...
Click to collapse
I thought the same, but while i was using interactive scaling, it worked perfectly, no issues at all. Probably because both cores were active by default, so both on 300MHz when screen was off.
mr4r4n said:
the second core i couldn't see turning off at a low clock and also i think it would max out easily causing instability (especially ICS)
Click to expand...
Click to collapse
No, I've checked cpu usage visa adb shell, and if the screen off is in hotplug, like what it is right now, the phone stays at 300MHz with the second core turned off, most of the time. And the phone has been running now for more than 3hrs with screen off profile set to Scaling: hotplug -- Max: 300MHz, and the main scaling set to Interactive.
The problem I've seen is, when main scaling is set to hotplug. Doesn't matter whatever u set in screen off profile, it crashes if the main scaling is set to hotplug. But, if no screen off profile is set then, hotplug in main works flawlessly.
That's weird. I've been using SetCPU for a year or so on my RAZR GB/ICS and never encountered any crashes with hotplug or the default ICS's interactive.
I have even tried unofficial governers like smartass2, boostedassv2 and etc, no crashes.
I personally set my phone to use u/c 200-200 for screen off and I find it really saves a lot of battery, and even o/c to 200-1300 when it's on.
Are you using the setcpu from xda or from playstore? I'm using the one from playstore with Razr asia ICS.
Nikorasu said:
That's weird. I've been using SetCPU for a year or so on my RAZR GB/ICS and never encountered any crashes with hotplug or the default ICS's interactive.
I have even tried unofficial governers like smartass2, boostedassv2 and etc, no crashes.
I personally set my phone to use u/c 200-200 for screen off and I find it really saves a lot of battery, and even o/c to 200-1300 when it's on.
Are you using the setcpu from xda or from playstore? I'm using the one from playstore with Razr asia ICS.
Click to expand...
Click to collapse
I think I downloaded it from here.
But I think, they both are the same, from same developer
hsyasin said:
I think I downloaded it from here.
But I think, they both are the same, from same developer
Click to expand...
Click to collapse
This means that you're using an old July 2011 version.
Do make use of playstore's 15 min return policy to test the newer ver. Maybe it will solve your problem.

The phone auto shutdown 4 cores

I have a rooted RN4 with RR (7.1.2) and ElectraBlue Kernel 8.0. When I am on low battery, cpu cores 4-7 will auto shutdown. How can I disable that feature ?
Changing the governer can solve this, by default the electra blue kernel is set to 'electron' governer which does all the magic. But changing it to something like, interactive can reset the settings. But keep in mind the magic of electra blue will not be much noticiable them
On my phone the default governor is interactive (electra blue kernel 8.0). But I use powersave. In this state (powersave) the phone have shut down 4 cores.
Then dobt use electrablue .use other kernels. Velvet is a fine kernel

Phone faster when touchscreen pressed.

Hello! I have an a32 5g and when I run intensive apps like emulators such as dolphin mmj and aethersx2, I can clearly see a drastic increase in performance when my finger are on the touchscreen. How can I ensure that my phone is running this fast all the time?
It's caused by "input booster", likely forcing CPU Freq at max_freq.
Try to tune CPU governor, e.g. set lower value for up_threshold.
Or you can use performance governor, but this will use max_freq all the time, draining battery very fast, except in deep sleep state of course.
I found Franco Kernel Manager and already have per app profiles set up to change when aether or dolphin launches. Thanks again!
*Completely fixed the problem btw!

Question Rooted Pixel 6 CPU frequency control without userspace governor

So I recently rooted my Pixel 6 (Android 13) using Magisk and tried to control the CPU frequency, but it did not have userspace CPU governor. I tried to set scaling_setspeed in /sys/devices/system/cpu/cpu0/cpufreq/ with no luck (kept popping up as <unsupported>).
Also tried setting scaling_max_freq and scaling_min_freq using the maximum frequency and scaling_governor as performance mode. While the CPU is idle, cpuinfo_cur_frequency says that the CPU is at max frequency, but when I run an application, the frequency would drop.
It was to my understanding that performance mode would keep the CPU at max frequency, but even then, the frequency would drop.
Is there a way to set and fix the frequency without adding userspace CPU governor through a custom kernel? Or does Android 12 still have the userspace governor? Then maybe I can rollback and control it that way.

Categories

Resources