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

[KERNEL] 1.6ghz - For Android 3.01

06-19-2011
The above has a max clock of 1.6ghz.. It has all the regular features included prior to this release - underclocking when it gets too hot.. various non-cpu overclocks and so on.. and unlike previous kernels.. its pretty damn stable.. I've tried to crash it. I can't.. Help me crash it. Don't help me crash it if you're on 3.1 - because this won't work with 3.1.. Ok? alright then.
#older stuff below
This lovely little kernel has a max of 1.646 (because 1.7ghz will run for about 30 seconds). But it also has been setup to set the max clock to 1.2ghz (temporarily) when temps get above 42 deg C.. For people using setcpu, I do not know if it sets only cpu0 to the desired freq (and presumes cpu1 will follow).. but it seems that you need to set both to the desired freq, otherwise it'll use the higher of scaling_max_freqs (cpu0,cpu1 - thus two scaling_max_freqs) and ignore the value you just set.. doesn't make sense? yeah.. ok..
if you set cpu0 to 1504
then you set cpu1 to 1504
then you set cpu0 to 1000
... scaling_max_freq is set to 1000 for cpu0, yet cpuinfo_cur_freq will show higher than that (under load obviously)..
just based on my experience.
Just because the max is 1646... doesn't mean you should complain when/if its unstable.. Well, you can.. but you really don't have to.
This is for 3.01.. Im not sure I trust 3.1 yet. ..
Here.. this has sys/avp/vde/gpu/pclk and of course cpu, overclocked. I ls'd the modules directory for you and got this..
bcm4329.ko cifs.ko ntfs.ko scsi_wait_scan.ko tun.ko
I don't know what it means.
If you have problems with netarchy's kernel and you don't with this.. You're probably insane and making stuff up...
This not my first compile. I run my own custom kernels on Gtab, xoom, G2, and HD2.. All pretty spicy with the overclocks..
This may cause some incontinence.. only some.. its ok tho. perfectly natural.
this is the first time I've posted any kerzanels..
http://www.github.com/ibladesi/
get your ultra verbose changelog there buster.
order
order
order

Omg this **** is smoking hot
Sent From My Evo

I'll give it a go.
Right after I nandroid.
And flash the new CWM >_>

Have you got a link to your source code ?

DAMN!!!! very nice

would love to see some benchmarks and improvements reviews

Well, I flashed this on my TF earlier today (running Prime 1.3r2)
I got Linpack scores of 63.3+ and a first run Quadrant of 4339. However, my device froze 3 times within half an hour of flashing it. I cleared the cache several times pre and post flashing. My device even froze on the initial boot after flashing the kernel, so I guess it isn't a thing of speed instability. There must be something else. I will try to reflash it later and see if this behavior continues.

egzthunder1 said:
Well, I flashed this on my TF earlier today (running Prime 1.3r2)
I got Linpack scores of 63.3+ and a first run Quadrant of 4339. However, my device froze 3 times within half an hour of flashing it. I cleared the cache several times pre and post flashing. My device even froze on the initial boot after flashing the kernel, so I guess it isn't a thing of speed instability. There must be something else. I will try to reflash it later and see if this behavior continues.
Click to expand...
Click to collapse
Not really. The init.ventana.rc script within the ramdisk sets the max frequency to 1.4 - so if there were freezes in android, there could be freezes when android starts to boot - roughly around the time adbd starts... Are there any kernel logs (ramdump files on your internal "sd")
Strange how it would run thru benchmarks, yet be unstable. Was this at 1.504?

Blades said:
Not really. The init.ventana.rc script within the ramdisk sets the max frequency to 1.4 - so if there were freezes in android, there could be freezes when android starts to boot - roughly around the time adbd starts... Are there any kernel logs (ramdump files on your internal "sd")
Strange how it would run thru benchmarks, yet be unstable. Was this at 1.504?
Click to expand...
Click to collapse
Yup, I set it at 1.504 and it allowed me to run Linpack a few times before crashing. Quadrant allowed me to go 1 full run and about 1/3 of the next before it crashed. I found a ramdump.log file in there. Is this the one you need?

