Database Info

[KERNEL] 2011-10-30 - x99kernel OC/UC/UV 1.2/1.8GHz smartass - Sense & CM7/AOSP

First things first...
MAKE A NANDROID BACKUP.
I take NO responsibility for ANYTHING that goes wrong with your phone, life, job, home, car, sex life, dog, cat, turtle, pet rock, etc. as a direct or indirect result of your use of this kernel.
Features of kernel for Sense ROMs:
Based on HTC source code - this should work on any stock-ish ROM
Features of kernel for CM7 ROMs:
Based on Toast's fork of the Cyanogenmod kernel
Common features:
BFQ I/O scheduler
Smartass governor
Undervolted (battery savings)
Overclocked - up to 1.8GHz (WHY?!? lol)
Underclocked - down to 184Mhz (battery savings)
By default, the kernel will clock up to 1.2GHz with the smartass governor. I personally just flash the kernel and run it as-is. If you want something different, use an overclock utility like "No-frills CPU Control". Be aware that some of these utilities run background processes and SUCK battery life.
Troubleshooting:
ON CM7.0.2
You will need to flash the kernel *AFTER* booting up the ROM for the first time. If you do a clean install of CM7.0.2 + the x99kernel, turning on wifi may make your phone go into a "boot loop" (restarting the shell, over and over).
If you're stuck in a boot loop, go into recovery (yank battery then vol down + power OR "adb reboot recovery"), flash the 7.0.2 file again, let it boot, make sure Wifi works, then go back into recovery and flash the x99kernel.
If anyone has further input on this, I'm all ears.
My phone is locking up!
Try a slower clock speed and/or a different governor. I have run this kernel reliably at 1.55GHz for a long time, but different phones can have different results. I have personally experienced lock-ups at high speeds with the interactive governor. Again, I have been running this kernel "as-is" without making any clock/governor changes... IMO, 1.2GHz is plenty fast for day-to-day use.
My phone is running hot and/or the battery is draining quickly!
Most likely, you're running the CPU at a HIGH speed and/or there are some over-active processes.
I suggest downloading OSMonitor from the market to see what processes are active. In the options, you can choose to sort the process list by CPU Load and also check the "Order" box to have the active processes shown at the top of the list. The "Misc" tab will show the current clock speed and phone temperature... you can also use it to change the speed or governor if you'd like.
"adb logcat" can reveal a LOT about what your phone is doing in the background.
Credit:
bcnice20 - I followed a lot of what he was doing with his own kernel, but removed bits that didn't seem to work right for me.
toast - CM7 kernel is forked from his github
cloverdale - Proper root in Sense kernel
Old, out-of-date changelog:
20110414
Step up to 2.6.32.36 from 2.6.32.33 in CM7 kernel
20110411
camera fix for bcnice20's Desire ROM in Sense kernel
20110408
Proper root in sense kernel
20110404
Added BFQ I/O scheduler
Misc compiler tweaks
Added version for CM7
20110323
Lowered voltage on 184MHz and 245MHz speeds
20110322
Re-tweaked the smartass governor (see current strategy below)
Slightly increased voltages for CPU speeds between 768MHz and 1.55GHz (may help some people with lock-ups)
Added an additional low speed... 184Mhz (power savings?)
20110321
Tweaked the smartass governor
Added the interactive governor
20110318
Added two additional clock speeds between 768MHz and 368MHz. By default, the smartass governor can't make the "jump" down from 768MHz to 368MHz, because the step is too large.
Added conservative governor (untested, but should be OK).
Current smartass strategy:
Max sleep speed is 245MHz
CPU load under 35% = step down. Can step down as much as is determined to be OK at once.
CPU load over 70% = step up. Will make steps upward of as much as 384MHz at a time.
If CPU is at 100%, jump up to at least 1.1GHz.
Current versions:
Download x99kernel-GBSense-20111030 #1 FOR GINGERBREAD SENSE ROMs, NOT FROYO. No smartass governor yet. Uses improved flashing script.
md5sum: 1973b881d09796f16c2ab7a485c1b6df
Download x99kernel-cm7-20111003 #5(?) This is a 2.6.35 kernel! Slightly incomplete... no underclocking yet. Improved flashing script to avoid missing module files (fix WiFi errors). Max smartass sleep speed is 368Mhz.`
md5sum: a215897e48f26a1d03510f5e632f59bb
Download x99kernel-cm7-20110530 Still #2 This is a 2.6.32 kernel! For CM 7.0.3.1, CM7 nightly #87, or earlier.
md5sum: 9569a39d5746756b9f6a3a5bfcc63a9b
Download x99kernel-sense-20110411 #8 FOR FROYO SENSE ROMs, NOT GINGERBREAD.
md5sum: 2e94b170f3976cdc44dcecbfb21f9157
Old versions:
Download x99kernel-cm7-20110615 #4 This is a 2.6.35 kernel! Slightly incomplete... no underclocking yet.
md5sum: 1318f22887322cefca3ebafd44043bb6
Download x99kernel-cm7-20110611 #3 This is a 2.6.35 kernel! Slightly incomplete... no undervolting or underclocking yet.
md5sum: 3d36a18e7590dd29689d216028452137
Download x99kernel-cm7-20110414 #2
Download x99kernel-sense-20110408 Still #7
Download x99kernel-cm7-20110404 #1
Download x99kernel-sense-20110404 #7
Download x99kernel-20110323 for Sense #6
Download x99kernel-20110322 for Sense #5
Download x99kernel-20110321 for Sense #4
Download x99kernel-20110318 for Sense
Download x99kernel-20110317 for Sense
GPL Source

