yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] chad0989:
12/08/2011

Added an ICS branch.

08/15/2011

Support for voice call recording.

Adjusted voltage range to 700min 1375max. Good luck have fun.

07/06/2011

Fast charge USB

Patch to increase performance of a function often used in the kernel (memcpy)

http://www.incredikernel.com

If you would like incredikernel to keep improving, please turn off adblock for the domain. It is greatly appreciated.

06/27/2011

Fix for devices that use newer touch controllers

Read this: http://xdaforums.com/showpost.php?p=15132827&postcount=3626

Get it at http://www.incredikernel.com

06/19/2011

2.6.38.8

Everything from the 4/19 release

A bunch of changes to fix smartass (I think finally)

Simple sysfs interface to enable/disable audio boost

http://www.incredikernel.com

12/23/2010 - Sense

incrediblec-MR3-2.6.32-g9a2fc16 base

Patched up to 2.6.32.27

OC up to 1.1136ghz

Screen on minimum 245mhz

Screen off 128/384

HAVS/UV

Improved smartass scaling (likes lower frequencies more) - default

BFQ I/O scheduler

Tiny RCU

CFS scheduler tweaks

GPU+

SD card speed fix

TUN + CIFS modules

ext4

Updated yaffs2/atmel touch/wifi

3/5 Multitouch support - NOTE: Some devices only support 2 touches

http://www.incredikernel.com

Use the +25v zip if you have stability issues

I recommend you don't change governors and don't set any profiles. Let smartass do its thing as it takes care of sleep.

If multitouch is not working, you may be able to get it to work by following this:

http://xdaforums.com/showpost.php?p=10231055&postcount=1104

InrediControl:

https://play.google.com/store/apps/details?id=com.incredicontrol

IncrediControl AdFree key:

https://play.google.com/store/apps/details?id=com.incredicontrolAF

Fastcharge widget:

https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget

Because of many requests to add this:
[Droid Incredible Android Development] DopeShiziot:
looks nice, would you mind if i included this in my rom?
[Droid Incredible Android Development] DS36:
Can you mod a kernel for cm6

Its already made just add more features? ????
[Droid Incredible Android Development] spjoneser:
I would imagine there's a few guys working on this? Good work getting it out first.

Gonna give it a go!
[Droid Incredible Android Development] scottylove:
Question, is the original kernel BFS or did you add that in? Just curious as I really like the UI smoothness of the stock .17 and I have absolutely 0 knowledge of linux besides what i've picked up from reading xda.

Thanks so much for cookin this up, smells good! :)
[Droid Incredible Android Development] DopeShiziot:
lol htc wouldnt cook in the bfs scheduler
[Droid Incredible Android Development] DopeShiziot:
chad,

would you actually mnd whipping up a cfs version? i find that cfs is much more stable than bfs
[Droid Incredible Android Development] Irieone:
sweet dling now ...ty

edit- holy benchmarks!
[Droid Incredible Android Development] jermaine151:
Thanks Chad! Just flashed it.
[Droid Incredible Android Development] alexdeluxe:
I just flashed it. What is GPU+ anyway?
[Droid Incredible Android Development] chad0989:
Go for it.

Did you have issues with this kernel? BFS really should be better suited for phones where a smooth UI is important.

Here's a little reading material:

http://www.google.com/url?sa=t&sour...qsCyDw&usg=AFQjCNG7ORB_chlUiype8OJZES-5bHzSjA

Its a patch for sense kernels that increases 2d and 3d performance.

http://xdaforums.com/showthread.php?t=825304
[Droid Incredible Android Development] DopeShiziot:
thanks!

and no, i havent had issues, but in the past ive found cfs to be much more stable and reliable.
[Droid Incredible Android Development] SomeGuyDude:
Make this for aosp please. Ziggy stopped doing them, King's had some issues, and Koush's test doesn't have all the governors enabled.
[Droid Incredible Android Development] overground:
Source needed

Please post or link your source changes. It is required under the GPL. Thanks for your cooperation.
[Droid Incredible Android Development] DopeShiziot:
is that by chance why the kings kernels were removed? j/w
[Droid Incredible Android Development] overground:
You guessed it. ;)
[Droid Incredible Android Development] chad0989:
There you go.
[Droid Incredible Android Development] DS36:
i wonder why when i ask any if its possible for cm6

i always get ignored????
[Droid Incredible Android Development] crazyg0od33:
anybody have good resullts? battery life? about to flash, just curious?

