Database Users

Screen locks immediately during calls - proximity sensor not working?

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?

Screen turns black during call, but then won't turn back on?

On my AT&T Galaxy S4, when I make a call the screen goes black when my face is next to the phone. This is good.
However, when I take my face away the screen will NOT turn back on. If I hit the [Power] or [Home] buttons, it will sometimes turn back on, but often times it requires several presses or requires me to wait several seconds until the phone turns back on.
I've tested this on stock and several ROMs...
Does anybody else have this problem?
If so, how do I fix it?

Pick up a can of compressed air and blow in the earphone. Sure enough the proximity sensor works perfectly now. I have solved this problem doing this. Tell me something
Enviado desde mi GT-I9505 usando Tapatalk

Dial *#0*#
You can test your proximity sensor readings here. It should turn the screen green and vibrate the phone constantly while your hand is in proximity. You can also see the numerical readings. The sensor works to about 6 inches.
If its not acting right, then you need to use faux kernel or you have a hardware failure.
If it is acting right, then use a better rom.

I seem to be having this issue on stock rom. When I bring my hand close to the sensor in diagnostic mode it goes green...but it doesn't stop when I remove my hand and there's nothing nearby. This seems to mirror the experience...where the phone goes black during a call, but doesn't wake up when it's removed.
faiyo said:
Dial *#0*#
You can test your proximity sensor readings here. It should turn the screen green and vibrate the phone constantly while your hand is in proximity. You can also see the numerical readings. The sensor works to about 6 inches.
If its not acting right, then you need to use faux kernel or you have a hardware failure.
If it is acting right, then use a better rom.
Click to expand...
Click to collapse

Hubris2 said:
I seem to be having this issue on stock rom. When I bring my hand close to the sensor in diagnostic mode it goes green...but it doesn't stop when I remove my hand and there's nothing nearby. This seems to mirror the experience...where the phone goes black during a call, but doesn't wake up when it's removed.
Click to expand...
Click to collapse
Yes, exactly!
I've flashed back to stock and tried that test screen. The sensor is OK at first, then I move my hand over it and it turns green and stays that way even after I remove my hand.
It seems like the sensor is half-working but gets stuck in the "on" position...

that sucks. i guess its time to contact samsung about warranty. just make sure theres no dirt on the sensor or anything

rpboronat said:
Pick up a can of compressed air and blow in the earphone. Sure enough the proximity sensor works perfectly now. I have solved this problem doing this. Tell me something
Enviado desde mi GT-I9505 usando Tapatalk
Click to expand...
Click to collapse
This is exactly what I done only I used a straw and I blew down it like hell and it cleared the problem. My phone was due to be returned to be fixed under warranty today but I tried a last ditch attempt and with the straw and blowing down it into the earpiece (aimed slightly towards the proximity sensor) I managed to sort the problem. It seems a little dirt or dust gets on the sensor and makes it malfunction.
Give it a whirl to see if it will work

[Q] LG G2 Proximity Sensor causing me problems!

Hello all, I know this issue has been raised before but there hasn't been a fix. I'm currently facing trouble putting my G2 in a waterproof ziploc bag because of the proximity sensor. It detects that something is in front of the phone and doesn't allow me to turn it on. I can't knock-knock to turn it on. The moment I turn it on using the back button the screen will time-out. This is a feature of the phone, not a defect. I want to know how to disable it. Please, if anyone knows how to do it, tell me! Your help will be much appreciated!
Edit: if you want to replicate the problem try putting your finger on top of the front camera - the phone will not turn on when knock-knock

Android App Disabler
I have found an app that may help, but I do not know how to use it! If anyone knows how please tell me!
https://play.google.com/store/apps/details?id=com.hatcyl.android.Hardware_Disabler&hl=en

