TD;DR - my touchscreen stops working whenever I get a phone call.
I'm experiencing a problem with the touchscreen. When I answer a call and the proximity sensor is activated, the touchscreen stops responding. It continues to be unresponsive even after I move the phone away from my head or end the call. I've mapped the power button "end call" or I can't hang-up )
Sometimes I can press the power button twice (sleep/wake) to restore functionality but on some rare occasions I cannot get the touchscreen to work again without rebooting.
This did not happen when the device was new (running Nougat). When I first encountered it I though it might be due to custom roms so I did a full reset to factory RUU (Oreo I think). This too had the issue. I'm currently running Fagyi's LOS 16.
When the touchscreen is working it works flawlessly. When it stops it mostly doesn't work at all - but double-tap to wake will still wake the device - it just doesn't respond to any touch input.
There's a really easy way I found to force the problem. Here are the steps:
1. With my phone sitting on my desk I call my phone.
2. When the phone rings confirm the touchscreen works.
3. Place my hand over the top area of the phone to activate the proximity sensor.
4. Move my hand away so the screen comes back on.
5. The touchscreen is now dead until I either press power-button twice or, in extreme cases, reboot.
I've watched logcat as this is happening and I could not find anything interesting that seemed related.
Any suggestions are greatly appreciated.
Related
Hi Guys,
Ive noticed that sometimes when i use the speakerphone (either by pushing the on-screen button or flipping the phone over), it works fine. However, once the call is over, the touchscreen is deactivated it seems. Nothing works. Cant press anything. As for the hardware buttons, the windows button works, and the power button works. The volume, call, and end call buttons do nothing.
Not sure if this is relevant, but I only notice it if the phone was flipped over (with touchscreen down). If i used speakerphone with the phone facing up, doesnt seem to happen.
The only ways ive found to fix this are to soft reset with that little button under the cover, or to miss a call. (obviously, if a call comes in, I cant answer it as none of the ways you'd use to answer a call still work). After the call is missed though, the touchscreen comes back to life.
any ideas??
thanks
havent notice quite this.. but something similar...
when i wanna make a quick phone call
i open the keyboard type name of contact,
select the contact and hit enter to make the
phone call.. when i close the keyboard to turn
the phone to my ear, half of the screen looks
normal and have of it looks all MESSED UP...
im sure is not a hardware problem or anything.. ( well i hope so )
i think is not bcuz it only do it on that situation..
besides that my screen is normal..
bump
phone been around a while now...maybe someone else noticed this problem...
I've noticed that sometimes my phone will go into "sleep" mode like when you quickly press the power button. Maybe a quick tap of the power button to wake it up will help.
I just got my new AT&T S3 a few days ago, and there's a problem I seem to be having with every single phone call I make or receive.
During the call, the screen goes dark, and none of the buttons seem to be able to wake it up again until the other party hangs up. I've literally had to rip my Otterbox off and yank the battery out to hang up during one call to an IVR system that just wouldn't hang up on its own (I guess I could have pressed the right combination of buttons to force a reboot, but at that point I was in no mood to spend 5 minutes experimenting with different permutations of power, vol-, and vol+ to find the magic combo).
Here's what I think might be happening. Note that I haven't exhaustively spent lots of time debugging it yet, on the theory that if it's a common bug, somebody else already has:
Call begins.
Hall Effect sensor triggered by proximity to face. Screen turned off, touchscreen input disabled.
Display settings ticking away in the background force timeout after N seconds. Ignores the fact that the display is already off, and puts the phone to sleep "for real" (at least, the part handling the UI), neglecting to re-enable the power button first.
I'm done with my call. I move the phone away from my face to hang up (or pull up the keypad to enter a selection). Hall Effect sensor broadcasts intent to turn on screen and re-enable touchscreen, and its intent falls on deaf ears because the phone is officially asleep and ignoring it.
Panic. Press power button. Seemingly ignored (though the phone might be waking up enough to see a note telling it to ignore the button, and going back to sleep without further action).
Anger. Press home button. Press volume buttons. Swear violently, and get really mad.
(other party hangs up; lock gets released, phone is awakened and problem seems to go away)
or...
(furiously press various two- and three-finger combinations of power, vol+, vol-, and home until either the call terminates or the phone reboots)
For what it's worth, the same bug show up if I make a call in my car, but the bluetooth call-control button DOES work, even though the phone itself appears to be a darkened unresponsive brick, and triggering a hangup via bluetooth wakes it back up again. I KNOW this isn't due to Tasker or anything, because I've had this problem literally since I made my first call on the new phone to terminate my Sprint account, when it was 100% stock and virgin.
I had the same problem with my white s3 . Then I changed the screen protector and cleansed the proximity sensor with a dust free cloth and haven't had any problems since
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Well, I found the root of my problem: the S3's proximity sensor isn't a Hall Effect sensor, it's near-infrared... and the plastic shell on my case is yellow, which meant it was reflecting too much near-infrared light back into the sensor and triggering it continuously from the moment the LED turned on. I ended up blackening the plastic that surrounds the sensor using a Sharpie marker, and it solved the problem.
Samsung S3 won't hang up
I have the same problem and found that I can insert earphones to phone to make light come back on. After looking at this forum I also noticed a setting (which I haven't tried yet). It's the 3rd from last under settings. Settings-Accessibility-Answering/ending calls-The power key ends calls.
I'm hoping that will work.
Hi,
I have a weird bug with the touchpad of my phone.
It stops working after unlocking the locked screen.
Ok, here is what happens:
I dropped my galaxy W on the road, then someone drove over it...
After this accident, the LCD screen as well as the glass broke but the phone could still start and was ringing when called.
I decided to take my chance and bought the parts to fix it. I have changed the digitizer and the LCD screen.
The phone boots just fine.
I am able to swipe to unlock the phone and access the home screen.
However, once I access the home screen, the touchpad doesn't respond anymore! Volume buttons, home button and power buttons are still working fine. Options and return button are not working too.
I am even able to access my missed calls from the locked screen if I press on the missed call button directly on the locked screen.
I have tried to access the recovery mode. By pressing volume up+home+power, I can access it, but I then need to press onto the "options" button which is not answering. I am stuck again.
I have also tried to access the downloading mode. I can access the "warming!" menu (with explainations about the dangers related to custom OS), but the phone stops answering after that. I press the volume button up or down nothing happens.
Is it a software issue or a hardware issue (related to the motherboard?)
Thanks for you help.
liquid can be contacted. Odin or try the setup ..:good:
Hi,
I have been noticing some problems in my Galaxy a5 2017 after updating to nougat (India).
1) the battery seems to be dropping much faster
2) screen does not go blank during calls. That is the proximity sensor should blank the screen when the phone is lifted to the ear and come on again once its taken off. But that does not happen at times and I have to restart the phone after which the problem goes away for sometime and reappears again. I have installed Smart Screen On/Off (from Luutinhit), Home touch and Volume on my phone.
I have installed Smart Screen On/Off so that I do not have to keep pressing the hardware power key all the time to lock the phone.
Home Touch is installed as I do not want to press the hardware home key all the time I want to go to the home screen.
Volume is installed to avoid pressing the volume hardware button all the time I wish to change the volume for each app.
Is anyone facing the above issues?? Also are the above installed apps responsible for the erratic proximity sensor behaviour??
If anyone could suggest alternate good apps that work well with finger print sensor I would be grateful.
Thanks,
Hi
I got the xt-1710-09 and recently installed the android 9 upgrade which never was officially released for this version.
everything works fine except every few weeks something crashes which results in the screen always staying off. I first considered it a hardware fault since the contacts to the screen aren't that good any more which results in gfx glitches when applying slight pressure to the screen.
Now I realized when booting into TWRP via ADB the screen goes on again and the phone works for a few weeks.
does anybody have an idea what could be the cause?
I suspect the code of the fingerprint sensor. since this code already crashed earlier which resulted in the fingerprint gestures not working any more until reboot.
when the screen is dead everything works fine except well the screen and touch control. which mean the phone is almost unusable except via "ok google" speech control.
using the fingerprint the phone vibrates approval. (not the wrong fingerprint vibration)
but regardless of pressing power button or fingerprint sensor, the screen just stays black.
i believe I rebooted the phone several times via letting run the battery down or pressing the power button for a long time. this did not help. only booting into TWRP always (temporarly) solves the issue.
the phone is unlocked, rooted and twrp installed.
thanx