So 4g, gps, and all those other bugs are worked out on this kernel? And can i apply this over nfx stock rom?
Sent from my PG06100 using XDA App

Nice job on the kernel. Been running it for bout two hours clocked to 1.8ghz on performance in setcpu. Temp hasn't reached over 80. Hitting steadu 2400 in quadrant.
Sent from my fast as **** Evo Shift 4G using Tapatalk

so which one would u guys recommend? this or bcnices1.8 kernel? what are the differences

x99percent said:
MAKE A NANDROID BACKUP FIRST.
I take NO responsibility for ANYTHING that goes wrong with your phone, life, job, home, car, sex life, dog, cat, turtle, pet rock, etc. as a direct or indirect result of your use of this kernel.
Click to expand...
Click to collapse
My sex life instantly was overclocked!
Sent from HTC Knight using Mikrom..because CM7 got overrated like CWM

Lol
Sent from my Htc Evo Shift 4G

K running this now and hitting 53 linpack score 1.8 perf..pretty nice so far
Sent from HTC Knight using MikShift..because CM7 got overrated like CWM

DWake014 said:
So 4g, gps, and all those other bugs are worked out on this kernel? And can i apply this over nfx stock rom?
Click to expand...
Click to collapse
There *shouldn't* be any issues with 4G or GPS, since this is based on the original HTC source code. I have used it successfully over NFX's ROMs before... I think I'm running one of his now.
I have edited the orignal post to be a little more clear.

Just a heads up - the smartass governor doesn't scale below 768 mhz. I believe bcnice mentioned he had the same issue on his kernel.
Sent from my PG06100 using XDA App

so this kernel seems to have solved my issue with loading pages in the browser locking up the phone. Nice.
Is there anyway you can add the wired tether patch so I can just use that? I'm not to keen on switching roms and having to start over.
EVO Shift and XDA app

abanh said:
Just a heads up - the smartass governor doesn't scale below 768 mhz. I believe bcnice mentioned he had the same issue on his kernel.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
With the smartass governor, it won't scale below 768 when the screen is on... that's for sure. (<-- NO LONGER TRUE)
If you use SetCPU, the "Info" tab will show you that the phone is happily running at 245MHz when the phone is off... and I'm not forcing it to 245MHz, either.
I actually posted in bcnice's thread about this issue, along with a solution for it. However, I do think that adding an extra step between 368Mhz and 768Mhz will help things.
EDIT: Added a couple of lower speeds, and things seem to be improved. Will post a new zip file during the day.

