yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] chad0989:
http://chad0989.dyndns.org/PB31IMG.zip

This one is 2.5.0.5

Put on root of sd, boot into hboot, select yes to flash PB31IMG.zip, reboot, reflash kernel.
[Droid Incredible Android Development] invisiblek:
interesting:

ive implemented the multi touch on the aosp kernel

never had more than 2 points until i flashed back to 2.5.0.5, then i got 3 (the kernel is limited to 3 at the moment)

flashed back to the latest cwm, and im back to 2 touch points (did not reflash kernel after going to latest cwm)

i dont know what in recovery would be causing this issue, but it seems to be related to what recovery is currently running on your phone
[Droid Incredible Android Development] bast525:
Chad - the only reason I disagree with this is that it NEVER happened on either the older stock kernel, .15 I believe, OR on Hydra's custom kernel. I have literally run Hydra's for like 1-2 weeks at a time without rebooting and without this issue. I ran that kernel for months and never once had it happen. It started when I went to King's kernels, every version I tried, and has since been the plague of every custom kernel I've tried based on .17 or higher. I've gone back to Hydra several times and had no issues.

Well, if you remember, I was running the older 8-1 leaked Froyo rom. So I decided that may be the problem and have upgraded to the 10-14 OTA. I miss that apps no longer move to EMMC, but I'll live. If it happens on this Rom too I'll go back to 8-1 and just reboot every night.
[Droid Incredible Android Development] chad0989:
Yeah, we established this a few days ago (http://xdaforums.com/showpost.php?p=10100653&postcount=996) and I've been trying to figure out what in the recovery is causing the problem ever since. I've went as far as compiling the recovery from source and including a MT kernel, and that doesn't fix the issue either. With 2.5.0.5 it works, with the latest available source (2.5.0.9) it doesn't, with or without a different kernel. Plus after extracting the ramdisk from the image and looking at the contents, there seems to be no real difference in the scripts on the ramdisk image between the 2.5.0.5 recovery and later ones. So it has to be something that changed in the binaries (and therefore source) between 2.5.0.5 and 2.5.0.9. I'm going to take a snapshot of 2.5.0.5 and compile that and see if it still functions and go up one commit at a time I think until I figure out where the issue is.

Its just extremely odd in general that the recovery would affect such a thing...
[Droid Incredible Android Development] apaxi:
Yup... I was the one that figured this out. I agree it doesn't make much sense that recovery would be causing this issue, but my hunch is that it is related to the fast scroll that is in the newer CWM recoveries. Chad is doing a diff between the .05 and .09 CWM source, so that should show what has changed.
[Droid Incredible Android Development] apaxi:
Chad, I've been meaning to do this for about a month now... thanks for all of the work you have put into these kernels. I have been a fan since day one.

Confirmation: 69Y42980EW3118011
[Droid Incredible Android Development] bobby janow:
Darn, I flashed the old recovery and it was working. I thought it was only 2.5.1.4 that was doing it, so I flashed 2.5.1.2 and bam, no MT. I think I'll just wait until you figure it out and leave MT alone until you do. So for your most stable, which do you suggest at this point while we wait?
[Droid Incredible Android Development] nagasgura:
Thanks! It worked!
[Droid Incredible Android Development] Hand76:
I am sure the CPU getting stuck at 100% is a kernal/SetCPU thing.

It only happens (at least for me) when I change the govenor in SetCPU to something different than what the kernals default is.

If I leave a kernal on smartass I am fine, if I change it to Interactive after 40+ hours I get stuck at 100% again. Maybe there are also other variables, but I never had that happen on the default kernal.
[Droid Incredible Android Development] jbeitel:


Bragging rights my friend
[Droid Incredible Android Development] jbeitel:


I am not experiencing any problems with 12-23. If I upgrade to this to stay current will it do more battery draining or will you continue to develop both. Also what was 12-23 2 diff. Can I leave it on if it works or should it come off since its experimental?
[Droid Incredible Android Development] jbeitel:
Trying it now
[Droid Incredible Android Development] jbeitel:
Ok here are my 12-23-2 vs 1 results showdown

In this corner we have tried and true defender 12-23-1

Results are

Q

1332

1413

1365

1428

1254

1336

L

32.582

31.246

33.627

27.522

27.513

33.294

In the far corner our challenger weighing in at 12 oz please welcome 12-23-2

Q

1301

1222

1433

1424

1207

1409

L

22.633

23.19

26.421

17.948

26.513

30.496

Now if I only knew what the challenge was I might be able to call the fight. Chad?
[Droid Incredible Android Development] jbeitel:
12-23-2

I did notice right off the bad that charging while using 12-23-2 is slower than molasses. i switched back to 12-23-1 because of it.
[Droid Incredible Android Development] RebelShadow:
I can report that I have absolutly no issues with performance and have outstanding battery with 12-23 v.1 Battery actually improved after moving to the 09.01 radio.
[Droid Incredible Android Development] chad0989:
Been extremely busy. Have an idea for mt, just need to get a chance to try it out. Possibly tomorrow.
[Droid Incredible Android Development] JarrettXavier:
--replied in wrong thread - please delete--
[Droid Incredible Android Development] SR3TLAW:
Really weird. 5 point multi touch was working on Chad's 23, checked this thread and went back to test and only two registered. Did something change.
[Droid Incredible Android Development] apaxi:
Yes... I bet you updated your recovery through ROM manager. Revert back to 2.5.0.5 (see Chad's instructions in the OP) and MT should come back for ya.
[Droid Incredible Android Development] SR3TLAW:
Thanks. It works. I find that the 12.20 version works best. Should I just deny ROM manager an update to keep this from happening again..
[Droid Incredible Android Development] RegnierD:
So this will probably sound like a silly question, but I've never done it and I'm curious... Are there any real-world benefits to wiping your battery stats?

I've been rooted for months, flashed a gazillion different roms kernels, recoveries, and even a few radios, but I have never, ever once wiped my battery stats. In fact, I'm almost afraid to, as I get fantasmical battery life as it is, especially with my heavy use of the phone from day to day.

Would someone knowledgeable on this subject be willing to shed some light on whether I should even bother? This is really the only general use thing I'm feeling un-educated about. Thank you. :)
[Droid Incredible Android Development] bast525:
O

Happens to me even without SetCPU installed. Also, when I WAS running SetCPU, I never hanged the governor, just overclocked. CPU still got stuck after 40-70 hours
[Droid Incredible Android Development] HoochieCoo:
I have wiped so that I can see fresh battery usage stats. I also did it once to recalibrate my battery, though I don't think that is really needed. But I charged to full, did a battery wipe, then let the phone run all the way down until it shut off.

I don't know if there are other benefits, and I've never noticed that it changed my battery life one way or another.
[Droid Incredible Android Development] chad0989:
Looks like there were some sort of changes upstream with the recovery that may have fixed MT. I was messing with it, updated my sources and then everything started working. Here's a fresh build of the latest (2.5.1.8), so you can upgrade ROM manager, flash this and it won't be nagging you to flash a new recovery.

http://chad0989.dyndns.org/PB31IMG.zip

As always, place on root of SD, boot into hboot and select yes to flash.
[Droid Incredible Android Development] greatchief1:
Same here, I thought it was only my phone that did this, this especially happens using any Aosp ROMS and but just happened to me using SKYRAIDER's new Athena ROM (senseless based) along with this kernel. A battery pull took care of it but I am not sure why this happens. Not using SETCPU. At this point, I am not sure if it is a function a ROM or Kernel that I am using. Other than that, I love the charge time on this kernel.
[Droid Incredible Android Development] jbeitel:
hi, not sure if i had this problem in the past because i havent paid attention but i noticed on the 12-23 kernal, if i use anything that involves networking my battery barely charges at all during use. it charges fine when I am not using it, just noticed this now. anyone experience this?
[Droid Incredible Android Development] rynosaur:
That worked just fine--the new CM Recovery flashes your kernel and keeps multi-touch. Still, ROM Manager thinks I have 2.5.0.5 recovery installed!
[Droid Incredible Android Development] Lexus One:
Just flashed 2.5.1.8 from Bootloader. I'm running Athena with 2.6.32.27 1223-2. ROM Manager displays 2.5.1.2. My MT is still only 2 point when it used to be 5 point. Do I need to go all the way back to 2.5.0.5 to get my 5 point working again?
[Droid Incredible Android Development] chad0989:
You have to reflash the kernel after also. And yes ROM manager will think its whatever the latest recovery that that version supported was.
[Droid Incredible Android Development] bobby janow:
Yep, that worked just fine. I flashed 2.5.1.8 and went immediately to reflash the kernel. Only one reboot needed.
[Droid Incredible Android Development] rfarrah:
If you're already getting "fantasmical" battery life, I wouldn't screw with it.
[Droid Incredible Android Development] HoochieCoo:
Well I am getting 5 points now, but I get the black screen with white bars using this recovery. Is there a 2.5.1.8 for an Incredible with SLCD?
[Droid Incredible Android Development] chad0989:
I'll look into making one.
[Droid Incredible Android Development] chad0989:
Anybody want to try this and let me know if it works with SLCD?

http://chad0989.dyndns.org/PB31IMG-slcdtest.zip

Don't forget to rename it to PB31IMG.zip (remember, lowercase .zip)
[Droid Incredible Android Development] daddymac117:
Yep, that v2.5.1.8 works fine on SLCD. Multi touch registers 5 inputs, and you can still boot into recovery.

Thanks!
[Droid Incredible Android Development] chad0989:
No problem.
[Droid Incredible Android Development] rynosaur:
My AMOLED DI w/ 2.5.1.8 CM is unable to do a nandroid b/c when it comes time to mount/backup DATA/DATA, recovery states: error: unable to mount partition . . .

Any ideas as to why this issue would occur? I'm having to flip between it and RA_181 (which does NOT correctly flash kernels to allow 5-point MT) because I can't get a proper nandroid with 2.5.1.8.

Thanks, Happy New Year!:D
[Droid Incredible Android Development] 999vulcan:
Still no MT on SLCD here, with 2.5.1.8, and also can't get nandroid backup with the same error as the post above
[Droid Incredible Android Development] xShin:
It works in the sense that I can boot into recovery, but I still have 2 points of MT for some reason.
[Droid Incredible Android Development] chad0989:
Did you reflash the kernel after flashing the recovery? You have to do that.

And to everyone else, I still have to work on it. That was just a test to see if I could get slcd working. Hang tight.
[Droid Incredible Android Development] daddymac117:
Tested MT with MultiTouch Tester immediately after flashing 2.5.1.8, screenshot attached below.

Those of you who are still only getting 2 MT points, what are you checking for MT points with?
[Droid Incredible Android Development] 999vulcan:
I was using multitouch visible test
[Droid Incredible Android Development] daddymac117:
Ah ok, I just downloaded that and it works fine for me in there too.

Did you reflash the kernel after flashing the recovery like chad suggested?
[Droid Incredible Android Development] 999vulcan:
of course :)
[Droid Incredible Android Development] jumperalex:
Got multi touch working with 2.5.1.8 but now I can't run a nandroid backup. I get an error that it can mount datadata. I tried flashing back to 2.5.0.5 and backup works but after reboot it reverts to 2.5.1.8

Anyone else having an issue. Searching for CM problems hasn't proved fruitful.

Not being able to nandroid strikes me as a "bad"
[Droid Incredible Android Development] rynosaur:
I just posted that same issue and for those of us who jump roms on a daily/hourly basis, it is 'bad', tho we must remember, all this gravy only exists b/c of Chad, Koush, et al . . .
[Droid Incredible Android Development] HoochieCoo:
I used Rom Manager to flash back to 2.5.1.2 and it worked. It also works fine with SLCD. I was also able to do a nandroid backup.

Edit: 2.5.1.2 doesn't allow 3/5 multi point on my device, but it appears to work just fine, which is infinitely more important. ;-)
[Droid Incredible Android Development] chad0989:
Fixed the nandroid issue, give this one a shot.

http://chad0989.dyndns.org/PB31IMG-slcdtest2.zip

Remember:

Rename to PB31IMG.zip (lowercase .zip), place on root of SD, boot to hboot (vol down + power), select yes when it asks if you want to start update. Boot to recovery, reflash kernel.
[Droid Incredible Android Development] jumperalex:
chad, is that file good for non slcd incs?
[Droid Incredible Android Development] chad0989:
yes it is.
[Droid Incredible Android Development] jumperalex:
ok i did it. now i can run a backup directly from reovery BUT ... when i try to run it from Rom Manager I get

E: Can't mount /dev/block/mmcblk0p2

(File Exists)

E: Can't mount CACHE:recovery/command

That left me sitting in recovery at which time I told it to backup and it worked. I rebooted and then tried another backup via Rom Manager but got the same error. A bit of searching showed me some comments about not having an EXT partition but I've never had one and never had this error ... or at least I never noticed it and it never stopped the backup process before from Rom Manager.
[Droid Incredible Android Development] chad0989:
I'm working on this, but it may take awhile to figure out. I would recommend for now though just to not use ROM manager, just boot into recovery to do your backups/flash manually.
[Droid Incredible Android Development] Hand76:
Chad is there anyway we could get a new kernal with a different governor? Interactive works great.

This smartass governor is terrible on battery life.

I am monitoring the cpu in setcpu and system monitor and the cpu never sits down and stays in the 245 mhz range. Its always bouncing around to 475, 768, up to 998 mhz just with the phone sitting idle.

Anyway thanks again for all your hard work but please ditch smartass.
[Droid Incredible Android Development] jwood:
My battery is great with the below kernel, I have the same kernel on my wifes phone an it also jumps all over at idle but again battery is good! Average 16 hours a day battery life...

Running SkyRaider 3.5 Incredible Rom with Chad 1213.2 kernel & Uncommon "color" rosie pack.
[Droid Incredible Android Development] chad0989:
You must have a background process somewhere that is using cpu causing it to scale up. Mine will settle at 245 after five or ten seconds and stay there.

Also don't look at the info tab under setcpu, it seems to report the frequency wrong. The main display is correct though.

But anyway, if you really don't like smartass you're free to change it with setcpu or the like. You'll have to set a screen off profile also then though.
[Droid Incredible Android Development] Hand76:
Hmmmm I understand what you are saying about backround proccess running but it doesn't happen as much when I change governors (inregards to the cpu jumping around)

But I don't like changing the kernal as that has led to me having problems with my cpu getting stock at 100% after the phone has been on for 40+ hours.
[Droid Incredible Android Development] jumperalex:
Ok fair enough. I was just getting worried it was a problem with my phone (read: I screwed something up). Thanks for everything!!!
[Droid Incredible Android Development] BillLee3:
Chad - I'm trying to follow this, but am losing track of what you are posting.

The most recent posts of various PB31IMG. Are they kernels? Are they fixes for recoveries after installing the most recent recoveries or what? Sorry for being obtuse.

Had tons of trouble with earlier 2.5.1.x recoveries. Am stable with 2.5.0.5 and before I do ANYTHING I want to make sure I understand exactly what it is you are saying to do to get stable at some higher version of your kernel, clockworkmod recovery and ROM Manager.

Thanks!

Oh, I have a non-slcd if it makes any difference....
[Droid Incredible Android Development] chad0989:
They're recoveries. You flash them through hboot. Theres no real need to update from 2.5.0.5. I'm messing with them more for the slcd guys so they can have multi touch.
[Droid Incredible Android Development] Lexus One:
I am using CMR 2.5.1.2 on my AMOLED DI and still only have MT 2 point. CMR 2.5.1.8 does get me back to MT 5 point, but it won't allow me to do a nandroid back up. I assume this is what (you said) you were working on...a working version of 2.5.1.8 that both backs up and supports MT 5 without having to go all the way back to CMR 2.5.0.5. Please correct me if I am mistaken.
[Droid Incredible Android Development] chad0989:
Yes, that's the plan.
[Droid Incredible Android Development] EnixLHQ:
Just an update:

Using both the 12232010 and the 12232010-plus25v I still experience random reboots.

The 12232010 can be narrowed down to events that occur when the screen is off. While off, going off, or coming back on, there is a reasonable chance the phone will lock up. Typically, it occurs when the screen comes on from sleep. The screen will lighten, show that an event happened, and then hang. The screen will continue to time out and eventually dim, and then turn off. If you interact with the phone during this time, your inputs are not registered, the screen still turns off eventually. When it turns off, hitting the hardware button to turn it back only lights the capacitive buttons at the bottom. Screen stays off.

The plus25v has a similar issue, but it differs on when it reboots. It reboots during the dimming stage of the screen off process. Or, when plugged in and the phone is set to always be on while on the charger, it will reboot while the screen has been dim for a couple of hours.

In terms of uptime, the non-plus25v last longer before it reboots and seems to avoid the dim screen problem the plus25v has.

For reference, the stock kernel on my rom, SkyRaider (link in sig) is the HTC kernel and is the most stable. When it reboots, it's very rare (average of a week to two weeks with me constantly changing elements on the phone) and also does so during screen off events.
[Droid Incredible Android Development] ilhe1s:
Chad,

I need my fix!

New Kernel Soon Please! :D
[Droid Incredible Android Development] chad0989:
Can someone with an slcd try this out?

http://chad0989.dyndns.org/PB31IMG-slcdtest3.zip

Same as always. Rename to PB31IMG.zip (case sensitive), place on root of SD, flash through hboot, reflash kernel.

Also, sorry for the lack of updates, been extremely busy so things are going to slow down for a bit, I'm still working on it when I get chances to though.
[Droid Incredible Android Development] turboguy:
Hey Chad,

Just tried this version out. It seems to break the touch screen. I tried with both 12232010 and the 12232010-plus25v kernels. It boots up fine and then sits on the lock screen. I can't interact with the device at all, it's not frozen though, as I can see the notifications icons changing (like the sync icon).

Thanks for all your work!
[Droid Incredible Android Development] turboguy:
Update on my previous post:

I started to get freaked out because I flashed back to your slcdtest2 recovery and my touchscreen was still not working. I was about to try Amon's recovery and see if it would work, but instead I decided to flash another kernel. So I flashed Lou's v4 kernel and suddenly my touchscreen worked again. So I decided to play around a little:

1) Flashed slcdtest3

