• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root SLCD kernel... PLEASE HELP!

ErisEscalavee

ErisEscalavee

Newbie
I have an SLCD Incredible. I am rooted, but having the SLCD screen, when I flash a ROM, I lose all function of the touch screen because most ROMs do not have the SLCD drivers, they have the AMOLED drivers. The ROM installs perfectly fine. i have called the phone with ROMs on it, the phone rings, I see the number, but no touch screen. I have been searching for 2 days for a kernel that is compatible with SLCD and will install the SLCD drivers, but I have had no luck at all.

Any suggestions? Anyone else experience this?
 
I am using Clockwork Recovery v2.5.1.2
HBOOT-0.92.0000
S-OFF
Touch Panel-ATMEL224_20aa
Radio-2.15.00.07.28

I have no problems in recovery. I have no problems with HBOOT. I do everything from HBOOT/recovery, (no ROM manager). The ROM flashes and works (I can see notifications changing, calls can come in and I see the caller, and I can receive texts). The only problem is no touch screen once the ROM is on there.

I have only flashed super-Z and warm two point two, and I have tried flashing incredikernal hoping it would install SLCD drivers... no dice.

I am about ready to unroot and give up. I have been searching for 2 days straight (literally... I was up until 4 am and back at it all day today). I don't want to keep flashing different kernels and ROMs because I have read of people killing their SLCD screens. I don't want to do anything without researching and reading, but I can't research something that no one has experienced! No one seems to have ever had this problem, so I can't find a fix. The only suggestions have been to try kernels, most of which I can't find.

ETA: When I restore to stock I have all touch screen function.
 
My SLCD has had just about every ROM in the list on it and dozens of different kernels and I have never had this happen.

Did you mess with the ROM's before flashing them?
Are you clearing cache before flashing?
Are you using AOSP kernels with non-AOSP ROM's?
 
m411b said:
My SLCD has had just about every ROM in the list on it and dozens of different kernels and I have never had this happen.

Did you mess with the ROM's before flashing them?
Are you clearing cache before flashing?
Are you using AOSP kernels with non-AOSP ROM's?
Click to expand...

No, I haven't done anything to the ROMs.

I am wiping data/cache/dalvik before flashing.

I am using kernels recommended by the dev and users of the ROM.

I am thinking I may unroot and start over, possibly installing Amon-Ra recovery instead of Clockwork. Something may have gotten screwed during rooting... Naaahhhhh... It HAS to be something with the SLCD drivers. Rooting just gives me recovery and root access. This is driving me nuts!
 
ErisEscalavee said:
Naaahhhhh... It HAS to be something with the SLCD drivers. Rooting just gives me recovery and root access. This is driving me nuts!
Click to expand...

I would tend to agree. This is one of the oddest issues I've seen in some time. And it seems you are indeed alone on this for the most part. I spent some time searching and about all I came across was your threads on mulitple Droid forums.

I have been racking my brain on this one and I am coming up with nothing. It almost seems like you received the wrong display for this device or something yet it works with stock. Hboot and radio up to date and even if they weren't, what the Hell would they have to do with touch screen functionality?

I mean it's almost like you have some top secret experimental device here that they sent out by accident. And what are you gonna do..."hey can I get a replacement phone cuz when I root and load any custom rom, my screen breaks?" :p

There's just one crazy idea you might try, it's the only thing I can think of. Try a different SD card in the phone. It's the only thing that makes even the slightest sliver of sense to change outside of a new phone or getting incredibly lucky and finding a particular kernel that works and if you do find one, I'd call it a shear accident because to my knowledge, nobody is deving for this issue b/c nobody else has it.

I'm still thinking but my brain hurts.
 
iowabowtech said:
I would tend to agree. This is one of the oddest issues I've seen in some time. And it seems you are indeed alone on this for the most part. I spent some time searching and about all I came across was your threads on mulitple Droid forums.

I have been racking my brain on this one and I am coming up with nothing. It almost seems like you received the wrong display for this device or something yet it works with stock. Hboot and radio up to date and even if they weren't, what the Hell would they have to do with touch screen functionality?

I mean it's almost like you have some top secret experimental device here that they sent out by accident. And what are you gonna do..."hey can I get a replacement phone cuz when I root and load any custom rom, my screen breaks?" :p

There's just one crazy idea you might try, it's the only thing I can think of. Try a different SD card in the phone. It's the only thing that makes even the slightest sliver of sense to change outside of a new phone or getting incredibly lucky and finding a particular kernel that works and if you do find one, I'd call it a shear accident because to my knowledge, nobody is deving for this issue b/c nobody else has it.

I'm still thinking but my brain hurts.
Click to expand...


Thank you, I appreciate someone sharing my brain racking! I had one person tell me that it happened to him on the CM forum. He suggested I try a CM build, so that is downloading now. If this doesn't work, I am going to unroot, because there is really no point if I can't mod it how I want, you know? Sure, I have SU, but big deal. :p
 
iowabowtech said:
There's just one crazy idea you might try, it's the only thing I can think of. Try a different SD card in the phone. It's the only thing that makes even the slightest sliver of sense to change outside of a new phone or getting incredibly lucky and finding a particular kernel that works and if you do find one, I'd call it a shear accident because to my knowledge, nobody is deving for this issue b/c nobody else has it.
Click to expand...


I was planning on getting a larger card anyway because I have tons of music on my card.

I am pretty sure you replied to me the other day about my Inc reading my "partitioned" card (which is isn't, my lappy was reading internal and external storage)..... This makes me wonder if my phone is somehow mixing up information that was left on the card from my rooted Eris.
 
ErisEscalavee said:
I was planning on getting a larger card anyway because I have tons of music on my card.

I am pretty sure you replied to me the other day about my Inc reading my "partitioned" card (which is isn't, my lappy was reading internal and external storage)..... This makes me wonder if my phone is somehow mixing up information that was left on the card from my rooted Eris.
Click to expand...

Yeah it was me although I didn't remember that until now and it makes me even more optimistic about trying a card change. Frankly I still think it's a longshot but you never know. I've seen smartphones of various models fail in one way or another due to a bad file on the SD. Blackberries are notorious for that. Idk, it's something quick and easy to try. No other major changes make sense to me. I mean you do have radio upgrade potential but a lot of people are on the 7.28 radio and doing fine. I can't imagine what on earth the radio would do to fix a screen problem. Makes zero common sense.
 
SUCCESS!!!!! CM 6.1 stable actually works!

I would really like to know why the hell the other ROMs wouldn't activate the touch screen now...
 
I have no idea but congrats on finally getting one working. Maybe it's just a Sense problem for you and AOSP Roms will all work? Whatever the case, you're back in the game. :)
 
You must log in or register to reply here.
Back
Top Bottom