adamr240 said:
Is there anyway you can add the wired tether patch so I can just use that? I'm not to keen on switching roms and having to start over.
Click to expand...
Click to collapse
I don't think that's handled within the kernel... from everything I've seen, that's a patch to a file in /system/framework/

adamr240 said:
so this kernel seems to have solved my issue with loading pages in the browser locking up the phone. Nice.
Is there anyway you can add the wired tether patch so I can just use that? I'm not to keen on switching roms and having to start over.
EVO Shift and XDA app
Click to expand...
Click to collapse
If you're talking about wired tether for root users needing ip filtering, that's on in all kernels for the shift, even stock. However, some bug or difference in framework doesn't let or phones tether on that or wireless tether on 3g, only on 4g
Sent from my PG06100 using XDA App

DWake014 said:
So 4g, gps, and all those other bugs are worked out on this kernel? And can i apply this over nfx stock rom?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
I'm running this over the nfx stock Rom, running smooth so far

I was running bcnice's kernel, but could only hit 1.1 max using on demand and the phone wold still hit 105 degress at times. Just installed Mik's rom and at this point am not using any kernel. Should this kernel work with this rom?

Aaargh! said:
I was running bcnice's kernel, but could only hit 1.1 max using on demand and the phone wold still hit 105 degress at times. Just installed Mik's rom and at this point am not using any kernel. Should this kernel work with this rom?
Click to expand...
Click to collapse
I use it so yes
Sent from HTC Knight using MikShift..because CM7 got overrated like CWM

Changelog:
20110318
Added two additional clock speeds between 768MHz and 368MHz. By default, the smartass governor can't make the "jump" down from 768MHz to 368MHz, because the step is too large.
Added conservative governor (untested, but should be OK).

x99percent said:
Changelog:
20110318
Added two additional clock speeds between 768MHz and 368MHz. By default, the smartass governor can't make the "jump" down from 768MHz to 368MHz, because the step is too large.
Click to expand...
Click to collapse
Nice update. Do you think you could also add the Conservative governor?

abanh said:
Nice update. Do you think you could also add the Conservative governor?
Click to expand...
Click to collapse
Done. Re-download the same link.

My frequency keeping ramping from 245 to 1.8 when idle, bouncing up and down on both ondemand and smartass. Flashed back to bcnice20's bfs bfq for now.. but I'd like to make this work as I love running the smartass gov. Any ideas?

[KERNEL][GPL]VisionKernel v1.3 *WIP*