@Blades,
Here you go...

Definitely will try this after work today! thanks for the new kernel!
HTC Thunderbolt & ASUS Transformer Rooted!

wow, what a crazy kernel

Thanks I'm going to give this a go with the modaco rom

Is there a way we can schedule the 1.5ghz to kick in? seems like it crashes few minutes after boot because some other app are still loading. I've set my setcpu to 1ghz max and reboot, everything loads perfectly then after 5 minutes i revert it back to 1.5ghzl, overnight my TF doesnt have any problem.
This morning i restarted my asus just to experiment if it will boot normaly while im in 1.5ghz max and 200+mhz min. It crashes few minutes after reboot.

45 minutes of Pocket Legends and no signs of slowing down at 1.5GHz!
Sent from my Transformer TF101 using XDA Premium App

@hurrpancakes: Pls try 1080p mp4 high bit rate, hope that it'll stable as well

kenblat said:
@hurrpancakes: Pls try 1080p mp4 high bit rate, hope that it'll stable as well
Click to expand...
Click to collapse
I believe high profile HD video performance is more an issue of HC 3.0 not taking full advantage of Trega2 hardware acceleration and until HC 3.1 we won't see much improvement. Overclocking will only help so much...

plz delete

new kirnizial up

Blades said:
new kirnizial up
Click to expand...
Click to collapse
Reserve 128mb of ram insted 256mb. You mean now we have more user ram avaiable for app?

[KERNEL][FROYO][OC][08-08-11]PeanutButta Jelly Time - OTB Edition

For the people that want overclocking, here is your chance. I took my standard voodoo kernel, and put in the stuff needed to overclock it. Thanks to nemesis2all and his OTB kernel from the Fascinate for the code needed to get this to work. Also, use extreme caution when using the higher clock speeds. The stock "max" voltage for the CPU is 1300mv, and 1500MHz and 1600MHz are both at 1500mv, so it's heavily over-volted at the top end. By default, the system will boot to 1000MHz and you need to set the speeds you want in Voltage Control App. I don't personally use this because I think overclocking is useless, so any bug reports need as much information as possible, or they will be dismissed and not looked into at all. If you run into an issue with the system locking up, odds are that you have undervolted to much for a given clock speed. Other than that, you're on your own. Same FAQ applies as the regular PBJ kernel, so look there until I get a chance to post it here as well.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0808
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB Storage in recovery
0730
Updated CWM binary
Custom boot animation support
0709
Voodoo Sound V10
0615
Overclocking - Use Voltage Control App to adjust clocks and voltages
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Smooth out boot animation
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.

FAQ Placeholder

2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts

Undervolted and running ok so far.
Sent from my SCH-I510 using XDA App

Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!

ZeppelinJ0 said:
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.

will2live said:
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.
Click to expand...
Click to collapse
Well it's definitely enabled. I just must have set the CPU settings poorly because this thing is crawling right now, I can't even scroll through the app drawer!
I've been trying to CWM back to the other PBJ kernels however my phone hangs on reboot, I'm guessing because those need to be flashed with Odin.

asenduk said:
2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts
Click to expand...
Click to collapse
I wish I knew what I was doing wrong.. running at 1.4 and my quadrant scores are exactly the same.... not that it really matters but still...

imnuts said:
. I don't personally use this because I think overclocking is useless.
Click to expand...
Click to collapse
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.

das7771 said:
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.
Click to expand...
Click to collapse
Use a program like CPUSpy that shows you the clock speed stats of your phone. >75% of the time, it will likely be in 400MHz or less, this probably approaches >90% if you say 800MHz or less, especially if you are not a heavy user. At that point, why overclock your phone? To get the overclocking stable, you need increase voltages across the board, and despite undervolting, you'll never get the same power usage as you can with a non-overclocked kernel as some of the voltage changes you can't revert. My opinion is that while overclocking can smooth some stuff out, for most day-to-day usage, it has no practical benefits and only causes more battery drain than you would otherwise have. Given how precious battery life is these days, why knowing make your battery drain faster?

