Develop Bugs

Voltage control questions

I finally got srf 1.2 to work really good. I have a few questions about voltage control.
1. Is it safe to overclock and undervolt?
2. What advantages will I see from undervolting, longer battery life?
3. Does overclocking really make that much difference, and is it safe?
4. Is there a how to, or a guide that can show me how to do it?
Thanks

Yes its safe just don't use the set on boot feature. As for battery improvement some people notice a difference and others don't I personally do undervolt. As for the guide just mess around with it for a while everyone Has different Preferences so results will always be different. I don't undervolt below 75 cause when I do I get lock ups. If you lock up just pull the battery and you'll be fine. I also recommend to use journaling ON cause if you lock up and pull the battery with journaling off you might get data corruption.
Hope this helps.
Sent from my SPH-D700 using XDA App

Yeah that helped but I really just don't know how to use it.

Led4lyf said:
I finally got srf 1.2 to work really good. I have a few questions about voltage control.
1. Is it safe to overclock and undervolt?
2. What advantages will I see from undervolting, longer battery life?
3. Does overclocking really make that much difference, and is it safe?
4. Is there a how to, or a guide that can show me how to do it?
Thanks
Click to expand...
Click to collapse
What kernel are you on?
I'm on Twilight and can overclock to 1.3ghz with full stability. I don't undervolt. Combination of my phone doesn't like it and I'm not looking to save that little battery to get wakelocks (phone doesn't come out of sleep mode because the processor speed is too slow or doesn't have enough juice to make that push.)
If you're using a kernel that can go to 1.4 or 1.5 test it for a while before you save your settings. Also consider buying the paid version. It allows over volting which may allow you to supply enough power if 1.4 or 1.5 causes freezes.
The app is pretty basic. The top bar on the first screen is how low you allow the processor to go in speed. The bottom is how fast. Lower than 100 mhz causes wakelock for me. Or used to. Haven't tried since. My settings are 200-1300 mhz. Second page is voltages. They start at default. If you have extreme, moving them to the right will overvolt and give those speeds extra power. Moving the slider to the left undervolts. Some people can only undervolt at the lowest speeds of say 100-400 mhz. It's a lot of trial and error. Have fun though!

So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?

Led4lyf said:
So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?
Click to expand...
Click to collapse
It wont make it much faster
Sent from my SPH-D700 using XDA App

Led4lyf said:
So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?
Click to expand...
Click to collapse
When you turn your phone off then on, does it show those same settings? The speed boost will be slight. It's not like we're resurrecting Jesus here.

[MOD] How To Turn off Exynos Cores (and underclock)

I expected it to be slightly more complicated than this but apparently not. I know that you can underclock with the use of applications but I thought I'd mention that it can be also be done this way too.
Note: I'm pretty sure this is modifying the Exynos but I've not had enough time to play with it yet so I'm not 100% sure.
WARNING: This modification will directly modify how the CPU works. As such I will not be held responsible for any damage this may cause. YOU HAVE BEEN WARNED.
Tested on
Samsung Galaxy S 4 i9500 (most likely will not work on the i9505)
Omega v4.0 ROM
Perseus Kernel
Requirements
I9500
Root Access
ADB command knowledge or a Root File Editor.
How to set the max number of active cores
1) Locate the file
Code:
/sys/power/cpucore_max_num_limit
2) Change it from 4 to whatever (you cannot set this to 0)
How to set the minimum number of active cores
1) Locate the file
Code:
/sys/power/cpucore_min_num_limit
2) Change it from 0 to whatever (you cannot set this to 4)
How to check it's working
1) Locate the file
Code:
/sys/devices/system/cpu/offline
This file should tell you how many cores are disabled (e.g, If you limit the active cores to 2, the 'offline' file will read "2-3".
2) You can double check with the
Code:
/sys/devices/system/cpu/online
file which will tell you have many cores are active.
How to underclock
[Pretty unnecessary as you can use various applications to do this bit for you]
1) Locate the file
Code:
/sys/power/cpufreq_max_limit
2) Change it to whatever you want (as long as it's a valid frequency)
You can also lock the device to 1.6GHz by editing the
Code:
/sys/power/cpufreq_min_limit
file
The Min and Max frequencies can also be changed by editing the files in
Code:
/sys/devices/system/cpu/cpufreq/ikcs-cpufreq
Things to Remember
1) These changes are not permanent. They will revert back to their defaults on boot.
2) Limiting the Exynos to 1 core causes the device to get rather unstable and can cause reboots.
3) I haven't tested this fully; any damage this may do I will not be held responsible for. Anything you do here you do so at your own risk.
Quadrant Scores
Device running on all 4 cores
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device running on 3 cores
Device running on 2 cores
Device running on 1 core
Device running on 1 core with CPU clocked at 600MHz (why not? )
Ok, but... Why?
Good question. For me, this mod is completely unnecessary. I'm planning on making an application for this in the near future if anyone's interested.
Interestingly, there's very little difference between 2 cores and 4 in general usage. This may extend your battery life somewhat and perhaps cool the device down for those experiencing overheating but apart from that it's fairly useless.
Enjoy!