VisionKernel v1.2
Designed for SyndicateROM Frozen 1.1.0​
Disclaimer
I nor any member of INC is responsible for anything that happens to your phone when using this kernel. It has been tested on mine and a few others phones to be working, but I cannot guarantee that it will work on yours. All CPU's are different, and each one takes to overclocking in different ways. That being said, don't be surprised if your phone locks up at 1.4ghz or 1.45ghz. Just set the clock down to a lower speed and it won't do it anymore; all this means is that your phone can't handle it.
Also, 1.45ghz is set at 1.400v and 1.4ghz is set at 1.375v which is definitely above the recommended voltage for the phone. This doesn't mean it will burn up your processor as they are very robust when it comes to heat dissipation, but just keep in mind that you are pushing the processor past its designed limit.
This is my first kernel release, although I have been compiling my own custom kernels since DI18. Took me a while to get the overclocking stable, a big thanks goes to tanimn and Rodderik for helping with getting 1.3ghz stable. Also, without tanimn none of this would really be possible. He has guided me through this process a lot, and I am especially thankful to him. You the man tanimn ;-)
1.45ghz is here, I cannot guarantee that it will work even at all on your phone. This is as high as I will go, no further.
Linpack: 19.84mflops
Quadrant: 2414
Changelog
*=Thanks!
v1.0
Overclocked to 1.3ghz and 1.4ghz @ 1.375v (steps are as follows)
100mhz, 200mhz, 400mhz, 600mhz, 800mhz, 1.0ghz, 1.3ghz, 1.4ghz
Added 600mhz step for better transitions *tanimn
Voodoo Sound v6 *tanimn and supercurio
Voodoo Color (mDNIe tweaks) *supercurio
FPS cap raised to 65fps for the time being, hoping to get that number higher *Rodderik
Everything else that is contained in Twilight Zone, minus the addition of voodoo color and 1.4ghz.
v1.1
Revert the refresh rate (framerate cap) to 56fps. People having problems with video choppiness, this should fix your issue. This is only temporary; as soon as someone can figure out a proper way to raise the framerate cap I will re-implement it.
Update to Voodoo Sound driver v7
v1.2
Add 1.45ghz (It's not 100% stable, use at your own risk.)
Add 1.2ghz step
Added BFQ disk scheduler
Implemented interactive CPU governor (use at your own risk, needs tweaking)
Smartass governor (still a WIP)
Add TinyRCU courtesy of tanimn
lowmemorykiller atomic notifier fixes
UV RAM and LCD; 2.7v and 1.65v respectively
UV_mV sysfs controls as well as frequency_voltage_table for use with Voltage Control and Pimp my CPU *Rodderik
New voltage/frequency tables thanks to Rodderik!
v1.3
Battery life improvement tweaks
BFQ by default
New frequencies
More...
How-to Video:
Thanks to qbking77 for making this excellent flashing tutorial! This will show you exactly how to get the kernel running on your phone.
http://www.youtube.com/watch?v=1k7hqewGoWk
*Downloads*
v1.2
Direct:
Temporarily removed.
v1.1
Direct:
www.holylivingfuck.com/ACS/Kernals/VisionKernel_v1.1.zip
More mirrors coming soon!
v1.0
Direct:
http://k0nane.info/rom/VisionKernel_v1.0.zip
Other:
http://www.mediafire.com/?tihrnrjm6cm177u
http://www.sharebeast.com/7egv5a83g9ab
*Source*
Github
Donations are never required, but always welcome
​

Donators:
darkfire79
epic4GEE
jbobspants
stir fry a lot

Alright, I'm swapping the twilight zone kernal for this. Thanks for an amazing job once again.

EDIT: Damned conversion from all caps.
ONE POINT FOUR JIGGAWATTS!
ACS FTW.

Great job Thomas. I'm one of those who can't push the processor past 1.2g. Despite that I have had the privilege of testing pretty much all of the Twilight kernels courtasey of Tanimn as well as the Vision kernel. Both are great kernels, and run smooth on my Epic as long as I don't push it to the highest clock. Never had a reboot or lock up pushing my phone with these kernels. Once gain thanks Thomas, I know how much time and energy you go into this kernel and it shows!

dreamsforgotten said:
Great job Thomas. I'm one of those who can't push the processor past 1.2g. Despite that I have had the privilege of testing pretty much all of the Twilight kernels courtasey of Tanimn as well as the Vision kernel. Both are great kernels, and run smooth on my Epic as long as I don't push it to the highest clock. Never had a reboot or lock up pushing my phone with these kernels. Once gain thanks Thomas, I know how much time and energy you go into this kernel and it shows!
Click to expand...
Click to collapse
You the man dreams, much appreciated my friend thank you!
Sent from my SPH-D700 using XDA App

OMGGGGGGG
Thank you !!!!!!!!!
..... So fast that Smartbench force closes

I'll try this in a few days, assuming my phone can handle 1.3 jigga hurtz first. Sure sounds good tho, thanks, I'll report back in a few days.

How is everyone's battery doing running this kernel?

nice I just downloaded this and about to set everything up. Thanks!!

Yea buddy....
Wheres me and dreams name in big red letters for pushing you to release this
Sent from my SPH-D700 using Tapatalk

can this be flashed on eb13?

MysteryEmotionz said:
Yea buddy....
Wheres me and dreams name in big red letters for pushing you to release this
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
If Tom is smart, he'll tell you the same thing I did: ***** please.
blspyro said:
can this be flashed on eb13?
Click to expand...
Click to collapse
Yes.

Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.

MikeyLee said:
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
Click to expand...
Click to collapse
Long story short: Quadrant sucks. Try a better benchmark.

k0nane said:
Long story short: Quadrant sucks. Try a better benchmark.
Click to expand...
Click to collapse
Any suggestions?

MikeyLee said:
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
Click to expand...
Click to collapse
Also you will get higher scores when you get off that old ass rom with old files and source. So like 4 months ago. Smartbench is good
Sent from my SPH-D700 using XDA App

How are you suppose to test stability of oc for your phone in setcpu? I ran the stress test at 1.3ghz with no errors was there other tests to confirm stability?
Sent from my SPH-D700 using XDA App

jbadboy2007 said:
How are you suppose to test stability of oc for your phone in setcpu? I ran the stress test at 1.3ghz with no errors was there other tests to confirm stability?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Try running something CPU intensive, such as Neocore or an3dbench.
Sent from my SPH-D700 using XDA App

And its resluts will tell me its unstable or will it be laggy or fc or re boot?
Sent from my SPH-D700 using XDA App

[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][GBSense] 2016Mhz OC LeeDrOiD Modified Kernel-VERY BETA

What I have here is a VERY BETA kernel built from the latest LeeDrOiD git with some ondemand tweaks to make it a bit more responsive, as well as AXI Scaling, an undervolted bottom end at 122mhz, and with a topend of 2016mhz.
Many phones may not run at the full upper-end, but vddsys is implemented as in the LeeDrOiD kernel, so you may increase or lower the VDD by 25 for 20160000mhz to attempt to get it working.
Currently working on getting a github page up with this source. I'm running it on the Unity rom at the moment without issue. 2016mhz should only be used for benchmarks, and not 24/7.
Two way call recording is also included, as well as a startup script to run at 1843mhz ondemand at startup.
Changelog:
June24-Initial Release...Working on Cleanup.
GitHub Page: https://github.com/synergydev
Will work on marking changes shortly. It should also be of note that because my GF's phone seems stable at [email protected], I changed the voltage at 2016 to 1.5 on the git just because it seems my phone likes high voltages.

I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable

LorD ClockaN said:
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
Click to expand...
Click to collapse
I'm using 1.525V at 2016, however my DHD could never run the 1.9986 in your kernel without a voltage bump (could undervolt all the way up to 1.8 however though). In this kernel, I needed to up the AXI clock at 2016 to even get it to run, let alone benchmark continuously. I still haven't been able to get it to scale with a minimum under 300mhz.
This is why I recommend reducing the VDD at that speed by 25 if anyone's DHD can't run it.
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).

