Related
Hi,
thinking of make launcher(s) as smooth as possible, while keeping best possible battery life, I was thinking os a probably foolish thing:
could be possible to write a script (even an init.d or something similar) that finds which CPU core is running the launcher and then sets up frequencies/governor for that core only ?
This way one could define the good performance/power level for the overall phone and apps, while still boosting the launcher performance.
Totally crazy ?
Doable ? How ?
Dual core is why we bought the S2 for mate
Sent from my GT-I9100 using xda premium
leminhnguyen0703 said:
Dual core is why we bought the S2 for mate
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Maybe it's so, but still some clever heads are doing good work making new opporutinies for us.
Tegrak has made an app 2nd Core, witch make you set these 3 different options, but only for Lutz kernel build 15 and up. Siyah's kernel is coming up with a beta soon supporting the settings below. For now you only see what core is active/inacitve.
[ Features ]
*Set on boot
Change mode what you selected automatically on boot time.
Menu > Settings
[ Modes ]
*Dynamic Hotplug Mode
Default. Recently, mobile multicore CPUs turn off extra core(s) to save battery life when system is not busy and only use 1 core.
They turn on extra core(s) when system is busy. so system use all cores again.
*Single Core Mode
Use 1 core always. A extra core is shut down. It makes battery life longer but performance is decreased.
*Dual Core Mode
Use 2 cores always. Performance is increased but battery life is shorter than others.
https://market.android.com/details?...1bGwsMSwyLDEsImNvbS50ZWdyYWsuc2Vjb25kY29yZSJd
If it will possible to set different OC's,UV's for each core, I don't know but lets see what the Lutz and the Siyah kernels brings in the future.
nilste said:
Maybe it's so, but still some clever heads are doing good work making new opporutinies for us.
Tegrak has made an app 2nd Core, witch make you set these 3 different options, but only for Lutz kernel build 15 and up. Siyah's kernel is coming up with a beta soon supporting the settings below. For now you only see what core is active/inacitve.
[ Features ]
*Set on boot
Change mode what you selected automatically on boot time.
Menu > Settings
[ Modes ]
*Dynamic Hotplug Mode
Default. Recently, mobile multicore CPUs turn off extra core(s) to save battery life when system is not busy and only use 1 core.
They turn on extra core(s) when system is busy. so system use all cores again.
*Single Core Mode
Use 1 core always. A extra core is shut down. It makes battery life longer but performance is decreased.
*Dual Core Mode
Use 2 cores always. Performance is increased but battery life is shorter than others.
https://market.android.com/details?...1bGwsMSwyLDEsImNvbS50ZWdyYWsuc2Vjb25kY29yZSJd
If it will possible to set different OC's,UV's for each core, I don't know but lets see what the Lutz and the Siyah kernels brings in the future.
Click to expand...
Click to collapse
+1. This is pure ingenuous. Since our phones seldom used the second core, it currently.is a battery hog and this app will brilliantly manage our battery life while maintaining the same level of performance. This will definitely improve our battery life by a significant margin.
Sent from my MB860 using XDA App
Probably I was too optimistic thinking Android is capable to turning off unused cores ?
My initial goal was to
- find which core executes home launcher (let's say core 2)
- leave core 1 untouched (1200/200)
- overclock core 2 to 1600/200
yet, if Android (or MIUI kernel to say my example) is dumb about switching off unused core, the solution discussed above becomes really interesting...
It is impossible to clock the cores independently. It IS possible to completely shut down the second core, effectively removing it from the system. Our system does this by default.
It's already done when system load is low. arighi has some kernel patches that change the hotplug heuristics to change when the second core gets fired up:
https://github.com/arighi/linux-gt-i9100
He's got a thread on it somewhere too.
Entropy512 said:
It is impossible to clock the cores independently. It IS possible to completely shut down the second core, effectively removing it from the system. Our system does this by default.
It's already done when system load is low. arighi has some kernel patches that change the hotplug heuristics to change when the second core gets fired up:
https://github.com/arighi/linux-gt-i9100
He's got a thread on it somewhere too.
Click to expand...
Click to collapse
If i remember rights there was a script tath can undervolt cpu independently, but i think that the launcher dont use especialy one core, but switch or use both of them
Tl;Dr is it possible to turn off Samsung's built in frequency adjusting/locking?
I was messing around with clock speeds just to see what affect it might have (it used to be helpful on my Note 2 to raise the min clock speed a step or 2 when I turned my screen on) and noticed some strange behavior.
It seems Samsung has built in some of this. Every time I turn on my screen most cpu apps will tell me the min clock is set to something like 1.9 ghz. The built in stuff overrides any settings I apply. Now, the main reason I'd like to change this is the Samsung stuff seems buggy (surprised? Psh...) and the min cpu frequency seems stuck at 1.9 ghz. If true, that can't be good for battery.
So, anyway to turn that stuff off? I imagine it would require a custom kernel and I should just give up.
Thanks
Apps tried:
ROM toolbox pro
No frills cpu control
Antutu cpu master
Other free apps
Sent from my SM-G900V using Tapatalk
I think Wanam has an option for this or look in xposed for "Samsung DVFS Disabler"
Sent from my Galaxy Note S5
Sorry for the extremely late reply, but neither of those seem to work. Oh well, I'll just live with it. Thanks.
Sent from my SM-G900V using Tapatalk
It is simple, tested on my nexus 6, just go to system/bin and delete mpdecision, then install an app that controls kernel, like kernel adiutor, raise min freq of cpu to 883000 mhz, then set apply on boot, reboot phone and enjoy lagfree and smooth super battery life
you are my hero
fedef12evo said:
It is simple, tested on my nexus 6, just go to system/bin and delete mpdecision, then install an app that controls kernel, like kernel adiutor, raise min freq of cpu to 883000 mhz, then set apply on boot, reboot phone and enjoy lagfree and smooth super battery life
Click to expand...
Click to collapse
Isn't enough to just turn off mpdecision in the kernel app?
this only works for stock roms? I can't find any mpdecision file on /system/bin
Sent from my Nexus 6 using Tapatalk
blanco2701 said:
Isn't enough to just turn off mpdecision in the kernel app?
Click to expand...
Click to collapse
if it turn off the 3 sec boost of mpdecision yes
sgloki77 said:
this only works for stock roms? I can't find any mpdecision file on /system/bin
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
works on all roms for nexus 6, some file managers cant see mpdecision in system/bin, try it in recovery using twrp
fedef12evo said:
raise min freq of cpu to 883000 mhz
Click to expand...
Click to collapse
Can you tell me if it's the minimum CPU frequency in the CPU tab or in the CPU governor configuration?
blanco2701 said:
Isn't enough to just turn off mpdecision in the kernel app?
Click to expand...
Click to collapse
Disabling in a kernel app will accomplish the same thing. The reason you are seeing a change in battery life is because of the 3 second input boost of MPD. Most of the custom kernels have a generic touch boost driver that is set to 1 second or less to take the place of the mpd boost and increase battery because of the decreased boost time.
MPD works great for some people and not for others. It is greatly dependent on your usage habits. For my typical usage, with mpd on, I average 6-7 hours of screen on time. If you are a gamer, where you are constantly touching the screen, mpd will adversely affect your battery life because of the constant boost.
As a kernel developer, I definitely would not recommend deleting the mpd binary. I would suggest trying a couple of different kernels and/or configurations to accomplish the same results.
lol.. seriously? i guess thats one reason that ive disabled mpdecision for the last 3+ years on whichever nexus i was on, but not the main reason
How can I turn mpd off on ex kernel manager
you don't need a kernel app to disable it BTW. all kernel apps do is provide a ui for you to use. it can be done via a terminal emulator app.. type,
su(press enter)
stop mpdecision(press enter)
and that's it.
I'm using kernel auditor and in the CPU hotplug section the first listing is mp decision. Is that what needs to be disabled?
OK, silly question.. do you know what mpdecision does? do you know what disabling mpdecision does?
simms22 said:
OK, silly question.. do you know what mpdecision does? do you know what disabling mpdecision does?
Click to expand...
Click to collapse
@simms22 good point here. This is good for everyone to know. If you disable mpd without a replacement, you risk all cores not coming back online after deep sleep. Mpd doesn't actually control hotplugging, it controls input boost and onlining of cores.
Sent from my Nexus 6 using Tapatalk
and that's exactly why I disable mpdecision, so I can have all 4 cores active at all times.
buckmarble said:
@simms22 good point here. This is good for everyone to know. If you disable mpd without a replacement, you risk all cores not coming back online after deep sleep. Mpd doesn't actually control hotplugging, it controls input boost and onlining of cores.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
When you say without a replacement what are you referring to? Trying to learn here..
MrMiami81 said:
When you say without a replacement what are you referring to? Trying to learn here..
Click to expand...
Click to collapse
A replacement such as Zen, Mako, Blu_Plug, etc.
Also, (just an FIY) Zen isn't really a hotplug (it keeps all four cores active at all times, unlike Mako, Blu_Plug, etc). It's still lumped in there for some reason.
I highly recommend disabling MPDecision. You know what MPDecision stands for, right? MakePoor Decisions
Face_Plant said:
A replacement such as Zen, Mako, Blu_Plug, etc.
Also, (just an FIY) Zen isn't really a hotplug (it keeps all four cores active at all times, unlike Mako, Blu_Plug, etc). It's still lumped in there for some reason.
I highly recommend disabling MPDecision. You know what MPDecision stands for, right? MakePoor Decisions
Click to expand...
Click to collapse
I'm running elemental x now and I can't find mp decision on kernel auditor. Do you know if it is included with this kernel? If so how would I disable it?
MrMiami81 said:
I'm running elemental x now and I can't find mp decision on kernel auditor. Do you know if it is included with this kernel? If so how would I disable it?
Click to expand...
Click to collapse
i believe its already disabled in elementalx kernel. anyways, you can always use a terminal emulator app, then type..
su(press enter)
stop mpdecision(press enter)
thats all. all kernel apps do is give you a ui to whats already available.
MrMiami81 said:
I'm running elemental x now and I can't find mp decision on kernel auditor. Do you know if it is included with this kernel? If so how would I disable it?
Click to expand...
Click to collapse
Some kernels come with it already removed. Check the features section of the original post in the Elemental X thread or try searching the thread.
I can say from experience that Kernel Auditor doesn't give you access to all of the adjustments in Elemental X. Some features are only accessible through the official Elemental X app, so it might be there, but you can't use Kernel Auditor to adjust it.
Face_Plant said:
Some kernels come with it already removed. Check the features section of the original post in the Elemental X thread or try searching the thread.
I can say from experience that Kernel Auditor doesn't give you access to all of the adjustments in Elemental X. Some features are only accessible through the official Elemental X app, so it might be there, but you can't use Kernel Auditor to adjust it.
Click to expand...
Click to collapse
I just downloaded the elemental x app. I'm gonna go over to the thread now. I appreciate your help
I intended to delete thermal engine to unlock the maximum performance of S810, but I didn't after a half day for thinking. Then I took a look at thermal-engine and do some optimize for it.
When I looked at the thermal-engine, I saw it use emmc_therm (temperature of emmc) sensor to do throttle, and the throttle start too soon, from 43°C, detail is two cores 6 and 7 will be hotplug (plug out, turn off), and big cluster will be limited to 1.2GHz at just 47.7°C (the battery temperature is just ~40-41°C). You can see more detail in below:
Temperature (/1000 to get the values in Celcius):
43000
47700
48900
50200
51400
52000
52600
53200
53600
54000
54500
55000
55500
55900
56300
56800
Action: cluster0+cluster1+hotplug_4+hotplug_5+hotplug_6+hotplug_7+gpu+s_backlight+battery+modem+s_cam_ltb_tim+s_cam+s_tel
1555200+1958400+0+0+1+1+630000000+255+2+0+100000+0+0
1555200+1248000+0+0+1+1+630000000+209+3+0+100000+0+0
1478400+864000+0+1+1+1+630000000+171+3+0+100000+0+0
1478400+384000+1+1+1+1+630000000+141+3+0+100000+0+0
1344000+384000+1+1+1+1+630000000+115+3+0+100000+0+0
1344000+384000+1+1+1+1+630000000+95+3+0+100000+0+0
1248000+384000+1+1+1+1+630000000+78+8+0+100000+0+0
1248000+384000+1+1+1+1+630000000+64+8+0+001800+0+0
960000+384000+1+1+1+1+630000000+52+9+0+001800+0+0
960000+384000+1+1+1+1+450000000+44+12+0+001800+0+0
864000+384000+1+1+1+1+450000000+44+12+0+001800+0+0
864000+384000+1+1+1+1+390000000+44+12+1+001800+0+0
768000+384000+1+1+1+1+390000000+44+12+1+001800+0+0
600000+384000+1+1+1+1+180000000+44+12+1+001800+0+0
460800+384000+1+1+1+1+180000000+44+12+1+001800+0+0
384000+384000+1+1+1+1+180000000+44+12+1+001800+5+0
EXPLAIN (from my knowledge, maybe it's not right at all)
cluster0: LITTLE (A53 cores) cluster clock limitation, value: hertz
cluster1: big (A57 cores) cluster clock limitation, value: hertz
hotplug_4-7: 1 to hotplug (disable) the core, 0 to do nothing.
gpu: GPU frequency, value: hertz (?)
s_backlight: the maximum brightness of screen, range: 255-0
modem: 1 to disable mobile data, 0 to do nothing.
the rest: IDK
I did a quick research and found that emmc can work from -25°C to +85C, so the limitation that Sony has set is too low (for me), just do a Geekbench and then the performance will come down clearly. Then I edit thermal-engine to increase the maximum performance of S810 but still keep my phone (IDK about yours just because we're not the same) in peace.
So why do I post here? Firstly, for those who wanna take the risk like me to unlock/get the true performance of our devices; secondly, maybe my knowledge is not right so I want you who have certain knowledge about this (EMMC, battery limitation; thermal, blah blah blah) correct me and help me and other users improve it.
I've done attached two files, one is original and the other is mine, hope you guys (who are sensei) will take a look on it to contribute for the community. For those who wanna use them, backup thermal-engine.conf first in /system/etc then copy the modify to the direction, correct name and permission and reboot.
UPDATE:
Thanks to @Envious_Data, his guide helped me to manage big cluster, now I can turn 4 big cores always on by make them becomes "non big cores", so now our phones are true octa cores. I was afraid that there're some issues that will appear such as heating, throttle (thermal manage won't work correct if it recognizes big cluster to be little cluster) so I made a test with Antutu Stress test and monitor CPU cores via Trepn Profiler, and amazing, thermel engine still works fine and my phone's temperature isn't different from old/original settings (just 1 big core on time and will be plugged in if need) so far (of course it should be hotter but not much). And I updated new thermal values too to improve some performance in camera. About battery life, I guess it would not go so far from stock settings because I saw the current discharge (mA) isn't higher (a lot).
Update 17/06: re-setting back to big cores for the best compatibility after enable all 4 big cores, so true octa cores is still there with big core setting is 1 (true).
Update 23/06: new thermal-engine to adapt with OC from SunKernel, it still works fine with stock or even any different maximum clock speed in kernel, why? Because I simply just remove "clusterX" action instead of edit it to match with the maximum clock.
INSTALL: download MODIFY files and rename to init.qcom.post_boot.sh and thermal-engine.conf (due to XDA's restriction so I have to change their type), put in /system/etc/, correct permission (644 rw-r--r--) and reboot.
UPDATING... (depend on you)
Now i try your file, my phone give 89k in antutu constantly
You tweaked it to 63°c max? Sounds not bad at all..
Gonna try as soon as I have some time!
Sent from my E6653 using XDA-Developers mobile app
Alessandro2553 said:
Now i try your file, my phone give 89k in antutu constantly
Click to expand...
Click to collapse
Try to do test continue to see the lost of performance, I just use Geekbench in my phone.
langeveld024 said:
You tweaked it to 63°c max? Sounds not bad at all..
Gonna try as soon as I have some time!
Click to expand...
Click to collapse
Actually you can see the emmc_0 and emmc_1 so the maximum is 68 Celcius and start throttle from 52.4 Celcius, at that temperature of emmc I still don't notice hot in my hand.
Sent from my E6683 using XDA Labs
@RyTekk
Interesting, but for my daily use Z5 is more than performant enough.
Why do you still want better performance ? For games ??
RyTekk said:
Try to do test continue to see the lost of performance, I just use Geekbench in my phone.
Actually you can see the emmc_0 and emmc_1 so the maximum is 68 Celcius and start throttle from 52.4 Celcius, at that temperature of emmc I still don't notice hot in my hand.
Sent from my E6683 using XDA Labs
Click to expand...
Click to collapse
And which model do you have?
nreuge said:
@RyTekk
Interesting, but for my daily use Z5 is more than performant enough.
Why do you still want better performance ? For games ??
Click to expand...
Click to collapse
I think we can also benefit from this when running heavy tasks like camera AR or 4K video.
I can feel phone slowing down after few minutes.
Sent from my E6653 using XDA-Developers mobile app
nreuge said:
@RyTekk
Interesting, but for my daily use Z5 is more than performant enough.
Why do you still want better performance ? For games ??
Click to expand...
Click to collapse
Because I got lost in performance so fast when just did install an app or play a single benchmark, I wanna unlock the highest as possible, Sony did limitation so much.
langeveld024 said:
And which model do you have?
Click to expand...
Click to collapse
E6683 dual sim variant as you see in my sign.
Sent from my E6683 using XDA Labs
Alessandro2553 said:
Now i try your file, my phone give 89k in antutu constantly
Click to expand...
Click to collapse
What kernel are you using? I've just got reboot when do Antutu bench, two times.
Androplus v30 with stock setting governor and clock speed
I have almost 84k on stock kernel. Nice
I've used this for some days now.
Was in Turkey last week (30°c) and all was fine.
In fact, performance seems much better.
I don't use benchmarks at all but I can feel multitasking is faster for a longer time and so for camera applications.
I'm now using it on 224 fw and Andro-kernel v31 and all seems good so far.
Thank you!
Sent from my E6653 using XDA-Developers mobile app
Any way to disable big cores permanently on latest firmware 32.2.a.0.224 z5 dual E6683
rajdeep312 said:
Any way to disable big cores permanently on latest firmware 32.2.a.0.224 z5 dual E6683
Click to expand...
Click to collapse
You mean thermal management for big cores?
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
You mean thermal management for big cores?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
I want to stop big cores permanently i read somewhere big cores cause heat up device while playing games about 5 min my device burn my hand so want to reduce heat like my galaxy s7 exynos
rajdeep312 said:
I want to stop big cores permanently i read somewhere big cores cause heat up device while playing games about 5 min my device burn my hand so want to reduce heat like my galaxy s7 exynos
Click to expand...
Click to collapse
U can set it via sysfs path in init.d or su.d script, depending on what kernel u use (different paths)
Note that especially for heavy tasks u will notice performance drop when disabling these cores.
I disables two big cores and for light use it was okay but the camera app started to lag.
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
U can set it via sysfs path in init.d or su.d script, depending on what kernel u use (different paths)
Note that especially for heavy tasks u will notice performance drop when disabling these cores.
I disables two big cores and for light use it was okay but the camera app started to lag.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Plz make file for me i am newbie 1. All big cores stopped and 2. Like u 2 big cores stopped
rajdeep312 said:
Plz make file for me i am newbie 1. All big cores stopped and 2. Like u 2 big cores stopped
Click to expand...
Click to collapse
I would, if I'd knew the exact sysfs path your installed kernel uses.
Are u running andro-kernel?
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
I would, if I'd knew the exact sysfs path your installed kernel uses.
Are u running andro-kernel?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Using this rootable kernel E6683 dual
http://forum.xda-developers.com/xperia-z5/development/32-2-0-224-ftf-rootable-kernel-t3391071
rajdeep312 said:
Using this rootable kernel E6683 dual
http://forum.xda-developers.com/xperia-z5/development/32-2-0-224-ftf-rootable-kernel-t3391071
Click to expand...
Click to collapse
Then most likely you're using core_ctl.
This thread is about minimizing thermal throttling (a.k.a wanting hotter phone, not cooler phone lol)
This is wrong thread to discuss this, head over to this thread:
http://forum.xda-developers.com/showthread.php?t=3376233
If using andro-kernel, I made a script for it, check here:
http://forum.xda-developers.com/showthread.php?t=3246100
Next time, give XDA search function a shot. It is such a nice feature, worth a try
Regards
rajdeep312 said:
Using this rootable kernel E6683 dual
http://forum.xda-developers.com/xperia-z5/development/32-2-0-224-ftf-rootable-kernel-t3391071
Click to expand...
Click to collapse
Sent from my E6653 using XDA-Developers mobile app
Thanks TS. Works pretty well so far for me (.224), and indeed the phone feels faster and more reactive under heavy load (noticed it after I finished recording a 10m 1080p60fps video). Good job
I'm using the newest flash kernel and elementalex kernel manager. Its been happening more and more. This time its stuck at max frequency on the big cluster. Everything else I can change like normal. What is causing this? I'm about to lose my mind with this crap. Its happened in several roms too. Right now I'm on screwd android nougat.
Woodrow256 said:
I'm using the newest flash kernel and elementalex kernel manager. Its been happening more and more. This time its stuck at max frequency on the big cluster. Everything else I can change like normal. What is causing this? I'm about to lose my mind with this crap. Its happened in several roms too. Right now I'm on screwd android nougat.
Click to expand...
Click to collapse
Do you have Facebook or Facebook Messenger installed? The latter app especially has been known to cause Max frequency problems for some people.
I do have those apps. But this is when im first setting up a new rom so they are not installed yet. It is also stuck overclocked when it happens. It finally let me change it this time. I have no clue as to why it does eventually let me but not at first. It didn't used to do this on previous version of flash kernel. I also tried changing it with another kernel app and it let me, no problem. Its something about exkm.
Woodrow256 said:
I do have those apps. But this is when im first setting up a new rom so they are not installed yet. It is also stuck overclocked when it happens. It finally let me change it this time. I have no clue as to why it does eventually let me but not at first. It didn't used to do this on previous version of flash kernel. I also tried changing it with another kernel app and it let me, no problem. Its something about exkm.
Click to expand...
Click to collapse
After rebooting or flashing files, the phone runs warm which means you cannot tweak CPU functions due to thermal throttling. The phone throttles when hot (worse if you live in a warm environment) or have low battery. That's a side effect of the Snapdragon 810.
If these issues persist half an hour or more after boot, then there is an app keeping your CPUs clocked high, like mentioned before.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
After rebooting or flashing files, the phone runs warm which means you cannot tweak CPU functions due to thermal throttling. The phone throttles when hot (worse if you live in a warm environment) or have low battery. That's a side effect of the Snapdragon 810.
If these issues persist half an hour or more after boot, then there is an app keeping your CPUs clocked high, like mentioned before.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
That cant be it. I can close exkm and open other cpu tuner app and immediately change the max frequency.
Woodrow256 said:
That cant be it. I can close exkm and open other cpu tuner app and immediately change the max frequency.
Click to expand...
Click to collapse
Keep it simple then. Uninstall then install EXKM from the Play Store and reboot. Open the app after two minutes then grant root access and modify kernel settings. Big cluster may still be offline due to rebooting.
Alternatively, clear data for EXKM and reboot then wait until it's been granted root permissions to modify kernel settings.
Sent from my Nexus 5X using Tapatalk
Woodrow256 said:
That cant be it. I can close exkm and open other cpu tuner app and immediately change the max frequency.
Click to expand...
Click to collapse
For solving your issue, use Kernel Adiutor, go into thermal on the side menu, and disable throttling. - this worked for me
Secondly, I do not recommend Screw'd, it left me well screwed.
- Home screen locking up, only being functional after rebooting
- VERY bad CPU over heating - I'm taking about 180°F - 82°C -while running social media and scrolling. And actually having to physically put the phone on ice to cool it down while I pulled files when I switched off of the ROM
- Random systemui crashes, kind of like CM all over again
I don't know if you get these issues, but I would recommend using a different ROM from my experience.
TL;DR : Screw'd causes CPU over heating and frequency troubles, also use Kernel Adiutor in thermal section to "unlock" or make it easier to tweak frequencies. Good luck!
TnT_ said:
For solving your issue, use Kernel Adiutor, go into thermal on the side menu, and disable throttling. - this worked for me
Secondly, I do not recommend Screw'd, it left me well screwed.
- Home screen locking up, only being functional after rebooting
- VERY bad CPU over heating - I'm taking about 180°F - 82°C -while running social media and scrolling. And actually having to physically put the phone on ice to cool it down while I pulled files when I switched off of the ROM
- Random systemui crashes, kind of like CM all over again
I don't know if you get these issues, but I would recommend using a different ROM from my experience.
TL;DR : Screw'd causes CPU over heating and frequency troubles, also use Kernel Adiutor in thermal section to "unlock" or make it easier to tweak frequencies. Good luck!
Click to expand...
Click to collapse
Wow, i cant believe screwd gives you such problems. Its has been my favorite nougat rom since last months beta. My phone never overheats. Ive only felt it get warm to the touch a few times since i got it last march. As far as throttling goes, if it does i never notice so it must not be too bad.