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..

[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

6210 kernel

I've finally managed to get the 6210 kernel to compile AND work with the standalone kernel modules that samsung didn't bother to provide source for (ar6000 and j4fs.) It seems that the source on opensource.samsung.com uses different config flags than the source they used to compile for the shipping tablet.
The question is: Now that I can recompile it, what do I do with it? Well, I'll think about that and come up with some interesting answers. Probably a few efficiency tweaks, modifying the init.rc to allow for init.d parsing, and.. well, I don't know what else.
(I can find the source for the ar6000 adapter and j4fs, but I was extremely determined to get things working with the existing modules. I'm stubborn.)
Take care
Gary

Good luck gary!

Can you get overclocking enabled?
Sent from my GT-P6210 using xda premium

excellent job gary. bravo!

Excellent work. I might try my hand at this kernel development stuff. I did a lot of work with pascal a number of years back. Some c on the side. I might be able to add features that others have pioneered? We'll see... time is the enemy I believe. Sorry about the ramblings.
Sent from my GT-P6210 using xda premium

I've slimmed down the kernel a bit and also added support for init.d scripts (of course with no so-called ROM devs to take advantage of that, it's useless.)
I'm actually more interested in undervolting support than overclocking, but will add both around the same time. I should be able to post the kernel for the 6210 (only) sometime before the end of this year (local time.)
Take care
Gary

posted in the development section

garyd9 said:
I've slimmed down the kernel a bit and also added support for init.d scripts (of course with no so-called ROM devs to take advantage of that, it's useless.)
I'm actually more interested in undervolting support than overclocking, but will add both around the same time. I should be able to post the kernel for the 6210 (only) sometime before the end of this year (local time.)
Take care
Gary
Click to expand...
Click to collapse
Hey, users can throw stuff in init.d themselves!
(although most are too lazy to do so...)

i would like my ext partition on my sdcard to mount itself if you can do that gary! thanks and good luck!

I tried the kernel on mine and I don't like it. It's kinda choppy now going from page to page. How can I revert back to the stock kernel?

deezomaxima said:
I tried the kernel on mine and I don't like it. It's kinda choppy now going from page to page. How can I revert back to the stock kernel?
Click to expand...
Click to collapse
Please find the thread(s) in the dev subforum referring to ODIN and/or stock firmware.

Thanks Gary. Not sure if it's just my Tab but just being honest about what I was seeing.

deezomaxima said:
Thanks Gary. Not sure if it's just my Tab but just being honest about what I was seeing.
Click to expand...
Click to collapse
No problem.

Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!

maxofmin said:
Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!
Click to expand...
Click to collapse
I'm not familiar with that, but I'd be happy to investigate it. I'll add it to my 'todo' (but no promises on a timeline.)

maxofmin said:
Could you add tun module to support OpenVPN? The default kernel doesn't have that module so that OpenVPN doesn't work. Thanks!
Click to expand...
Click to collapse
Actually... It appears that 'tun' is already compiled into the kernel (directly - not as a module.) You should be able to use it without loading "tun.ko".
Can you please check this out?
Gary

Gary,
Correction on my assessment of your kernel. It's fine.
I'm back to stock and it's still doing what it was doing at moments and I've come to 2 conclusions:
1. The email widget I'm using on one page with a few icons
2. The Facebook widget I'm using on another page.
Pages with just icons seem to run fine.
Now I saw in your first post that you said you weren't into benchmarking for speed but have you benchmarked for battery life over the stock settings?

