No touch sensitive - Mate 8 Q&A, Help & Troubleshooting

Hello
As said in the title I have the touch sensitive that no longer respond under certain updates, I am currently in B560 and it is impossible for me to update it under pain of having the touch sensitive non-functional, my TWRP also has the Tactil that no longer respond under a certain update. It's working with TWRP 3.1.0 but not with TWRP 3.1.1 or +
I said that I changed the LCD and that is since I have this problem ...
Thanks for your help in advance

https://forum.xda-developers.com/mate-8/help/tactil-t3662111

Related

A700 Screen Tracking Problem

Hello everyone, I'm new to the forum and have run into a snag. I recently installed the CM10 Nightly build. I had no issues with the install itself. However, now one of the axis' is not tracking properly on the touch screen. In portrait mode, the vertical axis is off, and in landscape the horizontal axis is the problem. Also, the corners seem to be fine, but if there is a button in the middle of the screen, I have great difficulty finding where on the screen to tap in order to activate it. Anyone else have this issue or have ideas on how to solve it? Some quick google searches didn't produce much for me (maybe I don't know how to search for this problem).
History:
I rooted my tablet back when that was first figured out and haven't really done much since. I installed CWM 6015 before I wiped data/dalvik cache and installed CM10 straight from the original ICS install.
Any help would be greatly appreciated...
Nobody has seen this before? Or have I explained it poorly?
Problem: Screen touches are bugged..
Hi,
I am also facing the same problem and need some urgent help..:angel:
I upgraded my A700 (was shipped with 4.0.4) to JB but the screen touches are completely off track. I did the following:
1) unlocked the bootloader
2) flashed CWM Rom 6.0.1.5
3) installed cm-10
Don't know what to do next..
Did you get it fixed?
You should take the JB OTA before installing CM 10, or search around for the updated bootloader/touch screen firmware and install that.

[q] middle part touchscreen doesnt work after update

MIDDLE part of one plus has become unresponsive after update lollipop ROM . tried many different solutions . none of them worked . please help how to get the touchscreen back again
The lower part of my screen (last inch or so) is often unresponsive so if I type, I'll miss a bunch of spaces.....
theMoiz94 said:
MIDDLE part of one plus has become unresponsive after update lollipop ROM . tried many different solutions . none of them worked . please help how to get the touchscreen back again
Click to expand...
Click to collapse
Test your touchscreen using this app https://play.google.com/store/apps/details?id=com.rn.yamtt
If there are issues with multi touch, only thing I can suggest is to switch to other ROM if you are rooted and bootloader unlocked
I had read that CM has fixed touchscreen issue in their latest CM12.1 nightlies
If you are not rooted, a factory reset may work (hopefully) else call the customer service for RMA if they do it for you so easily
I was facing such issue on CMOS12 and also on all lollipop ROMs so I downgraded to XNPH05Q

Interesting issue. Replaced my LCD and was stuck in bootloop but...

Hi everyone.
I recently replaced my shatter LCD and was subsequently trapped in a bootloop. I began to wonder if the LCD I ordered was defective, so I removed the new screen and attached the old one. The device booted up fine (as fine as a devastated LCD screen would permit anyway). I detached the broken screen and reattached the new one and the device seems to be working fine.
I am now worried that shutting down the device will cause it to enter a boot loop again. Would reflashing the stock rom solve this issue? Has Motorola installed a failsafe that would prevent devices from booting up if there is a replacement screen attached to the logic board??
I am having the same issue, did you find a solution?
mike29892 said:
I am having the same issue, did you find a solution?
Click to expand...
Click to collapse
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
ElonNoir said:
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
Click to expand...
Click to collapse
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
mike29892 said:
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
Click to expand...
Click to collapse
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
ElonNoir said:
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
Click to expand...
Click to collapse
I couldn't even get the device to boot before restoring to 5.1. I was on 6.0 broke my screen and then replaced the screen. After turning the phone back on it entered a boot loop. I restored to 5.1 and it was able to boot, but the touch screen was all wonky, and getting phantom touches. I tried to flash 6.0 again and it just put me in the boot loop again.
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
fresh cut vegetables said:
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
Click to expand...
Click to collapse
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
ElonNoir said:
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
Click to expand...
Click to collapse
It won't reboot until the OS starts loading, as long as you can access TWRP you should be safe to flash a custom ROM... it seems to be a known issue that a non-Moto replacement screen will bootloop the OS with Marshmallow but not Lollipop, unknown if CM13 and ROMs based it (which is all custom MM ROMs) will bootloop or not.
Best solution is replace it with an OEM Moto screen, it won't bootloop, only 3rd party ones do.

No tactil

Hello
As said in the title I have the tactile that no longer respond under certain updates, I am currently in B560 and it is impossible for me to update it under pain of having the tactile non-functional, my TWRP also has the Tactil that no longer respond under a certain update. It's working with TWRP 3.1.0 but not with TWRP 3.1.1 or +
I said that I changed the LCD and that is since I have this problem ...
Thanks for your help in advance
No One ?
What is "tactile"?
Boosik said:
What is "tactile"?
Click to expand...
Click to collapse
Hello
As said in the title I have the touch sensitive that no longer respond under certain updates, I am currently in B560 and it is impossible for me to update it under pain of having the touch sensitive non-functional, my TWRP also has the Tactil that no longer respond under a certain update. It's working with TWRP 3.1.0 but not with TWRP 3.1.1 or +
I said that I changed the LCD and that is since I have this problem ...
Thanks for your help in advance

After the last update, the touch screen no longer works inside the twrp recovery.

After the last update, the touch screen no longer works inside the twrp recovery, someone already had this problem and resolved? I can not use the twrp porq n anymore how to mark anything, not even to slide on the screen
Try otg+mouse and flash new twrp
I'm going through the same problem, I can not use anything. MIUI10 Global 9.3.21 9.0. I am using Twrp 3.2.3.1.
deniloo said:
After the last update, the touch screen no longer works inside the twrp recovery, someone already had this problem and resolved? I can not use the twrp porq n anymore how to mark anything, not even to slide on the screen
Click to expand...
Click to collapse
I can CONFIRM that after upgraded to MIUI10 with Android Pie ALL TWRP versions (Official and non-Officials) seems to stopped working.
Already reported on XDA-Developers, Mi Global Forum and GitHub.
None fix yet,

Categories

Resources