yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] baciv:
OK. First, I recommend wiping the cache (dalvik not necessary) when flashing a kernel. Second, Virtuous 3.2 _includes_ a new kernel, so if I read this correctly you've flashed two kernels in two days; tough to nail down where your problem may lie. Third, of course, when you flashed 3.2 you would want to have done a complete wipe.

My suggestion is that you do a full wipe, flash Virtuous 3.2, and then run that a while and see how you like it with its native kernel. You can then always flash chad's latest afterward.

Others may know better.
[Droid Incredible Android Development] rockehill10:
You might also try going into ROM Manager and under Utilities, click Fix Permissions.
[Droid Incredible Android Development] wraithdu:
Just thought I'd post a few thoughts from over the weekend.

I was noticing some sub-par battery life while the phone was off over the last week. I kept an eye on it for about 4 or 5 days on the 12/13-2 kernel (I do not bump charge). I had previously removed SetCPU, so I decided to try and re-enable it. I set a screen off profile of 245/384-conservative and screen on of 245/998-ondemand. I noticed the screen off battery life was much better. After about a day, I noticed the phone was very sluggish. I opened SetCPU and noticed the cpu speed was stuck at 400 something. Eh? Apparently the ondemand governor is not scaling at all. It gets stuck at whatever freq was set when it was enabled. Switching back to smartass enabled scaling again.

In the end I have a screen off profile of 245/384-conservative, and screen on of 245/998-smartass. The phone has been running great with no noticeable unlock or screen preview lag.
[Droid Incredible Android Development] DaGunn:
Do you have any other power saving/memory optimizing apps running? I know that SuperPower changes governor/cpu speeds. If you have System Panel set it to monitor apps, you will find cpu hogs that way.

I have been setting default governor for screen on/off to ondemand and it does indeed scale quite nicely.
[Droid Incredible Android Development] wraithdu:
Nope, no other power mgmt or task apps of any kind.

... Oh what the hell... NOW it's working fine. I swear I sat there and played with it for like 5 minutes and reproduced the problem consistently while changing gov's around.

Eh, whatever. My previous point about using a screen off profile set to conservative still stands, it produced better screen off power consumption for me.
[Droid Incredible Android Development] chad0989:
Try this one out.

3/5 point multi-touch and some other stuff

http://chad0989.dyndns.org/2.6.32.27-incredikernel-12202010-2_signed.zip

Download the multi touch test app from the market to test.

Should work for everybody (as in nobody should have a non-responsive touchscreen), you'll get either 3 or 5 points depending on what hardware you have.

Why 5? Because tracking the points gets worse after that point. And in reality, can you fit more than 5 fingers on your screen for anything useful?

EDIT: Fixed wifi
[Droid Incredible Android Development] Divine_Madcat:
The new kernel works great on skyraider 3.5,multitouch and all.
[Droid Incredible Android Development] ilhe1s:
Just installed the 12-20-2010 and I get 5 points on my Stock Rooted Inc. with AMOLED screen. Will post more later on my findings and any issues.

