Hello everyone, I recently got Note3.
Today, I looked at my phone through another phone camera and found a sensor which kept blinking all the time. (Please see attached clip)
To me, it seems like an infrared since human eyes could not see it.
Is this normal even I don't have air gesture ON?
Thank you
guitarz said:
Hello everyone, I recently got Note3.
Today, I looked at my phone through another phone camera and found a sensor which kept blinking all the time. (Please see attached clip)
To me, it seems like an infrared since human eyes could not see it.
Is this normal even I don't have air gesture ON?
Thank you
Click to expand...
Click to collapse
I noticed this on my s3 you can see it only through another camera.:-X its normal dont worry.
Sent from Galaxy Note 3 SM-9005
guitarz said:
Hello everyone, I recently got Note3.
Today, I looked at my phone through another phone camera and found a sensor which kept blinking all the time. (Please see attached clip)
To me, it seems like an infrared since human eyes could not see it.
Is this normal even I don't have air gesture ON?
Thank you
Click to expand...
Click to collapse
Very interesting. Mine too
That is the IR.
If you're using an IR remote app, and you press a key, that'll light up for human eyes to see.
ShadowLea said:
That is the IR.
If you're using an IR remote app, and you press a key, that'll light up for human eyes to see.
Click to expand...
Click to collapse
How can it be the IR?
If you were using an IR remote app then you'd have to show the front face of the phone to the TV, which would make looking at the phone screen a bit of an issue.
Bulbous said:
How can it be the IR?
If you were using an IR remote app then you'd have to show the front face of the phone to the TV, which would make looking at the phone screen a bit of an issue.
Click to expand...
Click to collapse
You mistake my meaning. If you look at the top of the phone, you'll see a small dot next to the audiojack. That is the IR blaster. The blipping dot at the front is the indicator of the IR blaster. It lights up when the IR blaster is transmitting, to alert the user.
Related
Front camera, ALS, infrared sensor and what's the fourth one?
I found in the video that the led is on the left of the speaker and cannot be recognized as a hole,which is the same as S3.
I don't have any idea. I tried to search too, but I can't find any information. Anyone can help us?
I believe the fourthopening maybe a microphone for recording sound bits that can be added to the camera shot.
The four are (left to right):
gesture sensor, infrared emitter, infrared sensor (those two make up the proximity sensor, and then the camera.
Also even more to the left but usually not visible unless turned on, is the notification led.
I suggest you watch this:
http://www.youtube.com/watch?v=diLD42QafIo (starting at bout 1:30).
Hironimo said:
The four are (left to right):
gesture sensor, infrared emitter, infrared sensor (those two make up the proximity sensor, and then the camera.
Also even more to the left but usually not visible unless turned on, is the notification led.
I suggest you watch this:
http://www.youtube.com/watch?v=diLD42QafIo (starting at bout 1:30).
Click to expand...
Click to collapse
IR emitter is on the top edge isn't it?
Al Gore said:
IR emitter is on the top edge isn't it?
Click to expand...
Click to collapse
Yes, the emmitor for remote controlling is on the side of the top of the phone.
See here: http://i-cdn.phonearena.com/images/reviews/129885-image/Samsung-Galaxy-S4-vs-Apple-iPhone-5-08.jpg
It's the round black 'spot' on the right in the 'metal' band.
I have two SGS4's. On one, when I place a call, the call screen stays on and it turns off when I raise it to my ear. It then turns on when I pull it away.
On the other, as soon as I place I call the screen goes dark. The only way to get it back is to push the power button and unlock the phone.
The "Turn screen off during a call" setting is set on both phones.
Anyone have any idea what is causing this? Next step is to do a wipe, but that just sucks.
I'm on stock and not rooted.
Thanks!
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Sirchuk said:
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Click to expand...
Click to collapse
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
jprocket45 said:
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Nope, mine is naked for now. I'll have to do a reset today/tomorrow and see if that solves my issue. If not, I'm taking back to the store for an exchange. It's only been a couple of weeks.
To late for me to take it back but suppose to be a update coming soon that does alot of fixes so we will see Good luck like I said reset I did notice fixed it a bit let me know how it goes I'm threw sprint just curious if you have them only reason I ask if it's just a carrier issue with software or something I doubt it but just figured to see who you had lol
Sent from my SPH-L720 using xda app-developers app
Dial *#7353# and make a test
sent from my Galaxy
samersh72 said:
Dial *#7353# and make a test
sent from my Galaxy
Click to expand...
Click to collapse
That's what I was looking for!
Sure enough,the proximity sensor was always on and wouldn't go off.
I'm with T-Mobile and they have a 30 return/exchange policy if you buy it outright, which I had, so it only took about 10 minutes for them to exchange it!
Thanks for the testing code! XDA comes through once again!
Same problem when I'm making a call, the screen goes blank when I put it to my head and when I remove it nothing happens.
I tried *#7353# and the proximity sensor goes of but will not stop..
I'm currently rooted, could it solve the problem to go back to stock?
Possible Fix
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
I have had the same problem over the last 3 weeks and decided to take a gamble. I tightened up all the screws on the device and squeezed real hard on the area where the prox sensor is and poof... it works. I have no idea what was up but I feel like the sensor is loose and the pressure resolved the issue. Many other post have talked about cleaning the area over the prox real good and it works but I think its the pressure that is actually fixing the issue. Anyone else have any ideas? Sorry if this was posted incorrectly, I have never posted before but I felt this issue is a PITA.
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
My proximity sensor works - when I go into diagnostic, it goes green when I bring a hand near the sensor - my issue is that it doesn't seem to notice when I remove my hand and there no longer is anything proximal - until I hit the back button to exit the test. Other than blowing out the earphone jack, does anyone have a suggestion?
Thx.
divche said:
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
Click to expand...
Click to collapse
Proximity sensor
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
I guess what it comes down to is.....for some you can reset the sensor, for some they can blow it out with compressed air, but others actually have to take apart their phone to fix this issue.
marduj5 said:
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
Click to expand...
Click to collapse
hi
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Shohat said:
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
Click to expand...
Click to collapse
Hubris2 said:
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Click to expand...
Click to collapse
i'm sorry. i already tried your first solution and it worked like charm ! thank you ! :good:
HOw to solve, none of this works. How cann i clean proximity?
I have noticed over the past few days that when my screen is off if I tap the sensor it will turn the screen on and the LED light will also light up (usually 3 taps about 1 second apart).
I have smart stay, air view, and all gestures turned off (except screenshot). Finger print scanner on. nothing set as far as i can tell in any other menu.
Has anyone else experienced this at all? Is this a "feature" to wake the screen up.
It doesn't bother me, just curious. I am going to test on my wife's phone tonight as well and see if hers does it.
Tap what sensor? The one at the top of the phone?
Yes on top of the phone between the ear piece and the front camera.
Interestingly enough I tested on my wifes S5 and hers does not do it. I am curious what app I installed or setting I changed that is making this happen. As of right now I also do not want to reset my phone at this time as it is not a nuisance. I will try to get a video clip of it and post it.
jselden said:
Yes on top of the phone between the ear piece and the front camera.
Interestingly enough I tested on my wifes S5 and hers does not do it. I am curious what app I installed or setting I changed that is making this happen. As of right now I also do not want to reset my phone at this time as it is not a nuisance. I will try to get a video clip of it and post it.
Click to expand...
Click to collapse
Cool.
Here is a quick video of this "feature."
Lodaserves said:
What is cool of that?
Click to expand...
Click to collapse
That a video was to be posted to view of the quirk.
Well I have figured out what was causing my phone to do this. It is in fact a feature of the phone and is called air wake up.
To enable or disable go into Settings>Accessibility>Dexterity and interaction>Air wake up.
I must have at some point enabled this by mistake without realizing it.
jselden said:
Here is a quick video of this "feature."
Click to expand...
Click to collapse
Cool..
I can't added this feature on my phone..
I was showing my phone screen to a friend on webcam today, when I noticed the IR blaster is supposedly active (see attached picture). But it would turn off when the screen would be off as well.
What gives? Is it supposed to be on all the time while the screen is on and wasting precious battery? If not, how do I go on about fixing this, or disabling the IR blaster altogether?
I'm sorry for the stupid questions, I just had to ask.
Thank you for reading!
That is not the IR blaster. The IR blaster is located on the top (top, not front) right side of the phone.
What you are seeing in the picture is the proximity/gesture sensors. They both use infrared and are both next to each other. So it's one of those.
GDReaper said:
That is not the IR blaster. The IR blaster is located on the top (top, not front) right side of the phone.
What you are seeing in the picture is the proximity/gesture sensors. They both use infrared and are both next to each other. So it's one of those.
Click to expand...
Click to collapse
You are absolutely right. I just tested this out on a camera and indeed, the top right corner lit up when I used a TV remote app. But like I said in the original post, forgive me for the stupid question. I just had to put my mind at ease haha
As the tittle says, on the back camera there's something like an infrared led or laser that I'm guessing it's used by the camera to focus better. (This light is only visible from a camera, can't be seen with the human eye)
The thing is that I noticed it's permanent blinking even when the phone is locked and the screen is off.
Is it intented, does anyone know more about this?
Haven't found anything related to it.
Its used to trigger Moto Display
Rheberto said:
As the tittle says, on the back camera there's something like an infrared led or laser that I'm guessing it's used by the camera to focus better. (This light is only visible from a camera, can't be seen with the human eye)
The thing is that I noticed it's permanent blinking even when the phone is locked and the screen is off.
Is it intented, does anyone know more about this?
Haven't found anything related to it.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B5cG4N8kdK8Ka2NGMktMTVZIT1U/view?usp=drivesdk
I have found the same problem.. both back and front side.. i have also found another issue,, if u shake ur phone close to your ears,, it feels like sound of some loose moving part inside.. is this normal or is it with me only..?? Please help..!!
ckret said:
Its used to trigger Moto Display
Click to expand...
Click to collapse
So it'll be blinking 24/7 even if I have that feature disabled?
toyesh.patra said:
I have found the same problem.. both back and front side.. i have also found another issue,, if u shake ur phone close to your ears,, it feels like sound of some loose moving part inside.. is this normal or is it with me only..?? Please help..!!
Click to expand...
Click to collapse
I also hear something loose when I shake the phone. At first thought it was the side buttons but doesn't seem to be the case.
Rheberto said:
So it'll be blinking 24/7 even if I have that feature disabled?
I also hear something loose when I shake the phone. At first thought it was the side buttons but doesn't seem to be the case.
Click to expand...
Click to collapse
Have you watched the video i shared in my previous post.. does it happen the same with you ??
toyesh.patra said:
https://drive.google.com/file/d/0B5cG4N8kdK8Ka2NGMktMTVZIT1U/view?usp=drivesdk
I have found the same problem.. both back and front side.. i have also found another issue,, if u shake ur phone close to your ears,, it feels like sound of some loose moving part inside.. is this normal or is it with me only..?? Please help..!!
Click to expand...
Click to collapse
i can clearly see in the video that you have active display on.
the sensors are on to trigger the active display
ckret said:
i can clearly see in the video that you have active display on.
the sensors are on to trigger the active display
Click to expand...
Click to collapse
Got it ..!! Thank you Ckret..!!
ckret said:
i can clearly see in the video that you have active display on.
the sensors are on to trigger the active display
Click to expand...
Click to collapse
I have moto display disabled and sensors are still on. That's my question, if its intended or it's a bug.
Rheberto said:
I have moto display disabled and sensors are still on. That's my question, if its intended or it's a bug.
Click to expand...
Click to collapse
Same problem bro
Nikhil Stark said:
Same problem bro
Click to expand...
Click to collapse
These are the dual pixel auto focusing Sensors and not the sensors for MOTO Display!!
Ambar Kambli said:
These are the dual pixel auto focusing Sensors and not the sensors for MOTO Display!!
Click to expand...
Click to collapse
Those are proximity sensors and they are not used for focus
Dual pixel auto focus sensors are in the camera sensor, in every pixel... Those are proximity sensors and the can't be turned off even by kernel side...