Database Users

[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 Strange behaviour - not working if u get very close.

I dont know if this is an issue with other handsets.
I installed proximity screen off application . The purpose was to have the phone turn the screen off when i close my flip case.
However i found something strange.
When the flip case is very close to the screen the proximity sensor does not seem to detect that there is something covering it.
Is this an issue with every one ?
Any solution
Please see the videos
As you can see from the videos when i bring the shield very close the proximity sensor does not seem to detect the sheild.
Edit : However if u use ur finger this is not seen

I've noticed the same behavior, it's quite annoying because it kills one of NoLed's best features (screen off using prox. sensor).
[deleted]
Still really annoying that the original flip cover won't work with the proximity sensor. A workaround might be a third party flip case. A diy modification of to the original one won't work since if I close it AND hold whatever object that alone is enough for a positive result over the flip cover, the sensor will still not register positive [because a minimal distance between an object and the glass surface is required, see below].

mine works even with a finger...
I've done it a few times accidently when i was trying to access the notification bar while on the phone

ph00ny said:
mine works even with a finger...
I've done it a few times accidently when i was trying to access the notification bar while on the phone
Click to expand...
Click to collapse
Thats the thing i was saying.
With finger i works great even if u touching the screen

Dial *#0*# and press sensor. If it vibrates, the proximity sensor is registering an object.
Maybe it comes in handy with testing.
It's working for me, thanks for the tip about the app!
edit:
Okay, I tested and found that indeed when you set the app to:
"Cover an hold to lock the screen" to say 5 seconds.
Close the flipcover.
It does not register.
However. If I set:
"Disable Accidental Lock" to .25 seconds.
Close the flipcover.
It works quite well.
Coming back to the sensor. It indeed does not register the flipcover when it's closed and touching the screen.
Weird thing is it does not register your hand anymore either.
Recreating issue:
Remove flipcover and lay it completely flat over the sensor.
Dial *#0*#.
Press "Sensor".
No registration.
Now hover your hand over where the proximity sensor is, and... How about that, no registration.
This indeed messes up NoLed's battery saving feature.
This can also be a problem when:
You set screen timeout to 10 min.
In the app's settings set "Disable in landscape" to on.
Then use an app in landscape mode.
Close flipcover while in landscape mode.
Then rotate to portrait. At this point it should start registering again and turn off screen..
The sensor does not register and screen stays on.
Drains battery.
It is a really cool idea, but it does not function properly.
It's too flaky, also when just handling your phone. I find myself accidentally turning off the screen.
Maybe if you use a case or some other cover with a different or thicker material it would work better.
I ordered a Zenuscase, I'll give it a try with that one.
Don't know how long it'll take to arrive though

reflective color
heey i found the problem , the sensor is working fine ... but when so close with any black object the light is not reflected back to the proximity sensor.(black color absorbs light).
Repeat your video with any white object and you will notice the difference..
Now i am using Autostart and it works great with samsung original flip cover (white flipcover).
you can use any white sticker on the black one.

ahmedtaha7 said:
heey i found the problem , the sensor is working fine ... but when so close with any black object the light is not reflected back to the proximity sensor.(black color absorbs light).
Repeat your video with any white object and you will notice the difference..
Now i am using Autostart and it works great with samsung original flip cover (white flipcover).
you can use any white sticker on the black one.
Click to expand...
Click to collapse
ya correct, just few day back i have asked this issue to developer
http://forum.xda-developers.com/showpost.php?p=22170417&postcount=5
But it will work perfact if you use proximity + light both sensor enabled.

Color has no influence, distance between an object and the proximity sensor is what matters. I've just tested this using pieces of paper, cloth, metal and wood in white and black colors. The sensor seems unable to correctly register anything that is less than approximately 1 mm away from the glass (it may report 0 cm or jump to 5 cm). Also it seems it only reports changes of a certain minimal distance between two readings, even if the reported value remains the same as the old one. Anything below the threshold of the 5 cm reading will always result in a reported value of 0 cm, but if the effective distance between reading A and reading B was below a certain threshold, the sensor will not report a new reading of 0 cm (thus an object hovering stable over the sensor will not produce a 2nd post). I'm not sure if the sensor has a state that can be read at any time. From my tests using AutomateIt Pro, it seems only new posts can be used by apps. And if the delta between two readings is to small to make the sensor post a "new" result, then this can be problematic under certain circumstances (like trying to turn the screen off after the flip cover got closed (prox. sensor = 0 for 0 sec) and stays closed (light sensor = 10 for 5 sec) while preventing the screen from going off after an accidental wipe over the prox. sensor e.g. with the hand).
@Dr. Ketan: I've tested Power Switch (again) and I'm quite certain that for the Note + Flip Cover it only works through the light sensor (which is unsatisfying since it then won't work correctly in the dark). Covering the proximity sensor only doesn't make the app reliably react.

Power switch works ok for me with the Samsung flip cover. I have the confirmation set to minimum Abe theactivation delay set to 0 seconds.
It doesn't always work from the lock screen but works fine from the home screen or apps
Sent from my GT-N7000 using xda premium

so is it a hardware issue of software?
might it be fixes in ICS? it's fu***ng annoying! just bought the flip cover(black) yesterday and also bought smart cover app, my note's screen keeps on turn off (when flip closed) then it turns back on (flip still closed)!
Any solution for gingerbread? like proximity calibrator perhaps? (while waiting for final version of ics to come out)

Power switch will work if you use proximity + light sensor both.
Sent from my GT-N7000 using xda premium

dr.ketan said:
Power switch will work if you use proximity + light sensor both.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It's so sensitive that the moment my finger move over the sensor, the shutdown menu pops up.
Any app that works with the flip cover?

Defective proximity sensor/screen stays off [SOLVED]

Just wanted to post up in case anyone has a similar problem.
Since I got my phone the screen never turned on when I took it away from my face - had to push the power button. Really annoying. Thought it might have been a bug in android but once I got into the test screen through *#0*# at the dialer, I found my proximity sensor ADC values never dropped below 50.
As demonstrated by the display model at AT&T, the ADC value range should be 0 - 255.
This problem simply caused the phone to detect proximity and turn the screen off (in my case an ADC around 61), but the ADC values never dropped enough (below 50, obviously) to trigger the reverse.
So if your screen stays off when you take your huge phone away from your head, check your ADC values.
AT&T warrantied the phone no questions asked :good:

[Q] i9505 Proximity Sensor problem

Hi everyone,
since a few weeks i got problems with the proximity sensor on my i9505
First i thought that it is software related but after clean installing a new ROM yesterday i see that the problem still exists...
It happens when the proximity sensor should react, when i am close to it, it reacts and activates but the problem is that it wont turn off again...
i dialed the test menu and went to sensor test, as i see the sensor sees the distance normaly, when i bring it close and when i move it away i see that the numbers react how they should, however after the sensor is once trigerred with a close object it starts to vibrate and the screen turns green (how it should), but after moving away it registers the distance but it won´t stop to vibrate and turn off :/
Anyone who knows what could be wrong?
I have to mention that the display was changed once (because of the glass broke) but it was working normal for months...
EDIT: after testing again i see that the sensor sees the distance just as it should the only problem is that once that the sensor action is triggered to 1.0 from 0.0 it stays at 1.0 no matter if i remove my hand...

D800 Screen keys pressed while on call - build.prop mod?

I´ve searched this forum, but found nothing like what I am facing. As per title, whilst on a call, with the phone on my ear (left ear usually, if that means anything) the on screen buttons are pressed, because I usually end up with the call on hold. Other times, it finishes the call, other times it dials a number from the contact list...Here´s a list of what I have done so far with no success:
1. Calibrate proximity sensor with apps
2. Use hidden menu to test functionality (it works as advertised)
3. Calibrate motion sensor
4. Full reset of the phone
5. Clear dalvik cache
6. Test sensor functionality with app (again, works as it should). It detects when my hand is covering the sensor and it detects when my hand is taken away from it. Instantly. Also, left my hand covering the sensor for a while (simulating a call) to see if at some point it stopped working, but no, the darned thing worked as it should.
I read somewhere here that a mod on build.prop might help (it has to do with the delay time of the proximity sensor) but since the post didn´t explain the exact setting, i googled it, and found 2 settings that might apply:
1.) ro.lge.proximity.delay
2.) mot.proximity.delay.
Neither of them is in my build.prop file, so, the questions that pop to my mind are:
1.)Which one of the two would affect the described issue? Apparently those settings are modified by users that had a problem with black screens after a call or with long delays for the screen to come back after taking the phone from their ears to use the keypad, but no post that I read indicated which one of the settings influenced what. I have the feeling that one of them is for the proximity sensor to "kick in" while the other controls how long does it take for the screen to come back after the proximity sensor stops detecting your ear.
2.)Can I add that setting to my build.prop without risking a bootlop or a brick?
As the title say, I have a D800, with official AT&T 5.0.2 ROM, rooted, with stock recovery.
Any help would be highly appreciated. As you can imagine is terribly frustrating that I cannot use my smartPHONE as a PHONE because of this!
Thanks in advance!
Frank.

a small, shameless bump!