Related
I have made a lot of searches and read a lot about battery calibration... and of course i know what the hell is kernel panic, its definition and its symptoms.
However I still have some confusions and I hope some of you may be able to solve them
Maybe some of them are noobie questions but I honestly sorry for that also this may help others who has these confusions too
My situation:
The system stats are shown in my signature.
on 5/9 I have flashed franco.Kernel v19.4 bfs and then started a lot of OC tests,
finally I was stable on stress test (SetCPU) 729mhz for 2 hours non-stop,
and also I used the phone stably for over 24 hours without reboot.
However I faced a problem which is related to Darktremor scripts.
I used 2 weeks to solve it and finally it is gone now.
I started battery calibration which is the final process before I use my phone normally in my daily lives.
But in these two days, my kernel panics after ~4 hours of usage of 729mhz max CPU frequency.
without the need of advice, surely i have downclocked to 710mhz max and its all good. but however i am super curious about why 729 becomes from stable to unstable before and after.
1) Does battery stats related to kernel panics in ANY extent? if yes, how?
Ignore all questions under 1 if the answer is No.
1.1) Does wiping battery stats before flashing a kernel helps you OC higher?
1.2) Does wiping battery stats before flashing a ROM helps you OC higher?
1.3) Does wiping battery stats (for calibration purposes) has possibilities to produce kernel panics?
2) Why is there a sudden drop of battery level (~4-5%) after kernel panics?
3) Is there any other possible causes of kernel panics BESIDES overclocking too high?
3.1) *2sd scripts?
3.2) ext4 barrier = 0?
3.3) inputting EXT4 data writeback?
(tune2fs -o journal_data_writeback /dev/block/mmcblk0p2)
4) Is SetCPU the problem?
Some says "dont use SetCPU when you can overclock using CM7 settings."
Is that true?
5) BESIDES the max speed, does it also depends on Governors?
Ignore powersave governor or others which forces the clock to the minimum frequencies.
So, is there any difference between setting the same maximum speed, different governors?
(for example) Would smartass gives a panic at 729mhz but ondemand doesnt?
6) Does the "change of frequencies" gives easier kernel panics?
Situation A: 729min, 729 max
Situation B: 480min, 729max
In situation B, the system makes the frequencies change due to load, means it may switch from 480 -> 600 -> 729 -> 710 -> 691 -> 480 etc.
so does this "change of frequencies" makes the kernel loads more and finally gets it to panic?
Thanks for your time reading and answering my questions!
Please just quote one of them if you would just like to answer one of the above
Thank you very much!
1) no.
2) It happens when u remove the battery and put it back.
3) There are some strange reports of kernel panic at 600Mhz which are weird. Sometimes Roms/kernel play a part(unknown).
4) it is because you can overclock in Cm7 settings menu, so no need to install another app such as SetCpu
5) Maybe, a governor who stays more on the highest frequencies i think are easy to panic because hardware can't handle it.
6) for me, i would say situation A would be easier to kernel panic, as it is constantly on the highest frequency and stressing your cpu too much that it can't handle it.
Since you get stable at 729mhz for 2h and panicked when 4h of use, that means the cpu can't handle 729mhz for above 4h.
@terratrix
thanks for your reply!! at least im not using my stupidity to wipe battery stats and trying to avoid kernel panics, lol.
@info update and conclusion after 1 more day of testing
And there, after some readings on the forum and the experiences myself, i think i have found the critical point already - QUESTION NO.5
Conclusion : kernel panics are related to governors, at least, our new amazing profiled one - SmartassV2!!
On the thread of Franco's .35 v1 kernel, there are some users reporting the panic issues faced with ONLY SmartassV2.
And me myself, has joined the party as well
Smartass(v1) has been my best bud all the time at 729mhz or even higher for more than 6 months. And when I left it and went to choose his next generation, my phone got a generation gap with Mr.V2, lol.
On my phone: (Franco.kernel 19.4bfs and no any reflash or stuffs between testings)
SmartassV2 ---
very unstable panics AND random shutdowns at random times
729mhz - sometimes 2 hours, sometimes 4 hours
710mhz - yeah I justnow kernel paniced with this also, you know how long after boot? 30minutes!!!
Why 30minutes? I suspect that it.is related to franco's network speed hack. I'm on EDGE data plan and because of Franco, I can enable HSDPA with 4x more speed.
On 710mhz, my phone was stable for over 8 hours with EDGE on (I intended to save battery), but after a reboot (manual one for some other purposes) I started to use (the hacked) HSDPA. After 30 minutes, panic. I remembered when I was at 729 on smartassv2 I panicked after 3 hours and at that time I was using HSDPA too.
Smartass (v1) ---
Well now I'm on smartass v1 at 729mhz stably typing this message. Funny huh...?
Results:
Franco's network speed hack
OR
3G network/HSDPA network
OR
Even just because of specific phone hardwares
IS NOT COMPATIBLE WITH THE ALMIGHTY SMARTASS-V2 GOVERNOR AND WOULD RESULT IN KERNEL PANICS AT THE FREQUENCIES WHERE THE PHONE CAN BE STABLE WITH OTHER COMMON GOVERNORS.
If I am wrong or you can confirm this by testing yourself, please let me know!!! thanks and hope I have provided some useful information
Goodnight and I'm going to continue working with my old friend smartass-v1 despite v2 has better profiling tweaks, lol
Sent from my LG-P500 using XDA Premium App
Dude, as i had mentioned earlier in franco's thread, that it had to do with the governors... cause i usually try and find out the cause of the issue myself before posting a bug..
SO all i tried were playing around with the performance settings... and i start off with changing the governors... the best targeted experimental ones are MINMAX (my personal fav), SMARTASS, SMOOTHASS (now removed but one AWESOME governor), and INTERACTIVE-X (rewritten by franco i guess).... About the frequencies... from what i have observed so far apart from reading stuffs is that, at 729 Mhz our optimus DOES pretty much stay stable even in the ****TIEST devices.. LOL i can say that cause we indians get the crappiest hardware of all... the point is... if you got a kernel panic at 729, it is most likely that you would get it again at 600 Mhz too cause its not overclock related..!!!
Bottom-line: Avoid SmartassV2 unless your phone is made of the finest hardware i.e. you can easily overclock it to 806 Mhz (ive seen some users using it at this frequency without any issues at all .. :O ) Use Smartass older or Minmax instead...!! And avoid overclocking above 729..!!!
P.s.: mine works fine even at 768 BTW....
We have to wait for Franco's next release for more smartass2 updates
Sent from my LG-P500
SmartassV2 is kind of strange, at least in my phone. I notice my battery draining faster while I use it, and it's probably because it stays in the max frequency longer for some reason, despite screen off. I use NoFrills for my CPU setting and it has the ability to view stats, and when I'm using V2 it stays longer at the max than at the min (65 vs 35%). The opposite is true for Smartass v1, which to me makes more sense because my phone stays at standby more often than being used.
As comparison data, my phone with smartass v1 can typically be OCed up to 787 MHz. 748 MHz on v2 is stable, but I haven't extensively tested higher freqs.
I have a Indian phone , smartass v2 oc to 768 stable xD
Sent from my LG-P500
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Haven't used powersave mode at all yet, It's possible that profile has bugs on this phone.
I have my screen off profile set to 800 mhz and conservative and have had 0 issues so far.
as far as I'm aware powersave doesn't let it out of the minimum frequency (could be wrong). Use the conservative governor instead.
Don't use power save. I have done a lot of testing with this.
Here is the lowest that you can go.
Range: 200-500mhz
Mode: ondemand or conservative
If you go less than 500mhz or put it on powersaver, then it won't wake up from locking the phone.
Thanks
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
geauxlsu83 said:
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
Click to expand...
Click to collapse
I noticed that setting it to 200-500mhz increased my battery life by about 15-20%, but I did notice a significant performance drop. 200-800mhz is much less noticeable performance wise, but I didn't check to see what kind of battery life I got on that setting.
As for widgets...I'm not sure on that one either.
geauxlsu83 said:
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Click to expand...
Click to collapse
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
thanks
yeah im actually flashing your kernel as we speak i looked under a battery thread and they said your kernel is good for battery conservation thanks for your help
actually i flashed it from heimdall and it says it is kernel version is 2.6.35.7 is this yours?
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Entropy512 said:
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Click to expand...
Click to collapse
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Well said.
Entropy512 said:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
Click to expand...
Click to collapse
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
vladm7 said:
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
Click to expand...
Click to collapse
This is why I also have my screen-off limited to 500. Once in a while, the phone needs to do a little extra work, and it's better to ramp to 500, get stuff done, then go back to deepsleep. As I said min=max=200 SHOULD be OK, but personally, I wouldn't recommend it.
I would love if SetCPU allowed for different governor tuning depending on profile. e.g. make up/down threshold more battery-biased with screen-off than screen-on. (Slower polling rate, higher up/down thresholds.)
SetCPU root access problem
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
IshouldntbeHere said:
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Click to expand...
Click to collapse
Pretty sure it's your phone cause mine OC's to 1.6 with no problem.
BigBopper said:
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
Click to expand...
Click to collapse
Have you tried updating the su binary in Superuser? (Even if you have the app updated, the app itself needs to update the binary.)
Beyond that I have no ideas.
Entropy512 said:
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
Click to expand...
Click to collapse
Ahh, that was my problem. I was using powersave. Do you (or anyone else) see there being a benefit to having a screen off profile?
In theory, a screen-off profile shouldn't help - in reality, it's a line of defense for cases where something goes nuts in the background.
Hello there, I'm here to ask how some people overclock their xperia x10 so high example to 1190 mhz, my one is instantly booting when i switch to that frequency, how do they do it ? Im on jb rom by scritch 007 and jb ferakernel . Any advices ?
loockzye said:
Hello there, I'm here to ask how some people overclock their xperia x10 so high example to 1190 mhz, my one is instantly booting when i switch to that frequency, how do they do it ? Im on jb rom by scritch 007 and jb ferakernel . Any advices ?
Click to expand...
Click to collapse
To start with, no two XPERIA X10i are the same when it comes to the silicon in them.
The odd one or two may be able to sustain 1128MHz for benchmarking, but highly unlikely to be able to sustain that frequency for an extended time with a 'standard' load of user installed apps.
The XPERIA X10i is spec'd to be run stable and conservatively at 998MHz and there was no consideration for any frequency changes above that when designed.
However that does not stop most of us attempting to find the limits.
I tend to favour 1113MHz for my max daily frequency using SmartAssv2 governor, others may select something different.
I use SetCPU to change CPU frequencies, others prefer AnTuTu cpu master or some other overclocking application.
I use Link2SD on a secondary partition with a 32GB SanDisk UHS-I SDcard which gets away from the slow read/write of internal data storage.
build.prop 'tweaking' for optimisation goes a long way too.
The smart money is not overclocking, but on how low you can maintain the CPU (and thus battery life) when the screen is off and still be able to come out of deep sleep without 'hanging' the phone.
I have a screen-off CPU profile clocked at 576MHz-192MHz using SmartAssv2 to do that (work in progress).
Limiting applications that wake your phone when the screen is off it also a bonus.
CPU Governors and I/O scheduler information is a good start to understand what the CPU is attempting to do with different settings.
I have installed and run scritch007 CM10 JB ROM v5.0 (think it was at the time) with Amin Kernel and I seem to remember 1190Mhz was the raged edge of stability with AnTuTu v3 on my phone, so it doesn't surprise me a phone may not be able to clock at that speed using a CM10 JB ROM. See my AnTuTu v3 benchmark below used SmartAssV2 and noop I/O scheduler.
One should consider with the JB ROMs, the phone is doing a lot more (albeit a lot smarter) with the same amount of HW resources and even if you set the clock at 1190MHz and benchmark it, even before installing your own apps, there is still a lot of processes all completing for resources.
To get a better idea of the abilities of your phone, you may want to installed generic GB 2.3.3 and root it with an Overclocked Kernel to see if high clock rates of 1190MHz+ can be maintained without crashing the phone (WLOD - White light of death).
I can set 1128MHz on my phone without crashing it, but it always crashes on AnTuTu benchmark test at that frequency which is only about bragging rights at the end of the day anyway. I can't do anything constructive at these clock rates.
Installing JB ROMs and Kernels under rapid development with their own quirks on an X10i is probably not the most ideal why to gauge the stability of your phone when overclocked.
At the end of the day, it's more likely just luck of the draw if an XPERIA X10i can maintain 1190MHz+ clock frequencies and I'd say that 1190MHz+ is the exception and not the rule.
Dr Goodvibes said:
To start with, no two XPERIA X10i are the same when it comes to the silicon in them.
The odd one or two may be able to sustain 1128MHz for benchmarking, but highly unlikely to be able to sustain that frequency for an extended time with a 'standard' load of user installed apps.
The XPERIA X10i is spec'd to be run stable and conservatively at 998MHz and there was no consideration for any frequency changes above that when designed.
However that does not stop most of us attempting to find the limits.
I tend to favour 1113MHz for my max daily frequency using SmartAssv2 governor, others may select something different.
I use SetCPU to change CPU frequencies, others prefer AnTuTu cpu master or some other overclocking application.
I use Link2SD on a secondary partition with a 32GB SanDisk UHS-I SDcard which gets away from the slow read/write of internal data storage.
build.prop 'tweaking' for optimisation goes a long way too.
The smart money is not overclocking, but on how low you can maintain the CPU (and thus battery life) when the screen is off and still be able to come out of deep sleep without 'hanging' the phone.
I have a screen-off CPU profile clocked at 576MHz-192MHz using SmartAssv2 to do that (work in progress).
Limiting applications that wake your phone when the screen is off it also a bonus.
CPU Governors and I/O scheduler information is a good start to understand what the CPU is attempting to do with different settings.
I have installed and run scritch007 CM10 JB ROM v5.0 (think it was at the time) with Amin Kernel and I seem to remember 1190Mhz was the raged edge of stability with AnTuTu v3 on my phone, so it doesn't surprise me a phone may not be able to clock at that speed using a CM10 JB ROM. See my AnTuTu v3 benchmark below used SmartAssV2 and noop I/O scheduler.
One should consider with the JB ROMs, the phone is doing a lot more (albeit a lot smarter) with the same amount of HW resources and even if you set the clock at 1190MHz and benchmark it, even before installing your own apps, there is still a lot of processes all completing for resources.
To get a better idea of the abilities of your phone, you may want to installed generic GB 2.3.3 and root it with an Overclocked Kernel to see if high clock rates of 1190MHz+ can be maintained without crashing the phone (WLOD - White light of death).
I can set 1128MHz on my phone without crashing it, but it always crashes on AnTuTu benchmark test at that frequency which is only about bragging rights at the end of the day anyway. I can't do anything constructive at these clock rates.
Installing JB ROMs and Kernels under rapid development with their own quirks on an X10i is probably not the most ideal why to gauge the stability of your phone when overclocked.
At the end of the day, it's more likely just luck of the draw if an XPERIA X10i can maintain 1190MHz+ clock frequencies and I'd say that 1190MHz+ is the exception and not the rule.
Click to expand...
Click to collapse
Thanks for your answer.
Hello. I have been running CyanogenMod 10.1-10.2 since I got my device back in July, everything has been working great. Bugfixes have been lovely and all that good stuff; however one thing continues to annoy me. I cannot underclock my device properly. Let's say I go into the normal CyanogenMod Performance settings. Then I put my CPU to something like 1024MHz, then I see how the results went over with PerfMon from Chainfire, it will underclock only on Core 0, the rest of the cores still run up to the standard limit, 1890MHz. The only way I can somewhat successfully underclock is by setting my CPU to 594MHz or lower, at which point it will disable all cores except Core 0.
This has been annoying me for a while, I am running the standard CyanogenMod kernel, and recently I tried the Elite Kernel. The only thing the Elite Kernel did was remove the ability to disable the other 3 cores when below 594MHz. (And add the ability to go up to 2.2GHz, but who wants to overclock the Galaxy S4 yet?)
It may be worth mentioning if I try to tweak individual core settings with Tasker, on Core 0 it will let me set a CPU frequency, then if I go in and try to set something on Core 1, it won't have any of the default values for anything, and I enter them manually, then it will give me some errors about not finding the governor I said and stuff like that.
Anyone who knows any way to fix this (Custom kernels, different ROMs (Only for curiosity, I would stick to CyanogenMod anyway), etc) would be greatly appreciated.
Anyone who questions my motives for underclocking, question away. I don't like how my battery life is next to junk when I'm not even touching my phone all day, and the GS4 hardly needs the CPU it has, so I plan to use Tasker to set up a bunch of power saving mechanisms.
I suppose I do have one other question. Will underclocking even benefit me if I can't modify the voltage settings? Are they modified automatically when you're running at lower frequencies? (You would hope so, considering it's kinda a mobile device with a power source that isn't infinite). But if it won't help me without lowering my voltage (and if it isn't modified automatically) is there any good way to do that with a Tasker based setup, so it can be switched instantly whenever I do something? For example, launching a music player. All 4 cores shoot up to 1890MHz (I know they eventually settle down to lower frequencies, but for example's sake), I would rather have it so when I launched the app, Tasker would come in and set my CPU to ~800MHz with only a single core. Everything might slightly lag, but it would work and I would potentially get better battery life while listening to music.
Also, I never tested this on TouchWiz, as I didn't stay on it for more than 30 minutes after I got my device.
I am running the latest CyanogenMod nightly in case it matters (20131002, and it'll be 20131003 tomorrow unless it breaks something)
Thanks in advance to anyone who can possibly help with this. I'm sorry if the post is unorganized, but I hope it's understandable.
[bump]
Forgive me for my ignorance since I'm on ME7 and unable to flash CM10.x yet, but couldn't you just try different governors instead? On my old phone I was using lulzactive and it gave me great battery life, and you could tweak all the values any way you want for more performance or battery life.
I also remember when I experimented with undervolting and much to my dismay it turns out it made my battery life WORSE because of all the error correcting it was doing.
I get at least a days worth of moderate/heavy use on mine and with how fast it charges I don't really care about battery life but I'm curious how much actual gain you'll get for your efforts
It's now in its final version but I'll still update as I see needed
[Donate here]
* IMPORTANT *
Read ENTIRE OP for compatibility and install instructions as I will not respond to a question that is answered in the op
OP has been updated with the new instructions
OK Here's the New CTTMod for marshmallow ROMs Working to improve performance eliminate lag along with lowering the core temps allowing your phone to continue to run smoothly after long or heavy periods of use. Now with faster charging times
Any developers feel free to use the mod in your ROMs just please give proper credit thanks
Please Read The Entire OP before installing
I Am Not Responsible For Anything You Do To Your Device.
How to determine if your G3 set up is compatible with this mod and INSTRUCTIONS and DOWNLOADS are in the 2ND post
Everyone I need your feedback with certain details which I list below in the 2nd post to be able to create an accurate list of which devices are compatible and which devices I'm currently working to make a compatible version for..
Remember always make a full nandroid backup before doing anything
I've decided to go into a little more detail in this thread to give people a better understanding of how and what this mod does, mostly by detailing how the thermal controls work and what I changed within in them. I also went into detail about governors because they go hand in hand controlling the CPU's frequency in different ways. which I'll go into more detail below in hopes of helping you understand when and how the CTTMod will improve your performance
______________________________________________
Governors and thermal control How & why they effect your phones performance
First here are a quick summaries of what a governor does and what the thermals do then I'll get into more detail below
Note I tried to write and explain everything as simple as possible in the hopes of helping even the newcomers to android to be able to understand and gain little knowledge and insight.
Also I hope this helps everyone also understand why and when this mod starts doing it's thing and why sometimes it might feel like it's not working and other times feel like it's working great.
There are a lot of variables and different criteria that has to be met for each process to be enacted.
The kernels governor manages the CPU's frequency mainly by the amount of load the cpu is under and other preset values.
Thermal control which determines the frequency by the temperature of the CPU and is told by preset values set in thermal files when it (cpu),should lower its frequency depending on temperature
Both play big rolls in how well your phone performs but in opposite ways the governor basically start out by trying to keep your phone running smoothly by increasing the clock speed to match the load on the cpu, whereas thermal control does the opposite where it kicks in after the cpu reaches a preset limit and starts lowering the clock speed in an attempt the cool down the CPU to keep the phone running smoothly
Now the governor bases what the clock speed is set to and determines the point the kernel will increase the CPU's frequency by the load value set in the governor which is preset by the OEM or dev. With a rooted phones most of these values can be changed. The load values based on numbers with 0 being the phone just sitting idle not under any load so the governor will have the cpu frequency set to the preset minimum allowed frequency set by the kernel. And as the work load increases the governor raises the frequency in steps also preset by the governor until the CPU reaches a frequency that handles the increase in work load and continues to raise the clockspeed as the load increases. Now once the CPU's load reaches the preset target load value it will be running at the maximum allowed frequency set in the kernel. Different governors have a different numbers of load and other settings some can be changed and some can't depending on the governor and what features were added by the builder
For example the conservative governor sets it's target load values high usually around 95 and a step value of say 14 (step value being the amount of frequencies it will go thru to reach the maximum set frequency. Which helps improve battery life but you sacrafice performance. As say the interactive governor with the target load value set at 70 (Target load value being the highest amount of work load on the CPU before bumping it up to the maximum allowed CPU frequency set in RJ kernel and a step value of 7 will have better performance that the conservative .
All but one governor (performance) which is set to run at the maximum CPU frequency all the time) has parameters that can be tuned to your liking with one of the many CPU/kernel control apps out. But not all kernels and the governors come with the same settings. The builder/OEM/dev. of the kernel can pick and choose what features and governors to put in the kernel and also what settings are allowed to be changed. Also not all particular governors come with the same allowed settings. One developer might only put in the interactive governor and only put a few settings that can be changed whereas a kernel from another developer will add in every setting there is for the interactive governor.
Here's a great page explaining just about everything you should know about governors it's a must read.
http://forum.xda-developers.com/gene...ors-o-t3048957
OK now thermal control works by throttling the CPU down to preset frequencies at preset temperatures and is also done in a preset # of steps. Thermals also monitor and play parts in controlling other components like the GPU, battery and a couple of other things.
First let me be clear about one thing
The CTTMod does not turn off thermal throttling. Now the trick of going into the hidden menu and turning thermal mitigation and thermal control on. That does turn off all thermal monitoring and control and I highly advise against ever doing it. You take a huge risk of frying your phone.
Now let me explain a little what gets changed by installing this mod, and how and when the thermal control do there thing.
What i did is changed the first 3 bump downs (steps). I did this raising the preset frequency in the phones thermal file that tells the CPU to slow it's clockspeed down when the cpu reaches a preset temperture. Now in reality the thermal just sits and monitors the temperature of different components. It doesn't affect the CPU at all until it reaches a preset temperature.
Now there are 6 steps 5 of which throttle your cpu down. The first one being you CPUs max frequency and as long as the cpus actual temperature is below the one predefined in the file the CPU is allowed to scale as high as it needs to in order to complete the task in an efficient and speedy manner. So until it reaches that temperature it's the kernels governor that is deciding what the CPUs frequency needs to be by the load that the CPU is under at any given time. Now each different governor has its own way of how and at what load points it'll tell the cpu it can scale up or down by the values set in parameter settings of the governor and also tells the CPU how many steps ( scaling frequencies) to go thru and how long to stay at each step before moving on. So in short but not the entire story is that the governor controls when to speed up the cpu by the load it's under and the thermal controls tell the cpu when to step down to certain frequencies that corresponds with temperature points that are set in the thermal file in an effort to keep the temperature of the CPU down to try and keep the phone running smoothly and within an efficient operating temperature
Now what I have done is raised the first 3 points at which the thermal tells the cpu to be at. But left the last two and the shut off values at their stock values so it doesn't let the phone get hot enough to burn up. That's why you might notice with this mod after a long period of time using your phone under heavy load and the cpu reaches that forth step down temp. that when you'll notice a dramatic slow down. The thermals also control a what i would consider a fail safe temp setting that will automatically shut your phone down. Which is set at 120°c and won't let you turn your phone back on until the temp lowers to 115°c which I also left at the factory settings.
Now hopefully after reading this you have an understanding of what the mod does and how it affects the performance of your phone. And how the settings in whichever governor you are using also affects the performance of the phone. So if your governor is not tuned to your usage. You will not see a difference after flashing the CTTMod.
Now I'll explain what changes I made to the first bump down to. I changed the first frequency bump down to 2.26 and raised the tempurture it has to reach to 70°c Stock was set to drop the cpu down to 1.5 GHz at 60°c
Now at stock they scale your clockspeed by almost half of the processors actual top speed of 2.45 ghz which is why the g3 has such bad lag when after a short time of moderate to heavy use. So as a result of increasing the first set frequency to 2.26 GHz and raising the temperature limit will allow you turn operate you phone for a much longer period of time before you start to notice the phone slowing down .
Also in the LP versions I was able to tweak some of the battery values to keep the phones temperature down which I had discovered by accident and for most people they say there battery now stays cooler compared to stock. And tweaked the GPU. The second version that is now up implements the cpu throttling and battery improvements and I hope to hand the GPU tweaked and working in the next version.
I Hope this has helped you have a little more insight on what this mod does and how you devices improvement might not be noticeable compared to someone else who show a great improvement in performance. It all depends things we do to our phones to customize them .ie different ROMs kernels, settings and mods we add to them.
Let me know how the mod works for you and what carrier version and ROM and kernel you are on and governor being used
Thanks Rob
Also with the vs985 MM firmware the thermal file in system/etc is thermal-engine-8974.conf
So check to see what thermal file/s you have. If they're different send me a link to your thermal files and I'll take a look and see what I can do modifying them
Instructions and Downloads for G3 Marshmallow
Instructions
#1 - DO A FULL BACK UP BEFORE YOU DO ANYTHING
And since I only have access to the vs985's 46a stock firmware (MM) That is the only variant I can actually test myself . So far haven't found a device that's not compatible
Any g3 variants that have different files the just the one I name below I will need you guys to post me the information and file/s that I have listed at the end of the instructions
First you have to determine if your phone and ROM are compatible.
Check your Roms thread op and see if it's already included in the ROM as many Roms have now included the CTTMod
So before anything, you'll have to see in you have the file named
thermal-engine-8974.conf.
To do so navigate to /system/etc and look to see if you have the file with the same name as I just stated above. If you see that you have only one thermal file and the names match,
Then follow the New Instructions- First still follow the instructions in op to see if your variant or ROM is compatible then proceed
1- reboot into recovery
2- flash mod
3- wipe the cache important no need to wipe dalvic, but you must wipe the cache for the mod to take into affect.
Then in your kernel control app. In thermal make sure it's set to core control.
Now this is optional but under cpu hotplug turn mp decision/intelliplug to off. With hotplug off it will throttle less or on to throttle faster but both ways it'll only throttle to 2.26ghz on the first bump down instead of 1.5 or 1.7. You can read more about mp decision and intelliplug and how they affect the mod HERE
If you decide to leave feedback, good or bad you must include the details about your phone I have listed here
starting with your G3 model # The type of ROM (ie stock, aosp or cm, whether you on a stock or custom kernel, and the governor you are using.. Also please leave any results you have based on one of the two ways below on how to evaluate whether or not the mod works as it's intended too and just how much of an improvement you notice
First and easiest way is your actual user experience. Use your phone like you would on any given day and try to remember things you been doing on you phone that caused your phone to feel slow , laggy , not as responsive, or made your phone get hot to the touch. . Then install the mod and try to repeat what you did before and feel the difference.
If you'd like to take it a step further for some real evidence on if it's working or not. You can do some real testing by
First you'll need an app like CPUtemp to see the CPU frequency, load it's under and the temp of the cpu in real time .
With your phone fully charged use it moderately like going on Facebook and making a call have 2 or 3 apps going at once and doing something on the phone. For around thirty minutes. You want to put the cpu under at least 50%: load logging the temp and frequency every couple minutes for about twenty to thirty minutes. Then do the same again but this time you'll want to put the cpu under a heavy load 100% really work it.(running alot of apps, playing a resource hogging game, running a benchmark or stability test I think you get the idea)
Log the temps and CPU frequency again every couple minutes for 20 to 30 minutes or as long as it takes to reach full load
Then repeat the process after you install the mod.
You should perform the tests once before you install the mod logging the results and then try to duplicate what you did the first time after you install the mod and log the results. It's important to do some testing before you install the mod to give a baseline to compare with. Then you will be able to see what did or didn't gain any improvement compared to stock. And if an something got worse I'll know where to look to fix it.
Thank you as the more people willing to do the testing and share the results will help me greatly on improving, perfecting and to trying to make it compatible with as many variants and ROMs possible.
DOWNLOADS (Alternate download links bottom of this post)
G3-CTTMOD-MM_final:
Yes this is the same mod I had posted in post 52 I've just now made it official after having tested it for a while now.
As stated before I will still be updating as I see fit
CTTMod-MM+FC-v2
Change log: increased the charging voltage by 50mv on the second and third bump downs. Left the first and forth and fifth stock. Goal is to to speed up charging times. I only increased it slightly to start so there might not be much of a noticeable difference. Will increase more once some testing has been done on this one. Please leave feedback thanks
CTTMod-fc-V-2.1 - changes - increased the second and third charge by another 50mv and still left first, forth and fifth stock the same as v-2
CTTMod-MM+gpu-v3-beta
Change log: added slight increase in GPU
CTTMod+fc+gpu-V.3.1- change log- goal better GPU performance along with the faster charging from v2.1
Back to stock zip
( I haven't personally tested this but I don't see any reason why it wouldn't work)
Test versions
I'm going to work on posting all my test versions here as I have many improvements I'm trying to make but can only do and test one at a time to make sure the changes are doing what I want them to do. So please if you decide try a test version please message me with your findings and how you tested
Remember any of the mods posted here are experimental and have not been tested as with anything you flash this at completely your own risk
Here's the first test version for better gaming
CTTMod-fc-gpu-v4
Please lane feedback
Download link doesn't work for me....
D855
RUNNING: N&N 1.9 STOCK MM
+1
cultofluna said:
Download link doesn't work for me....
D855
RUNNING: N&N 1.9 STOCK MM
Click to expand...
Click to collapse
Requires login
cultofluna said:
Download link doesn't work for me....
D855
RUNNING: N&N 1.9 STOCK MM
Click to expand...
Click to collapse
Had to reload should will be up shortly
Can't download because AFH require sign in.
{
"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 LG-F400S using Tapatalk
Robshr said:
Had to reload should will be up shortly
Click to expand...
Click to collapse
Thanks for the MOD,but why we have to log in to download?.....
D855
RUNNING: N&N 1.9 STOCK MM
cultofluna said:
Thanks for the MOD,but why we have to log in to download?.....
D855
RUNNING: N&N 1.9 STOCK MM
Click to expand...
Click to collapse
You don't have to register to download
Here's am alternate download link to the new G3 thermal mod for MM- https://mega.nz/#!q1B3wYxS!jfyhwQnXa8c0rYAA2JcDVpiqeEDc4IlbvQ6DfSvZyIs
Robshr said:
I don't know maybe it's something new with android file host just click on the bars in the upper right corner and register is free and they Smit send you a ton of junk it's what all the dev use
Click to expand...
Click to collapse
No thanks.......
D855
RUNNING: N&N 1.9 STOCK MM
cultofluna said:
No thanks.......
D855
RUNNING: N&N 1.9 STOCK MM
Click to expand...
Click to collapse
I just posted an alternate download link in the op
chuyennho184 said:
Can't download because AFH require sign in.
Sent from my LG-F400S using Tapatalk
Click to expand...
Click to collapse
Alternate download link is up
Robshr said:
I just posted an alternate download link in the op
Click to expand...
Click to collapse
Thanks Dev, download it....
D855
RUNNING: N&N 1.9 STOCK MM
Robshr said:
Alternate download link is up
Click to expand...
Click to collapse
check your file/folder permission though, this is what I got even I am logged in
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.
PS: Also, the link should be www.androidfilehost.com/?fid=xxxxxxxxx (17 digits ) , but yours is androidfilehost.com/user/?w=settings-dev-files&flid=49846
Robshr said:
Instructions
First thing since I only have access to the vs985's 46a stock firmware (MM) and won't flash an asop MM ROM until I have this just have I want it and it all backed up to my computer.
So before anything go to /system/etc and find any files with thermal or thermald in it. Hope you only have 1. Named thermal-engine-8974.conf if that's the only file you have you can just flash the zip wipe the both caches reboot and give it about a day to settle in before starting to test or give any opinions
Now if you have different files then the one I name above send all the details about what's running on your phone and upload a copy of whatever files you have and send the link along with you phone info
Link to downloads-
https://www.androidfilehost.com/?fid=24415232478675537
Alienate download link: https://mega.nz/#!q1B3wYxS!jfyhwQnXa8c0rYAA2JcDVpiqeEDc4IlbvQ6DfSvZyIs
Please remember this is a WIP so please be patient thanks
If interested here are my interactive governor settings see attachment
Click to expand...
Click to collapse
abced123 said:
check your file/folder permission though, this is what I got even I am logged in
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.
PS: Also, the link should be www.androidfilehost.com/?fid=xxxxxxxxx (17 digits ) , but yours is androidfilehost.com/user/?w=settings-dev-files&flid=49846
Click to expand...
Click to collapse
I got it fixed I had copied the link to the folder with contained the file and not the link to the file itself. Anyway it's all good now
I'm on fulmics 3.5 with solid kernel (d850). I don't see any thermal file in my system\etc folder. Can I still flash the mod?
sociojeje said:
I'm on fulmics 3.5 with solid kernel (d850). I don't see any thermal file in my system\etc folder. Can I still flash the mod?
Click to expand...
Click to collapse
EDIT SORRY MISREAD you're right in the /system/etc/ there and definitely a thermal file in there
near the bottom
File is. .config or you might been on a romv with a thermal. XML file or similar
Dump question but you're using a root file browser
Second version on the way
I started on the second version last night in hopes of keeping the phone cooler at high loads compared to stock ) like I did with previous versions). So after my initial real feel testing for the first few hours after flashing the the new mod I was happy to feel that the phone felt cooler and didn't lag at all and just felt very smooth even after am hour of moderate to heavy use. I was happy enough to say f-it and go against my own rule of testing and just waited a few hours to let the phone get back to normal temps and than I started an all it assault on the CPU for about thirty minutes straight I kept the CPU under 100% load or as close as possible for the entire 30 minutes. Well the results were better than I hoped for. The highest temp the CPU reached was right around 80° c and was there for only a few seconds and throttled down the CPU just that time and cooled down enough to throttle back up in less than a minute. Now compared to stock. And doing pretty much the same tests for the same amount of time stock went as high as 100°c and throttled down to 1.2ghz within the first ten minutes then down to 1.19 after 15 minutes and stayed between 996 and 1.2 the rest of the time occasionally dropping lower. By a little over halfway testing it stock without the mod the phone was at a crawl and by the end I thought for sure it was going to shut down.
Now with the mod installed it only throttled down once maybe twice but never lagged and ran smooth as silk the whole time. So I think I'm happy enough to try and release it tomorrow as version 2 experimental just in case I find a bug or something in the next few days if i don't then I'll post it in the op. continue testing it and start on the next version which hopefully I can make it as good as possible and achieving what I wanted to do with this mod, but there's always room for improvement. Well below I posted a screenshot of cputemp which was taken at around the 28 minute mark into the test and it shows the load the CPU is under, the frequency it's running at, and its temperature . now it doesn't really refect the average temp or average clockspeed which was closer to 70°c and 2.26 ghz because it bounces up and down quickly. That's why you need to check the reading alot because of how fast and how much all the different readings change every few seconds. So to get a more accurate average of the readings you need to log them as often as possible with whatever app you're using to see the temps and frequency.. Like in the picture I caught it at a much lower frequency than the average which was around the 2.26 mark and spending almost the same amount of time at the top speed of 2.45 ghz . one other bonus I noticed is how low the battery temp stayed. I don't think it ever went above 36°c and remember I had the on charge the entire time.
And these results should improve over the next few days as the mod has a chance to settle in. Hopefully users will get similar results and post them to confirm my results.
I'll perform the tests again in a few days and post them hopefully they improve
Robshr said:
I started on the second version last night in hopes of keeping the phone cooler at high loads compared to stock ) like I did with previous versions). So after my initial real feel testing for the first few hours after flashing the the new mod I was happy to feel that the phone felt cooler and didn't lag at all and just felt very smooth even after am hour of moderate to heavy use. I was happy enough to say f-it and go against my own rule of testing and just waited a few hours to let the phone get back to normal temps and than I started an all it assault on the CPU for about thirty minutes straight I kept the CPU under 100% load or as close as possible for the entire 30 minutes. Well the results were better than I hoped for. The highest temp the CPU reached was right around 80° c and was there for only a few seconds and throttled down the CPU just that time and cooled down enough to throttle back up in less than a minute. Now compared to stock. And doing pretty much the same tests for the same amount of time stock went as high as 100°c and throttled down to 1.2ghz within the first ten minutes then down to 1.19 after 15 minutes and stayed between 996 and 1.2 the rest of the time occasionally dropping lower. By a little over halfway testing it stock without the mod the phone was at a crawl and by the end I thought for sure it was going to shut down.
Now with the mod installed it only throttled down once maybe twice but never lagged and ran smooth as silk the whole time. So I think I'm happy enough to try and release it tomorrow as version 2 experimental just in case I find a bug or something in the next few days if i don't then I'll post it in the op. continue testing it and start on the next version which hopefully I can make it as good as possible and achieving what I wanted to do with this mod, but there's always room for improvement. Well below I posted a screenshot of cputemp which was taken at around the 28 minute mark into the test and it shows the load the CPU is under, the frequency it's running at, and its temperature . now it doesn't really refect the average temp or average clockspeed which was closer to 70°c and 2.26 ghz because it bounces up and down quickly. That's why you need to check the reading alot because of how fast and how much all the different readings change every few seconds. So to get a more accurate average of the readings you need to log them as often as possible with whatever app you're using to see the temps and frequency.. Like in the picture I caught it at a much lower frequency than the average which was around the 2.26 mark and spending almost the same amount of time at the top speed of 2.45 ghz . one other bonus I noticed is how low the battery temp stayed. I don't think it ever went above 36°c and remember I had the on charge the entire time.
And these results should improve over the next few days as the mod has a chance to settle in. Hopefully users will get similar results and post them to confirm my results.
I'll perform the tests again in a few days and post them hopefully they improve
Click to expand...
Click to collapse
Thank you for your amazing contribution for our G3 community.
All the download links are working fine
No more login prompt?
Uploading v2 now link will be posted later on in the op