Database Develop

[Announcement/Update] SetCPU Profiles w/ Manhattan Kernel

First of all, for anyone who has not yet tried the new Manhattan Project 1.6ghz kernel by Team Whiskey, i suggest you do so (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=821514). It is currently in alpha but so far has gotten outstanding feedback. Ive personally been running it and I'm not looking back.
Up until now its been well known that SetCPU profiles not only dont work on our phone, but also causes crashes and severe instability. However, SINCE I FLASHED THIS NEW KERNEL (and running Bionix Fusion 1.1), I have successfully profiled my phone. Here is what I've been running all day with absolutely no issues, and my phone running like LIGHTNING:
Main: 1600-200 Conserv.
Screen Off: 200-200 Conserv.
Temp > 50: 800-200 Conserv.
I posted these results in the kernel forum, but I also wanted to post them here for everyone to see because i know that the lack of SetCPU profiles has been a major complaint around here. If anyone would like to try this out and verify that it works for them also with this kernel, please post here, so everyone can finally enjoy the beauty of overclocking AND underclocking.
Once again, I'm running Manhattan Project Kernel and Bionix Fusion 1.1

Outstanding!

Appreciate the profiles. Should be a great help. I personally lowered my Temp to 40c but thats just my opinion

Excited to get the running will tell results soon!

So had my phone sitting for a bit, it became unresponsive and i think it had something to do with the sleep profile. I went ahead and changed it to 400/200 conserv for testing.

Awesome. But is the set on boot option still not working?
Oh and just an educated guess bit I would figure no Voodoo on this kernel. So disabling just in case before I update

YatimaMeiji said:
Awesome. But is the set on boot option still not working?
Click to expand...
Click to collapse
i dont even bother, its not really needed....even if its unchecked yoru settings are preserbed upon reboot
----------------
UPDATE #2: after 5 hours of no problems my phone finally started crashing, so i have may have spoken prematurely. But I'm stubborn, so Im still gonna try every damn combination possible until my phone tells me to go f*ck myself haha

I will post my feedback as well...
OP, are you running any lag fixes?

drizze99 said:
I will post my feedback as well...
OP, are you running any lag fixes?
Click to expand...
Click to collapse
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work

With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.

TopShelf10 said:
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
Click to expand...
Click to collapse
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz

jnp1974 said:
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
Click to expand...
Click to collapse
probably not going to help, but i certainly hope it does!!!

TopShelf10 said:
probably not going to help, but i certainly hope it does!!!
Click to expand...
Click to collapse
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
EDIT: I was testing different benchmarks with scaling on conservative, on-demand and performance to see if they altered my benchmark results. The difference was minimal, but I forgot to change scaling back to conservative and it wouldn't wake. When I pulled the battery, rebooted and checked SetCPU, it said conservative, but was stuck on performance. Changed to on-demand, left SetCPU, back in and changed to Conservative. It worked.

jnp1974 said:
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
Click to expand...
Click to collapse
dont be fooled, it can often work for a while before it shows its ugly side, be patient

I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
edit: for screen off don't be so stingy trying to set it to 200/200, if you need more battery life then get a bigger battery or spare batteries or Juice Defender , I usually set it to 200/800 and I have no issues.

TopShelf10 said:
dont be fooled, it can often work for a while before it shows its ugly side, be patient
Click to expand...
Click to collapse
I was fooled, ditching profiles altogether, boo

Can conferm that both profiles and set on boot work.
Sent from my Vibrant.

Mouahmong said:
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
Click to expand...
Click to collapse
i never check set on boot....what are your profile settings and what ROM/kernel are you running?

OK, I don't have mine OCLF yet but so far so good.
I have run Sleep profiles of 200/200 and 400/200 and the phone wakes up every time. I have gotten a txt message as well during my test and the screen lit up just like Bionix should! Will continue to kep messing with it....

turbosix said:
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
Click to expand...
Click to collapse
if it does so automatically then why is there an option to adjust "screen off" values?
Setcpu automatically scales between the high/low you set. SO if you let the main value stay at 1600-100..when the screen is off it will scale at a lower value of course cus you're not using the phone..but it wont stay at 200, because it has a Max of 1600! So depending on background processes it could scale back up to 4 or even 600 while screen is off
MY suggestions:
Download superpower battery saver from market, tweak to turn data on/off with screen and force ondemand cpu scaling
Download Autokiller--donate to get extra functions-- and set the value to Extreme or Ultimate when screen is off and Moderate or Optimal when it is on
I did that without setcpu profiles and it took 4 1/2 hrs to go from 81 % to 70
Im running Fusion 1.1 w/ Manhattan Project

Z3C laggy, mpdecision acting weird. Possibly found fix

