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
Related
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:
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 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.
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Sounds like Doze.
I don't find anything related to Doze or "standby" about this screen.
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
David_26 said:
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Click to expand...
Click to collapse
thophan1975 said:
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
Click to expand...
Click to collapse
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
Sounds like there is an issue with the proximity sensor (not light sensor).
It's setup to turn the second screen off as well as disable knock on if the phone is in your pocket. Even during daylight hours if you put your finger within an inch of the sensor when the main screen is off, it should trigger it.
It seems your sensor may just be messed up.
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
There are a few apps on the play store you can try to fix it if you are rooted. You could also try a sensor app to see if the proximity sensor is showing feedback properly although you might need to be rooted for the apps to show the proximity sensor properly (not sure). My note 4 had a hardware test in the service menu not sure how to do it on V20 though.
Same Issue
Edit: Resolved the issue. Please read this post. There is a small rubber gasket-type thing that sits in the hole of the phone's frame where the proximity sensor is positioned. That rubber gasket was not included with my replacement screen. I pulled the rubber piece out of my original, broken screen, and installed it into my replacement screen. I am no longer having issues with the phone in the dark.
I am experiencing the same issue. I have a T-Mobile LG v20 (H918) and I cracked the screen last week. I ordered a replacement LCD assembly and installed it myself. Everything works fine during the day or in a well lit room, but at night, in a dark room, I experience all of the issues you are reporting. I am finding other posts online with our same issue, but as of yet, no resolution.
Even though the second screen is set to always be on, at night, in a dark room, it turns off almost immediately after locking the phone. It is almost as if the phone is in a "deep sleep" or something, because the following also occurs:
Knock On will not wake the phone
Fingerprint sensor will not wake the phone
Even connecting to the phone via AirDroid / AirMirror the phone doesn't wake
Need to press the power button multiple times to wake phone
Providing a light source immediately turns on second screen and resolves all issues
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.