This post has been edited because I added Mandrobench results because it utilization of both cores. Mandrobench scores were identical for both kernels. Running Mandrobench at 1500 more than once tended to overheat my phone and cause reboots and other signs of instability.
One thing is clear, if you run either Faux or Trinity kernel you must OC at least to 1100 or you take a huge hit on performance.
I ran 4 different benchmarks on every configuration of CM 10 times with the Faux and Trinity kernels. I normalized the results so that each benchmark was evenly weighted and so the numbers are better understood they were normalized so that CM with its own kernel scores 100. All other numbers are relative to that. The 4 benchmarks were Quadrant, Smartbench 2011, Linpack, and Mandrobench. The results are a bit surprising, I am attaching the spreadsheet so that anyone can check my methodology.
CM w/CM kernel 1000 MHz score 100
CM w/Faux kernel 1000 MHz score 77
CM w/Faux kernel 1100 MHz score 104
CM w/Faux kernel 1200 MHz score 114
CM w/Faux kernel 1300 MHz score 123
CM w/Faux kernel 1500 MHz score 138
CM w/Trinity kernel 1000 MHz score 85
CM w/Trinity kernel 1100 MHz score 116
CM w/Trinity kernel 1200 MHz score 124
CM w/Trinity kernel 1400 MHz score 140
CM w/Trinity kernel 1500 MHz score 147
Test for each configuration were started following a reboot with a battery charged over 60%. They were run sequentially the same way for each configuration. Each number above was the result of the averaging a total of 30 benchmarks.
Interesting note, the first couple Quadrant scores on each run were generally lower than the rest, result of caching by the phone perhaps? On certain configurations the Smartbench results fluctuated wildly producing unexpectedly low scores. Not sure what the reason for this fluctuation but it is repeatable, at least on my phone, but only on certain configurations.
This took a long time, I am sharing it because I found the results unexpected and that they might be useful to somebody. Not everyone is dumb enough to sit and run benchmarks all day. Would be interesting to know how close the numbers are ran on another phone. I am intentionally only providing the numbers and my methodology, I will leave it to someone smarter to explain them.
Add Mandrobench to the list... only app that utilizes TWO cores for its benchmarking (free too). Then we'll talk.
EtherealRemnant said:
Add Mandrobench to the list... only app that utilizes TWO cores for its benchmarking (free too). Then we'll talk.
Click to expand...
Click to collapse
I agree, Mandrobench should have been included, I didn't originally because it has disappeared from the market. I have searched my back-ups and found the apk, so I will incorporated them into the experiment later today. It is my understanding that most current apps do not take advantage of the dual core, therefore the results from benchmarks that are not optimized for dual-core have significance.
EtherealRemnant said:
Add Mandrobench to the list... only app that utilizes TWO cores for its benchmarking (free too). Then we'll talk.
Click to expand...
Click to collapse
Above not available anymore on market - maybe post the .apk.
Let me start by saying thanks! This undoubtedly took a very long time and it was nice of you to share the results with everyone. Did you use only ext3 or ext4 kernels or a combination of both?
Sent from my LG-P999 using Tapatalk
I appreciate u sharing your results. Just a quick question. was ur battery life changed a lot while u overclocked it. Also what's the difference between ext4 and 3
Sent from my LG-P999 using XDA Premium App
EtherealRemnant said:
Add Mandrobench to the list... only app that utilizes TWO cores for its benchmarking (free too). Then we'll talk.
Click to expand...
Click to collapse
Mandrobench was added to my original post. These results were identical for both kernels.
r4d14n7 said:
Let me start by saying thanks! This undoubtedly took a very long time and it was nice of you to share the results with everyone. Did you use only ext3 or ext4 kernels or a combination of both?
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Both kernels were ext4, made much easier to switch back and forth by the new version of clockwork.
Both of these are file systems and ext4 is newer and theoretically faster, probably more so on a computer where there are more read/writes to disc. I don't think any of these benchmarks test for this. Someone else may correct this as I don't know a lot about phones, I am a computer guy, and an out of date one at that.
moeahmad1995 said:
I appreciate u sharing your results. Just a quick question. was ur battery life changed a lot while u overclocked it. Also what's the difference between ext4 and 3
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Running consecutive benchmarks can kill a battery in 2 hours.
Battery life is a subjective, I haven't thought of a way to objectively test it. I feel I get the best battery life with CM with its own kernel or Eaglesblood Froyo. Bionix appears to eat batteries.
After seeing these results, I plan to run the Trinity UV11 kernel for awhile and see to see how good the battery life is. The performance increase appears significant for only OC to 1100 and I like the idea of getting the advantages of a little OC/UV without having to run Pimp my CPU.
I have gotten a clear increase (hours more idle time) by simply turning off 4G and only toggling it on when I need it. I use Pandora a lot and it ironically runs better at 2G when I am bicycling (less drops interruptions in the streaming as I move around).
Cubeology said:
Running consecutive benchmarks can kill a battery in 2 hours.
Battery life is a subjective, I haven't thought of a way to objectively test it. I feel I get the best battery life with CM with its own kernel or Eaglesblood Froyo. Bionix appears to eat batteries.
After seeing these results, I plan to run the Trinity UV11 kernel for awhile and see to see how good the battery life is. The performance increase appears significant for only OC to 1100 and I like the idea of getting the advantages of a little OC/UV without having to run Pimp my CPU.
I have gotten a clear increase (hours more idle time) by simply turning off 4G and only toggling it on when I need it. I use Pandora a lot and it ironically runs better at 2G when I am bicycling (less drops interruptions in the streaming as I move around).
Click to expand...
Click to collapse
Really? I found that these 2 kernels gave me better battery life then the stock cm7 kernel. Also can you add antutu benchmark to the list?
maxesxp said:
Really? I found that these 2 kernels gave me better battery life then the stock cm7 kernel. Also can you add antutu benchmark to the list?
Click to expand...
Click to collapse
you are also quoting and talking about a response from 6 months ago which was beginning stages for cm7 on this phone especially kernels lol... Glad you are getting great performance and battery though.
mt3g said:
you are also quoting and talking about a response from 6 months ago which was beginning stages for cm7 on this phone especially kernels lol... Glad you are getting great performance and battery though.
Click to expand...
Click to collapse
LOL oops I need to start learning to read dates.. -.-
Sent from my LG-P999 using Tapatalk
some one should run tests again
I tested Trinity vs Faux in AnTuTu and got pretty much same results on charger,but off charger Trinity got about 50 more (6000 off charger and 6125 while charging)
I use UV kernels clocked at 1100.
Switched to Faux because Trinity has bugs like reboot hangs the phone and sometimes waking up take a while. Also boot image and animations are not that nice and boot sound with kernel doesn't even seem to be working.....
Trinity 6004-6120
Faux 5918-6124
CM Stock around 5500
kolyan said:
some one should run tests again
I tested Trinity vs Faux in AnTuTu and got pretty much same results on charger,but off charger Trinity got about 50 more (6000 off charger and 6125 while charging)
I use UV kernels clocked at 1100.
Switched to Faux because Trinity has bugs like reboot hangs the phone and sometimes waking up take a while. Also boot image and animations are not that nice and boot sound with kernel doesn't even seem to be working.....
Trinity 6004-6120
Faux 5918-6124
CM Stock around 5500
Click to expand...
Click to collapse
Why are you getting such low scores? Not OC'd maybe? I'm using Fauxs newest kernel and my Antutu score was 7566. Average scores around 7300-7600
Sent from my LG-P999 using xda premium
mike7169 said:
Why are you getting such low scores? Not OC'd maybe? I'm using Fauxs newest kernel and my Antutu score was 7566. Average scores around 7300-7600
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Faux's newest kernel is ~1.5 correct?
He's probably using the Trinity battery saving kernel clocked at 1.1 and undervolted.
I use the Trinity 1.1GHz kernel and undervolt to -200mV (for the lower ones, leave the top three at stock for stability reasons) and I score around 6100 in Antutu.
redmonke255 said:
Faux's newest kernel is ~1.5 correct?
He's probably using the Trinity battery saving kernel clocked at 1.1 and undervolted.
I use the Trinity 1.1GHz kernel and undervolt to -200mV (for the lower ones, leave the top three at stock for stability reasons) and I score around 6100 in Antutu.
Click to expand...
Click to collapse
That makes sense. I just did a benchmark @1.1ghz and I got 6007. Ya the Faux kernel max is @1.5ghz. Its undervolted too, not much, just enough to get great battery life.
Sent from my LG-P999 using xda premium
I said in post that I use UV kernels clocked at 1100mhz
I now use Trinity Kernel because Faux did not have 216Mhz option in SetCPU. I also UVed by -25 for now and set charging profile to 400+ Mhz to avoid SoD
I wonder whats the difference in battery life if you use 1100Mhz or 1500Mhz ?
kolyan said:
I said in post that I use UV kernels clocked at 1100mhz
I now use Trinity Kernel because Faux did not have 216Mhz option in SetCPU. I also UVed by -25 for now and set charging profile to 400+ Mhz to avoid SoD
I wonder whats the difference in battery life if you use 1100Mhz or 1500Mhz ?
Click to expand...
Click to collapse
It's a significant difference. I don't have any data to back it up. But I've accidentally left it on the max after a benchmark and it would be in a free fall. Especially when playing a 3D game like MC3
Sent from my LG-P999 using xda premium
I've tried using both Kernels as well as stock. Granted they both seem to run better then stock, I'm currently on Trinity with Standard Voltage, because the Under voltage versions of both Faux and trinity seemed to freeze on reboots for whatever reason. They both appear to run about the same set at 1100 which is what I've set to.
I'd like to say thank you for performing scientific and useful benchmarks!
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
hello, I just wanted to make this thread for everyone to share their lowest AND stable voltage values for each frequency. Here goes mine:
(anything above 1000mhz was not tested)
1000mhz <-- 950mV
800mhz <-- 825mV
500mhz <-- 550mV
300mhz <-- 500mV
The following was done with eb1.0.4 + trinity kernel.
please share yours.
Copied from the kernel thread...
Bionix 2 at 1.2Ghz using deadline scheduler.
I attached my PMCpu settings in case anyone needs a reference.
Stressed tested for 15 mins stable.
Quadrant at 3337, Linpack around 45.
Click to expand...
Click to collapse
I started by doing -50 on all from 1200 oc...ill test for a whole day and drop it down -25 tomorrow and test for a whole day. And please post scheduler also.
So far @-50 on deadline scheduler all is working well, no freezes.
G2X
And how is battery life for everyone?
I can't belive how efin good mine has been, bt on, wifi on for 2 hrs, on xda forums every 30 minutes unplugged at 4:30a at 1:00p still had 55% left, whereas stock kernel would be at 15-10%...
G2X
GideonX said:
Copied from the kernel thread...
Click to expand...
Click to collapse
Using your settings running very smoothh!
Sent from my LG-P999 using XDA Premium App
fcisco13 said:
I started by doing -50 on all from 1200 oc...ill test for a whole day and drop it down -25 tomorrow and test for a whole day. And please post scheduler also.
So far @-50 on deadline scheduler all is working well, no freezes.
G2X
Click to expand...
Click to collapse
I have no idea what schedulers are
Also, a question to everyone, what are some of your unstable symptoms from UV? Since I've never had any rebooting issues with my g2x, I am not sure if some of the symptoms I was experiencing is from UV'ing or from the kernel. If you gone under the UV limit, does your phone just freeze or would it autoreboot?
c19932 said:
I have no idea what schedulers are
Also, a question to everyone, what are some of your unstable symptoms from UV? Since I've never had any rebooting issues with my g2x, I am not sure if some of the symptoms I was experiencing is from UV'ing or from the kernel. If you gone under the UV limit, does your phone just freeze or would it autoreboot?
Click to expand...
Click to collapse
UV will more than likely freeze or you will reboot... UV typically just makes everything really unstable, you might get stuck in a bootloop and have to reflash
JHaste said:
UV will more than likely freeze or you will reboot... UV typically just makes everything really unstable, you might get stuck in a bootloop and have to reflash
Click to expand...
Click to collapse
oh and a precaution to those using eb1.0.4 + trinity kernel. I set my max voltage for 1000mhz (my max. frequency as well) too low, and the phone autoreboot on startup twice and then did a factory reset itself This happened twice so be aware
GideonX said:
Copied from the kernel thread...
Click to expand...
Click to collapse
I'm running this settings and so far really good.
Thanks man!
Sent from my Bionix 2 - A TeamWhiskey Production using XDA App
fcisco13 said:
I can't belive how efin good mine has been, bt on, wifi on for 2 hrs, on xda forums every 30 minutes unplugged at 4:30a at 1:00p still had 55% left, whereas stock kernel would be at 15-10%...
G2X
Click to expand...
Click to collapse
What ROM and Kernel are you using? Also, which EB can be used with the Trinity kernel? GB or FroYo?
Anyone find that their battery has actually gone down while UV'ing? I'm finding after a full charge, the first 30% has been quicker by almost an hour. Not a really scientific method of testing, but I do just about the same thing every morning (email, txt, etc.) left over from the night before. That first 30% has a lot of screen off time, which will lower the speed to 300Mhz using PMCpu.
I'm going to up the voltage to at least 700 for 300Mhz and see how that fairs.
hah2110 said:
What ROM and Kernel are you using? Also, which EB can be used with the Trinity kernel? GB or FroYo?
Click to expand...
Click to collapse
--EB 1.0.4 FROYO (gutted removed live wallpapers, wifi calling, tmo stuff)
--Trinity 15 EB1.04 FROYO
[email protected] pimp my cpu (free on xda)
--Went down -50volts on all speeds
Battery is unbelievable..
G2X
I just restored my EB 1.02. I'm going to flash trinity kernel and report back after one day of use.
Sent from my LG-P999 using XDA App
I've heard several people had lockups and phone factory reset when uv too low, i think going more than -50 is really risking it...
G2X
fcisco13 said:
--EB 1.0.4 FROYO (gutted removed live wallpapers, wifi calling, tmo stuff)
--Trinity 15 EB1.04 FROYO
[email protected] pimp my cpu (free on xda)
--Went down -50volts on all speeds
Battery is unbelievable..
G2X
Click to expand...
Click to collapse
Can Trinity be used with EB Gingerbread?
hah2110 said:
Can Trinity be used with EB Gingerbread?
Click to expand...
Click to collapse
There are specific kernel for gb, look for one that is for EB1.04GB
G2X
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
EDIT:
So I was asked what kernel I'm using... I will post my ROM + KErnel! and just to let you know, my G2x has never had any problems so that may be way my G2x can get -200 on 500 and 400
And I am using faux's CM7 Kernel Version 0.2.4
Full name:
"2.6.32.41-CM7-Faux123-v0.2.4
Mod version
CyanogenMod-EagleBlood_v1.2
Im new to setcpu, good thread for me to learn a bit more from other users...
Sent from my LG-P999 using XDA App
Yes I'm trying to decide on SetCPU or PimpMyCPU so any info is appreciated
GManLynx said:
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
Click to expand...
Click to collapse
What kernal are you using?
GManLynx said:
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
Click to expand...
Click to collapse
How are you not getting reboot problems with 400 at -200mv? I'm using faux's froyo kernel and when I undervolt at -100mv i get rebooting problems
I replied to your comment in my main post, since other people may be interested in that and that will cause them not to scan the pages.
Bump :\ I would like input
so how is your battery life?
Bad. Something about those settings messed it up. I much prefer just using the custom rom default kernel its much better on the battery
Sent from my LG-P999 using XDA Premium App
My chip could only use faux's OC 1.2ghz, using the kernel OC 1.5 would cause my phone to boot loop. I could go stable @ faux OC 1.2 with minimum UV, getting qudrant score of atleast 3000 - 3500. Another kernel that i tried is MOrfic's, I can go stable up to 1.4 Ghz/minimum UV- quadrant of atleast 4000-4300. I believe i have what they say as the "weak chip" though running OC @ 1.4 ghz doesn't make it look weak. Thanks to the great DevS!
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