thanks
[Droid Incredible Android Development] chad0989:
What did you need done?
[Droid Incredible Android Development] chad0989:
I'd leave it, unless you want to underclock the max freq then use setcpu by all means. No need for a screen off profile or anything though, the gov takes care of that.
[Droid Incredible Android Development] mikeymop:
That ifs probably the problem I've had with the kernel as I always charge the phone up after flashing it. If that bug gets sorted out I'd definitely try it out again.

As for it not appearing in Ruby it's probably because Ruby has the built in over clocking tools
[Droid Incredible Android Development] DS36:
hmmm is it possible to add anyore love to the asop kernel?
[Droid Incredible Android Development] dscribe:
I just installed the new CFS version of the kernel and time will tell of course, but first impressions are really good! I'm anxious to see how this works out. The 1368 Quadrant score it just got with the SA governor looks good too. I'll report back tomorrow and tell you my continued impressions after using it for a day but so far it is looking like a "job well done!"
[Droid Incredible Android Development] omgi0wn:
Would it be possible for you to allow us to overclock this kernel? I think it could be improved a lot if we could overclock and undervot. Also, it runs amazing! I'm testing out this newer version and ziggy's, not sure which one I like most yet.
[Droid Incredible Android Development] Lexus One:
I agree. Back in post #113 I said that it was laggy as heck. But after trying your latest and greatest (11/26) release, I am of a changed mind. It rocks! My SR 3.3.4 is the most responsive I have ever seen it. Benchmarks are up too. And no more laggggg! This one is the one! Thanks for all your hard work !
[Droid Incredible Android Development] pete_kowalski83:
I wouldn't say no more lag. but I have to say the web browsing lag I was having has significantly decreased... I +1 for OC & UV might help with some lag thats still there. its def getting better man!

I'm gonna keep running it and abusing it for the next cpl days
[Droid Incredible Android Development] whewstoosae:
+1 love your work chad.

Sent from my MIUI Incredible.
[Droid Incredible Android Development] jitajt:
I am using MIUI ROM and for me set cpu made it worse, it froze and thew my phone into a boot loop, i restored the original kernel and it started back at the setup screen and a ton of F/C. I had to do a full restore. it has great potential and I would love to keep using it but for now I will have to stick to the kernel that came with the ROM.
[Droid Incredible Android Development] mikeymop:
Are you on BFS of CFS?
[Droid Incredible Android Development] Lexus One:
I believe it is CFS.
[Droid Incredible Android Development] spjoneser:
Had to ditch it on the first go around due to the laggy unlock. But this is just what I've been waiting for. I like several of the older kernels but REALLY like the charge speed of the newer release, glad Chad has got this one rolling well.

Good Work!

Time to overclock?
[Droid Incredible Android Development] Hand76:
What is this new smartass gov supposed to do? Looks like a battery killer since it never went under 460 mhz.

Btw what is better to save on battery life, conservative our powersave?
[Droid Incredible Android Development] tktouch12:
this kernel looks really nice. i'm about to try it, but i want to make sure:

will it work with skyraider 3.3.4? i assume it would, but i use hibernate a lot and i'm not sure if that is dependent on something found in the kernel?
[Droid Incredible Android Development] AdhvanIt:
Any possibility of adding some more clock speeds between 998 and 1.152?
[Droid Incredible Android Development] chad0989:
I set it to not go under 460 while awake to prevent lag, tossing around the idea of trying 384 though. Screen off it will still clock down to 245 which is where you really conserve battery anyway.

Powersave always clocks the cpu at the lowest freq, so it would use the least battery, but you'll probably have a lot of lag.
[Droid Incredible Android Development] chad0989:
At some point I plan on it.
[Droid Incredible Android Development] Hand76:
Oh yea being able to o/c some would be sweet.
[Droid Incredible Android Development] vinylfreak89:
i'll ask again... any plans on doing AOSP for the new kernel... really think this has huge potential.
[Droid Incredible Android Development] alexdeluxe:
I'm using SR 3.3.3 and the kernel runs great. It's the only kernel I've wanted to switch over from the King kernels. Hibernate looks like it works when I just tested it (although it changed my screen brightness; not sure if that is kernel related though because I've never used it)

