now my proximity sensor is acting funny
i use direct call (when i put phone to ear, it will call the number on screen). that works fine, but once its at my face, my screen turns off. when i distance it away, it doesnt come back on, and i need to press home button to light the screen and to end call
tested the proximity sensor via *#0*# and it works fine.
help
This is normal. There's an option to disable this. I don't remember where, but exists. I think it's in the motion part.
Related
Does anyone know how to stop the screen from turning off during a call?
Move the phone away from your head?
Otherwise, why would you need it to be one when you're talking on it?
turn on the speaker, i think that disables the sensor.
This is a huge problem with 2.1.
In Android 1.5 on the Eris, you could push the TRACKBALL during a call to wake up the screen.
In 2.1, you only have two options. Pull the phone away from your head (often works, but not always, especially if you're trying to get through a phone tree, and often going back to the screen) or push the 'End' button.
If your phone's screen has been off LONG enough, the 'end' button will wake it up.
If it hasn't, the 'end' button will both wake up the screen AND END THE CALL!
It's a huge risk, and unnecessary. THE MINUTE the OTA comes out, I'm calling HTC about it, and asking them.
Oh, and for what it's worth, Screebl Lite takes care of this.
Just set up Screebl, mine is like 20-90 degrees for both portrait and landscape, and for the in-call activity, I have it not be active when up to my ear.
Screebl works GREAT to keep the screen on properly during a call.
Still calling HTC about it. That functionality should be built in better, or at least give me a way to wake up the screen when it gets stuck.
That is exactly my problem. When i go to wake it up to navigate the through menu options it hangs up alot. Very irritating! I will try Screebl.
Thanks!
you can also press any of the two volume buttons and that will wake it up without any bad effect except for a volume change.
Good tip about the volume buttons, I wasn't aware of that trick.
thanks
sometimes my phone won't wake up when I pull it away from my ear, but I usually just move my hand over the prox sensor and then back and it generally wakes up.
Keep Screen
This is a good thread. I had this problem too. After reading your posts I used the copy of KeepScreen that I already had and it worked also! May be my imagination but proximity sensor seems more responsive too.
During a call, if I keep my HTC Hero close to my ear the touchscreen becomes none responsive, meaning I can't touch stuff by mistake. If I take my phone away from my ear, I can touch the screen again.
Which is fine. This is how it's supposed to work but there's a problem:
If a call lasts longer than 1 minute (or however long you set your phone to automatically go on stand by) the screen goes dark, which is fine in most cases but sometimes you need to look through your phonebook during a call or put the person you're talking to on hold so you can answer another incoming call, etc.
Of course you can just press a key and the screen lits up again and you can do all the above mentioned, but pressing a key like the "Reject button" (which normally unlocks your screen) will not only lit up the screen but also cancel your ongoing call.
Similar to that pressing any key might also have an undesired action, which can make any during call operations frustrating.
Can the screen be configured to behave like the iPhone's (or Nokia's touchscreen phones for that matter)? Meaning when the sensor detects the phone is close to something (like your ear) the screen goes dark to save power and it becomes non responsive, but when you take it away from your ear the screen lits up and becomes responsive again?
The change isn't that dramatic, go dark instead of just becoming unresponsive (waiting 1 min to go dark) and lit up again when the phone is no longer close to something, instead of remaining dark.
radu.tanasescu said:
During a call, if I keep my HTC Hero close to my ear the touchscreen becomes none responsive, meaning I can't touch stuff by mistake. If I take my phone away from my ear, I can touch the screen again.
Which is fine. This is how it's supposed to work but there's a problem:
If a call lasts longer than 1 minute (or however long you set your phone to automatically go on stand by) the screen goes dark, which is fine in most cases but sometimes you need to look through your phonebook during a call or put the person you're talking to on hold so you can answer another incoming call, etc.
Of course you can just press a key and the screen lits up again and you can do all the above mentioned, but pressing a key like the "Reject button" (which normally unlocks your screen) will not only lit up the screen but also cancel your ongoing call.
Similar to that pressing any key might also have an undesired action, which can make any during call operations frustrating.
Can the screen be configured to behave like the iPhone's (or Nokia's touchscreen phones for that matter)? Meaning when the sensor detects the phone is close to something (like your ear) the screen goes dark to save power and it becomes non responsive, but when you take it away from your ear the screen lits up and becomes responsive again?
The change isn't that dramatic, go dark instead of just becoming unresponsive (waiting 1 min to go dark) and lit up again when the phone is no longer close to something, instead of remaining dark.
Click to expand...
Click to collapse
Take a look at the app "proximity sensor" as the hero doesn't have such a sensor. The app uses the light sensor to emulate it
pulser_g2 said:
Take a look at the app "proximity sensor" as the hero doesn't have such a sensor. The app uses the light sensor to emulate it
Click to expand...
Click to collapse
I took a look at the app online, I'll try it out.
I didn't know the Hero didn't have a proximity sensor but whatever 2.1 does it does it well, I don't accidentally press anything, the touchscreen gets disabled.
I'm upset about the fact that the screen stays on and goes to standby after a while instead of being dark when the phone is near my ear and lit up when it's not.
The phone knows when it's close to something, it deactivates touch input, I just wanted it to also turn off the screen and turn it back on when it's not close to anything.
When a call is coming, the screen will be lighted up, but will not be unlocked. If I pick up the call by pressing the answer button on the bluetooth headset, the screen will be unlocked, and the proximity sensor will start working to prevent the screen to be turned on during the call.
The problem is, after hanging up the call by bluetooth headset, the proximity sensor stop working, the screen will be lighted up instead of turning off automatically, and it will stay in the dial interface. If the phone is in my jeans' pocket, the dial button will be pressed accidentally.
I remember the iPhone will turn off the screen automatically after picking up the call by bluetooth headset. Is there any solution or advice for this annoying problem?
I'm running the stable version of CM10.1.3 on the xt910. Yes, I have a screen protector and the proximity sensor works. The phone is set to "sleep" after about 1min and I enabled "end call" by pressing the power button.
Other threads don't really address the question in relation to Cyanogenmod.
Is there a way to prevent the the screen from "sleeping" and locking me out during a phone call? The proximity sensor works very well before the phone "sleeps". In other words, prior to locking me out the screen dims and lights when the sensor is covered or not. Once the phone sleeps, the only way to end the call and access the phone is to press the power button.
I couldn't find any settings within CM that allowed me to change this feature.
Thanks
Hello everyone, i've some issues with front proximity sensor, sometimes it stay with 1cm and call screen stay always black and WhatsApp audio stay on ear and not in loudspeaker. I need press it and work again. But if i restart the phone it work normally again without press the sensor. I already tested on several different ROMs.