Related
Hello guys,
at first i want to excuse for my language mistakes, it's not my native language.
I have a problem with my phone. If I make a phone call, the proximity sensor deactivates the screen, like it should be, but the screen won't wake up, after I push the phone away from my ear. It takes a long time, until I can see something again on the screen. I don't want to create a new thread where I am crying about this issue, I want to solve this problem.
I also searched at many other developer-forums and i noticed, that this happens to many people around there and everybody is crying about it.
Everybody who can provide informations, that can help to solve this problem is invited to share his experiences with us.
The HD2 is a very beautiful mobile phone, but this problem is really annoying.
I made a lot of tests to find the reason of this problem.
Things, that I did without getting clear results:
1. Dirty sensor
It could be possible, that the sensor or the glass plate is dirty inside and because of this, the sensor can't recognize it properly.
2. Light sensor
It was random, that I expected that this issue also depends on the light sensor. I made a call and the screen goes off, like every time. Now i take the flashlight and light it in the area of the proximity and light sensor. Instantly the screen went on and displayed everything, but if I move the flashlight away again, it goes off. and that happens as long as you make the call. If you end the call the screen stays off like it's everytime the case. If I move the flashlight now in front of the sensor area, the screen goes on and it stays on.
EDIT: It's not everytime working.
The following things I did, but brought no solution:
1. Flashing everything new
I did a task29, flashed some different radio roms, different HSPL's and also many different ROM's. Windows Mobile and ALSO Android. Nothing helps.
2. Blowing inside the case
I also read that it help if I blow inside the case near the area of the sensors. I don't know if it really helps, but it's fur sure not the reason.
3. Display protector
In my case it's not the reason, because I don't use a protector and never used one.
Questions, that I have now:
1. Proximity sensor
Everybody says the HTC HD2 has a proximity sensor, but I don't know if this is sure. Maybe the phone has only a light sensor, which works like a proximity sensor, like other newer phone's like the HTC Wildfire.
2. Production error
Could it be a failure from the factory? Encoutered anybody this problem only after some time? Or maybe anyone who can say that the problem was solved by itself?
Please don't answer like: use the forum search or something like this.
I searched a lot and not only in this forum.
Best regards Gerhard Silvio
Further test confirmed, what I said. The problem must be the light sensor. After a call and the phone don't turn on, light a fire in front of the phone or light with a flashlight to the sensors. it goes on immediately!
Strange..
EDIT:
I made a video to show what I mean. Excuse me for my bad english ^.^
Now you developers outside are asked how to fix it...
Open the phone and clean? Or maybe it's not so easy?
Best regards
There is no possibility to fix this issue, because the light sensor is not programmable (as we know now, the HD2 has no proximity sensor). The sensor decides to turn the screen off when it gets dark, so i took some black nail polish and put it under the glass surface in front of the sensor. The screen now don't turn off and automatic light won't work also, but i can compensate these problems better than the call issue.
And without doing this, you will never be able to use WP7 right, because you can only end a call if you push the on-screen button, and this button won't appear. So you must wait until the other side ends the call, and if this don't happen you can't use your phone again without remove and reinserting the battery ^^
I hope I could help you by providing these informations.
Thread can be closed, there's nothing more to say.
The problem is isnst a problem 'cos you burned the proximity sensor with that heat.
iamrv said:
The problem is isnst a problem 'cos you burned the proximity sensor with that heat.
Click to expand...
Click to collapse
What are you talking?
That has nothing to do with any heat (if you mean the lighter). It was 3cm or more, can't follow your answer, cause its unlogical. It also worked with a normal light or a laser or anything else.
the problem u have ( i have too) only happens in nand builds, i dont have this issue with Duttys_2.5_5.21916.5.0.95_3.14_HD2_ML_Family_ROM_(V12)_WWE installed.. the phone act normal completely.
so i have to say this to me is a nand build issue, why others on htc hd2 arent not having this problem is what confuses me
In my case, it was not depending of what build or os i use. It happened in wm6.5, sd android, nand android and also in wp7. I caused by the hardware, and if i can't repair it, i have to destroy or deactivate it. with software you can't deactivate the sensor so i coloured the sensor black, that he won't notice anything anymore and the problem is solved. i have no problem with the screen active, while calling.
Firstly, the HD2 DOES have a proximity sensor and it works flawlessly in WM6.5. I know this was 100% fact for me, as I was very impressed at how well it worked. There are 2 sensors, clearly visible, next to the earpiece. One is a light sensor, as you know, and the other is a proximity sensor. This is not an opinion - it's a fact. I just wanted that to be very clear.
Also, I don't have this problem in Android, either SD builds (I don't use any more), or NAND builds (my daily driver). I will admit that there is a delay of a couple of seconds when I take the phone away from my ear, before the screen comes on, but I know that's just down to the fact that I'm using ported software.
You say that in your case this failed to work in both WM6.5 and Android. You've got a dodgy proximity sensor then. This is clearly a hardware failure.
The HD2 DOES have a proximity sensor but this fault does occur on some android builds
If it occurs for you everywhere, then u simply have a faulty proximity sensor, and i know this because i too have used wm.5, andoird nand and sd, and WP7
and the proximity sensor works fine on all but some (older) android builds
if the HD2 didn't have a proximity sensor there wouldn't be a second hole, next to the light sensor.
johncmolyneux said:
Firstly, the HD2 DOES have a proximity sensor and it works flawlessly in WM6.5. I know this was 100% fact for me, as I was very impressed at how well it worked. There are 2 sensors, clearly visible, next to the earpiece. One is a light sensor, as you know, and the other is a proximity sensor. This is not an opinion - it's a fact. I just wanted that to be very clear.
Also, I don't have this problem in Android, either SD builds (I don't use any more), or NAND builds (my daily driver). I will admit that there is a delay of a couple of seconds when I take the phone away from my ear, before the screen comes on, but I know that's just down to the fact that I'm using ported software.
You say that in your case this failed to work in both WM6.5 and Android. You've got a dodgy proximity sensor then. This is clearly a hardware failure.
Click to expand...
Click to collapse
Thanks for your opinion, but my proximity sensor works flawlessly in windows mobile 6.5.3 but under superram darkstone build I suffer rge same problem. Most of the times can be fixed touching the write arrow button...
Maybe can help...
Sent from my HTC Desire using XDA App
My HD2 tmobile also has this proximity sensor problem. I use my finger to cover the sensors (light, proximity) during the call. The screen will off. But the screen cannot back to on when I moved out the sensor cover. I tried to use the torch to shine the sensor but no response.
If HD2 connected to power supply or PC USB for battery charging. The screen can switch on. I think this charging method for sensor disabled.
you already thought about a Hardware Problem and let HTC fix it?
yogya said:
Thanks for your opinion, but my proximity sensor works flawlessly in windows mobile 6.5.3 but under superram darkstone build I suffer rge same problem. Most of the times can be fixed touching the write arrow button...
Click to expand...
Click to collapse
Thanks, but that's clearly just an issue with the Android build you're using. Try another one and see if it's better.
I tested my HD2 again. I restored WM6.5 to my HD2 tmobile. The proximity sensor was no problem. the screen can turn off when my face close to screen and my face is far to screen, the screen will turn on.
I also tested the lighting sensor. I put my HD2 under the strong sunshine, screen will light strongly.
If I re-installed the android rom NAND. This problem will be issue. I tried more than two ROMs. The result is same.
Sorry, maybe my english is not good.
johncmolyneux said:
Thanks, but that's clearly just an issue with the Android build you're using. Try another one and see if it's better.
Click to expand...
Click to collapse
Thanks for the info...
If I change my build I el let it know here... For the moment, I can survive with this...
Sent from my HTC Desire using XDA App
jackykwan said:
I tested my HD2 again. I restored WM6.5 to my HD2 tmobile. The proximity sensor was no problem. the screen can turn off when my face close to screen and my face is far to screen, the screen will turn on.
I also tested the lighting sensor. I put my HD2 under the strong sunshine, screen will light strongly.
If I re-installed the android rom NAND. This problem will be issue. I tried more than two ROMs. The result is same.
Sorry, maybe my english is not good.
Click to expand...
Click to collapse
then it can only be an issue with the nand builds unless the nand builds have use of an additional sensor not used in wm6.5..
Hi.
Readed all this thread. Also one other same situation, described on HD2 Android Q&A and General forum on thread "[Q] screen goes off if I make a phone call".
I can confirm that this issue goes active with Android NAND builds. Not matter, is it Froyo or Gingerbread. I tested lot different roms. Best results i got on PureGingerbread gpc_hd2_gingerbread_v1.3 and with SetCPU on conservative. On somewhere proposed smartass didnt work.
Actually i dont remember this same bug, when i runned Android at SD.
Now i placed back stock win rom and all works perfect. This shows that my hardware works correctly. But i dont like winmo (also winphone 7 is unripe and i dont like it too). I want use Android and not at SD. Must i go to change phone and loose todays best smartphone (my opinion)?
I dont know fundamental of Android and dont have time to learn it too (so many works and other things todo). But maybe some rom or kernel chief can handle this and overlook things that operate with Proximity or Light sensor.
I dont have so many posts yet that post this to my preferred rom thread. I dont want go spam over forum to get post count bigger. this was reason why i posted my opinions here.
Finally sorry about my poor enlish.
I heard so much meanings where the reason could be and i have to end up my whole life without solving this problem.
in my case it's not os-dependent.
i never needed my screen to turn off while talking, the hd2 is very big and with android there's nearly no chance to push any button and with wp7 the same, so why i should be angry about this problem. my sensor won't recognize anything anymore, that's enough for me ^^
http://forum.xda-developers.com/showthread.php?t=951858
This sounds very interesting. The proximity sensor of the Desire HD of most people was not correctly calibrated so it won't work good and they got the same issues like we do with our beloved HD2. Check out the thread and the app. I'm not sure if it works, but you can give it a try. I'm not able to use it, because i deactivated my sensor in a hardware-way xD !
Silberpfeil3110 said:
http://forum.xda-developers.com/showthread.php?t=951858
This sounds very interesting. The proximity sensor of the Desire HD of most people was not correctly calibrated so it won't work good and they got the same issues like we do with our beloved HD2. Check out the thread and the app. I'm not sure if it works, but you can give it a try. I'm not able to use it, because i deactivated my sensor in a hardware-way xD !
Click to expand...
Click to collapse
Hello
I have this problem since 2 days
And i test it
now my phone not turn off during a call. screen stay on.
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?
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!
I am having issues with my Z3 proximity sensor being activated when it's not supposed to.. e.g. when I receive a call the screen will just go black and I cannot answer the call or even see who is calling me, same when I dial out, I just have to hope the other person hangs up or I have to soft reset my phone with power + vol up until it turns off then restart.
I have tried all the silly apps and none of them work, or they are just bloated with ads etc. and besides I would rather not have to rely on an app for this. I have read in a few places that the proximity sensor is at /dev/cm3602 but only on certain devices, and possibly only on ICS/JB.
Surely there must be a way to disable the proximity sensor via root shell?
I have tried so many things, at first I thought it was a firmware issue, but after trying various ROMs I figured it's not. What confuses me is that the proximity sensor and light sensor are the same sensor, and the light part works fine but the proximity doesn't.
Is there anyone out there who knows anything about this? Has done this before? Or is willing to give me any idea on how to get going in the right direction?
Cheers in advance..
Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?
In the engineering menu * # * # 6484 # * # * we find 27 - Proximity sensor
When approaching the palm to the front camera should show "0".
I always showed "5", did not want to be calibrated.
I pressed Error, went out and went to the engineering menu, a miracle happened - it was calibrated.
stanley56 said:
In the engineering menu * # * # 6484 # * # * we find 27 - Proximity sensor
When approaching the palm to the front camera should show "0".
I always showed "5", did not want to be calibrated.
I pressed Error, went out and went to the engineering menu, a miracle happened - it was calibrated.
Click to expand...
Click to collapse
No, nothing happened. As usuall, screen is always on.
Yes, proximity sensor in settings was on and I have rebooted the phone.
I really don't know what to do. Is it because of bug in Global Rom or is it hardware malfunction?
Fortis10 said:
No, nothing happened. As usuall, screen is always on.
Yes, proximity sensor in settings was on and I have rebooted the phone.
I really don't know what to do. Is it because of bug in Global Rom or is it hardware malfunction?
Click to expand...
Click to collapse
Hold your phone with your left hand. The placement sensor gets blocked by your right ear when you make calls using your right hand. Give it a go and get back to us.
DelphinusMinor said:
Hold your phone with your left hand. The placement sensor gets blocked by your right ear when you make calls using your right hand. Give it a go and get back to us.
Click to expand...
Click to collapse
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...
Fortis10 said:
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...
Click to expand...
Click to collapse
I can't help there but left/right holding is an issue I guess with this phone. Or maybe it's the Pro. I forget offhand.
Fortis10 said:
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...
Click to expand...
Click to collapse
Obviously the proximity sensor is at fault. Enter the menu using the code mentioned above, then press the menu/options button and select Calibrate proximity sensor. Once you're there, hold your hand over the proximity sensor (to the right of the front camera) and tap the Calibrate button. That's one thing that could fix it.
Failing that, go to incoming call settings and turn off the proximity sensor (turn off screen in call). Restart your phone, go to the same toggle and turn it on.
If neither of these works, you likely have a faulty piece of hardware. Your last option is to have the phone repaired or try a different kernel/ROM.
Fortis10 said:
Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?
Click to expand...
Click to collapse
Hi , are you on miui global stock rom? Or custom rom?
I just had the same issue , but in my case , I recently opened the bootloader and installed xiaomi.eu rom, everything was working fine. I got notification of update ,I downloaded the update , but flash it thru TWRP , and then with the new update, the proximity was not working at all. Flash again the new rom, but wiping everything , and now works.
jonathan_jon said:
Hi , are you on miui global stock rom? Or custom rom?
I just had the same issue , but in my case , I recently opened the bootloader and installed xiaomi.eu rom, everything was working fine. I got notification of update ,I downloaded the update , but flash it thru TWRP , and then with the new update, the proximity was not working at all. Flash again the new rom, but wiping everything , and now works.
Click to expand...
Click to collapse
Is the EU rom that better?
I mean is there any plane to compare the known issues between the global and EU ?
I'm using the miui global 10.3.3.0 PFGEUXM and definitely have some "issues" with the proximity sensor.
I'm still trying to tie down the exact nature of the problem:
With a quick test, or doing calibration, it seems to work exactly as I would expect; the screen switches off as you approach closer than about 2 inches.
However during a long call I notice the display start to flash "on" frequently in the corner of my eye and soft keys can get inadvertently pressed.
It kinda feels like it gets worse during the call, is it time or perhaps the phone warming up in my hand? Not sure.
hi @All!
is there still no permanent solution for fixing proximity bug?
its really annoying and making me crazy....
even after making it working again using quicktune app - doing one call it is broken again
fasty said:
I'm using the miui global 10.3.3.0 PFGEUXM and definitely have some "issues" with the proximity sensor.
I'm still trying to tie down the exact nature of the problem:
With a quick test, or doing calibration, it seems to work exactly as I would expect; the screen switches off as you approach closer than about 2 inches.
However during a long call I notice the display start to flash "on" frequently in the corner of my eye and soft keys can get inadvertently pressed.
It kinda feels like it gets worse during the call, is it time or perhaps the phone warming up in my hand? Not sure.
Click to expand...
Click to collapse
Exactly what i've experienced.
Super annoying when you accidentally hang up during a call.
It happend countless times so far.
I'm on eu beta btw.
Wish there would be a solution.. . But afaik proximity is even more bugged in non miui custom roms.
I had this problem to. my proximity sensor what not responding at all. I thought it was defective because the calibration was not working to.
Then i went to the system update settings, downloaded the latest package and flashed it. After reflashing it started working with no problem at all.
Factory reset did the trick for me. Working normally now.
Install Quick Tuneup. Then do Sensor Celebration & Restart your device twice.
Two solutions
Fortis10 said:
Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?
Click to expand...
Click to collapse
It turns out that the problem is because MIUI does not activate the proximity sensor when the smartphone is turning on.
To force MIUI to ALWAYS activate the sensor at each start, we can do two things:
1- Always have "Automatic brightness" activated
2- Activate the "Pocket mode" (the best choice)
After applying one of these situations, it is necessary to restart the phone.
Only by activating the pocket mode it is no longer necessary to have automatic brightness activated all the time.
In the video I show how to activate the "pocket mode"
w w w . youtube.com/watch?v=2dfrqmH02O8
I published this solution in a forum in my country (Colombia).
w w w . laneros.com/temas/soluci%C3%B3n-sensor-de-proximidad-xiaomi.239997
I don't speak English, I had to use the google translator, sorry for any translation error.
2- Activate the "Pocket mode" (the best choice)
After applying one of these situations said:
KMILO_PARRA is a KING .........................
above is proof to SOLVE the Proximity Sensor no reaction in my Redmi Note 7.
I was having lots of TASKER Profile depending on whether or not Proximity Sensor is covered.
I found all those Profiles no more function due to the issue after I believe OTA to Global rom the latest ( August-2019 )
Thanks again to KMILO_PARRA
Click to expand...
Click to collapse
Actually, the proximity sensor for Redmi Note 7 isn't in the "usual" top-center position, it's a little bit on the top-right edge (if you watch the phone "against the light" you can actually see a small dot on that side).
If you're calling\responding try to put your ear at that angle, you'll never have those problem anymore.
I know it seems crazy, and of course the first times could be "unusual" to put the ear there, but it actually worked out flawlessly for me.
Mr
Quaresma_7 said:
Obviously the proximity sensor is at fault. Enter the menu using the code mentioned above, then press the menu/options button and select Calibrate proximity sensor. Once you're there, hold your hand over the proximity sensor (to the right of the front camera) and tap the Calibrate button. That's one thing that could fix it.
Failing that, go to incoming call settings and turn off the proximity sensor (turn off screen in call). Restart your phone, go to the same toggle and turn it on.
If neither of these works, you likely have a faulty piece of hardware. Your last option is to have the phone repaired or try a different kernel/ROM.
Click to expand...
Click to collapse
Thanks.....
It works for me
Hi guys,
I have made a little workaround, using the suggestion of @KMILO_PARRA user. (pocket)
https://taskerprofilecenter.blogspot.com/2019/09/project-proximity-sensor-workaround-for.html
This is mainly for Tasker users, but I have generated an APK to be installed too. So any user can use it. But what is needed, by now, is root, as it needs to write to Settings table.
Please, report me back if it does the job or not.
Note1: For those users that don't know how Tasker works, just install the app, and give it root permissions, and allow Write System Settings permission (Android option). I recommend you to not set it as an app to be killed from the OS using the battery optimization, as it could be killed. It acts on every shutdown and device boot.
Note2: It will generate two permanent notifications: Place holder, and the one that is the mini-Tasker code monitor (required). Just, disable the Place holder one, as described in the same notification (click on it), and disable notifications completely for the installed app to get rid of the last one.
---------- Post added at 12:44 AM ---------- Previous post was at 12:31 AM ----------
What it does exactly?
Well, as I explained on my web, it just changes the value (0/1) from the 'enable_screen_on_proximity_sensor' Global Settings table, that makes the pocket option to be toggleable in an automated way.
So, be sure not to use that option as a daily one, as the project/app uses it to allow the sensor be available at startup. And do not forget that you will need root too! Sorry.
What to download if I don't know what Tasker is?
You will only have to download the APK from the 'Kid App (APK)' link, provided under the 'DOWNLOAD' section. Nothing else.
If you know Tasker, you will know what to do.
Does it work really?
I'm currently testing this workaround, but as I could see, at least on my device (lavender too), seems to be working as expected. But needs to be tested a little more.
So, if it does not what it's intented for, please, report it me back.
After installing the app, giving root permissions, and allow it to modify system settings, reboot the device to take it effect.