Will def have to play some SNESoid to try this 5 pt MT out.
[Droid Incredible Android Development] mmmark111:
Only two points here :(
[Droid Incredible Android Development] chad0989:
On 12/20?

Can you do a:

adb shell cat /sys/android_touch/vendor

or if you have a terminal emulator installed on your phone just

cat /sys/android_touch/vendor

and tell me what output you get? Also go to "about phone" and then "hardware information" and tell me what it says for hardware version.

This goes for anybody who gets less than 3 points or an unresponsive touchscreen.

Theres a possibility that some hardware only supports two points. Whats most important is that its enabled on what devices it can be but doesn't make the touchscreen unresponsive on those that don't support it.
[Droid Incredible Android Development] mmmark111:
I get ATMEL_x0080_x0016
[Droid Incredible Android Development] xShin:
If you don't mind me asking, what exactly did the "some other stuff" consist of? Or if you had reasons for not saying just yet, that's fine too, I'm just curious :P
[Droid Incredible Android Development] Gahh Its Lee:
Is the new kernel basically the 12/13-2 with the multi touch? I'm curious before I flash it.
[Droid Incredible Android Development] texanaustinite:
Same here, along with Hardware version 0002. Only two points.

Running Nils' Desire-Z Rom. Could it be due to the ROM?

mmmark111, what are you running?
[Droid Incredible Android Development] mmmark111:
I'm running a custom rom that I made based off the latest stock from rmk40.
[Droid Incredible Android Development] Nevilshaze:
When I load the 12-20-2010 one I do not have wifi, it just says error in the settings menu. Had to restore a nandroid to fix anyone else having this issue or have any idea how to fix using this kernel? I had 5 Points in the Multi-touch tester while I had this kernel installed.
[Droid Incredible Android Development] Divine_Madcat:
I have the same Amtel hardware and HW version 0002, but the 5 points works for me; no glitches found anywhere. I am running Skyraider 3.5 w/ Uncommon pack.

What i suspect, is that the ROM's built on non-Incredible framework may be bhorking things up a bit. The Desire Z roms were never quite there for me, and I would not be surprised is this is the source of the issue..
[Droid Incredible Android Development] chad0989:
Fixed, sorry about that:

http://chad0989.dyndns.org/2.6.32.27-incredikernel-12202010-2_signed.zip
[Droid Incredible Android Development] chad0989:
Its my work-in-progress source. Patched up to 2.6.32.27, multi-touch, and some updated drivers.
[Droid Incredible Android Development] amonra50:
I have the hardware 0002 AMOLED as well, running skyraider 3.5 and I'm only getting 2 touch points. I've wiped cache, and dalvik prior to kernel install; tried installing the 12202010-2 test kernel twice. I only show 2 touch points in the multitouch test app. Same deal with lou's multitouch 3-10 sense kernal; only 2 points but otherwise everything else is working normally.

I'm not sure what could be different about my setup that would prevent the multitouch for working. I've themed my framework a bit but only by swapping out some of the green pngs in the stock skyraider 3.5 framework-res.apk and com.htc.resources.apk, no changes in the code or anything, just green pngs to red pngs. Could some app I have installed be preventing the multitouch 3-5?

Madcat, by looking in my sig, is there anything that jumps out that may be significantly different from your setup? particularly the radio and/or hboot. obviously, disregard the kernel listed as I'm currently trying out chads 12202010-2
[Droid Incredible Android Development] chad0989:
It really is entirely possible that there's hardware out there that only supports two touches. That's probably the reason that its defaulted to two. What we're trying to figure out is what exactly it is that is limiting the support.

Also look at my earlier post and post what touch panel version you have not just hardware version.
[Droid Incredible Android Development] Gahh Its Lee:
I tried the first new kernel and it gave me five points but no wifi or 3g and then I flashed the second one and got wifi and 3g but only two points. Also when I flashed back to the 12/8 kernel I got force closes like crazy. I always wipe dalvik and cache when flashing. But I did get five points with the original 12/20 kernel. Hope that's helpful also I have the amoled model running virtuous 3.1. Hope this is helpful.
[Droid Incredible Android Development] amonra50:
I have:

ATMEL_x0080_x0016

I'm going to backup my current setup, do a full wipe, and reflash the skyraider35.zip that should get me back to a good baseline. I'll then install this 12202010-2 test kernel and we will see what happens.
[Droid Incredible Android Development] C4H1LL:
yea i have x0080_x0016 and hw version 0002 and am running virtuous v3.2.0 with only two touch points. do you guys think it has something to do with what kernel you flash the new one from? for instance, do u think it matters that i flashed the 12/20 test over virtuous v3 kernel? i cant make any sense out of why it works for some and not others when the atmel hardware or hardware versions are the same? im flashing SR 350 from a full wipe now and gonna install the 12/20 kernel but im gonna be kinda pissed if it doesnt work..

i have hboot .92 and radio 11.19
[Droid Incredible Android Development] amonra50:
Still only 2 touch points after a full wipe and fresh skyraider35 install. bummer.
[Droid Incredible Android Development] Gahh Its Lee:
Did anyone else get five points with the 12/20 kernel then two with 12/20-2??
[Droid Incredible Android Development] Nevilshaze:
No I was getting 5 with the 1st 12-20-2010 then like you sd no wifi/3g i restored to a prev nandroid backup then installedthe 2nd 12-20-2010 still have 5 points. I have stock sense rom w/ latest update
[Droid Incredible Android Development] DaGunn:
You didn't mention anything about whether you now have wifi/3G?
[Droid Incredible Android Development] Nevilshaze:
Yes Both wifi and 3g are working. I havn't noticed any other issues either.
[Droid Incredible Android Development] Gahh Its Lee:
Yea sorry I have 3g and wifi on the second kernel but only two points so I have no idea.
[Droid Incredible Android Development] chad0989:
You try re-flashing and trying again? Because there were no changes at all in the kernel, I just rebuilt it and repackaged it because I had an old wifi module in there.
[Droid Incredible Android Development] amonra50:
I have turned up two different incredible touch digitizers from photos online, possible more out there as well.

One has this number:

0079 rev:3 fpc-1

http://www.amazon.com/ORIGINAL-HTC-VERIZON-INCREDIBLE-DIGITIZER/dp/B004AOX57C

Another has this number although the bezel says HTC in the top center when ever other one I've seen says verizon: chinese knockoff bezel I would guess:

0079 rev:3 fpc-2

http://www.ecrater.com/p/9248074/droid-incredible-by-htc-ace#
[Droid Incredible Android Development] DaGunn:
DELETE that old wifi module! LOL
[Droid Incredible Android Development] crombej:
Boot Loops for Breakfast!

Hi,

I have SR 3.5, distINCtion v1.50, had the stock .17 kernel and flashed Chad's 1220-2 from the OP link. Downloaded it, then went into ROM Mgr and chose Clear Cache and Backup and installed it. All looked good during the CWR (2.5.0.5) backup & install, then it rebooted and it just keep boot looping.

Pulled the battery and then booted into recovery and tried clearing the Dalvic and Cache and then rebooting but it still loops. Restoring my nandroid (doing that now) and hope to be back where I started.

Did I do something wrong? I thought that was how I've installed the other Chad kernels in the past.

Thanks!

JC
[Droid Incredible Android Development] chad0989:
Also would anybody who has ATMEL_x0080_x0016 but only 2 touch points be willing to try a different (or even stock) rom and see what happens so we can eliminate a rom issue.

It might help also if we know who has working 3/5 point and what their hardware is.
[Droid Incredible Android Development] chad0989:
May be on to something there. I wonder how hard it is to disassemble these and check...
[Droid Incredible Android Development] amonra50:
easy if you wanna break a void sticker and thus break any kind of warrenty. there is a sticker over one of the screws you need to remove.

Anyone who has this working wanna crack open their device??? didnt think so... anyone know anyone who has had to replace a digitizer yet?

http://www.youtube.com/watch?v=lr4uy9yKqIE

I've think I've seen a third digitizer that appears to be missing the numbers listed above but has a 2d barcode instead. let me go back and take a closer look.

Pause this around the 2.07min mark to see the barcode. Although this one seems to have some kind of a bump for lack of better term on the side of the ribbon when the other ones dont have this extra material in the ribbon.

http://www.youtube.com/watch?v=eF-Nztd24eI
[Droid Incredible Android Development] C4H1LL:
ive tried it on the new virtuous and on SR 350 and stioll a no go. i have x0080_0016 and hw 0002.
[Droid Incredible Android Development] chad0989:
I'd be willing but I have ATMEL_x004F which is good for 3 and isn't where people are having issues.
[Droid Incredible Android Development] amonra50:
Yup, now I have seen two digitizers with the same ribbon but different numbers printed on them as well as a third digitizer where the ribbon physically has a different shape to it then the others while still ending in what appears to be the same connection.
[Droid Incredible Android Development] jprow507:
I have always simply cleared dalvik cache only. Sorry for the noob question, but is it necessary to clear cache as well from recovery? And in doing so, does that wipe my data and settings or is it just temporary cache?
[Droid Incredible Android Development] amonra50:
in the end a couple incredibles may have to be opened up to figure out why this works on some devices and not on others...
[Droid Incredible Android Development] byrong:
5 points works flawlessly for me: I'm actually impressed watching the testing app track the 5 inputs.

As for my phone's info:

/sys/android_touch/vendor reads ATMEL_x0080_x0016

Hardware version under "about phone" reads 0002

ROM: Sense(less) rEVOlution ROM

Still too early for me to comment on any other performance aspects of the new kernel.
[Droid Incredible Android Development] GideonX:
Same, except I'm running SR3.0 rc3, 5 tracking perfectly.
[Droid Incredible Android Development] ilhe1s:
I have 5 point MT on:

HTC Incredible

AMOLED Screen

Vendor: ATMEL_x0080_x0016

Hardware Version: 0002

I have a Stock Sense ROM Build # 3.26.605.1

I have removed BloatWare and added Chad0989 12-20-2010-2 Kernel

"Hope This Helps"
[Droid Incredible Android Development] C4H1LL:
any idea why some will do it and some wont?
[Droid Incredible Android Development] Gahh Its Lee:
I've tried reflashing twice. For some reason I only get more then two points with the original.
[Droid Incredible Android Development] 29629:
HTC Incredible

Hardware rev 0003 (SLCD)

Unrevoked s-off + Forever

rom: Skyraider 3.5 + Uncommon "color" rosie pack

kernel: Chad's 2.6.32.27-incredikernel-12202010-2

recovery: ClockworkMod 2.5.0.5

radio: 2.15.00.09.01

hboot: 0.92

Terminal Emulator Readout: AMTEL_x004F_x0016

I only get the two points on the multi-touch tester. Tried to clear cache&dalvik cache and reflash. Still only got the two points.
[Droid Incredible Android Development] C4H1LL:
your lucky you ever got more than 2 lol
[Droid Incredible Android Development] Gahh Its Lee:
Yea I have no idea I get five points oon the original kernel whenever I flash it... rather odd
[Droid Incredible Android Development] C4H1LL:
what set up do you have? SLCD?
[Droid Incredible Android Development] Gahh Its Lee:
Amoled and I'm running virtuous 3.1

Its odd that only the one works but yea...
[Droid Incredible Android Development] bast525:
Dammit dammit dammit!!!! This finally did happen to me again!!! I NEVER had this happen on the stock kernel or on Hydra's 1.15 kernel, both of which I've run for weeks without rebooting and had no issues.. But every one of King's kernels, Ziggy's kernels, and Adrynalyne's kernels have done this to me, and now Chad's 12-13.2. After 52 hours of run time, the CPU pegged 100% and the phone became almost completely unresponsive. I saw this on System Panel, and tried ending ALL apps, even system apps, but it didn't help, CPU was peged at 98-100% load and full speed. I let it sit for 5 mins to see if it wasn't just something running that would stop, but it never did. I had to reboot.

I seem to remember running 12-8 for about 5 days straight and never had this happen. It sucks because I really, REALLY liked the 12-13.2 kernel, such great performance. I'm gonna go back to 12-8... I can't remember now if I had any issues with it but I seem to remember being pretty pleased with it. I think any of the kernels before that were the ones I had issues with them freezing completely on boot up (at stock CPU speed, no SetCPU). If 12-8 locks up or pegs 100% on me, back to the slower charging, battery killing, non-GPU+ having, yet 100% rock solid stable Hydra kernel :(
[Droid Incredible Android Development] mirwolf:
Works great! All 5 points.

HTC Incredible

AMOLED Screen

Vendo - ATMEL_x0080_0016

Hardware Version - 0002

Rom - MYN Warm Two Point Two RLS4
[Droid Incredible Android Development] TheLynxy:
ATMEL_x0080_x0016, hardware 0002, SkyRaid 3.3.4, and all is great. Quadrant 1450 and all 5 points working beautifully. I never in my wildest dreams thought my Incredible would support more than 2 points - THANK YOU!
[Droid Incredible Android Development] 29629:
Chad, for what it is worth, just for testing purposes i tried flashing LOu's new kernel. Same outcome...only two points on the multi touch, but my quadrant scores were about 200 points lower
[Droid Incredible Android Development] Muerte_X:
This is exactly my setup, and with the 12/20 test kernel, I still only get 2 with either multi touch app.

I've also tried the #6 and the heyitslou kernel and none get more than 2...
[Droid Incredible Android Development] C4H1LL:
me too, god damnit, i wish it wasnt so random so we might be able to fix it, but at this point i dont even think the devs care who has it or who doesnt, it seems impossible to fix. i would like to have it when EA starts rolling out their games though.. fingers crossed! anyone with any idea wtf is up with it?
[Droid Incredible Android Development] chingy51o:
so may sound dumb but how do you tell how many points of touch you actually have? i flashed lous #6 and have no idea what im looking for... haha
[Droid Incredible Android Development] ptsmith24:
I think this is the one everyone is using:

I found this great Android app 'Multitouch Test' on AppBrain: http://www.appbrain.com/app/de.greenrobot.multitouchtest
[Droid Incredible Android Development] TheLynxy:
That app has really big dots lol. I personally use http://www.appbrain.com/app/touch-test/org.hermit.touchtest
[Droid Incredible Android Development] chad0989:
deleted...
[Droid Incredible Android Development] HoochieCoo:
I have this problem with these kernels every time I use SetCPU to change the governor. I just ended up uninstalling SetCPU and haven't had a problem since. No biggie... the smartass setup in this kernel is more than good enough for me so far.

EDIT: I did not have any issues with this when I was running KingxKlick BFS #5. I didn't try #6. Haven't run any Adrynalyne kernels.
[Droid Incredible Android Development] Muerte_X:
I don't know, it sounds like they care...2 people that make kernels have tried to incorporate it into their kernel and asked for feedback.

If I had to guess, it's probably something specific about our phones, maybe the multitouch will never work. Since HTC never planned for it to work, they probably didn't test it to make sure it worked on every screen.

I think it's cool, but I can live without it. Right now nothing takes advantage of it. I'm just happy we have so many kernels to choose from right now. Not that long ago we had 1 choice other than stock.
[Droid Incredible Android Development] chad0989:
Exactly this. My hypothesis is that HTC only ever intended 2 point, no more, so in some revisions of the phone some of the pins on the controller aren't being utilized. If you look in the source there are 3 versions of the controller that HTC used, and we have exactly 3 scenarios when we enable more than 2 touch points. 1) It works to its fullest potential, 2) We get 3 points, if you set more you get an unresponsive screen, 3) Get 2 points no matter what.
[Droid Incredible Android Development] csseale:
Yea makes sense and in all honesty more than two is pointless on a phone anyway. Yea for some games it would be nice but noone is gonna develop for more than two anyways
[Droid Incredible Android Development] Divine_Madcat:
Looking at the flood of different responses, that scenario seems to work, but it begs the question as to why HTC was so random about it. Could it be that when filling the flood of back orders, they were forced to reduce quality control or chip suppliers leading to three different types/configs of touchscreen controlers?
[Droid Incredible Android Development] chad0989:
I wouldn't say quality control, but obviously different versions of the controller -> different configurations. And theres always the possibility that they were trying to reduce manufacturing cost somewhere. I'm going to leave the config in since its not causing anybody to have an unresponsive touchscreen. So those who are lucky enough for it to work get it and those who aren't, well thats how it goes.

Plus really if you ask me its more of a novelty thing anyway. I've honestly never had any need/desire to use more than 2 touches.
[Droid Incredible Android Development] skorpios1027:
Chad,

First off, thanks for the great work. I just flashed the 12/20-2 coming from 12/08. I do get the 5 point MT (too cool, but rather superfluous). I have the x0080_x0016 AMTEL and running SkyRaider 3.5. I do use Set CPU but leave the governor alone and (at least with 12/08) have had no complaints. Will report back after giving 12/20 a good run.

Thanks again!
[Droid Incredible Android Development] bast525:
I've had the problem with and without SetCPU installed. In this most recent case with the 12-13.2 kernel, I was using SetCPU to overclock, but had NOT changed the governor, nor had any profiles or anything else. Just overclocked to 1.13. I've run Hydra at 1.15 stably for long periods of time so it wasn't the overclocking that was causing the instability, at least I don't think so?

When the phone started to chug really badly, I opened SetCPU, changed the max speed back to 998, unchecked set at boot, and then closed and uninstalled it, just running the kernel as it is. I had the same problem. I don't know what is so different from the Chad/King/Ziggy kernels, and the stock and Hydra kernels... but whatever it is, all custom kernels other than Hydra give me the same issue....
[Droid Incredible Android Development] sonypete:
Am I able to overwrite the screen off speed with setcpu. I'm having issues with music playback getting stuttery with the screen off when background process are trying todo its thing. This shouldn't be hard set like this if setcpu can't be used to overwrite these values.

=========================

Screen on minimum 245mhz

Screen off maximum 245mhz

=========================

- Pete
[Droid Incredible Android Development] chad0989:
I have something coming in about 5 minutes that might just fix that... and help battery life (well at least while not playing music) to boot.
[Droid Incredible Android Development] chad0989:
12/21 test kernel:

128/384 screen off and possibly better scaling in general

Lowered 128/245/384 voltages

Some driver updates

I'm going to leave multitouch in since its not causing anybody to have an unresponsive touchscreen. So those who are lucky enough for it to work get it and those who aren't, well that's how it goes.

http://chad0989.dyndns.org/2.6.32.27-incredikernel-12212010_signed.zip

Give it a shot. I like this one.

Biggest thing we're looking for here is any instabilities because of the lowered voltages and the effectiveness of 128/384 over 245/245. Hopefully 128/384 will provide better or the same battery life but will not delay texts/calls and work better for playing music etc with the screen off since it will be able to scale up to 384.
[Droid Incredible Android Development] 29629:
Running new kernel since you posted it. GREAT battery life but few people have complained that they called and i have no missed calls. Personally, think 245 is better than 128