it's funny you say that becuase i noticed with ludeboy's kernel that when overclocking system panel very rarely showed my phone running over the stock speed. Usually it was as you stated some where around 800mhz..I understand what your saying...Thanks for the quick response.

So what if we run stock clock...but undervolt? Do you think we will see any batt savings?

Backup SD and app data b/c crashing/freezing can corrupt files.
Edit: Also keep Voltage Scheduler Remover on your phone just in case.
1600
1500
1400
1300 -0
1000 -25
800 -50
400 -75
200 -100
100 -150
"interactive" was unstable a couple kernels ago so I haven't tried it.

suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
Potentially, yes, but you may lose stability.

Awesomeness
I love it. I can deal with a slightly shortened battery life. I wanted to OC because a lot of the more intense games don't run as smooth as I would like. With OC, its all butter. Thanks!! I have mine set at 1400, and it really didn't improve my quadrant scores, but there's a noticeable decrease in lag going from one app to another.

suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
You would see better battery life at stock clock speeds if you just used the standard (ie. not overclocked) kernel I built.

Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
I'm on board with not thinking it's necessary - though I can see how the tinkerers and speed demons would love it. (And all the more power to them, literally)

I don't know imnuts, I always noticed when I forced the phone into a higher overclock it always seemed quite a bit snapier.

Keep it on conservative. Interactive is buggy.
ZeppelinJ0 said:
Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse

underscored said:
Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
Click to expand...
Click to collapse
This will remain separate from the standard kernel most likely. I will see if I can build off of this source without overclocking and have it work, though I don't know if it will. I want to keep them separate for stability and battery life reasons.

[KERNEL][Unofficial CM11][Linaro][tate][07/12] Overclocks

Modified kernels overclocked.
I am not responsible if this bricks your device(no reason that it should but just in case).
***Update 7/12***
kernel allow usage of ext4 or f2fs on same partition.
this will not format to f2fs.
to use f2fs go here: http://forum.xda-developers.com/showpost.php?p=53427756&postcount=1&nocache=1&z=32066198618380
Bootimg_ext4orf2fs_CM11_Overclock_20140712.zip - 3.85 MB
MD5:ead39d8e659b3bc63518b0508a0e6ddb
Features
Hashcode's latest updates
http://review.cyanogenmod.org/#/c/65480/
GPU Overclock to 512 MHz up 33% from stock, CPU Overclock 42% up to 1.7 GHz
Linaro dropped for now
source https://github.com/Maromi-/kernel_omap_bowser-common
Linaro
Makefile
ifdef CONFIG_CC_OPTIMIZE_MORE
KBUILD_CFLAGS += -O2 -fmodulo-sched -fmodulo-sched-allow-regmoves -fno-tree-vectorize
endif
KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-fno-strict-aliasing -fno-common \
-Werror-implicit-function-declaration \
-Wno-format-security \
-fno-delete-null-pointer-checks \
-march=armv7-a -mtune=cortex-a9 -mfpu=neon \
-ffast-math -fsingle-precision-constant \
-fgcse-lm -fgcse-sm -fsched-spec-load -fforce-addr
tate_android_deconfig
-CONFIG_CC_OPTIMIZE_size=y
+# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
+CONFIG_CC_OPTIMIZE_MORE=y
Old Stuff
https://www.dropbox.com/s/rniaco65frepkye/CM11_Overclock_20140418a.zip
MD5:13df3ec88983ad54498ec065486f0d33
Smartreflex Override
]https://www.dropbox.com/s/9j0v4htkyznewis/CM11_Override_20140331.zip
md5:d9986618035115fbd6a5df3b5903b8f0
THANKS TO:
Hashcode for his kernel
Galaxy Nexus XDA Forum Devs

