I just noticed the issue today. When I tried making a phone call, the screen went completely black, and when I tap the screen, power button and volume keys it doesnt show any display.
Communication works because I can talk with the person I called. I also tried the other way around by calling my Nexus 4, and after answering it the display also goes out.
It only comes back after the call ends and you have to hit the power button to make it lit up. Did a factory reset and it didn't fix it....
Is this a known bug in 4.2.2?
Did some research online. And I saw this http://forum.xda-developers.com/showthread.php?t=2001861
Found out that the issue is with screen protectors blocking the proximity sensor.
I recently put one on my Nexus 4. Just the cheap ones from local vendors here. I just had to cut the upper left corner.
SOLVED! :good:
1. Activate pointer location in developer option
2. Touch at around 900-1000 pixels of X axis
3. Got two point in my finger
Is it only me or everyone else get this issue? Anyone get solution to repair this bug?
Sometimes my screen can even unresponsive to my finger and freeze(but volume button and power button working) until I sleep the screen and turn it on again.
faqisupgraded said:
1. Activate pointer location in developer option
2. Touch at around 900-1000 pixels of X axis
3. Got two point in my finger
Is it only me or everyone else get this issue? Anyone get solution to repair this bug?
Sometimes my screen can even unresponsive to my finger and freeze(but volume button and power button working) until I sleep the screen and turn it on again.
Click to expand...
Click to collapse
Just tried at 900-1000 of x-axis. Only one point displayed all over the x axis. Maybe others will be getting this. Can this be because of the specific ROM you are using? I am on Paranoid android with tablet layout.
Sent from my GTN7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Ive tried so many custom ROMs, but none get rid of my issues..
But when i used TWRP recovery, the bug seems not appearing at all. Guess this is software bug..
Sometimes my screen freezes by itself and need to be sleep and awake to get the screen working..
Hello XDA,
I have a weird problem going on with my Note 3. I had an issue where my screen would not shut off during calls so I immediately figured I'd test the proximity sensor with some debugging app and also the built-in service menu. I went ahead and did that and noticed it was sort of working but one of the values (the main one that ranges from 0.0 to 8.0) stayed at 0.0 and didn't change. I did some research and used an app that I believe recalibrated it and it began to work perfectly… EXCEPT, when the screen goes off during a call and SHOULD be locked from touch events I can still touch the screen and it is responsive, meaning even thought the screen is black I can end the call, mute it etc granted I touch the right area seeing as I can't see anything. Another thing that's going on that leads me to believe this is some sort of software bug is, when the screen is turned off due to the takeover setting, when I press the home button to turn it back on, it turns back on BUT the front app is lowered and i am brought to the home screen as if the screen was on and I hit it. Weird huh?
Any help would be appreciated…
Verizon Note 3 running on T-Mobile and CM13
I don't expect there's much that can be done if the hardware is to blame. This reminds me of my Galaxy S3 -- so it's a problem that everyone else fixed ages ago. When I touch the touchscreen, very very often, it doesn't register that touch at all. Sometimes you get a delayed response. This leads to all kinds of fun where you tap the screen again at the same moment that PH-1 responds to your first touch, so it applies your second tap to whatever is going to come up on the screen a half second later.
Does anyone know if this can be fixed by firmware updates or is this a hardware issue?
same here! my huawei honor 8 is much faster
Touch Screen unresponsive is a hardware issue. I had the same problem with my HTC U11 until it was replaced. Essential phone does not have this issue assuming screen is working properly.
Sent from my Pixel XL using XDA-Developers Legacy app
Touchscreen responsiveness, having to tap more than once for the screen to register a touch and awful light bleed caused me to send it back. But it was from the first batch that were manufactured. No issues on my U11, but I bought it in early August.
Confirming u installed the most recent OTA (NMI64C)? Because that fixed my touch issues.
flakko86 said:
Confirming u installed the most recent OTA (NMI64C)? Because that fixed my touch issues.
Click to expand...
Click to collapse
Yep that's what I currently have. I think the phone found that update on its own a few days ago. Touch issues seem to be hit or miss and maybe less frequent since that update. We'll see how it goes from here.
touch unresposive is due too thermal trottling or like me the launcher stock.
Solved with Evie launcher
Using a different launcher and such didn't help me out, unfortunately. Besides the tap issues, scrolling through a web page in any browser or with apps was extremely slow and laggy. My PH-1 was already being returned, so I couldn't test the latest software update they pushed out. But my device also had some horrible light bleed all along the left and right edges.
No light bleed here. But [email protected], the responsiveness of this touch screen is worse than any other phone I've had. And the new software update hasn't helped at all!...
Same issue!
I too am having touch screen issues. Today, I was on the phone and went to go back to the screen and the screen stays black. I tried everything including pressing the power button and I got no response from the phone whatsoever. The only thing that finally worked was to press the power button and the volume down button and hold them at the same time to shut my phone off after the call already ended. In addition to that issue , I also use Swipe to type and when I do so it often skips over letters and types words that I am not even trying to type . It should be mentioned that I'm a very experienced swipe user and I have not had this problem with my S7 Edge or my Wellington . Also, I should mention that I have the most recent OTA. Also, has anyone else noticed that the camera shutter has a serious delay in it even with the Google camera mod?
I've noticed my touch screen freaking out sometimes. It has more to do with the screen having too many prints on it. Guess it's a bit too sensitive. I wipe the phone screen off and it's fine. Doesn't happen very often. I have one of the latest batches, pure white.
Already looked into this?
Sensitivity:
1. Tap on the "Settings" icon on the home screen.
2. Tap "Language and Input".
3. Scroll to the very bottom of these settings and tap "Pointer Speed".
4. Increase the slider to make the touch screen more sensitive and easier to tap. Decrease the slider to make your touch screen less sensitive and more difficult to tap.
5. Tap "OK" and then experiment with the results.
Essential Support still working on that and they send me this instructions for now.
I think it makes the user experience better.
Shadow Samurai said:
I've noticed my touch screen freaking out sometimes. It has more to do with the screen having too many prints on it. Guess it's a bit too sensitive. I wipe the phone screen off and it's fine. Doesn't happen very often. I have one of the latest batches, pure white.
Click to expand...
Click to collapse
Same.
Hope it will have a fix soon.
Early on I got the black screen that required a power hold reboot, since moving to Oreo I've not seen that
basongwe said:
Same.
Hope it will have a fix soon.
Click to expand...
Click to collapse
This I have experienced too
edit : solved with oreo beta
basongwe said:
When I touch some letters on my keyboard, it's unresponsive. Same with some apps. I don't know why this phone is so frustrating to use even if it's a very good smartphone.
EDIT : I'm on Nougat's lastest version, not on Oreo beta.
Click to expand...
Click to collapse
Had it on both versions to be honest, but hoping it's getting resolved as time goes on!
Just got mine..same thing but...
My screen was doing fine until i installed "All in one gestures". I was messing around with side gestures and this caused the screen to be non-responsive. I un-installed the app, reinstalled it and set it up differently and now it is fine.
I hope this helps.
D4rk_nVidia said:
Already looked into this?
Sensitivity:
1. Tap on the "Settings" icon on the home screen.
2. Tap "Language and Input".
3. Scroll to the very bottom of these settings and tap "Pointer Speed".
4. Increase the slider to make the touch screen more sensitive and easier to tap. Decrease the slider to make your touch screen less sensitive and more difficult to tap.
5. Tap "OK" and then experiment with the results.
Essential Support still working on that and they send me this instructions for now.
I think it makes the user experience better.
Click to expand...
Click to collapse
This helped me. I have mine set at approximately 3/4 and I'm happy one day in. Seems to work great now. I would still like smoother scrolling though. Thanks a million.
I was also having trouble with Android Pay and then found a post about the NFC being located near the bottom of the phone as opposed to the top as on my Nexus 6p.
With these problems fixed I'm completely pleased with this phone.
ugh! Flashed back to stock on 7.1.1/NMJ32F/436 as that is how my phone came, and now I have no touchscreen after re-boot?!?!?! any advice? Please?
Thanks,
DJ
I have a Moto G4 that has had the touch screen become very erratic lately. This issue appeared shortly after a factory reset. The phone is stock, recently OTA updated to NPJ25.93-14.7. It frequently freezes and won't respond to touches of apps or the home/back/recent buttons, and won't side scroll to the next screens properly. Sometimes random apps launch on their own without any touch, and if you try to quit them with the back button they keep relaunching. The problem is intermittent.
I activated "Show Taps" in Developer Options and when the problem is happening there is a tap dot near the lower right side of the screen. It bounces up and down a little bit and vibrates sometimes. When this dot is visible tapping on anything else like app icons or buttons usually has no effect, however the taps are shown on the screen. If I hit the power button to make the screen go black it will sometimes recover when I reopen the display, other times it takes a reboot.
Wondering if it's a hardware issue, a guy at a Verizon store who seemed to know more than most said it was a faulty digitzer--it's seeing touches where there are none. I've replaced displays successfully before, would just like to have a confidence level that the digitzer is really bad before doing that, as opposed to a software or other hardware issue. Any ideas about problems that might cause this problem, like other hardware or a corrupted OTA? Seems very hardware-ish to me, but I'm no expert.
I have Drive links to a couple of short videos on the symptoms, can send links. Much appreciate any insights.
Mine has that issue as well. It will spam the 9 key on the unlock screen or anything in that spot if an app is open or what is on that spot at the home screen. I have to double unlock the phone to fix it. I guess turning the screen on and back off resets it for that session. But it's mostly every time the screen goes dark and comes back up I have to turn the screen off and back on to use the phone.
I had a similar problem and was able to send it in under warranty and get a replacement phone
G4 Digitizer or ghost touch
Apparently this is called Ghost Touch issue, and affects many phones. One solution tried is to disable Battery Optimization for System UI and Google Now Launcher in Settings>Battery>Battery Optimization. That seemed to cure it for a week or so, but the problem returned today. I can sometimes recover form it by hitting the power button to blank the screen and then reopen. Other times it requires a reboot. I see all kinds of alleged solutions out there from dimming the brightness to removing tempered glass protector to using a slow charger, but those don't seem like real fixes but workarounds (if they even work at all). Any other ideas?