Database Info

[KERNEL] [GPL] MixUp - Overclock/Undervolt (11/10/2010 - Taco Madness!)

This is based off the latest Samsung kernel source (DI18) with some of my tweaks. Overclock to 1.2Ghz @ 1.25V is maximum. That is 50mV LESS than the voltage given in a stock kernel for 1Ghz!
This kernel is UNBELIEVABLY fast! Average Linpack scores of 9.5+ mflops & Quadrant scores of ~950-1050.
Battery life is great on this beast. Yesterday I ran it all day starting around 8AM, and I didn't hit low battery until 10PM. Thats the furthest I've ever gone, and almost double stock.
Just flash the zip in recovery. I have had no issues with this kernel, nor have any of my testers. This kernel is already included in AOSP Magic & Tha Boss ROM v.2 or above (it was actually made special for Tha Boss at the request of it's maker @KyleCole90). If you're running one of those ROMs you don't need to flash this, unless I release a new version here.
Use SetCPU to set the clock. You'll have to re-do the autodetect (press Menu, Choose Device, Autodetect) for it to decide the new speeds, and you may have to do it a few times. Also, if you flash a different kernel, or update then you'll have to re-detect as well.
Props to @Decad3nce for the BFQ patch from his Hero kernel, @Supercurio for his Voodoo Color mod for the i9000 I just ported it to Epic, Skeeterslint for helping me solve a problem with my ramdisk, @KingKlick92 for a baseline of safe values for voltages from his Vibrant kernel, @Herver for the conservative tweaks, and to Unhelpful on the Captivate forum for his helpful (*rimshot*) source for his Captivate overclock kernel.
If you have any questions or problems (shouldn't be any ) then Twitter me or email me. Also, I don't ask for donations, but if you're feeling generous and you like my work please check out my apps on the Market or send me a donation via the Paypal Donate link in my signature.
-------------------------------------------------------------------------------
Root Issues On Some ROMs:
There are some root issues on some ROMs due to the fact that they still use the old JoeyKrim root. It was never intended to be a permanent root method. Once we got kernel root it became moot. I recommend you ask your ROM dev to fix this, instead of complaining to me
Here's how to fix it if your ROM dev doesn't (just run this from a shell/command prompt, you must have ADB set up):
Code:
adb shell
remountrw
rm /system/bin/playlogo
rm /system/bin/jk-su
mv /system/bin/playlogo-orig /system/bin/playlogo
-------------------------------------------------------------------------------
Changelog:
MixUp-20101110-1036 -- Released 11/10/2010 10:37PM CST:
Added Smartass governor. Still beta. Not default, but available. Similar to interactive, but more responsive & better battery supposedly. Thanks to a dev in the Hero forums whose name I can't remember.
CIFS support
VooDoo Sound support. Still beta.
1.3Ghz & 1.6Ghz OC!
Light & CPU tweaks from Devin
Several more small tweaks I can't remember
This version is beta! I have NOT tested this one at all! I'm running FroYo atm, and I can't test this kernel since it isn't .32. Let me know of any (probably a few) bugs.
MixUp-20101024-847 -- Released 10/24/2010 8:47PM CST:
Switched back to conservative scheduler by default. Interactive is still there, but not default. It'll get set to default when someone fixes interactive.
Patched up to 2.6.29.6 (thanks @Nullghost)
Various scheduler tweaks, backported from newer versions
New BusyBox version
Back camera tweaks, sharpness & saturation upped a notch. I think its better, but if you disagree then take them down a notch in camera settings.
Front cam tweaks. Samsung -- People != blobbish vampires. Sharpness & color upped. No more pale blobs of Play-Doh.
RNDIS! Finally! DevinXTreme got this one goin.
Speaking of Devin, this is now a collab between him & I, with some (credited) kanging from @Nullghost
Optical sensor tweaks. I know, I know, they keep coming. It's good, I promise. I think I FINALLY fixed it.
IMPORTANT! Calibrate your battery after flashing this kernel, else it will decrease! To calibrate, charge your phone all the way (or insert a full battery), wipe battery stats in Clockwork, let it drain to ZERO, plug it in and charge to FULL! Do NOT put in a full battery after the discharge. Your battery should really improve after this.
MixUp-20101017-855 -- Released 10/17/2010 10:05PM CST:
New CPU tables again. Alleviate radio sleep issues. Anything left is just DI18's fault
Actually capped at 1Ghz at boot now, just change with the OC program of your choice
No more no-voodoo version. Voodoo is brightness issue free now, and its too much hassle to maintain two kernels. It may return eventually if I get around to integrating it to my config
Interactive CPU governor added & set as default. Ondemand still available as are the rest.
Fixed lots of config errors, depriving you of EXT4 & BFQ
More optimization for Cortex-A8
MixUp-20101005-809 -- Released 10/5/2010 8:09PM CST:
New CPU Tables (MOAR BATTERYZ!!11!)
More conservative tweaks from Herver (BATTERYZ!!!)
Updated to DI18 sources
New ramdisk
Limited to 1Ghz until changed in setcpu now, better battery by default & more stable for some users. Just up it in SetCPU if you want OCing
Tweaked minimum brightness levels
Screen doesn't fall to minimum brightness automatically until 1% battery now. Used to be 5%. You're welcome
I left up the old DG27 kernel for people who haven't yet upgraded to DI18, just in case the DI18 one causes issues for them
MixUp-20100926-323 -- Released 9/26/2010 3:55PM CST:
Switched to BFQ scheduler. See here for details.
Tweaks to the default Conservative governor. Scales up sooner to avoid hangups and scales down sooner to save battery
Added the Voodoo Color option (thanks @Supercurio for creating it, I just ported it to Epic). There are some issues with it as described at the link. If you don't like it, use the one without it instead of complaining, kthx
Fixed root issues finally, if you experience them you still have the JoeyKrim exploit installed. Bad user.
Undervolted 50 more mV across the board, battery life on this beast is amazing
Added Superuser Permissions app (thanks for the help, Skeeterslint)
adbd now runs as root by default. That means "adb shell" drops you straight to # instead of $
EXT3/EXT4 FS support included in kernel. Do with it what you will.
Changed to a different floating point emulation method that *may* yield better performance
NEON support in the kernel
MixUp-20100921-655 -- Released 9/21/2010 6:55PM CST:
Added Clockwork & ROM Manager support.
Judging from the reports I've heard and things I've seen, I'ma call this one Stoopid Fast. Just cuz it sounds cool
MixUp-20100920-630 -- Released 9/20/2010 6:30PM CST:
adbd now runs as root. This allows adb push to /system. It also enables adb remount to remount /system to RW or RO, but there is something missing from the ROMs that don't allow adb remount yet. I'm working on it.
Small tweaks to voltage table (I think) so possible better battery life on this one, but don't hold me to that. I'll be fine tuning them later on some more.
-------------------------------------------------------------------------------
Source:
My source is now on GitHub.
Stock DI18 Samsung kernel branch here. This is for beginning kernel devs. It's totally stock. Feel free to fork this or download the tree to start your own kernel base.
MixUp VooDoo is here. This has all my changes applied and I will push all my changes to it.
I did not have time to upload my source for the non VooDoo kernel today, I have the local repo done, but I only have access to a high speed connection when I go into town, and I didn't have time to upload this one while I had access. Really though, if you want the source for a non-Voodoo kernel its identical to this, just change the "drivers/video/samsung/s3cfb_tl2796.c" and "drivers/video/samsung/s3cfb_mdnie.c" files with the ones from the stock repo. Everything else is identical.
For devs wondering how I made ADBD run as root, I'm sure you already know how to do this, but if not do the following. Go to your ramdisk, open up default.prop, and then:
Change ro.secure=1 to ro.secure=0
Change ro.debuggable=0 to ro.debuggable=1
Change persist.service.adb.enable=0 to persist.service.adb.enable=1
Then recompile. That's it.
-------------------------------------------------------------------------------
And just to protect me:
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
Overclock kernels carry an inherent risk. You're pushing your hardware further than it's meant to go. Everything should be safe, and I've tested it myself and I trust it on my phone. But that doesn't mean it's perfect.
If *you* screw up and blame me, I will point at you and laugh. Deal with it.

i think i'll wait a bit to see if this is safe to flash

If I flash this kernel will I get those black screens like I did with Heros rom?
Sent from my SPH-D700 using Tapatalk

plmiller0905 said:
If I flash this kernel will I get those black screens like I did with Heros rom?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I don't notice them, but if you got them on his ROM you may well see them here too since its the same kernel. I recommend you set it on OnDemand scheduler with SetCPU instead of Conservative or whatever the default is

Geniusdog254 said:
I don't notice them, but if you got them on his ROM you may well see them here too since its the same kernel. I recommend you set it on OnDemand scheduler with SetCPU instead of Conservative or whatever the default is
Click to expand...
Click to collapse
Ok sounds good...what about having to hurry up and put the phone to sleep on the intial startup to stop the bootloops, do I have to do the same for this kernel as well?
Sent from my SPH-D700 using Tapatalk

plmiller0905 said:
Ok sounds good...what about having to hurry up and put the phone to sleep on the intial startup to stop the bootloops, do I have to do the same for this kernel as well?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Probably. I've gotten away without doing it, but the last couple boots I've had to. I'll build my own kernel later today and see if that fixes it. Just gotta download the Samsung source and set up a build environment for this instead of my Evo

Geniusdog254 said:
Probably. I've gotten away without doing it, but the last couple boots I've had to. I'll build my own kernel later today and see if that fixes it. Just gotta download the Samsung source and set up a build environment for this instead of my Evo
Click to expand...
Click to collapse
Ok I'll wait to flash this then cause trying to hurry up and put the phone into sleep mode at startup is hell. I'll be looking forward to your kernel and thanks for your hard work.
Sent from my SPH-D700 using Tapatalk

This kernel boot loops your phone. Even with a battery pull. I suggest flashing back to the stock kernel with Odin3.

casual864 said:
This kernel boot loops your phone. Even with a battery pull. I suggest flashing back to the stock kernel with Odin3.
Click to expand...
Click to collapse
are you putting it to sleep as soon as it boots??

Good so far thanx for posting it

BopChie said:
are you putting it to sleep as soon as it boots??
Click to expand...
Click to collapse
Even if I do that, whenever I put the phone to sleep it won't turn back on. Forcing me to do a battery pull.

casual864 said:
Even if I do that, whenever I put the phone to sleep it won't turn back on. Forcing me to do a battery pull.
Click to expand...
Click to collapse
Hmm did you put SetCPU at Set on Boot? I've seen that cause issues before. I know that it's working fine for me, although I occasionally have to do the instant-sleep trick on boot, but not always.
I know that it works for me, and it's reported working in the og. Grimey Goods thread as long as you do the instant-sleep. YMMV

so i dont set setcpu on boot or i do?

evoguyfhp said:
so i dont set setcpu on boot or i do?
Click to expand...
Click to collapse
You can give it a shot. I have it set on boot and it works for me but it's caused problems in the past if you set weird freqs. YMMV

Just posted a new version. Yes, I actually compiled this one
Let me know how it works. I'm going to bed. It's late here. I'll check feedback in the morning and respond to them tomorrow after class.
Enjoy

Geniusdog254 said:
Just posted a new version. Yes, I actually compiled this one
Let me know how it works. I'm going to bed. It's late here. I'll check feedback in the morning and respond to them tomorrow after class.
Enjoy
Click to expand...
Click to collapse
changelog?

[email protected] said:
changelog?
Click to expand...
Click to collapse
See OP. No more issues on boot (don't worry about locking and unlocking as soon as it boots anymore) and no wake issues. To make sure you have no wake issues, use the "ondemand" governor. That's the only one I've tested with. Can't guarantee that on conservative or powersave or any of the others. You can change them in SetCPU

Got It.. D'Oh..

PlankLongBeard said:
Only thing I ask for is a update.zip for returning to stock DI07 Kernal. After that all is well.. (BTW.. Thats for the Just In Case) Makes it Easier!
Click to expand...
Click to collapse
clockwork backup?

BopChie said:
clockwork backup?
Click to expand...
Click to collapse
Yeah, will be doing so, I forgot..

Can't overclock my Nexus S

Hey all,
I've tried on multiple occasions now to overclock my phone, using both the Trinity & Netarchy (1.1) kernel, everytime I have done so however it will put me into a bootloop, sometimes not getting past the nexus boot animation or lock screen, I'm sure that I'm doing everything right
1. Wipe data/cache
2. Flash ROM (I've tried Stock, Bionic, CM & Modaco, which I use currently.)
3. Boot
4. Flash kernel
5. Boot
I've no idea what's going on, I've just about given up, perhaps I've been handed a crappy piece of silicon, should have returned it before it was too late
Any help appreciated anyways, peacee.

Instead of flashing the ROM and then immediately applying the kernel, let the phone completely reboot. Then go back into recovery and flash the new kernel. Should work.

I've tried this already dude, probably should of mentioned it in my steps cheers anyhows

risegeek said:
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
Click to expand...
Click to collapse
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?

kenvan19 said:
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
Click to expand...
Click to collapse
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )

risegeek said:
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
Click to expand...
Click to collapse
Have you tried Netarchy 1.2 yet? I've had a lot of issues with CM7, including kernels. Sometimes I would have to just flash the kernel 3 times and then it would work. Now I'm using MoDaCo and it is infinitely more stable. I've noticed the trinity kernels tend to be a little more volatile and hit or miss than the Netarchy one seems to be. If it is really of grave concern to you, if you live in an area where a return would be easily possible and if you are within your return period, return it and try a different slice of silicon

I've actually had this phone since release date, sadly I am out of the return period, I don't really mind all that much, this phone has been amazing coming from a constantly slow and crashing iPhone 3G.
I've just downloaded the new kernel from Netarchy, it seems to address stability issues regarding voltage, which I think it might be. I'll flash it and update this post in a second.
EDIT: Hasn't helped seems to be looping at the Google screen now.

Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.

What the heck? I keep hitting edit but it keeps quoting =( please delete.

sanketrino said:
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
Click to expand...
Click to collapse
Have you tried Netarchy's kernel? A link to his thread is in my sig and it works great for me. It will boot you to 1GHz then using SetCPU (which can be attained for free on XDA, legally, just search for it. The Dev posted it) you can up the clock speed. You should take note however that the Nexus S is damned fast stock. I typically run my phone at 1.2GHz unless I want to show off to my friends and then I bump it up hehe
EDIT: Thank you also for not posting a new thread about this Its nice to see people using the search function!

Blah please delete.

I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.

sanketrino said:
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
Click to expand...
Click to collapse
Odd...for my own testing purposes I've been running at 1.4GHz (testing battery life vs other clock speeds) since yesterday and haven't had a single crash. What ROM are you using?

I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App

sanketrino said:
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm, I used his 1.1v kernel on MoDaCo but never the new kernel so I can't speak to its stability.

Some phones are able to run up to 1.4-1.5 without issues whereas some aren't due to hardware limitations (different batch,build quality etc).
Most however, from what i read in the forums, are able to clock up to 1.3 with either kernels (CFS or BFS, versions types etc) without facing the issue of random rebootings.
Personally, i'm only able to clock up to 1.3. I'll get random reboots if i run smartbench with a 1.4. Quadrant is fine for me at 1.4 though. Was able to get ~3500-3600 scores but in terms of real life situations, i can't tell the difference between a 1.3 to 1.4.

Hey guys,
seems my thread is still alive I flashed the newest version of netarchy the other day, I can manage 1.2-1.3 quite happily atm - I have to manually use SetCPU after each boot though, if I set on boot it will loop
ah well.

[KERNEL/GPL/Sense]ScaryKernel 1.8 super uv/oc/uc/smartass/scary governor/bfq

PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Link to bcnice20's 1.5ghz kernel: http://forum.xda-developers.com/showthread.php?t=941728
If that doesn't work, try flashing over his 1.8ghz kernel(This is what worked for me, bcnice, if you want me to take down this link just let me know.) - http://thebcblends.com/shift/kernels/Sense-1.8ghz-bfq-test1.zip
Table of contents:
Intro
Features/what this includes
Why it's labeled unstable
Disclaimer
Latest kernels
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
Intro: I'm scaryghoul.
What this includes
Swap
BFQ I/o scheduler
Extreme undervolt
Overclocked & underclocked values
HW3D enabled
Sleepers disabled
Smartass governor
New Scary governor!
Tweaked conservative governor
and much more(All of bcnice20's kernel)
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
Scarykernel 1.8 suv - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Suv.zip
Scarykernel 1.8 stable undervolt - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
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 =)
Zdbox - Great toolbox app, just don't let it run in your notifications bar, it's a cpu eater
Setcpu/Nofrills - Apps that help manage your cpu/profiles/ect.(I don't use them but they're pretty okay)
Perfect system or Elixer widgets - Widgets that monitor battery, current, cpu%, cpu speed, and more(Great for battery guru's)
Adw ex - Smoothest/fasted/lightest ratio in a launcher I've seen so far, and least cpu intensive(for me that's a big thing so the cpu scales less)
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
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: How do I flash this?
Answer: You probably shouldn't be flashing one of my kernels if you don't know how(Mine are unstable =P)
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
Then look for items with high amounts of cpu% while the phone is idle.

Changelog
v1.8 - Initial kernel release for sense
Safe voltage kernels
v1.8
Scarykernel 1.8 stable - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Notes:
No I can't take the overclock any higher, I think everyone who's had a chance to take a crack at this source has tried, and going any higher seizes up after a few seconds.
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: bcnice20 - For 99.8% of his 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 see nobody else has chimed in on this kernel yet.. I will install Mikshift tomorrow and report my findings.

Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk

Yeah both versions don't work on mine.

If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.

Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk

ozzie1p said:
Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you flash over bcnice20's kernel?
PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Thanks for clarifying that, I took down the links until we can get this working on several devices.
ozzie1p said:
Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you try both of them over bcnice20's 1.5ghz? Not everyone can handle the suv one.
edit: Links back up! I need some testers to try the fix at the top.

Ya, I flashed right over the top of bc's. Ill try these new ones.
Sent from my PG06100 using Tapatalk

Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..

PaulB007 said:
Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..
Click to expand...
Click to collapse
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<

Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk

Scaryghoul said:
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<
Click to expand...
Click to collapse
Whats the suspected culprit?

ozzie1p said:
Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
PaulB007 said:
Whats the suspected culprit?
Click to expand...
Click to collapse
I don't know so much for the freezes, but I believe that the booting has to do with me using my old voltages, and sense handling things differently than aosp >.<
I'll redo the voltage table later.

Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.

notsointeresting said:
Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.
Click to expand...
Click to collapse
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).

Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
Ah ok that sucks was really hoping for it but I understand thanks for the fast reply

Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
The ndk from google's web site has the toolchains needed to build gb kernel in it. The dl isn't terribly huge.
Sent from my PG06100 using XDA Premium App

[KERNEL][28 APR]LorDMod|SMARTASS|BFSv400|CFS|SLQB|UV|1.99GHz|VOL|V DD|SQ LITE3|

http://forum.xda-developers.com/showthread.php?t=1020637
DON'T USE THE ROM, IT IS OUTDATED AND HAS BEEN DISCONTINUED!
DO NOT USE THE "PUV" (Pinky UnderVolt) VERSION, IT WILL CAUSE YOUR DEVICE TO GET STUCK AT THE SPLASHSCREEN! (POSSIBLY)
I DID NOT MAKE THIS KERNEL, I'M JUST POSTING IT HERE FOR YOU ALL.
THIS IS NOT FOR ANY OTHER ROMS BESIDES CM7 (AND CM7-BASED ROMS) AND MIUI, SO DON'T ASK!
I'm using the UUV CFS version. It is very fast and smooth, I urge you not to have an OC past 1.3GHz as a daily driver, unless you want horrible battery life.
Any option below PUV is safe (UUV, -50mV, and -25mV all work, but every device varies).

i didnt think my phone could ever sh*t itself until i flashed this kernal.

dethpikil said:
i didnt think my phone could ever sh*t itself until i flashed this kernal.
Click to expand...
Click to collapse
i logged in just to ask you to decrypt that message. what does that mean? bad kernal?

vln004 said:
i logged in just to ask you to decrypt that message. what does that mean? bad kernal?
Click to expand...
Click to collapse
lol, iffy kernal. especially with two versions available, its kinda strange testing them and seeing whats best for your phone. flashed the cfs version, and as expected, things seemed evenly smother throughout the phone, yet even at 1.99, there was nothing special or over the top about performance. also, i had a very strange, completely indescribable hiccup after booting.
EDIT
tried the bfs version, and still nothing special. maybe its just me and my miui rom. the 1.99 is cool, but i think im just gunna stay away from this.

Been running his kernels for a couple of weeks, no issues. It is nice to be able to choose from different undervolt versions. Helps battery life a little, around 5%-10% in my experience.

NikolaiT, just FYI this kernel works with Ultimate Droid, which is based on CM7. In case you want to update the OP.

henrybravo said:
NikolaiT, just FYI this kernel works with Ultimate Droid, which is based on CM7. In case you want to update the OP.
Click to expand...
Click to collapse
+1. Running 4.2 cfs -25 version on UD now. 4.0 was the best battery life ever on any cm7 based roms. Haven't tried the puv version yet, but rest assured I will try and report results..
Sent from my Desire HD using Tapatalk

dethpikil said:
lol, iffy kernal. especially with two versions available, its kinda strange testing them and seeing whats best for your phone. flashed the cfs version, and as expected, things seemed evenly smother throughout the phone, yet even at 1.99, there was nothing special or over the top about performance. also, i had a very strange, completely indescribable hiccup after booting.
EDIT
tried the bfs version, and still nothing special. maybe its just me and my miui rom. the 1.99 is cool, but i think im just gunna stay away from this.
Click to expand...
Click to collapse
Hardly "iffy", the differences are stated in the thread or here.
I've been using this kernel with CM7 Final for quite some time now and it's been quite solid.

rasroygbiv said:
+1. Running 4.2 cfs -25 version on UD now. 4.0 was the best battery life ever on any cm7 based roms. Haven't tried the puv version yet, but rest assured I will try and report results..
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Careful, the PUV version softbricked my device. Easily fixable through reflashing your ROM or just a new kernel.
It may not brick yours because some devices can handle it, some can't.

helushune said:
Hardly "iffy", the differences are stated in the thread or here.
I've been using this kernel with CM7 Final for quite some time now and it's been quite solid.
Click to expand...
Click to collapse
+1. Not "iffy" at all.

I've been using it for a while now. At the moment I'm using the latest CFS -25 UV version @ 1305 with the scaling set to Intelligent Donkey (lol) and I actually made it an entire day without charging. That's saying a lot for someone that gets about 12 hours max on a charge.
Sent from my GT-I9000 using XDA App

TheBassman369 said:
I've been using it for a while now. At the moment I'm using the latest CFS -25 UV version @ 1305 with the scaling set to Intelligent Donkey (lol) and I actually made it an entire day without charging. That's saying a lot for someone that gets about 12 hours max on a charge.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'm currently pulling two days at 64% with the same kernel but my CPU settings are 122 min - 1075 max.

So what's everyone recommendations for the best version of this Kernel in terms of both optimum battery and performance?
Additionally... what kinds of CPU governors and max-min frequencies are you using? I've seen a few post what their using in this thread, but I'd like to get some more opinions.

I've been using this Kernel for a few weeks now with no issues. The UUV had some slight hesitation when scrolling so now I'm running 4.3 CFS with the -50 UV and it's absolutely perfect. Fantastic battery life running at 122/1305 MHz with the -50 UV.

i'm using 4.2 and I didn't flash any scripts... is the default -25UV? I'm gonna try 4.3 and -50 script later tonight.
quick question to the group: what is eating up your battery? mine, oddly enough is cell standby and phone idle. i'm using stock radio. in the past (on froyo builds), it's always been screen time.

substance12 said:
i'm using 4.2 and I didn't flash any scripts... is the default -25UV? I'm gonna try 4.3 and -50 script later tonight.
quick question to the group: what is eating up your battery? mine, oddly enough is cell standby and phone idle. i'm using stock radio. in the past (on froyo builds), it's always been screen time.
Click to expand...
Click to collapse
Default is no undervoltage.
Cell Standby and Phone Idle are my two biggest "battery killers" but that's normal operation.

henrybravo said:
+1. Not "iffy" at all.
Click to expand...
Click to collapse
maybe all of you missed the whole miui thing. it says it works great with miui, but my phone seemed very buggy after switching from cattleprods kernel, but you tested it on very different roms than me. it addition, my quadrant score were crap on both types, cfs and bfs, which is completely contrary to the description of one over the other. so yes iffy.

Can anyone explain the difference between the scheduler flavors? I use cfs, but bfq or io?

dethpikil said:
maybe all of you missed the whole miui thing. it says it works great with miui, but my phone seemed very buggy after switching from cattleprods kernel, but you tested it on very different roms than me. it addition, my quadrant score were crap on both types, cfs and bfs, which is completely contrary to the description of one over the other. so yes iffy.
Click to expand...
Click to collapse
I sure did. Pardon.
sugardaddy1979 said:
Can anyone explain the difference between the scheduler flavors? I use cfs, but bfq or io?
Click to expand...
Click to collapse
Check these two posts: Post 1, Post 2. Looks like BFQ is the standard scheduler and VIO is quicker on paper (kind of like BFS vs CFS).

Thanks for the explanation. The bfqhs seems much smoother than the io. I am running it with the uuv.

really ticked, need advice..

okay soo i started off loving my tbolt. i ran bamf ginger remix for months without issues. i then changed to aosp and while i prefer it, many bugs and bad battery life are keeping me away.
so i went back to bamf and while i feel at home, i get alot of lag no matter what kernel i use. i need some advice on what to do and what rom is the fastest/lag free with the best kernel combo.
im dying here guys.
as far as setcpu settings i usually use ondemand or interactive no higher than 1228/245.

fixxxer2008 said:
okay soo i started off loving my tbolt. i ran bamf ginger remix for months without issues. i then changed to aosp and while i prefer it, many bugs and bad battery life are keeping me away.
so i went back to bamf and while i feel at home, i get alot of lag no matter what kernel i use. i need some advice on what to do and what rom is the fastest/lag free with the best kernel combo.
im dying here guys.
as far as setcpu settings i usually use ondemand or interactive no higher than 1228/245.
Click to expand...
Click to collapse
As far as I can tell, the Ziggy kernel in the latest Gingeritis3D is the smoothest. Might be something newer in the synergy ROM, but I'm getting good battery life and things are nearly lag-free.

I am running OMFGB right now, and while I do prefer AOSP roms, the battery life isn't great. I have an extended battery so the battery life for me isn't an issue.
I agree with the previous post in regards to Gingeritis 3D. I had version VII installed, deleted almost all sense out with Tibu and used ADW EX. It was nice having some sense, lockscreen, pulldown, but that was all I really liked about sense. I oc'd to 1.4 and thought it ran great with excellent battery life.
Sent from my ADR6400L using Tapatalk

I haven't messed with uberBAMF yet. I understand it's a work in progess. I'm not sure what kernel it uses, but it might be worth giving a go. I'd love to think it's NOT a Ziggy or Imoseyon kernel just because I think Sense kernels NEED a LOT more attention.

im going to stick to bamf ginger remix until the theory 1.3x rom goes final. the newest ziggy kernel in synergy isn't very good imo, very laggy. i just extracted the gingeritis one and it's a kernel build from july, it's one of the better ziggy kernels. you know, the one from my thread that was removed. ill stick to it for the time being.
i just wish there were more stable aosp roms. no offense to cm7 or the devs, it's just not 100% yet and the battery life is ****, at least for me.

fixxxer2008 said:
im going to stick to bamf ginger remix until the theory 1.3x rom goes final. the newest ziggy kernel in synergy isn't very good imo, very laggy. i just extracted the gingeritis one and it's a kernel build from july, it's one of the better ziggy kernels. you know, the one from my thread that was removed. ill stick to it for the time being.
i just wish there were more stable aosp roms. no offense to cm7 or the devs, it's just not 100% yet and the battery life is ****, at least for me.
Click to expand...
Click to collapse
The Ziggy's in Gingeritis3D is different than the Ziggy's in the older Gingeritis. The clock settings and smartass parameters are different. I think part of the reason that Ziggy kernel is as lagy as it is sometimes is because of his smartass governor parameters. I think if they were tweaked to be a little less stingy the phone might be much snappier. As it is, that kernel seems VERY reluctant to creep past 1 GHz, like the load requirement for stepping up is fairly high. I think it's ramp down is just a little too aggressive, and the period of load polling too long as well.

loonatik78 said:
The Ziggy's in Gingeritis3D is different than the Ziggy's in the older Gingeritis. The clock settings and smartass parameters are different. I think part of the reason that Ziggy kernel is as lagy as it is sometimes is because of his smartass governor parameters. I think if they were tweaked to be a little less stingy the phone might be much snappier. As it is, that kernel seems VERY reluctant to creep past 1 GHz, like the load requirement for stepping up is fairly high. I think it's ramp down is just a little too aggressive, and the period of load polling too long as well.
Click to expand...
Click to collapse
i meant i pulled it from gingeritis3d. that's the kernel your running, it's the one i posted last month.

fixxxer2008 said:
i meant i pulled it from gingeritis3d. that's the kernel your running, it's the one i posted last month.
Click to expand...
Click to collapse
You sure? This one just seems smoother.

loonatik78 said:
You sure? This one just seems smoother.
Click to expand...
Click to collapse
almost 100%

fixxxer2008 said:
almost 100%
Click to expand...
Click to collapse
I'm not sure it is. I know that one didn't go up to 2GHz. It's definitely a similar build. The up_threshold on the smartass on that one you extracted seemed even more aggressive than this one. I had issues typing with it if I set the min_freq too low. I run this one at 122MHz without a problem.
Edit: Actually, I'm sure it's not. The one you extracted didn't have the camera fix for the new base Chingy used for beta 6 and 7.

loonatik78 said:
I'm not sure it is. I know that one didn't go up to 2GHz. It's definitely a similar build. The up_threshold on the smartass on that one you extracted seemed even more aggressive than this one. I had issues typing with it if I set the min_freq too low. I run this one at 122MHz without a problem.
Edit: Actually, I'm sure it's not. The one you extracted didn't have the camera fix for the new base Chingy used for beta 6 and 7.
Click to expand...
Click to collapse
its from the same build date. its possible some other tweaks were added though. anyways im still open for suggestions guys.

fixxxer2008 said:
its from the same build date. its possible some other tweaks were added though. anyways im still open for suggestions guys.
Click to expand...
Click to collapse
Wouldn't be surprised knowing how he works.

I would recommend trying the uber bamf preview 3. I tested out preview 1 and it was by far the smoothest feeling ROM I've used and it also gave me the greatest battery life I've ever had on my Thunderbolt. They've fixed a few bugs since preview 1 so I'm sure it's even better now. It includes a stock kernel by the way.
You may also want to try the latest nightly Synergy ROM, it's what I'm on now. Performance has been pretty good and battery is okay. I have SetCPU at 1344/245 with lagfree.

DRGilroy said:
I would recommend trying the uber bamf preview 3. I tested out preview 1 and it was by far the smoothest feeling ROM I've used and it also gave me the greatest battery life I've ever had on my Thunderbolt. They've fixed a few bugs since preview 1 so I'm sure it's even better now. It includes a stock kernel by the way.
You may also want to try the latest nightly Synergy ROM, it's what I'm on now. Performance has been pretty good and battery is okay. I have SetCPU at 1344/245 with lagfree.
Click to expand...
Click to collapse
not a huge fan of synergy, i may give uber a whirl.

Go back to the stock released ROM (rooted, if you prefer to make things easier). That should be the baseline for everything.

mike.s said:
Go back to the stock released ROM (rooted, if you prefer to make things easier). That should be the baseline for everything.
Click to expand...
Click to collapse
naw... not into stock roms much but thanks.

fixxxer2008 said:
not a huge fan of synergy, i may give uber a whirl.
Click to expand...
Click to collapse
To make things a little easier for you...
uber-BAMF

fixxxer2008 said:
naw... not into stock roms much but thanks.
Click to expand...
Click to collapse
Then quit'yer'*****in. Throw a bunch of modified stuff into the mix, and you get what you pay for.

mike.s said:
Then quit'yer'*****in. Throw a bunch of modified stuff into the mix, and you get what you pay for.
Click to expand...
Click to collapse
WTF? You for real?

fixxxer2008 said:
okay soo i started off loving my tbolt. i ran bamf ginger remix for months without issues. i then changed to aosp and while i prefer it, many bugs and bad battery life are keeping me away.
so i went back to bamf and while i feel at home, i get alot of lag no matter what kernel i use. i need some advice on what to do and what rom is the fastest/lag free with the best kernel combo.
im dying here guys.
as far as setcpu settings i usually use ondemand or interactive no higher than 1228/245.
Click to expand...
Click to collapse
Something is happening here, but you don't know what it is, do you, Mr. Jones?