You could easily echo the commands in init.d scripts. Set sleep first to allow device to boot smoothly
Sent from my GT-I9500 using xda premium

An application would be useful, very useful. If you could release an app, I'd be really grateful.
Sent from my GT-I9500 using Tapatalk 4 Beta

Nasty_z said:
An application would be useful, very useful. If you could release an app, I'd be really grateful.
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and knock one up quickly later on.
For the battery conscious among you I've been running my phone on 1 core all day by accident, I must have forgot to change it back, and it seems to have been both stable and pretty efficent, battery wise. I'll do a proper test when I next fully charge it.
Sent from my GT-I9500 using xda app-developers app

mate, the oc/uc can be easily done via either sytem tuner or nstool or any other cpu tools right?

bala_gamer said:
mate, the oc/uc can be easily done via either sytem tuner or nstool or any other cpu tools right?
Click to expand...
Click to collapse
Yup, I use CPU Master Free. Don't think anyone's made an oc capable kernel yet but you can just use applications to lower the cpu speed
Sent from my GT-I9500 using xda app-developers app

Meltus said:
Yup, I use CPU Master Free. Don't think anyone's made an oc capable kernel yet but you can just use applications to lower the cpu speed
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
did you note something odd? played with few of those values now my cpu always hangs arooung 1.6ghz regardless of cpu usage ignoring low cpu clk
edit: changed the minfreq again after a reboot, its back to normal

If i'm correct these changes only apply to the A15 cores not A7?

Meltus said:
I expected it to be slightly more complicated than this but apparently not. I know that you can underclock with the use of applications but I thought I'd mention that it can be also be done this way too.
Note: I'm pretty sure this is modifying the Exynos but I've not had enough time to play with it yet so I'm not 100% sure.
WARNING: This modification will directly modify how the CPU works. As such I will not be held responsible for any damage this may cause. YOU HAVE BEEN WARNED.
Tested on
Samsung Galaxy S 4 i9500 (most likely will not work on the i9505)
Omega v4.0 ROM
Perseus Kernel
Requirements
I9500
Root Access
ADB command knowledge or a Root File Editor.
How to set the max number of active cores
1) Locate the file
Code:
/sys/power/cpucore_max_num_limit
2) Change it from 4 to whatever (you cannot set this to 0)
How to set the minimum number of active cores
1) Locate the file
Code:
/sys/power/cpucore_min_num_limit
2) Change it from 0 to whatever (you cannot set this to 4)
How to check it's working
1) Locate the file
Code:
/sys/devices/system/cpu/offline
This file should tell you how many cores are disabled (e.g, If you limit the active cores to 2, the 'offline' file will read "2-3".
2) You can double check with the
Code:
/sys/devices/system/cpu/online
file which will tell you have many cores are active.
How to underclock
[Pretty unnecessary as you can use various applications to do this bit for you]
1) Locate the file
Code:
/sys/power/cpufreq_max_limit
2) Change it to whatever you want (as long as it's a valid frequency)
You can also lock the device to 1.6GHz by editing the
Code:
/sys/power/cpufreq_min_limit
file
The Min and Max frequencies can also be changed by editing the files in
Code:
/sys/devices/system/cpu/cpufreq/ikcs-cpufreq
Things to Remember
1) These changes are not permanent. They will revert back to their defaults on boot.
2) Limiting the Exynos to 1 core causes the device to get rather unstable and can cause reboots.
3) I haven't tested this fully; any damage this may do I will not be held responsible for. Anything you do here you do so at your own risk.
Enjoy!
Click to expand...
Click to collapse
Can I use this method to turn off some core on the stock kernel from SS? Im not using the Perseus kernel. Does this method working only on Perseus kernel or any kernel?

