Related
Hello
The proximity sensor doesn't seem to work on my note II anymore. Whenever i make a phone call the screen just goes black. Also direct call and quick glance won't work. Tried to do the tutorials but nothing.
Anyone else had this problem? Do you guys think it is a hardware fault or software wise? I have tried using two different custom roms and unrooted stock rom.
Sorry for the late reply, but did you ever find a solution for this? Because I just started experiencing the same problem with my phone, and I want to know if I need to try and get it exchanged. Thanks a lot.
Anyone can help ? My proximity sensor not working too ....
Using N7105 Singapore Singtel.
Did not find a solution. A guy told me to get it repaired but still havent't done it.
there is no solution for this sadly
Proximity sensor
Guys i also have the same problem....was searching for solution for quite a long time.
The problem seems to be either the sensor is damaged due to fall or there is dust on the sensor.
The solution which i got are:
1 Send to samsung gallery for sensor replacement (Safest Option and only if the sensor is broken)
2 Take a compressed air can and try blowing through the earpiece grill. (Many have got the sensor back to working since the dust blows off)
I am personally going to try the compressed air solution since my phone didn't fall. So assuming sensor is not working due to dust inside.
Hello!
A month ago I had an issue when all of a sudden, when I was on a phone call and separated my Note 3 from my ear (to check the time as an ex,), the screen would stay black and the proximity sensor wouldn't work. It was very annoying (to me anyways) as I believe in having a phone working 100%. Honestly...I thought it was ROM and/or kernel related, but it's not. Doing some research here in XDA, I found several members of this community (Sprint Note 3 to be specific) experiencing the same issue. Apparently, it's dust affecting the proximity sensor making it unresponsive.
Long story short, one member said that he fixed his Note 3 by blowing air into the earpiece where the sensor is located. I thought the worse about the guy (lol) thinking it was a crazy idea...BUT, I said, "WTH...let me try it" and sure enough, it FREAKING worked!!! My Note 3 was working properly again!
That very same day, on Google +, I came across this article http://www.infotales.com/samsung-galaxy-note-3-proximity-sensor-issue-fix where the author "YASIR MIRZA" wrote an AWESOME article with this particular issue. He goes real deep into the subject and has 2 different methods more in depth about fixing the issue.
I will NOT maintain this thread since I don't have time. I'm only posting this here because I think it's the right place "Q&A", plus maybe if someone has the issue (like I had), by doing SEARCH (like I did), this thread will pop up and maybe help!!!
READING IT'S FUNDAMENTAL... SO READ FROM THE LINK I'VE PROVIDED WHERE IT HAS MUCH MUCH MUCH USEFUL INFORMATION!
HIT THAT "THANK YOU" BUTTON IF I HELPED OR YOU FIND THIS USEFUL!!! IT DOESN'T BITE...lol
That is a really good and thorough article. While I have not had any proximity sensor issues (yet), people who have will certainly appreciate the how-to. It is for a rooted device, though.
This is all great info, but it doesn't address the core issue which I gather from reading, is dust obscuring the sensor. I'm assuming this will recalibrate the sensor partly covered by dust, but If the dust got on the sensor once, there is pretty good chance it will get there again and change calibration? So how to stop it from getting there in the first place would be my concern, especially because so far my sensor works fine. Maybe solution should be to seal headphone jack, (if that's the culprit) which personally I rarely use, with some rubber insert, easy to remove if needed? And there is another opening (microphone?) right next to it, could that be a way inside as well?
As my phone's not rooted, nor have any compressed air handy, I opted to physically clean the sensor.
It's pretty simple and straightforward (the teardown videos are on youtube). Basically, you just unscrew the back casing and remove the sensor. Then either wipe the sensor window or use a tape to stick up the dust.
Before cleaning my readings were 105 and not working. After cleaning it went down to 40 and has been working ever since. Blowing the dust may simply dislodge it moved it around, having a chance of it finding its way back whereas cleaning it removes it altogether until some new dust finds its way back onto the window.
mwerkz said:
As my phone's not rooted, nor have any compressed air handy, I opted to physically clean the sensor.
It's pretty simple and straightforward (the teardown videos are on youtube). Basically, you just unscrew the back casing and remove the sensor. Then either wipe the sensor window or use a tape to stick up the dust.
Before cleaning my readings were 105 and not working. After cleaning it went down to 40 and has been working ever since. Blowing the dust may simply dislodge it moved it around, having a chance of it finding its way back whereas cleaning it removes it altogether until some new dust finds its way back onto the window.
Click to expand...
Click to collapse
I just fixed my proximity sensor problem by doing a tear down and cleaning the dust out from the screen in front of the sensor also. Fairly easy to do.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Hands-free mode
Hi everyone, just disabled the hands-free mode (steering wheel symbol - from the upper curtain) and your problem is solved.
Cheers.
God bless. :laugh:
The link in the OP does not work; am I missing anything - like a period or some other punctuation or some word(s)?
No Gyroscope, No Proximity Sensor, No Temp...
I have a SM-N900 Showing no values for any sensor, I have tried unplugging and replugging proximity sensor with no sucess, also tried restoring via Odin Stock firmware, no sucess.
The Phone was apparently working fine, without root on stock lollipop, and after resetting the device for selling it, it stopped working.
I can't even rotate the screen...
I also tried the calibration method with no sucess...any suggestions?
Same here!!
It is so frustrating. I've restored to stock, with Odin. Had 3 different roms and have never had my sensors working. I've tried
libgnustl_shared-1.so fix for rotation. It didn't work.
Does anyone have any ideas? I don't have water damage.
I solved my problem by installing google phone app and selecting this phone app as system default from app permissions menu.
The heart rate sensor on my phone seems to work only when it wants to. I used it 2 days ago and now no matter where I place my fiber tip over the sensor it does not light up or detect my finger....?
Anybody else have this issue? I think I'm going to ask At&t for a brand new replacement. Cause I've only had the phone for about 3 weeks and it does this all the time.
It'll probably work just fine when you take it in to have it looked out. That's how life works...
It's pretty much hit and miss with mine. For the most part S-Health sensors work just fine. I found if I just adjust my finger (if it starts complaining) that does the trick.
Don't push too hard against the sensor.
I exchanged my note 4 for different reasons, but my last model and this model are both having the same problem with the sensor...
Guys Hi,
After the last update, my watch suddenly stopped counting floors and Altimeter, Barometer is not working. Resetting and rebooting does not help. I have checked permissions also. Any ideas?
Hi! I had the same problem.. I had the floor objective to 150 floors, I changed it back to 10 and it started counting again
Even I'm facing the same issue since the update.. Restarted & even did a hard reset.. still the same
Hi guys I'm just refreshing this thread..
I'm currently having issues with floor count being widely inaccurate and counting way too many floors. I've noticed this behaviour for a few weeks now. To give an example, a few days ago it clocked up to 252 floors and is still clocking phantom floors even when walking on flat ground.
I've calibrated the alti-barometer app and the barometer reading is fine but the altimeter is completely off. It's reading NEGATIVE values (between -60 and -15m) and I live in a high-rise apartment. I've checked the altitude for my location using other webapps and Android apps and they are reading between 5m and 10m for my location.
Same problems. Altimeter, barometer not working. No sleep tracking, no floors, battery from 5 days to 1... Warranty issue. Samsung changed the matherboard and now working again...
lgxmedia said:
Same problems. Altimeter, barometer not working. No sleep tracking, no floors, battery from 5 days to 1... Warranty issue. Samsung changed the matherboard and now working again...
Click to expand...
Click to collapse
I also had to get my motherboard replaced. So many hardware problems with this watch. I can't believe Samsung are being so oblivious to them and not acknowledging them.
Changed two sensors and one mother board on first watch. Third time when it fails received a new watch. Again changed sensor two times, waiting for third failure and I will ask for money return and buy newest Garmin. Galaxy watch is not serious product.
minervino96 said:
Hi! I had the same problem.. I had the floor objective to 150 floors, I changed it back to 10 and it started counting again
Click to expand...
Click to collapse
Same problem here, floor count stopped working and no measurement from the barometer sensor spontaneously, with the floor objective unchanged at 10.
I changed it to 5, just to see if "changing it" would make the difference.
It did, if you reboot the watch after changing the floor objective. :victory:
Many thanks for the tip. I was about to send it back for repair.
Update: since above post (december 6) the barometer sensor stopped working overnight every night I was wearing the GW while sleeping (in "good night mode"), but I was able to revive it with above tip, giving me the opportunity to test different settings to see if I can wear the watch without the barometer sensor stopping. These are my observations:
- After revival of the sensor I can see in the barometer widget when the sensor stopped working.
- I haven't seen the barometer sensor having problems during the day if it works fine in the morning (after a revival).
- A manually started training stops the barometer sensor, an automatically detected training doesn't, although today the sensor stopped 30mins áfter a detected bike trip.
- If I keep the watch on the charger overnight, the barometer keeps working.
- Sleep tracking is intermittent for some reason. It will stop and then continue after an hour or so. The sensor stops when also sleep tracking stops, but doesn't come back "on" when sleep tracking does.
- A reboot before putting the watch in Good Night Mode didn't help to prevent the sensor/sleep tracking problem.
- Disabling detection of REM sleep does not prevent the sensor/sleep tracking problem
- The sensor revives after changing the floor objective and reboot, but watch and phone need to be fully synchronized (sleep tracking/training data) for revival to work.
All in all, I haven't found a setting to prevent this problem. It is clearly a software bug, not a hardware failure. I hope that the new update (R800XXU1DSL1) will solve the problem.
congusto said:
Same problem here, floor count stopped working and no measurement from the barometer sensor spontaneously, with the floor objective unchanged at 10.
I changed it to 5, just to see if "changing it" would make the difference.
It did, if you reboot the watch after changing the floor objective. :victory:
Many thanks for the tip. I was about to send it back for repair.
Update: since above post (december 6) the barometer sensor stopped working overnight every night I was wearing the GW while sleeping (in "good night mode"), but I was able to revive it with above tip, giving me the opportunity to test different settings to see if I can wear the watch without the barometer sensor stopping. These are my observations:
- After revival of the sensor I can see in the barometer widget when the sensor stopped working.
- I haven't seen the barometer sensor having problems during the day if it works fine in the morning (after a revival).
- A manually started training stops the barometer sensor, an automatically detected training doesn't, although today the sensor stopped 30mins áfter a detected bike trip.
- If I keep the watch on the charger overnight, the barometer keeps working.
- Sleep tracking is intermittent for some reason. It will stop and then continue after an hour or so. The sensor stops when also sleep tracking stops, but doesn't come back "on" when sleep tracking does.
- A reboot before putting the watch in Good Night Mode didn't help to prevent the sensor/sleep tracking problem.
- Disabling detection of REM sleep does not prevent the sensor/sleep tracking problem
- The sensor revives after changing the floor objective and reboot, but watch and phone need to be fully synchronized (sleep tracking/training data) for revival to work.
All in all, I haven't found a setting to prevent this problem. It is clearly a software bug, not a hardware failure. I hope that the new update (R800XXU1DSL1) will solve the problem.
Click to expand...
Click to collapse
Sorry but I received that update and my barometer stop working! With no reason! I try to change the objective but no results. Reset and reboot didn't work either.
Only as Info... longer Story:
https://forum.xda-developers.com/smartwatch/gear-s3/samsung-gear-s3-sensors-t3889064
Short... Please check this Code:
Code:
*#0*#
If "scared"... see attached Video.... in theory nothing will explode.
Maybe...
Best Regards
Charging the floor objective stopped working for me as well, so I am getting stuck on this. As soon as I am back home I intend to go back to an older firmware (e.g. BSA4) to see what that does.
This might work to fix floor count and barometric pressure.
I found info on the Samsung site about cleaning the sensor with warm water. I tried it in conjunction with something else and it is early days but seems to have worked. I cleaned the atmospheric barometric sensor (the small hole) on the back of the watch by VERY GENTLY using a wood toothpick with sharp tip blunted to loosen gunk, presumably soap, dust etc and then flushing the particles away with warm water. Don't STAB at it, just very gently rub the blunted tip around it using no downward pressure whatsoever. I had 12 floors today, despite doing none, but in the past few hours no more phantom floors have registered and my altimeter reading of 35 metres has stayed steady. Before, it was ranging from -8 to +70m! I hope this may help some people and again I emphasise be very gentle. It may even just need flushing with warm water, but for me there was a solid mass of soap in there. Let's know if it helped anyone. I will report again in a couple of days to see if I was being over optimistic.
@Maccyb122. Just to understand your situation better, was your watch showing unstable air pressure values or no values at all?
TIA
Thanks for the question. It was showing unstable air pressure.
congusto said:
@Maccyb122. Just to understand your situation better, was your watch showing unstable air pressure values or no values at all?
TIA
Click to expand...
Click to collapse
Maccyb122 said:
I found info on the Samsung site about cleaning the sensor with warm water. I tried it in conjunction with something else and it is early days but seems to have worked. I cleaned the atmospheric barometric sensor (the small hole) on the back of the watch by VERY GENTLY using a wood toothpick with sharp tip blunted to loosen gunk, presumably soap, dust etc and then flushing the particles away with warm water. Don't STAB at it, just very gently rub the blunted tip around it using no downward pressure whatsoever. I had 12 floors today, despite doing none, but in the past few hours no more phantom floors have registered and my altimeter reading of 35 metres has stayed steady. Before, it was ranging from -8 to +70m! I hope this may help some people and again I emphasise be very gentle. It may even just need flushing with warm water, but for me there was a solid mass of soap in there. Let's know if it helped anyone. I will report again in a couple of days to see if I was being over optimistic.[/QUOTE @Maccyb122 after the cleaning other day, the sensor continue still OK?
Thanks
Enviado desde mi Pixel 3a mediante Tapatalk
Click to expand...
Click to collapse
Unfortunately my friend, I have to say no, it didn't fix it. After a day it started acting erratically again. I called Samsung support and they have suggested that the sensor may indeed be faulty. Luckily there is an official Samsung repair centre close to where I live ans and I will be taking it to them early next week for repair or exchange. Ironically a friend of mine did have success by cleaning the sensor, but it didn't work for me.
Maccyb122 said:
Unfortunately my friend, I have to say no, it didn't fix it. After a day it started acting erratically again. I called Samsung support and they have suggested that the sensor may indeed be faulty. Luckily there is an official Samsung repair centre close to where I live ans and I will be taking it to them early next week for repair or exchange. Ironically a friend of mine did have success by cleaning the sensor, but it didn't work for me.
Click to expand...
Click to collapse
What a pity, have you try to cleaning again?
Enviado desde mi Pixel 3a mediante Tapatalk
I did check it. Used a magnifying glass to look at the sensor grill. It's sparkling clean. Can't do any more. When I get a chance to take it in to the service centre, I'll report back on what happened. The watch is performing perfectly well in all other aspects of health, just the floor count is a problem. My hobby is mountaineering so the Altı-Barometer accuracy is important. Never had a problem with the S3 Frontier. I'm a little bit disappointed. I'm sure they'll fix it.
Another update
Change to status. This morning my Altı-Barometer was registering no data whatsoever and reinstall of app and reboot made no difference. It's also completely stopped registering floors. Steps and other sensors are ok. I will be at the Samsung Service centre in about 15 minutes to have them take a look. My guess is that after all the erratic behaviour the sensor has died, given up the ghost, kicked the bucket! Lol
Maccyb122 said:
Change to status. This morning my Altı-Barometer was registering no data whatsoever and reinstall of app and reboot made no difference. It's also completely stopped registering floors. Steps and other sensors are ok. I will be at the Samsung Service centre in about 15 minutes to have them take a look. My guess is that after all the erratic behaviour the sensor has died, given up the ghost, kicked the bucket! Lol
Click to expand...
Click to collapse
Any news? Have you check the status of sensor in test mode?
Enviado desde mi Pixel 3a mediante Tapatalk
i have a oneplus 8 pro that was running on OOS 11 like magic
then update it to COS 12 and the proximity sensor stopped working
yesterday COS 13 came and i thought it would fix the problem but no, the problem still there.
any fix for the proximity sensor one COS 13 please.
Mine is also not working at all since oos12. Im completely stock on oos13 now.
Sensor doesnt react at all.
Hi,
mine too stopped working a few days ago.
Im on OOS13 (eu) but it worked the hole time, suddently it stopped working, without any changes to the system.
I did a proximity sensor test (dialpad : #*899# ) and it does not react at all.
PS : Can anyone tell me where the sensor is located on the phone i cant find it.
riding the same boat
I tried to reset it with "Proximity Sensor Reset" app, but it didnt work so I think its a hardware problem...
Fortunately the hardware piece costs about 5-10 bucks, unfortunately phones today are so glued that I dont wanna hassle to open it just because of the little sensor..
Edit: I found out where the sensor is located somewhere in the right corner,
yesterday I coincidentally noticed that it sometime works when the top right corner comes in contact with my pants or any other fabric.
When I try it with my hands or head it doesn't react at all...
Deavy said:
I tried to reset it with "Proximity Sensor Reset" app, but it didnt work so I think its a hardware problem...
Fortunately the hardware piece costs about 5-10 bucks, unfortunately phones today are so glued that I dont wanna hassle to open it just because of the little sensor..
Edit: I found out where the sensor is located somewhere in the right corner,
yesterday I coincidentally noticed that it sometime works when the top right corner comes in contact with my pants or any other fabric.
When I try it with my hands or head it doesn't react at all...
Click to expand...
Click to collapse
I was going to tell you that, I accidently discovered that proximity sensor is kind of working when in contact with my hoodie that is covering my ears.
but when phone is directly touching the skin it wont work.
Same here. I bought a used one in very good condition and figured out that the phone does not switch off the screen during calls. I can run the diagnostics and see that the sensor works properly when I use some fabric on it but has absolutely no effect when using the hand or the ear.
I wonder how that can be and if it's really an issue with the OS version or a hardware issue.
Also same here. Proximity sensor problems after oos13 update. Has anyone tried custom roms if problem are still occuring on those too?
i found the solution on yt
AidenDRJr said:
i found the solution on yt
Click to expand...
Click to collapse
You are the best thanks a lot
Works 100% fine after new calibration.