Wierd, I just experienced what you are talking about by testing it out. If the phone is already on and being used and you cover the proximity sensor it doesn't turn off, but, if it is covered as you turn the phone on it will immediately turn itself back off. Even if you use the button and try to swipe the screen quickly it doesn't prevent the phone from turning off automatically.
Unfortunately, I am not able to help you with this problem as it is fay beyond my limited knowledge of linux/android etc. However, maybe this reply will cause someone who can help you with an easy solution.
One thing that would almost certainly fix it would be to switch to one of the alternatives rom not based on the stock LG software/kernel like Cynogen Mod or Android Open Source Project, etc. Those roms use a different kernel and also a standardized version of android that is open source. So the sensor problem will likely not be an issue, however, I believe you lose either knock on or knock off functionality with Cynogen Mod, not sure which one as I am still running LG based rom.
Some people prefer the open source alternatives to the LG rom, so, you might even like it better than the LG setup. However, it will require some effort/reading to learn how to root your phone. Then to flash your particular model of G2 with a custom recovery and then to install a rom/kernel. It is not that hard though, you just have to acquire the knowledge to avoid bricking your phone by doing something foolish.

DornoDiosMio said:
Wierd, I just experienced what you are talking about by testing it out. If the phone is already on and being used and you cover the proximity sensor it doesn't turn off, but, if it is covered as you turn the phone on it will immediately turn itself back off. Even if you use the button and try to swipe the screen quickly it doesn't prevent the phone from turning off automatically.
Unfortunately, I am not able to help you with this problem as it is fay beyond my limited knowledge of linux/android etc. However, maybe this reply will cause someone who can help you with an easy solution.
One thing that would almost certainly fix it would be to switch to one of the alternatives rom not based on the stock LG software/kernel like Cynogen Mod or Android Open Source Project, etc. Those roms use a different kernel and also a standardized version of android that is open source. So the sensor problem will likely not be an issue, however, I believe you lose either knock on or knock off functionality with Cynogen Mod, not sure which one as I am still running LG based rom.
Some people prefer the open source alternatives to the LG rom, so, you might even like it better than the LG setup. However, it will require some effort/reading to learn how to root your phone. Then to flash your particular model of G2 with a custom recovery and then to install a rom/kernel. It is not that hard though, you just have to acquire the knowledge to avoid bricking your phone by doing something foolish.
Click to expand...
Click to collapse
Thanks a lot for the tips but i think there should be a way to disable the proximity sensor on the stock rom. If all else fail then i will try and install custom rom like the ones you mentioned.

catfish90 said:
Thanks a lot for the tips but i think there should be a way to disable the proximity sensor on the stock rom. If all else fail then i will try and install custom rom like the ones you mentioned.
Click to expand...
Click to collapse
Yes, it would have been a nice feature for them to include, I wonder if they just overlooked it. That being said, I'm not sure if there is anyway to do it on the stock rom. Hopefully for you it will be possible in time. Good luck!

I can confirm that CM11 is not affected. I put it in a baggy and it will still respond to all input.

zero0422 said:
I can confirm that CM11 is not affected. I put it in a baggy and it will still respond to all input.
Click to expand...
Click to collapse
Really? That is good news! Sorry but im to custom roms - is aosp or paranoid android rom based on cm11? I believe those are one of the best custom roms for android. I might install one of them soon.

catfish90 said:
Really? That is good news! Sorry but im to custom roms - is aosp or paranoid android rom based on cm11? I believe those are one of the best custom roms for android. I might install one of them soon.
Click to expand...
Click to collapse
I think you meant AOKP? But either way, AOKP, PA, and CM are all AOSP based ROMs. Just different paths. PA has some really great features right now, but lacks a couple tiny things that keep me on CM11.
If you're looking for a no frills mostly stable ROM CM11 is probably the best choice, plus Delta updates make it pain free.

zero0422 said:
I think you meant AOKP? But either way, AOKP, PA, and CM are all AOSP based ROMs. Just different paths. PA has some really great features right now, but lacks a couple tiny things that keep me on CM11.
If you're looking for a no frills mostly stable ROM CM11 is probably the best choice, plus Delta updates make it pain free.
Click to expand...
Click to collapse
I heard that people are having random reboots on CM11 - is it true? What are Delta updates?

catfish90 said:
I heard that people are having random reboots on CM11 - is it true? What are Delta updates?
Click to expand...
Click to collapse
I get some here and there, nothing major. Delta updates take the nightly, and process it to pull only the changes, so you get about an 11mb update instead of a 150+ mb update. Its all in an app.

