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?
Related
Well, I've searched the forums for this phone and I haven't found anyone with this issue.
When I make or receive calls, the proximity sensor either doesn't turn off the screen or, more often, it does but turns it back on after a while. This results in random keys being pressed making noise and, eventually, it presses the button to end the call or puts the call on hold and dials another number.
It's very, very annoying. Could it be something on the settings? Hope it's not hardware... Any sugestions on how to solve this?
I'm using Miui 1.9.9 with franco.kernel from 10 set.
The proximity sensor is located at the top left corner of the phone (next to the speaker) and flashes red while active. Make sure you cover this area with your head when speaking. I am left handed and sometimes the sensor doesn't detect anything because of the way I hold it, this could be the case with you also...
There are some apps that can help you test the sensor if it works or not.
Mine was stupid too with stock rom, but with custom roms it works very good. detects even finger in 3cm range and turns on screen after 2 seconds.
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
I searched, and didn't find any other posts about this, but the search engine here seemed a bit flaky.
I installed SlimKat 4.4.4.build.8.0 on my Samsung Galaxy S3, um, last year I think it was. I had previously been using SlimBean, having dumped the original Samsung ROM fairly shortly after I bought it. Since then there has been weirdness that relates to the proximity sensor.
I used E-Robot to disable the screen when anything is close to the proximity sensor. So put it face down, screen off; put it in my shirt pocket face inwards, screen off; leave it on the desk face up so I can see the screen, screen on. Naturally - hold it to your ear on a phone call, screen off, though that's a basic function of the proximity sensor, it did that anyway. On the flip side, if it was blanked and you uncover the sensor, the screen would come back on, but it would be the Lightning Launcher lock screen that I prefer. I got used to Lightning Launcher from SlimBean.
After installing SlimKat, when covering the sensor, first the volume controls show for a few seconds, THEN the screen goes off. Coming out again, the Lightning Launcher lock screen would not show. This got a bit awkward before I figured it out. I usually put my phone in my shirt pocket screen inward, so that the sensor triggers the screen disable. But now, since the volume control is showing for a few seconds first, I discovered that my chest would brush against the screen, randomly adjusting one of the volumes as it went in my pocket. Since I usually have the volume turned all the way up, the only way was down. I missed a few phone calls that way before figuring out why my phone wasn't ringing.
So I have disabled that E-Robot thing now. BTW, there's no way to turn the SlimKat screen blanker off? I would have tried that first, but could only find how to set the timeout, not how to turn it off.
More recently, though this may be a new hardware problem, but it's a big coincidence ... now the proximity sensor refuses to work at all. It always thinks it's covered. This is a really big pain, since as mentioned above, the proximity sensor is designed to disable the screen when you hold it to your ear, only now it disables it the moment the phone call starts, AND refuses to enable it after the phone call is over. The sensor still thinks it's being held to your ear, the screen stubbornly refuses to switch on, no matter what buttons I press. Only way I can get out of that state is to pull the battery. This is not good. (On the other hand, this sort of thing is why I always get phones with swappable batteries, as a very experienced computer dude, I know that sometimes you just have to kill the power.) So anyone I call gets to hear my swearing as I rip the case open and pull the battery out, before I can end the phone call. Though pulling the battery naturally ends the call. lol
About the same time I noticed the proximity sensor no longer working, I noticed the up volume button also isn't working. That could have been broken for awhile, I rarely use either volume control. Part of the reason for doing this entire proximity sensor disabling the screen thing is so I could avoid wearing out the physical buttons. The S3 is old, but I like to keep my computer hardware running for a long time.
Sooooo, proximity sensor and volume controls interact in odd ways, then both fail. That's a pretty big coincidence. Though having just written that, I have come up with a new theory. Maybe some common part of the physical circuitry for the sensor and the button was going flaky, such that the sensor triggering sent noise through the up volume control, triggering the on screen volume controls before blanking. Still, a coincidence that it only happened after installing SlimKat. Also, wouldn't this trigger both volume controls and screen disable at the same time, rather than within a few seconds? No idea how Lightning Launcher fits into this new theory.
So I'm still not sure what's causing this, or how to fix it. Other than going back to SlimBean to see if that fixes anything. It doesn't look like I can go forward, 4.4.4 looks like the last SlimRom made for the S3. At least according to OTA.
Anyone got any ideas? "Buy a new phone" isn't a good answer for me right now, can't afford it.
onefang,
I have a S3 that I ran the Slimkat 4.4.4 build 9 on for a while (9 months). There is a known issue with the CM package (used in SlimKat) that causes the volume button not to work correctly. When you are on a call, the call volume can not be raised or lowered. There may be other issues. I am currently running the CyanogenModCM12.1-20151117-SNAPSHOT-YOG7DAO1K6-d2att rom and the performance is much better than Slimkat.
Hi, anyone have issues with galaxy s8 when making/receiving calls ? My S8 was pre-ordered and on the first day of usage im faced with this issue, when making call or receiving phone randomly lights on display (once) and genlty randomly vibrates (as you press home button or nav button), then im take away phone from ear and put it back to ear display turns off, sometimes it keep turned off as normaly but sometimes it lights on again and vibrates, so i have to do previous steps or if ignore that issue than display turns off after some time and when im take away phone from ear to end call phone is locked and display won't light up until press lock button. Also im noticed that when im lock phone or even take it in hand (fingers touches both curved sides of display) phone also gently vibrates and turns from AOD to lock screen, this issue is also randomly. Some times AOD screen suddenly goes bright and than fades like it should be. After two weeks of chatting with samsung and store support im was send it to "service", they tested phone and after 10 days im received phone with status "no problems detected, software reflashed" but issues still not gone. And im can't replace it with new one because store refuses to replace it and says that they don't replace devices with software issues. Now im stuck and don't know what to do.
P.S. in *#0*# menu proximity sensor ADC values randomly keep changing even if nothing is in front of sensor, values are between 79-125 and when completely put finger on sensor values is 16368
Same issue here. Not sure why.
same for me too, international dual sim version s8
I have little bit different issue related to light sensor. My phone doesn't turn off the screen and locks in a pocket or if I close light screen by hands.
Sent from my SM-G950F using XDA Free mobile app
I have the same issue (also the oversensitive home button issue too).
I have a similar issue. But my screen never lights up. Neither during a call or when on the desk, for example. But during calls it sometimes vibrates as if I hard pressed the home button even though the screen is still off and I haven't pressed anything with my face, nor have I received any notifications. It doesn't seem to happen once every minute either (some phones notify you of every passing mine during a call).
It's not a big deal for me, just kind of curiously annoying.
Sent from my SM-G950F using Tapatalk
Check in settings on ambient display, pocket mode, etc. Or maybe a cache wipe and reboot will solve.
Like Settings-Display-Screen Mode
-Keep screen turned on/off
Thanks to Samsung and Consumer Rights Protection Centre, together we forced store to replace phone. It was a factory deffect, so anyone who has similar problem im advice to replace phone.