Related
I have downloaded the kingklick kernel and there is OC'ing available. It is capable of being OC'ed around 1.1ghz or so. Now I purchased the SetCPU from the market and I was wondering what to do next? Im afraid to just try to fool around with some stuff and mess up my phone. Anyone able to help?
go to setCPU and and click the about tab (i think thats what its called) the dev put a nice info page together that describes the ropes.
Other than that, it is pretty basic (although full of awesomeness). Just set the governor (how the cpu scaling is performed) and set the min max.
But the info page should describe most. There is also information around somewhere that goes more in-depth I am sure
this page helped me
http://www.pokedev.com/setcpu/#7
also, if you search around for 'setcpu profiles' and such, you can see where folks have posted their configs. look around in the thread of your favorite ROM, chances are folks are playing with setcpu in there...look for a couple that sound like they have a clue and ask them if they use setcpu (i'm thinking a direct message, not a thread posting) if they'd send you a screenshot to help jump start your understanding of the app.
Seems like a lot of people are facing problem waking up the phone resulting in getting black screen and nothing else.
I faced the same problem too that is why I decided to create a new thread specifically on this.
Let's share what caused our phone to go into coma based on our observations so that in time, the root of the problem can be traced.
Based on my observation, when my phone is left idle for some time, say 1-2hrs, it tends to become sluggish and setcpu will stuck at max or min value (Yes! sluggish even when stuck at max value!). Given long enough idle time, it will fail to wake up (e.g. every morning when i wake up after 7-8hrs of idle time).
I was using OpenDesire v4.0.10 and just changed to v4.0.15 to see if it still exist. I have setcpu set on 1075max 245min (ondemand) and 245max 245min (ondemand) when screen off. Also, using task manager.
Please share your observations and phone settings (ROM, versions, setcpu, task manager and others)
have you tried removing setcpu?
cgrec92 said:
have you tried removing setcpu?
Click to expand...
Click to collapse
Nope, but in OpenDesire thread, people without setcpu experienced the same thing. Do you have such problem?
I noticed using setcpu does make the phone sluggish. when uninstalled problem was solved.
Installed undervolt & got better batt life.
Sent from my HTC Desire using XDA App
Perhaps, a more tailored topic title will help all readers understand what you're talking about.
However, HAVS kernels is the only common factor and SetCPU is not the cause.
And, my two cents, I don't think this issue deserves a dedicated thread since is specific to a single kernel flavor.
shai.bosse said:
I noticed using setcpu does make the phone sluggish. when uninstalled problem was solved.
Installed undervolt & got better batt life.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
what is this undervolt you talking about? mind elaborating a little?
@ngel said:
Perhaps, a more tailored topic title will help all readers understand what you're talking about.
However, HAVS kernels is the only common factor and SetCPU is not the cause.
And, my two cents, I don't think this issue deserves a dedicated thread since is specific to a single kernel flavor.
Click to expand...
Click to collapse
I created a specific thread on this topic because there are many people out there experiencing this bug and there is no dedicate thread to discuss it. I assume you are not facing this problem because otherwise you would understand the pain and frustration of encountering this problem repeatedly
webber2109 said:
what is this undervolt you talking about? mind elaborating a little?
Click to expand...
Click to collapse
Undervolt is a kernel mod that you install and it lowers the cpu drain by setting it to use lower volt values on each cpu freq. This cause it to stay cooler too.
Look for it in this forum. [Kernel] undervolt
Sent from my HTC Desire using XDA App
I am suffering from this once per day on Defrost and OD so I suspect its kernal related. I am running the default HAVS kernel at the stock 998 frequency. I uninstalled SetCPU yesterday and had a lock this morning ( Defrost 4.1 ). The notification LED was flashing orange. So SetCPU is not causeing the problem. I have swapped over to SVS so I will report back on how that goes.
webber2109 said:
Nope, but in OpenDesire thread, people without setcpu experienced the same thing. Do you have such problem?
Click to expand...
Click to collapse
I use OpenDesire 4.0.10, then 4.0.15, then 4.0.16, each release for at least 3 days, and not for once have I encountered such "black death"....no setCPU of course.
Care to elaborate what apps you have there ?
webber2109 said:
I created a specific thread on this topic because there are many people out there experiencing this bug and there is no dedicate thread to discuss it. I assume you are not facing this problem because otherwise you would understand the pain and frustration of encountering this problem repeatedly
Click to expand...
Click to collapse
That issue is relative to OpenDesire and DeFroST ROMs only, and when they use a particular kernel version (HAVS) on selected CPUs, so I continue to think that it'll be eventually sorted out by the respective developers and/or Kali- and the kernel team; those guys do monitor the ROMs threads so they're already aware of the issue.
And yes, I suffered the issue twice, as I wrote more times in the DeFroST thread. "Pain" (panic?) and "frustration" sound a bit strange to me, when dealing with overclocked, custom, highly tweaked cooked ROMs. If a reboot scares you, head for a stock HTC ROM and you'll be fine.
I was worried I was the only one who had this. Thread title isn't that helpful for people seeking advice on it though. Get this after every reboot for about a minute until everything is back to normal.
Had the sluggish issue when using YouTube after about 20/30 mins, other than that I've had no lags.
Using 4.0.16
Sent from my HTC Desire
Double post
I got this on a svs kernal, so its not just restricted to havs. I had 1300 svs installed. With setcpu. Done the same with 1267 svs.
I've also had this issue on SVS kernels, was also having a series of hard resets last night - have rolled back to an earlier version of my favourite ROM flavour for now.
Never experienced anything like that...Although there are times that my Desire's performance would remind me of the bad old Diamond days,where patience was a virtue(well,not a virtue,but a money saving method!throwing your phone to the wall with your full strength after it frustrates you with being slow is known to be a costly process! ).Seems to be some apps running in the background...Maybe if your phone recovers after it without a reboot you can check if any apps use a larger than normal amount of ram.Other than that...Well,god is almighty and people experiencing epiphanies are known to work wonders through the ages!
And something completely off-topic(sorry about that).When using an undervolted rom/kernel you are not able to overclock to values as high as when using a normal-volted(is the word right?I dunno...) rom/kernel,right?I mean,what would happen if someone tried to overclock to 1382MHz(I know,I like the limits) using an undervolted kernel?And finally,how does this all apply to the hardware?Does UV affect the CPU's health like overclocking or something like that?
Thanks a lot!
I've had it on OpenDesire 4.0.10 and 4.0.15 a few times. Stopped happening when I stopped using profiles and defaulted back to to 998/ondemand.
Will try running it on 998/interactive for a while and see what happens.
No lockups after SetCPU to ondemand. OD 4.0.15.
Sent from my HTC Desire using XDA App
Separate thread IS useful, otherwise replies get lost in ROM threads where the focus is not specifically on this problem.
I too had this issue three times. DeFroST on all occasions, versions 3.x iirc. Never tried the HAVS kernels, just plain default what is shipped with the ROM (SVS @ 12xx Mhz?). Also SetCPU'd it, have not yet bothered to try and turn that off yet. SetCPU keeps it at 995 Mhz max, interactive governor, while switching to powersave while asleep.
Issue happened twice while browsing (possibly with Flash ads on the page by accident) and the power state switching (i.e. turn the device off quickly while running for train, afterwards reading for 2 minutes again, etc). Third time it happened while tethering my internet connection to my laptop.
Hth
I had this problem few times a day when I upgraded OD to .10 and the new ADW on the same day.
Then I restore back the old OD with old ADW, then no problem.
Anyone have a good explanation of the governer scaling for newer selections (smartassV2,smartass,powersave,interactive) There was a prior post I had seen I think on the captivate forum that spelled it out to people who don't understand the linux commands
Also I apologize if this has already been asked and answered search revealed nothing for me
PS: Anyone have a radio firmware package that seems to pull better signal than others they've tried?
Weselers said:
Anyone have a good explanation of the governer scaling for newer selections (smartassV2,smartass,powersave,interactive) There was a prior post I had seen I think on the captivate forum that spelled it out to people who don't understand the linux commands
Also I apologize if this has already been asked and answered search revealed nothing for me
PS: Anyone have a radio firmware package that seems to pull better signal than others they've tried?
Click to expand...
Click to collapse
-the smartass governor is based on the interactive governor and tries to get the best performance while keeping power consumption in check.
-powersave governor always keeps the CPU at the minimum set frequency
Ok guys i have got permission to bring over lean kernel and offer support for it on xda. I will keep this post up todate with all the most recent kernel updates and news. All credit goes to imoseyon as the original op and rootzwiki for original posting. I am posting this with full permission and support from imoseyon
Mod Type:: Kernel
Difficulty:: Very Easy
Mod Status:: Stable
Apply In:: CWM Recovery
Requires Root:: Yes
Exp builds are also up and includes a bunch of Android/OMAP updates not in stable.
SOURCE:
ICS
JB
This is a minimalistic Galaxy Nexus kernel. My philosophy is to keep the kernel as lean and stable as possible, at the same time to keep the kernel as modern and close to latest mainstream linux as possible. You will see that my kernels will lack some of the bells and whistles from other kernels.
sorry host4droid is still down. Mirrors:
kk4.4 LK 9.0 beta (use at ur own risk)
JB4.3 [ stable builds | exp builds ] [ change log | exp changes ]
JB4.2:Stable
Stock JRN84D kernel
Terminal Emulator not finding scripts? Read this post.
CHANGE LOG JB 4.2
FEATURES
Patched to latest in Linux 3.0.x branch.
All unnecessary kernel components removed to make kernel lean and fast!
OC to 1.65ghz. Boot speed is maxed at 1.2ghz within kernel (in addition to ramdisk) for stability.
User voltage control
InteractiveX V2 (screen-off hotplug of cpu1) added. Select it using setcpu if you want to use it.
Ramdisk tweaks (sysctl, vm, filesystem speed, etc.)
SWAP & zram (next generation compcache) support. Run "zram enable" in terminal.
init.d support in ramdisk.
lk.conf for basic kernel configuration.
HotplugX governor (Hotplug optimized and modified for screen-off suspend).
wakelock tweaks for wlan and lte modem
lkflash - script to flash latest versions of leanKernel from Terminal (type "su" without quotes, hit enter, then type "lkflash" without quotes and then hit enter)
checkv - voltage checking script (for custom undervolting) - detailed at bottom of this post.
checkt - script that displays 1) your current temp, 2) # of times you were throttled due to temp "recently", 3) CPU trim type, and 4) CPU silicon type, etc.
Fast USB charge (by chad0982) and "ffc" toggle script by me. (Open terminal, and type "ffc" without quotes then enter)
ColorControl from both CM9 and Ezekeel (compatible with all ROMs). Helpful posts: 1and 2.
TempControl - sysfs interface to control the CPU temp threshold. Read these two posts: 1 and 2.
Variable GPU OC - sysfs interface to select GPU max speed between 307MHz (stock), 384MHz and 512Mhz. The changes take effect immediately. Check FAQ for more info and how to use it.
Custom SR Tuning - override kernel default minimum voltage for SR calibration.
SoundControl
Gamma Control
ROW scheduler v4
DIRECTIONS
Uh.... flash the zip in clockworkmod.
Thanks to forum member maddler for providing file hosting
FAQ
How do i change voltage? - Use the latest version of setcpu, leantweaks, cputuner, or your ROM's built-in tools.
Do i need to wipe dalvik/cache? - in general there's no need, but it doesn't hurt so if you have time go ahead. Posted Image I don't wipe.
Can we OC higher or add more frequency slots? - You can find the extra slots in my experimental versions.
Will this work on GSM gnexus as well? - It should. I don't have a GSM phone to test so let me know if it stops working.
What is interactiveX V2? Read this post and thttp://rootzwiki.com/topic/13092-kernel-leankernel-minimalistic-kernel-120-123111/page__view__findpost__p__342571
Are you getting Screen-Off/Sleep-Of Death (SOD), general instability, or unusual battery drain?
Before you post here (especially if you're running the experimental version), try the following steps in order:
0) dude, disable screen-off profiles if you're running interactiveX.
1) If you're running the experimental version, do you have 180mhz/230mhz and/or 1.42ghz slots enabled? If so disable them both!
2) If the above doesn't help, do you have custom undervolting enabled? If so disable it! (keep in mind that the kernel is already undervolted by default).
3) If the above doesn't help, are you using interactiveX or hotplug governors? If so change to interactive.
4) If the above doesn't help then you should not be running the experimental version. Install the stable version and try both interactiveX and interactive without custom undervolting.
If you're still getting SOD with stable/interactive, report it here.
What about call-recording? - First the app needs to support Galaxy Nexus. Find out if it does and then find out from the author of the app what kernel changes are required and let me know.
Should i set up screen-off profile? - ICS kernels have built-in screen-off profile for all governors at 700mhz. So you don't need it unless you want to set it lower than 700mhz. In general there isn't a whole lot to gain by setting it lower.
Hotplug vs interactiveX? - Read this post. HotplugX vs interactiveX
What is zram and why do i need it?
zram basically takes a portion of your RAM (10% using my script) and turns it into a compressed swap device. So in layman's terms you're extending the size of your memory (potentially from ~700mb to close to 1000mb depending on the compression ratio).
To answer the 2nd question, no you don't really need it but if used properly (using custom LK zram script) it could help you in two different ways:
1) Android OS is based on Linux OS and the OS will try to use a growing portion of your RAM for file and inode caches and if you keep your phone up without rebooting after a while you may notice things getting a little sluggish. That's because the OS is not doing a good job in dropping the caches and freeing up memory for the apps.
2) more RAM and tweaked minfree (also handled by custom LK script) could potentially allow your apps to stay in memory longer (this may or may not be desirable based on your preference of course).
In conclusion, I'd say if you're curious it doesn't hurt to try. To revert, just type "zram disable".
What's the low-down on the GPU OC?
My kernel's GPU is now set to stock 307Mhz by default. You can adjust that by using Variable GPU OC (see a separate FAQ entry below).
When you go from say 307 to 512Mhz, you will not experience near double performance increase. Due to the factors outside the GPU module (ie. memory bandwidth limitation), you can't truly OC the GPU. In fact, most people can't tell the difference between 307, 384 and 512. Nenamark2 will roughly give you the following scores: 307/25fps, 384/28fps, and 512/31fps.
Some of you have seen the note from Colin, the Google kernel engineer, not to OC the GPU because using the OV_UV voltage slot will drain the battery. My kernel uses the same voltage for both OV and OV_UV slots. So there's no danger of battery drain there.
Why are the IO benchmark test scores lower than another kernel?
Some of the kernels out there have fsync disabled to increase benchmark scores. I believe that is unsafe and could cause data corruption. I do have hooks in my kernel to disable it but I don't use it.
In real world there will not be any user perceivable difference whether you have fsync enabled or disabled.
Is there a way to tune hotplug via sysfs?
yes. Advanced users only!
My phone doesn't seem to be deep-sleeping, what gives?
(assuming you checked in the right place like cpuspy) In terms of deep-sleep, there's not a whole lot going on in the kernel. It works or it doesn't - and I can assure you that I test every release (well almost every release) for deep-sleep before I release.
19 out of 20 times it's either 1) some sort of background process that's preventing your phone from going into deepsleep, or 2) something's misconfigured in your ROM, or both. Also connecting to USB will prevent phone from going into deepsleep.
I'm having unusual battery drain - help!
First of all, our gnex has very poor battery life while in active use. It's downright horrible while screen is on - screen is definitely the main culprit and there's not a whole lot I can do about that.
Custom undervolting can help or can hurt. This is mainly due to SmartReflex (class1.5) which auto-calibrates the ideal voltages for you. In fact, with SR you don't really need to use the custom undervolting feature for frequencies other than the 2 lowest. It does a great job calibrating higher frequencies. I personally don't touch it.
The "notrim" versions are an exception because I had to disable SR1.5 for the trim override to work. There's no auto-calibration going on there. Feel free to mess with custom undervolting on the notrim versions.
Now, if you've already accepted the horrible battery life while screen is on, but have questions about battery drain while idle - read the next question.
I'm having unusual battery drain while screen is off, or phone is sleeping - help!
First, let's find out if you're phone is going into deep-sleep. Install CPUSpy, unplug phone, turn off screen, and leave the phone alone for 5-10min. Turn the screen back on, launch CPUSpy, and see if you see an active entry for Deep Sleep. If so congratulations - read on.
If you've determined that your phone is not entering deepsleep by using the above method, read my entry above that says "My phone doesn't seem to be deep-sleeping". I've heard that removing SDM.apk helps as well as rebooting the phone. Also try turning your bluetooth on and off, and launching camera app and closing it.
If you've determined that your phone is entering deepsleep fine but still feel like battery drains, read the next question.
I'm having unusual battery drain while phone is in deep-sleep - help!
First make sure you are absolutely positive that deep sleep is working (read the previous question).
While on my kernel *and* connected to Wifi, you shouldn't drain more than 1% battery per hour *average* while in deep sleep (based on 5-8 hour continuous deep sleep). With wifi turned-off, my guess is probably no more than 1-3% per hour, depending on signal strength.
tip 1: If above is not happening for you, first charge the phone all the way and reboot. Let things settle a bit - give it a day or so. If you're using Battery Monitor Widget (which is not accurate for gnex), things should eventually settle between -2mA and -60mA per sample.
tip 2: Install BetterBatteryStats and look at which wakelocks dominate. Google search for names of the wakelocks to see how you can fix them.
tip 3: http://checkthis.com/d87t
If nothing seems to help, you can try the "notrim" version, but stick to speeds between 350 and 1350 (don't use OC slots). The notrim version has SR1.5 disabled which could help for those of you with drain issues on my other kernels.
What is tempcontrol and how do I use it?
First, read these two posts: 1 and 2.
Although tempcontrol was designed to be used with the experimental notrim builds because the cpu gets hotter in notrim frequencies, you can actually use tempcontrol to throttle lower frequencies. I haven't tried myself, but theoretically you can set your top speed at say 1.2Ghz and use tempcontrol to throttle at say 60C (instead of the stock value of 63C) resulting in slightly cooler phone. Theoretically.
What is SmartReflex?
SmartReflex performs continuous dynamic voltage scaling around the nominal operating point voltage according to silicon characteristics and operating conditions.
My stable and experimental builds will have SR Class 1.5 enabled by default.
You can disable SR via sysfs
How do I use Variable GPU OC?
You can use Lean Tweaks by Jake, or use the built-in "oc" script. Both leantweaks and my oc script will create an init.d script so the setting sticks at boot. My "checkt" script will also show the current GPU max speed. Note that 512MHz will probably not work for everyone.
307Mhz (stock) is set default by the kernel.
Open Terminal, and type for stock speed of 307Mhz: oc gpu 0
for 384MHz: oc gpu 1
for 512Mhz: oc gpu 2
What are the available sysfs options?
Check this post (thx byrong)
Which governor should I use on JB?
As usual I'd recommend trying all the governors and see which one works best for you. Stock JB, however, is optimized for interactive. The OS will automatically modify various interactive governor parameters on the fly while you're using the phone as part of "project butter". Namely, the following parameters are constantly adjusted by the OS: boostpulse, timer_rate, min_sample_time, hispeed_freq, go_hispeed_load, and above_hispeed_delay.
I hope this helps people if there is any other information you might want added just ask and i will do my best to come up with a comprehensive guide.
Donate to your favorite charity, or donate to imoseyon.
Did you ask Imoseyon before you posted this?
Thanks for bringing the thread over to XDA. Hopefully you got the necessary permissions, for the sake a peaceful thread. Its good to have most developments of the GNEX here and I finger tip away.
Sent from my Galaxy Nexus using xda premium
I've heard a lot about this kernel!
yes this is with his permisson
ajf64 said:
No i didn't ask him but i did put all due credits in it and it is in every other gnex forum but the sprint one all brought over by other people so if he has a problem with this he can feel free to pm me and i will get it removed i just figured it give us some easier access to his great kernel. In no way am i claiming this to be my work all support should be directed at the original thread op. I was just trying to make access to his kernel a bit easier for all xda users
Click to expand...
Click to collapse
That's all hunky dory but just doing things without asking the developer is just not right. Regardless if he has an issue or not. Its like you make something you work diligently on and then somebody just posts it somewhere else.
I dunno maybe its just me but its just common courtesy.
Sent From My Toro+ via SkyBlue Tapatalk
Thanks op.
#inb4close
#ReOpened
Sent from my Galaxy Nexus using Tapatalk 2
all fixed
ajf64 said:
well then sorry for posting it will a mod please delete this thread before it becomes a flame pit
Click to expand...
Click to collapse
Doesnt need to be deleted.. if just ask him if its alright.. thats fine enough
ÜBER™ said:
Doesnt need to be deleted.. if just ask him if its alright.. thats fine enough
Click to expand...
Click to collapse
Why do you always ruin the flaming? With your...good nature...and your rap music.
Thanks for linking. You can still ask dev for permission but I get what you're trying to do. I prefer xda since this is where I have gotten help with every phone since my nexus 1.
Sent from my Galaxy Nexus using XDA Premium HD app
Well i have gotten permission to post this from imoseyon and to keep this thread updated on xda sprint forums for him so it looks like we are all set he got back to me alot faster then i thought he would so every thing should be all good guys
and yes jayare313 i am so used to finding every thing i need on xda some times it s a pain having to check 3 or 4 sites to see if any of your mods for your rom are updated
Sorry. 3 issues here:
1) I need to verify permission from the developer and he needs to verify that he is going to support it here. If someone downloads it, flashes it, and somethings wrong.......who is going to give answers and support it? We have an active community who can help, sure, but the developer has to actively support it here. If he were ready to give support here, he would have posted it here already. And even then it would have to go in general unless he started the thread.
2) There is no source provided in the OP. Kernels must be GPL compliant and listed in the OP.
3) If you did not create it, do not post it in the development section.
Alrighty. Everything should be good now. I'll be keeping an eye out.
OP will be updated soon, with source and I've spoken to the developer.
Thank you guys.
---Jay--- From the GNex
Well, I will say I like having this thread here. So thanks to the op.
Sent from my Galaxy Nexus using Tapatalk 2
I will be updating the thread when i get home today and be offering any support you guys may need for this kernel
MichaelMcEntire said:
Well, I will say I like having this thread here. So thanks to the op.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I totally agree. Thanks to OP for the thread and imoseyon for the kernel
Sent from my Galaxy Nexus using xda premium
Np guys any time and if there is any thing i can help with just ask i plan to provide full support for this kernel. Also if there are things you wish to have added feel free to post them as well i have permission to compile my own versions of lean kernel with cherry picked features from his repository and to add features to it. I look forward to your feedback.
is 4.2 jb cm10 compatible
twoeleven99 said:
is 4.2 jb cm10 compatible
Click to expand...
Click to collapse
Yes
Sent from my Galaxy Nexus using xda app-developers app
Thermals, Kernel Managers and their affect on short and long term battery life.
As requested, by fellow LePro 3 owners, I created this thread for a discussion on the benefits of thermal management, using manual thermal settings, and sharing flashable thermals and user settings. To be clear I am not yet an expert on this subject, so I am learning along with everyone else. But, why not share the experience?
Of course we want our phones to last, while also pushing them to their limits, but in a safe and efficient manner. Recently our developers have shared their ideas on thermal management, and they have been gracious enough to allow us access to their own settings, that can be used across multiple builds. See the link below to download the first set of flashable thermal management options.
Recently, some of us have encountered shutdown issues, with some roms having battery stats reporting issues, unexpected shutdowns, and unrelated unrelated lockscreen issues. We users have found that often these troubled builds can be fixed by flashing a fix. Such as the thermals from a previous or other builds that did not have the same issue. Fortunately, it appears that we can use alternate perf and thermal management files that have not only offered a quick fix for some of these current issues, but also offers a longterm solution for using old, new, and future roms builds...collectively. :good:
The plan is to make this discussion much more extensive and simple
So consider this initial post to be an ever changing rough draft.
The end goal is to make it much easier for people to access and share their thermal management files or settings in one easily found central location, and hopefully for everyone to share their suggestions along the way
Helpful to Gamers who want safe power and speed.
Helpful to Non-Gamer's who want simply want stable performance, long battery life
Help everyone by helping us learn to optimize our phones to last for the longterm.
For me, no more repeating the same stuff over and over on various Rom threads, or private messages. No more having trouble digging through threads to find a recommended thermal or setting. So please participate, we can keep the OP updated whenever anything new comes along. Should I get access to something new I will add it to the Megadrive and make a post
Inventory
So far we have the thermals from Lineage, AEX, Balkan, AICP, EUI and in my view one the best is the latest by Jabashque. The idea of this post is to share the thermal settings so that they can be used on whichever ROM you want to try out.
Finally, you do not necessarily need to use these thermals unless you have an issue with general usage, heat or battery life. However, you will immediately notice the benefits.
Edit ( Updated Info)
Regarding kernels: Personally, I use BlackScreen 6.3, it has a long list of governors and I like options.
Currently the best thermal option is the Jabashque edit ( Thermal Fix 7 ) Get it Here: https://forum.xda-developers.com/showpost.php?p=78717015&postcount=18
These thermals work!
Over the past 2 weeks, I have gone back and tried several old ROMs, and these thermal and profiles make those old Roms perform so much better! For example, the September 3rd JMXL version of DotOS.: Yes, Its outstanding with the Sergey thermal. BootLegger's is also much improved, and it was already pretty great as it was. The Miui ROMs, are significantly improved by far! etc.
Of course we have so many great Roms. Occasionally, we get a build that is experimental and it may have unexpected issues. We have seen over the past week that flashing an alternate thermal is a perfect way to save the installation without having to revert to an earlier build. I mentioned old Roms above, they also work on every single Pie Rom.
Here is My Mega Drive Link for all of Thermals that I have collected so far
https://mega.nz/#F!9EokAQTb!Au6cBnJaCJXZrUlaXSLjhg
Alternate Link with key
Link: https://mega.nz/#F!9EokAQTb
Key: Au6cBnJaCJXZrUlaXSLjhg
Jabasque's thermals are in the Jabashque folder. Version 1 and 2 :
Probably shouldn't result in any difference if not gaming.
"Most likely, it would only be noticeable if you're not throttled down to 1440/1900MHz and you're running something that's using 100% cpu" ( Jabashque)
What to use
If you are wanting long battery life and low temperatures use Sergey's thermal or JaBashque version 1
If you want stock EUI faster throttling but slightly higher temps use the ShivateJappedi EUI thermal.
If you want to leave your cores unchanged from the default setting with higher temp throttling, more full power access and yet still safe while use JaBashque 6 Its a rework of the EUI 30s thermals designed to work better on modern Pie Roms : See more information here: https://review.lineageos.org/c/LineageOS/android_device_leeco_zl1/+/238809
Soon, I will create a post in the reserved section below to deeply define the details and differences between these thermals. Because while they all have similarities, they are also very different from one another.
In addition, I plan to add various kernel manager settings for various uses : Gaming, Long Life etc.
Finally, even when moving to another Rom. kernel manager programs such as Ex Kernel Manager will allow you to import and use saved profiles. It seems that it is possible to save the best of each of these thermals by saving the profiles of each. We can share those settings! Then later you can manually choose within your kernel manager which settings you want to use by simply importing choosing a preferred profile.
I hope this clears up the confusion. As mentioned this is a work in progress that was requested by 3 people. This is just the beginning of this discussion that will help everyone understand how to use Kernel Managers and the add-on thermals patches. I need to do some further research to make it all worthwhile . For example, although I love the elementalX governor, I haven't researched it enough to explain why I think it's better. So I plan to find out specifically what it's actually doing vs what other governors do, and how does changing sample rates, and wake locks affect performance and battery life etc.
If there are any experts out there? Please chime in and contribute.
See Updated information from Jabashque, which explains the differences between patch 1 and patch 2
https://forum.xda-developers.com/showpost.php?p=78670166&postcount=2
Installation
Dirty flash the patch that you want to use..thats it.
If you want to try a different patch, dirty flash the Rom, reflash Magisk and dirty flash the patch
You can manually adjust settings by going to /vendor/etc/thermal-engine.conf
Update from JaBashque Edit April 21 2019: ( I use ThermalFix7, its my personal favorite/ it is the best and the safest period.)
@tsongming
Hey, after seeing your thread about thermals, I felt I should write an explanation about how my v1 and v2 differ from stock EUI thermals that you could add to that forum post, since the one you have on there was me describing the difference between v1 and v2, not stock EUI: "JaBashque"
There are two different set of sensors that the original config monitors for the CPU:
the CPU temp sensors (tsens_tz_sensor{4,6,9,11}) and xo_therm_buf. The CPU temp sensors measure the temps of the cores themselves. xo_therm_buf measures what seems to be some sort of overall temperature, though I'm not sure what in particular. However, xo_therm_buf does correlate more directly with how hot your phone feels.
Original:
thermal-engine rapidly throttles your CPU down to 902MHz on the little cores and 825MHz on the big cores when any one of the cores hits 95C, and stops only when the hottest core drops back to 65C. When xo_therm_buf gets to 43C, thermal-engine slowly throttles all your cores to 902MHZ little and 825MHz big until xo_therm_buf drops back to 40C.
Patchset 1:
thermal-engine rapidly throttles your CPU down to 902MHz on the little cores and 825MHz on the big cores when any one of the cores hits 85C, and stops only when the hottest core drops back to 65C. When xo_therm_buf gets to 37C, thermal-engine throttles all your cores to 1440MHZ little and 1900MHz big until xo_therm_buf drops back to 34C. When xo_therm_buf gets to 43C, thermal-engine throttles all your cores to 1132MHZ little and 1363MHz big until xo_therm_buf drops back to 40C. When xo_therm_buf gets to 50C, thermal-engine throttles all your cores to 979MHZ little and 1132MHz big until xo_therm_buf drops back to 43C.
Patchset 2:
thermal-engine throttles your CPU down to 1516MHz on the little cores and 2054MHz on the big cores when any one of the cores hits 95C, and stops only when the hottest core drops back to 65C.
This change was made because I realized that the previous version still had a situation where the CPU performance can tank unpredictably. xo_therm_buf-related CPU throttling is same as Patchset 1.
Thanks to JaBashque for sharing his work! Patch-set 2 is my personal preference. Although the Sergey Perf + Combo is also very good.
@tsongming
Thank you very much for listen us and always give your help.
Rigth now I am on BaikalOS 28th December 2018, if I want to flash any Profile of those, what I should to do (Clean flash? This first, later that etc... and Wich of them I should ti flash for best battery, I do not play on movil)
I am very curious for test this...
I have x722, I do not play. I am now on aex 5.7 oreo. The most depends on the battery, so which zip to flash ? This is a great topic.
kukuteku said:
@tsongming
Thank you very much for listen us and always give your help.
Rigth now I am on BaikalOS 28th December 2018, if I want to flash any Profile of those, what I should to do (Clean flash? This first, later that etc... and Wich of them I should ti flash for best battery, I do not play on movil)
I am very curious for test this...
Click to expand...
Click to collapse
You can dirty flash these thermals.
Personally I like Sergey and Jabashque version 2 the best so far on Pie roms.
The Shivate patch works really well on Marshmallow, Nougat and Oreo.
The Sergey patch works really well on Oreo and Pie, I haven't tried it on Nougat Roms yet.
You can manually adjust settings by going to /vendor/etc/thermal-engine.conf and In this same folder ( vendor/etc) you can also make audio changes, and I am not talking about policies and Tasha.xml files, although you would make changes to those files too, if wanted. This will be something that we can discuss in more detail soon.
gsiwy said:
I have x722, I do not play. I am now on aex 5.7 oreo. The most depends on the battery, so which zip to flash ? This is a great topic.
Click to expand...
Click to collapse
Either the Sergey or the JaBashque 2 with be perfect, depending on what you want.
Use Sergey if your goal is battery saving.
Use JaBashque 2 if you want better gaming performance.
@tsongming thank you for this useful thread. I just have one question. I noticed that sergey's thermal file you uploaded comes also with perf so do you know is it maybe EUI perf and if not is it possible to upload just sergey's thermal without perf? Thanks.
I'm using aex 6.2 and i play a lot of games, but i looking for something that gives the power to run the games and after that (of course after some time without using the cellphone to cooldown) use the phone without worry of him overheat with simple use like 39 or 37 ºC. Do you have something like that?
I have a x722
MnMchill said:
@tsongming thank you for this useful thread. I just have one question. I noticed that sergey's thermal file you uploaded comes also with perf so do you know is it maybe EUI perf and if not is it possible to upload just sergey's thermal without perf? Thanks.
Click to expand...
Click to collapse
Sure, I can extract the perf, I will do that and add it to a separate folder so that there are two options.
Edit: Here is the Sergey thermal only
I removed the perf and added the additional key edit options from the Jabashque patch. So this a combo patch.
Use at your own risk
However, I have tested this and it works fine. I wanted to give the caveat that I am a Noob at this! But its okay. FYI: all I did was remove the perf, so now the perf will come from the rom and I added the Moshe key feature, which some Roms such as AICP includes anyway.
https://mega.nz/#F!ZVpXBQjC!PpXn1ZtLEHJb72Gbw7nWqg
Heitor Lima said:
I'm using aex 6.2 and i play a lot of games, but i looking for something that gives the power to run the games and after that (of course after some time without using the cellphone to cooldown) use the phone without worry of him overheat with simple use like 39 or 37 ºC. Do you have something like that?
I have a x722
Click to expand...
Click to collapse
Use the Jabashque 2
See updated in depth info from JaBashque : here: https://forum.xda-developers.com/showpost.php?p=78670166&postcount=2
So, thank you for your work!!One question,i am at the last AICP Pie,do you believe is better to flash one of these or stay with the settings of AICP?
Thanks in advance!
Don't work
I used to play pubg and the big stay on 1,4 ghz and little on 1,0 ghz
tsongming said:
Sure, I can extract the perf, I will do that and add it to a separate folder so that there are two options.
Edit: Here is the Sergey thermal only
I removed the perf and added the additional key edit options from the Jabashque patch. So this a combo patch.
Use at your own risk
However, I have tested this and it works fine. I wanted to give the caveat that I am a Noob at this! But its okay. FYI: all I did was remove the perf, so now the perf will come from the rom and I added the Moshe key feature, which some Roms such as AICP includes anyway.
https://mega.nz/#F!ZVpXBQjC!PpXn1ZtLEHJb72Gbw7nWqg
Click to expand...
Click to collapse
Works good, thanks.
geo307cc said:
So, thank you for your work!!One question,i am at the last AICP Pie,do you believe is better to flash one of these or stay with the settings of AICP?
Thanks in advance!
Click to expand...
Click to collapse
If you are not having any issues, then don't install any of these.
However, if you want to try it, keep a record of your existing performance, battery life, heat levels for battery and CPU (when idle) and compare that against using these thermals.
If you flash one of these thermals and don't like it. You can quickly return to your previous settings by dirty flashing your rom, or by restoring the system part of a nandroid backup.
Heitor Lima said:
I used to play pubg and the big stay on 1,4 ghz and little on 1,0 ghz
Click to expand...
Click to collapse
So which one of the 5 thermals did you try? Some of them include perf
Understand that you still have to setup your kernel manager. If you are wanting to use it for Gaming use the JaBashque version 2 to and leave the cores on the highest setting.
Yes, it works. It works for me a and a lot of other people on Telegram
If you want low temperatures and long battery life underclock the cores at idle my battery hovers around 85 F and the CPU are around 100-105F
Just so you know you can access your thermal.conf file and edit it manually to increase your thermal limit in /vendor/etc/thermal-engine.conf
Next, save a copy of your existing current setup as a profile, so you can easy switch from one to another with ease and easily compare it to the changes of using an alternative file. You can tweak it to the settings that you are wanting...Just keep safety in mind or you could burn up your CPU.
UpDate!
@jabashque has spent time recently improving his thermals further, and released several new versions .
The latest and greatest is now version 6!
Get it here: https://mega.nz/#!pFoSRaQA!R068WV-YltbQAFzuc3aH72z_OPyrN2uBjgsux2h0dNY
If you like it, please thank him!
Anyone who is using the last build of Jabashque 6 . It has a small error with he tthermal.
Flash this zip file from my Mega drive.
https://mega.nz/#!UZwhAQwY!GDUYQX2Ewcj92jjhs2t-oYnVcUKSbu9WfaOyAJjaKzs
The file adds a GPU setting to the Thermal
Repair by Jabashque: https://mega.nz/#!UZwhAQwY!GDUYQX2Ewcj92jjhs2t-oYnVcUKSbu9WfaOyAJjaKzs
Reference : https://review.lineageos.org/c/LineageOS/android_device_leeco_zl1/+/239612
I want to install Bootleggers os 8.1 on x722 and I have a question: after installing romu and gapps and initial configuration I can flash BS5.1-r3 AND thermal.zip a magisk mantle? will thermal.zip not interfere with BS? Thank you.
gsiwy said:
I want to install Bootleggers os 8.1 on x722 and I have a question: after installing romu and gapps and initial configuration I can flash BS5.1-r3 AND thermal.zip a magisk mantle? will thermal.zip not interfere with BS? Thank you.
Click to expand...
Click to collapse
Sorry I haven't been on XDA much recently, and never received the notification.
If you use Bootleggers, the stock kernel is fine. But blackScreen 6.3 will work fine and it gives you more options. You flash the thermal at anytime. I recommend the Thermal-fix7 which is Jabashque 6 that I edited to fix a typo. No there is no conflict