This rom solve the issue:
http://forum.xda-developers.com/showthread.php?t=2582845
Very nice ROM, works perfect, better then stock

fsi09 said:
This rom solve the issue:
http://forum.xda-developers.com/showthread.php?t=2582845
Very nice ROM, works perfect, better then stock
Click to expand...
Click to collapse
Thanks, i might test it this weekend.

Working
i have a g2 d802 and i have tried the script workaround and is fine, but when i do put the phone next to my ear the screen remains on and does not go off, is this something i can chhange?
is there another workaround?
i am using Cm11

Had the same problem.
Great temporary fix: right after you unlock the screen hit the volume button once or twice. Not a permanent fix but it works for the time being.
It usually blacks back out because something is wrong with the proximity sensor next to the front camera. Either it's covered partially, dirty, a screen protector is peeling off over it, etc. I've read that some people have problems with the screen not coming back on during calls because the proximity sensor is messed up. Some said to use a high powered suction vacuum and put it up against the screen to get debris out of the cracks or simply try wiping it clean if there's something on it. Hopefully it works!

1509
Oh god, I just permanently fixed my proximity sensor \o/
So I had the issue where the proximity sensor would detect something near it, making it hard to wake up the phone (screen getting dark after half a second, as the phone thinks it's still in my pocket) or keeping the screen dark after a call.
An app displaying the proximity sensor output was showing the sensor always reporting 0cm when it's not working, and 5cm when it's fine.
If your get "no data" in a test app, then sorry you have another issue. Probably a dead sensor. If you do get the sensor always returning an obstacle at 0cm, keep reading!
I also noticed that pressing on the screen around the sensor kind of made it work. So I thought for a while my screen was slightly off, maybe slightly unglued.
But it's the opposite: it's actually the sensor that was moving a bit, thus getting too far from the screen surface - and detecting the screen as the obstacle. Just by a ridiculously small amount.
Now THE FIX:
I switched off the phone, and removed the SIM and the rear door,
I removed the 7 screws holding the top plastic plate and buttons
On the rear of that plastic plate with the buttons, there's a small soft pad that pushes on the sensor to hold it against the screen: that's your target! That pad is just a tad too thin.
I've put a very small piece of adhesive tape (I used a slightly thick double-face white tape, maybe a tenth of a millimeter) on that pad,
Then I put everything back together and... the sensor now works! All the time! And the knock-on too of course.
I can't post a picture of the pad below the button assembly. But if you look for "OEM Part - AT&T LG D800 G2 (WHITE) Rear Back Housing + Buttons + Camera Lens" on ebay, and look at the 2nd picture, the pad is the fully black rectangle on the top left, on the right of the empty black rectangle and below the half-circle small opening (probably for the light sensor).
Pic of the fix: reho.st/self/cb4a29e598652f925a19f05770b6f192b09af8f5.jpg

Sly_North said:
Oh god, I just permanently fixed my proximity sensor \o/
So I had the issue where the proximity sensor would detect something near it, making it hard to wake up the phone (screen getting dark after half a second, as the phone thinks it's still in my pocket) or keeping the screen dark after a call.
An app displaying the proximity sensor output was showing the sensor always reporting 0cm when it's not working, and 5cm when it's fine.
If your get "no data" in a test app, then sorry you have another issue. Probably a dead sensor. If you do get the sensor always returning an obstacle at 0cm, keep reading!
I also noticed that pressing on the screen around the sensor kind of made it work. So I thought for a while my screen was slightly off, maybe slightly unglued.
But it's the opposite: it's actually the sensor that was moving a bit, thus getting too far from the screen surface - and detecting the screen as the obstacle. Just by a ridiculously small amount.
Now THE FIX:
I switched off the phone, and removed the SIM and the rear door,
I removed the 7 screws holding the top plastic plate and buttons
On the rear of that plastic plate with the buttons, there's a small soft pad that pushes on the sensor to hold it against the screen: that's your target! That pad is just a tad too thin.
I've put a very small piece of adhesive tape (I used a slightly thick double-face white tape, maybe a tenth of a millimeter) on that pad,
Then I put everything back together and... the sensor now works! All the time! And the knock-on too of course.
I can't post a picture of the pad below the button assembly. But if you look for "OEM Part - AT&T LG D800 G2 (WHITE) Rear Back Housing + Buttons + Camera Lens" on ebay, and look at the 2nd picture, the pad is the fully black rectangle on the top left, on the right of the empty black rectangle and below the half-circle small opening (probably for the light sensor).
Pic of the fix: reho.st/self/cb4a29e598652f925a19f05770b6f192b09af8f5.jpg
Click to expand...
Click to collapse
I just want to pop in and say thanks for this fix. It really helped. :good:

proximity sensor issue
i had the same issue for my lg g2 . when i searched the internet for solution , all i got was to install proximity sensor disablers , rooting apps to disable them . i have solved the issue interms of hardware . the solution goes :
1 . go watch a youtube video of teardown of lg g2
2. in the video there will be showing a plug that connects the sensor to the circuit board.
3 . pick up a screw driver , open the casing of ur phone
4. unplug the connection between the board and the sensor
5. put everything right back
6 PROBLEMO SOLVED BAYBE
thank me

Just in case someone searched and finds this thread - the easiest way to disable the proximity sensor on any rom/kernel is to go through Xposed and this module: http://repo.xposed.info/module/com.mrchandler.disableprox
Works on 4.4, 5.0.2, Cloudy's rom, Dorimanx's kernel...

Big Thanks!!!
Sly_North said:
Oh god, I just permanently fixed my proximity sensor \o/
So I had the issue where the proximity sensor would detect something near it, making it hard to wake up the phone (screen getting dark after half a second, as the phone thinks it's still in my pocket) or keeping the screen dark after a call.
An app displaying the proximity sensor output was showing the sensor always reporting 0cm when it's not working, and 5cm when it's fine.
If your get "no data" in a test app, then sorry you have another issue. Probably a dead sensor. If you do get the sensor always returning an obstacle at 0cm, keep reading!
I also noticed that pressing on the screen around the sensor kind of made it work. So I thought for a while my screen was slightly off, maybe slightly unglued.
But it's the opposite: it's actually the sensor that was moving a bit, thus getting too far from the screen surface - and detecting the screen as the obstacle. Just by a ridiculously small amount.
Now THE FIX:
I switched off the phone, and removed the SIM and the rear door,
I removed the 7 screws holding the top plastic plate and buttons
On the rear of that plastic plate with the buttons, there's a small soft pad that pushes on the sensor to hold it against the screen: that's your target! That pad is just a tad too thin.
I've put a very small piece of adhesive tape (I used a slightly thick double-face white tape, maybe a tenth of a millimeter) on that pad,
Then I put everything back together and... the sensor now works! All the time! And the knock-on too of course.
I can't post a picture of the pad below the button assembly. But if you look for "OEM Part - AT&T LG D800 G2 (WHITE) Rear Back Housing + Buttons + Camera Lens" on ebay, and look at the 2nd picture, the pad is the fully black rectangle on the top left, on the right of the empty black rectangle and below the half-circle small opening (probably for the light sensor).
Pic of the fix: reho.st/self/cb4a29e598652f925a19f05770b6f192b09af8f5.jpg
Click to expand...
Click to collapse
After almost a week trying to solve this, your answer hit right on the spot! I found it funny how the roms not based on stock LG's are not affected by this issue, but all of the LG's ones (I've tried 4 LG's stock roms and CloudyG2) so I've always assume this was a SW issue (and probably can be addressed via SW) so when I get to your answer saying that could be fix tearing the phone apart I was reluctant to do so, but as I've told you guys I was desperate. On a sidenote, the Stock JB ROM is not affected by this, but it is death slow for this times.
BTW, I've wanted to have a ROM that had the LG's camera app (any version) since the ones that came on the CM ROMs wasn't really good enough for my taste, so now I'm rocking the CloudyG2 3.2 ROM with any issues so far.
Your fix gave my phone some solid 6 more moths of life! (at least!) THANK YOU!

Hand wave to wake lock screen does work ! Well kind of

Hello everyone this is my first post here.
I just upgraded from a Moto X XT1060 to the newer Moto G 3rd Gen 1GB/8GB XT1540 two weeks ago, And found out that it does have a hand swipe to wake the Moto Display but it only works once every lock screen cycle.
I'm assuming this behavior is a bug, Can anyone else test this for me ?
1. Make sure Moto Display is on and set the phone on a table, let the screen go black, wait 2min.
2. Now swipe your hand over the screen about 1/4inch from the glass, Walla !! screen turns on ! woohoo ! lol
3. Now hand swipe again, Yep it doesn't work anymore....
4. Now unlock the screen to show your main home page etc.
5. Now set the phone back on the table and let the screen turn off again, Wait 2min and repeat hand swipe, Works again lol ! but again only works once.
Anyone else seeing this ?

No it doesn't work for me.
Sent from my MotoG3 using XDA Free mobile app

That is moto display, the moto g 2015 shouldn have swipe to unlock.

not working for me
Tested under these conditions :
1) Moto display ON
2) Layed it still on bed , table.
3) waved my hand really close to it several times, and i touched with out disturbing it on every spot ..
Result :: Not working wave gesture,
NOTE: if ur device moves in x,y,z directions even a little.. the moto display gets active ONLY ONCE.

