VisionKernel v1.2
Designed for SyndicateROM Frozen 1.1.0
Disclaimer
I nor any member of INC is responsible for anything that happens to your phone when using this kernel. It has been tested on mine and a few others phones to be working, but I cannot guarantee that it will work on yours. All CPU's are different, and each one takes to overclocking in different ways. That being said, don't be surprised if your phone locks up at 1.4ghz or 1.45ghz. Just set the clock down to a lower speed and it won't do it anymore; all this means is that your phone can't handle it.
Also, 1.45ghz is set at 1.400v and 1.4ghz is set at 1.375v which is definitely above the recommended voltage for the phone. This doesn't mean it will burn up your processor as they are very robust when it comes to heat dissipation, but just keep in mind that you are pushing the processor past its designed limit.
This is my first kernel release, although I have been compiling my own custom kernels since DI18. Took me a while to get the overclocking stable, a big thanks goes to tanimn and Rodderik for helping with getting 1.3ghz stable. Also, without tanimn none of this would really be possible. He has guided me through this process a lot, and I am especially thankful to him. You the man tanimn ;-)
1.45ghz is here, I cannot guarantee that it will work even at all on your phone. This is as high as I will go, no further.
Linpack: 19.84mflops
Quadrant: 2414
Changelog
*=Thanks!
v1.0
Overclocked to 1.3ghz and 1.4ghz @ 1.375v (steps are as follows)
100mhz, 200mhz, 400mhz, 600mhz, 800mhz, 1.0ghz, 1.3ghz, 1.4ghz
Added 600mhz step for better transitions *tanimn
Voodoo Sound v6 *tanimn and supercurio
Voodoo Color (mDNIe tweaks) *supercurio
FPS cap raised to 65fps for the time being, hoping to get that number higher *Rodderik
Everything else that is contained in Twilight Zone, minus the addition of voodoo color and 1.4ghz.
v1.1
Revert the refresh rate (framerate cap) to 56fps. People having problems with video choppiness, this should fix your issue. This is only temporary; as soon as someone can figure out a proper way to raise the framerate cap I will re-implement it.
Update to Voodoo Sound driver v7
v1.2
Add 1.45ghz (It's not 100% stable, use at your own risk.)
Add 1.2ghz step
Added BFQ disk scheduler
Implemented interactive CPU governor (use at your own risk, needs tweaking)
Smartass governor (still a WIP)
Add TinyRCU courtesy of tanimn
lowmemorykiller atomic notifier fixes
UV RAM and LCD; 2.7v and 1.65v respectively
UV_mV sysfs controls as well as frequency_voltage_table for use with Voltage Control and Pimp my CPU *Rodderik
New voltage/frequency tables thanks to Rodderik!
v1.3
Battery life improvement tweaks
BFQ by default
New frequencies
More...
How-to Video:
Thanks to qbking77 for making this excellent flashing tutorial! This will show you exactly how to get the kernel running on your phone.
http://www.youtube.com/watch?v=1k7hqewGoWk
*Downloads*
v1.2
Direct:
Temporarily removed.
v1.1
Direct:
www.holylivingfuck.com/ACS/Kernals/VisionKernel_v1.1.zip
More mirrors coming soon!
v1.0
Direct:
http://k0nane.info/rom/VisionKernel_v1.0.zip
Other:
http://www.mediafire.com/?tihrnrjm6cm177u
http://www.sharebeast.com/7egv5a83g9ab
*Source*
Github
Donations are never required, but always welcome
Donators:
darkfire79
epic4GEE
jbobspants
stir fry a lot
Alright, I'm swapping the twilight zone kernal for this. Thanks for an amazing job once again.
EDIT: Damned conversion from all caps.
ONE POINT FOUR JIGGAWATTS!
ACS FTW.
Great job Thomas. I'm one of those who can't push the processor past 1.2g. Despite that I have had the privilege of testing pretty much all of the Twilight kernels courtasey of Tanimn as well as the Vision kernel. Both are great kernels, and run smooth on my Epic as long as I don't push it to the highest clock. Never had a reboot or lock up pushing my phone with these kernels. Once gain thanks Thomas, I know how much time and energy you go into this kernel and it shows!
dreamsforgotten said:
Great job Thomas. I'm one of those who can't push the processor past 1.2g. Despite that I have had the privilege of testing pretty much all of the Twilight kernels courtasey of Tanimn as well as the Vision kernel. Both are great kernels, and run smooth on my Epic as long as I don't push it to the highest clock. Never had a reboot or lock up pushing my phone with these kernels. Once gain thanks Thomas, I know how much time and energy you go into this kernel and it shows!
Click to expand...
Click to collapse
You the man dreams, much appreciated my friend thank you!
Sent from my SPH-D700 using XDA App
OMGGGGGGG
Thank you !!!!!!!!!
..... So fast that Smartbench force closes
I'll try this in a few days, assuming my phone can handle 1.3 jigga hurtz first. Sure sounds good tho, thanks, I'll report back in a few days.
How is everyone's battery doing running this kernel?
nice I just downloaded this and about to set everything up. Thanks!!
Yea buddy....
Wheres me and dreams name in big red letters for pushing you to release this
Sent from my SPH-D700 using Tapatalk
can this be flashed on eb13?
MysteryEmotionz said:
Yea buddy....
Wheres me and dreams name in big red letters for pushing you to release this
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
If Tom is smart, he'll tell you the same thing I did: ***** please.
blspyro said:
can this be flashed on eb13?
Click to expand...
Click to collapse
Yes.
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
MikeyLee said:
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
Click to expand...
Click to collapse
Long story short: Quadrant sucks. Try a better benchmark.
k0nane said:
Long story short: Quadrant sucks. Try a better benchmark.
Click to expand...
Click to collapse
Any suggestions?
MikeyLee said:
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
Click to expand...
Click to collapse
Also you will get higher scores when you get off that old ass rom with old files and source. So like 4 months ago. Smartbench is good
Sent from my SPH-D700 using XDA App
How are you suppose to test stability of oc for your phone in setcpu? I ran the stress test at 1.3ghz with no errors was there other tests to confirm stability?
Sent from my SPH-D700 using XDA App
jbadboy2007 said:
How are you suppose to test stability of oc for your phone in setcpu? I ran the stress test at 1.3ghz with no errors was there other tests to confirm stability?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Try running something CPU intensive, such as Neocore or an3dbench.
Sent from my SPH-D700 using XDA App
And its resluts will tell me its unstable or will it be laggy or fc or re boot?
Sent from my SPH-D700 using XDA App
Related
ANDROID CREATIVE SYNDICATEpresentsXTREME KERNEL V1.2.0
First of all, I want to put my thank yous up here at the top, so, here they are:
-geniusdog254 - My primary teammate, been helping me every step of way.
-nullghost - One really cool dude. Always on when I ask for help. Git would still be a scary thing if not for him.
-rjmjr69 - Funny, funny dude. Keeps me motivated to keep going
-The Voodoo Team - Your work is awesome!
-My beta testers - You were/are all great. Thanks for helping me with this!
-All the devs across the board - Seriously, you're all a bunch of absolutely awesome people.
-Anyone I forgot - You're all great!
Now, here we go:
THE STANDARD DISCLAIMER
I, DevinXtreme, AM NOT responsible for what happens to your phone, your cat, your house, or anything relating to you! If your phone bricks, OH WELL. Have a nice day.
This kernel has a MixUp kernel base. DI18, blah blah. I deviated once Interactive got working. I also removed the Voodoo color modification. So, there's that.
It is built and designed for Syndicate ROM, which will be out later tonight. Sickest ROM you've ever seen. The version released with the ROM is slightly different, but only for fun's sake
Changelog:
v1.2.0
-Removed the 1.6GHz step. The time machine is gone. Plus, was causing more problems than it was helping.
-Added 1.3GHz step courtesy Herver
-Switched from MPLL to APLL. Smoothness and speed increase. Thanks to nullghost for help on this.
-Added Voodoo color mod, tweaked version, courtesy Herver. I will be maintaining a no-voodoo version. I just haven't yet.
-Tweaked the light sensor, adding a new step and made it not jump to the brightest setting as much. Should save battery and transition smoother. Also pols a little more often.
-Tweaked scaling rules for 1.3GHz. Should scale there less, thus saving battery.
ADDITION: The file ending in 'nv.zip' is a no-voodoo version. The file ending in 'ov.zip' is the version for the original voodoo mod, not the tweaked one.
v1.0.1
-Fixed scaling. Linpack scores and tests work fine now.
-Disabled Carrier IQ in init.rc. Carrier IQ is essentially Sprint spyware. Kernel devs: This is really easy to do. Just comment out the iqmsd lines at the end.
v1.0
-Overclock to 1.6GHz!! Requires SetCPU which is, for some reason, defaulting to performance. Make sure you change it to conservative.
-Default governor without SetCPU is conservative with 200MHz-1GHz steps.
-Removed Voodoo
-Framerate unlocked (78-80fps)
-Built for ROMs with a custom boot. Makes stock boot look like garbage. We're working (still) to fix this.
-Undervolted
KNOWN BUGS:
-In spare parts, if you set the WiFi policy to never sleep, it still sleeps with the screen off. -skandranon314
-Some weird vibration thing going on when 1.6GHz is hit.
NOTES:
Linpack is being strange with this. I'm getting between 9.2 and 9.8 with some REALLY strange numbers. I'll have this fixed this weekend.
SetCPU sets the default governor to performance. If you use it, be sure to change it immediately for battery life.
FOR 1.2
-I recommend 200MHz-1200MHz. Some phones can't reach 1.3GHz safely.
-200MHz - 800/1000MHz is a great setting for battery and you should still have a very smooth experience.
For those who care, I get 1135+ in quadrant.
You can read my source here.
Thanks, guys. I hope you enjoy!
How stable is this??
When is the rom out?
Sent from my SPH-D700 using XDA App
Looking forward to trying this out!
1.6 GHz???????
That's awesome, though I don't think I'll crank it that high.
Is there any advantage to this vs MixUp running at 1.0 Ghz?
spitefulrain said:
How stable is this??
Click to expand...
Click to collapse
I've hit no bumps, neither have my testers.
joshottley said:
When is the rom out?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Give it a couple of hours.
SORRY, HAD TO TAKE IT DOWN FOR JUST A LITTLE BIT. EXPECT AT ~12:45AM MST.
Why take it down? I already downloaded and flashed, was that a bad idea??
I'm running it. Smooth so far.
Sent from my SPH-D700 using XDA App
Dusting the epic off now.
[email protected] said:
Dusting the epic off now.
Click to expand...
Click to collapse
Should have never abandoned dude lol.
Sent from my SPH-D700 using XDA App
Very smooth so far. got 1194 on quad, and 9.2 average on linpack. Wonder how the battery life will fare.
spitefulrain said:
Why take it down? I already downloaded and flashed, was that a bad idea??
Click to expand...
Click to collapse
Nope, just a tweak. Your phone is fine! XD
And I'll be in a movie, so I won't be able to get it up until then. Sorry guys!
DevinXtreme said:
Nope, just a tweak. Your phone is fine! XD
And I'll be in a movie, so I won't be able to get it up until then. Sorry guys!
Click to expand...
Click to collapse
Ok, good. I was worried for a sec
So would you recommend flashing the new one when it's up since you're tweaking it?
Hmm.. something's not right here. I just got 22 fps in Neocore with the removed kernel. What could I be doing wrong?
Edit: Switching from performance to conservative upped my results to 62 fps which is quite respectable.
spitefulrain said:
Ok, good. I was worried for a sec
So would you recommend flashing the new one when it's up since you're tweaking it?
Click to expand...
Click to collapse
Yeah, it'll be a good idea.
what kind of voltage are you giving it to get 1.6 stable? based on what im reading, anything above 1.3/1.4 is pretty much unachievable on these devices and is not really the speed that the device is running thus the unscaled rise in benchmark scores. iv been following hero_over and he couldnt get a stable 1.4 OC although he did get 1.3ghz on stock volts stable..which keeps me wondering if we really can hit 1.6 stable
illogic6 said:
Hmm.. something's not right here. I just got 22 fps in Neocore with the removed kernel. What could I be doing wrong?
Edit: Switching from performance to conservative upped my results to 62 fps which is quite respectable.
Click to expand...
Click to collapse
lol I was gonna say. I'm going good with Neocore as well.
d94 said:
what kind of voltage are you giving it to get 1.6 stable? based on what im reading, anything above 1.3/1.4 is pretty much unachievable on these devices and is not really the speed that the device is running thus the unscaled rise in benchmark scores. iv been following hero_over and he couldnt get a stable 1.4 OC although he did get 1.3ghz on stock volts stable..which keeps me wondering if we really can hit 1.6 stable
Click to expand...
Click to collapse
All of it is on my git. I release my source, as devs should with GPL. The problem is that the fsb isn't scaled properly, affecting the floating point processor, causing low Linpack scores. I'll have it worked out this weekend,
Bummer.... I missed the link the first go around..... Will be waiting
Sent from my SPH-D700 using XDA App
If this was a hero_over post, he'd be in trouble for a teaser post lol... just trolling lol. Had to have a smart ass comment
Quick. And stable so far
Sent from my SPH-D700 using XDA App
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
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!
What started as a modification of the Community Kernel has grown into it's own beast....
As always, what you flash from me has not warranty as you have already borked your manufacturer's anyways.....
Now presenting the Choose your own Core version of Infusion Kernel. Since I couldn't deliver Dual core speeds, I thought that I would deliver 2 different cores!
Both Cores have the following....
BLN
Voodoo Sound 10
Voodoo Lagfix
TinyRCU
Insecure boot (ro.secure=0)
bfq and cfq schedulers
And now for the differences:
Core A has the standard frequencies
100
200
400
600
800
1000
1200
1400
1600
Nothing new here....
Core B however has
104
208
416
624
832
1040
1248
1456
1664
"Nani?" you say? (Nani is Japanese for what)
What I have done here is overclocked the whole CPU/GPU bus from the ground up. Thus making a more user oriented experience and preventing bouncing the GPU all over the place. It's still a beta status (since the 1664 can freeze with large amounts of playing games, but is stable for everyday use), so I would not expect as smooth as the standard 200 MHz bus, but if you feel daring, have fun!
Many thanks to:
Hardcore/Unhelpful: for the HUGE work with the SGS/Infuse processor
gtg465x: for the community kernel
supercurio: for Voodoo of course!
drowningchild/Entropy512: for the help and pushes to the kernel
You: for encouraging me and choosing my kernel!
Last but not least, the Insanity Crew:
crazynfo
gb96
Unknown #1
2sl0w
ookba
motumbo
(If you're not here yet, either the info hasn't went through yet, or I don't know who donated what.... Feel free to drop me a line. )
Previous Versons, known issues, ect.
Previous versions of the Infuse Kernel can be found here.
Known issues:
No CPU states in Core B.
Downloading now! Thanks!
----------
Working great. Loving these funky CPU clock speeds,
Sent from my SAMSUNG-SGH-I997 using XDA App
----------
TehInternetzOozer said:
Quadrant is crashing every few tests I take. When it finishes, I get always over 2300. It seems like it scores more when CPU is hot.
Click to expand...
Click to collapse
Careful with that though, I'm seriously thinking of taking the CPU/GPU from 208 to 206 due to 1664 being too close to my top speed of 1670 and freezing up 15-20 min into a graphically intensive game.... Great benches, with Nenamark 1.0 at 51 FPS (only top frequency and performance/Ondemand), but stability is key.
----------
BLN seems to be working well! Thanks!
Is there any difference between Core A and Infusion 1.8?
I tried to UV -150 and -100 across the board on core-a and got SOD both times anybody else try Uving
Sent from my Samsung Infuse with Infused 1.5.3
VinnyCh4se said:
I tried to UV -150 and -100 across the board on core-a and got SOD both times anybody else try Uving
Sent from my Samsung Infuse with Infused 1.5.3
Click to expand...
Click to collapse
too much uv on lower freqs, i dont even uv 100-200
good work on the kernel
Hmm that makes sense since I don't feel like destroying my phone I put everything back to normal and I'm gonna just wait and see
Sent from my Samsung Infuse with Infused 1.5.3
bedwa said:
What started as a modification of the Community Kernel has grown into it's own beast....
As always, what you flash from me has not warranty as you have already borked your manufacturer's anyways.....
Now presenting the Choose your own Core version of Infusion Kernel. Since I couldn't deliver Dual core speeds, I thought that I would deliver 2 different cores!
Both Cores have the following....
BLN
Voodoo Sound 10
Voodoo Lagfix
TinyRCU
Insecure boot (ro.secure=0)
bfq and cfq schedulers
And now for the differences:
Core A has the standard frequencies
100
200
400
600
800
1000
1200
1400
1600
Nothing new here....
Core B however has
104
208
416
624
832
1040
1248
1456
1664
"Nani?" you say? (Nani is Japanese for what)
What I have done here is overclocked the whole CPU/GPU bus from the ground up. Thus making a more user oriented experience and preventing bouncing the GPU all over the place. It's still a beta status (since the 1664 can freeze with large amounts of playing games, but is stable for everyday use), so I would not expect as smooth as the standard 200 MHz bus, but if you feel daring, have fun!
Many thanks to:
Hardcore/Unhelpful: for the HUGE work with the SGS/Infuse processor
gtg465x: for the community kernel
supercurio: for Voodoo of course!
drowningchild/Entropy512: for the help and pushes to the kernel
You: for encouraging me and choosing my kernel!
Last but not least, the Insanity Crew:
crazynfo
gb96
Unknown #1
2sl0w
ookba
motumbo
(If you're not here yet, either the info hasn't went through yet, or I don't know who donated what.... Feel free to drop me a line. )
Click to expand...
Click to collapse
great work
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Trying B kernel. Running great so far, Oc'd and Uv'd but not using 1664 because of too many phone freezes. I did see other people say that bln is working good but not for me. I wonder why?
Edit: bln working fine battery was really low and so phone was trying to conserve power, I think?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Nice to have BLN again.
Sent from my Infuse 4G
Got a few SOD with this one.
no UV, both on ondemand and conservative 100Mhz 1664.
Thanks for all the hard works so far!
4% overclock seems kinda useless but I tried it anyway. it needs like 100mv more to run stable so I don't think I could get more than 1.7 if I needed to. it seems stable so far.
I wonder why nobody has ever added unhelpful's gpu overclock to hardcores oc/uv meathod. with the buss overclock this could give you 231mhz. maybe 260 (if my assumtions about how it works are correct) I'm not sure if the gpu could run at 250 or 260 but it would be fun to test.
ok. I have a question about the governors. I read that deadline is the best? or no? could somone plz explain the different governors?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I don't like bln how do you disabled it?
Sent from my Samsung Infuse with Infused 1.5.3
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