I wrote an overclocking app today that will become opensource as soon as I put the source online(lol). This is confirmed to work on at least Haykuro's 5.0.1G ROM. Allows setting custom min and max cpu frequency. Enjoy . (Thanks buttkicker for this idea)
And the source code is now live on googlecode.
site is: http://code.google.com/p/openoverclocker/
UPDATE: New version up. Everything is now working and tested on both JF and Haykuro. Will continue to set clock even after reboot, so enjoy!
[email protected] said:
I wrote an overclocking app today that will become opensource as soon as I put the source online(lol). This is confirmed to work on at least Haykuro's 5.0.1G ROM. Allows setting custom min and max cpu frequency. Currently gets reset on restart but will fix that soon as well. Enjoy . (Thanks buttkicker for this idea)
Click to expand...
Click to collapse
Nice Marcus! Just downloaded it from the marketplace, and it works! I don't mind the reset after restart because honestly, how often do we restart our phones? Confirmed working on 5.0G (apps to sd) as well. go poly! =]
Question: would it harm the phone to set min and max to 528?
wow, it works fine. thank you. its pretty fast
it doesn't seem to work in the H version
Hmm darn no go on H eh? Lol I'll have to wait till someone figures out how to overclock that one and then incorperate it.
Perrosky said:
it doesn't seem to work in the H version
Click to expand...
Click to collapse
I am running 5.0.2H, and it should work.
[email protected], are you doing anything different in the app?
Hmm no, not really. Except that I'm saving the values in files and then cat-ing them out to the frequency files. Perrosky, did you set a different minimum? It will scale between them so it might not run at max when you look at /proc/cpuinfo
seems to work fine with my G1. is this actually overclocking or just clocking the processor to its max.
jaboswell said:
seems to work fine with my G1. is this actually overclocking or just clocking the processor to its max.
Click to expand...
Click to collapse
As I understand it, the G1 has a scalable 512 MHz processor, so this is clocking it to it's max specs.
testing567 said:
As I understand it, the G1 has a scalable 512 MHz processor, so this is clocking it to it's max specs.
Click to expand...
Click to collapse
Thats what I thought, was reading it somewhere but couldnt remember so I just asked..
well some programs seem to run faster, but that could just be me.. i ran cat /proc/cpuinfo and got a speed of 383.38...i have it set to min 384 max 524 even tried 512 as max..when i run some programs it seems faster than before..but when i run term. emu to get speed it resets the app to 384 max. 248 min.
I got the 5.0.1H...
and I don't think it works for me too...
how to check ? If I set Max to 528 MIN 248 and click "apply" nothing happen
if I set MAX/MIN both 528.. phone hang/crash
victortung said:
I got the 5.0.1H...
and I don't think it works for me too...
how to check ? If I set Max to 528 MIN 248 and click "apply" nothing happen
if I set MAX/MIN both 528.. phone hang/crash
Click to expand...
Click to collapse
Hmm interesting on the phone hanging. For the 528 max and 248 min the phone will run faster when taxed but will run the same at low points. Maybe try 528 max and 400 min and then see what "cat /proc/cpuinfo" says? If it says anything over 348 then you're already over what the normal maximum is
jaboswell said:
Thats what I thought, was reading it somewhere but couldnt remember so I just asked..
well some programs seem to run faster, but that could just be me.. i ran cat /proc/cpuinfo and got a speed of 383.38...i have it set to min 384 max 524 even tried 512 as max..when i run some programs it seems faster than before..but when i run term. emu to get speed it resets the app to 384 max. 248 min.
Click to expand...
Click to collapse
App always resets to 384 max and 248 min, I hardcoded those in. Next revision should support loading the actual speed and remembering what you put last.
After reboot, sometimes it hangs while requesting superuser access, then crashes.
Doesn't seem very different thus far. Any way to benchmark it?
I guess we'll find out if our battery life shortens.
Edit: Nevermind... I found my answer in this thread.
Saw this last night during my nightly before-I-sleep market app search.
Thanks!
[email protected] said:
Hmm no, not really. Except that I'm saving the values in files and then cat-ing them out to the frequency files. Perrosky, did you set a different minimum? It will scale between them so it might not run at max when you look at /proc/cpuinfo
Click to expand...
Click to collapse
sorry for my late post, I set the min at 328 and max at 500 I hit apply and the overclock apk just stay still, then when I use the Terminal to see the speed I show 258
Perrosky said:
sorry for my late post, I set the min at 328 and max at 500 I hit apply and the overclock apk just stay still, then when I use the Terminal to see the speed I show 258
Click to expand...
Click to collapse
Do you have the superuser whitelist app installed.
You will need that.
Not sure, but since the cpu is scaling, the terminal or other program would show the current cpu usage when it reads and display it.
So, if you're not doing anything in the OS, the readout would be near the low-end, when you check the freq.
I tried the software, but I wish it had a button to monitor or show the cpu mhz somewhere.
clspdhax1 said:
Not sure, but since the cpu is scaling, the terminal or other program would show the current cpu usage when it reads and display it.
So, if you're not doing anything in the OS, the readout would be near the low-end, when you check the freq.
I tried the software, but I wish it had a button to monitor or show the cpu mhz somewhere.
Click to expand...
Click to collapse
That will be in the next version. That's why it says MHz at the top, planning on putting the number there but gonna have to do some parsing of /proc/cpuinfo... somehow...
Related
Why does it not clock to the selected CPU speed???
I am running the latest released DUDE ROM,
No matter what I try it still does not clock up
suggestions?
The only sure way I have found to ramp it up (in JF1.5 at least) is to set the min and max to 528. It will instantly ramp it to 527. You can definately tell the difference in the phone, but I haven't had the guts to leave it on for any length of time.
cl2eep said:
The only sure way I have found to ramp it up (in JF1.5 at least) is to set the min and max to 528. It will instantly ramp it to 527. You can definately tell the difference in the phone, but I haven't had the guts to leave it on for any length of time.
Click to expand...
Click to collapse
I have set it at 528min and 528max and i have let it run for days and no problems what so ever.
worked great for a while then kept force closeing anyone haveing problems??
It seems to be working fine for me. One thing is that when I set the clock to 128 or something, the status displayed on the widget still shows 527. The performance is significantly slowed so I assume it's doing it's job.
Overall I think it's a nice little widget. Great for maxing out performance, and maxing battery life by limiting performance.
Phone:
Black G1
JF 1.51
Yup...me too
I will make the change but it sometimes does not refresh the gui. It will also not work if you reboot. (if i remember correctly) also tons of force closes. I am on 6.01 and have tried JF1.5 and am curently on HERO but have not had success with the widgets on the build yet so I dont have a confirmation.
Could someone post the previous version of this app please? The updated version on the market shows "problem loading gadget" on the Hero rom when you add it to the screen..previous versions worked without any problems. Thanks in advance.
edit: nm..fixed it..just had to run the odex optimization script and all is good again
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
what is a good configeration for over clock..i dotn want to mess up my phone??
I was thinking the same and should I have it on always max. Or what?
I've got mine set to 128Mhz min and 527Mhz max, it has drastically increased my battery life. Batter life barely drops 1% overnight.
Anyone have the Version before the 1.7 update. The new update doesnt seem to work on hero w/ Rosie.
You can grab the 1.6 apk from the Dev's Google Site (check the Files section).
1.7 doesn't work with Ion for me either
zgmf-x322a said:
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
Click to expand...
Click to collapse
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
IronCross1788 said:
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
Click to expand...
Click to collapse
The creator of the original Overclock app hasn't updated his application for even Cupcake build support yet. I thought he removed it from the market.
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yeah NeoBlade (thanks!) gave me the tip on that one yesterday. Seems to be helping a ton.
Min384Max527
Screen off Min128Max245
I can't find Overclock Widget in Market, was it removed?
I have the Overclock Widget and my question is, is it bad for my phone that while my screen is on i have it a min 527 max 527 then while screen off min 128 max 245... I've noticed that phone charges last longer but the useage of going back and forth determental to the phone? Thanks
coolbho3000 said:
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
Click to expand...
Click to collapse
Thanks, that would be of great help. Specially the battery profile settings. If you could also put a monitor, be it a widget or something on the notification bar it would be beyond awesome, or maybe a just notification of when the speed is changed and to what it was changed to.
Does anyobdy know if this SETCPU works on Hero ?
And must the app be on after i set the clock or can i close the app after ?
*bump* need to know
im using serendipity 4.0.1, and rGB-v.4-Voodoo #10, im new to UV the phone, but i search in the post and found a template, i applied it and save it as boot setting, when i pressed the back button and open the app again, the values reseted, how do i maintain them?
The values reset because you didn't hit "Apply for now".
"Apply for now" applies the values until you reboot the phone and "Save as boot setting" saves your settings for everytime the phone boots up.
So, either put everything back in and hit "Apply for now" or restart the phone. I recommend erasing your bootup settings and hitting "Apply for now" so you don't end up in a boot loop if your settings are not stable.
how do i erase my bootup settings?
i dont know how to set up my voltage control app, it keep crashing on me
also consider the battery life for normal usage when oc ...
im not trying to over clock, i just want to save on battery but i cant seem to set up Voltage Control without crashing, i dont know what to do anymore, i cant set it up!!
hernan078 said:
im not trying to over clock, i just want to save on battery but i cant seem to set up Voltage Control without crashing, i dont know what to do anymore, i cant set it up!!
Click to expand...
Click to collapse
Try going to adb shell and removing it, and then reinstalling it. If that doesn't work you might just need to reflash Serendipity.
Auridran said:
Try going to adb shell and removing it, and then reinstalling it. If that doesn't work you might just need to reflash Serendipity.
Click to expand...
Click to collapse
i think the problem is not the app, is the values im using, i dont know what to do, i was pumped to using voltage control to save battery!
hernan078 said:
i think the problem is not the app, is the values im using, i dont know what to do, i was pumped to using voltage control to save battery!
Click to expand...
Click to collapse
Have you tried lower values? Does it do the same thing?
I lower the values and it works, for a while, when i press the lock button i wait 2 minute or less and the phone crashes and i have to do a battery pull out!
hernan078 said:
I lower the values and it works, for a while, when i press the lock button i wait 2 minute or less and the phone crashes and i have to do a battery pull out!
Click to expand...
Click to collapse
What values are you using? Not all the processors in the phones are created equal, and some don't like to be run very far out of spec.
I would recommend to start conservatively.
Note: If u r using OC based kernels, try not to reduce much voltage from any step over 1200. I think I read in some post there (probably glitterballs' kernel related one) that 1200 and 1280 both use same voltage levels. So its best to be conservative on that end.
Values I regarded as safe are 100, 100, 75, 50, 50, 50 (bottom to top), and the ones I am currently using are 125, 125, 100, 75, 75, 50 (bottom to top), and I have my speed capped at 1000 (since this is sufficient for my needs).
diablo009 said:
I would recommend to start conservatively.
Note: If u r using OC based kernels, try not to reduce much voltage from any step over 1200. I think I read in some post there (probably glitterballs' kernel related one) that 1200 and 1280 both use same voltage levels. So its best to be conservative on that end.
Values I regarded as safe are 100, 100, 75, 50, 50, 50 (bottom to top), and the ones I am currently using are 125, 125, 100, 75, 75, 50 (bottom to top), and I have my speed capped at 1000 (since this is sufficient for my needs).
Click to expand...
Click to collapse
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
hernan078 said:
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
Click to expand...
Click to collapse
Your phone may just not be quite capable of those undervoltages. It might not be capable of any undervolting at all. Remember, undervolting is running the processor out of spec. It's all luck of the draw if you get a processor that is from the top of the bin or a processor that is from the bottom of the bin.
Auridran said:
Your phone may just not be quite capable of those undervoltages. It might not be capable of any undervolting at all. Remember, undervolting is running the processor out of spec. It's all luck of the draw if you get a processor that is from the top of the bin or a processor that is from the bottom of the bin.
Click to expand...
Click to collapse
but it doesnt matter what kernel im running? if i use a kernal that dont support UV, i cant UV? The kernel im using, support undervolt?
hernan078 said:
but it doesnt matter what kernel im running? if i use a kernal that dont support UV, i cant UV? The kernel im using, support undervolt?
Click to expand...
Click to collapse
As far as I know, every kernel that supports overclocking for the Captivate supports undervolting. I know for a fact the kernel you're using does.
Auridran said:
As far as I know, every kernel that supports overclocking for the Captivate supports undervolting. I know for a fact the kernel you're using does.
Click to expand...
Click to collapse
And what you suggest is the problem? :S
hernan078 said:
And what you suggest is the problem? :S
Click to expand...
Click to collapse
Like I said, your CPU probably can't handle the level of undervolting you're trying to give it. Also, some peoples' phones can't even reach 1.28GHz (the stock clock of the kernel you're using) without undervolting at all, so your problem could easily lie there, unless you've limited the clock to 1GHz in Voltage Control.
hernan078 said:
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
Click to expand...
Click to collapse
Is it crashing for the values in green too? They were supposed to be very conservative, and the ones I regard as "safe".
And like "Auridran" quoted, try limiting speed to 1000.
Edit: I would recommend u starting with 25 for lower speeds, and try not reducing voltage at speeds over 800.
When battery goes low and 2 cores are shutted off, when they come back on they will be stuck to max freq, it happens even with thermal throttling, I have not the solution to this problem, if someone more capable of me may help me I will be glad
fedef12evo said:
Nexus 6 is a good phone, but there are lot of small glitches, one of them is the freq stucked to max (2649000) for 2 cores, it happens when phone goes thermal throttling, and thermal manager shut down 2 cores, then when temperature goes down to safe, mpdecision will push online the 2 cores shutted down and 90% they will get stucked to max freq,to avoid this annoying bug I modified thermalconfig for shamu to avoid shutting down cores in hot situations,thermal manager will work anyways by lowering max freq but it will no longer disable cores.
https://www.dropbox.com/s/802p4kr0kqcj7g0/thermal-engine-shamu.conf?dl=0
here the thermal engine modified, if anyone is able to make a flashable zip post here. Push thermal engine to system/etc, and set permission 0644 or rw-r--r--
Click to expand...
Click to collapse
lol, you went about it the LOOOOOOOOOONG way around. i just turn off thermal throttling when i boot. but thats not the main kicker, i also use a different cpu system. i change my governor to ondemand, and it all functions better.
anyways, this is how you disable thermal throttle via a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
simms22 said:
lol, you went about it the LOOOOOOOOOONG way around. i just turn off thermal throttling when i boot. but thats not the main kicker, i also use a different cpu system. i change my governor to ondemand, and it all functions better.
anyways, this is how you disable thermal throttle via a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
Click to expand...
Click to collapse
with ondemand, power consumption is more than interactive, also I need thermal throttling, because when cpu temp is more than 50 degrees is very hard to touch the screen
fedef12evo said:
with ondemand, power consumption is more than interactive, also I need thermal throttling, because when cpu temp is more than 50 degrees is very hard to touch the screen
Click to expand...
Click to collapse
lol, 50? seriously? i guess mobile computers are not for you then, as 50C is a normal temperature, before thermal throttle kicks in. and no, ondemand is much better for battery consumption. i see 5.5-7 hours sot every single day.
Interactive works quite well
lol, all the governors work well, just how they are supposed to.
simms22 said:
lol, you went about it the LOOOOOOOOOONG way around. i just turn off thermal throttling when i boot. but thats not the main kicker, i also use a different cpu system. i change my governor to ondemand, and it all functions better.
anyways, this is how you disable thermal throttle via a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
Click to expand...
Click to collapse
Interesting! Does this work on stock+root?
toastgodsupreme said:
Interesting! Does this work on stock+root?
Click to expand...
Click to collapse
yes
simms22 said:
yes
Click to expand...
Click to collapse
Seems mine was disabled by default. So no effort needed by me then.
Didn't Franco try this awhile ago but abandon it because it was so unstable??
toastgodsupreme said:
Seems mine was disabled by default. So no effort needed by me then.
Click to expand...
Click to collapse
fsync is always enabled. the reason for this is if you crash, and fsync is disabled, you can lose data(or not boot up after). so, its ALWAYS enabled unless you disable it manually.
simms22 said:
fsync is always enabled. the reason for this is if you crash, and fsync is disabled, you can lose data(or not boot up after). so, its ALWAYS enabled unless you disable it manually.
Click to expand...
Click to collapse
fsync? i was talking about echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
fedef12evo said:
Nexus 6 is a good phone, but there are lot of small glitches, one of them is the freq stucked to max (2649000) for 2 cores, it happens when phone goes thermal throttling, and thermal manager shut down 2 cores, then when temperature goes down to safe, mpdecision will push online the 2 cores shutted down and 90% they will get stucked to max freq,to avoid this annoying bug I modified thermalconfig for shamu to avoid shutting down cores in hot situations,thermal manager will work anyways by lowering max freq but it will no longer disable cores.
https://www.dropbox.com/s/802p4kr0kqcj7g0/thermal-engine-shamu.conf?dl=0
here the thermal engine modified, if anyone is able to make a flashable zip post here. Push thermal engine to system/etc, and set permission 0644 or rw-r--r--
Click to expand...
Click to collapse
Well.... I've never seen that happen, or even heard of it. You running some kind of hacked up "custom" junk rom or something? That certainly is NOT normal behavior. Its also the wrong way to fix that kind of issue if you did happen to have a problem like that.
The proper solution is to get rid of whatever brokenness you have that is causing it, or diving into the code to fix whatever is broken. Disabling critical features is not a solution.
doitright said:
Well.... I've never seen that happen, or even heard of it. You running some kind of hacked up "custom" junk rom or something? That certainly is NOT normal behavior. Its also the wrong way to fix that kind of issue if you did happen to have a problem like that.
The proper solution is to get rid of whatever brokenness you have that is causing it, or diving into the code to fix whatever is broken. Disabling critical features is not a solution.
Click to expand...
Click to collapse
It happens in alla Roms, even stock ROM, only with interactive governor.
toastgodsupreme said:
fsync? i was talking about echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
Click to expand...
Click to collapse
sorry, i was having a conversation in another thread about fsync.. i mistook which thread i was in :angel:
fedef12evo said:
It happens in alla Roms, even stock ROM, only with interactive governor.
Click to expand...
Click to collapse
Definitely not present on stock, so if you're experiencing it, its something you did to yourself.
doitright said:
Definitely not present on stock, so if you're experiencing it, its something you did to yourself.
Click to expand...
Click to collapse
then it is hardware problem of my device
Forgive my newish question: how do we monitor cpu frequencies to know if they're stuck?
electricpete1 said:
Forgive my newish question: how do we monitor cpu frequencies to know if they're stuck?
Click to expand...
Click to collapse
there are many google play and non play store apps that do this. many!
fedef12evo said:
then it is hardware problem of my device
Click to expand...
Click to collapse
I really don't see how a hardware problem could have that kind of a side-effect.
First of all, all credits go to @Tomoms that kindly created the zip.
Our bacons are getting pretty old especially on the battery side. After using sultanxda rom that was underclocked to 1958 Mhz i noticed a nice improve of SOT without sacrificing performance too much .
Unfortunately, on every other ROM, changing frequencies trough kernel tweaking apps (ie kernel adiutor) results in Qualcomm mp-decision not behaving correctly, cores not going offline and frequencies scaling pretty much messing up.
This zip underclocks correctly your CPU to 1958mhz, without the need of any third party app, hope you ll find it useful.
Again, all credits go to @Tomoms
Let me add that the zip should be universal, that is, I expect it to work on all Oreo ROMs and probably on Pie/Nougat ROMs as well. If it doesn't work on certain ROMs, I'll update it to support all of them.
Flash it now. I'm running android 9 pie and it works for me. It reduces my overheating problem!!!!!
Thanks a lot!!!!!
Do you make GPU boost settings for gaming? i need this for not rooted phone.
@Tomoms can you make one For Oneplus 2.
Is this work on cyanogen os 13?
omgomgomg i was wondering about this for so long !
my fault for not checking this place for 2 years lol. I also used Kernel Adiutor which misbehaved at times, random overheating after settings failing to apply on boot, and noticed mdprecision erros in the logs
1958 MHz is also the frequency i used, how is this all a coincidence ^^
Is it possible to edit a value in the zip to underclock to 2.3 Ghz ? (i don't remember the exact number)
Not that i need it, just wondering. OPO currently pretty dead from weird cpu/power/battery issues, if this fixes I'll be ecstatic
so how do u make it back to default?
Can the number be set in the `anykernel.sh` file to any reasonable clock speed? such as 1750Mhz? Or does it need to be a specific multiple, or something?
sgtfoo said:
Can the number be set in the `anykernel.sh` file to any reasonable clock speed? such as 1750Mhz? Or does it need to be a specific multiple, or something?
Click to expand...
Click to collapse
It has to be a valid frequency of the OPO's CPU. You can find a list here: https://github.com/LineageOS/androi...174a0802/arch/arm/boot/dts/msm8974.dtsi#L1548
Not working on the microg build of lineage OS
The script runs fine with no errors but when I boot back to android the max CPU freq is still unchanged.
Not sure where I can find the debug log to post here,
Thanks.
ffff2 said:
Not working on the microg build of lineage OS
The script runs fine with no errors but when I boot back to android the max CPU freq is still unchanged.
Not sure where I can find the debug log to post here,
Thanks.
Click to expand...
Click to collapse
Updated zip that should work on newer ROMs:
https://mega.nz/file/VoURxIZD#l2bL5yS0cArj47ablsxHjuFLughHSPt1aORJR2F3T0k
EDIT: it underclocks all CPUs to 1,9 GHz, as in Sultan's ROM. Not tested but it should really work. If anyone tries it, please give me feedback
Tomoms said:
Updated zip that should work on newer ROMs:
https://mega.nz/file/VoURxIZD#l2bL5yS0cArj47ablsxHjuFLughHSPt1aORJR2F3T0k
EDIT: it underclocks all CPUs to 1,9 GHz, as in Sultan's ROM. Not tested but it should really work. If anyone tries it, please give me feedback
Click to expand...
Click to collapse
I had revived my account just to say thank you!
CPU frequencies seem to be working fine on most recent Lineage OS 17.1 and CPU info never shows usage above 1958 MHz.
It's amazing that this phone has survived 8 years, here's hoping it can survive 8 more.
Artos0131 said:
I had revived my account just to say thank you!
CPU frequencies seem to be working fine on most recent Lineage OS 17.1 and CPU info never shows usage above 1958 MHz.
It's amazing that this phone has survived 8 years, here's hoping it can survive 8 more.
Click to expand...
Click to collapse
What app are you using to check CPU clock speeds?
Artos0131 said:
I had revived my account just to say thank you!
CPU frequencies seem to be working fine on most recent Lineage OS 17.1 and CPU info never shows usage above 1958 MHz.
It's amazing that this phone has survived 8 years, here's hoping it can survive 8 more.
Click to expand...
Click to collapse
Can I flash the ZIP file through TWRP? How would I remove this app if necessary?
why new frequency not show? how to fix
Tomoms said:
It has to be a valid frequency of the OPO's CPU. You can find a list here: https://github.com/LineageOS/androi...174a0802/arch/arm/boot/dts/msm8974.dtsi#L1548
Click to expand...
Click to collapse
Tomoms said:
It must be the frequency obtained by multiplying 192MHz BCLK with the multiplier
Click to expand...
Click to collapse