Well weird lol my moto g is bugged or something.
I do have both hand gestures turned off, Both the camera twist and chop for Flashlight are off, Wonder if that's why I have this bug.
I hope someone else posts this same behavior or I guess ill be forced to return it since it could be a defective product. Would any of you return it for this bug ?

No go for me either. OP are you sure you're not somehow moving the phone when you wave your hand by it? I mean it only takes an ever so slight movement to active the Moto Display, so if you're waving your hand 1/4 inch from the screen maybe wind is moving the phone causing it to work?

Proximity sensor can activate moto display to.

I'm sure I'm not moving the phone when i wave my hand over it, I'm also sure it is the proximity sensor.
But can anyone check this, I didn't run Google play store to update apps yet so I'm thinking its because of that it hasn't updated the Moto app. Which in turn is something else that's strange, Within the first 12hours of setting it up it only updates like 13 apps etc. then after 12 hours of sitting the Google play store is offering more to update like Moto boot and some others, Weird that letting it sit for 12hours it then is offering more to update very strange.

garikfox said:
I'm sure I'm not moving the phone when i wave my hand over it, I'm also sure it is the proximity sensor.
But can anyone check this, I didn't run Google play store to update apps yet so I'm thinking its because of that it hasn't updated the Moto app. Which in turn is something else that's strange, Within the first 12hours of setting it up it only updates like 13 apps etc. then after 12 hours of sitting the Google play store is offering more to update like Moto boot and some others, Weird that letting it sit for 12hours it then is offering more to update very strange.
Click to expand...
Click to collapse
yeah, that might be the case, when i got the mobile the 1st moto app used to behave strangely.. that was infact good and less intelligent
1) BEFORE:when i power on torch using Chop CHop it used to be ON till i OFF with either Chop-chop or manually turn off. that is the only case to turn off.
NOW : if i keep the phone idle without disturbing it in Flipped/regular way it stops automatically after 2 seconds or so..
2) moto display also became more agressive,while i am sleeping if bed's cushion goes down even a little it would lit up .. that was a little annoying.
These are the things i had seen changed..
so.. i am sure that updates had changed the behaviour of Moto App, that might also be the reason.. i will try to uninstall updates and check it
---------- Post added at 08:55 AM ---------- Previous post was at 08:45 AM ----------
Yo genius it works
i had uninstalled the Updates and now the proximity seems to be working but it just Lights up the moto display, and quickly turns off the display
and that i call it a WORKING
if you update your Moto app, this will be GONE
Tested conditions :
1) on a table, by keeping a haircomb near to it for a second and removed it with out disturbing the mobile
2) On the bed same with my hand on the proximity sensor or a second and removing it
NOTE: i am not waving my hand over it, it seems like i am not perfectly waving it else it would also work ..