Also, today's update is great. Runs a lot smoother than the original.
[Droid Incredible Android Development] jayochs:
hell yeah man. a few friends and i were planning on it a year back, but it just fell through...they were devils fans, and i was the sabres fans, and the devs were playing in buffalo..so rather than just go like an hour away to newark to see the sabres play the devils, we planned an 8 hour roadtrip to buffalo haha..one day it'll come through!!
[Droid Incredible Android Development] cpupeli1:
I used my GPS for nearly 4 hours starting with 15% when I left. I'm running GB 2.6.37.4 on the latest MIUI Rom. Charged perfectly and it never got hot which was a first.
[Droid Incredible Android Development] yopete525:
I noticed this improvement as well, although there appears to be some sort of "tearing" in the ADW EX app drawer (I use it in the new vertical setting with a 100% black background) when fling it up/down really fast.
[Droid Incredible Android Development] poetzmij:
hmm i like the new kernel like always and the wake seems a little more reliable, like on the last kernel it was fast but every once in a while it would lag or not turn on at all but i guess it would think it did? anyways havent run into that problem once yet. BUT the whole experience is faster but at times it will stutter, i never had this stutter on the last one :/
[Droid Incredible Android Development] chuckyteets:
is the brightness reading at 10 new for this preview? i don't think i noticed it in preview one. i have really been wanting this on your kernel, baller! i think i've finally got them where i want them.
[Droid Incredible Android Development] chad0989:
Yes it is. I pushed it over to my testing branch real quick because everyone kept mentioning it.
[Droid Incredible Android Development] nevetsvsx:
With the new preview kernel the charging is insanely fast!! I agree!!
[Droid Incredible Android Development] gohamstergo:
hmm interesting. ill have to test it out again. see if its changed since i last did long distance gps
[Droid Incredible Android Development] blackstallion:
I just flashed #31 and the 3/18/01 Incrediblekernel (wiped cache and dalvik). All was running well so I went ahead and changed my bootanimation and then downloaded Rover's latest 1.6 theme. After installing Rover's latest, I got a google framework FC, Theme Chooser FC, ADW EX FC, and now I can't boot into my phone OR recovery! Anyone can tell me whats going on? I try to reboot into Recovery by hitting power and the volume down but it just goes to splash and then bootanimation, where it stays for a long time and then the screen eventually dies. I then have to either do the three button reboot or a battery pull....but it still won't boot into recovery. What's going on?
[Droid Incredible Android Development] J2theMatt:
Anyone had any issues with the "set on boot" feature under cyanogenmod settings for the new preview kernel?
[Droid Incredible Android Development] texanaustinite:
Any luck?

Maybe as easy as holding down 'volume down' then 'power'.
[Droid Incredible Android Development] byrong:
Yes, someone helped him in the CM7 nightlies thread and it's taken care of now. You are correct: he wasn't properly holding to boot into recovery
[Droid Incredible Android Development] blackstallion:
Yea, I had a noobie moment, didn't hold the pair down long enough, alls well now, thanks.
[Droid Incredible Android Development] texanaustinite:
Good to hear. I had a brain fart last week.

I flashed an update that I was going to just flash over. Did it when I woke up and ended up wiping all data instead if cache. Didn't nandroid. Shoulda had coffee first.
[Droid Incredible Android Development] JetBomber117:
Hey, I am stilling using the first preview build you released. I noticed that using the optical joystick was almost too sensitive.. It was picking up my thumb moving both forward and backwards, which was making selecting far away things really tough.
[Droid Incredible Android Development] baciv:
Just wanted to thank you, chad, for the best kernals I've ever used. I understand it may be my particular device, but Sense or AOSP, yours have remained my go-to kernals for very nearly every ROM I've ever flashed. Often recommended but too rarely praised. The quick to wake and outstanding battery life combination of the 3/18 prompted to me to stop by.
[Droid Incredible Android Development] poetzmij:
hey chad are you going to be updating to 2.6.37.5? or are you sticking with .4 for awhile or not updating at all because there is no reason too?

oh and nvm bout the stuttering problem i posted, its gone now, must have just needed a reboot or something :rolleyes:
[Droid Incredible Android Development] chad0989:
I'm still working on that. Trying to make it actually usable without being too sensitive.

The final will be .5.
[Droid Incredible Android Development] J2theMatt:
+1
[Droid Incredible Android Development] mrchambo:
+1 here as well, Chad. Thanks, man.

jc
[Droid Incredible Android Development] chad0989:
I lied, it'll be .6.
[Droid Incredible Android Development] byrong:
Chad (and anyone else who experiments with voltages),

I finally got around to testing voltage limitations on my device today. At each clock speed, I've found the voltage level at which it starts to become unstable. Now that I have that info, how would you recommend I build my table?