2) Flashed Chad's kernel - Resulted in no touchscreen

3) Flashed Lou's v4 kernel - My touchscreen was back

4) Flashed Chad's kernel again - No touchscreen again

5) Flashed Lou's v6 (multitouch) kernel - Still no touchscreen

6) Flashed Lou's v4 kernel - Touchscreen works again

7) Flashed Lou's v6 kernel again - Touchscreen is broken again

8) Flashed slcdtest2

9) Flashed Chad's kernel - No touchscreen

10) Flashed Lou's v6 kernel - No touchscreen

11) Flashed Lou's v4 kernel - Touchscreen is back

12) Flashed Chad's kernel - Touchscreen continues to work...

So there seems to be something in the multitouch kernels that is conflicting with this recovery and it seems to persist until a non-mt kernel is flashed. I'm not sure what all this means, but maybe it can help.

Just FYI, I do have an SLCD and have never been able to get >2 finger multitouch to work.
[Droid Incredible Android Development] chad0989:
Okay. Thanks.
[Droid Incredible Android Development] chad0989:
Another SLCDer want to give this one a try?

http://chad0989.dyndns.org/PB31IMG-slcdtest4.zip

Same instructions as above
[Droid Incredible Android Development] Dmtalon:
I have an amoled Inc and have been on the 12/23 for a while now. Last week my phone started random rebooting every couple days. Upon reboot, I have no touch screen "after" I slide to unlock. After 20sec it reboots, back to the no touch screen after unlock. Happens until I pull the battery.

