Today I noticed that the proximity sensor of my G6 (H870DS) was on while reading in google books. I found that odd so I tried other apps, the home screen and screen off (tried disabling the knock-on feature and have always on display disabled)... still emitting.
Also found this reddit thread with people experiencing the same issue. OP suggests that it came after the July OTA.
I didn't notice any issues, or battery drain, except that it is always on. Did anybody else notice this? Is there a way to turn it off?
I'm not comfortable with it emitting all the time, might damage over time. Thx!
hi does anybody else experience this? thanks
ad astra said:
Today I noticed that the proximity sensor of my G6 (H870DS) was on while reading in google books. I found that odd so I tried other apps, the home screen and screen off (tried disabling the knock-on feature and have always on display disabled)... still emitting.
Also found this reddit thread with people experiencing the same issue. OP suggests that it came after the July OTA.
I didn't notice any issues, or battery drain, except that it is always on. Did anybody else notice this? Is there a way to turn it off?
I'm not comfortable with it emitting all the time, might damage over time. Thx!
Click to expand...
Click to collapse
it can happen when an app using the sensor and doesn't release it so it always scan and funtion. it can be phone app or a bug in firmware.
restart your phone and directly go to google book and check if this issue occurs or not.
:good:
Hey there, nope that's regrettably not the case. The proximity sensor starts emitting in the last stages of the boot process (LG logo animation is still on screen), so it's very likely not app related.
I am also experiencing the same issue. It also occurs when in Safe Mode. If you search reddit LG G6, you can see that several people have reported this issue. I've contacted LG and they know nothing about this issue. There must be a way to get a senior engineer at LG to look into this.
My proximity sensor always seems to be on. If I place a phone call and hold the phone next to my face and then remove the phone from my face, the screen does not turn back on. I have to use a BT headset to conduct phone calls.
Related
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
Hello,
I have the i9505 and i have flashed it with [ROM]【4.4.4】Google Play Edition 07-17-2014 - Pure Nexus Edition build now available by @Danvdh and i absolutely love this ROM and works like a charm but there is one thing i am having issue with and i cannot say its a bug as looked over his thread but no one has mention it. i can comment or post in the developer thread due to the number of posts i have, however i come here to ask for help.
When I make a phone call, my screen goes completely black and when i try wake the screen up, it would take multiple times and sometimes i have to take the battery out. The call somehow runs in the background, so if i managed to wake the phone, i have to pull the notification down fast to hang up and this is pain in the neck.
I suspected it could be the proximity sensor in my phone, i have no cover or screen protector, i cleaned the screen and still the same. so i ran few tests to check the sensor. phone detects the sensor but it doesn't do anything.
Thank you in advance
after many research, i have found the issue and its fixed.
http://forum.xda-developers.com/showthread.php?t=2569141
you will need to reset the proximity sensor depending on the values. i can say all working now
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