Maromi said:
Modified kernels undervolted and overclocked they each also boot at max speed. Tested on PA and CM10.1.
1.4 GHz(try me first)
https://www.dropbox.com/s/va7u6t0dlomgc5r/UV_Modified_Kernel_KFHD7_1.4GHz.zip
MD5:e7810e7272b98fca97c02a0b519ad6d7
1.5 GHz(did you try 1.4?)
https://www.dropbox.com/s/1kd5qpi9o7w2pwl/UV_Modified_Kernel_KFHD7_1.5GHz.zip
MD5:060c9aaad58016580e39a4f066dfb0f1
1.3 or 1.6 GHz(boots at 1.6 GHz)
THANKS TO:
Hashcode for his kernel
Click to expand...
Click to collapse
The people who experienced a freeze at the boot animation of Hashcode's CM10.1 build will also experience a freeze here (I tested both myself), no matter which .zip file you choose. If you wish to proceed, please make sure you have Hashcode's 1.2GHz kernel on the sdcard, so that you can just flash that over and not have a paperweight on your hands. A backup would also come in handy.

Maromi said:
Modified kernels undervolted and overclocked they each also boot at max speed. Tested on PA and CM10.1.
1.4 GHz(try me first)
https://www.dropbox.com/s/va7u6t0dlomgc5r/UV_Modified_Kernel_KFHD7_1.4GHz.zip
MD5:e7810e7272b98fca97c02a0b519ad6d7
1.5 GHz(did you try 1.4?)
https://www.dropbox.com/s/1kd5qpi9o7w2pwl/UV_Modified_Kernel_KFHD7_1.5GHz.zip
MD5:060c9aaad58016580e39a4f066dfb0f1
1.3 or 1.6 GHz(boots at 1.6 GHz)
THANKS TO:
Hashcode for his kernel
Click to expand...
Click to collapse
see if meta.inf is well placed
---------- Post added at 06:46 PM ---------- Previous post was at 06:44 PM ----------
Maromi said:
Modified kernels undervolted and overclocked they each also boot at max speed. Tested on PA and CM10.1.
1.4 GHz(try me first)
https://www.dropbox.com/s/va7u6t0dlomgc5r/UV_Modified_Kernel_KFHD7_1.4GHz.zip
MD5:e7810e7272b98fca97c02a0b519ad6d7
1.5 GHz(did you try 1.4?)
https://www.dropbox.com/s/1kd5qpi9o7w2pwl/UV_Modified_Kernel_KFHD7_1.5GHz.zip
MD5:060c9aaad58016580e39a4f066dfb0f1
1.3 or 1.6 GHz(boots at 1.6 GHz)
THANKS TO:
Hashcode for his kernel
Click to expand...
Click to collapse
add governors and io scheluders and gpu overclock (or adding a new value, so we will have 3 frequencies, no the default 2) please

seokhun said:
The people who experienced a freeze at the boot animation of Hashcode's CM10.1 build will also experience a freeze here (I tested both myself), no matter which .zip file you choose. If you wish to proceed, please make sure you have Hashcode's 1.2GHz kernel on the sdcard, so that you can just flash that over and not have a paperweight on your hands. A backup would also come in handy.
Click to expand...
Click to collapse
are you wiping anything before or after flashing?
also of note is that im just sharing what i did to my device.

Maromi said:
Modified kernels undervolted and overclocked they each also boot at max speed. Tested on PA and CM10.1.
1.4 GHz(try me first)
https://www.dropbox.com/s/va7u6t0dlomgc5r/UV_Modified_Kernel_KFHD7_1.4GHz.zip
MD5:e7810e7272b98fca97c02a0b519ad6d7
1.5 GHz(did you try 1.4?)
https://www.dropbox.com/s/1kd5qpi9o7w2pwl/UV_Modified_Kernel_KFHD7_1.5GHz.zip
MD5:060c9aaad58016580e39a4f066dfb0f1
1.3 or 1.6 GHz(boots at 1.6 GHz)
THANKS TO:
Hashcode for his kernel
Click to expand...
Click to collapse
Now that you guys are making new kernels does this mean we are getting any closer to enabling USB host mode? maybe also enabling the GPS that's on the motherboard?