At the gym last night I put your 12/13 back on my phone. only been 24h, but we'll see how it does in a couple days.
[Droid Incredible Android Development] firestorm126:
I tried it with 12/13/10-2 and no dice on multitouch, touchscreen works with 2 though. Also I've never had more than two, SLCD.
[Droid Incredible Android Development] chad0989:
You reflash the kernel after flashing the recovery?

Also anybody else try it? Need to know if anyone with an slcd has mt with it.

Amoled people can use it too. It fixes the ROM manager issues. ROM manager will still report .2 not .8. That's a ROM manager thing.
[Droid Incredible Android Development] firestorm126:
Yep I reflashed after loading new cwm. Also tried Lou's #6 as well. My ROM Manager shows .2 but loading cwm shows .8 (as you said). Oh and I'm on Sky Raider 3.5 if that helps with data collection. I'll be glad to test more for you.
[Droid Incredible Android Development] grokdesigns:
Applied the CWM fix and reflashed kernel. Still only 2MT points. Running SR3.5 on SLCD.
[Droid Incredible Android Development] turboguy:
Funny, I just tried this one as well and I get the same results as with slcdtest3. My touchscreen doesn't work until i flash a non-mega-multitouch kernel. I would have thought all SLCDs would have the same result.

I'll keep trying them though, thanks!

[EDIT] I am using a different ROM however, I'm on VirusROM Revolution 1.2
[Droid Incredible Android Development] chad0989:
Does the regular pb31img-slcdtest.zip from chad0989.dyndns.org give you guys multi? Note that it has issues with ROM manager so do everything straight from the recovery after you flash it.
[Droid Incredible Android Development] turboguy:
I wasn't able to try the first slcdtest. I think you took it off your site? But I've tried slcdtest2-4 with no luck.
[Droid Incredible Android Development] chad0989:
Here's another to try out:

http://chad0989.dyndns.org/PB31IMG-slcdtest5.zip

This would be a lot easier if I had an SLCD. Haha.
[Droid Incredible Android Development] jumperalex:
Fixes which problem? I have two:

1) can't nandroid from RM

2) when recovery boots I get mounting errors (mentioned above) but then nandroid works

I'm guessing #2 causes #1 but it seems odd that I can still manually nandroid and of course I'm not feeling confident that nandroid is actually getting everything anyway when I see that some things won't mount.
[Droid Incredible Android Development] chad0989:
Fixes both
[Droid Incredible Android Development] firestorm126:
Still no MT, tested with 12/23-2. I'm wiping the cache and dalvik before and after loading the kernel zip.