Thanks for the excellent work:thumbup::beer:
Spoiler
Phone: SGS2
Inviato da: Tapatalk 2
Rom: NeatROM 4.7 LITE XWLSS
Kernel: Apolo 4.6 v0 ←testing-
Modem: XXMS2
Battery: Stock 1650mAh
SD Ext. : 32Gb class 10
Inviato dal mio supermuletto :tank:

Wait for the APP of urs ... @Meltus sir

palash_6670 said:
Wait for the APP of urs ... @Meltus sir
Click to expand...
Click to collapse
Me too
Sent from my GT-I9500 using xda premium

palash_6670 said:
Wait for the APP of urs ... @Meltus sir
Click to expand...
Click to collapse
Zahid Ali said:
Me too
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Currently waiting to be sent an invoice to get my S4 repaired (the LCD screen cracked, possibly due to overheating as I never dropped it).
I could build you a quick app if you want but it won't have been tested.

It's fine, I can volunteer to test the app.

Meltus said:
Currently waiting to be sent an invoice to get my S4 repaired (the LCD screen cracked, possibly due to overheating as I never dropped it).
I could build you a quick app if you want but it won't have been tested.
Click to expand...
Click to collapse
Yeah sure why not
Sent from my GT-I9500 using xda premium

Meltus said:
……
Note: I'm pretty sure this is modifying the Exynos but I've not had enough time to play with it yet so I'm not 100% sure.
WARNING: This modification will directly modify how the CPU works. As such I will not be held responsible for any damage this may cause. YOU HAVE BEEN WARNED.
Tested on
Samsung Galaxy S 4 i9500 (most likely will not work on the i9505)
Omega v4.0 ROM
Perseus Kernel
……
Click to expand...
Click to collapse
The stock kernel can work fine with this way, in deep.
Good Job.

Ok, here's an app to do it for you.
Exynos Core Control
Should allow you to set the minimum and maximum amount of cores in use.
Requirements
i9500
Root Access and Busybox
Completely untested - Use at your own risk!
This is directly modifying how the CPU works. I will not be held responsible for any damage done to your device.
YOU HAVE BEEN WARNED

Now been using for almost four hours with max 2 and minimum 0 cores active. Used apps like camera etc, faced no issues so far.
Sent from my GT-I9500 using Tapatalk 4 Beta

There is no point in trying to turn the cores off by force, they are powered off by CPU idle C2 state. Same reason why the phone doesn't have usual hot-plugging anymore. All you're doing is limiting performance and probably even worsening battery life by not having the load spread out over many cores at low frequency.
Also I think this thread belongs in some other forum.

