Hi.
Somebody please help me fix this as I'm not able make calls or receive calls. The phone is hung after I slide until the call is disconnected. I have 2 phones with this problem. Tried miui, omni rom as well & the problem still persists.
tweetsoud said:
Hi.
Somebody please help me fix this as I'm not able make calls or receive calls. The phone is hung after I slide until the call is disconnected. I have 2 phones with this problem. Tried miui, omni rom as well & the problem still persists.
Click to expand...
Click to collapse
if it goes black after a call or after disconnection then try removing the scratch guard it might be blocking the proximity sensor coz after making a call when you get your cell to ears the screen goes of and maybe the proximity sensor is blocked coz of screen guard so its not waking back so try removing the screen guard
krishna8691 said:
if it goes black after a call or after disconnection then try removing the scratch guard it might be blocking the proximity sensor coz after making a call when you get your cell to ears the screen goes of and maybe the proximity sensor is blocked coz of screen guard so its not waking back so try removing the screen guard
Click to expand...
Click to collapse
This is not about proximity sensor..
tweetsoud said:
This is not about proximity sensor..
Click to expand...
Click to collapse
ohh i had similar problems in my moto e, g4 plus and asus because of tempered glass but then i moved to normal screen guard and it solved the problem in all three devices maybe its something else in your case.
someone more experienced might help you out with this
Related
Does anyone know if there is a way to adjust the proximity sensor.
It's proving a problem for my wife who uses the phone. When she's on a call the phone is intermittently sensing if she's holding it to her ear.
Hence being a capactive screen, when her cheek brushes the screen during a call the other end either hears DTMF or gets cut off by it touching the end call.
I called her yesterday and kept getting random DTMF digits sent to me, then I got sut off.
I was watching her use the phone and the screen was de-activiting (correctly going blank) for part of the call then coming back on, this would happen several times during one call.
Is this a hardware issue or software bug. Has anyone else suffered this problem?
Also happened to me a few times touching end call wih my cheek, really annoying.
Anyone else having the same problem with the proximity sensor intermittently not working during a call?
I had that problem on the old 1.43 ROM but it was fixed when I upgrade to 1.48.
I have this problem and I constantly have to call back and say sorry to my customers and blame it on the phone...
I have reported several errors to HTC and all i get back is "Take it to the retailer and get it changed, it must be a hw error", annoying as hell
1.48 not yet official in sweden.
TouchLockPro
You can try TouchLockPro, it has an InCallTweak, using the GSensor. Searching for accessing programmatically the Proximity Sensor though, for more options (e.g unlock by Proximity Sensor). It works on HTC Leo, people confirmed.
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
philtrick123 said:
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
Click to expand...
Click to collapse
Indeed, TouchLockPro detects itself the available sensors and uses the available ones. Of course you can configure detailed things (via pressing the BattClock), but the defaults are already the sensible ones
Thanks again ZuinigeRijder.
Just been doing some more testing and occasionally the screen flashes on for a brief moment during a call. Could it be the proximity sensor trying to turn on the screen? Or is it the G sensor not being very accurate?
In the application is there a way for me to adjust the G-Sensor angles that activate the screen off? i.e. 45+ Degrees activate ??
Or are there any other adjustments I could make during testing??
I found one more problem... I checked it several times....
If u make a call using portrait orientation of phone app (Rotated using BSB Tweak). Proximity sensor doesnt work at all.... i made a while lyin on the bed and no matter wat i tried it wasnt turning off the screen....
Then i kept it in portrait position for a few seconds den proximity started working again...
Is there anyone who can confirm me with this problem.... or is this issue only with my HD2
Hi guys,
I dont know if this has already been discussed or if anybody has had the same problem,
The proximity sensor that is supposed to turn off the display while in call only works when i make a call. If i am receiving a call then the display stays on and i end up ending the call accidently will my cheek.
I was wondering if there is a fix or app to sort this out. I am looking for something that purely sorts this problem out and dont really want any other features etc.
Many thanks,
Loz
I cannot replicate this problem. The sensor on my HD2 works perfectly on incoming calls.
no offences but i am sort of hoping others have this problem so im not the only one lol strength in numbers and all that...
can anyone relate to the problem i have, i have searched the settings time amd time again looking for proximity settings to see if it has been disable or something
please help!
hi guys,
i am still having problems with the proximity sensor when i receive a call, can anyone help????????
thanks
There has been a few posts like this in the past, but AFAIK no-one has posted a solution or reason for it happening. I've never had any problems with the proximity sensor on my handset so can't help any either, but I would guess it has something to do with using a screen-protector or possibly the screen being full of smudges right around the sensor.
thanks for the reply
i dont think it is the screen protector im using because it works whenever i make a call, its just when receiving a call it doesnt turn off the display!
does anyone no if there is a fix or reg edit i could do to get it working again?????
bluearmyb said:
thanks for the reply
i dont think it is the screen protector im using because it works whenever i make a call, its just when receiving a call it doesnt turn off the display!
does anyone no if there is a fix or reg edit i could do to get it working again?????
Click to expand...
Click to collapse
Hello,
I have the same bug and I post it yesterday, the screen off when I make a call and stay on when I am getting a call.
My Rom is 1.48.405 from UK, and I have screen protection from HTC with small hole on the sensors.
also when I making a call the screen off but need to turn on when you take the phone far from your head, sometimes it is heppens but sometimes not.
kochavy
When I bought the phone it was 1.43.405 and I upgraded it to 1.48.405.
maybe this is the problem!!
kochavy
just a innocent fact.
I had noticed that when starting to make a phone call the prox. sensor turns off the display but when the connection is made (the fuzzy noise and the first beep) the displays turns on. To reactivate the prox. sens i have to move the phone from my ear and then approach it again (please forgive my bad english) and the display turn off as designed. This issue can lead to the idea that the sensor is broken or malfunction.
I hope it helped
kochavy said:
Hello,
I have the same bug and I post it yesterday, the screen off when I make a call and stay on when I am getting a call.
My Rom is 1.48.405 from UK, and I have screen protection from HTC with small hole on the sensors.
also when I making a call the screen off but need to turn on when you take the phone far from your head, sometimes it is heppens but sometimes not.
kochavy
Click to expand...
Click to collapse
yeah it sounds the exact same problem. i have the exact same rom (1.48.405 from uk) and screen protector from htc. startin to become a big problem coz i keep ending calls accidently
hopefully can fine a solution
bluearmyb said:
yeah it sounds the exact same problem. i have the exact same rom (1.48.405 from uk) and screen protector from htc. startin to become a big problem coz i keep ending calls accidently
hopefully can fine a solution
Click to expand...
Click to collapse
Where did you buy it? mine from Israel.
vi_rus said:
just a innocent fact.
I had noticed that when starting to make a phone call the prox. sensor turns off the display but when the connection is made (the fuzzy noise and the first beep) the displays turns on. To reactivate the prox. sens i have to move the phone from my ear and then approach it again (please forgive my bad english) and the display turn off as designed. This issue can lead to the idea that the sensor is broken or malfunction.
I hope it helped
Click to expand...
Click to collapse
thanks for the info.
when i make a call the screen turns off straight the way before i have even put the phone to my ear, and to turn the display on i have to press a hard key
i am startin to think it is a proxomity sensor malfunction so hoping for some kind of fix
kochavy said:
Where did you buy it? mine from Israel.
Click to expand...
Click to collapse
i got mind from the uk, did you have the problem before you upgraded rom?
How do you turn it off? what is hard key?
what are you doing when you get a call?
kochavy
bluearmyb said:
i got mind from the uk, did you have the problem before you upgraded rom?
Click to expand...
Click to collapse
I dont know I just bought it and upgrade the same day.
Did you send mail to HTC?, I did but thay never send me mail back
kochavy said:
How do you turn it off? what is hard key?
what are you doing when you get a call?
kochavy
Click to expand...
Click to collapse
i dont no it does it automatically but not using the prox sensor, i usually press the back key to turn it back on but the it stays on
there is nothin i can do when i get a call the display always stays on
HTC havent got back to me so i was hoing some one on here would no wat to do!
may someone can help us out?
I will wait for Rom 1.66
yeah me too hopefully that will resolve our problem
ill be checking htc website constantly until the uk rom is released
After two weeks testing I found out that the original screen protector with the two holes for the sensor makes the problems!!!
thake the screen protector out or cut it and the proximity sensor will work perfect.
Kochavy
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........
Does anyone out there have any idea whats happening and what the fix may be?
Thanks for any help
Remove your screen protector.
Blacksmith5 said:
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........ Does anyone out there have any idea whats happening and what the fix may be? Thanks for any help
Click to expand...
Click to collapse
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Proximity sensor turns off screen when you put it to your ear to avoid your skin touching the "End call" button or something else
kbakalar said:
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Click to expand...
Click to collapse
Thanks for that info I had not thought about that... That may be cause of my problem.... I will have to figure out a solution
Thanks again
Didgeridoohan said:
Remove your screen protector.
Click to expand...
Click to collapse
I am not using a a "screen protector" But thanks for the input
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Didgeridoohan said:
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Click to expand...
Click to collapse
I did as you suggested and the results say 2" uncovered 0 when covered
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Didgeridoohan said:
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Click to expand...
Click to collapse
I'll keep looking for a solution.......... It's a pain especially if if I have to respond to a VM and hit a Number.......
Thanks again
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Man of La Mancha said:
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Click to expand...
Click to collapse
Yes I resetthings so I only have to hit the power button to end a call Thanks for all the help
Install Google Fit.
...so who's got some of those "defective" screen protectors without sensor cut outs? Will be them from you for cheap!
None of the vendors have it in stock?
Well, I was able to see the screen for 5 calls. Now it's back to black as soon as call registers.
Really weird. Think Fit does somehow effect proximity sensor. Many 5 and 6 users (who only have black screen in call after upgrade to 6.0) are reporting that disabling Google Fit fixed their problems.
i'm so confused, so is it to install google fit or not?
Can't hurt to try. When I first installed it, my phone was working correctly. But that only lasted for 5 calls.
Not working for me, didn't try the phone call, the ambient display still disabled. So this is only a partial fix, not really useful.
Where is the proximity sensor on the the N6P?
perveeus said:
Where is the proximity sensor on the the N6P?
Click to expand...
Click to collapse
Right where that cut out on my screen protector is on the lower right hand side of the top speaker.
Thank you buddy! Just curious if you've run into the screen going black during calls? If you is it attributable to the screen protector?
perveeus said:
Thank you buddy! Just curious if you've run into the screen going black during calls? If you is it attributable to the screen protector?
Click to expand...
Click to collapse
I haven't had any problems with calls going black at all. My screen protector doesn't block the sensor so it works just fine.
Namuh said:
I haven't had any problems with calls going black at all. My screen protector doesn't block the sensor so it works just fine.
Click to expand...
Click to collapse
Appreciate the feedback. Just seems odd that it's affecting the Nexus 6 crew also.
hey community, i am having problem with proximity sensor. Whenever i receive a call on whatsapp or even regular call, the screen goes black and i have to move my hand on the proximity sensor to get it working again then it goes back to being black. It only goes black during he calls. i have tried reflashing the ROM but the issue is still there. Will i need o pull log? any help would be appreciated.
P.S. oh i have Moto g4 plus running lineage OS unofficial latest update. i didnt have this issue before!
sublimeace said:
hey community, i am having problem with proximity sensor. Whenever i receive a call on whatsapp or even regular call, the screen goes black and i have to move my hand on the proximity sensor to get it working again then it goes back to being black. It only goes black during he calls. i have tried reflashing the ROM but the issue is still there. Will i need o pull log? any help would be appreciated.
P.S. oh i have Moto g4 plus running lineage OS unofficial latest update. i didnt have this issue before!
Click to expand...
Click to collapse
That's what the proximity sensor is for - to switch off the screen based on interactions. It goes off so that your face doesn't accidentally touch any button and cause problems. It's normal behaviour.
Yes bro ik that but the screen should go black when the sensor is covered with the face or hand. But it goes black as soon as my phone starts ringing. I need to cover the sensor to bring the screen back up so that I could answer the call. Similarly, as soon as I start listening to a voice note received on WhatsApp the screen goes black and the volume goes low I don't know what to do I have tried flashing stock ROM then latest lineage OS unofficial latest build, any help would be appreciated
sublimeace said:
Yes bro ik that but the screen should go black when the sensor is covered with the face or hand. But it goes black as soon as my phone starts ringing. I need to cover the sensor to bring the screen back up so that I could answer the call. Similarly, as soon as I start listening to a voice note received on WhatsApp the screen goes black and the volume goes low I don't know what to do I have tried flashing stock ROM then latest lineage OS unofficial latest build, any help would be appreciated
Click to expand...
Click to collapse
Well, a complete wipe (Dalvik,Cache,System, Data) should ideally fix such things. But if doesn't, I think your sensor is damaged. Just take it to a service centre then
1chrome said:
Well, a complete wipe (Dalvik,Cache,System, Data) should ideally fix such things. But if doesn't, I think your sensor is damaged. Just take it to a service centre then
Click to expand...
Click to collapse
Sigh, I thought so man, I was hoping it was not the case. Turning the sensor off will fix the issue but no xposed for N yet. I'll keep using this one seeing it's fine usually lol. Thanks for your help mate.