Awesome thanks !, So it only does the hand wave once then doesn't do it again until you go to home screen then let it fall back to sleep ?

I noticed my twist motion has become far more sensitive, as well...I'm forever opening my camera by accident. Especially when I take my phone out of my pocket.

All the Reviews I've read for this phone were saying the same thing that the twist for camera is sensitive.

Whenever I wave my hand over it, it wakes up for about 3 seconds then turns right off. I woke it 3 times in a minute.
Not unlocked but awake.
I'm using gestures in Moto and in Res Remix ROM.

So your using a custom ROM with your Moto G 2015 ? and it lets you do the wave more then once per lock session ?

It works very well just you need to wave your hand over proximity sensor and it will wake your phone.
Sent from my MotoG3

Clock appears on lock screen when the phone is moved

Just got a G5 Plus yesterday.
When the phone is at rest, if the surface moves or I pick it up without touching the finger print sensor or the power button, the clock/battery/date appears very dimly on the screen and disappears after a few seconds. Is there a way to turn this feature off? I have searched for ways to turn it off but haven't found a way yet.
I'm worried that when I work out with the phone in my pocket, the motion will wake up the phone and the sweat/heat will accidentally call 911 or something even though I haven't pressed any buttons.
Thanks

It's called Moto Display. To turn it off, go into the Moto app and hit display. I've used it for years and I don't think the phone ever was unlocked while in my pocket. If you have a password/pin or fingerprint set up, it's almost impossible to become unlocked in your pocket.

