As soon as I get on a phone call, the screen will turn off. I will push power and then 2 seconds later the screen will turn off again, but this time nothing will wake it up unless i hold the power button until it resets. I have no case and no screen protector on the phone. Any ideas? It's driving me crazy. It wont even allow to hang up the call or anything.
Bone stock. No Root.
Sounds like a proximity sensor issue. There's a little sensor about a half-inch left of the HTC logo text on the top of the screen. It's designed so when you put the phone to your face during a call, it will turn the screen off so it's not wasting energy/blasting the side of your face with screen light.
There's a lot of reports of screen protectors causing this issue.
Do you have a screen protector on that doesn't have the area cut out for the sensor? Zagg Invisishield has a little cut out chunk right where the sensor is at, but a lot of other screen protector makers didn't test before pushing their products out the door.
Kujila said:
Sounds like a proximity sensor issue. There's a little sensor about a half-inch left of the HTC logo text on the top of the screen. It's designed so when you put the phone to your face during a call, it will turn the screen off so it's not wasting energy/blasting the side of your face with screen light.
There's a lot of reports of screen protectors causing this issue.
Do you have a screen protector on that doesn't have the area cut out for the sensor? Zagg Invisishield has a little cut out chunk right where the sensor is at, but a lot of other screen protector makers didn't test before pushing their products out the door.
Click to expand...
Click to collapse
No screen protector at all.
If the screen is clean in the proximity sensor area and it's still doing it, I'd go get it swapped out. Some of them actually have issues, and the others were all caused by screen protectors.
regalpimpin said:
If the screen is clean in the proximity sensor area and it's still doing it, I'd go get it swapped out. Some of them actually have issues, and the others were all caused by screen protectors.
Click to expand...
Click to collapse
Tried it again while outside and it didnt do it, so apparently it only does it when indoors. I will go to sprint tonight and try it again. I just passed my 30 days though so does that mean I get a refurb one?
I had the same problem as you. They replaced the phone but I was within the 30 days.
blueluck77 said:
Tried it again while outside and it didnt do it, so apparently it only does it when indoors. I will go to sprint tonight and try it again. I just passed my 30 days though so does that mean I get a refurb one?
Click to expand...
Click to collapse
The phone is so new, there probably aren't any refurbs yet. You will most likely get a new one.
Sent from my EVO LTE using xda premium
do you get another phone if you purchased via a third party dealer like wirefly or amazon?
I had the same issue....and would only happen in low light.....but I did have a zagg so I made Best Buy put a new one on and made sure it was all the way to the top....that solved the issue. My phone still turns off after I make a call but power will at least turn it back on now. Before I had to reboot as well to get out of a call.
Good luck hopefully they will let you exchange it.
+1 on the screen protector issue. Best buy put a new on for me also due to the cut-out slightly covering just the edge of the proximity sensor, thus screwing with the screen on/off issue. Once they did that all was perfect.
Sent from my EVO using xda premium
Since this is probably not fixable with an ota, would be cool if they added a toggle to disable/enable the sensor in call.
Check Me Out On The Google Play Store!!!
Sent From My HTC Evo 4G LTE, On The Now Network From Sprint!
Related
Is there any way to change the sensitivity of the proximity sensor. It seems every screen protector I try makes the screen turn off when in a call even without anything near the sensor. I had to cut one of the screen protectors to get around it (but had messed up a corner when applying so I replaced it)
Or is there a way to completely disable it so I just have to hit the power button when in a call to manually turn the screen on or off.
+1
Dont have the same problem but would be helpful.
There is a distance setting in the build.prop file. You could try adjusting that and seeing if that helps.
Sent from my MB860 using XDA Premium App
Perfect. Changed the value (increased it from default of 60) and its working great now. Thanks for that tip.
Sent from my MB860
Well after further testing seems that it didn't fix the problem. Seemed to work when I first made the changes but now the screen is stroll turning off and no matter what I change the value to I can't get the proximity sensor to work right.
Spectre51 said:
Well after further testing seems that it didn't fix the problem. Seemed to work when I first made the changes but now the screen is stroll turning off and no matter what I change the value to I can't get the proximity sensor to work right.
Click to expand...
Click to collapse
According to the official Atrix manual -
http://www.motorola.com/staticfiles...s/StaticFiles/Atrix_US-EN_UG_68014798001B.pdf
Note: Your touchscreen might
stay dark if the sensor just
above it is covered. Don't use
covers or screen protectors (even clear ones) that
cover this sensor. To find Motorola accessories for
your phone, visit www.motorola.com/products.
Anyway, why do you guys keep using the screen protectors with this gorilla glass phones? I have carried Moto Milestone in my pocket for a year and D2G for 3 months and there are no scratches on them whatsoever.
I use them on every phone I get because although it is gorilla glass it can still get scratches under the right conditions and I for one do not want my $400+ phone to have a scratch on the screen. Never had a phone that had issues like this with screen protectors and the proximity sensor. Multiple iPhones, Dell streak, nexus one, droid, galaxy s. I've tried two different screen protectors with the atria and both have this issue.
I'm having issues with my proximity sensor too, but it seems that I can't make it turn off the screen when I'm talking. I'm not using any screen protector but I do have a case. It was working fine till a week ago but now I just have to block the phone every time I get a call.
The only difference is that I've installed 2 new games, maybe those are affecting the sensor?
Another thing that isn't working anymore is the auto brightness that's always set to minimum, no matter the light conditions. The phone is online for 260+ hours already (had it go to 500+ before but had to turn it off to add a micro sd card, just to be sure it would find it).
Spectre51 said:
I use them on every phone I get because although it is gorilla glass it can still get scratches under the right conditions and I for one do not want my $400+ phone to have a scratch on the screen. Never had a phone that had issues like this with screen protectors and the proximity sensor. Multiple iPhones, Dell streak, nexus one, droid, galaxy s. I've tried two different screen protectors with the atria and both have this issue.
Click to expand...
Click to collapse
Ugh... thing is if you drop your phone, it could crack both with screen protector and without one. If you grind the screen against your keys, it will get scratched through the protective film.
If you use it normally - the chance of scratching it really small. Just my 2 cents.
xploited said:
Ugh... thing is if you drop your phone, it could crack both with screen protector and without one. If you grind the screen against your keys, it will get scratched through the protective film.
If you use it normally - the chance of scratching it really small. Just my 2 cents.
Click to expand...
Click to collapse
My wife's phone had a screen protector on and got scratched by being in her purse. The actual screen though had no marks. The screen protectors help. Obviously each incident is different but they can help prevent some damage so in my opinion they are worth it.
Sent from my MB860
Hi there,
Got the same trouble..... but I just noticed it work fine at the sun (outdoor)..... turn the screen off in the shadow..... and switch on in the sun....
so I think a light adjustment has to be done.... but where ?...
Thanks to developers
anyone having issues with screen turning off as soon as a call is placed even when not near your ear?, i was trying to setup my voicemail and since the process ask you press numbers to confirm or # i coulnt do it cus the screen would just keep turning off and wont turn on until i use power ,but, it will only last few second and turns off again, very annoying cus i cant see nothing when i place a call, on my OG evo the screen would turn off when near my ear but would turn on as i got it away.
then the opposite the screen stayed on and had used power to turn it off but, it locked the phone and when i tried to unlock it as soon as i got near anywhere in the whole screen it would just turns off and wouldnt let me unlock it to hang up,
and sometimes it would stay on when i place a call and wont turn off even if i get it near my ear..
sorry for my english...
Are you using a screen protector or have a case on that covers any part of the front?
Sent from my EVO using Tapatalk 2
yes i am using a zagg screen protector, no cases.
i was thinking maybe the protector, i hope is not that cus i paid $25 plus $7 to have it install at bestbuy
i was just checking the protector and i can see it covers the sensor space...
EDIT: THANKS donatom3..i decided to risk the $32 dollars i spend on the protector and cut the little corner where the sensor is, now works great!! when i get to a call it wont turn off like it did, when i place a call and get it near my ear it turns off but when i get it away and comes on just like my OG EVO...thanks cus i only did it after you asked me..i hope this help someone else having issues...
Welp, woke up this morning to my phone screen turning of randomly as if it was against my head during a call. In order to make it come back, I had to press the lock button. Then I pressed home while still in call and locked the screen, pressed the unlock button to get to the lock screen and every time I touched the ring to unlock the phone, the screen turned off again. This forced me to yank the battery to get the phone back.
Same thing happened after another call, so had to reset again.
Downloaded AndroSens and under the proximity sensor tab, it says sensor_Status_unreliable and the number/bar stay at 0 regardless of whether my hand is over the sensor or not.
Is the proximity sensor in my rezound toast?
Some people have reported dust making it go wonky.
Do you have a screen protector covering the sensor on the front... I have had this issue. Just cut the protector around the sensor if that's the issue
GrayTheWolf said:
Some people have reported dust making it go wonky.
Click to expand...
Click to collapse
Unfortunately, no dust on the top of the screen and I don't see any under it. I'm familiar with pulling the phone apart, but don't really have the desire to do that just to check for dust haha.
Juicy92 said:
Do you have a screen protector covering the sensor on the front... I have had this issue. Just cut the protector around the sensor if that's the issue
Click to expand...
Click to collapse
I do have a protector, but it already came with notches around the sensor and FF camera.
I have the same probably but mine is from the digitizer "floating" up because the glue is weak underneath. If i push on the screen by the proximity sensor to push the digitizer down again the sensor works again. Haven't been able to fix. Maybe your digitizer is loose also.
Ullmz469 said:
I have the same probably but mine is from the digitizer "floating" up because the glue is weak underneath. If i push on the screen by the proximity sensor to push the digitizer down again the sensor works again. Haven't been able to fix. Maybe your digitizer is loose also.
Click to expand...
Click to collapse
Floating digitizer? Never heard of that before.
That's new, but sounds right
Ullmz469 said:
I have the same probably but mine is from the digitizer "floating" up because the glue is weak underneath. If i push on the screen by the proximity sensor to push the digitizer down again the sensor works again. Haven't been able to fix. Maybe your digitizer is loose also.
Click to expand...
Click to collapse
Same problem here, been debating on calling for warranty replacement
Sent from my ADR6425LVW using xda premium
Ullmz469 said:
I have the same probably but mine is from the digitizer "floating" up because the glue is weak underneath. If i push on the screen by the proximity sensor to push the digitizer down again the sensor works again. Haven't been able to fix. Maybe your digitizer is loose also.
Click to expand...
Click to collapse
Yeah mine is loose but only on the left side so my screen is tilted although it hasn't affected anything else it's still very annoying
Sent from my ADR6425LVW using Tapatalk 2
I've sent two rezounds back for the same problem. Call Verizon, they should replace it for you.
Sent from my GT-P5113 using xda app-developers app
You can try blowing out the speaker grille at the top of the phone with condensed air. Might clear any dust. Otherwise, call verizon.
I would rather not have to return to verizon and get a refurb if i can help it. I got the phone in November when it first released, so I'll definitely be getting a refurb. Oddly enough, androsens had it working just fine last night before bed. Put my finger over it, sensor went to 9/9, removed finger and went to 0/9. Repeatable for 10 minutes.
Then this morning it isn't working again. I can see the faint red light inside the housing for the prox sensor is lit. I might try blowing it out and disassembling/reassembling to see if I can fix anything.
Thanks all.
The touchscreen on my Verizon G3 started acting up recently. In the lower portion of the screen there's a space where it doesn't register my touches well (take a look at pics the space in between the lines don't really 'register' my touches. You can see in the second pic I'm currently touching the part where its not really working and it looks like I'm touching the screen with two fingers even though I'm only using one). When I type sometimes two letters are pressed at the same time or its like I didn't touch the screen at all which makes typing difficult and takes a lot of time. The whole screen sometimes doesn't hold a touch, like I tap and hold but it only 'holds' like I only tapped the screen. Other times when I'm sliding my finger across the screen, it starts jumping around. Now the top row of the keyboard/screen doesn't even register touches anymore so can't really do much now. I've reset the phone and didn't fix anything. Is this something LG would fix if I sent the phone in? If so how long is turnaround and will I have to reset it back to stock/unroot it?
if you have any type of glass screen protector on, take it off and verify the issue.
some tg screen protectors are junk, and have caused issues like this.
bweN diorD said:
if you have any type of glass screen protector on, take it off and verify the issue.
some tg screen protectors are junk, and have caused issues like this.
Click to expand...
Click to collapse
I had a $5 glass screen protector on it from ebay and thought that was the problem but when I took it off the problems ensued
Some g3s do have or develop touchscreen issues. Check under the back cover that there is nothing putting pressure on the display from behind, like a swelling battery.
It is probably a warranty issue, though.
Sent from my VS985 4G using Tapatalk
Sometimes if my G5 has not been used for an hour or so, it is refusing to wake up from double tap, power button or volume button quick shortcut. Only plugging it in has seemed to wake it up on these occasions.
Has anyone else had this issue?
Not yet.
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Same problem, same case.
What I have found is if you pull the phone out of the case it wakes up. Thinking proximity sensor.
Sent from my LG-H830 using XDA-Developers mobile app
Yup. It really doesn't take much extra coding for them to allow the power button to "Always Wake" the device... I imagine there will be an update in the near future.
As for me... jumping ship to the S7 edge. I really liked the G3, and was hoping this phone could have been that for me... Well, not like I really swap batteries out often anyway
Same case. Same issue. Take the phone out of the case and throw a blanket over yourself and the phone. (Simulating night) and my screen unlocks easy peasy. Something about this lifeproof case. You would think this issue would have been caught in testing and QC.
Yes the phone has a built prox. override. But it only becomes an issue at night. Outside of the case I have no issues with prox. sensor.
I have experuenced this exact same issue with my g5. Whenever its in the dark the power button nor the double tap will wake the screen when in the lifeproof fre case. When out of the case the phone works just fine.
Word to the wise though if you have a zagg glass screen protector and drop your phone both the screen protector and the screen with shatter even if in the lifeproof case. I just experienced this and now have a replacement phone. Just a heads up.
soninja8 said:
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Click to expand...
Click to collapse
I have the rs988 variant and I have noticed this behavior when screen is in always on mode: if I suddenly change from light to dark by covering sensors, the always on clock goes out and nothing I do will allow it to wake up, until I allow brighter light again and the clock reappears. and I can use the double tap and power button again to see the screen. I also notice that the always on clock seems to have an auto brightness independent of the screen settings - I leave screen at 50% no auto brightness, yet I still see clock light levels dim in low light, One other thing - I notice that when I answer a call the screen blanks out (the way it is supposed to ) but does not reappear until I press the power button, just taking away from my ear does not bring display back; I also have the lifeproof case. and just removed it and verified my display now works when I take away from my ear; I just took some spray lens cleaner and cleaned all the surfaces of the phone and case with a microfiber cloth and put it back together and has vastly improved the issue, maybe gone, not sure yet. Update: seems like no matter how clean it is there is still a problem with the case doing something to the proximity detector, cleaning made it better. I can always wake up with the power button for the calling screen(sometimes swiping across top sensor too), wonder if the sensor is a passive light sensor or active (rf/infrared emission)
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
There are allot of other cases you can use but not waterproof. That really sucks good thing for this thread I was going to buy a lifeproof case. Using a otterbox defender right now. Thanks for the post guys saved me some grief.
still under warranty?
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
if still under warranty, see if they will honor it. They did with mine but that was right at the beginning when these problems were linked to the case; mine was in the first 3 months, but the new one worked well for a while, now a little flakey again but not enough to bother me...too bad, a great case otherwise
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
It's not a bug and not poor implementation. Its not light for "dark rooms" lol.. As far as I know it's the proximity sensor. When it is blocked it means the phone is in a pocket or bag and should not register taps. It really makes sense. If you dont xover the sensor and double tap doesn't work ..well.. Well, eother you have defective device or sensor , or the sensor is blocked (maybe bad screen protector?). This didnt happen with my G5 even once. It works 100% (assuming I tapped the same place)
Are the problems as described in this thread still manifesting on current firmware?