AndreiLux said:
There is no point in trying to turn the cores off by force, they are powered off by CPU idle C2 state. Same reason why the phone doesn't have usual hot-plugging anymore. All you're doing is limiting performance and probably even worsening battery life by not having the load spread out over many cores at low frequency.
Also I think this thread belongs in some other forum.
Click to expand...
Click to collapse
Not sure about battery life savings, didn't test it fully.
Running on 2 cores doesn't seem to impact much on performance in games but it does drastically reduce the overheating problem so I guess this could be considered a 'quick fix' until (or even if) Samsung sorts it out. I even said in the original post that this mod is pretty unnecessary but I thought I may as well post that it's possible to do.
Don't see why it doesn't belong in this forum either as it's a mod that no one's done before (as far as I'm aware) making it "Original". I guess it'd be at home in both Original and non-Original Development but the criteria for each aren't exactly clear.
I'm sure a mod will move the thread if they deem it to be misplaced.

[Q] Overclock with SetCPU

Hi,
Would anyone be kind enough to list a step-by-step process on how to overclock the Note 8.0 using SetCPU? I'm a new user of this app and I'm afraid I may end up doing some irreparable damage to the device.
I am also just curious to see if I can squeeze some more gaming juice from the Note 8.0.
thanks in advance.

jnolaw said:
Hi,
Would anyone be kind enough to list a step-by-step process on how to overclock the Note 8.0 using SetCPU? I'm a new user of this app and I'm afraid I may end up doing some irreparable damage to the device.
I am also just curious to see if I can squeeze some more gaming juice from the Note 8.0.
thanks in advance.
Click to expand...
Click to collapse
I was going to post a link to a setCPU guide, but its no longer available
Id only push the CPU a little. In order to gain real gaming perfomance increases you need to push the GPU, but in order to do that you will need a kernel that supports it.
I only received my tablet last night and wont be rooting it until the weekend so cant say what settings ill be using yet. my aim is to attempt to overclock slightly and undervolt where I can...

You're not going to break it with SetCPU. If you overclock too much, the system will become unstable, then just back off. Also, the system will shut itself off well before any temperature possible of causing permanent damage was reached.
SetCPU has an option to create a recovery-flashable zip file, which resets the CPU settings to default. I would absolutely take this precaution, as I've had to resort to it on my old HTC Flyer tablet (became unstable, and bootlooped). As long as you select this option, you're pretty safe.
Other than that, just follow the basic rule of overclocking any computer, and push the clock up one or 2 increments at a time, then test for a few hours to see if the tablet is stable under various usage conditions. Repeat until you've either reached a desirable clock speed, or encounter instabilities.
Also, as you may already be aware, higher than "stock" CPU clock steps are normally not available unless you flash a custom kernel.

The trickster app supports GPU overclock on Civato's kernel.
If you're looking to push the GPU that's the way to go.

Thanks for the valuable inputs to all.

roustabout said:
The trickster app supports GPU overclock on Civato's kernel.
If you're looking to push the GPU that's the way to go.
Click to expand...
Click to collapse
Does the Trickster app allow for senario clock settings. Ie. underclock the CPU on screen off or if battery is bellow a certain percentage?
I may have to switch from setCPU to it if it has the same settings and more...

Touch screen randomly stops functioning

I've been facing non responsive screen with my OnePlus 5T. The screen touch stops responding and only volume keys and power button are responsive.
Sometimes a reboot fixes the trouble but other times I have to dirty flash the stock Oxygen OS 10.0.0 zip file in TWRP recovery using OTG and mouse, to bring back the touch function to normal.
What should I do to permanently solve this trouble?
This has been a frequent problem as posted by many users here.
https://forum.xda-developers.com/oneplus-5t/help/touch-screen-5t-randomly-stops-t3888017

Well, this problem is 100% a hardware one and it is caused by the fluid of the screen digitizer. One possible cause (apart from manufacturing flaw) is the prolonged heat that is encapsulated inside the phone. That's why most people with thick protective cases and protective plastic screen film had the issue appear as soon as 4 months of usage.
You can easily prove my theory: the next time it happens again leave the phone in the fridge (not freezer) for around 10 minutes, without restarting or doing anything to it. Then see by yourself if your touchscreen has come back to normal.
The most permanent solution is to replace the AMOLED screen and use a case that is as thin as possible. Other people had success by flashing a different custom kernel (probably one that lowered the Snapdragon's power consumption) but even then some reported that it reappeared after a few months. But I think that the screen's digitzer fluid has been permanently damaged by the heat over the years of use.
So to sum up:
1. Change screen for a new one
2. Use the thinnest possible case for the phone
3. (my recommendation) Flash a slightly underclocked/undervolted kernel alongside a stock-android based custom ROM
The third step is just a precaution to prevent it from happening again.
Hope I helped to clarify the issue

BlackRazor97 said:
Well, this problem is 100% a hardware one and it is caused by the fluid of the screen digitizer. One possible cause (apart from manufacturing flaw) is the prolonged heat that is encapsulated inside the phone. That's why most people with thick protective cases and protective plastic screen film had the issue appear as soon as 4 months of usage.
You can easily prove my theory: the next time it happens again leave the phone in the fridge (not freezer) for around 10 minutes, without restarting or doing anything to it. Then see by yourself if your touchscreen has come back to normal.
The most permanent solution is to replace the AMOLED screen and use a case that is as thin as possible. Other people had success by flashing a different custom kernel (probably one that lowered the Snapdragon's power consumption) but even then some reported that it reappeared after a few months. But I think that the screen's digitzer fluid has been permanently damaged by the heat over the years of use.
So to sum up:
1. Change screen for a new one
2. Use the thinnest possible case for the phone
Click to expand...
Click to collapse
Thanks for replying @BlackRazor97. Few minutes ago, I faced this trouble again.
My screen froze and I rebooted once. The screen wasn't responding. I gave a second reboot. It started functioning again. While it was booting, I came here and went through your post. I just went through your post. Getting the screen replaced is probably going to be an expensive affair. I would rather buy a new phone but still want to continue with this one without getting any hardware replaced.
I'll surely try the fridge trick the next time it happens.
BlackRazor97 said:
3. (my recommendation) Flash a slightly underclocked/undervolted kernel alongside a stock-android based custom ROM
The third step is just a precaution to prevent it from happening again.
Hope I helped to clarify the issue
Click to expand...
Click to collapse
I have never done underclocking/undervolting before. Wouldn't it make the phone slow? Can you please suggest any reliable slightly underclocked/undervolted kernel for stock oxygen os 10.0.0 as that's the one I'm currently on. Flashing a new ROM, restoring my apps will take a long time.

archz2 said:
I have never done underclocking/undervolting before. Wouldn't it make the phone slow? Can you please suggest any reliable slightly underclocked/undervolted kernel for stock oxygen os 10.0.0 as that's the one I'm currently on. Flashing a new ROM, restoring my apps will take a long time.
Click to expand...
Click to collapse
I have only used FrancoKernel myself but since it's not available for Android 10, I recommend you to flash blu_spark r209 stable kernel for Android 10. It should work fine for stock Android 10 OOS.
https://forum.xda-developers.com/oneplus-5/oneplus-5--5t-cross-device-development/kernel-t3651933
And then by using the FKM (Franko Kernel Manager) under "battery tips" you can underclock the CPU. You don't need to underclock it too much; set it to 2Ghz (instead of 2.45Ghz) for the big cluster and 1.2Ghz for the little cluster. You will see no big difference in performance and your battery life will improve too !
Always do a backup of your stock kernel, just in case something happens.
Please let me know if it helped resolve your issue.

BlackRazor97 said:
I have only used FrancoKernel myself but since it's not available for Android 10, I recommend you to flash blu_spark r209 stable kernel for Android 10. It should work fine for stock Android 10 OOS.
https://forum.xda-developers.com/oneplus-5/oneplus-5--5t-cross-device-development/kernel-t3651933
And then by using the FKM (Franko Kernel Manager) under "battery tips" you can underclock the CPU. You don't need to underclock it too much; set it to 2Ghz (instead of 2.45Ghz) for the big cluster and 1.2Ghz for the little cluster. You will see no big difference in performance and your battery life will improve too !
Always do a backup of your stock kernel, just in case something happens.
Please let me know if it helped resolve your issue.
Click to expand...
Click to collapse
I'm quite frustrated now. I'll try flashing the blu spark and do settings with Franco Kernel Manager.
Anyway, my experience with the refrigerator trick today.
First time it worked. The other time when screen issue came up, I rebooted my phone twice, hoping to solve the problem, but it didn't happen. Then I put it in the fridge. After ten minutes, I took it out the screen wasn't responding. I rebooted it. The screen started working.
Sent from my ONEPLUS A5010 using Tapatalk

@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A5010 using Tapatalk

archz2 said:
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?View attachment 5128013
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Yes exactly. Let the minimums as it is and lower the maximum frequencies. FKM received a big overhaul update in version 4.0, which apparently I haven't used. The menus are different but the functionality must be the same. Also don't forget to enable blu_spark blu_active governor.
Let me know if the fix is a permanent solution for you.

BlackRazor97 said:
Yes exactly. Let the minimums as it is and lower the maximum frequencies. FKM received a big overhaul update in version 4.0, which apparently I haven't used. The menus are different but the functionality must be the same. Also don't forget to enable blu_spark blu_active governor.
Let me know if the fix is a permanent solution for you.
Click to expand...
Click to collapse
Okay. Thanks. I've done it. So far so good. I have set frequencies to 1248MHz, 2112MHz. These I selected from the options pop-up. There's no way to type frequencies manually. One small query. When I do any changes in franco kernel, I don't have to reboot to apply those changes. Or should I ?

archz2 said:
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?
Click to expand...
Click to collapse
Actually there is a battery tips tab.
And if you are interested, you can check the Lazy kernel
They say it's good.

archz2 said:
Okay. Thanks. I've done it. So far so good. I have set frequencies to 1248MHz, 2112MHz. These I selected from the options pop-up. There's no way to type frequencies manually. One small query. When I do any changes in franco kernel, I don't have to reboot to apply those changes. Or should I ?
Click to expand...
Click to collapse
Nice! Yes, I think you don't need to reboot for the settings to apply. You can check with another app like CPUZ to check if clocks go above 2112MHz. But I think you should be fine.
As for the Lazy Kernel, I don't know if it's compatible with stock Android 10 OOS. But here we don't go for the performance but we target stability and low thermals to resolve the screen issue.

BlackRazor97 said:
Nice! Yes, I think you don't need to reboot for the settings to apply. You can check with another app like CPUZ to check if clocks go above 2112MHz. But I think you should be fine.
As for the Lazy Kernel, I don't know if it's compatible with stock Android 10 OOS. But here we don't go for the performance but we target stability and low thermals to resolve the screen issue.
Click to expand...
Click to collapse
Yah there is lazy kernel for stock OOS .
Those who flashed it has high recommendations and showed low ram usage .
Before flashing lazy kernel it was 700 mb free ram usage .
After flashing lazy kernel , attached screenshot.
Rom- derpfest
I haven't flashed it yet , I will when I get time

...........

@BlackRazor97
Okay. Almost a week went by. I faced non-responsive screens in last 3-4 days but the issue got resolved by tapping mindlessly on the screen when it was locked and frequent screen unlocks. Yesterday came the issue where I rebooted the phone multiple times to make the screen respond. Today the issue also came, half an hour ago and frequent reboots didn't solve the issue. I rebooted in recovery and wiped the cache and dalvic. Then I started my phone. It responded fine. I went to Franco Kernel Manager. To my surprise, the frequencies were switched back to 2361 MHz for Big Cluster and 1824 or 1900 MHz (can't remember which one) for the Little Cluster. Now I've changed them back to 2112 MHz and 1248 MHz
How did these frequencies got back to higher number without me every touching the Kernel Manager? I didn't install any app, nothing in these days.

archz2 said:
@BlackRazor97
Okay. Almost a week went by. I faced non-responsive screens in last 3-4 days but the issue got resolved by tapping mindlessly on the screen when it was locked and frequent screen unlocks. Yesterday came the issue where I rebooted the phone multiple times to make the screen respond. Today the issue also came, half an hour ago and frequent reboots didn't solve the issue. I rebooted in recovery and wiped the cache and dalvic. Then I started my phone. It responded fine. I went to Franco Kernel Manager. To my surprise, the frequencies were switched back to 2361 MHz for Big Cluster and 1824 or 1900 MHz (can't remember which one) for the Little Cluster. Now I've changed them back to 2112 MHz and 1248 MHz
How did these frequencies got back to higher number without me every touching the Kernel Manager? I didn't install any app, nothing in these days.
Click to expand...
Click to collapse
Did you set it to set on boot my friend?

When I enable the CPU governor blu_active, I get the notification "set on boot:true", that's it. I didn't toggle any other setting. I just restarted, the frequencies are back to 2361 MHz. Is there some other place where I should set on boot ?
View attachment 5132257

archz2 said:
When I enable the CPU governor blu_active, I get the notification "set on boot:true", that's it. I didn't toggle any other setting. I just restarted, the frequencies are back to 2361 MHz. Is there some other place where I should set on boot ?
Click to expand...
Click to collapse
Do one thing this time.
Under clock both your CPU AND GPU.
Under battery life tips, check under clock both.
And click on the settings icon just near to it and set it on boot.
Check this for some days and tell me

This

rohithksaj said:
Do one thing this time.
Under clock both your CPU AND GPU.
Under battery life tips, check under clock both.
And click on the settings icon just near to it and set it on boot.
Check this for some days and tell me
Click to expand...
Click to collapse
Thanks. I've done it. I'll keep you posted.

The situation became worse after underclocking. Had to reboot twice to get the screen working. I went back to the old settings.

archz2 said:
The situation became worse after underclocking. Had to reboot twice to get the screen working. I went back to the old settings.
Click to expand...
Click to collapse
DO NOT use the automatic underclock button. This also lowers the voltage to the point it becomes unstable and we don't want this to happen. Use the typical 2112 MHz and 1248 MHz (big and little cluster accordingly).
Unfortunately, it seems that the "set on boot:true" flag is bugged. So every time you shutdown your phone, you have to re-configure to the frequencies. Let me know if you have found any better solution to keep the settings.

Is Redmi note 8 pro locked at 2 GHz normal?

i've been using this phone for about 2 years now and recently moved (about a few months ago) to using a custom rom (crdroid 7.1.2). it was running smooth and cool until day the clockspeed decided to lock itself at 2000 MHz (checked using cpu-z). I do not know if this is normal but the phone's temperature goes up to 36C on idle. i thought the problem was with the Lspeed app (+custom kernel) so i uninstalled it but it didn't work. I also factory resetting it, but still not luck. will updating the firmware resolve my issue? if not, what other available solutions are there?

have you thought about flashing the stock kernel ?

Fytdyh said:
have you thought about flashing the stock kernel ?
Click to expand...
Click to collapse
I have, but it still gets hot

do you use a case ? does your phone goes over 45 degrees celsius when charging ?

Fytdyh said:
do you use a case ? does your phone goes over 45 degrees celsius when charging ?
Click to expand...
Click to collapse
I do use a case, but hasn't been this hot before recently, and it does tend to hit 40C when charging

topsecretasian said:
I do use a case, but hasn't been this hot before recently, and it does tend to hit 40C when charging
Click to expand...
Click to collapse
If you are using Fast Charging, that heating is entirely normal (happens to me too)
But heating during idle is not normal. Try changing CPU governor to something else. (like schedutil or powersave)

Canny1913 said:
If you are using Fast Charging, that heating is entirely normal (happens to me too)
But heating during idle is not normal. Try changing CPU governor to something else. (like schedutil or powersave)
Click to expand...
Click to collapse
Do you know how to change cpu governor? I tried doing it last night but didn't find a whole lot of information. Schedutil seems to just set it all the way to 2ghz, so I want to change it to powersave

topsecretasian said:
Do you know how to change cpu governor? I tried doing it last night but didn't find a whole lot of information. Schedutil seems to just set it all the way to 2ghz, so I want to change it to powersave
Click to expand...
Click to collapse
use Rootify, select the CPU tab located at the top then change it.
The app sometimes gets stuck at Loading screen though.

Canny1913 said:
use Rootify, select the CPU tab located at the top then change it.
The app sometimes gets stuck at Loading screen though.
Click to expand...
Click to collapse
ok so it does work when i change the cpu govenor, but the only option that actually works is 'powersave' (as well as 'userspace'). all the other ones still sets it to 2GHz. 'userspace' seems to have a somewhat of an improvement but it's only setting everything to a constant value. is there a way have it set to balanced mode?

topsecretasian said:
ok so it does work when i change the cpu govenor, but the only option that actually works is 'powersave' (as well as 'userspace'). all the other ones still sets it to 2GHz. 'userspace' seems to have a somewhat of an improvement but it's only setting everything to a constant value. is there a way have it set to balanced mode?
Click to expand...
Click to collapse
powersave forces the processor to work in the lowest frequency availible, thus consuming less power.
userspace allows the app to set the CPU frequency whatever it wants. This isn't supposed to be used in Android since changing CPU speed thorough an app is super uncommon.
Others like ondemand normally keep the power low but starts using the higher frequencies if a processor intensive app is launched.
You can learn which governors do what in this post so you can set the most suitable one for you.
[REF][GUIDE]Saber's guide on CPU governors, I/O schedulers and more!
Collective guide of CPU governors, I/O schedulers and other kernel variables I present to you a wonderful collection of descriptions, comparisons and graphs of common kernel variables. Before continuing on the wonderful journey of Linux kernel...
forum.xda-developers.com

Canny1913 said:
powersave forces the processor to work in the lowest frequency availible, thus consuming less power.
userspace allows the app to set the CPU frequency whatever it wants. This isn't supposed to be used in Android since changing CPU speed thorough an app is super uncommon.
Others like ondemand normally keep the power low but starts using the higher frequencies if a processor intensive app is launched.
You can learn which governors do what in this post so you can set the most suitable one for you.
[REF][GUIDE]Saber's guide on CPU governors, I/O schedulers and more!
Collective guide of CPU governors, I/O schedulers and other kernel variables I present to you a wonderful collection of descriptions, comparisons and graphs of common kernel variables. Before continuing on the wonderful journey of Linux kernel...
forum.xda-developers.com
Click to expand...
Click to collapse
I see. Well I guess it does work as a solution.
Thanks for the help!