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.
Just tips for people who might have the same issue as me.
Problem: When you are in a call, the proximity sensor turns off the screen but when you pull the phone away from your face the screen stays off.
Solution: In my case it was because there were dusts covering the proximity sensor which caused it to not be as sensitive as it should. I blew some compressed air thru the speaker (top) and everything works well.
Hope this helps, I was struggling with it for months thinking maybe a custom rom installation went haywire.
takuyaah said:
Just tips for people who might have the same issue as me.
Problem: When you are in a call, the proximity sensor turns off the screen but when you pull the phone away from your face the screen stays off.
Solution: In my case it was because there were dusts covering the proximity sensor which caused it to not be as sensitive as it should. I blew some compressed air thru the speaker (top) and everything works well.
Hope this helps, I was struggling with it for months thinking maybe a custom rom installation went haywire.
Click to expand...
Click to collapse
I have this problem too. I believe my proximity sensor is damaged. I have done a lot of reading out there and tried all solutions. This is very annoying when you want to turn on the speakerphone or use the keypad when calling #'s that require input. I tried using Pacman rom 4.2.2 and 4.4. I heard its possible to disable the proximity sensor during calls with stock Touchwiz rom, but I can't stand it. I may consider trying Goldeneye 4.4 TW Rom, but installation seems like a major hassle. I hope there is a custom rom out there that disables the proximity sensor.
When Im on cm11 or any other aosp rom my phone wakes up in pocket and sometimes even dials numbers. Everything is okay on stock based roms. Is there any fix to enable (proximity?) sensor while on cm? Without it its useless for me
Anyone? :crying:
AddictedToPlaying said:
When Im on cm11 or any other aosp rom my phone wakes up in pocket and sometimes even dials numbers. Everything is okay on stock based roms. Is there any fix to enable (proximity?) sensor while on cm? Without it its useless for me
Click to expand...
Click to collapse
yeah.... AOKP supports it but it's a device specific flag, which means it's not in our builds as we have no active maintainer..
I use Tasker for it.
ouch
Can You tell me more about using tasker to do this? I really like to set CM as my daily rom
up
AddictedToPlaying said:
ouch
Can You tell me more about using tasker to do this? I really like to set CM as my daily rom
Click to expand...
Click to collapse
Sure, profile context is proximity close, screen on. Task is System Lock. Easy.
I think it's partially working beacouse when i cover sensor while screen is on it locks immediately but i can still unlock phone when i cover sensor
AddictedToPlaying said:
I think it's partially working beacouse when i cover sensor while screen is on it locks immediately but i can still unlock phone when i cover sensor
Click to expand...
Click to collapse
Dunno, works for me. In fact it often annoys me to be covering the sensor and tap to wake and it goes immediately back asleep.
Topic is still actual
Any news in this topic?
Hi,
i've always the pb of proximity sonsor or somthing in that field when i'm installing a custom rom of android 6.0, 7.0 or 7.1 such as (OptimizedCM-14.1-20161121-BETA1-AROMA, JDCTeam_jdc_jflte-7.1-20161117-BETA, MK60.1-jfltexx-201605070057-NIGHTLY)
so when i make a call, via messenger or my sim dialer, the screen turns off and won't turn on if i push power or home buttons.
so, what's the solution of this pb i'm suffering from, from a long time...
Does the phone work properly on a stock ROM? Did you try disabling the proximity sensor or disabling the screen-off function?
audit13 said:
Does the phone work properly on a stock ROM? Did you try disabling the proximity sensor or disabling the screen-off function?
Click to expand...
Click to collapse
Yes, i'm now on 5.0.1 (stock rom) it works fine
how can i disable the proximity sonsor or the screen-off function?
This sure looks as a problem with the proximity sensor, the s4 is known for accumulating dust and grease on top of it. Open your phone with a small Phillips tool, remove it and clean it. It will work as new.
Don't think it's a hardware problem since the sensor works properly on a stock ROM.
Sorry, I no longer have an s4 and I don't remember how to disable the proximity sensor in a custom or stock ROM.
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.