My elderly neighbor held onto her Motorola Moto E (2nd Gen) for years till it recently stopped responding all of a sudden to her touches. It still charges fine and the display exhibits no issues, but the touchscreen is totally unresponsive despite repeated reboots. I'm guessing the touch digitizer is dead? Anyway, I've convinced her it's pointless to waste money repairing it and to simply get a new device. Since there weren't too many apps in use (most apparently stopped working over time on what must've been either Lollipop or Marshmallow), those aren't the issue here. What is required is to extract the bare minimum but very important data from the phone like **pictures, videos, contacts and messages (SMSes)**, and finally import everything into a new Android phone. So my question is, is any of this even possible with a completely unresponsive touchscreen? And if so, how?

I have an LG G2. The bottom 50% of the screen doesn't respond to touch. Right now, I am running BlissPop ROM, which allows 180-degree screen rotation, and that is currently my workaround. But I'd like to use the top half of the display only. What I'd like to do is use the top 50% of the screen, but rotated so that the 1080 pixel-wide side is oriented up/down, and have a shrunken phone in that top 50%. |What is going on right now|What I'd like to do| |-|-| ||| I've tried using adb shell wm overscan 0,0,0,960 but it breaks most apps (probably due to the weird resolution) How to get Android to assume my screen is rotated 90 degrees and only spans the top half? I'd prefer if the resolution was 4:3 so I could use more of my screen, but if 16:9 keeps better compatibility with apps, I will do that.

This is a little different to other posts. I have a **Samsung Note 20 Ultra** - There is no damage to the phone or screen - I have not dropped it - Suddenly in the middle of browsing the touchscreen stopped responding - Since I have fingerprint access, its hard to do anything - I used the stylus to boot into safe mode - The issue is still there - I have checked all touch screen settings - Accidental Touch Protection is off - Touch Sensitivity - tried on and off - Touch and Hold delay is 0.5 sec - Tap duration is off - Ignore repeated touches is off - I tried *#2663# to recalibrate touchscreen, the firmware update fails. Is this an Android issue or is it hardware ?

My Google Pixel 7 got dropped in water, and now it's getting phantom touches in a horizontal straight line about a quarter of the way down from the top. I know this has been asked a lot before, but stuff like adb shell wm size wouldn't work. Is it possible to stop touches from this area alone without reducing the entire screen size? I'm willing to root it if that would help.

I have a broken-screen, non-rooted Xiaomi Redmi Note 6 Pro that looks like this and I'm experiencing a LOT of ghost touches (and the digitizer's gone). I am using scrcpy to control it from my PC, so I want to disable the touchscreen because otherwise it interferes with my commands and does what it wants. I don't want to detach the digitizer physically since I have no tools for opening my mobile and this one has to be opened from the screen, so I could damage it more. How can I do it (possibly with ADB)?

My Samsung Galaxy J6 (J600G/DS) touchscreen isn't responding this morning. I opened just one app and wanted to slide it off and then it just stopped moving for some reason. So, I just turned it off and now it still hasn't responded. I've charged it also and it remaining full 100%. I can't open or do anything really because I can't slide it open. I can't put it on power off because the touchscreen isn't responding. I've tried pressing the power button with the volume button but it didn't work. Please help.

I have a SenlinTech Android Tablet (pad6_ee). I factory reset the thing and now my touchscreen is not responding at all, and I can't get past this screen to even attempt a fix. I have searched high and low trying to figure out how to fix it. I have a phone and laptop as well. I've also been trying to 'update from adb' but I can't seem to work that out either. The Senlin site is useless and this tab just doesn't seem to exist. It's windiws 14. I thought of resetting again and I got this error. Is there a fix I can do using a phone/laptop?

I have an IKALL K260 Android 6 phone with a faulty touch digitizer, a broken connector strap, and is irreparable, having IC SILEAD GSL1691. I want to replace that digitizer with Gionee F205's touch digitizer having IC Goodix 917D. I have connected the pins in the same order, but it's not working. It (IC Goodix 617D) heats up and does not let the display glow. It seems like there is some driver-related issue, the phone may not have drivers for the new touch digitizer. So, can anyone tell me, is it possible to add drivers through USB with a computer?

