Database Develop

Proximity Sensor testing request

Hi,
I've made an app for the Hero which uses the light sensor as a proximity sensor, but the magic has the same sensor I believe so could someone kindly download it and test please? Its in the market, just search Proximity Sensor
Thanks

Didn't work on my 32B Voda Magic. I'm pretty sure the magic has no light sensor though.

Thanks for testing, did it just FC?
Don't know if it does have a sensor, but this place has a review where they say "On top of the display is the earpiece, flanked by an ambient light sensor and the status LED."
Anyone know for sure?

It ran and I followed the instruction of covering the light sensor etc. but nothing happened.

no, the magic has no light sensor.
there is a place for that, but it has no light sensor.
we ttried already when we ported hero roms. but there is none.
just the hero has a light sensor. the magic not.

Ok thanks for the confirmation, shame!

revie on Gsm arena says there is a light sensor
http://www.gsmarena.com/htc_magic-review-377p2.php

they are wrong then.
we had this discussion when hero roms came out

Iris scanner always on and emitting IR

Using the T-mobile Note 9 here, and I've noticed something peculiar. The front facing iris sensor is *always* on, even when it's not lit up red when scanning. Whether the screen is on or off, the scanner is on and sending IR. Even turning off biometrics doesn't stop it. I found this by chance as an infrared detector I have lights up whenever my phone screen faces it. (goes off if I cover the iris sensor).
Why is Samsung keeping the sensor on all the time, even when I turn off biometric unlock?

pakraider said:
Using the T-mobile Note 9 here, and I've noticed something peculiar. The front facing iris sensor is *always* on, even when it's not lit up red when scanning. Whether the screen is on or off, the scanner is on and sending IR. Even turning off biometrics doesn't stop it. I found this by chance as an infrared detector I have lights up whenever my phone screen faces it. (goes off if I cover the iris sensor).
Why is Samsung keeping the sensor on all the time, even when I turn off biometric unlock?
Click to expand...
Click to collapse
My best estimate would be that this will be used as the proximity sensor.
OK, false, if you open the sensor test menu in the dialer by keying in "*#0*#", then open sensor test, you will notice that the sensor right next to the IR emitter is the proximity...
Maybe it would assist the proximity?
Sent from my [device_name] using XDA-Developers Legacy app

Isn't this supposed to be bad for the eyes?
Samsung itself says during setup that the iris scanner should not be used on children, and also, when a person uses it, for safety it should be held around 25cm or more from the face..
If it is always on maybe it is better to cover it up?

Yeah, it can damage your eyes. The reason it's supposed to be safe is that your exposure is so low (just when you unlock). But it's on all the time!

TML1504 said:
My best estimate would be that this will be used as the proximity sensor.
OK, false, if you open the sensor test menu in the dialer by keying in "*#0*#", then open sensor test, you will notice that the sensor right next to the IR emitter is the proximity...
Maybe it would assist the proximity?
Click to expand...
Click to collapse
Still, there's no reason for it to be on when the phone is locked and the screen off.

pakraider said:
Still, there's no reason for it to be on when the phone is locked and the screen off.
Click to expand...
Click to collapse
Could be for sensing if your phone is in your pocket, there is such a setting.
Sent from my [device_name] using XDA-Developers Legacy app

TML1504 said:
Could be for sensing if your phone is in your pocket, there is such a setting.
Click to expand...
Click to collapse
I disabled that to test, still stays on.

pakraider said:
Yeah, it can damage your eyes. The reason it's supposed to be safe is that your exposure is so low (just when you unlock). But it's on all the time!
Click to expand...
Click to collapse
I mean, if it is always on, what is the difference from when you are trying to use it to unlock your phone? If it is on all the time, it would be damaging every user's eyes all the time while they are using the phone..

Did you check that it is actually the iris thing sending IR, and not the proximity sensor? E.g. put a small piece of foil on top of a specific hole and see if the IR detector still reacts? (Afaik, proximity sensors using IR should be safe.) Proximity sensor might be "always" on for detecting pocketing as mentioned earlier.

Has this been sorted out?

Bump

melchiar said:
Bump
Click to expand...
Click to collapse
Please don't bump threads in under 24 hours.
This isn't a bug and it also isn't something to worry about. Unlike others have stated in this thread, the tiny amount of IR that is emitted is so small, it'd never have any health impact.
It's more than likely that OP's detector is picking up the IR from the proximity sensor, a sensor that is constantly on and emitting IR.

