Database Users

No Wake-up after phone call

Still tested different NAND-Android Roms on my HD2 but got still a problem. If i make a phone call and the screen turns black while calling i press the endkey to end the phone call. But instead of turning on the device, the screen stays black and i need to pull the battery and restart the phone.
If i make a phone call and use the free speaking funktion, while the screen don't turn off, i got no problem when ending the phone call.
I don't know what the problem could be, but it seems, that the thing has to do with the sensor who turns the screen on and off. But i don't know if this is the problem and/or know how to fix this problem. Like i said, i tested different Android Roms formated the SD-Card, deleted cache and all the stuff, but nothing fixed this problem. :-(

28 Views and no one with this problem? :-(

There are 2 other threads discussing this issue already. Here is one.
http://forum.xda-developers.com/showthread.php?t=946012
Issue lies with the light/proximity sensor. Could be defective hardware. Could be incorrect sensor drivers. Could be dirty sensors. I have yet to take mine apart to check for dirt on sensors. Blowing into the led/earpiece opening seemed to help. I notice if it doesn't come back on I can hold a very bright light (ex: cigarette lighter) about an inch away and the screen comes on as long as the lighter is lit. Sometimes it stays on.

thanks for your answer. seems to be more things to test and maybe solve this problem. Thanks!

THANK YOU Agoattamer!
Your link helped me to solve the problem! I just cutted a little piece of my screen protector, where the proximity sensor is, and got no more freezes after the phone calls! The screen protector still got two holes for the light and proximity sensor, but this seemed not to be big enough. Anyway, thank you a lot for your post!

wake up problem
Palerider-de said:
Still tested different NAND-Android Roms on my HD2 but got still a problem. If i make a phone call and the screen turns black while calling i press the endkey to end the phone call. But instead of turning on the device, the screen stays black and i need to pull the battery and restart the phone.
If i make a phone call and use the free speaking funktion, while the screen don't turn off, i got no problem when ending the phone call.
I don't know what the problem could be, but it seems, that the thing has to do with the sensor who turns the screen on and off. But i don't know if this is the problem and/or know how to fix this problem. Like i said, i tested different Android Roms formated the SD-Card, deleted cache and all the stuff, but nothing fixed this problem. :-(
Click to expand...
Click to collapse
I also tried a a lot of different NAND ROM and I had also this problem and I can't use Android efficiently. Now I am using hyperdroid ROM ( first GBX now CM). With this ROM and sanity app (from market, with correct settings you can find with trying) I almost solve this problem. ( probability of 95 % I don't get this error)

hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^

anthonydo1991 said:
hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^
Click to expand...
Click to collapse
Does any other one tried this solution ???

[Q] Proximity sensor funkiness?

This has been happening pre and post Nodo on my focus. If i'm on a phone call for at least a few minutes, then pull the phone away from my head, the phone's display should become active, but it isn't.
Anyone else having this issue or is it time to exchange the phone?

I have the same issue also it seems like I have to press the power button a couple of times to get it back.
Sent from my SGH-i917 using XDA Windows Phone 7 App

I'm also having this issue. Anyone remember if ther were having it pre-Nodo? Just wondering if the update changed something.
Regardless, it's a bit of a PITA.

I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.

ArcWhistler said:
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
Click to expand...
Click to collapse
How did you do that?

Yeah, ditto that - how do recalibrate the sensor?

Samsung Diagnostic App.
http://forum.xda-developers.com/showthread.php?t=839154
I was pecking around the screens months ago, and there was one bank of tests (multi-touch, red, green, blue, white, battery, etc, etc) that allowed setting and viewing the proximity sensor.
I remember playing with moving my hand closer, and further and watching it change from sensed to clear.
Sorry, can't remember which codes now.

I used the Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
LCD Test - *#0*#

Ok, mine says No Detection. Is there anyway to set the value?

One other thing to note, about the samsung focus specific update regarding disabling the touch sensitive buttons while in a program, that also isn't working for me either. Not sure if they are related, but thought I'd throw it out there.
And as far as calibrating goes, not sure it would help since the problem only occurs while I'm on a longer phone call. On short ones the proximity sensor works just fine.

If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.

ArcWhistler said:
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
Click to expand...
Click to collapse
Mine says No Dectection. It has Prox Sensor: XXX I've taken my entire hand and covered my phone. NOTHING. When I push SET, It says ProxThreshold :0. Is there anyway to set it manually?

samsung focus post nodo
I believe the prox sensor issue is happening post nodo, I have never had this problem prior to the update... I have been able to fix it temporarily by pulling the battery and starting it up... don't know how long the fix works... got to do some testing... I am wondering if its a power thing as the screen wouldnt work when you plugged it in to power and had on a soft surface....

Still nothing. I didn't want to hard reset since I have Chevron installed. For some reason I did four updates on my phone and don't have a single backup. If I hard reset I'm S.O.L. with Twin Blades and other homebrew apps

What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?

BooR4dley said:
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
Click to expand...
Click to collapse
It has a big red box. It says No Detection. Prox Sensor:XXX Do I press Set or Reg?

another thing is wrong
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?

rockclimbaudiextreme said:
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
Click to expand...
Click to collapse
same problem here. seems like those two sensors are burned

Proximity sensor delay after a call

Hi guys just wondering if you noticed this strange behaviour.
I noticed a quite frustrating delay after a call when i take the phone away from my ear, it takes 2-3 sec for the screen to turn back on.
Has anybody experienced the same?
Do you know if there is a solution for this?
Sent from my GT-I9100 using XDA App

yes, think its normal. looks like the same delay when pushing power button for screen on.
sent from my SGSII via T*patalk

Thank you.
That seems strange as it is something really basic that you expect to work in a phone of this price range. Moreover it's something you come across quite often.
Do you know if the latest firmware improves this?
Sent from my GT-I9100 using XDA App

i am on ke7, so no.
sent from my SGSII via T*patalk

Cuz80 said:
Thank you.
That seems strange as it is something really basic that you expect to work in a phone of this price range. Moreover it's something you come across quite often.
Do you know if the latest firmware improves this?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You can just turn off the sensor in the call app, if you want your screen to be available just after a call.. I don't see the problem.. but my delay is also just around a second or so.

mljjlm said:
You can just turn off the sensor in the call app, if you want your screen to be available just after a call.. I don't see the problem.. but my delay is also just around a second or so.
Click to expand...
Click to collapse
But if I do that i will drain battery unnecessarily. I don't know you guys but I find it really annoying having to wait 2sec after a call for the screen to wake up. I want to be able to hang up immediately i think I'm not asking something ridiculous.
Sent from my GT-I9100 using XDA App

you can also set the power button to terminate the call and you will not have to wait for the screen to turn on...

Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc

dfi2k5 said:
you can also set the power button to terminate the call and you will not have to wait for the screen to turn on...
Click to expand...
Click to collapse
How do you go about doing this? Can it be changed in the setting sor does it require a separate App?

xiga said:
How do you go about doing this? Can it be changed in the setting sor does it require a separate App?
Click to expand...
Click to collapse
Pls go to settings then call then calls answering ending and tick power key ends calls

Yes i find this very annoying too!
Especially when on a call center, press 2 (wait for screen) then press 4 (wait for screen) you get the idea
this is actually the only problem i have with the SGS2 since ke7
Sent from my GT-P1000 using XDA App

pulser_g2 said:
Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc
Click to expand...
Click to collapse
sgs 1 managed it fine though?....or am i missing something

Yeh my i8000 had no delay with the proximity censor.
But the screen delay seems to be everywhere. Turning on from sleep, time to adjust to ambient light and obviously the proximity sensor after pulling it away from your face.
Its not a major drama for me but I agree that it would be good to not have the delay.

I just noticed that when I use Skype the sensor works really well, meaning there is almost no lag.
I'm confused..
Sent from my GT-I9100 using XDA App

Yes! Very annoying.
Yep! I was commenting on this the other day. To be honest, I make and receive very few calls from my phone but when i do, I feel the rage rising inside me everytime because of the sensor delay.
It's the small things that annoy you the most.
As mentioned, you can opt to have the power button hang up the phone. It also does not turn the screen off, so you can continue working on the phone.
This is actually under accessibility settings, not call settings.
Menu -> Settings -> Accessibility -> Cancel the prompt -> Tick 'The power key ends calls'.
I also find the lag on waking up very annoying. Even once the screen has woken up, it takes a second for the touch input to be recognised so the pattern unlock only registers my last two or three inputs depending on how quickly I start swiping. I have to enter the pattern again. Very annoying.

pulser_g2 said:
Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc
Click to expand...
Click to collapse
I also have this problem, although I'd estimate it only takes about 1-1.5 seconds for the screen to come on.
I do however not think that this is a sensor problem, but rather a software problem.
Type *#0*# in the dialer, and press Sensor.
The phone will now vibrate once you trigger the proximity sensor. And it seems to be very fast and responsive here.

i have the problem using Skype...when i start a call it turns automatically the screen off ! i need then to push on home button to get out of skype...very ennoying...

last time i made an order online, my bank sent me a code by phone and following the instruction, the voice asked me to push the number i hear...i simply could not !! the screen was completely off ! and i could not succefully purchase online, my order was cancelled !.....due to this problem of screen..i think it is seriously ennoying and must be fixed in an update firm or something .

Agreed, this is a very annoying and unnecessary delay. Especially coming from an iPhone, where the screen turns on instantaneously when removed from the ear.
Hoping for a fix.

im ready to pay to get this fixed

[Q] Screen goes black when I make a call

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

Unintended taps during call: how to prevent them?

Hi!
I"m not the only having the problem: during a call unintended taps takes place while screen waking up is not registered during the call. So, you see, I'm not sure a proximity sensor is the reason of the problem as far as screen is kept turned off.
I have tried to reproduce the issue by fingers, but wasn't lucky.
Have you any ideas how to eliminate the problem?
I mean not-rooted official up-to-date stock firmware use case.
And, by the way, I haven't found proximity sensor calibration in service menu for A1. Is it placed somewhere into another place?

That happens to me all the time too.

Yup, me too. While in call I sometimes unknowingly turn on the flashlight and probably look like an idiot. ?

With the rn3p I would constantly end up muted. With mi a1 the problem is much less although I've noticed that numbers are still pressed. I've learned over time to switch to keypad so when something gets touched it's not the mute and at worst the other person receives some key tones.

I also have this problem a lot. I mute myself 9/10. To bypass to problem, I just lock the screen before placing it against my ear.

Yes, a simple soutions is just when you call someone, imidiately press power button to lock the screen (no password or fingerprint requred to unlock)

dejano said:
Yes, a simple soutions is just when you call someone, imidiately press power button to lock the screen (no password or fingerprint requred to unlock)
Click to expand...
Click to collapse
That's what I've been doing. That and pushing the top part of the mobile on my face just to make sure. lol
Oh and use the Feedback app and send it to xiaomi and hope they fix it on the next update.

i had this problem too, has it been fixed in the latest of updates? its a really annoying bug.

You must be doing something wrong. This issue "must" have been in all smartphone operating systems in the world, if what you are saying is the truth.
There's no way to drop the call, or press anything while you are calling someone. The proximity sensor doesn't allow turning on the screen when it's close to an object. The gyroscope also turns off the screen when you rotate the phone vertically during a call.
But all I can say is that it's not a bug, this is how is your phone knows when you are in a call, and you put your phone to your ear, or when you use your "speaker", and so the phone knows it's supposed to used it's speaker to transfer voice through the call.
Beside my poor English, try to move your phone a bit vertically before putting it close to your ear.

same problem here, also disabling ambient display... i also tested proximity sensor with some apps and it seems ok

I have that problem too from the beginning. None of the updates came up with a solution

Same here: I mute, turn on the flashlight or even open apps sometimes with my face. And thanks for the input @SmallTarzan but i know how to operate a smartphone and did not have any similar problems for the last five years. Apart from that annoying bug it's a great phone.

Wow, i dont know of this bug since i'm using custom rom from very beginning.
Try to make a call then use your hand to cover top part of the phone, screen doesn't lock??

I am having this issue too and it is really annoying

And still nobody came up with a solution???
It's easy to understand why it happens.
Proximity activates while you're in a call, but apparently the touchscreen digitizer remains working (even though the screen is off). Touching the digitizer with your ears or cheeks activates different actions while you think your screen is locked.
I can't believe how this issue is not fixed yet! That's a shame!
Same applies for the network fluctuation issues. You need to either choose 3G or 4G to avoid loosing your data connection.
Xiaomi that's more than LAME! You need to be ashamed of yourselves.

It happens to me quite often, although not always.
It's more frequent during long calls. If the call lasts for less than a minute or so, it doesn't happen.
Proximity sensor works, and screen turns off as soon as I put it at my ear.
Keyboard is off and not responding for a while. Then, all of a sudden the phone comes alive.
In my case it's not the torch. What I activate unknowingly is the handsfree loudspeaker, which can be even more embarrassing, sometimes.
Maybe it's because I am left-handed.
In an attempt to have the proximity sensor fully covered by my face, I tried to make calls by holding the phone with my right hand, but to no avail, after some time the screen wakes up regardless of everything.

Happens to me too. Although I did notice some differences regarding the position of the phone on my ear or which side of my head I put the phone on, I started pressing the power button long ago to turn the screen off. It may not be ideal, but it takes care of it.

AlaiSalaam said:
Happens to me too. Although I did notice some differences regarding the position of the phone on my ear or which side of my head I put the phone on, I started pressing the power button long ago to turn the screen off. It may not be ideal, but it takes care of it.
Click to expand...
Click to collapse
Try this app, some users say it helps.
https://play.google.com/store/apps/details?id=ss.proximityservice

Any fixes yet?

simontol said:
Any fixes yet?
Click to expand...
Click to collapse
None, same sh**