http://www.ifixit.com/Teardown/Kindle+Fire+HD+Teardown/10457/2
This Aldo shows FM transmitter/received included. Just curious if its possible
Sent from my Amazon Kindle Fire HD using XDA Premium HD app

Shawnsch said:
http://www.ifixit.com/Teardown/Kindle+Fire+HD+Teardown/10457/2
This Aldo shows FM transmitter/received included. Just curious if its possible
Sent from my Amazon Kindle Fire HD using XDA Premium HD app
Click to expand...
Click to collapse
I was gonna say FM radio but then i remembered it has no antenna!
unless it works the same way as some mobile phones where the headset 3.5mm jack acts as a receiver, But idk!

GPS would be awesome though
Sent from my Amazon Kindle Fire HD using XDA Premium HD app

AmrBanawan said:
unless it works the same way as some mobile phones where the headset 3.5mm jack acts as a receiver, But idk!
Click to expand...
Click to collapse
Some? dont you mean all? XD
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2

Thanks Maromi, this is working flawlessly for me and my benchmark is up to 9195!
Sent from Hell... in HD!

AmrBanawan said:
I was gonna say FM radio but then i remembered it has no antenna!
unless it works the same way as some mobile phones where the headset 3.5mm jack acts as a receiver, But idk!
Click to expand...
Click to collapse
the Tune In app is pretty amazing

