This is a direct port of my kernel on the international I9300 Galaxy S3 and sidekick to the international N7100/5 Note 2 kernels.
Recap of features:
CPU overclocking up to 1.8GHz and undervolting from 600mV to 1400mV.
GPU overclocking and undervolting.
GPU scaling reworked.
Screen sharpness and colour modifications.
Extended Pegasusq and improved Performance governors.
Removed Touch Booster and replaced with custom Flexrate mechanic.
Improved scheduler power management for improved idle residencies on auxiliary CPUs.
USB charging rate limit increased to 900mA.
Application for control of various settings.
This is supposed to be merely a proxy thread. Please refer to the N7100/5 thread for full changelogs, explanations, bug-reports and other issues. Kernel for specific device versions will be posted here.
This kernel is for the North American Verizon variant SCH-I605. Versions for other variants are found in their respective forums.
You obviously need to be unlocked with the "Suck it Verizon" bootloader/IROM unlock method before flashing this. I will not be responsible if you break your device by screwing up anything related to that.
flashing now!
Freaking awesome. Thank you for posting this.
Any known bugs/issues we should be aware of?
DaRkL3AD3R said:
Freaking awesome. Thank you for posting this.
Any known bugs/issues we should be aware of?
Click to expand...
Click to collapse
You let me know if there's something wrong. Now before things go down the same way as the other US variants, I implore everybody please read in the international N2 thread linked above for information about the kernel and the newest additions or if there's something wrong, it will always be more up to date than the proxy threads.
This kernel is absolutely insane! Wow!!
STWEAKS PROFILES! and proper bootloop fix.
Alright! now that Perseus Kernel .28 is out we have a new added feature that lets us implement override profiles!
What does this mean?
Well now this UNCHECK SET ON BOOT zip will actually just update your current default.profile and uncheck the set on boot options.
Which makes it the best fix for a bootloop, because you can then go back in to your old settings that failed and modify them.
I also am going to be generating 5 profiles. (will edit this post)
Each more aggressive overclocking and undervolting.
For people who are unsure of how to do do this properly with Stweaks,
You can just flash any of my profiles.
I recommend you download them all start at 5 and flash, if you bootloop or crash move up a profile until your stable!
Profile 5G is the one I run everyday (and is the lowest values for voltages)
It also is 200-1800 mhz overclocked and gpu 160-640 mhz
My custom governor tweaks (I believe the cpu is too aggressive and also the cores dont respond as much as id like to see them responding, 1 core on idle, 4 cores when needed.)
Profile 5 is the one I run everyday (and is the lowest values for voltages)
It also is 200-1800 mhz overclocked and gpu 160-640 mhz
STOCK governor settings
Profile 4 is slightly less aggressive on the voltages
200-1800 mhz 160-640
Profile 3 is slightly less aggressive on the voltage curve
200-1800mhz 160-533
Profile 2 is slightly less aggressive on the voltage curve
200-1600mhz 160-533
Profile 1 is slightly less aggressive on the voltage curve
200-1600mhz 160-533
Profile 0 is the DEFAULT profile the kernel came with. (it just deletes your profile and rebuilds it so its safe for all versions inlcuding S3-i9000)
EDIT: I have also included a zip with just the governor tweaks, these will not alter your voltages on cpu/gpu and will not change your max cpu
custom governor tweaks detailed below:
here is my logic
defaults parameter mine
30000 sampling rate 20000
82 up threshold 90
5 down diff 10
40% thres for response 81
1200 freq for fast down 1600
95 up thres fast down 98
37 up step 18
6 splice amount 4
13 down diff 8
With the default settings when the load is measured if the cpu load is over 82% off current freq step it will scale up.
New logic added in perseus .27 now gives us 3 up steps instead of just a fixed one.
so your cpu will step up more aggressively based on how much above the threshold it is, not just if its over, this is
great.
Right now, if we are coming in with a
load of 83%-88% we increase freq by 300mHz
if we are 89-94% we increase freq by 400 mHz and
if we are 94-100% then we increase freq by 700 mHz.
This is too fast for me.
For a few reasons the main one being that the amount we jump has gone up because our max cpu is 1800 instead of 1600 (at 1600 the jump ups are 200,300,600mhz)
The logic I use on my N2 is as follows:
Load of 90-94 = 100 mhz jump
load of 95-98 = 200 mhz jump
load of 99-100 = 400 mhz jump
The responsiveness of the phone is not compromised at all, the cpu just steps up less and only when it has really high loads(keep in mind the load is calculated every 20000 microseconds or 50 times in one second.)
It still gets to 1800 and does many operations there, but it comes out of 1800 fast and when it jumps down it jumps down further.
The fastdown has been upped from 1200 to 1600 , meaning it now requires 98% or higher load to jump up when above 1600 mhz not 1200 mhz, I found that the CPU was always in 1800 or like way lower,
never in the 1700 - 1200 range as it used to need 95% load to be in that range.
The cores hotplug has been slightly changed to turn off cores quicker when not in use and takes more samples to turn them on so they only turn on if load exists for longer duration of time.
PLEASE NOTE
Flashing any of these zips OTHER THEN THE UNCHECK SET ON BOOT will REMOVE your STWEAKS settings and replace them with the profile. PLEASE back up your profile if you want to save it.
Where is it?
/data/.perseus/default.profile << back this guy up. rename to default.profile2 works. or copy to sdcard.
Due to the way that these changes are applied (at initial boot) it will take longer then usual before beginning to display the boot animation for the first boot after changing profile.
This also means that you cannot flash 2 of these files in one boot, for example profile 3 and the governor tweaks.
You would need to flash the governor tweaks or the profile first and then reboot, and then flash the other.
Yay
Sent from my unlocked beans rom Galaxy Note 2
Is there a stock kernel?
This is great...wow!!!! so this is fine to flash in twrp...it says cmw...thank you!!
rayhodge02 said:
This is great...wow!!!! so this is fine to flash in twrp...it says cmw...thank you!!
Click to expand...
Click to collapse
Flashed fine for me in twrp
Sent from my unlocked beans rom Galaxy Note 2
So many questions...umm so we can flash governor and a profile at the same time.? What is the tweaks file for?
nnnnr14 said:
Flashed fine for me in twrp
Sent from my unlocked beans rom Galaxy Note 2
Click to expand...
Click to collapse
thanx
Or would you flash the governor and the uncheck boot file then go back and flash a profile? What is the original setrtjng without a profile ?.....okay I think i got it. I just need to flash the kernel (the zip file) and start with profile 5. (Can I flash at the same time)
Then if there's problems I can flash the uncheck at boot file so it'll revert and I can make the changes? That about right.
Dear OP,
Thank you very much for bringing this to us. Is this kernel also compatible with CM10?
kwkw480 said:
Dear OP,
Thank you very much for bringing this to us. Is this kernel also compatible with CM10?
Click to expand...
Click to collapse
no I believe its for touchwiz only.
blackbass595 said:
Or would you flash the governor and the uncheck boot file then go back and flash a profile? What is the original setrtjng without a profile ?.....okay I think i got it. I just need to flash the kernel (the zip file) and start with profile 5. (Can I flash at the same time)
Then if there's problems I can flash the uncheck at boot file so it'll revert and I can make the changes? That about right.
Click to expand...
Click to collapse
You got it bro.
First kernel. Then 5. Have th others in hand. If 5 won't work for you you will be boot looped. The uncheck set on boot will save your ads then reboot. Then flash 4 etc until you are stable. Only one profile per boot flashing more just overrides your last change. The profile is applied at kernel boot
Sent from my SGH-I317 using xda app-developers app
gundal said:
You got it bro.
First kernel. Then 5. Have th others in hand. If 5 won't work for you you will be boot looped. The uncheck set on boot will save your ads then reboot. Then flash 4 etc until you are stable. Only one profile per boot flashing more just overrides your last change. The profile is applied at kernel boot
Sent from my SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Cool but can I do kernel and profile "x" at the same time?
And I hate to be "captain questions" here but what is the tweaks zip? Is that like an app it installs or a script or what?
I just flashed the kernel only, rebooted, opened up STweaks from app drawer, set min to 300mhz, set max OC to 1800mhz, set gpu to 640mhz, and left the other settings stock for the time being. I gained 2500 points running antutu benchmark. 17200 stock, 19600 with flux kernel. Seems rock solid so far...need a couple days to see how battery life is with that much OC, but its SMOOTH!
blackbass595 said:
Cool but can I do kernel and profile "x" at the same time?
Click to expand...
Click to collapse
Yup jut do kernel first. Then 5g which will do gov tweaks and cpu gpu oc uv to the most aggressive voltage curve. If it Boot loops just flash 4 and continue
Also the set on boot uncheck is only needed if you want to retain your profile that caused a boot loop so you can adjust it
Sent from my SGH-I317 using xda app-developers app
droidstyle said:
I just flashed the kernel only, rebooted, opened up STweaks from app drawer, set OC to 1800mhz, set gpu to 640mhz, and left the other settings stock for the time being. I gained 2500 points running antutu benchmark. 17200 stock, 19600 with flux kernel.
Click to expand...
Click to collapse
What's flux? Or did you mean lux?
Sent from my unlocked, and overclocked Galaxy Note 2 running bean's rom
Related
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.
I'm running Olympus Titan HD 3.0 (says Olympus Trinity XE in os) with Chad's Anthrax-CDMA-SENSE 2.6.38.6 rev 5 (not indicative of a problem with the brand new rev 5, same problem with the rev 4), and I have a few questions about the OC capabilities.
I want to get away from using software like setcpu to OC my device. I feel like it's less reliable/capable than doing it at a low level. Having recently discovered the init.post_boot.sh file while attempting to force cpu1 on. I believe I've succeeded in doing that, but I see a bunch of options for setting the CPU speed in a system file.
I changed the parameters that apparently control cpu0/cpu1's min/max frequency to 384000/1728000 384000/1404000 respectively. However, after setting the permissions rw-r--r-- as instructed in the guide I was reading and rebooting, my max OC is now 1512 MHz (as reported by CPU master). I tried reflashing my anthrax kernel (which supports much higher frequencies), but still the 1512 MHz cap persists. There's no way (as far as I can tell) to verify what CPU1 is running at, but I can see that CPU0 is running at 1512 by using system monitor and CPU Master.
I'm afraid I've damaged my init.post_boot.sh file and bugged the phone or something, so attached is my init.post_boot.sh for review. Remove the .jps extention. I added it so the forum would let me upload it.
What can I do to get the anthrax kernel working properly again, and how do I use this init.post_boot.sh to do what I want it to do?
My next step after resolving this current problem involves manipulating the CPU governer using the .sh file. It looks like I can set different governers per core by stating
Code:
echo "IntelliAnthrax" >
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governer
echo "conservative" >
/sys/devices/system/cpu/cpu1/cpufreq/scaling_governer
Does it work in this way? Additionally, what does this mean for the top half of the file which specifically refers to the "ondemand" governer such as sampling rates?
Code:
ie, echo 50000 >
/sys/devices/system/cpu/cpu0/cpufreq/[color="red"]ondemand[/color]/sampling_rate
Would I just replace the ondemand part in all of those statements with the governer of choice, such as IntelliAnthrax? Would I also have to append a duplicate set of those parameters for the "conservative" governer as well if I chose to use different governers for each CPU?
Sorry so many questions, thank you for reading.
That new qualcomm base kernel is only capable of 1512 Max.
Sent from my HTC Evo 3D using xda premium
Just reflash your rom. I use system tuner pro to oc my phone and it allows undervolting.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
SketchyStunts said:
That new qualcomm base kernel is only capable of 1512 Max.
Sent from my HTC Evo 3D using xda premium
Click to expand...
Click to collapse
Really? http://forum.xda-developers.com/showthread.php?t=1318005
That thread details all the different OC levels of that kernel...
That is based on a bit old info. The new source has very few tweaks in it compared to the A series kernels. This "B" source is much closer to stock and doesnt yet allow any undervolting and also only goes up to 1.512 GHz.
You should try the 12/19 kernel as it has many more options and can get the higher speed
EniGmA1987 said:
That is based on a bit old info. The new source has very few tweaks in it compared to the A series kernels. This "B" source is much closer to stock and doesnt yet allow any undervolting and also only goes up to 1.512 GHz.
You should try the 12/19 kernel as it has many more options and can get the higher speed
Click to expand...
Click to collapse
You're just a wealth of helpful information today. Thank you, flashing older revision.
Sent from my PG86100 using XDA App
Okay, I looked at what ziggy and cron247 did over on XDA and tried to make it better.
This kernel is unsecured, meaning adb connects with root.
It OverClock's up to 1.836MHz.
It has the SmartAss V2 governor.
It uses my ramdisk, not the one you have. I cannot forsee this being an issue. If it becomes one, let me know.
Updates:
Version 1.1.3 changes the version of lagfree, the old one was having issues. Also removes forcing the second CPU to be online which was causing choppiness.
Version 1.1.2 adds increased read ahead, writeback tweaks, decreased dirty ratio settings, simple I/O scheduler, and the lagfree governor.
Version 1.0.5 adds mpdecision fix by Mr X, thank you whoever you are, if you removed mpdecision, put it back. Also added voltage control for you UV lovers.
The only control program I have tested to work is AnTuTu CPU Master (Free), I have had issues with SetCPU and a few others. This one does speed, governor, and voltage all very well.
Get it here: AnTuTu CPU Master (Free)
The following problems seem to be fixed at this point: governor and speed settings not sticking, smartass staying at top speed, random reboots or bootloops overnight.
READ THE INSTRUCTIONS, THIS IS A SINGLE FILE
To install this kernel:
Copy the file to the root of your SDcard.
Reboot into recovery (CWR or AmonRa).
Flash the file from the SDcard.
At the end of the flash the phone will reboot to fastboot.
Once fastboot loads, tap PWR to get to HBOOT.
HBOOT will find the update and ask you to install.
Tap Vol Up to begin the install.
When it finishes it will say tap PWR to reboot. Do it.
After the phone boots remove the PH98IMG.zip file from your SDcard.
Use AnTuTu CPU Master (Free) to set min/max/gov/voltage.
Enjoy!
Thanks to ziggy and con247 for getting us started and having stuff out there for me to get ideas from.
Download:
Link: dsb9938 Kernel 1.1.3
MD5: a2558e70f9af572f43e258c9aedb4b40
Source on GitHub.
My favorite Rezound kernel so far. Haven't had one crash, even at max OC. Thanks so much guys at BAMF!
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
dccoh said:
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
Click to expand...
Click to collapse
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Argent36 said:
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Click to expand...
Click to collapse
It's kernel related; I'm running rezrom and had the same exact issue with my alarm running this kernel.
Do you think ziggys is more stable?.. or do I just need to find the right overclock/underclock settings?
I seem to recall seeing them have that problem on ziggy's - but I never had that problem on earlier versions of dsb's - so maybe it's just something that is fixable for the next release
*wanders off to test it again*
This is no doubt me doing things wrong that led to this, but I downloaded the kernel through the phone browser, then flashed it from the download directory on the internal SD. When I flashed Incredikernel from there it copied the PH98 to the sdcard, but no dice on this kernel until I copied it to the sdcard then flashed it.
I probably should have copied it to the sd card myself first anyway, but I figured I would let you know!
Well this morning - my alarm clock went off - I was able to snooze it - and then a few minutes later the phone went in to boot loops - had been running stable all weekend - once I pulled the battery the phone booted back up just fine.
we'll see if it repeats this behavior tomorrow morning or not...
Call recording support in the kernel?
timp123 said:
Call recording support in the kernel?
Click to expand...
Click to collapse
Nope, only Ziggy's kernel currently supports this.
I only set one alarm at a time usually, but I have one set to go off every morning at 7:30 & it has worked perfectly everyday for a few weeks now.
~John
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
sandman_nyc_316 said:
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
Click to expand...
Click to collapse
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
hgoldner said:
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
Click to expand...
Click to collapse
Thanks! How's your battery life been with those settings?
sandman_nyc_316 said:
Thanks! How's your battery life been with those settings?
Click to expand...
Click to collapse
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
hgoldner said:
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
Click to expand...
Click to collapse
Appreciate it. Gonna see what happens. Will update with my results. Thanks again!
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
zetsumeikuro said:
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
Click to expand...
Click to collapse
Good question. I haven't had a single bootloop since flashing this kernel after coming from Ziggy's. Been running this 192min/183max and UV'd -75 across the board and running great.
Hopefully I don't jinx myself.
Guys with bootloops/lockups...are you running any profiles?
Make sure you do a dalvik cache wipe....
Ziggy's would always lock up on me (multiple times per day) so I gave up on it. The only problem I have with this on (and this was a problem with Ziggy's too) is the min jumping to max.
My frequencies bounce on this kernel. It spends about equal time between the highest setting, and lowest setting. It works great other than that. My question is this bad for my CPU? I get great battery life, and performance, just scared the bouncing could be bad for the processor. Any help would be great.....
Sent from my ADR6425LVW using Tapatalk
As the title says, would like to gather your ExTweaks settings. Always looking to improve battery/performance.
What is ExTweaks? From the makers of Voltage Control & SiyahKernel comes a highly configurable kernel tweaker. Requirements at the moment are SiyahKernel 2.6.13 or Entropy's DD 3/5/2012 +. It allows you to change such things as CPU Hotplug, GPU Steps/Voltages, Governor/Scheduler & much more.
Reference on what these settings mean: http://forum.xda-developers.com/showpost.php?p=23616564&postcount=6
Post in whatever format is easier for you. I am currently just listing them from start to end. Here are my current settings: (init.doh 0.4.6b & Siyah)
CPU Tab:
CPU Hotplug Default/50/90/80/100/200/600/1000/600000/AFTR+LPA/0/2/2/2
GPU Tab:
100/160/200/800/850/900/90/55/90/70
Screen Tab:
7/20/0/24
Misc Tab:
Unchecked/500/ondemand/sio/stock
I am aiming for battery with the above tweaks. So what are you currently "rocking"?
Just a heads up, Entropy's DD has been updated (3/5/2012 and Up) to run this also.
I don't have a screen tab on entropys kernel?
Sent from my AT&T cellular device.
jdbeitz said:
I don't have a screen tab on entropys kernel?
Sent from my AT&T cellular device.
Click to expand...
Click to collapse
Probably just something his kernel does not let you configure at the moment.
cwc3 said:
Probably just something his kernel does not let you configure at the moment.
Click to expand...
Click to collapse
That is correct. The idea of ExTweaks is to provide a "universal" configuration app.
Files in the kernel initramfs itself define nearly everything in the user interface - each tab, and each item within a tab.
I can tell you, for example, that the CPU screen has some significant differences from Siyah in my kernel, as I have decided not to include Tegrak Second Core support (It's redundant - the only thing that can't be done with the existing interface is to force the second core on, which is kind of pointless and bad for power management.)
The GPU interface should be nearly the same, but it might change in the future. I'm thinking of changing the down thresholds to "step down target" - Instead of defining it as the percentage load at the current frequency, define it as the target load at the next frequency step down.
I have at least one additional option in misc (Per-File fsync() control) that isn't in Siyah
Entropy512 said:
I have decided not to include Tegrak Second Core support (It's redundant - the only thing that can't be done with the existing interface is to force the second core on, which is kind of pointless and bad for power management.)
Click to expand...
Click to collapse
Been reading up on this myself: http://forum.xda-developers.com/showthread.php?t=1494653
What is your 2cents on hot-plugging?
cwc3 said:
Been reading up on this myself: http://forum.xda-developers.com/showthread.php?t=1494653
What is your 2cents on hot-plugging?
Click to expand...
Click to collapse
I didn't have time to revisit things, but I'm fairly certain, as I mentioned in that thread, that the test was flawed - Plugging in USB appears to fire enough interrupts to block AFTR and LPA from ever getting entered. As a result, one of the bigger power penalties invoked by activating the second core (blocking AFTR and LPA) has already been taken in his tests.
I set second core kickin threshold to 1000mhz and I undeclock to 1000mhz. I set gpu to 100/100/100 @800/800/800. Ondemand governor and noop scheduler.
How is this working for you? Notice ant difference in battery?
Sent from my SAMSUNG-SGH-I777 using XDA
ryude said:
I set second core kickin threshold to 1000mhz and I undeclock to 1000mhz. I set gpu to 100/100/100 @800/800/800. Ondemand governor and noop scheduler.
Click to expand...
Click to collapse
In my opinion, 800 is probably the best place for second core kickin - from 800 to 1000 is where voltage starts rising quite a bit, so you get more work per unit of energy when kicking in the second core at 800 than ramping up to 1000.
Thanks for making this. seems you beat me too it this time. lol.
Here are my settings
CPU
25/75/75/100/300/500/700/800000 AFTR+LPA
GPU
100/133/267/850/900/1000/50/50/75/50/1/1/1
MISC
Ondemand/cfq/Unchecked
Quadrant score of 3507
Could I also use Voltage control in tandem with this to tweak the voltages for each step? *Pretty sure it would cause conflicts/my phone to explode so I was curious...*
I didn't make it - Xan did. I just added support.
In any event, I'm really appreciative and glad to have a new venue to futz with on my phone. I can't wait till I learn what to tweak to get it running at optimal performance. *Not to say these phones are slouches at all though.*
Thanks for sharing your settings folks! Thanks for the information too Entropy.
As for your voltage control settings, ignore the GPU tab in that (He will be removing the GPU tab soon). Just use Voltage Control for changing you CPU voltages & min/max freq. Can also change your gov/scheduler, but ExTweaks does it too.
Please note whatever you save as a startup in voltage control will overwrite whatever conflicts there are with ExTweaks (Gov/Sched/Charging etc).
cwc3 said:
Thanks for sharing your settings folks! Thanks for the information too Entropy.
As for your voltage control settings, ignore the GPU tab in that (He will be removing the GPU tab soon). Just use Voltage Control for changing you CPU voltages & min/max freq. Can also change your gov/scheduler, but ExTweaks does it too.
Please note whatever you save as a startup in voltage control will overwrite whatever conflicts there are with ExTweaks (Gov/Sched/Charging etc).
Click to expand...
Click to collapse
Good to know thanks.
Alucardis666 said:
Thanks for making this. seems you beat me too it this time. lol.
Here are my settings
CPU
25/75/75/100/300/500/700/800000 AFTR+LPA
GPU
100/133/267/850/900/1000/50/50/75/50/1/1/1
MISC
Ondemand/cfq/Unchecked
Quadrant score of 3507
Could I also use Voltage control in tandem with this to tweak the voltages for each step? *Pretty sure it would cause conflicts/my phone to explode so I was curious...*
Click to expand...
Click to collapse
Thanks! I've followed suit as i was pretty intimidated by this. Let's see where this gets us...I'd love to see those cliffs in my battery graph flatten out a bit during screen on.
Sent from my SAMSUNG-SGH-I777 using XDA
Alucardis666 said:
Thanks for making this. seems you beat me too it this time. lol.
Here are my settings
CPU
25/75/75/100/300/500/700/800000 AFTR+LPA
GPU
100/133/267/850/900/1000/50/50/75/50/1/1/1
MISC
Ondemand/cfq/Unchecked
Quadrant score of 3507
Could I also use Voltage control in tandem with this to tweak the voltages for each step? *Pretty sure it would cause conflicts/my phone to explode so I was curious...*
Click to expand...
Click to collapse
Thanks man!! Gonna give these a shot.
Alucardis666 said:
Thanks for making this. seems you beat me too it this time. lol.
Here are my settings
CPU
25/75/75/100/300/500/700/800000 AFTR+LPA
GPU
100/133/267/850/900/1000/50/50/75/50/1/1/1
MISC
Ondemand/cfq/Unchecked
Quadrant score of 3507
Could I also use Voltage control in tandem with this to tweak the voltages for each step? *Pretty sure it would cause conflicts/my phone to explode so I was curious...*
Click to expand...
Click to collapse
I use setcpu from xda, it allows me to set screen off and charging profiles as well as voltages. It helps a lot
ryude said:
I use setcpu from xda, it allows me to set screen off and charging profiles as well as voltages. It helps a lot
Click to expand...
Click to collapse
I might give it a try again. The first time I used it, it seemed as if setcpu worsened the battery life.
Glad so many seem to like my config. still tweaking it, but lemme know how it goes for you guys.
Introducing the CTTMod
(cpu thermal throttling mod)
Most popular mod for the G3 & G4 now here for the Nexus
Remember always make a full nandroid backup before doing anything
I Am Not Responsible For Anything You Do To Your Device.
Please read entire op before asking questions
Rom & kernel developers please feel free to include in your work. Just please give proper credit thanks
Best used in conjunction with an over clocked kernel i.e. elemental x
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.
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.
What I've done is changed the first frequency bump down of two in the little cluster and left the 2nd stock
And in the big cluster I changed the first and second frequency bump downs of three and left the third stock
I've also increased the temperature at which it resets by 5° in versions 4x
For more info on how thermal works along with how the governor affects performance you can check out my op for the CTTMod for the G3 here
Instructions
1: Do a full nandroid back up
2: Back up your thermal file which is in system/etc ( thermal-engine.conf )
3: Flash mod and wipe cache
4: Reboot
5: In your kernel control app like kernel auditor set your thermal driver to msm thermal or temperature limit SoC temperture limit depending on what you kernel offers
The idea in the above is to make the kernel use the system's stock thermal driver which is the one I modded
I personally also check all cores on
Finally enjoy
One final note this mod and xceed kernel do not work together as xceed has built in it's own thermal control. If you would like to use this mod with xceed kernel you would have to ask the developer of xceed to make a compatible version. Sorry out of my hands.
Please hit the thanks Button and give it a 5 star rating :good:
Downloads
AFH downloads:
CTTMod v-3.1
CTTMod-v4
Change log: increased when the CPU resets after it has reached it's max temp, upped from 55°c to 60°c
CTTMod v-4.1
Changelog: increased the frequency of the first bump down in the big cluster
CTTMod v-5
Changelog: Increased the temperature by 2° at which the CPU and GPU bumps down there frequencies (Left the last bump 2 bump downs stock)
CTTMod v-5.1
Changelog: increased the temps of the CPU and GPU first 2 bump downs. CPU now starts throttling at 48°c and GPU starts at 44°c
CTTMod V-6
Changelog: increased 2nd GPU frequency step down and the goal of the experimental part is to lower overall temps
CTTMod- v6.1 revised
Change log: Fixed smoothness and I also modified the thermal hot plugging
Giving the option to use the stock thermal hot plug and still reap the rewards of this mod (please Google or an xda search on hot plug/ing if you don't know what it is before asking)
CTTMod 6.2: Improved performance
* 6- for MM *
* 7+ for nougat only *
CTTMod-V-7 1 Nougat
Updated for the final version on nougat (plus some added improvements)
Fixed and reuploaded
CTTMod 7.2 Nougat
Improved performance
CTTMod 8 over clocked nougat
Increased both big and little clustered first bump down and the GPUs first bump down to increase performance on kernels that can be overclocked to at least 2ghz on the big cluster and 1.7 on the small cluster
CTTMod 8.1 over clocked nougat Increased first bump down on big and little clusters
CttMod-Oreo-stock kernel-v-1
CttMod-Oreo-over clocked kernel-v-1
Donations are welcome but not required
At least please hit the thanks button to show your appreciation
Thanks Rob
Return to stock, pre-releases & governor settings
Return to stock-
Stock thermal
CTTMod 7.1.1 test version
Original thermals taken from the latest build of nitrogen ROM with there kernel
Go here for my CPU interactive governor settings for the best balance for performance and battery
I recommend elemental x kernel over clocked, I/o schedule to deadline and f sync off
Flashed over RR's stock kernel will update
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Yay...never thought I'd see this on the 6p...loved it on my old g3...about to test it on Android N...will report back
BakedTator said:
Yay...never thought I'd see this on the 6p...loved it on my old g3...about to test it on Android N...will report back
Click to expand...
Click to collapse
Thanks let me know what you think just remember this is my first official version more improvements to come
Robshr said:
Thanks let me know what you think just remember this is my first official version more improvements to come
Click to expand...
Click to collapse
Everything flashed fine, what temp should I start to see it throttle now?
BakedTator said:
Everything flashed fine, what temp should I start to see it throttle now?
Click to expand...
Click to collapse
I haven't changed the temps on this version only the CPU frequency it throttles to, I'm in the process of testing the next version with different temps
The Nexus handles things a bit differently then the g3 so I'm still working things out
Robshr said:
I haven't changed the temps on this version only the CPU frequency it throttles to, I'm in the process of testing the next version with different temps
The Nexus handles things a bit differently then the g3 so I'm still working things out
Click to expand...
Click to collapse
Good deal...even an extra 5 degrees would help...this phone throttles at a rather low temp...starts at 50c I think
Great to see Robshr here. Loved your mod on my further g3 and g4. Throttling seems really to be a problem on this phone. So i gonna flash this and report.
Gesendet von meinem Nexus 6P mit Tapatalk
Just flashed on n with stock kernel it booted up lol don't know if it worked tho
flashed this on Android N dp3, with elementalX Kernel.
How to confirm this working?
To check go to system/etc/thermal file
Sent from my Nexus 6P using XDA Labs
lenixroman said:
To check go to system/etc/thermal file
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I've only got this thermal-engine.conf so did it work on n
The thermal file was original there but when you flash the zip replace the original one with the mod one he only change some frequency in the thermal file he didn't touch the temp
Sent from my Nexus 6P using XDA Labs
Just what the 6P needs, the throttling kills performance on this phone so much.
This works with any kernel?
pa.pn2 said:
This works with any kernel?
Click to expand...
Click to collapse
Yes
Robshr said:
Yes
Click to expand...
Click to collapse
In the original OP for G# it says you have to have the thermal-engine-8974.conf file, which the 6P only has thermal-engine.conf, so is that same? Does still work? Not clear on that part. Thanks! Also, I have always kept msm_thermal and core control disabled, I can still do that right? Be disabled still?