deezomaxima said:
Now I saw in your first post that you said you weren't into benchmarking for speed but have you benchmarked for battery life over the stock settings?
Click to expand...
Click to collapse
Only very non-scientific ones. (It's extremely difficult to ensure that exact same number of messages are pushed to my phone in a given period of time, that various forms of wifi interference are causing the same increases in power, etc.) That being said, I'm getting slightly better time on my battery with wifi set to "always on" compared to what I got on the stock kernel with wifi set to "never turn off when plugged in." (tablet was left in range of an AP in both cases.) I drop perhaps 5% in a 16 hour period with little to no screen time.
However, I'm also undervolting a bit with the custom kernel (values used are posted in another thread in this subforum), and have no active widgets beyond a single WX one that polls once/hr. I also changed the governor on my own to conservative at default settings (which saves a bit of battery as well.) Default for the kernel is ondemand which gives slightly better "snappiness."
Take care
Gary
Does it make a huge difference? Of course not. The undervolting is probably the only thing making much of a difference at all.

BTW, some of the tradeoffs between ondemand and conservative can be reduced by making some tweaks to the conservative governor:
https://github.com/Entropy512/linux_kernel_sgh-i777/commit/3b92eb76e72bbaa88aa8d87d306d1b61c9485912
Should be easy to port to .36
Main thing there if you don't want to change defaults is the stuff that reduces the minimum polling interval - the MIN_SAMPLING_RATE_RATIO lines - everything else is just tuning more aggressive (performance-tuned) defaults.

Thanks for the reply Gary.
So, I'm back on your kernel and installed SetCPU. I'm still messing with the settings to see what I get as far as battery life. I've had my Tab off charge since 7am this morning and it's now 1320 and Juice plotter is showing I have 67 hours of run time (95%) as opposed to seeing numbers in the 40s before hand. My device now wakes up out of sleep as it should instead of going into a non-responsive state sending me to reboot the whole device.
Everything is looking good now.

Public Beta testing now open for WildKernel

As some of you may know, I've been working on a custom kernel for ICS/JB and its about done (for a first release). Current kernel features include: (If feature begins with a * then check below for more information)
Compatible with all AOSP ICS & JB roms
rebased to CAF Linux 3.0.40 kernel
Built in Low-memory killer w/ Fugeswap (as seen in the v6 Supercharger)
Optimized ram usage/handling (Swap & Zram)
Increased Wi-fi connectivity range
*Low & High power Wi-fi scaling steps
*Badass Governor (Default)
Lazy Governor
Imported Snapdragon optimizations used by the Sensation (Thanks Romanbb)
Lagfree Governor
Fast charging for unknowns
HIGHLY Tweaked for the perfect battery life and performance
Updated Bluetooth code from CAF
V(R), simple, deadline, noop, and CFQ I/O schedulers
*Ondemand & Intelli(gent)demand Governor
Stable Undervolting of the CPU
increased SDcard readahead speed
Tweaked Flashlight
Added more clock steps to the GPU for compatibility with low power browsing and GPU OC @ 320 mhz
I think 6 testers should be enough for now, thanks for participating
If you wish to join in this this beta testing please feel free to shoot me a PM or hit me up on GTalk @ [email protected]
You may find my source hosted @ Github
Current testers (in order of request sent):
AgentCherryCola
sino8r
onebornoflight
phone77
jjbz
WeekendsR2Short
CoNsPiRiSiZe
More information:
Badass Governor: This governor has built in profiling (like used in SetCPU but not as battery & Ram consuming). This is also the default and highly recommended governor. This governor features a 3 phase system CPU profiling system. This will change your CPU speed based on usage. This saves a lot of power as your speed doesn't just keep at one clock no matter how much your using you phone. A similiar profiling system is also used for the GPU and such.
Ondemand and Intellidemand Governor: Intellidemand is based off the Ondemand governor but features a 2 phase CPU profiling system with some added tweaks.
Wi-fi Low and High power scaling steps: This is a feature that will determine whether to use High or low power voltages on the Wi-fi chip to save battery. eg: Wi-fi will be turned to low power when idle or screen off. Wifi will be turned to high power when actively in use or in progress of a download. Take note that high power wi-fi voltage isn't necessarily "High" power but more of just "Stock HTC" power.
Thanks:
TeamDS
Strapped365
faux123
showp1984
RomanBB
and any others I may have missed

I'll test out this Kernel. I'll test CM9, AOKP, and MIUI.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

I'm ready!
ditto dude... thanks!

Il do it!
::Respect::

So how's the kernel testing going out guys! This looks really promising
Sent from my myTouch_4G_Slide using Tapatalk 2

Ok I think thats enough testers for now, Testing will begin soon just making some final adjustments

Quite psyched to check this out!
Sent from my HTC MyTouch 4G Slide using xda app-developers app

sorry for the delay, Ive been troubleshooting battery issues which started after upgrading past 3.0.30, im thinking about downgrading back to that version to see if the problem persists

xmc wildchild22 said:
sorry for the delay, Ive been troubleshooting battery issues which started after upgrading past 3.0.30, im thinking about downgrading back to that version to see if the problem persists
Click to expand...
Click to collapse
Battery issues are nothing new with the latest kernel commits. Just take a stroll through the CM9 thread
Honestly, I've seen better battery life on the old 2.6 kernel

gtmaster303 said:
Battery issues are nothing new with the latest kernel commits. Just take a stroll through the CM9 thread
Honestly, I've seen better battery life on the old 2.6 kernel
Click to expand...
Click to collapse
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::

CoNsPiRiSiZe said:
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::
Click to expand...
Click to collapse
Yea, I don't know how you do it... Possibly a fluke, or just your setup

CoNsPiRiSiZe said:
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::
Click to expand...
Click to collapse
Then I'll make sure to include the "Conspirisize ultra performance" version

Soooooo how about that kernel release for all of us (;
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

I think his Kernel was lost in Goo.Im crash.
::Sense 4.0::

I believe he had most of it on Github?

WeekendsR2Short said:
I believe he had most of it on Github?
Click to expand...
Click to collapse
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE

strapped365 said:
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
I had 30+ commits that I were going to push to git fixing a lot of problems but my hard drive fried at the same time goo went down. (I have a live network backup of my hard drive hosted on goo) So I lost those commits.

strapped365 said:
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
Well CRAP! :crying:
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
..
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
xmc wildchild22 said:
I had 30+ commits that I were going to push to git fixing a lot of problems but my hard drive fried at the same time goo went down. (I have a live network backup of my hard drive hosted on goo) So I lost those commits.
Click to expand...
Click to collapse
..

[Kernel][ICS] TFQ Scorched Kernel ICS v1.0.29 (2012-12-21)

Team Fah-Q Presents...
Scorched Kernel for Blaze ICS v1.0.29
Built with the Linaro Toolchain v4.7, the purpose of this kernel is to fix bugs, add features, add performance, and hopefully save some battery where possible. However, battery life will most likely not be as good as stock, since the device is overclocked and DVFS (dynamic frequency and voltage scaling) is turned off. I have done my very best to squeeze every ounce of battery life out of this device.
It includes a brand new CPU Governor called Scorched, developed by me and based on the lagfree governor. It focuses on saving power and reducing the usage of the higher CPU frequencies unless necessary, while still keeping responsiveness and performance intact.
The kernel should work with any ROM that is derived from the stock Samsung ICS release IMM76D.LH5, however I recommend using it with the Tweaked ROM, as that is what I develop it against.
This is a kernel several months in the making. Hope you like it
It is STRONGLY advised to do a full nandroid backup in CWM before installing the kernel,
as the installer will overwrite kernel modules in /system/lib/modules. You've officially been warned
NOTE: This thread is reserved for bug reports, logcats, and other development related discussion. General discussion, questions, etc should be posted in this thread​Kernel Features
IO Schedulers:
zen (NEW)
vr (NEW)
sio (NEW)
deadline
cfq
noop
CPU Governors:
scorched (NEW)
lagfree (NEW)
interactive (NEW)
ondemand
conservative
userspace
powersave
performance
Other Features:
Overclocked to 1.72 GHz
Voltage control support
Support for init.d scripts, added automatically during installation of the kernel.
ZRAM support with Google Snappy compression, with a default size of 64 MB.
Other tweaks and fixes, too minor to note. Check the Google Code site if you're interested.
Credits/Thanks
withere2 - Endless testing, testing, ideas, more testing, scripting support, more testing. Did I mention testing?
erikmm - Pulling me into kernel development
showp-1984 - Lots of initial help getting off the ground with kernel development
faux123 - Some source code from his Samsung GS2 github repo

Changelog and Downloads
Changelog and Downloads
2012-12-21 - Version 1.0.29 - tfq-scorched-kernel-ics-1.0.29-signed.zip
ADB now runs as root. Not as easy as you might think to do it properly...
2012-12-17 - Version 1.0.22 - tfq-scorched-kernel-ics-1.0.22-signed.zip
Initial public release of kernel
Resolved issue with battery life. Standby time should be almost double that of version 1.0.20
The source code for this kernel can be found on Google Code:
http://code.google.com/p/scorched-kernel-t769-ics/
All previous release versions of the kernel can be found on the Scorched Google Code site
http://code.google.com/p/scorched-kernel-t769-ics/downloads/list

FAQ
FAQ
What is the Scorched CPU Governor?
The Scorched CPU governor is rather similar to the lagfree governor both in its source code and its purpose. The difference is that while lagfree seeks to give performance-on-demand by increasing immediately to the maximum CPU frequency, Scorched jumps immediately to a mid-point frequency and then gracefully increases or decreases the CPU frequency as required. This provides both performance-on-demand as well as extended battery life.

multi core support
is there anyway of changing it to were we have multi core support ( in regards to offlining 2nd 3rd etc cores ) to save battery by chance cause some other kernels ive tested have that capability if i knew how to do so myself ( im slowly learning with massive reprocussions lol ) but would that be possible at all

awesome finally some scorchness for the blaze

merwin said:
Changelog and Downloads
2012-12-17 - Version 1.0.22 - tfq-scorched-kernel-ics-1.0.22-signed.zip
Initial public release of kernel
Resolved issue with battery life. Standby time should be almost double that of version 1.0.20
The source code for this kernel can be found on Google Code:
http://code.google.com/p/scorched-kernel-t769-ics/
All previous release versions of the kernel can be found on the Scorched Google Code site
http://code.google.com/p/scorched-kernel-t769-ics/downloads/list
Click to expand...
Click to collapse
Many thanks for your hard work.
However I've been using this kernel for a couple of days now with tweaked 2.1, and deleted battery stats but my battery life is really poor.
I've left the system essentially in standby for several full charge cycles but I only get 10 hours with next to no use, if lucky.
With stock kernel and Blz3r v3 and with heavy usage I would easily get 14 hours.
I'm still going to keep on using it and characterizing it and hope it gets better.
Sent from my SGH-T769 using xda app-developers app

theshowman said:
Many thanks for your hard work.
However I've been using this kernel for a couple of days now with tweaked 2.1, and deleted battery stats but my battery life is really poor.
I've left the system essentially in standby for several full charge cycles but I only get 10 hours with next to no use, if lucky.
With stock kernel and Blz3r v3 and with heavy usage I would easily get 14 hours.
I'm still going to keep on using it and characterizing it and hope it gets better.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Not sure what to tell you. I've attached an image with my stats on it. That's 7 hours, mostly standby, dropping 30%, with wifi calling, exchange sync, gmail sync all on.
And this is more of a general Q&A thread topic also

soldier1184 said:
is there anyway of changing it to were we have multi core support ( in regards to offlining 2nd 3rd etc cores ) to save battery by chance cause some other kernels ive tested have that capability if i knew how to do so myself ( im slowly learning with massive reprocussions lol ) but would that be possible at all
Click to expand...
Click to collapse
Please ask this in the general questions thread.

Using just CPU0
soldier1184 said:
is there anyway of changing it to were we have multi core support ( in regards to offlining 2nd 3rd etc cores ) to save battery by chance cause some other kernels ive tested have that capability if i knew how to do so myself ( im slowly learning with massive reprocussions lol ) but would that be possible at all
Click to expand...
Click to collapse
This app will let you use 1 core, both or link them together as one:​
PC Link: https://play.google.com/store/apps/...sMSwyLDEsInJzLnBlZGphYXBwcy5LZXJuZWxUdW5lciJd​

nickmcminn60 said:
This app will let you use 1 core, both or link them together as one:​
PC Link: https://play.google.com/store/apps/...sMSwyLDEsInJzLnBlZGphYXBwcy5LZXJuZWxUdW5lciJd​
Click to expand...
Click to collapse
In my own testing, I have found that it is often worse to turn off a core completely, than to aim for a lower clock speed on both active cores. My theory is that the increase of speed with multithreading speeds up processing over the single corr, thus staying at a higher frequency for less time.
Just a personal observation.

I'm New
I'm sorry if i sound like an idiot, but Does this work on the stock ICS rom? I'm rooted btw
and does it support undervolting?

Thank you, Very stable and responsive kernel. Only issue I've had after installing the kernel is that when I try to send an app from play.google.com to my phone it doesn't show up. I can still install from within the phone itself just not website to phone, not sure if it's related to this Kernel or not but started after flashed it.
Again I'm not 100% positive that it's related so will need to do some more testing...

techclan said:
Thank you, Very stable and responsive kernel. Only issue I've had after installing the kernel is that when I try to send an app from play.google.com to my phone it doesn't show up. I can still install from within the phone itself just not website to phone, not sure if it's related to this Kernel or not but started after flashed it.
Again I'm not 100% positive that it's related so will need to do some more testing...
Click to expand...
Click to collapse
Looks like the problem with the apps not getting pushed to the devide was a stuck process, my "smooth calendar" was at 83% cpu utlization and app pushes were being halted.

Android ICS 4.0.4 UVLH5 + Scorched Kernel ICS v1.0.29

techclan said:
Android ICS 4.0.4 UVLH5 + Scorched Kernel ICS v1.0.29
Click to expand...
Click to collapse
That's about right for the benchmark. I'm considering going a slightly different route with the kernel that may reduce performance a bit but should up battery life significantly.
Sick 2 year old at home so I've had limited time to play, unfortunately.

merwin said:
That's about right for the benchmark. I'm considering going a slightly different route with the kernel that may reduce performance a bit but should up battery life significantly.
Sick 2 year old at home so I've had limited time to play, unfortunately.
Click to expand...
Click to collapse
Hope your 2 year old gets well soon. Yes sacrificing a bit of performance to up the battery is definitelyitly worth it. Also seems like your scorched will outilizelize 384 and above, not sure how much battery can be saved but basic call functions and such can perfectly work on 192Mhz

roms
does this work on pacman rom 4.1.2 for the blaze please respond quickly my current kernel is random rebooting and this worked when i was on stock rom

No its for ICS
Sent from my SGH-T769 using xda premium