could you add frandom, is faster, 10-50 times faster than urandom
https://github.com/Ryuinferno/frandom-android crossbreder has a script to use it, no the module, the module has to be made
4. Remove /dev/random as it's blocking . Link it to non-blocking /dev/urandom. Since /dev/random is blocking and designed to protect us from Quantum alien cryptographers with mathematical certainty and urandom is non blocking pseudo-random device that most apps and OSs are using anyway and with Haveged running, is as secure anyway as it's very difficult to empty the entropy pool faster than Havege can replenish it. Pre ICS devices have a lot to gain with this but ICS+ devices show visible gains too.
5. Frandom support - CrossBreeder now supports linking both your random devices to the extremely fast alternative - Frandom ( http://billauer.co.il/frandom.html ). This module is orders of magnitude (10-50 times) faster than the standard character devices ( Check this out - http://forum.xda-developers.com/showpost.php?p=37409586&postcount=134 ). The erandom character device also installed by Frandom doesn't use up system entropy at all on top of being fast. You will need to ask your ROM developer to develop the kernel module for you and then place it in /system/lib/modules. CrossBreeder will then try and load it and if successful, make all the necessary adjustments so that both /dev/random and /dev/urandom are pointing to /dev/frandom and /dev/erandom respectively. The speed benefits are to be seen to be believed. But since each ROM requires a unique kernel module, this option is left optional ( but auto detect ).
feature 5 is inportant, but the other is useful too to make our kindle very fast, or better, we couldnt see any difference but, there will be a gigant difference in system. i dont know, so many people say it is exellent

seokhun said:
The people who experienced a freeze at the boot animation of Hashcode's CM10.1 build will also experience a freeze here (I tested both myself), no matter which .zip file you choose. If you wish to proceed, please make sure you have Hashcode's 1.2GHz kernel on the sdcard, so that you can just flash that over and not have a paperweight on your hands. A backup would also come in handy.
Click to expand...
Click to collapse
I don't believe this is correct. Although my tablet was freezing with hashcode's original 1.5ghz kernel, both of these 1.4 and 1.5ghz builds are completely stable for me. It's worth trying even if you had problems with the other, however it may not work for all devices.
-Ken

will this work with the 4/22a build?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2

codepoet82 said:
I don't believe this is correct. Although my tablet was freezing with hashcode's original 1.5ghz kernel, both of these 1.4 and 1.5ghz builds are completely stable for me. It's worth trying even if you had problems with the other, however it may not work for all devices.
-Ken
Click to expand...
Click to collapse
Hashcode said there were problems with hardware, and that not all 4460s are the same, so whether you think it's correct or not is irrelevant. The tablets behave differently in many circumstances from one another.

seokhun said:
Hashcode said there were problems with hardware, and that not all 4460s are the same, so whether you think it's correct or not is irrelevant. The tablets behave differently in many circumstances from one another.
Click to expand...
Click to collapse
All hardware is not created equal, same reason some people may get more overclock out of a cpu then the next person with an identical setup.

I'm one of those regularly experiencing a freeze with CM10.1 (20130508 build).
I flashed the latest Hashcode build (20130511), which obviously works for me, because clock is back at 1.2GHz.
Then I flashed your kernel UV_Modified_Kernel_KFHD7_1.4GHz.zip, wiped cache & dalvik and I booted up with no problem!
But are you sure the boot is at maximum frequency?
I'm asking because, as soon as I select 1.400 MHz as max frequency in the Performance section, my KFHD7 instantly freezes.
EDIT: just had again a video acceleration during playback with MX Player (S/W decoder).

seokhun said:
Hashcode said there were problems with hardware, and that not all 4460s are the same, so whether you think it's correct or not is irrelevant. The tablets behave differently in many circumstances from one another.
Click to expand...
Click to collapse
Here, let me restate my original comment in the manner it was intended to be read.
"Seokhun is wrong, even if your tablet didn't work with hashcode's first 1.5Ghz kernel you should try these. Don't let his narrow minded view of how he thinks the world works prevent you from trying this yourself."
Now, why don't you take your bad attitude and put it in a box with a little pink bow on top, and go give it to mommy. She can tell you how you're a beautiful and unique snowflake, and the adults around here can get back to doing the actual work.
-Ken

degiovab said:
I'm one of those regularly experiencing a freeze with CM10.1 (20130508 build).
I flashed the latest Hashcode build (20130511), which obviously works for me, because clock is back at 1.2GHz.
Then I flashed your kernel UV_Modified_Kernel_KFHD7_1.4GHz.zip, wiped cache & dalvik and I booted up with no problem!
But are you sure the boot is at maximum frequency?
I'm asking because, as soon as I select 1.400 MHz as max frequency in the Performance section, my KFHD7 instantly freezes.
EDIT: just had again a video acceleration during playback with MX Player (S/W decoder).
Click to expand...
Click to collapse
It doesn't boot up at 1400, it boots at 1200 and you have to set it to 1400 if you want it there.

codepoet82 said:
Here, let me restate my original comment in the manner it was intended to be read.
"Seokhun is wrong, even if your tablet didn't work with hashcode's first 1.5Ghz kernel you should try these. Don't let his narrow minded view of how he thinks the world works prevent you from trying this yourself."
Now, why don't you take your bad attitude and put it in a box with a little pink bow on top, and go give it to mommy. She can tell you how you're a beautiful and unique snowflake, and the adults around here can get back to doing the actual work.
-Ken
Click to expand...
Click to collapse
I stated in the original reply that I tried all the .zips that Maromi provided along with Hashcode's, you donut. If you're going to be a douchebag about it, might as well go to do something else if you don't have a more civilized comeback. By your logic, we should ignore Hashcode's advice, because Maromi's kernels and Hashcode's kernel are actually quite similar.
The problem, according to Hashcode, lies with the devices, not the kernels themselves, you donut! How dare you make a statement regarding my mother, you insolent fool. If you've got any sense of decency, at least do it tomorrow, and not on Mother's Day!