Related
Read the thread before posting bugs or issues or questions
Table of contents:
Intro
Features/what this includes
Quirks of the kernel
Why it's labeled unstable
Disclaimer
Latest kernels
Methods of flashing
Benchmarks!
Instructions for using swap
Governor exlainations
Governor strategies
Recommended apps
Locating cpu% Eaters && other negative items towards battery life
FAQ!
Changelog
Stable/safe voltage kernels
Notes
Source
Credits
Old links, go here for other aosp roms with older video drivers & older builds
Intro: I'm scaryghoul
What this includes
It's scary!
Swap
Deadline I/o scheduler
Extreme undervolt
Overclocked & underclocked values
Sleepers disabled
Toast's new video drivers
Smartass governor
New Scary governor!
Tweaked conservative governor
and much more(All of toast's kernel)
Quirks of this kernel:
Sometimes when changing speeds with something like setcpu, they take a few seconds to actually clock to that speed, turning the screen on and off fixes it and clocks it right away though.
I would advise against using the speeds 66mhz->180mhz during real usage. It's a little laggy, but works =)
This doesn't work with sense based roms like mikshift, yes it needs to be said more than once
Why it's labeled unstable: So I don't get people poking me in the eyes with spoons if/when it freezes up. It actually works quite well, but since I heavily undervolted an undervolted kernel, it is bound to not be 100% stable(It is about 90% stable =P)
Disclaimer: What everyone else puts in kernel threads, about me not being responsible, ect.
Latest kernels
The voltages of the superUV will not work for everyone, if they don't work for you, then try the builds labeled stable
Recommended speeds 245-800mhz or 245-1ghz on scary governor && no setcpu profiles - I'll keep my current speeds in my signature.
Mirrors of kernels uploaded by VICODAN
Super SUV
http://www.mediafire.com/?47perl0d43n1nyr
Super Stable kernel
http://www.mediafire.com/?9qmtzuu35cpr8yz
Super Girly kernel
http://www.mediafire.com/?1s4z4y7bh78e04j
Methods of flashing
Joeykrim's "flashimage gui" app on the market using one of the zImage files from the zips. http://forum.xda-developers.com/showthread.php?t=1045797
Teamwin's "Kernel manager" app on the market. http://forum.xda-developers.com/showthread.php?t=1030500
Flashing via recovery using one of the zips here.
Benchmarks! - All done at 1.8ghz on cm7
Quadrant standard 1.1.7 - 3900 is the highest I've seen so far I believe.
Smartbench(2runs) - 2150/1850 - Mine were around there
Linpack(3runs) - 61, 63, 63 - These won't change much at all.
Instructions for using swap
For a swapfile do something like this.
dd if=/dev/zero of=$Swapfile bs=1048576 count=$Size
Where $Swapfile is the location of the file you want, and $Size is the amount of mb for swap you want to use.
Then type
mkswap $Path
swapon $Path
Replacing $Path/$Size with your own values of course, so if I wanted 20mb of swap I'd execute the commands
dd if=/dev/zero of=/sdcard/swapfile bs=1048576 count=20
mkswap /sdcard/swapfile
swapon /sdcard/swapfile
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/smartass-governor-info ) - "is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Governor strategies
Conservative - Upthreshold 85, downthreshold 60
Smartass - Sleep max 245760Hz, Ramp up at 384000Hz at a time, up threshold 90, downthreshold 60
Scary - Upthreshold 80, down threshold 45, sleep max 245760Hz, sleep min, 122880Hz
Recommended apps =)
Nofrills - App to manage I/O scheduler, clock speeds & governors.
Adw ex or go launcher ex
Colorize widgets - Great widgets to replace the lpp ones for those converting to other launchers.
AppMonster(pro or free) - Great backup utility, automatically backs up all apps.(I like it better than TB)
GPS Status - Great application for finding satalites near you and helping get a quick lock.
Any go dev team app - Great dev team, all their apps are worth looking at.
Frequently asked questions
Question: My phone is boot looping/not booting on the released suv, what do I do?
Answer: Your phone cannot handle the super undervolted values, you will need to flash the stable undervolted kernel or girly kernel
Question: My phone's graphics are running really lagishly, why is this happening? It worked fine on version 1.4 and before.
Answer: You are likely running an outdated version of your rom not supporting the new video drivers in version 1.5+, you will need to roll back to v1.4 and before
Question: My phone is running slow on the batterysave or scary governors, what do I do?
Answer: Set your minimum speed higher, those governors spend a lot of time at the lowest values
Question: My wifi/wifitether and other stuff is broken and wasn't before I flashed your kernel
Answer: READ THE BIG BOLD STATEMENT AT THE TOP OF THE THREAD THAT SAYS THIS IS NOT FOR SENSE
Question: How do I flash this?
Answer: You probably shouldn't be flashing a kernel labeled unstable if you don't know how
Question: I'm not getting the amazing battery life/benchmark scores that others are getting
Answer: Well, every device is different, so you may not be able to score as high as some others, but you should get close at least, and the battery completely depends on usage patterns
Question: My phone can't clock to 1.8ghz, or some of the other higher values but does fine on the lower ones
Answer: Every device is different and not all can handle the same speeds/voltages, you are probably better off staying away from the higher speeds, I enabled the speeds but hope that you all are mature enough to handle them
Locating cpu% eating applications.
When in ADB shell type the following
top |grep app
or if your rom supports it htop is much better(Without grep, so just "htop")
Then look for items with high amounts of cpu% while the phone is idle.
changelog:
Release1:
Swap support enabled
Unlocked 1.6-1.8ghz
Superundervolted
Release 2(1.1):
Unlocked 3 new underclock values
Took the undervolt farther.
Release 3(1.2):
Added hw3d
Release 4(1.3):
Removed interactive governor since it only causes trouble
Overall undervolt taken farther. May be unstable for some
Release5(1.4)
Disabled sleepers
Changed kernel name
Added an alternative voltage kernel
Release 6(1.5)
Cleaned up the source
Updated to toastcfh's new video drivers, greatly improved video performance and fixed a lot of issues with aosp video. - Thanks toast =D
Release 7(1.6)
Still cleaning up source
Addeed smartass governor && tweaked it, Down thresh: 70, up: 90
Added a real kernel name
Added lulz
Added two new clock speeds && modified voltage table
Tweaked conservative governor(Should be less erradict now, so scaling less==less power consumption==Yay =D)
Release 8(1.7)
Added Scarygov 0.5
Removed userspace governor
Release 9(1.7.2)
Tweaked scarygov to 0.6, removing a bug
Release 10(1.7.3)
Fixed a lag issue on scary governor by slightly optimizing the code.
Tweaked smartass.
Release 11(1.8)
Optimized scary governor's code
Safe voltage kernels && Stable kernels(come here if you can't handle the super undervolt
NEW VIDEO DRIVERS
1.8
ScaryKernel 1.8 stable http://dl.dropbox.com/u/15373824/ScaryKernel1.8safe.zip
Girly Kernel 1.8 stable http://dl.dropbox.com/u/15373824/GirlyKernel1.8safe.zip
1.7.3
ScaryKernel v1.7.3 stable http://dl.dropbox.com/u/15373824/ScaryKernel1.7.3Stable.zip
v1.7.2
ScaryKernel v1.7.2 safe uv http://dl.dropbox.com/u/15373824/Scarykernel1.7v2Safe.zip
v1.6
[UNTESTED]1.8Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/ScaryKernel1.6SafeJesusNoSleep.zip
v1.5
[UNTESTED]1.8Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/Scarykernel1.5StableJesus.zip
[UNTESTED]1.5Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/Scarykernel1.5StableNoJesus.zip
OLD VIDEO DRIVERS(1.4) - For roms that don't support the new video drivers.
1.5Ghz safe voltage kernel no sleepers http://dl.dropbox.com/u/15373824/ScarykernelSafe1.5NoSleepers.zip
1.5ghz safe voltage kernel, sleepers enabled http://dl.dropbox.com/u/15373824/ScarykernelSafe1.5Sleepers.zip
1.8ghz safe voltage kernel, no sleepers http://dl.dropbox.com/u/15373824/ScarykernelSafe1.8NoSleepers.zip
1.8ghz safe voltage kernel, sleepers enabled http://dl.dropbox.com/u/15373824/ScarykernelSafe1.8Sleepers.zip
Notes:
Nothing for now.
Here is the source code for this build. I'll try to maintain it, I have a lot of kernel sources, but this will always be the latest release code, unless I state otherwise.
https://github.com/Scaryghoul
Credits: Toastcfh/bcnice20 - For 99.8% of their kernel source.
Dogejcr/Preludedrew - For helping me get my laptop setup for kernel compiling.
Testers - For flashing this even though it says unstable :-X
JoesephMother - For helping me unlock the new lower clock values && other kernel related matters =)
x99percent - I used his middle clock speeds between the 3xx->7xx values as a base(edited voltages) as well as used his smartass source.
I just got my shifty two days ago from having the heroc. It took me a full five minutes to root the sob. This kernel clocking it to 1.8ghz is sick. Good job!
On my Gingerbreaded Evo-Shifted Premium XDA App.
Nice work again scaryghoul. Quadrant scores are very reflective of real-world performance in this case.
Awesome numbers coming off this kernel.
Quadrant = 3104
SmartBench 2011 = 2095/1887
SmartBench numbers were incredible!!!!
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
crump84 said:
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
Click to expand...
Click to collapse
Just curious but what rom?
Sent from my PG06100 using XDA App
I used 1.5 SUV no sleepers and the responsiveness of the screen lags while scrolling in adw. I flashed back to the stock #29 on N#32 and the lag is gone
Sent from my PG06100 using XDA Premium App
CrashV2010 said:
I just got my shifty two days ago from having the heroc. It took me a full five minutes to root the sob. This kernel clocking it to 1.8ghz is sick. Good job!
On my Gingerbreaded Evo-Shifted Premium XDA App.
Click to expand...
Click to collapse
Glad you can handle it.
smoothtaste said:
Nice work again scaryghoul. Quadrant scores are very reflective of real-world performance in this case.
Click to expand...
Click to collapse
Thanks =O
jjb61 said:
Awesome numbers coming off this kernel.
Quadrant = 3104
SmartBench 2011 = 2095/1887
SmartBench numbers were incredible!!!!
Click to expand...
Click to collapse
Thanks for sharing here =)
crump84 said:
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
Click to expand...
Click to collapse
What rom and which kernel....
threeFiftyLi said:
I used 1.5 SUV no sleepers and the responsiveness of the screen lags while scrolling in adw. I flashed back to the stock #29 on N#32 and the lag is gone
Sent from my PG06100 using XDA Premium App
Click to expand...
Click to collapse
Interesting. Never had that issue, what range of speeds are you using?
JKILO said:
Just curious but what rom?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Scaryghoul said:
What rom and which kernel
Click to expand...
Click to collapse
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
crump84 said:
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
Click to expand...
Click to collapse
Kernels before 1.5 aren't meant for the newest Cm.
1.5+the testing ones with the New video drivers, are the ones meant for it.
Scaryghoul said:
Kernels before 1.5 aren't meant for the newest Cm.
1.5+the testing ones with the New video drivers, are the ones meant for it.
Click to expand...
Click to collapse
Well I guess that would explain why I was having issues..
crump84 said:
Well I guess that would explain why I was having issues..
Click to expand...
Click to collapse
Version 1.5+ is meant for cm7's nightlies from 31+.
When I first tried it, I felt a little lag but after I wiped it ran better than before.
Scaryghoul said:
Interesting. Never had that issue, what range of speeds are you using?
Click to expand...
Click to collapse
Stock default 245/1200.
I'll try to wipe and start fresh when I have time. I started Nightly #27 freshly wiped but haven't wiped since.
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Edit: flashed release 1.5 uv 1.8ghz and it was acting up as well, on release 1.4 @ 1.8 ghz and the phone is really smooth, very fast and very stable. On a side note my performance numbers blow compared to the cm7 numbers, 1400/1400 smart bench, 48 avg linpack and like 2k on quadrant.....?
Sent from my PG06100 using XDA App
threeFiftyLi said:
Stock default 245/1200.
I'll try to wipe and start fresh when I have time. I started Nightly #27 freshly wiped but haven't wiped since.
Click to expand...
Click to collapse
Okay.
DWake014 said:
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Try one of the earlier kernels then, there might be some sort of aosp framework change required to take use of the new video drivers, I can't confirm it without hearing from toastcfh but that's why I say v1.5+ is for cm7 nightly31+.
I may be completely wrong about it though.
DWake014 said:
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Edit: flashed release 1.5 uv 1.8ghz and it was acting up as well, on release 1.4 @ 1.8 ghz and the phone is really smooth, very fast and very stable. On a side note my performance numbers blow compared to the cm7 numbers, 1400/1400 smart bench, 48 avg linpack and like 2k on quadrant.....?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Edit for your edit.
Yes, as I just said I think there might be some sort of framework change required/recompile of evervolv to support the new drivers.
Are you sure the speeds are taking? As described in the quirks, it takes a few seconds to take a speed for some, and sometimes requires screen off/on. I usually don't benchmark until linpack hits 60+
crump84 said:
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
Click to expand...
Click to collapse
I thought that was the problem
Sent from my PG06100 using XDA App
Ran some more tests, this is on Evervolv with release 1.4. Set it on 1.8/1.8 performance and:
Linpack (12 runs): avg 61, few 62s
quadrant free ( 8 runs) : avg ~2600, high was 2900
smartbench (7 runs) : avg 1800/1800, high of 1800/1900
Scaryghoul said:
Okay.
Try one of the earlier kernels then, there might be some sort of aosp framework change required to take use of the new video drivers, I can't confirm it without hearing from toastcfh but that's why I say v1.5+ is for cm7 nightly31+.
I may be completely wrong about it though.
Edit for your edit.
Yes, as I just said I think there might be some sort of framework change required/recompile of evervolv to support the new drivers.
Are you sure the speeds are taking? As described in the quirks, it takes a few seconds to take a speed for some, and sometimes requires screen off/on. I usually don't benchmark until linpack hits 60+
Click to expand...
Click to collapse
I think you're right on Evervolv cause mine from yesterday works great but my testkern.a2 is crap on there.
Nice job on the undervolting. I couldnt even boot the newest one! As always, appreciate your help with all my n00b questions.
Toasted by Nightly.
DWake014 said:
Ran some more tests, this is on Evervolv with release 1.4. Set it on 1.8/1.8 performance and:
Linpack (12 runs): avg 61, few 62s
quadrant free ( 8 runs) : avg ~2600, high was 2900
smartbench (7 runs) : avg 1800/1800, high of 1800/1900
Click to expand...
Click to collapse
Thanks for sharing =D
smoothtaste said:
I think you're right on Evervolv cause mine from yesterday works great but my testkern.a2 is crap on there.
Nice job on the undervolting. I couldnt even boot the newest one! As always, appreciate your help with all my n00b questions.
Toasted by Nightly.
Click to expand...
Click to collapse
Thanks =)
---------------------------------------------------
1.6 is out for the unstable voltage.
I'll compile the stable ones later, already made the commits to the github for what I can remember I changed
Check the changelog people =D
I want to make sure I'm not trippin', I've searched all thru the dev forum, and I don't see a non overclocked kernel. everyone complains about battery life but they are using a kernel that wasn't geared for battery life. oc kernels are for performance and bragging rights. we need a stock kernel with uv and ram optimization along with battery optimization mods
Sent from my Desire HD using XDA App
boimarc89 said:
I want to make sure I'm not trippin', I've searched all thru the dev forum, and I don't see a non overclocked kernel. everyone complains about battery life but they are using a kernel that wasn't geared for battery life. oc kernels are for performance and bragging rights. we need a stock kernel with uv and ram optimization along with battery optimization mods
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Why not just not overclock? Also, the kernel that comes in Inspired Ace isn't overclockable.
There are many battery saving options! If you have the Leedroid kernel, in setcpu you have the option of running your proccesor at Powersave, performance,smartass and so on...this is also in a few other kernels but I am not sure which ones at the moment.
And if you are really hyped up on saving battery, shutoff haptic feedback, turn of data when you are not using it, lower screen brightness, Use a task killer to kill stray apps(if you were playing angry birds kill it afterwards).
These are a few things you can do that will increase your battery life significantly...
With an overclock capable kernel, you can underclock. I run mine at 921 MHz and don't notice any performance hit. I've tweaked the undervolt to as low as I can get away with. I get pretty awesome battery life that way.
Before you ask, I'm using a kernel I compiled myself from HTC's latest linux source for the Inspire. It's essentially stock with only the addition of the frequency table and hooks for OC/UV.
Gene Poole said:
With an overclock capable kernel, you can underclock. I run mine at 921 MHz and don't notice any performance hit. I've tweaked the undervolt to as low as I can get away with. I get pretty awesome battery life that way.
Before you ask, I'm using a kernel I compiled myself from HTC's latest linux source for the Inspire. It's essentially stock with only the addition of the frequency table and hooks for OC/UV.
Click to expand...
Click to collapse
This.
Simply underclocking will solve your problems. I prefer to run @1.4 Ghz. I have everything optimized for speed & efficiency and still don't lose in battery performance.
Running CM7 with LordMod UE 2.6 kernel and smartass CPU governor, I can set the max speed to 768mhz with very little performance hit noticed. I might just keep it that way, haven't decided yet. Scrolling is still smooth, Angry Birds is still smooth. The cool thing about running max 768mhz with the pinky undervolt script is the CPU voltage never goes above 900mv.
I'm running CM7 with nightly 91 and on my Vibrant, they made a kernel that was stock uv no oc and u could use it all day, literally....
Sent from my Desire HD using XDA App
Can you experienced doods, help out a noob? I have recently rooted my phone (after MUCH research and reading) and just installed Set CPU app. I have been reading about the different settings for Set CPU, and it appears to be device specific, so I wanted to know if any can suggest some stable and useful settings and profiles I can use.
My goal would be to extend battery life and increase erformance while the phone is being used. I kinda guess this is most peoples reason for using this app. Slow the CPU down while the screen is off, and increase it a bit when the screen is on. I am not totally sure why you adjust it while it is charging. And wold this fi into the screen is off profile.
Ok enough rambling, and thanks for any assistance!
Forget SETCPU. Voltage Control is the way to go. For battery life, I would underclock to 100-800mhz and have -100mv all through the range. For performance, 100-1400 mhz (1.5 & 1.6 ghz are heavily overvolted) and have -100mv from 100-1000 mhz and -75 for 1100-1400. Leave the governers and io schedulers where they are.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Forget SETCPU. Voltage Control is the way to go. For battery life, I would underclock to 100-800mhz and have -100mv all through the range. For performance, 100-1400 mhz (1.5 & 1.6 ghz are heavily overvolted) and have -100mv from 100-1000 mhz and -75 for 1100-1400. Leave the governers and io schedulers where they are.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Using the voltage control within SetCPU or a voltage control app?
Thanks
Edit: after installing set CPU my phone seems to be running slower than usual. So, I ran a quadrant benchmark and it is coming up with much lower scores than it did before. Is there any way to set it back to the original cpu speeds with out deleting the app?
Delete setcpu and get voltage control from the market.
Sent from my SCH-I510 using Tapatalk
sneakysolidbake said:
Delete setcpu and get voltage control from the market.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
Thanks, can I use this with imnuts OTB kernal?
gdubya34 said:
Thanks, can I use this with imnuts OTB kernal?
Click to expand...
Click to collapse
you should be able to yeah.. try a different set of settings every day to find whats the most fast and stable on your phone, what works on mine may not necessarily work on yours or someone elses
blazing through on my VZ Droid Charge 4G
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
Tried those settings and my phone froze a few times so I upped the voltage to get it to work for me. This is my first time overclocking a phone. Do any of these settings look strange using voltage control?
100-400mhz uv-75
800-1000mhz uv-50
1200-1300mhz uv-25
I haven't froze yet, although I noticed my battery drains a little faster then normal (that was expected).
hmmm.... The GummyCharged GBE 1.9RC1 8/13/11 kernel is not incompatible with the Voltage control free app.
Error message "Unsupported kernel detected. The kernel your device is running is incompatible with Voltage control."
praveen1789 said:
hmmm.... The GummyCharged GBE 1.9RC1 8/13/11 kernel is not incompatible with the Voltage control free app.
Error message "Unsupported kernel detected. The kernel your device is running is incompatible with Voltage control."
Click to expand...
Click to collapse
GummyCharge GBE is gingerbread which means stock kernel, no voodoo and therefore no changing of voltage settings
blazing through on my VZ Droid Charge 4G
Gotcha! Thanks to that.
Now I have a crazy question below. (trust me there are even more questions all over my mind now)
When they say "ROM", I'm assuming that its collective of Kernel, all the apps and the radio.... Can't we just downgrade the kernel of "GummyCharge GBE" Rom?
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
These gave me a reboot watching netflix on wifi. Will try -25 @ 1300 and see what happens. Thanks for the post though. Its a great starting place for me.
running humble 1.51
Khanusma said:
These gave me a reboot watching netflix on wifi. Will try -25 @ 1300 and see what happens. Thanks for the post though. Its a great starting place for me.
running humble 1.51
Click to expand...
Click to collapse
Yeah those are kinda high 'performance' settings, not all phones like being overclocked or undervolted much less both lol.. Start with it just overclocked for a day or two and see how it runs, however there's gonna be some serious battery drain obviously. Then move on to undervolting slowly like maybe -25 across the board and leave 1400 alone for another day or two... just experiment like this until you have the right balance of speed, stability and battery life. As a matter of fact I toned mine down a bit afterwards and it worked nice:
Overclocked to 1.2ghz (1200mhz),
took out 600mhz frequency and set 100 to -75, then 200-800 at -50, 1000 and 1200 at -25
or if you want battery life and don't mind sacrificing a little performance you can underclock to 800mhz and set all to maybe -75... its a lot of testing to find what works for your phone, if it reboots freezes or lags too much its either overclocked too much or undervolted too much
edit: I also use the free voltage control app from the market, it lets you set min. and max. clock speeds as well as voltage so thats all I need lol
blazing through on my VZ Droid Charge 4G
praveen1789 said:
Gotcha! Thanks to that.
Now I have a crazy question below. (trust me there are even more questions all over my mind now)
When they say "ROM", I'm assuming that its collective of Kernel, all the apps and the radio.... Can't we just downgrade the kernel of "GummyCharge GBE" Rom?
Click to expand...
Click to collapse
Roms are not always all inclusive with a kernel and whatnot.. Most are custom apps, themes, and build/framework remakes to operate on top of the stock roms and will use stock radio and kernel to operate unless a custom radio/kernel is flashed. While most radios and apps will work well with different roms, kernels (being basically the 'engine' for the android OS i believe) are dependant on baseband and will not work by switching them around or flashing one over the other. This is the way I understand it to be anyway, I just know kernels are not compatible between 2.2 and 2.3
blazing through on my VZ Droid Charge 4G
anoninja118 said:
Roms are not always all inclusive with a kernel and whatnot.. Most are custom apps, themes, and build/framework remakes to operate on top of the stock roms and will use stock radio and kernel to operate unless a custom radio/kernel is flashed. While most radios and apps will work well with different roms, kernels (being basically the 'engine' for the android OS i believe) are dependant on baseband and will not work by switching them around or flashing one over the other. This is the way I understand it to be anyway, I just know kernels are not compatible between 2.2 and 2.3
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
Makes sense. I'm sure the apps and radio are dependent on the kernel as it is the core. (like an Operating system that provides the platform for applications to work.)
I'm sure the developers thoroughly test these combinations before releasing any ROM, .
However I want to have some fun updating the kernel on the GC GBE 1.9 that I currently have on my charge with couple other kernels out there....
Will see if I create some magic
praveen1789 said:
Makes sense. I'm sure the apps and radio are dependent on the kernel as it is the core. (like an Operating system that provides the platform for applications to work.)
I'm sure the developers thoroughly test these combinations before releasing any ROM, .
However I want to have some fun updating the kernel on the GC GBE 1.9 that I currently have on my charge with couple other kernels out there....
Will see if I create some magic
Click to expand...
Click to collapse
don't use froyo kernels with GB (as of right now there's only one custom GB kernel, navenedrobs nameless ext4 one), it will just lead to a soft bricked phone... i could be wrong but i think imnuts and imoseyon from team gummy are working on some GB kernel awesomeness
blazing through on my VZ Droid Charge 4G
What about the noop, fifo, bfq, vr options? What do these mean?
Sent from my gummycharged SCH-I510 using XDA Premium App
gdubya34 said:
What about the noop, fifo, bfq, vr options? What do these mean?
Sent from my gummycharged SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Don't touch them. They will either make your phone crawl or have FCs. It hasn't been implemented in the kernel yet.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Don't touch them. They will either make your phone crawl or have FCs. It hasn't been implemented in the kernel yet.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Oh crap, I am not sure what one it was on when I installed it. I think I changed it by accident. right now it is on the vr setting.
Are there any setting s to avoid when messing with the voltage control, and if I delete the app does go back to the default settings?
gdubya34 said:
Oh crap, I am not sure what one it was on when I installed it. I think I changed it by accident. right now it is on the vr setting.
Are there any setting s to avoid when messing with the voltage control, and if I delete the app does go back to the default settings?
Click to expand...
Click to collapse
To avoid: IO schedulers, overvolting (only done in Extreme), and going above 1400 mhz, as 1500 & 1600 are HEAVILY overvolted. Toasted processors=bad magic.
However, you can switch the governers from conservative to performance, but its kind of useless.
If you delete the app it will NOT go back to default...I think. The default io scheduler for imoseyon's kernel is deadline, I forgot what PBJ's is. If you switched it and its still working, don't worry about it.
Sent from my Droid Charge running GummyFroyo 1.9.1
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
DirtyPISTOLA said:
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
Click to expand...
Click to collapse
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
fcisco13 said:
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Alright thanks will try
Sent from my LG-P999 using Tapatalk
I've seen some general advice not to UV for anything over 1ghz speeds as well, but it may not hurt to try if you want and adjust as needed for stability.
I'm running on a -75mv at 1.5Ghz faux kernel 0.4.7..
Perfectly stable, benchmarked AnTuTu, Quadrant, and all those other good stuff.
I have not tried -100mv yet, I doubt it will be stable.
Every phone is different, but I run mine at -20 up to 1 G, and -10 for the rest.
Mine I cant undervolt shoot I have to keep my minimum frequency at 500 to be stable, course I can also run at 1.5 all day (I keep it at 1.2).
Well I guess I can't say I cant UV since I use pimp my cpu and it only gives you options in 25 increments, maybe I would be stable at like -10. But coming from my galaxy s 4g where I could UV over -150 and still be stable, that just doesnt even sound worth doing.
Edit: I just thought about it and maybe the reason I cant UV (more) is because I'm using fauxs pre UV/OC kernel, so I dont even know what stock voltage is. But comparing to my sgs4g at stock voltage I am running considerably lower voltages on the g2x.
The faux thread says it's pre uv at -50 across the board.
Beekersguy said:
The faux thread says it's pre uv at -50 across the board.
Click to expand...
Click to collapse
I been running it so long and flashed so many friends phones I can't even remember details anymore!
Sent from my LG-P999 using xda premium
1. Just like the title, i want to ask you guys which rom and kernel you guys are using now and which ones do you think are the best for overclocking nexus s cpu?
2. How did you set the settings? e.g. TWEAK, CPU, VOLT and etc..
I am currently using a korean rom called 'Provision' rom and Air 4.0.
Please reply in details
Morfic's Trinity kernel is easily the best overclocker/performance beast. Pretty much every other kernel supports LiveOC, Voltage control and Frequency control, which can all be set through NSTools.
I think that trinity T132 with cyberGR v10 is the best combo for overclock and overall speed
trinity t144 kernel is best for ocing/performance(if your phone can handle it, many cant but some phones love it), otherwise id say that trinity t132 is best.
voltage
I've just flashed T132 on my phone and it works very well.
Smooth but not that noticable.
Is there any way to set voltages up as well?
You guys also may want to try set cpu