Try turning off all these functions and report back.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N960U1 using Tapatalk

How did you find that your IR diode is still on? Did you take another phone and via it`s camera notice glowing? Or how else?

I am pretty sure something else is emitting the light and not the iris scanner.

Just to close the loop on this, the Android Pie update has fixed this bug. Now the sensors only emit IR at the lock screen while trying to unlock.

pakraider said:
Just to close the loop on this, the Android Pie update has fixed this bug. Now the sensors only emit IR at the lock screen while trying to unlock.
Click to expand...
Click to collapse
How did you test this?
Photo's[emoji2398] by Sully using SM-N960U or SM-870A

sullytrny said:
How did you test this?
Photo's[emoji2398] by Sully using SM-N960U or SM-870A
Click to expand...
Click to collapse
I have an IR detector, which is how I picked up on this issue in the first place with the sensors always emitting IR all the time with Oreo. After the update to Pie, I verified that they are only emitting IR when trying to unlock the phone on the lock screen and they turn off right afterwards.

pakraider said:
I have an IR detector, which is how I picked up on this issue in the first place with the sensors always emitting IR all the time with Oreo. After the update to Pie, I verified that they are only emitting IR when trying to unlock the phone on the lock screen and they turn off right afterwards.
Click to expand...
Click to collapse
It's to bad you didn't have a chance to reset to factory because there is a proximity sensor but I have not looked up how it should work
Photo's[emoji2398] by Sully using SM-N960U or SM-870A

I've just discovered my Note 9 always has an IR light on, VIA security cam with night vision. It got the Android 10 update recently. I don't know if this was happening before the update.
Does anyone know how to turn it off?

"Virtual" Proximity Sensor

According to this article, the Oneplus 7 Pro does not have an optical/IR/hardware proximity sensor:
Optical hardware proximity sensors have been around since the dawn of the smartphone and are used to turn off the screen and disable touch functionality when a user is in-call. Since they typically rely on infrared hardware sensors, they require unsightly holes on the front of the phone in order to function. In contrast, Elliptic Labs’ patented software-based virtual smart sensors possess no such handicap, providing cleaner design while simultaneously offering support for additional features such as gesture and presence detection through its proprietary fusion of sensor data, AI, and machine learning.
Click to expand...
Click to collapse
This would seem to indicate that the procedures espoused in various threads related to proximity sensor calibration via the factory test menu (*#808#) are not actually doing anything, and that also the various suggestions that the sensor is behind the display are erroneously based on information related to other phones.
Using an app that let me read the proximity sensor, my own (albeit limited) testing seems to confirm this notion in that covering the display with your hand does not trigger the proximity sensor (regardless of the position of the phone). However, I can get it to react when I bring it to my ear. My guess is that the motion sensors are being relied upon, and possibly the microphone as well (to detect noise level changes when the phone it brought close to the face). Additionally, the reading is ever only 0 or 5 cm - nothing in between - which further lends credence to the lack of hardware.
I cannot account for why some people are saying that running the proximity sensor test somehow fixes double tab to wake issues, but given that many others seem to have limited or no success with this method leads me to suspect the reasoning is fallacious (post hoc, ergo propter hoc). (I'm not trying to cast aspersions, and mean no offense.)

Don't know about that, but every phone that I ever owned have always shown 0 or 5 on proximity sensor tests. So, that's not a good indication for your theory.
Just adding some information, not saying you are wrong or anything. I honestly don't know.

It seems like what they are doing is using the earpiece as the proximity sensor but only when the device is held up to the ear.
If you download the app "sensors multitool" on Google play and look at proximity, you can see covering the earpiece with a piece of paper does nothing until the phone is in an upright position.
The thing is, the phone also has an ir proximity sensor under the screen but it seems that they have disabled it in the latest 9.5.8 because before cpuz and other tests would make it visible in the upper middle-right of the screen but after updating to 9.5.8, it no longer works. Would also explain why you can't go into the calibration settings for it anymore.
Edit: if you select light sensor in the multitool app, you can cover the upper right portion of the screen with a piece of paper or something else and see the value go down and then back up when you uncover it. That's the ir proximity sensor as well.

And here's another thing. Attached is a screenshot from the ifixit oneplus 7 pro teardown video. When they remove the motherboard, you can clearly see the two cutouts in the display for the ir proximity sensor/lux sensor on the top right (left on screenshot because back of display)

jdhedden said:
According to this article, the Oneplus 7 Pro does not have an optical/IR/hardware proximity sensor:
This would seem to indicate that the procedures espoused in various threads related to proximity sensor calibration via the factory test menu (*#808#) are not actually doing anything, and that also the various suggestions that the sensor is behind the display are erroneously based on information related to other phones.
Using an app that let me read the proximity sensor, my own (albeit limited) testing seems to confirm this notion in that covering the display with your hand does not trigger the proximity sensor (regardless of the position of the phone). However, I can get it to react when I bring it to my ear. My guess is that the motion sensors are being relied upon, and possibly the microphone as well (to detect noise level changes when the phone it brought close to the face). Additionally, the reading is ever only 0 or 5 cm - nothing in between - which further lends credence to the lack of hardware.
I cannot account for why some people are saying that running the proximity sensor test somehow fixes double tab to wake issues, but given that many others seem to have limited or no success with this method leads me to suspect the reasoning is fallacious (post hoc, ergo propter hoc). (I'm not trying to cast aspersions, and mean no offense.)
Click to expand...
Click to collapse
Interesting theory, but this device definitely does have an infrared proximity sensor. Just open CPU-Z and raise the phone up like you're making a call, then take a picture of the screen with another phone.

Proximity Sensor Issue

I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?

I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.

jdock said:
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
Click to expand...
Click to collapse
Thanks mate, appreciate your feedback. Proximity sensor works fine on my phone during calls. Can't think of any reason why Samsung would intend it this way...

Proximity sensor issue here as well
I have the same problem. I put phone into test mode and it was bad compared to my wife's s9 search proximity sensor s20fe on YouTube and see others with issue

There is no fix. This is apparently the way AOD works now. I can't remember if it started with the S10s or S20s.

uggies said:
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
Click to expand...
Click to collapse
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.

No problems with Verizon S20 FE 5G UW
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
I just purchased the Samsung S20 FE 5G UW (how about we shorten this to FE UW?) with all updates AND a glass screen protector and have no touch/proximity issues.
FYI I bought it at the Costco kiosk for a few dollars less per month, no activation charges and a 90 day return policy.

the Galaxy S20 FE (5G) has no physiscal proximity sensor.
Insted it uses a combination of the front camera, touch screen and gyroscope.

I have tested the proximity issues, luckily for me there were ok...turn green. The only thing that drive me crazy is the touch screen issues which never been fixed even after updates. Oh well at least its better than before.

Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
Mate great information here, really appreciate this.
Tested the Proximity sensor using *#0*#, I agree with your analysis. The proximity must be using electric reaction to detect if my ears are touching it or not. Covering it with a book does not trigger a proximity sensor... This explain why my screen keeps waking up in the pocket.
As much as this is annoying, there appears to be no way out Just have to let the phone face outside rather than my legs.

I also have the same issue, while on a phone call, the phone's screen goes on and off constantly and I can see the notification bar moving. Very annoying.
This is a terrible design by Samsung. The punch hole usually goes in the "Empty" part of the ear, so the screen stays mostly on.
I might just return the phone because of this issue, I don't see it getting fixed by a software update.

I have the exact opposite issue with the proximity sensor on my Samsung S20 plus running Android 10 - i.e. it works well by turning the screen off when my ear/cheek/face is very close to the proximity sensor during phone calls; whereas, when the phone's screen is locked and turned off, the proximity sensor is turned off as well. Control by hardware? Software/firmware? Don't know?! To turn the screen on without using the Power hardware button, I had to enable the "Double Tap" feature in Settings.
On earlier/other Android mobile devices - Samsung included - the proximity sensor is always on - whether the screen is on, off, or currently locked. When it's always on, you can be innovative and build a widget, for instance, to turn the screen on by "waving" your hand above the proximity sensor to interrupt the laser. I suspect new(er) Samsung mobile devices like S20 and Note20 variants might be using a "virtual" proximity sensor setup/combo for controlling the device's screen - and that really sucks!
To test if the proximity sensor is always activated on Samsung S20 and Note20 variants, I type *#77692# - which displayed a hardware screen to test proximity and light sensors. Note: if you type *#0*#, the proximity and light sensor options are absent from the hardware test screen.
Has anyone found any method - via codes even - to permanently turn on the proximity sensor, even when the screen is locked and turned off?
I searched through AOSP framework vanilla codes and couldn't see anything out of the ordinary regarding control of the proximity sensor. Samsung might be doing something dubious with their firmwares/hardwares though - well, at least, the S20 and Note20 variants are having issues with the proximity sensor setup.
P.S: Not sure if you guys are aware, but Samsung mobile devices with odd designation tends to be more problematic than their even-designated counterparts, like screen's burn-ins/shadows on Samsung S3 devices, light sensor fluctuation (which affects screen brightness control) on Samsung S5s, and now proximity problems with the S20s and Note20. Samsung S20 variants are in fact "S11" variants renamed. So the trend continues with Samsung always stuffing up their odd-designated device releases.

Question No proximity sensor in s21 ultra ?

I feel there is no proximity sensor in this phone..
Becuase while i am on call , even though the screen is touched to my ear , it will light up randomly as i am walking and turning.
Is that function managed by accelerometer and gyroscope as in new redmi phones ?
The autobrightness is also acting weird for me in some cases .

aj7400 said:
I feel there is no proximity sensor in this phone..
Becuase while i am on call , even though the screen is touched to my ear , it will light up randomly as i am walking and turning.
Is that function managed by accelerometer and gyroscope as in new redmi phones ?
The autobrightness is also acting weird for me in some cases .
Click to expand...
Click to collapse
It doesn't do so for me but yes if I move my face when talking the screen turns on but then goes back off immediately. It seems that proximity sensor is managed by the accelerometer combined with ai just like it was in my old OnePlus 7Pro. However, I could be totally wrong!

amirage said:
It doesn't do so for me but yes if I move my face when talking the screen turns on but then goes back off immediately. It seems that proximity sensor is managed by the accelerometer combined with ai just like it was in my old OnePlus 7Pro. However, I could be totally wrong!
Click to expand...
Click to collapse
While on call I tried to use another phone`s camera to search for proximity sensor ( it is ir based , so camera picks it up).
But couldnt find it

