I am having issues with my Verizon Galaxy S3 SCH-I353. Over the past few months this problem has been increasing in severity. My screen is detecting "phantom inputs". These inputs are rapid, horizontal movements in the top 1/3 of the screen. These movements render the screen unresponsive, and will register as touches to any screen item in that zone. Turning the screen on and then off stops the movements but only very temporarily. Some days this problem is minimal, while others my phone is nearly impossible to use due to the frequency of these inputs. These inputs occur in the same exact spot every time, and at the same spot that other people have reported, so I can rule out screen scratches or smudges. I created a .gif of the inputs after I turned on "show touch inputs" in the developer options.
I've seen others with this problem online, but no one has narrowed down if this is a software or hardware malfunction. Here are some of my possible problems:
1. Hardware: Possibly a loose cable? Malfunctioning Screen? Possible fix - taking it apart and putting it back together.
2. Software: Screen needs re-calibration of some kind (too sensetive?), would this be possible?
3. App running in the background that overrides touch inputs and is somehow creating this?
Any help would be greatly appreciated.
Other info: Problem started on stock 4.1.2, Verizon SCH-1535
Now on stock 4.3, rooted with xposed modules.
Phone was purchased new in Fall 2012.
No water damage.
Related
I got nexus s (i9020T) recently and found the touch screen unresponsive sometimes. I've already tried several launchers(adw, lancherpro, go launcher ex), and it seems not launcher's problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
Later I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally.
I'm confused by the strange behavior, anyone experienced similar issue?
more info from test,
I connect my phone with adb, and tried to "cat /dev/input/event0"
The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I don't know kernel very well, so I cannot find the source code Any help please?
FYI. we are not alone.
http://code.google.com/p/android/issues/detail?id=13853
I got this problem too whenever my phone is in my pocket facing inward.
I have tried to open the calculator to see which part of the screen having problem. Mine is usually the "8" and "5" location unresponsive if my phone stayed in my pocket facing inwards for a certain period of time.
The problem will goes off after couple of mins when i can feel that the phone is cooler than my body temp.
I knew this happens to the Dell Streak as well.
I've come across an issue with the touchscreen. In apps where you draw a line across the screen by dragging your finger - e.g., Air Control HD & Sketchbook Mobile - I'm finding that I can only draw short lines. After dragging my finger a bit (it varies from a few inches to something very short), the screen no longer registers the touch. It doesn't seem to be dependent upon any particular part of the screen. This is on stock US JB. Any thoughts?
Have you tried a cold boot?
Assuming software can't fix it take it back as it has a defective touch screen. Mine doesn't behave like that in air control hd.
sbdags said:
Have you tried a cold boot?
Assuming software can't fix it take it back as it has a defective touch screen. Mine doesn't behave like that in air control hd.
Click to expand...
Click to collapse
I can readily draw lines in the Notemaster app so it would seem that this is not a h/w problem. I have cold booted several times, too.
OK, this is a h/w problem and I have to RMA this baby.
I can go into Developer Options and enable Debugging Mode. If I enable Pointer Location and then draw my finger back and forth across the screen in landscape mode I can see an area about half an inch wide in the middle of the screen where the drawn line is broken. This dead area extends from the top of the screen to the bottom. If I enable Show Touches, I can see the visual feedback jump over this dead area, not glide through it. I have done a factory reset but no change occurred.
I have replaced a crashed LCD/glass assembly on my unrooted Z90-7. I chose an assemby with frame included, trying to save time and trouble. This would have been a good move, had I known that the new frame lacked the two tiny flex cables holding microswitches for the volume, power and camera buttons. Once I realized that, I had to remove these cables fixed by adhesives from the edge of the original frame and put them in place on the new frame, all without breaking anything. Unfortunately, in the process, an "invisibly" small amount of too much adhesive tape came under one of the microswitches, making it sit less than a tenth of a mm too high on the frame edge. As a result, when all screws were back and tightened, the volume button was in permanent down position. So, when I powered up, all I saw was a self test menu. It took several cycles of trial and error, before I found out what was happening. I am telling you this, so that you know, that my Z90-7 was started and run in permanent volume-down-position several times. This is as far as I know, the only abnormal operating mode it has been subjected to.
Anyway, when it was all fixed and the Z90-7 could start normally, it turned out that the orientation sensors are way out of calibration and probably also the magnetic ones. The screen rotates to horizontal position when I want it vertical most of the time. I have googled and there are plenty of solutions, like shaking the mobile, turning it over it's three axes for a few times, moving it quickly around in an 8-like path, downloading some sensor testing apps with claimed recalibration capability, etc. All of these solutions have been in response to queries about other brands and models than Lenovo Vibe Shot and none of them have had any effect on my mobile.
So, does anyone have a clue on how to fix this issue on a Vibe Shot? Is it all possible to fix on a mobile that isn´t rooted?
So I recently dropped my phone (with a case) and a rock may have hit the screen directly. There is only a tiny, minor scratch on the top of the screen but the internal touch sensor on the bottom half seems to be messed up. Certain places of the screen will identify touches randomly to other places on the screen causing random swipes and taps when typing. I probably wouldn't be able to type this post on my phone without it tapping out of the keyboard or exiting chrome completely. I could barely swipe through developer tools without it randomly tapping the enable toggle countless times.
Now I know I probably can't fix this cause its a hardware issue but is there any way to make my experience any better for me until I can finally get an upgrade?
RIP, looks like it was just the crappy block I was using to charge the phone
I had my Pixel 2 screen replaced with an aftermarket screen in Bangalore, India. The display works perfectly fine, and so id the touch for the first week. However, recently the touch screen is causing issue, in one of three states
State A) Completely unresponsive and not registering any touches
State B) Registers multiple false touches, all at once, making the phone unusable
State C) Works perfectly, as though nothing is wrong with the screen
I noticed this by enabling the "show touches" feature in developer options.
I have tried all of these without any luck:
- Restarting the device multiple times -
- Tapping and mildly pressing on the screen
- Cleaning the screen, removing all screen protectors
- Recalibrating the touch using a Play Store app
The phone has a mind of its own —*it switches between State A, B, an C.
Two questions
1. What is wrong with the screen?
2. What can I do to fix it?
screen is ****ed, theres nothing you can do to fix it without replacing it with an oem one. why you would use a third party one in the first place is beyond me.