Related
I have tried just about every kernel i have come across. The 2 with the best performance i have noticed are:
1. http://www.ziggy471.com/ "scroll down"........ quadrant 3000 @1.8
2. http://forum.xda-developers.com/showthread.php?t=1022460 quadrant 2750 @ 1.8
My question is that when i have these kernels on ondemand with a min and max at 1800. i can run a stress test and confirm its stable. however when i start to scale and bring a minimum into the equation. Is when i start to expierience freezes. Is this possibly a scaling issue? set cpu issue?
Thanks
If you are basing performance upon quadrant scores and speed, you are doing it all wrong. And there is no need to run it at that speed, you don't notice a difference from 1.4-1.8. Don't run it so fast and you probably won't get the lockups anymore. Just because you can run a stress test doesn't mean that it won't lock up during everyday use.
Please post in the correct section next time.
Sent from my ADR6400L using XDA App
Paulb787 said:
I have tried just about every kernel i have come across. The 2 with the best performance i have noticed are:
1. http://www.ziggy471.com/ "scroll down"........ quadrant 3000 @1.8
2. http://forum.xda-developers.com/showthread.php?t=1022460 quadrant 2750 @ 1.8
My question is that when i have these kernels on ondemand with a min and max at 1800. i can run a stress test and confirm its stable. however when i start to scale and bring a minimum into the equation. Is when i start to expierience freezes. Is this possibly a scaling issue? set cpu issue?
Thanks
Click to expand...
Click to collapse
I am also interested in kernel dev responses concerning the min scaling. I have tried quite a few kernels as well and have noticed that when scaling to a min they become more fragile over time. Is this due to dropping/adjusting the voltages versus a set voltage at a set speed? How is that handled by the cache?
I guess the overall stability of the kernel when scaling is what I am wondering about as well. I doubt it is the handling by setpcu. I wish I knew more so I could expound upon the original question.
What factors are we looking at for stability when scaling multiple voltages and clock speeds?
As an observation of mine....
If I do NOT install setCPU and modify the settings maually, I do not have any lockups. I do recall reading that setCPU can cause some issues with certain kernels. Could be that using setCPU to modify the settings causes some misconfiguration that leads to the lockups.
Sent from my ADR6400L using XDA Premium App
I was looking into manually setting the freq. I do believe that setcpu is corky and causing some problems. Is there a page that you can direct me 2 for more info?
have you tried using one of Adrynalyne's kernels?
http://forum.xda-developers.com/showthread.php?t=1024338
try installing the latest one and use the 'smartass' governor. that particular governor should alleviate your need for using setcpu other than to overclock it.
First off i take no credit for the virtuous oc daemon itself, it was developed by rmk40.
And credit goes to -viperboy- for the idea, i used his rom and really liked the oc daemon and saw the difference it makes. Check his rom out here. It has a nice interface to control the oc daemon and other features of the rom.
You can get more info here
DON'T use any apps to adjust cpu with this ie., setcpu, cpumaster, etc.
Ok, here is the deal flash the zip file the script will run by itself the only adjustment you have to make is the virtuous oc settings. This should work with any rom and probably any device i just don't have any other devices to test it on.
Here is how:
Open root explorer (or whatever file manager you use) and navigate to /system/etc/virtuous_oc, you will see 6 files named:
sleep_governor
sleep_max_freq
sleep_min_freq
wake_governor
wake_max_freq
wake_min_freq
These are the files you edit to your liking, i only edited wake_max_freq to read 1836000 or 1.8ghz
The two governor file have different settings and they are:
conservative
userspace
powersave
ondemand
performance
Again edit to your liking i left them ondemand myself seems to work good. I don't really know what the settings do exactly when it comes to these but they seem pretty self explanatory.
To see if it's working all you need to do is open terminal emulator or adb shell and type one of the following:
Current CPU frequency
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Current CPU governor
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Current min CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Current max CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
It autostarts using init.d, so MAKE SURE your rom supports init.d, if it doesn't you can still use it but it has to be started manually by entering the following in terminal emulator:
Code:
/system/xbin/virtuous_oc
If you overclock MAKE SURE your kernel supports it, I'm not responsible for any damage incurred
In the future i want to make an app to control the settings but i am still learning that part.
Big thanks to rmk40 for this awesome daemon and -viperboy- the bad ass idea !!
EDIT:
A basic rundown of the oc daemon is it scales up your cpu when you screen is on and scales it down when it is off, so your cpu is not overclocked continuously. It does save on battery as long as you don't get crazy with the overclocking.
rugedraw said:
The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
Click to expand...
Click to collapse
Added my pcm controls to the downloads, this will underclock/overclock(soon i hope) your battery when the battery reaches a specified percent. See this post for more details: http://forum.xda-developers.com/showthread.php?t=1227938
Changelog:
8/11
-Added Juwe11 ram optimization script
-Added speed up SD hack (Set at 3072) Details here
8/14
-Added Uninstaller
8/24
-Added virtuous_oc_pcm
Sweetness! To OC or UC, do you need to to increase or decrease the processor speed by certain increments? If so, please add them the OP for all of us noobs.
Thanks!
Edit: Since you didn't reserve any additional posts, feel free to shoot me a PM if you want me to add anything to this post in the future.
rugedraw said:
Sweetness! To OC or UC, do you need to to increase or decrease the processor speed by certain increments? If so, please add them the OP for all of us noobs.
Click to expand...
Click to collapse
Basically you can set them to what you want within reason, the way i do it is
1836000 is 1.8ghz
1188000 is 1.1ghz
So if you just put a . in between the first 2 numbers its roughly the ghz so
1288000 would be roughly 1.2ghz, at least that's my understanding if i'm wrong i'm sure someone will correct me. I wouldn't go crazy and set it at 2288000 that might do some damage.
Woooohooooo!!!! Im going in. Thank you sir!
hTc Evo [3D]
smokin1337 said:
I wouldn't go crazy and set it at 2288000 that might do some damage.
Click to expand...
Click to collapse
The phone would most likely reboot/crash.
Sent from my PG86100 using XDA App
DDiaz007 said:
The phone would most likely reboot/crash.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
And die! Haha
Id hate to be the one tackling that script :/
hTc Evo [3D]
Why yes, I'll take one thank you.
Dude! Freakin' awesome! I've been hoping someone would create this. Thanks!
smokin1337 said:
Basically you can set them to what you want within reason, the way i do it is
1836000 is 1.8ghz
1188000 is 1.1ghz
So if you just put a . in between the first 2 numbers its roughly the ghz so
1288000 would be roughly 1.2ghz, at least that's my understanding if i'm wrong i'm sure someone will correct me. I wouldn't go crazy and set it at 2288000 that might do some damage.
Click to expand...
Click to collapse
Actually, 1288000 is 1.3 rounded up and 118000 is the stock 1.2 speed, but I get what you're saying.......maybe I didn't do a good job of explaining myself. If you want 1.5, you can't set it at 150000......you'd have to set it at 1512000 (or something like that) because it must go up or down by fixed increments. I don't remember what the exact increments are, but I can look it up and post it if you'd like.
Edit: The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
I haven't tried using this method yet, as I'm already OC'd using viperboy's script. Maybe someone else can test this and confirm it is accurate.
Sent from my PG86100 using XDA Premium App
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Thanks rugedraw i added the frequencies to the op.
clamknuckle said:
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Click to expand...
Click to collapse
SetCPU can take up to several seconds to adjust, and it uses RAM also. A Daemon is instantaneous, and uses little to no RAM.
Sent from my PG86100 using XDA App
clamknuckle said:
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Click to expand...
Click to collapse
This is developed by Virtuous Unity for stability in OC the CPU, Set CPU uses some voltage to run and has been known to be unstable at times, this is the most stable way to control OC frequencies right from boot.
The Daemon works great (I have a version of this I'm testing on the MT4G at the moment) and there are benefits to using it, I would have to say it's important to spend some time reading information on Kernels to better understand what your using and the risks behind it.
Found Here: http://forum.xda-developers.com/showthread.php?t=1143177
( Scroll to the 4th Post for full information on the Daemon )
State-of-the-art-solution
So we (more precisely rmk40) thought of a better solution.
He wrote a native C Daemon which changes the governors instantly without any lag.
This leads to major performance improvements right after turning on the screen and in the lockscreen.
But at the moment this solution is a little bit harder to configure. We are planing to make a GUI for this, so you get the same comfort as using SetCPU.
Nevertheless you can even now adjust the daemon to your needs.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
Click to expand...
Click to collapse
smokin1337 said:
Thanks rugedraw i added the frequencies to the op.
Click to expand...
Click to collapse
No worries.........glad I can help with the little stuff. However, it seems like basic math is too hard for me. The correct increments are 54,000 and NOT 48,000. After some careful review, some of the high end OC frequencies had typo's, as well. I changed the info in myl post, but please update the OP, as well. I'm sure most people will be referring to that.
Just set this up on Rewind 2.1 and it appears to be working awesome.. definitely seems smoother then using a screen off profile in setcpu..
What I don't get is why Google doesn't incorporate something like this in all Android builds. It seems there are many things that can be manipulated to improve battery life on Android devices but that these solutions are just being ignored. Anyhoo, I don't think I will ever use SetCPU again...
Useless without voltage control
So this will work with nets kernel, and not against it? Just use it instead of setcpu?
NCspecV81 said:
Useless without voltage control
Click to expand...
Click to collapse
It definitely isn't useless without voltage control. I don't see how saving battery and using no system resources is useless. Plus, you cannot edit voltages on the E3D kernels yet, the sysfs HAVS interface needs to be implemented first.
-viperboy- said:
It definitely isn't useless without voltage control. I don't see how saving battery and using no system resources is useless. Plus, you cannot edit voltages on the E3D kernels yet, the sysfs HAVS interface needs to be implemented first.
Click to expand...
Click to collapse
I believe him. Hell, I all those frequencies I posted came from the OC script he designed for his rom.........which is awesome.
Samsung Fascinate CDMA
Rooted MIUI 1.9.16
Did a brief search here looking to understand how to operate overclocking kernals, but find it/me relatively limited.
I have installed and ran Glitch v11 and v12, played around with HL to LL, and made adjustments to undervoltage utilizing Pimp My CPU and Voltage Control. I have also ran Tweak (though not really a kernal).
My question is this,
am I overclocking when I reduce voltage on Mhz's above 1,000?
If not, could someone point me to, or explain how to achieve overclocking on our phones, and
which kernel and governor do you prefer for overclocking?
As an ammended note, I've installed Tegrak Overclock, but am still looking for a user guide...
Thank you for your time.
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
efan450 said:
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
FJRSport said:
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
Click to expand...
Click to collapse
come on man.. Clock speed (mhz) and undervolting are 2 completely different things.. Forget the voltage.. No changing the voltage is NOT overclocking.. You overclock by changing your maximum clock above 1000mhz which is stock for this phone.. Try long pressing 1200mhz and selecting set as max.. Now your overclocked to 1200mhz..
Sent from the fascinate that holds the record benchmark on antutu
No decreasing the voltage is simply undervolting whether it's over 1000 or under. The idea behind undervolting is increasing battery life, but you can't necessarily go and set each level to the maximum undervolt (200) you half to see what works. Increasing the processor speed is overclocking, stock speed is 1000 so anything over that is over clocked. As far as how far as how far you can over clock depends mostly on 2 things, 1. the kernel your using, ( for example if it shows 1300 in the list that means thats all that specific kernel supports) 2. It varys greatly between phones. For example with glitch you can overclock to 1700 but very few phones can run that high for longer than a few minutes!
Hope that helps.
Sent from my SCH-I500 using xda premium
Yes.. And the fact you say your running glitch and your max oc is only 1300 my guess is you broke your kernel with tegrak overclocks module.. Delete tegrak and stop downloading overclock apps. or any other root app unless you know fully the consequences first.. If after deleting tegrak, and rebooting, if your voltage control don't show a maximum clock of 1700 mhz, then you will need to reflash your glitch kernel
Sent from the fascinate that holds the record benchmark on antutu
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
FJRSport said:
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
Click to expand...
Click to collapse
There are no issues with glitch.. It is what I run.. Very smooth.. Just have to give your phone time to adjust and build cache
Sent from the fascinate that holds the record benchmark on antutu
Landscape
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
sageDieu said:
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
Click to expand...
Click to collapse
That was it. I had re-installed the older Glitch v12 that was already on my PC. Deleted them and downloaded the newer Glitch kernels to experiment with.
Thanks!
FJRSport said:
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Click to expand...
Click to collapse
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
OC & UV settings
neh4pres said:
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
Click to expand...
Click to collapse
Yeah, locking and rebooting was while using the older version of Glitch v12. With the 9/15 dated Glitch I'm at 1300 now with the following settings:
Deadline / ondemand
200 - 1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
1.2GHz is the best I say if you want good battery with a higher frequency. 1.4GHz is the best for anyone who uses their phone alot. Samsung did add 1.2GHz overclock in their source.
Sent from my SCH-I500 using XDA App
Back to running MIUI without Glitch.
Things that make you go, Hmmm?
For some reason, every time I accessed the keyboard for Google+, it hung, then froze, and 3 of the four times rebooted. The fourth time I needed to remove the battery to reboot. So I re-flashed MIUI 1.9.16 (effectively removing Glitch) and have 0 problems.
Bummer, I like Glitch too.
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
mkropf said:
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
Click to expand...
Click to collapse
are you using JT's 9/12 kernel?
if so...did you overclock it?
i'm on jt's 9/12 with miui 1.9.16 and wondering if I can / should overclock and undervolt it. I'm just trying to maximize battery life at this point.
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
sageDieu said:
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
worshipNtribute said:
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
Click to expand...
Click to collapse
You wouldn't want to use my voltages, I put everything way lower than anybody else does or recommends and am just lucky that it is stable for me but it causes the sleep of death for anyone else.
For comparison, just run JT's kernel for a bit and then flash glitch and try it... once you play with OC/UV and voodoo color you won't be able to go back. (you'll be able to but you'd have to be insane.)
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.
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