roygbiv859 said:
It's called Moto Display. To turn it off, go into the Moto app and hit display. I've used it for years and I don't think the phone ever was unlocked while in my pocket. If you have a password/pin or fingerprint set up, it's almost impossible to become unlocked in your pocket.
Click to expand...
Click to collapse
To add onto this. If it's in your pocket the display isn't turning on due to the proximity sensor being blocked by the pocket. You can test this by holding your hand in front of the earpiece for 5 seconds, remove it and the screen will turn on. The screen will also turn on if for example you pick it up from a table.
EDIT: Didn't see that he mentioned this in the OP. It's perfectly normal. Would also like to add I've had the Moto x which has the same features for years and it never accidentally unlocked or called anyone. And I didn't even have a password set on it.

bvsbutthd101 said:
To add onto this. If it's in your pocket the display isn't turning on due to the proximity sensor being blocked by the pocket. You can test this by holding your hand in front of the earpiece for 5 seconds, remove it and the screen will turn on. The screen will also turn on if for example you pick it up from a table.
EDIT: Didn't see that he mentioned this in the OP. It's perfectly normal. Would also like to add I've had the Moto x which has the same features for years and it never accidentally unlocked or called anyone. And I didn't even have a password set on it.
Click to expand...
Click to collapse
It's a great feature. It's the sole reason I'm sticking with the stock rom.

roygbiv859 said:
It's a great feature. It's the sole reason I'm sticking with the stock rom.
Click to expand...
Click to collapse
It's the main reason I go with moto phones now. All the other companies are starting to do it though but you can't get those phones for cheap like the g5 plus.

Operating as designed

I miss my g4 plus. It was stolen. Can anyone send me an APK for the Moto display of g5 plus. I want to use that on my phone ( Honor 6x). Wish it works. Thanks.

first thing i turn off.

roygbiv859 said:
It's a great feature. It's the sole reason I'm sticking with the stock rom.
Click to expand...
Click to collapse
Ambient display/moto display works fine on custom ROMs and is configurable.

username8611 said:
Ambient display/moto display works fine on custom ROMs and is configurable.
Click to expand...
Click to collapse
Can you tell me which ones? I was under the impression the stock rom had a separate processor set aside just for moto display which meant longer battery life

I turned this off because while driving at night and the phone rest in the passenger seat or on my lap/on the seat between my legs, the display would keep lighting up in response to vehicle movements. Too distracting.

Is there a setting to make that clock brighter and stay on a bit longer PLS?

What is pocket mode and how it works
Pinned ringtone inactive when phone is screen is on table