synergye said:
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
Click to expand...
Click to collapse
+1 on that, but don't think you're more enthusiastic when talking about OC
We can argue about that the whole day
looking forward for your git!

I think 1.2G is enough..

@LorD ClockaN: if that's an sense kernel, you know what you have to do
Your 2016 MHz ASOP kernel coming soon?
with friendly greet
starbase64

You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?

Tryng with virtuous sense 3 and it makes lag the sense but for the rest is quiet good
Edit: after some time the lags disappears and all is perfect now

where source code?
u canT post kernels on XDA without source code

m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!

m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.

tolis626 said:
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
Click to expand...
Click to collapse
Mine has voltage till 1.525 via vdd
Sent from Desire HD with CyanogenLordMod!!!

adwinp said:
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
Click to expand...
Click to collapse
really?
lol
Why do you explain to me?

m-deejay said:
really?
lol
Why do you explain to me?
Click to expand...
Click to collapse
Oohoo... Dev fight!! LOL
Sent from Desire HD with CyanogenLordMod!!!

wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??

Lizzo said:
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Click to expand...
Click to collapse
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.

Ace42 said:
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Click to expand...
Click to collapse
uuuggghhhh... how do i raise the min b4 startup?

Lizzo said:
uuuggghhhh... how do i raise the min b4 startup?
Click to expand...
Click to collapse
echo 806400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
On adb you have to change the min freq while booting up. 800 might work. Or use 1305600 [1.3GHz].

This is madness, yes i know people will post no this is sparta, but seriously, anything over 2ghz i personally wouldn't test