For example, at 128000, my phone starts to become unstable at 875. Given that figure, what min/max combo would you pick?

850/950?

900/1000?

Also, I notice (in both stock and the tables that people have posted) that some frequencies have much larger voltage windows than others. Some have a min/max that is 50v apart while others have a min/max that is 225v apart. Why? It doesn't seem to follow a pattern: both the low and high speeds have small windows while the middle speeds have large windows.
[Droid Incredible Android Development] runagt2:
Byrong, maybe you don't see a logical pattern in your voltage table because it takes a lot of troubleshooting to find precise tolerances at each clock speed, and Chad created a table that should work for all Incredibles. If you found the limits for each clock speed, that's awesome, and I'd like to see your full table after you create it!

If for example 128MHz is unstable below 875, set 875 for min and 925 for max. That 50 volt range has worked for me at frequencies I've tested, but I haven't motivated myself to check every clock speed.

My Dinc has proven pretty robust, so I bet mine can handle the same voltages as yours. Share, please.
[Droid Incredible Android Development] Gahh Its Lee:
I'd love to try as well.
[Droid Incredible Android Development] poetzmij:
Ok so I'm on preview 2 and I'm seeing tearing it isn't bad but I noticed it when I would scroll through the forums on xda app. I see three lines of tearing and its more noticeable as it slows down. Besides that I can't find anything wrong with this kernel, and honestly I can deal with the tearing just thaught it is considered as a bug.

I'm on amoled. Still I wouldn't trade this kernel for any other, its deffinitly the best for the incredible and has been since you showed up on xda.
[Droid Incredible Android Development] cu-n-az:
OK, I just flashed CM7 RC3. I

didn't

flash Incredikernel this time since the CM7 devs will only accept bug reports on RCs and ONLY if you're running the stock kernel. I figured I'd try it this way for a while and see if I can find and report any new bugs needing squishing.

The problem: I feel like some kind of cheater! Like I should be running over to the local no-tell motel to flash this or something. That's how dedicated I've gotten to Chad's kernels. Anyway, I expect to be back on the Incredikernels soon... Keep up the awesome work Chad!
[Droid Incredible Android Development] POQbum:
haha yea I haven't found a kernel that can match up to this one.

With CM7 and this kernel it's rock solid awesomesauce battery life with underclocking to 883MHz.

Be sure to report back on how CM7's new kernel is running. They're always making tweaks and I've heard it's better on battery now, would like to know how it compares without having to flash it myself
[Droid Incredible Android Development] byrong:
runagt2,

I get that Chad's tables are made to work with a broad range of Incs, but I'm trying to understand why some frequencies have a wider window than others. On the stock voltage table, for example, cpu 768000 has a min/max of 975/1200. That's a difference of 225. Meanwhile, the very next frequency of 806400 has a min/max of 1175/1225, a difference of only 50.

That's what I'm questioning: why two frequencies that are right next to each other would have such wildly different windows.

In any regard, here are the voltage levels at which my Inc starts misbehaving. These were recorded while the processor was under load.

128000: 875

245000: 875

384000: 875

422400: 900

460800: 900

499200: 925

537600: 925

576000: 950

614400: 950

652800: 975

691200: 1000

729600: 1025

768000: 1050

806400: 1075

844800: 1100

883200: 1100

921600: 1125

960000: 1125

998400: 1175

1036800: 1175

1075200: 1175

1113600: 1225

I noticed that if the processor wasn't under load, I could go one (maybe two) steps lower. As such, I'm going to try the following table for now, which is -25/+50 on the values that I recorded above:

128000: 850, 925

245000: 850, 925

384000: 850, 925

422400: 875, 950

460800: 875, 950

499200: 900, 975

537600: 900, 975

576000: 925, 1000

614400: 925, 1000

652800: 950, 1025

691200: 975, 1050

729600: 1000, 1075

768000: 1025, 1100

806400: 1050, 1125

844800: 1075, 1150

883200: 1075, 1150

921600: 1100, 1175

960000: 1100, 1175

998400: 1150, 1225

1036800: 1150, 1225

1075200: 1150, 1225

1113600: 1200, 1275