aj7400 said:
While on call I tried to use another phone`s camera to search for proximity sensor ( it is ir based , so camera picks it up).
But couldnt find it
Click to expand...
Click to collapse
So then, my suspicions are right..It's accelerometer+ai

I think it uses the camera too. If you try unlock the phone with the selfie camera covered, it will try to prevent it.
Likewise, if you make a call with your phone placed flat on a surface, you can get the screen to turn off by covering the camera.

adamlee2012 said:
Yes it has one. It's near the light sensor... They are both under the display.
Click to expand...
Click to collapse
I dont think it has .
Even when i am on call , phone just touching my ear , it randomly lets the screen turn on .
Also as far as i remember , always on display in the previous generations used to turn off when the phone was in pocket ( or screen was covered)
But here , the aod always remains on regardless if phone is in pocket or outside .

adamlee2012 said:
I’ve just tested mine during phone call. It’s definitely there… I’ve seen it.
Click to expand...
Click to collapse
Yes you are right. It has an ir based one like note 10,20, s10, s20...

Samsung probably is wondering if they should make it invisible with no indicator. That tiny flashing circle has caused more commotion than a midget hooker in the playpen. Every new model provokes this same discussion... talk about a fixation
Using the camera sensor be prohibitive because of power consumption. It would still need an IR emitter to work properly. Net zero gain... and a lot of added complexity at best.

You can test the light sensor with CPU-Z, cover the space to the right of the front camera, that's also what triggers display dimming no matter what adaptive brightness settings you have.

my S20 FE does the same thing on calls. super irritating... i wonder if Samsung will correct the SD card slot omission mistake on the S22. they did the same thing with the S6 and fixed it on the S7

inpression said:
You can test the light sensor with CPU-Z, cover the space to the right of the front camera, that's also what triggers display dimming no matter what adaptive brightness settings you have.
Click to expand...
Click to collapse
The light sensor is there , itried with cpuz , but i feel the proximity sensor does not work properly .
It wakes up the screen during calls