adwinp said:
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Click to expand...
Click to collapse
PMSL Benchmarks mean fuk all tbh do not reflect real world peformance running at 1.8/1.9ghz stuff like Playstation emulator etc run far much smoother and with no slowdowns etc... newbs and benchmarks lol!

[KERNEL][AOSP4.4/5.1/6.0/7.1] dkp - d2vzw & d2usc - 2/4/18

Welcome to decimalman's kernel playground!​
As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.
Features:
Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)
Underclocking down to 54 MHz, with stability improvements
Undervolting compatible with most apps
Fast charge without unplugging first
Glorious animations for the notification and softkey LEDs
Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)
freelunch and tierservative governors for optimal battery life without sacrificing responsiveness
Automatic mpdecision and auto-hotplug are only enabled when needed
Adjustable minimum voltage for stability on finicky processors
Optimized UKSM to free up some extra memory
Code optimizations for size and speed
Compiler optimizations (-O3, LTO, and more) because faster is better
Donors: Thanks, everyone! Your generosity is much appreciated. :good:
drpenguino, 0xScott, vmancini3 (twice! :good, Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict
Remember:
Nandroid!
last_kmsg and/or logcat or it didn't happen.
Other kernels have their own threads or forums. Discuss them there.
Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.
Be silly. We're here to have fun.
Installation:
Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called.
Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).
Reboot.
Undervolting:
Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).
Downloads:
MediaFire:
All Downloads
dkp-vmin-XXX.zip
Solidfiles (Make sure you have an adblocker!):
All Downloads
dkp-vmin-XXX.zip
Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.

Bugs:
Let me know.
Stable changelog:
3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.
4/8/13 (3.0):
FauxSound support
Strip more useless stuff
A few bonus optimizations
4/8/13 (3.4):
Port everything except erandom from 3.0
Enhance cpufreq for easier configuration
4/24/13 (3.4):
Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.
Lots of CM/CAF/Linux updates
Working AssWax governor
Trinity colors support
sio, zen I/O schedulers
erandom is back!
Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness
Probably lots more, but there's hundreds of commits to sort through...
5/29/13 (3.4):
Bugfixes: better overclocking support, better hwrng support, etc.
Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface
Automatic auto-hotplug
New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain
6/14/13 (3.4):
Bugfixes: fix several critical bugs in the 5/29 release.
9/7/13 (3.4):
Fixes for OC, UV, auto-hotplug.
A few new optimizations.
Synced up with CM.
9/20/13 (TW):
Ported everything from AOSP to TW.
9/20/13 (4.3):
Merged 4.3 from CM into the existing 4.2 code.
Current experimental branches:
Nothing interesting at the moment.

