Hello, I have a problem with my LG G2 VS980 by verizon.
There are two problems depending on preloaded rom
1 The display shuts down immediately when call to someone. (after the conversation has will not turn on)
or
2 When someone call to me, after a conversation I can not unlock the screen (either the knock on, or by power button - appears on the screen and immediately turns off).
I've tested all the roms that are available. The one who runs without problem with the display there is a rom by HeatshiverSX - 4.3.1. The problem is that this rom has problem with the rotation of the screen.
Are you able to tell what's going on? Could someone help / advise? Thanks!
Anyone ?
LG G2 proximity sensor causes screen and touch problems during conversations
vivatbg said:
There are two problems depending on preloaded rom
1 The display shuts down immediately when call to someone. (after the conversation has will not turn on)
or
2 When someone call to me, after a conversation I can not unlock the screen (either the knock on, or by power button - appears on the screen and immediately turns off).
Click to expand...
Click to collapse
Did you manage to solve it by now?
If not, it seems that @Bam9 manged to solve it by a firmware update as he reported here.
It seems that there are two similar issues in LG G2 which are both caused by the proximity sensor which causes screen and touch problems during conversations:
The screen stays on and the touch buttons in the dialer (speaker, add call, mute, etc...) aren't responsive.
(This issue was already reported by @athorax here)
The screen turn off and goes blank while in conversation.
(This issue was already reported by @madafis here)
In both of these situations the only quick way to end a call is to pull down the status and notifications bar and hang up from there.
Thanks to @Bam9 and @EtherBoo , who suggested to clear the proximity sensor from the outside and squeeze the top left corner of the phone, I tried to clean it and put some stress on it - and it worked!
I have a glass screen protector (which don't block the proximity sensor), and I am rooted and using CyanogenMod 11 ROM.
I used ioroot to root and AutoRec, which comes with TWRP 2.7.0.0, to install CyanogenMod ROM.
However, going back to stock ROM (in my case, LG G2 D802, it's D80220C) won't help since the issue still exists.
What I'm sure is that it was pretty much okay in the beginning, and the situation became worse and worse - occurring randomly, until it arrived to a situation in which I can't use the phone properly during conversation.
Now that I discovered that I can put some stress on the proximity sensor it seems that I have a hardware rather than a software issue.
I have noticed that during a phone call proximity sensor doesn't while to taking i could hear those click sound(touch sound) and after i end call somehow i am in gallery or whatsapp or some other app.
Sent from my D6503 using Tapatalk
Can't say I've experienced that myself
Sent from my D6503 using Tapatalk
I get my calls cut off occasionally. That happened with my previous SIII so I guess it is just a standard problem with proximity sensors - they're not as effective as the manufacturers would have you believe.
Sent from my D6503 using XDA Free mobile app
The proximity sensor turns the screen off when the phones in a normal talking position. If you're led down, it's likely it won't. Try it, move the phone around and put your hand over the sensor.
Sent from my D6503 using Tapatalk
its not a proximity problem as the screen stays off if it was the sensor the screen would keep lighting up
I have had this problem and posted about it already
I have tried with the double tap to wake feature off to see if it was that but no such luck!!
---------- Post added at 09:43 PM ---------- Previous post was at 09:42 PM ----------
heres the thread I started http://forum.xda-developers.com/showthread.php?t=2769679
i also find myself in different places after call, this happens with flap cover closed
I usually have same problem, I click on power button to turn off the screen and usually it solves the click problem.
Don't know why android phones proximity sensor doesn't works as good as iPhone. Never had that problem in any iPhone and for android it seems all the phone have this problem.
ikm19 said:
Don't know why android phones proximity sensor doesn't works as good as iPhone. Never had that problem in any iPhone and for android it seems all the phone have this problem.
Click to expand...
Click to collapse
never had this problem on my HTC one X
and I have never heard of the problem on other phones either!!
I also used to have problems with proximity sensor not waking up the screen during a call. It seemed to be completely random: sometimes it happened after only 1 min of talk time, other time after 5 minutes, other time it worked ok even after 20 minutes of talk time. I turned off "double tap to wake up" and I never had any problems since. I'm not sure it's not a coincidence, but it worked so far (10 days).
About the cut off calls:it's not the proximity sensor. For me that happened on any European firmware. I tried the original .55 Vodafone Germany (the one that the phone came with), .55 UK and .402 Germany. It happened randomly on all of them. I tried repair firmware, factory reset, re flash with FlashTool. Nothing worked. The ones that work flawlessly for me are TW firmwares. I tried both .69 TW and currently on .402 TW. No cut off calls, no problems, no overheating in 4K (about 10 minutes recording).
Turning of double tap to wakeup seems solved my problem.
my PS works great. never had that issue. maybe you should take your phone to diagnostics.
Im having the same issue. Hearing ticks/clicks when im on a call and I end up somewhere after a call. I hope Sony fixes this. Temporarily I lock my phone to prevent this problem.
ikm19 said:
Turning of double tap to wakeup seems solved my problem.
Click to expand...
Click to collapse
No it doesn't I tried that weeks ago
In the Diagnostics app, go to Test Device and run the Ear Proximity test. Mine passed just fine.
Sent from my D6503 using Tapatalk
Fixed my Proximity/Ambient light Sensor
Hi, I had this problem since new and I tried installing lots of stock and custom roms (Stock US, Stock SP, Stock TW, Miui, CM11) but it was until I installed EXISTANZ rom, and a hard reboot, and then it magically started working. I knew it wasn't a Hardware issue because when the phone boots it worked for few minutes, then stop reading samples. But I've been with this rom for 3 weeks and I don't have any problem with this (Already installed and update, reset the phone and still working).
So if you have the chance, install this rom.
double tap to wake issue
raducanmihai said:
I also used to have problems with proximity sensor not waking up the screen during a call. It seemed to be completely random: sometimes it happened after only 1 min of talk time, other time after 5 minutes, other time it worked ok even after 20 minutes of talk time. I turned off "double tap to wake up" and I never had any problems since. I'm not sure it's not a coincidence, but it worked so far (10 days).
About the cut off calls:it's not the proximity sensor. For me that happened on any European firmware. I tried the original .55 Vodafone Germany (the one that the phone came with), .55 UK and .402 Germany. It happened randomly on all of them. I tried repair firmware, factory reset, re flash with FlashTool. Nothing worked. The ones that work flawlessly for me are TW firmwares. I tried both .69 TW and currently on .402 TW. No cut off calls, no problems, no overheating in 4K (about 10 minutes recording).
Click to expand...
Click to collapse
Hi ,
I also encountered this issue and i performed a test with and without the "double tap to wake" option.
The result is: without the option activated all is fine but when the "double tap to wake" option is activated and the proximity sensor is covered(screen is black) if you double tap the screen it remains closed. So seems that if you are engaged in a conversation and you miss touch twice the screen, it will remain closed.
Hi all,
First sorry from bringing an old thread.
I am an owner of two black d6502 xperia z2
One of them is running perfectly, the other suffers from the same behaviour the op describe.
When handling a call, the proximity sensor works fine, it is making the screen black but it is NOT LOCKING the menu, I.e the screen is black but you can swipe the status bar down and enter different menu while the proximity sensor is keeping the screen black.
My second xperia z2 behave normally, when handling call, proximity sensor turn the screen black and locks the menu, if i swipe on the screen the software ain't responsive.
Was anyone successful to fix this issue?
Elie.
The problem is in the screen protector. There is a post in the Sony Forum how to solve the problem.
It's simple hardware problem... you have to remove back cover, find connector of proximity sensor, remove it and put again, press hard and it will work...
for long time I've had that issue, but until I ordered new sensor tried to do that trick and it helped
so about 2 months ago my note 3 started vibrating when using the camera. I first noticed it in snapchat, the camera wouldn't focus and I noticed the phone is vibrating. Basically every time an app uses the camera and it fails to focus the phone would start vibrating for a really long period of time, which then makes pics distort and the camera fails to focus again which extends the vibration. I thought it's a touchwiz rom error (I was using xnote when it happened for first time (4.4 btw, don't remember which version of x-note it was) but then I tried out some AOSP roms and the stock s5 port and then I came back to xnote v16 and it kept doing this vibration thing. Any ideas what causes it/how to fix it?
I have no idea. Mine started doing this just now. But I noticed it's not just in the camera app, it's anytime the phone is in landscape no matter what app is running.
same issue on N9005
I can't remember when it started but it's rendered the camera basically useless. Sometimes it finds focus and stops the vibration... what I found helps somewhat is shaking the phone rather violently, it stops vibration and then works as normal, untill I close the Camera app and go back into it, then same story. I can't think that this is a hardware issue as it is able to focus and take pictures just fine. This is a major annoyance but I don't think it's unsolveable. I'm no developer but may it be at all possible yo fix this with an xposed module or tweak that completely disables the vibration motor in the phone while in the camera app? Is this a possibility or is the problem deeper than that. I've tried loads of ROMs and it's present on all of them, the leaked Lollipop firmware as well. It's impossible to go back to Jelly Bean AFAIK but before I updated to Kit Kat I didn't have this issue.
I have this problem too
Vibrate when im in camera...not always somtimes
5.1.1
I guess this was never solved?
I believe I was having this phone disconnect issue since I flashed a lollipop based rom. What happens is when I am on a phone call, the call will disconnect. My proximity sensor is working fine. To test what was going on, I made a call, put my finger over the proximity sensor, and can double tap anywhere on the screen (which is off), even a slower double tap, and it will end the call and wake the screen.
I cannot find any setting for this. It appears my face bumps the phone while talking. I've had this G2 for a while, and only experienced it since I flashed CM12 lollipop, and I even tried another lollipop Resurrection Remix and it still does the same thing.
Also another tidbit, my screen was dropped and a local shop did replace the front glass and digitizer recently, and I think I upgraded to lollipop shortly after I got it back. Not sure if it has anything to do with it. All other features on my phone work great.
Any ideas?
Hi.
I have an SM-910F, android version 5.0.1 with a bugging problem. During calls when i get a second call or some other notification the screen turns on and i end up pressing different buttons and commands with my cheek. proximity sensor functions ok as it turns on and off correctly when i dont have call waiting or when no other notifications get in the way. i believe the problem comes from the stock phone app which cant be replaced. i tried in call settings to disable "Notify during calls" and/or the "Call-related pop-ups", all in vain. It is very annoying as i ended some calls and noticed i opened almost 10 new windows (bluetooth, mobile data aso screens).
is anyone else having this issue? is there a solution to this?
my only hope is that this will be fixed with the new android update (5.1.1) which seems to be taking forever.
Anyone?
Sent from my SM-N910F using Tapatalk
I face the same issue too especially when I'm getting a pop up call notification. I just put the phone back and forth on my ear an it works sometimes. Guess it's a Samsung bug.
and still no word on the android update. i need a fix for this issue. its annoying
well, the update arrived but with no damn fix