I have an aging parent who I want to acquaint with using an Android smartphone. Gestures are a bit of a problem for him, and I want to acquaint him with swipe-down, swipe right, long-press, single tap, double tap, pinch zoom. Preferably but not necessarily in the context of actual Android phone use - bringing down settings, moving a shortcut around on the desktop, moving a shortcut to another page on the desktop, etc. Is there a way to achieve this? In the context of actual use (i.e. practice on a 'practice desktop' where nothing he does is permanent. Or something simpler just for practice would do. I'd just give him a smartphone to practice on, but he lives a long distance away and it's difficult to tell if and when he screws a gesture up and does something inadvertently or changes some setting that leads to headaches.

I'm running a triple-boot between Android, Ubuntu, and Windows. My computer has a bad touchscreen that is randomly clicking certain areas of the screen, and I want to know if it's possible to disable the touchscreen driver. I have Android set up to boot via grub2. (Note that I never attempted to install Android on the machine itself, I installed it to a USB drive on virtualbox then copied the android system folder to Ubuntu's partition, then modified my 40_custom file so I can boot Android.) The Android version I'm running is 5.1. I installed this because Android 6 didn't seem to boot in Virtualbox so I thought it probably wouldn't boot on my PC. (Apparently it seemed to softlock on boot inside Virtualbox.)

I have a strange problem with my Samsung Galaxy A14 phone, as soon as I install a screen protector for the device, a problem occurs in the touch function, which is: when touching a point on the upper half of the screen and waiting six seconds or more, the entire upper section becomes unresponsive to touch until a point on the lower half of the screen is touched! - I have changed the screen protector three times to no avail. - No problem occurs if the screen protector is removed. - This problem does not occur when the charger is connected to the device even with the screen protector installed . - What is the explanation for this and what is the solution?

So I ordered a cheap Chinese phone (umidigi) as a secondary device and the unit I got, out of the box, was afflicted with a faulty display. Troubleshooting it I have diagnosed the problem precisely: * There is an intermittent false touch input occurring in the bottom right, very far bottom right part only of the screen * Lowering the brightness appears to minimize the presence of the false input * Is likely to require disassembly of the device to remedy the issue I alerted the seller I bought the phone from, and they're sending me a new unit pronto, and told me to just keep this one. Yay. So, Id like to eventually permanently resolve this phones issue and open it up myself, but in the meantime I'd like to get some use out of it. But, with the ghost touch using the phone with anything other than a Bluetooth mouse is maddening. The area effected is at the very, very bottom of the phone and may occupy 15px or so at most. I attempted to use a few apps, one called 'Partial Screen' and some others like Screen Shift. However, the adjustments to the display only result in cosmetic changes and do not desensitize the adjusted portion of the screen to touch input and thus the false input creating problems. Can anyone point me to a procedure, adb input or otherwise, that could ensure that some specified portion of the touch screen will not respect any touch input? Thanks.

I have an Android 5-based smartphone that I like a lot but it's an old phone and the touchscreen is damaged. The screen works perfectly but there's no user input available. The battery was changed recently and I suppose the technician did a good job fixing the backing side but broke the front part containing the touchscreen. **Is there an option to access it somehow and make it controllable remotely?** If I use a USB cable, is possible to install TeamViewer or some other remote control software to still use it? The phone has no other remote control software preinstalled. Its touchscreen broke before I was able to install anything for remote control. The point is to use its camera and mic functionality, and still use its sensors to do something useful like a remote camera or something similar.

I'm observing a strange behaviour on my phone out of the blue. Yesterday, the left side of my screen stopped working properly. I started having a hard time clicking anything next to the left edge, typing the keyboard or pressing buttons on the left. I enabled *Developer Options > Input > Show touches*, and I was able to observe that when I try to tap the left side of the screen, the screen appears to detect two taps on opposing sides of a column, as if the whole column of pixels were damaged. The phone hasn't suffered any hits or gotten wet. This is just out of nowhere. " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> I've uploaded a video of this to make it clearer here . This is an Xperia Z3, D6603, running Android 5.1.1. Has anyone encountered something like this? I've tried restarting the phone to no avail.

Consider the following system: - Stock Android 9, unrooted - USB and wireless debugging unavailable - screen permanently turned off So basically a headless Android device. **Question:** Is it possible to programmatically execute touchscreen inputs without any user interaction, e.g. in order to automatically force-stop selected apps? **Example:** The default method to do this manually is from the app info menu, i.e. Similarly, inactive/background apps can be closed from the developer settings: **Note:** A purely programmatic solution is required. Connection to a debugging device is allowed only once for initial setup, otherwise: No external devices.

How do I deal with a frozen or unresponsive screen on my Android phone? I have tried restarting the phone multiple times, but the issue persists.

I have an LG G8X I'm trying to get working with an external USB IR touch frame and it's been driving me bonkers for weeks... I feel like I'm so close to figuring it out, yet so far at the same time. If I turn on "Show touches" and "Show touch data" in developer options and proceed to use the IR touch frame, it shows all touch events as expected and multitouch works fine. The problem is that my taps and swipes don't actually do anything -- I can't click, I can't scroll, nothing works EXCEPT if a do a swipe gesture from the edge of the IR frame. This means that I can perform a "back" or "home/recent apps" gesture just fine... I've tested the IR touch frame with my S23 Ultra and it works perfectly fine. I've tested a different external touchscreen monitor on the G8X which also worked as expected. I've run "adb shell getevent -l" and the events seem to be registering fine: add device 8: /dev/input/event7 name: "Touch p303 Keyboard" could not get driver version for /dev/input/mouse0, Not a typewriter add device 9: /dev/input/event8 name: "Touch p303" /dev/input/event8: EV_ABS ABS_MT_TRACKING_ID 00000000 /dev/input/event8: EV_ABS ABS_MT_POSITION_X 00004690 /dev/input/event8: EV_ABS ABS_MT_POSITION_Y 00005cc8 /dev/input/event8: EV_ABS ABS_MT_TOUCH_MAJOR 00000090 /dev/input/event8: EV_ABS ABS_MT_TOUCH_MINOR 00000090 /dev/input/event8: EV_KEY BTN_TOUCH DOWN /dev/input/event8: EV_ABS ABS_X 00004690 /dev/input/event8: EV_ABS ABS_Y 00005cc8 /dev/input/event8: EV_SYN SYN_REPORT 00000000 /dev/input/event8: EV_ABS ABS_MT_POSITION_X 00004748 /dev/input/event8: EV_ABS ABS_MT_POSITION_Y 00005ba8 /dev/input/event8: EV_ABS ABS_X 00004748 /dev/input/event8: EV_ABS ABS_Y 00005ba8 I've created an *.idc file per this documentation , but have had difficulty finding what properties I can even change. My config is as follows: touch.deviceType = touchScreen touch.orientationAware = 1 touch.gestureMode = spots I've confirmed the .idc file is being used, but as expected, this didn't change the behaviour. The strange thing is if I change the touch.deviceType to 'pointer' it works exactly as I would expect -- it turns into a large trackpad with a mouse cursor displayed on screen and I can actually 'click' on items... I've also checked out dmesg and adb shell dumpsys input, comparing the different touch screens and different phones, but nothing seemed out of the ordinary (with my limited knowledge anyway...). Any hints on what might be the issue or further steps I can take to troubleshoot would be much appreciated!

I'm looking for a way to disable and enable the phone's touchscreen via console, and possibly the physical buttons, so to prevent finger touches from being processed. The phone is a Samsung Galaxy Fame, Android 4.1.x. **Background:** I'm configuring an old Galaxy Fame to serve as a sat navigator fixed on my car dashboard, aiming at using the up-to-date and free OpenStreetMap. When I turn the key, the phone's USB is powered at 5V, when I turn off the car, the USB has no power. The phone is able to detect these events and I scripted some actions upon them, aiming at providing an instant-on and instant-off navigator service. The phone remains always on and just switches to a power-save status when the car is off. The navigator app – OsmAnd – starts automatically at boot, but the boot does not occur between a car-on / car-off cycle, because the phone remains on to detect the mentioned USB changes. Currently, what happens when I start the car and the USB gets powered: - Display is lit (echo 200 >/sys/class/backlight/panel/brightness) - Sat receiver is activated - CPU frequency set to max What happens when I turn off the car and USB loses power: - Display's backlight off - The sat receiver goes off, along with WiFi and Bluetooth, in case they might have been active - CPU frequency set to minimum Up to this point, everything is working. My problem now is that, when the car goes off and the phone enters this quasi-standby mode, the touchscreen still accepts input and, if the phone is handled or touched for whatever reason, it will stealthily react to those touches while the screen is unlit.

I have a damaged screen and touch digitizer on an automotive head unit. I am trying to access the diagnostics menu for the unit (Honda Clarity 2018 PHEV non-touring), but the touch input keys are not (to my knowledge) among the standard Android keyevent codes. Is there some way to pull these directly from the head unit itself? I have root on the unit, and I did find some keyboard data files but the enclosed keyevent codes don't appear to all be functional, and it isn't clear from the descriptors which keys would match with the necessary inputs (Power, Menu, and Screen Brightness, the first two of which are not the standard Android ones). EDIT: here's a picture of the keys in question. Note that these do **not** correspond to the Android generic equivalents, e.g., keyevent 24 & 25 will invoke the Android native UI's volume control, but not the same as these keys; same for the rest of the keys.

I recently purchased a 55" Infrared touch frame for my Android TV 55", this IR frame works perfectly when I connect it to a PC with Windows 10 via USB no drivers are needed. However, when I connect the same frame to my TV OS:Android TV 11, there's no response to touch input. After some research, I came across the concept of "android.hardware.touchscreen" in Android and started wondering if this feature might be disabled on Android TV OS, preventing the IR frame from functioning. My questions are: * **Is it possible that a disabled "hardware.touchscreen" feature is causing my issue?** I haven't found any definitive information about whether Android TVs generally have this feature enabled or disabled by default. * If so, **is there a way to enable "hardware.touchscreen" on my Android TV?** I'm hesitant to tinker with settings even if it could potentially harm my TV. * **Are there any other potential causes for the IR frame not working on my Android TV?** It would be helpful to understand other areas I could investigate.