Goodies:
dkp doesn't come with its own splash screen. However, the dkp installer (i.e. the install zip) is smarter than you think, and can apply a custom splash screen for you. Here's how:
Create a folder on your internal storage named "dkp"
Copy a PNG image into the directory, and rename it "splash.png". Alternatively, copy an RLE image (i.e. from a flashable custom splash screen zip) and rename it "splash.rle". Ideally, the image should be roughly 1280x720 to begin with, since it won't be resized.
The image will be used as your splash screen whenever you flash dkp. Reflash to apply initially.
mikedavis120 has put together a how-to video that covers tweaking dkp for optimal battery life. If you're new to dkp, take a look! He also put together a zipped collection of apps that will come in handy while tuning dkp. It also includes a flashable zip, "dkp-debug_v1.zip". After flashing it, running
Code:
su
dkp
from a terminal emulator will collect lots of useful debug information that will make it much easier for me to track down the issue you're having. :good: mikedavis120 recommends installing SuperSU (included in the zip) instead of what's included in you ROM.
sysfs:
It's possible to adjust all the settings available in dkp without using apps. Because they show up as files, settings can be adjusted with file managers, terminal emulators, adb and initscripts. Here's the most interesting files inside sysfs:
/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors (not available on newer AOSP builds): display tint (0 = very red, 2 = default, 4 = trinity colors)
/sys/class/misc/gammacontrol (only available on newer AOSP builds): various color controls. See this post for details on enabling Trinity colors on builds that use these controls.
/sys/devices/system/cpu/cpu<N>/cpufreq/UV_mV_table: voltage table
/sys/devices/system/cpu/cpu<N>/cpufreq/scaling_...: scaling_governor is the governor, scaling_min_freq and scaling_max_freq are the minimum and maximum frequencies, scaling_available_governors and scaling_available_frequencies show the available governors and frequencies
/sys/kernel/dkp/force_fast_charge: fast charge
/sys/kernel/dkp/link_core_settings: when linked (the default), frequency settings and some governors are automatically copied to the other core
/sys/kernel/dkp/vmin: minimum processor voltage in mV
/sys/kernel/mm/uksm/run: activate UKSM
auto-hotplug tuners:
These show up in the governor settings for any governor that doesn't do its own hotplugging. They only take effect when using auto-hotplug, so you'll probably need to disable mpdecision in Trickster.
hotplug_intpulse: when set to 1, automatically turns core 2 on whenever the screen/buttons/whatever is pressed. Default is 0.
hotplug_sampling_periods: number of samples to use for average number of running tasks. Default is 15.
hotplug_sampling_rate: number of 'jiffies' (currently 1 jiffy = 10 ms) between each sample of running tasks. Default is 20 (0.2 sec).
hotplug_enable_one_threshold: the average number of running tasks required to turn core 2 on, multiplied by 100. Default is 125 (1.25 tasks on average).
hotplug_disable_one_threshold: the average number of running tasks required to keep core 2 on, multiplied by 100. Default is 250 (2.5 tasks on average).
freelunch/nanolunch tuners:
freelunch and nanolunch aren't materially based on other governors, so their configuration is quite different than other governors. There's lots of tuners, since I haven't really decided on an ideal tuning. I encourage experimentation! I'll explain a bit of how these governors work before actually listing the tuners.
Generally speaking, there are two modes: in "normal" mode, sampling is done occasionally and frequency is generally increased slowly; in "interactive" mode, sampling is done much more quickly, and frequency increases much more quickly. "Interactive" mode ends after several samples of very low usage. The idea of a "hispeed" frequency is used in lots of governors, and it refers to the frequency that the CPU will jump to when more CPU usage is needed; generally, it's a generous estimate of how much CPU will be needed. Here, the hispeed frequency is adjusted on-the-fly, increasing when more CPU is needed and gradually decreasing when the CPU is idle. In "interactive" mode, the hispeed frequency is kept fairly high so that everything will feel snappy.
Hotplugging is taken care of in the least complicated (and in my opinion, most reasonable) way possible: if core 1 is using lots of CPU, and there are several tasks running (in other words, if it's likely that core 2 will have something to do), core 2 is turned on; if either core isn't doing much except using power, core 2 is turned off.
sampling_rate: the usual
hotplug_up_cycles: number of consecutive heavily-loaded samples before core 2 is turned on
hotplug_down_cycles: number of consecutive lightly-loaded samples before core 2 is turned off
hotplug_up_load: number of running tasks required to bring core 2 online
hotplug_up_usage: number of used CPU cycles (in thousands per second) required to bring core 2 online
hotplug_down_usage: number of used CPU cycles (in thousands per second) required on both cores to keep core 2 online
overestimate_khz: number of CPU cycles to overshoot usage by in "normal" mode
hispeed_thresh: if CPU usage is within this many cycles (in thousands per second) of the maximum frequency, frequency will be increased to the hispeed frequency. Generally, hispeed is pretty low in "normal" mode, and fairly high in "interactive" mode.
hispeed_decrease: when the CPU is sitting idle, the hispeed frequency is decreased by this amount each sample (this isn't ideal, but it works)
interaction_hispeed: the initial hispeed frequency when switching to "interactive" mode
interaction_return_cycles: number of consecutive lightly-loaded samples before returning to "normal" mode
interaction_return_usage: number of used CPU cycles (in thousands per second) required to stay in "interactive" mode
interaction_panic (nanolunch only): when set to 1, allows aggressively jumping past the current hispeed frequency under some circumstances
interaction_sampling_rate/overestimate_khz: equivalent to the "normal" versions of the tuners, these take effect in "interactive" mode

This looks great - especially excited about your custom governor! Thanks!!
Sent from my SCH-I535 using xda app-developers app

Glad we have another kernel dev. But do you plan on releasing a tw kernel? I run tw 98% of the time and would love to try it out. Thanks for your work regardless

PsiPhiDan said:
This looks great - especially excited about your custom governor! Thanks!!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
freelunch is absurdly simple, but does its job well. Let me know what you think. Happy flashing!
aypeeootrek said:
Glad we have another kernel dev. But do you plan on releasing a tw kernel? I run tw 98% of the time and would love to try it out. Thanks for your work regardless
Click to expand...
Click to collapse
I don't run TW, so I don't have any plans to release a TW kernel. If there's enough interest, I suppose I could get to work on one though.

Interesting. Looks cool man, will check it out
Sent from my SCH-I535 using Tapatalk 2

I'm excited to give this a shot!
Sent from my SCH-I535 using xda app-developers app

flashaholic commencing flash!

Anyone using trickster mod with this kernel?
Sent from my SCH-I535 using Tapatalk 2

Love this kernel! Freelunch is amazing
Sent from my SCH-I535 using xda premium

This kernel run pretty good!!
Sent from my SCH-I535 using xda app-developers app

masri1987 said:
Anyone using trickster mod with this kernel?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's the recommended tuner app, and plenty of people are using it (mostly on Sprint and AT&T). It shows some options that are completely bogus (like GPU governor), but I've added a few extras that only Trickster supports.
Thanks for the encouraging feedback, everyone! It's much appreciated. :good:

Kudos on this kernel. It has been perfect for me so far.

Running good on my d2usc! What scheduler do you recommend?
Sent from my SCH-R530U using Tapatalk 2

New 3.4 experimental builds are going up!
governors is building now, and has sio and zen. It'll eventually have a few new governors, but I haven't gotten everything ported yet.
gcc480 is up now, and is a test to make sure GCC 4.8.0 isn't causing any crazy bugs. It's also got sio and zen.
Edit: I forgot about you, trvbone. I don't have a preferred scheduler. I usually just use sio. I've never had a positive experience with ROW, but that might just be bad luck on my part.
More edit: I'm building a 3.0 kernel with trinity colors support and GCC 4.8.0 now. It should be up shortly.

decimalman said:
New 3.4 experimental builds are going up!
governors is building now, and has sio and zen. It'll eventually have a few new governors, but I haven't gotten everything ported yet.
gcc480 is up now, and is a test to make sure GCC 4.8.0 isn't causing any crazy bugs. It's also got sio and zen.
Edit: I forgot about you, trvbone. I don't have a preferred scheduler. I usually just use sio. I've never had a positive experience with ROW, but that might just be bad luck on my part.
Click to expand...
Click to collapse
I'm no noob when it comes to kernel lingo, but I'm not sure what the dif is here between the kernels listed as governors and gcc480. Are these two different kernels? I'm not aware of what gcc480 is I guess. Sorry until recently I was a dedicated lean kernel user and don't know all of the terminology since lk was pretty plain Jane.
I'm not a huge fan of row, but that's what I'm using right now cause it's quick just a little sketchy sometimes.
Sent from my SCH-R530U using Tapatalk 2

trvbone said:
I'm no noob when it comes to kernel lingo, but I'm not sure what the dif is here between the kernels listed as governors and gcc480. Are these two different kernels? I'm not aware of what gcc480 is I guess. Sorry until recently I was a dedicated lean kernel user and don't know all of the terminology since lk was pretty plain Jane.
I'm not a huge fan of row, but that's what I'm using right now cause it's quick just a little sketchy sometimes.
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.

decimalman said:
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
Click to expand...
Click to collapse
Thanks for the expl I'll flash tomorrow morning and give it a whirl! Great job BTW. This is now my daily driver!
Sent from my SCH-R530U using Tapatalk 2

decimalman said:
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
Click to expand...
Click to collapse
Giving it a go now. Do you have any test methods you use to test the stability of a kernel other than the everyday use approach? Thanks for the support, looks sweet:good::good::good: