Hi everyone,
I recently changed my HTC's Aria digitizer because it was cracked.
During the process everything went smoothly however after that I have discovered that when a person calls me or when I call someone the screen turns off and never gets back to normal if there is no other "stimulation" such as putting the phone to charge for example.
My guess was there was a problem with the sensor so under settings I chose to keep the screen awake at all times during a phone call, still, I am having the same problem.
The weird thing is that sometimes when I remove the battery cover everything works fine and the screen keeps on, but sometimes not, so its not a constant rule..
I may have messed up something during the replacement of the digitizer (its just the glass not the lcd) such as removing the sensor and not placing it back correctly but the thing is that I dont really know the components of this device so Im not sure what is what..
If anyone could help me to understand the problem a little bit I would really appreciate it.
Thanks in advanced..
Anyone? Please
The sensor is right above the AT&T logo. If the little rubber ring isn't perfectly aligned with the sensor, you will have this problem. My wife's phone has a similar problem and it is fixed (temporarily) by firmly pressing on that corner. The adhesive strips have failed and I am looking for a source besides "Repairs Universe".
Thanks a lot!
I will try to take apart my Aria again and see if I can align it correctly
thanks again
glad that i found this, having same issues with my wife's aria, will give it a shot
Hello guys! After a long search on the recent questions in this amazing forum I couldn't find anything similar to my girlfriend problem...
Her Nexus 4 was just fine until the update to 4.3.. After that it started to show a problem during/after calls, the screen turns black completely (even when is not near the face or anything) and its impossible to do anything with the phone after that. Power button doesn't work, and there is only two ways to get the phone working again: the other person hang up the call.. or to hard press the power button until the restart...
I tried already to change for a 4.3 ROM and now I changed it to a 4.2.2 ROM... any idea or suggestions to a possible solution?
Thanks a lot guys!
I too recently had this problem. There was a simple fix after dealing with it a couple of days. My 4yo daughter had been playing with my phone after which I started having the problem. What I found was one of her hairs had become stuck in the bumper and was resting on the screen over the proximity sensor. Once I cleared that, no more problem.
The sensor is on the upper left of the screen.
Sent from my Nexus 4 using Tapatalk 4
If You use screen protector and it goes over sensors, than will be the reason of Your problem. Just remove it.
It could be the 4.3 update. I didn't have any such issues until the update and then they began. AndroSensor confirms that no matter what, proximity sensor is at 0.
Any thoughts on what to do short of RMA?
--Dan
I can assure you its your screen guard that is creating an occlusion for your sensor on top left. Remove it and it will definitely work.
vasusharma.28 said:
I can assure you its your screen guard that is creating an occlusion for your sensor on top left. Remove it and it will definitely work.
Click to expand...
Click to collapse
Not sure if I mentioned it earlier (perhaps in another thread) - no screen guard. That wasn't the issue. Finally, I changed the proximity sensor itself, all bueno. No RMA which means avoiding a bunch of hassles (namely new phone, data xfer, etc).
--Dan
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!
hi, i recently got a new screen for my phone since i broke it. i called my friend to give him the good news but when after i dialled his number the screen went black. i would have to either press power multiple times or shut off my phone to get it back to normal. what do i do to fix it?
Do you have a screen protector?
devinwifi said:
hi, i recently got a new screen for my phone since i broke it. i called my friend to give him the good news but when after i dialled his number the screen went black. i would have to either press power multiple times or shut off my phone to get it back to normal. what do i do to fix it?
Click to expand...
Click to collapse
it is a common issue with after market screens and it has to do with the proximity sensor.
check this video on YouTube "Nexus 4 Disassembly Teardown - Screen & Case Replacement - Drop Test Repair LG E960" -- sorry I am not allow to post links yet
if you follow the steps on that video with regards to the proximity sensor, it would be installed correctly and the holes would line up perfectly between the gasket and sensors. However, that doesnt seem to work, you want to now install with the tab facing the other way, you will now see that the holes do not line up correctly and the gasket is partially covering the sensors, dont panic, that is what you want it to look like. This worked for me and for many others.