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
Related
Does anyone know if there is a way to adjust the proximity sensor.
It's proving a problem for my wife who uses the phone. When she's on a call the phone is intermittently sensing if she's holding it to her ear.
Hence being a capactive screen, when her cheek brushes the screen during a call the other end either hears DTMF or gets cut off by it touching the end call.
I called her yesterday and kept getting random DTMF digits sent to me, then I got sut off.
I was watching her use the phone and the screen was de-activiting (correctly going blank) for part of the call then coming back on, this would happen several times during one call.
Is this a hardware issue or software bug. Has anyone else suffered this problem?
Also happened to me a few times touching end call wih my cheek, really annoying.
Anyone else having the same problem with the proximity sensor intermittently not working during a call?
I had that problem on the old 1.43 ROM but it was fixed when I upgrade to 1.48.
I have this problem and I constantly have to call back and say sorry to my customers and blame it on the phone...
I have reported several errors to HTC and all i get back is "Take it to the retailer and get it changed, it must be a hw error", annoying as hell
1.48 not yet official in sweden.
TouchLockPro
You can try TouchLockPro, it has an InCallTweak, using the GSensor. Searching for accessing programmatically the Proximity Sensor though, for more options (e.g unlock by Proximity Sensor). It works on HTC Leo, people confirmed.
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
philtrick123 said:
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
Click to expand...
Click to collapse
Indeed, TouchLockPro detects itself the available sensors and uses the available ones. Of course you can configure detailed things (via pressing the BattClock), but the defaults are already the sensible ones
Thanks again ZuinigeRijder.
Just been doing some more testing and occasionally the screen flashes on for a brief moment during a call. Could it be the proximity sensor trying to turn on the screen? Or is it the G sensor not being very accurate?
In the application is there a way for me to adjust the G-Sensor angles that activate the screen off? i.e. 45+ Degrees activate ??
Or are there any other adjustments I could make during testing??
I found one more problem... I checked it several times....
If u make a call using portrait orientation of phone app (Rotated using BSB Tweak). Proximity sensor doesnt work at all.... i made a while lyin on the bed and no matter wat i tried it wasnt turning off the screen....
Then i kept it in portrait position for a few seconds den proximity started working again...
Is there anyone who can confirm me with this problem.... or is this issue only with my HD2
I have two SGS4's. On one, when I place a call, the call screen stays on and it turns off when I raise it to my ear. It then turns on when I pull it away.
On the other, as soon as I place I call the screen goes dark. The only way to get it back is to push the power button and unlock the phone.
The "Turn screen off during a call" setting is set on both phones.
Anyone have any idea what is causing this? Next step is to do a wipe, but that just sucks.
I'm on stock and not rooted.
Thanks!
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Sirchuk said:
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Click to expand...
Click to collapse
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
jprocket45 said:
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Nope, mine is naked for now. I'll have to do a reset today/tomorrow and see if that solves my issue. If not, I'm taking back to the store for an exchange. It's only been a couple of weeks.
To late for me to take it back but suppose to be a update coming soon that does alot of fixes so we will see Good luck like I said reset I did notice fixed it a bit let me know how it goes I'm threw sprint just curious if you have them only reason I ask if it's just a carrier issue with software or something I doubt it but just figured to see who you had lol
Sent from my SPH-L720 using xda app-developers app
Dial *#7353# and make a test
sent from my Galaxy
samersh72 said:
Dial *#7353# and make a test
sent from my Galaxy
Click to expand...
Click to collapse
That's what I was looking for!
Sure enough,the proximity sensor was always on and wouldn't go off.
I'm with T-Mobile and they have a 30 return/exchange policy if you buy it outright, which I had, so it only took about 10 minutes for them to exchange it!
Thanks for the testing code! XDA comes through once again!
Same problem when I'm making a call, the screen goes blank when I put it to my head and when I remove it nothing happens.
I tried *#7353# and the proximity sensor goes of but will not stop..
I'm currently rooted, could it solve the problem to go back to stock?
Possible Fix
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
I have had the same problem over the last 3 weeks and decided to take a gamble. I tightened up all the screws on the device and squeezed real hard on the area where the prox sensor is and poof... it works. I have no idea what was up but I feel like the sensor is loose and the pressure resolved the issue. Many other post have talked about cleaning the area over the prox real good and it works but I think its the pressure that is actually fixing the issue. Anyone else have any ideas? Sorry if this was posted incorrectly, I have never posted before but I felt this issue is a PITA.
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
My proximity sensor works - when I go into diagnostic, it goes green when I bring a hand near the sensor - my issue is that it doesn't seem to notice when I remove my hand and there no longer is anything proximal - until I hit the back button to exit the test. Other than blowing out the earphone jack, does anyone have a suggestion?
Thx.
divche said:
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
Click to expand...
Click to collapse
Proximity sensor
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
I guess what it comes down to is.....for some you can reset the sensor, for some they can blow it out with compressed air, but others actually have to take apart their phone to fix this issue.
marduj5 said:
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
Click to expand...
Click to collapse
hi
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Shohat said:
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
Click to expand...
Click to collapse
Hubris2 said:
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Click to expand...
Click to collapse
i'm sorry. i already tried your first solution and it worked like charm ! thank you ! :good:
HOw to solve, none of this works. How cann i clean proximity?
I'm sure most are familiar with proximity sensor issues in calls on 4.2.2 roms. It appears that everyone's experiences differ a bit. I've seen some say that buttons are pressed when the screen is off. For others, and myself, the screen doesn't turn off.
When I first moved to 4.2.2, I was pleased to find the Xposed module that fixes the issue. However, after I activated it, I had a black screen issue. During calls (if more than a few minutes), the screen/device would become completely unresponsive (temporarily). It wouldn't even respond to a long press of the power button. I attributed this to the xposed module and turned it off.
Unsurprisingly, the original issue resurfaced. I noticed that it seemed more pronounced when receiving a call (and the device was previously idle). It seemed as though the device wasn't waking up the proximity sensor when calls were received. I created a Tasker profile (with Secure Settings) to execute a "wake device" action when phone calls (incoming) are detected. It has been a week since I created this, and I haven't seen the problem since.
For anyone still experiencing the issue, this may be a solution.
EDIT: Solution quoted below.
CrazyTrond said:
If your screen doesn't turn off during a call and your ear is pressing buttons it means your sensor is not working. On my phone it works again after a reboot but after some time stops working again (you can check with android sensor box from play store). I found a fix that works, described in this post: http://forum.xda-developers.com/showpost.php?p=44872536&postcount=206
Click to expand...
Click to collapse
Simba501 said:
....It seemed as though the device wasn't waking up the proximity sensor when calls were received. I created a Tasker profile (with Secure Settings) to execute a "wake device" action when phone calls (incoming and outgoing) are detected. It has been a week since I created this, and I haven't seen the problem since.
For anyone still experiencing the issue, this may be a solution.
Click to expand...
Click to collapse
Interesting solution, this drove me crazy on a 4.2.2 ROM..... I'm on 4.3 now, and thankfully the issue isn't present. I really hope AT&T will stumble up to an official 4.3 release and skip 4.2.2.
Only experienced this on 4.1.2, all 4.2.2 roms have been fine for me
Galactus said:
Only experienced this on 4.1.2, all 4.2.2 roms have been fine for me
Click to expand...
Click to collapse
Funny. It was the opposite for me.
Sent from my HTC One
I'm on stock 4.2.2 and I have no proximity sensor issues. I've had some issues on 4.1.2.
Everybody has the proximity sensor issue: plug in the headphones, cover the sensor, make someone call you, after the call, the screen will wake. That will happen in your pocket, which is very bad. The only solution that works for me is copas' proximity tool extension (on Google play), which I enable every time I am using headphones...
Sent from my HTC One using Tapatalk 4
If your screen doesn't turn off during a call and your ear is pressing buttons it means your sensor is not working. On my phone it works again after a reboot but after some time stops working again (you can check with android sensor box from play store). I found a fix that works, described in this post: http://forum.xda-developers.com/showpost.php?p=44872536&postcount=206
No, you didn't understand. Sensor works during phone call. After hanging up, either the other party hangs, or you via the headphones button, screen turns on. This is a bug in all HTC devices, as far as I know. Try it. Make someone call you, cover the proximity sensor with your fingers, tell them to hang up, while still covering the sensor (simulating the phone is in pocket or bag) and see what happens. Screen will turn on.
Sent from my HTC One using Tapatalk 4
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
Otherwise my proximity sensor works perfectly, never had a problem with it.
Sent from my HTC One using Tapatalk 4
When I make phone calls the screen stays on when I put it to my ear. This results in touch presses ranging from muting the call, typing digits or really doing anything through the phones interface. Bloody infuriating.
It's very annoying and it shouldn't be doing it. I say shouldn't because it doesn't always; some times a reboot will seem to fix the problem but that seems to depend on how soon after the reboot a call is made/answered.
I have used AndroSensor to test the sensors (accelerometer, light, proximity etc) and they all seem to be registering values. For proximity, putting my finger over the sensor can result in a drop in value to 0.4in or 1.2in. This could be the cause of the issue as 1.2in is far to high a reading to correctly disable the screen afaik.
Possibly related; when the screen stays on, and the call is long I believe the normal screen timeout will kick in and the screen goes blank, meaning to hangup I have to wake the phone and unlock etc.
My questions are;
Has anyone else experience this?
Is it a setting, bug or faulty hardware?
Can someone else perform the same tests with AndroSensor to see if their results are the same as mine?
Moto X Play XT1562
Android 6.0.1
Build MPD24.107-52
Do you have screen protector applied?
Sent from my XT1562 using XDA-Developers mobile app
pijes said:
Do you have screen protector applied?
Sent from my XT1562 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope.
Did you ever get this sorted out? I'm having the same issue, but the proximity sensor numbers don't change at all. No screen protector, stock unrooted device on Marshmallow.
Same Problem
Actually even i have been having the same problem. It is not smethin that has been there forever it has started in the past few weeks.
I had this problem once, but a simple restart had solved it.
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