So I'm having from the beginning extreme problems with stuttering and lag and couldn't really pinpoint it. Benchmarks went great and apps run good but not the animations and scrolling. Perticular on the homescreen, really really bad.
I installed Kernel auditor and looked at the stats and was quite baffled that mpdecision trottled down to one core. Thats not usual. Under Hotplug it was surpisingly disabled and switching it on did nothing, it just reverted back itself. I fiddled around when suddenly two cores stay on the whole time, like i experienced in the past from this hotplug. This was after running Antutu. I was like, naaah, this can't be it.
Looking in Kernel auditor the switch was suddenly on. I'm like wtf is going on here. What is causing this? Am i the only one that notices the stutter on a phone that got shipped thousands of times and praised in many reviews?? This can't be it. So i switched it on and off and then it goes. Only one core...
Switched it off then rebooted and guess what? 2 cores.
Please explain what is causing this cause i don't know what is going on
Added a little touchboost and now its pretty on par with the smoothness on my old Galaxy S5, but to be it would need a GPU touch boost too.
EDIT:
It's like i would enable this special function in stamina to lower the performance, exactly like that. I would be interested in other people having the same problems as i have!
EDIT2:
Maybe GPU acceleration is not in full effect? Using devloper settings i cant let me show what is rendered with the gpu. It just doesn't flash up.

Noone?

I've been having this problem too, on CM12. Sometimes I could go a couple days after a fresh flash with butter smooth animations, then it would revert to stuttery animation

zander21510 said:
I've been having this problem too, on CM12. Sometimes I could go a couple days after a fresh flash with butter smooth animations, then it would revert to stuttery animation
Click to expand...
Click to collapse
Interesting... but they're using different kernels. I first thought they tweaked the hotplug to be more aggressive, or something in the phone itself triggers that to get more battery life for sacrificing user experience... i dont know but for now its smooth even when i tame the interactive governer.
My S5 didn't had any of these problems. CM12 was extremely smooth but they have good custom kernel. I still think that somehow gpu rendering is borked...

boilavera1980 said:
Interesting... but they're using different kernels. I first thought they tweaked the hotplug to be more aggressive, or something in the phone itself triggers that to get more battery life for sacrificing user experience... i dont know but for now its smooth even when i tame the interactive governer.
My S5 didn't had any of these problems. CM12 was extremely smooth but they have good custom kernel. I still think that somehow gpu rendering is borked...
Click to expand...
Click to collapse
So what i did now to test is that i enabled the "old" hotplugging where it goes down to one core, even enabled core parking, but gave it a near 2ghz touch boost for 500ms now.
I'm really curious if someone tested this : http://forum.xda-developers.com/xperia-z/development/mod-gpu-rendering-tweak-t2286709
I can't do it right now because i need my phone at his moment, but could test it tonight and see what happens.

boilavera1980 said:
So what i did now to test is that i enabled the "old" hotplugging where it goes down to one core, even enabled core parking, but gave it a near 2ghz touch boost for 500ms now.
I'm really curious if someone tested this : http://forum.xda-developers.com/xperia-z/development/mod-gpu-rendering-tweak-t2286709
I can't do it right now because i need my phone at his moment, but could test it tonight and see what happens.
Click to expand...
Click to collapse
Okay so i stumbled upon this thread http://forum.xda-developers.com/showthread.php?t=2769899 and tweaked the interactive gouvers in this way. Stay pretty good idle and is very smooth like i wanted it. Don't know about battery life but i cant stand a stuttery mess.

2 cores stucked at max freq? am I the only one to have this problem?

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.

Is there a way to always have cpu cores offline?

Hi,
Id like to disable two of the cores for the little prosessor and the big prossesor. So core; 2-3, 6-7.
Id like to do this to reduce heat... Ive disabled the cpu cores in the kernel, but somehow they can get back online... Ive modified the thermal config to always have them hotplugged or disabled.
It would be nice to have them offline during boot as well.
Any thoughts? Or anyone who knows more about this than me?
Thanks!

bjowol said:
Hi,
Id like to disable two of the cores for the little prosessor and the big prossesor. So core; 2-3, 6-7.
Id like to do this to reduce heat... Ive disabled the cpu cores in the kernel, but somehow they can get back online... Ive modified the thermal config to always have them hotplugged or disabled.
It would be nice to have them offline during boot as well.
Any thoughts? Or anyone who knows more about this than me?
Thanks!
Click to expand...
Click to collapse
i've been trying to do this for about a month with no luck at all. flashed multiple roms and kernels trying to achive it but no.
i think its a pretty dead end. even kernels which stated that cores was turned of didn't do the trick

well, in its latest iterations SunKernel does only allow 3 cores during bootup (http://forum.xda-developers.com/xpe...el-zachs-kernel-playground-z4-z3-wip-t3404587),
and you can modify the hotplug behavior of the cores with @RyTekk 's thermal-engine and qcom modifications (http://forum.xda-developers.com/xperia-z5/general/tweak-improve-performance-reduce-t3387879)

zacharias.maladroit said:
well, in its latest iterations SunKernel does only allow 3 cores during bootup (http://forum.xda-developers.com/xpe...el-zachs-kernel-playground-z4-z3-wip-t3404587),
and you can modify the hotplug behavior of the cores with @RyTekk 's thermal-engine and qcom modifications (http://forum.xda-developers.com/xperia-z5/general/tweak-improve-performance-reduce-t3387879)
Click to expand...
Click to collapse
I did modify the hotplug behavior, telling it to always have two of the big cores offline, and did turn off two of them in the kernel as well, but sometimes entering camera or games the cores would turn on...
I managed to increase my devices performance after a lot of trickery but now i sent it in to my provider in hopes to get mye money back...
Is there a thread here siggesting other phones? Im looking at the nexus 5x or the upcoming nexuses

[TWRP ZIP] Underclock CPU without messing up mp-decision

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