Hi everyone,
I recently have a problem on my (old) TF201. The touch screen works fine, except the right and left edge. When I turn on Developer options and enable 'Show touches' i clearly see that when I move my finger to the right or left it sort of 'snaps' to the edge. So there a small stroke (left and right) that doesn't respond to input. Very frustrating when trying to point out something on the very right or left of the screen
I've opened my TF201 to see it wasn't a loose cable; but everything is in place. No difference.
Anyone an idea?
I did replace the factory ROM with a custom recovery (TWRP) and used
http://forum.xda-developers.com/devdb/project/dl/?id=6853 to install once a CROMBi-kk ROM for TF300t. Maybe this generates this screen edge fault? If so; how do I revert back to TF201? My TF201 thinks it's a TF300 now.
Thanks for reading this problem.
Hi,
Same problem here. It looks like it started after installing KatKiss. I was previously using Cyanogenmod without any problem. I thought that this could be caused by the new bootloader, but the problem persisted even after reverting back to the stock BL and ROM.
I even tried to replace the touch screen, no luck.
Have you been able to fix the issue?
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
[email protected] said:
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
Click to expand...
Click to collapse
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
altya said:
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
Click to expand...
Click to collapse
I am not sure exactly which kernel it was. But as I explained, I first installed Androwook AiryBean 2.31.
Then I used the "Androwook airyBean 2.31 Kernel Installer" to reinstall the default Androwook kernel, meaning the default kernel shipped with the kernel installer. That probably not Grimlock lite 5.1... See this page to download the kernel installer (and the Androwook ROM): http://forum.xda-developers.com/showthread.php?t=2407248
Maybe I should clarify a bit:
1. I completely wiped the tablet and did a clean installation of Androwook, following the instructions to the letter, including the 30 to 60 minutes wait "for the system to cache itself", followed by a restart. At that point, I still had the issue with the screen edges.
2. I then re-installed the kernel, again following the instructions to the letter. After the final reboot, the problem was gone.
3. And I finally re-installed KatKiss (v26). Since then I enjoyed my TF201 without any issues.
The reason why I tried to re-install the default kernel is because of the following quote:
HairyBean 2.31 Kernel Installer will allow you to try different kernel options without re-flashing the rom. It will also clean up bits left behind by the previous kernel before installing a new one
Click to expand...
Click to collapse
I am not sure that this is what solved the problem, but this is definitely a software issue. And since wiping the tablet multiple time, downgrading to stock and trying various ROMs didn't do anything, this was my last hope. It worked for me, and I hope that it will work for you too...
I can confirm that this is a software issue. After installing the reverse axis kernel of Hairy bean, the unresponsive areas in the touch screen was also reversed! I tried the solution provided above, unfortunately without success. Is it right to assume that everyone got this issue after installing Katkiss version after V26?
jan3586 said:
Is it right to assume that everyone got this issue after installing Katkiss version after V26?
Click to expand...
Click to collapse
I don't think so. I got the problem with an earlier version of KatKiss, and I believe (but may be mistaken) from the research I did in the past that a few people ran into this problem with other custom ROMs.
Thanks, are you using ver 2 of the kernel installer?
Sent from my Nexus 4 using XDA Free mobile app
jan3586 said:
Thanks, are you using ver 2 of the kernel installer?
Click to expand...
Click to collapse
Yes, it was version 2 that I used.
Related
Hey Guys.
So I have a Tab 10.1, bought by me in the UK, tho I believe the model I have is a French one (bought it from Expansys) as that's the language it started up in.
I have tried to root my tab, using this method http://forum.xda-developers.com/showthread.php?t=1239185/
However, no matter what rom I try to install, my screen ends up flickering with lots of lines across it, after about 5 mintues, rendering it useless. I have tried to install a stock rom, and unroot using Odin. I downloaded Root Checker from the market and it says I am now not rooted. I am currently running a stock 3.1 Rom.
But I don't know what to do now. Whatever rom I seem to choose to flash I still get the flickering issue.
I also got the flickering in CWM, but got it working using this guide http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
but it didn't stop the flickering when I installed a new rom.
Can someone help, pleaseeeeeeee? :fingers-crossed:
Ok, I seem to have fixed the screen flickering.
I did this by flashing the file P7510XABKMN_P7510UEKMM_HOME.tar.md5 (which was in a file I found called sgt10.1_root_unroot) through Odin.
I'm not sure how to root and/or flash now as I don't want the same problems again.
I have no CWM because when I boot into recovery I have no option to install zip from SD card.
My About Section tells me:
Model Number GT-P7510
Android 3.2
Build No. HTJ85B.UEKMM P7510UEKMM
So I am guessing I have managed to get a stock rom back on the device, which has solved the flickering isses.
I have no Superuser and so am not rooted.
My aim is to install Tasker 14.
Does anyone know the reason why I got the flickering from Clockwork, and how I can flash without getting it?
Going to go to bed now since I've rescued its functionality! I'll get back on trying to flash it tomorrow.
Thanks
So I managed to root and install CWM again, flickering seemed to not exist.
I then tried to flash Task 14 and have the screen flickering again.
I flashed the bootloader file before I did any of this, as of these instructions: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
Hope u have got the solution now
Sent from my GT-P7500 using xda premium
Had same problem Look at this thread
http://forum.xda-developers.com/showthread.php?t=1691875
Thanks for your reply.
Weirdly, the AOKP, CM9, and my current rom Overcome all work on my tablet, without the screen issues. The only time I get the screen scrambling is when install Task 14 (tried both fat and slim versions). This is on a clean install.
No idea why this is. But I'm happy the screen issues are sorted and I'm now running the modified honeycomb rom that is Overcome. Just got to wait for the Camera drivers for ICS
Cheers
Sent from my GT-P7510 using xda app-developers app
I just flash hairybean 2.31 to my prime and found that touch screen is not responsive 2 columns at 2 sides when place horizontally.
Flash back to 4.1 still cannot fix.
If anyone experienced the same issue, please share as I have no idea if this is hardware error or because of screen driver.
brightsea2001 said:
I just flash hairybean 2.31 to my prime and found that touch screen is not responsive 2 columns at 2 sides when place horizontally.
Flash back to 4.1 still cannot fix.
If anyone experienced the same issue, please share as I have no idea if this is hardware error or because of screen driver.
Click to expand...
Click to collapse
I've never seen anyone with this problem before.
Did you have any Updates come in after you installed the rom ?
Screen calibration after flashing hairybean 2.31 update
flumpster said:
I've never seen anyone with this problem before.
Did you have any Updates come in after you installed the rom ?
Click to expand...
Click to collapse
I had the same problem. I reflashed the ROM and this time I did not check the box for reverse axis program. I also let the rom stabilize for about 30 minutes before doing anything with it including initial settings like Language. It works great now and no more calibration problems. Try reflashing it. I think the ROM works great after reflashing it.
heccal2276 said:
I had the same problem. I reflashed the ROM and this time I did not check the box for reverse axis program. I also let the rom stabilize for about 30 minutes before doing anything with it including initial settings like Language. It works great now and no more calibration problems. Try reflashing it. I think the ROM works great after reflashing it.
Click to expand...
Click to collapse
I am having similar issues, just reflashed katkiss v30 from stock rom and now left side there is around 2cm of unresponsive column and right side is 1cm...
Tried reflashing the rom but still the same issue......
I flashed Iced Bean 4.0 on my xperia sk17i and i think my touch screen died because of it, That rom has aroma installer and there was no my device on that list so i chose xperia pro. Installation was successful but touch screen didnt work. I reverted to stock using flashtools and it still doesnt work. Is there any way to fix this problem? i really need to try something so pleas suggest.
Just to be clear i'm not blaming on anybody, it is total my fault. I'm fully aware of risk installing custom roms so pleas help in any way you can
Thanks in advance
Have you tried to flashing a new kernel which was made for the phone? As far as I know drivers areusually stored within it in Linux / Unix systems so it might apply here for the touch screen as well.
i tried using command fastboot flash boot boot.img and generally did not work. I have unlocked bootloader. I had hard time finding guide to do that for my phone. I did revert to stock using flashtools and ftf file.
When you say fastboot didn't work, do you mean it could not connect to the phone? Where you in fastboot mode when you tried it?
I recently put the 4.4.4 AOPK rom (Link) on my phone and had trouble getting into fastboot to flash the required kernel, I think I solved that by using the flashtool.
If flashing the stock kernel doesn't fix the issue, perhaps using a custom one, which works with ICS, will help?
You can find some here: http://forum.xda-developers.com/showpost.php?p=47407355&postcount=3
-edit-
does this thread help you? [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)
Fastboot worked fine, but any custom kernel after successful flashing didn’t work. I have installed managed to install xperialegacy cm11 it has custom kernel and it didnt fix touch screen. I will try the link you posted. On the side note i bought another sk17 today, yes i love this phone LOL xD
Yess, million times thank you . I made it using this tutorial
here is what you have to do for fix your Bricked touchscreen.
What you need for that is any custom rom with an aroma installer.
1. Flash suitable firmware with Flashtool ( i flashed .587 Because i used Zellycream rom V4 )
2. Then Install any ics Kernel that you like (I installed messa hybrid kernel v4.3 )
3: Then install Any rom that has Aroma installer in it and does support your device, via Cwm recovery (I installed Zellycream V4)
3. While installing the rom choose ST17i in Aroma instead of SK17i
4. Reboot after installation is completed.
5. Wait until phone is On homescree.Nopw touchscreen should work but h/w keyboard not
5. Reboot again into CWM install "keymap_for_pro_XXXX.zip
Link here For Keymap Mini pro
6. Reboot phone again.. Now keyboard and touchscreen should be working. Also options for h/w keyboard should appear now.
Good luck,
It did worked for me hopefully its also going to work for you.
Notice : At first your Touch might not responce how it was before, but give it a time it will work fine after some hours or day or it might never work like before.Mine touch screen worked normally after 8 hours of installing the rom with this method.
Click to expand...
Click to collapse
Now i have questions. Can for some reason touchscreen die again? and also which rom do you recommend for good battery and camera? i like stock but i find it tedious to root and remove all the unwanted apps only to free up a couple of MB and potential screw something
Update: I see that i need to flash a zip which fixes tochscreen. when installing new rom. Is this hardware or software problem?
It would surprise me if the screen died again from the same issue, as the harmful code should have been overwritten by the fix.
I am not a developer though, just a normal user with some basic linux knowledge.
I'd suggest trying out Real ICS. I think I ran it before I got my new phone (I just recently started using the Mini Pro again) and can't remember having any complaints back then.
Other than that you could just go through the rom list. There are some which claim to be focusing on performance, I haven't tried them myself though.
I currently use AOKP kitkat (with some modifications, see this post) but I cannot yet if I'll stick with it. Maybe gonna try out this one http://forum.xda-developers.com/showthread.php?t=2277199 next.
I think im going to stick to the stock for the now. Camera is the best there
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Bucov said:
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Click to expand...
Click to collapse
I'm confused. Didn't you solve the issue already?
If the damage is permanent, then maybe the touchscreen got damaged by using the wrong rom?
If you really want to have two working phones, you could get a replacent display from ebay. They start at around 30€ these days.
Hi.
I have a Nook Tablet (16gb version) with which I have a problem.
Once upon a time (couple summers ago), I decided to flash another touchscreen firmware through the Touchscreen Firmware Flasher app included in the KK version of LiquidSmooth, unofficial build for NT. I had just changed the glass part of the screen, so I was looking forward to using my tablet for months to come.
The problem is that the flasher app crapped out on me and force closed in the middle of the installation, leaving me without a usable touch driver. I have tried using SD-boot ROMs and I believe they have done nothing for me. I flashed many ROMs, including MIUI, stock and CM 10.1.3, with no result other than a successful boot. But still no touch input.
I talked to demetris about this (seemed like a good idea) and he gave me many tips. Essentially, all I have to do is run a script after placing a file in /system/etc/firmware and it should be fixed. Alas, this has not worked. I shall include a screenshot of the error.
I am now in possession of a Nook Tablet with a screen that will not respond to touch at all, but can boot standard CM 10.1.3, TWRP and CWM. I used the ADB included in TWRP for the procedure, and nothing. This is probably something that has to be done from within the system, so...
Is it possible to add a line in build.prop saying "ro.secure=0"? I read online that this will disable secure ADB (remove the need for RSA key approval) so that I may run the script?
UPDATE: I made a breakthrough. I am currently trying to put this script into a flashable zip. The part I still can't do by myself is the updater-script. It's mostly working but the recovery says the zip is bad. The exact thing is in the thumbnails below.
If anyone can use Edify (Recovery Script Language) and at least give me some tips, I'd be grateful. Thanks for checking!
TheAnonymusModUser said:
Hi.
I have a Nook Tablet (16gb version) with which I have a problem.
Once upon a time (couple summers ago), I decided to flash another touchscreen firmware through the Touchscreen Firmware Flasher app included in the KK version of LiquidSmooth, unofficial build for NT. I had just changed the glass part of the screen, so I was looking forward to using my tablet for months to come.
The problem is that the flasher app crapped out on me and force closed in the middle of the installation, leaving me without a usable touch driver. I have tried using SD-boot ROMs and I believe they have done nothing for me. I flashed many ROMs, including MIUI, stock and CM 10.1.3, with no result other than a successful boot. But still no touch input.
I talked to demetris about this (seemed like a good idea) and he gave me many tips. Essentially, all I have to do is run a script after placing a file in /system/etc/firmware and it should be fixed. Alas, this has not worked. I shall include a screenshot of the error.
I am now in possession of a Nook Tablet with a screen that will not respond to touch at all, but can boot standard CM 10.1.3, TWRP and CWM. I used the ADB included in TWRP for the procedure, and nothing. This is probably something that has to be done from within the system, so...
Is it possible to add a line in build.prop saying "ro.secure=0"? I read online that this will disable secure ADB (remove the need for RSA key approval) so that I may run the script?
Click to expand...
Click to collapse
Did you see this thread?
nmyshkin said:
Did you see this thread?
Click to expand...
Click to collapse
Yes, I did. I tried booting off an SD card and the screen still would not respond at all.
My Kindle Fire HDX 7'' got hammered (literally). I fixed the dents, un-bent the chassis, replaced the lcd+digitizer and it's working again, but the accelerometer seems to be dead so I can't rotate the display. I tried with several "sensors test" apps, and they don't detect the chip (InvenSense ). I think maybe some contact broke because of the mainboard getting bended and it need to be resoldered, but I'm unable to locate the chip on the board.
Do you know where the chip is?
ttortuga123 said:
My Kindle Fire HDX 7'' got hammered (literally). I fixed the dents, un-bent the chassis, replaced the lcd+digitizer and it's working again, but the accelerometer seems to be dead so I can't rotate the display. I tried with several "sensors test" apps, and they don't detect the chip (InvenSense ). I think maybe some contact broke because of the mainboard getting bended and it need to be resoldered, but I'm unable to locate the chip on the board.
Do you know where the chip is?
Click to expand...
Click to collapse
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Syuriy said:
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Click to expand...
Click to collapse
I had the same problem but after I reflashed my rom it started working again. Try that if u can, or maybe if on stock downgrade to 3.2.8 then update back that might have the same effect
Syuriy said:
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Click to expand...
Click to collapse
CocoBun said:
I had the same problem but after I reflashed my rom it started working again. Try that if u can, or maybe if on stock downgrade to 3.2.8 then update back that might have the same effect
Click to expand...
Click to collapse
Same. Flashed LinOS 14.1 on known good device and rotation stopped working. Tried common solutions but issue persisted. Wiped and flashed CM 13 (rotation started working again) then LinOS 14.1 with full wipes. No issues with rotation since. No logical explanation but 'ROM hopping' (for lack of better term) has reported worked for others experiencing rotation issues. Sounds nutty.
I tried to install all TWRP flashable firmware Nexus, Stock, CM 11 12 13 14, LOS with wipe and format data. No result!!!
Syuriy said:
I tried to install all TWRP flashable firmware Nexus, Stock, CM 11 12 13 14, LOS with wipe and format data. No result!!!
Click to expand...
Click to collapse
Out of ideas. Indeed may be a hardware problem. Hopefully you can find an app that supports reasonably convenient orientation selection (common UX places controls in a permanent notification).