I'll report back if I run into any issues with these values.
[Droid Incredible Android Development] chad0989:
Its mostly just out of sake of being conservative. The lower frequencies tend to be able to handle pretty low voltages whereas some of the upper ones (above 768 or so) quickly start to not like them. So its sort of a way of saying, "these ones you might get away with going pretty low, but don't try to set 768 at 950, because its not going to like it at all.
[Droid Incredible Android Development] d08speed3:
When you releasing this new kernel bro I wanna flash away lol!!!
[Droid Incredible Android Development] POQbum:
This makes a lot of sense why it's like that :rolleyes:
[Droid Incredible Android Development] runagt2:
Byrong, I posted my table on pg. 165. I realize there are some huge windows for the voltages of the upper frequencies. I think I lowered all voltages system-wide, then bumped up the max voltages when it wasn't stable. See, the max voltages step up kinda steadily, but I didn't touch the min voltages.

I'll try out what you're running and see how it goes.
[Droid Incredible Android Development] Odin2347:
i see everyone messing with voltages and the flashable voltage mod wasn't stable for me i was just wondering is this kernel undervolted by default? thanks
[Droid Incredible Android Development] kall00:
Since I flashed preview 2, and maybe even before that with the 3/18 kernel, my screen has been going nuts. Detecting false touches or not detecting any touches at all. Using CM7RC3 and the preview2 kernel currently, I'm going to go back to the 3/18 kernel and see if that helps any.
[Droid Incredible Android Development] byrong:
Is there any pattern to the behavior? I.E. does it only misbehave when plugged-in? Or all the time?

And is it just the optical joystick that is registering the false behavior on screen?
[Droid Incredible Android Development] chad0989:
@kall It's the oj. Too sensitive. I need to work on it.
[Droid Incredible Android Development] kall00:
That's kind of what I suspected. Thanks for confirming it.
[Droid Incredible Android Development] OSully:
LOVE this kernel. I'm getting better battery life than the newest stock sense kernel, and I thought that was amazing.
[Droid Incredible Android Development] BarackMitzvah:
On CM7, you can set it to smartass, if I dont have it set on boot, will the kernel will do its own thing with smartass, or will is use ondemand? If so, Is it better to do this if you're okay with stock speeds?
[Droid Incredible Android Development] thisguy23:
Anyone know the min and Max mV of our phones (snapdragon v2)? The lowest I've seen is 800 and highest is 1350mV.
[Droid Incredible Android Development] POQbum:
it's smartass by default. I've heard of a couple other people using ondemand, not sure if it's a better choice or not for this kernel. Chad made this specifically for being run on smartass, so if it's running like crap with ondemand then putting it back would fix.
[Droid Incredible Android Development] byrong:
Are you asking the manufacturer's rated min/max, or the min/max that people have found stable? The two will be different, and the stable values will vary from phone to phone (just like clock speeds)

Chad's stock table in the most recent kernel goes from 900-1325, but we've had people post more aggressive tables that run min 800
[Droid Incredible Android Development] jesssiii:
IMHO, if you use ondemand, might as well stay with stock Slayher kernel. It's a great kernel and ondemand by default.

Also, IMHO, Chad's kernels are far superior, as is smartass.

;)

Incredible

ZEAM Launcher

2.15.00.09.01 Radio

Chad's IncrediKernel
[Droid Incredible Android Development] BarackMitzvah:
You guys are misinterpreting what I mean't, but you did answer my question, partly, so now I know that if I dont mess with it, it will use smartass,the second thing I would like to know is, is it best to let the kernel do its own thing?
[Droid Incredible Android Development] jesssiii:
Actually, I believe that CM7 will use ondemand default and overrides the kernel default. That's why you need to change to smartass if using CM7 (you can do it in the rom settings). Sorry for the confusion. Not sure if other roms override kernel settings.

And, yes, smartass does it's own thing once set, though I know some still mess with profiles.

Incredible

ZEAM Launcher

2.15.00.09.01 Radio

Chad's IncrediKernel
[Droid Incredible Android Development] SteveG12543:
Yes, if left alone it uses smartass and is better to let it do its thing.

Sent from my Droid Incredible running CM7 RC3.
[Droid Incredible Android Development] BarackMitzvah:
:confused::confused::confused: Conflicting ideas here
[Droid Incredible Android Development] jesssiii:
Are you using CM7?

Incredible

ZEAM Launcher

2.15.00.09.01 Radio

Chad's IncrediKernel
[Droid Incredible Android Development] BarackMitzvah:
yep, it's in my sig
[Droid Incredible Android Development] jesssiii:
Then use CM7 Settings to change to smartass, set on boot, forgetaboutit! ;)

Incredible

ZEAM Launcher

2.15.00.09.01 Radio

Chad's IncrediKernel
[Droid Incredible Android Development] BarackMitzvah:
Okay, I did that, thanks!