Related
Hi to all,
A couple of days ago I noticed that when I answered a call the colors of the screen looked bad, and I didn't pay attention to it.
Now my screen has transparent horizontal lines which are pretty visible, kind of like interference you get in computer screens when you take a picture of them.
I would like to mention that I haven't dropped the phone even once.
I'm considering doing a factory resest in hopes that it will solve the problem, but I doubt that it is a software issue.
What do you guys think?
Please advise
Itay
Sounds like a broken screen to me. And definitely like a warrenty case. Restore stock f/w if you have flashed and return it.
Restore the original firmware (if you have flashed the phone) and call the samsung service for the assistance.
the thing is that now I don't see it at all.
It's as if it came and gone.
I disabled my task killer and juice defender, performed a complete titanium backup, in case I want to restore afterwards, and now everything is normal.
It does sound like a hardware issue, but do you think there's a chance it is software related?
I'm asking because I purchased it in europe, and I don't live there, so sending it for repair is something I would rather avoid.
Of course, if it is indeed 100% hardare issue, I have no choice.
That is why I'm asking, to be certain and to see if there are others who experienced this issue.
Your replies are much appreciated
update:
It appeared again -> Did a Factory Reset -> It's still there -> Sending for repair.
Must be a hardware issue.
Thank you for your replies.
I've actually always had slight screen issues with my Galaxy S also. The screen flickers slightly once in a while. I don't know if the radio is actually the cause but it's the kind of thing you might expect from radio interference.
Has anybody else noticed this?
Benjamin Dobell said:
Has anybody else noticed this?
Click to expand...
Click to collapse
Nope, never seen any flicker. My screen seems to have a defect of it's own though, but I'm not sure if it's worth the effort to send it in, because I imported mine from the UK while I live in South Africa.
When in the sun or under bright light I can see a two vertical lines near the sides and a horizontal line on dark/black colours and when the screen is off. As if those pixels have a grey/brown tint to them. The line is mostly one pixel thick but in places it is two pixels.
They are almost impossible to see unless under sunlight where they are clearly visible where the screen is black.
Does anyone else see this or know anything about it?
Edit: Apparently it's just the motherboard or something visible through the screen and they all have it, so I'm worrying about nothing...
That's interesting...
It used to come and go, but I think now it's here to stay.
It's really annoying and the screen, while usable, is really not a pleasant sight to look at.
I've attached some photos showing the problem.
With a normal screen I would say that it looks that way because that's what you see when you photograph a screen of an electronic device, but the sad thing is that what you see in the picture is exactly what I'm seeing now.
I did a factory reset, so it's in german now.
I heard some Droid X had a similar problem, but didn't know Galaxy S was having it as well.
In any event, can you confirm that after a factory reset, I no longer have root access?
Just making sure so that they don't give me problems with the warranty.
seem like the phone was dropped, and the screen got damaged
the connectors are lose
double posted again....
Really?
That's very weird...
The only time it was "dropped" was from half a meter , it didn't fall directly but partially sideways, it was with a case, and it landed on its back, not on the screen.
I wouldn't even call that a fall.
Unless, someone in my family dropped it without telling me...
Either way, I think there's no escape but to send it to repair.
If you think it's a problem with the connectors, would you try and give it to some local lab to try and fix it or send it to samsung for replacement?
I faced similar problem.
This problem only occurs when I use the phone in 2g mode.
there are occasions whereby the signal bar for 2g is full and when I place the phone near some conductive surfaces the lines becomes very obvious, to the point of irritating.
nit sure if anyone has such problems too
I have same problems with horizontal lines.
I never paid attention if i am on 2g or 3g when it happens. I will now.
Edit: rooted on jm5
-------------
It seems that my phone too has started to do the same thing since last night.
I have called Samsung and am waiting to hear from them now.
I hope this is a thing covered in the warranty.
I have reverted to the local ROM for India and have deleted everything on my device.
Yet it shows lines flickering like you can see on old computer monitors.
Its not as bad as the ones on the attachment above but it is starting to annoy me.
It usually happens when the screen is completely filled with a single color except black.
Eg. When you pull down the notification tray down.
Also I seem to notice that when the wifi is off, it stops.(I dunno maybe a placebo effect)
aditya_t90 ,
I have sent it to Samsung for repair, and they should tell me in the coming days exactly what the problem is and whether it can be fixed under warranty or not.
I will update as soon as I hear from them.
Until then, try to see if it changes when you hold the phone differently, for example if you grip it more firmly or hold it in another way.
itaykoren said:
aditya_t90 ,
I have sent it to Samsung for repair, and they should tell me in the coming days exactly what the problem is and whether it can be fixed under warranty or not.
I will update as soon as I hear from them.
Until then, try to see if it changes when you hold the phone differently, for example if you grip it more firmly or hold it in another way.
Click to expand...
Click to collapse
When did you send it in and when did they receive it(if you were not there when they got it).
Also how long has it been without your phone?
The samsung service center is shut in my area today.
I will go to them tomorrow and get this sorted out.
Its not like the phone was cheap or anything.
I actually sent it to my uncle in Germany because it was purchased there.
He went to the store where he bought it and the store owner immediately sent it to samsung and said that probably by this Tuesday or Wednesday (so tomorrow or in 2 days) he will get an answer from them and see what's going on.
aditya_90 ,
Just to let you know that Samsung are sending me a new phone to replace the damaged one.
I sent in my phone for repairs and they replaced the LCD module. The problem is now gone.
I suggest that you should do the same while the warranty still holds since it appears to be the LCD that failed somewhat.
I've noticed from day one that sometimes the proximity sensor seems to be a bit goofy on my phone. Sometimes the screen would go blank immediately after starting a call, and nothing I could do could bring it back except for putting it back up to my face and pulling it away again.
Welp, now the sensor seems to be totally dead unless I smack the phone with my hand. It makes calls, but the display goes blank and no buttons will work at all until the other person hangs up (doesn't matter if it's incoming or outgoing). I've only had the phone for a week. If I have it away from my face and smack the front of the phone with the palm of my hand the display comes back on and all buttons start working again for a few seconds, then it'll go blank again.
I've reverted it back to the stock DI18 that it came with and formatted the SD card (along with wiping everything more times than I can count). Anything else I should try before I take it back to Sprint tomorrow?
lifeofbean said:
I've noticed from day one that sometimes the proximity sensor seems to be a bit goofy on my phone. Sometimes the screen would go blank immediately after starting a call, and nothing I could do could bring it back except for putting it back up to my face and pulling it away again.
Welp, now the sensor seems to be totally dead unless I smack the phone with my hand. It makes calls, but the display goes blank and no buttons will work at all until the other person hangs up (doesn't matter if it's incoming or outgoing). I've only had the phone for a week. If I have it away from my face and smack the front of the phone with the palm of my hand the display comes back on and all buttons start working again for a few seconds, then it'll go blank again.
I've reverted it back to the stock DI18 that it came with and formatted the SD card (along with wiping everything more times than I can count). Anything else I should try before I take it back to Sprint tomorrow?
Click to expand...
Click to collapse
Mine is doing the same.... even worse actually. If the other side doesn't hang up (after taking call and it going blank)..... I have to do a battery pull to fix the issue until the next call. Other times (smaller percentage)... the screen won't turn off at all while talking on it. Either way is unacceptable. I don't know what is causing it... I tried to do a complete wipe and have stock rom.... but it didn't fix the problem. This only starting happening a few weeks ago. I took it into a sprint store and they ordered me a new phone (out of stock). It's still under warrantly... so all is good I hope. I plan on dumping Samsung once a better Gingerbread HTC phone comes out early next year. Samsung support sucks!
Mine goes blank on every single call - only way to get the phone to respond is by removing the battery or smacking the **** out of the front of it with my hand (at which point it brings up the normal in-call screen). Really annoying especially since I just got it on Tuesday.
Hopefully the store near me has some of them in stock. It's also a service center, and a fairly large corporate owned store, so I'm pretty sure I'll be able to swap it tomorrow.
So, the screen stays black until the call is ended right? Well, I have a solution for ending the call if the otherside doesnt hang up anyway, if your running 2.2...
You can set the power key to end calls, that way you can easily disconnect the call without having to have the screen on. I know this isnt a solution, but it may work as a stop gap until you can get it working correctly.
Menu->Settings->Accessibility-> (If a box pops up saying 'No accessibility applications found', just hit cancel) -> Check the box next to 'The power key ends calls'
If your not running 2.2, you can do this by editing one of the key map files, just follow the how to in this thread: http://forum.xda-developers.com/showthread.php?t=849075
That is an option, but it'd be a lot nicer if the phone actually worked the way it's supposed to.
Turns out the corporate owned stores are open late during the holidays, I swung by a little while ago and they confirmed the sensor was borked. Swapped it out on the spot.
Thanks though.
lifeofbean said:
That is an option, but it'd be a lot nicer if the phone actually worked the way it's supposed to.
Turns out the corporate owned stores are open late during the holidays, I swung by a little while ago and they confirmed the sensor was borked. Swapped it out on the spot.
Thanks though.
Click to expand...
Click to collapse
same here... they were out of stock though...and ordered me one. I wonder what caused the sensor to be broken?
this is not a sensor problem, i have this problem and only had it after having the "leaked" 2.2 froyo build, and flashing back to eclair.
this problem didnt happen on 2.2, but now it happens to me on 2.1
Same thing, when i make a call, screen is dead, the only way to get it back is to have the other person hang up.
I have the same issue. I make a call, put the phone to my ear and the screen goes blank. Say I'm calling my credit card company and need to enter in my credit card number via the keypad to continue, I take the phone from my ear back to horizontal in front of me and the screen won't turn on. I can press all buttons, open and shut the keyboard but nothing gets the screen to turn back on until the phone call is disconnected, or I pull the battery.
I don't have insurance through Sprint or Best Buy. I got the phone the first day it was available last fall. I flashed back to stock and still had the issue, the most I ever did was root and clockworkmod. What should I do? Do I have a manufactures warrenty? What kind of process is that, will I be stuck with a POS phone for a month like I was with my Touch Pro back when I had Best Buy replace that...
bmasephol said:
I don't have insurance through Sprint or Best Buy. I got the phone the first day it was available last fall. I flashed back to stock and still had the issue, the most I ever did was root and clockworkmod. What should I do? Do I have a manufactures warrenty? What kind of process is that, will I be stuck with a POS phone for a month like I was with my Touch Pro back when I had Best Buy replace that...
Click to expand...
Click to collapse
I think this would fall under the "manufactures warrenty" since you might have a possible hardware failure already within a year. I would call and ask to find out.
While I'm waiting to stop at the Sprint store after work I downloaded a few sensor test programs from the market. The ones that support the proximity sensor never give me a value when doing the tests. They usually just sit there in a status of "Waiting for sensor". Does anyone know how Sprint can test the sensor or will they just do what I've done?
bmasephol said:
While I'm waiting to stop at the Sprint store after work I downloaded a few sensor test programs from the market. The ones that support the proximity sensor never give me a value when doing the tests. They usually just sit there in a status of "Waiting for sensor". Does anyone know how Sprint can test the sensor or will they just do what I've done?
Click to expand...
Click to collapse
I know there are phone codes that will put you in the test hardware mode, I did this a while back when I got the epic. If I can remember as you come closer to the phone with the hand or whatever you use either the screen would turn off or it would vibrate maybe it did both like I said I can't remember.
I did some homework for you via Google of course, I tried it out and it worked, a screen will popup when you enter the codes pick sensors...just cover up the prox sensor and the value will change from 0 to a 1 and vibrate.
*#0*# - LCD TEST
red/green/blue/melody/vibration/dimming/megacam/Sensor/touch/sleepmode/LED/RECEIVER
Very useful tests for the LCD
I didn't know they had a hardware diagnostics built in. Thanks for the info. Looks like my proximity sensor doesn't change from 1.0 when I cover up the phone. I had a friend do similiar tests with his EVO and it switch from 1.0 to 0.0 when you got your finger about 0.25 inches away from the sensor. Thanks again.
Just to follow up, I took the phone to my local sprint store, which now is a repair center, and they took a look at it and said that they could fix it for $35. I don't have TEP on it so that is why I paid $35. I picked it up today and they put a new screen (top half of the slider) on to fix it and tightened up the looseness of the slider as well. Well worth the $35 in my mind. Although they forgot to put the micro usb cover back on so I have to stop back and see if that is laying around on the work bench.
Hi, everyone. So I have an LG G4 for more than a year now and I am very pleased with its performance. I did have an issue with sometimes the audio is stuck after a call but I think it more has to do with bad reception as I noticed so its rare this days. However, lately something happened with the knock on feature which I cannot figure out at all. Sometimes it just doesn't work. I tap and nothing happens. The power on button is working perfectly but the knock on is unresponsive. I fiddled with the proximity sensor but it's not it. Sometimes it just stops working for 5-6 times and then it works and the again it doesn't. There is no pattern. When it's powering on the feature works with no hiccups but after that it's like the cpu forgets to monitor the process. I don't know. I have tried calibration and it works with no problem for a few minutes and then it goes back again to this stutter. Does anyone have any ideas about this? I am thinking factory reset but the hassle would be pointless if the problem persists and I am in no mood to install all those apps I have from the beginning for no reason. Any hep will be really appreciated. Thanks in advance.
I am experiencing the same issue but mine Knock on is a bit delaying.. for an example, I double tap on the screen and it gives response in 3-4 mins or not... I am suspecting from screen protector which has been mounted for almost a year, it could be corrupted(scratch) Give a try on removing the screen protector(if you have any)
It's a hardware problem. Many threads online about it
Sent from my LG-H811 using Tapatalk
Nailen said:
Hi, everyone. So I have an LG G4 for more than a year now and I am very pleased with its performance. I did have an issue with sometimes the audio is stuck after a call but I think it more has to do with bad reception as I noticed so its rare this days. However, lately something happened with the knock on feature which I cannot figure out at all. Sometimes it just doesn't work. I tap and nothing happens. The power on button is working perfectly but the knock on is unresponsive. I fiddled with the proximity sensor but it's not it. Sometimes it just stops working for 5-6 times and then it works and the again it doesn't. There is no pattern. When it's powering on the feature works with no hiccups but after that it's like the cpu forgets to monitor the process. I don't know. I have tried calibration and it works with no problem for a few minutes and then it goes back again to this stutter. Does anyone have any ideas about this? I am thinking factory reset but the hassle would be pointless if the problem persists and I am in no mood to install all those apps I have from the beginning for no reason. Any hep will be really appreciated. Thanks in advance.
Click to expand...
Click to collapse
Is your case or temp glass protect over prox sensor. That can affect it bad. Also scratches on glass over prox sensor. If not. Then more than likely hardware related.
No the screen protector does not cover the prox sensor. It's cut out as it should be. I am starting to think it's a hardware problem. The thing is why now?!
Nailen said:
No the screen protector does not cover the prox sensor. It's cut out as it should be. I am starting to think it's a hardware problem. The thing is why now?!
Click to expand...
Click to collapse
They are mostly sensors just like on a car. Sometimes it's just there time. Electrical components fail all the time. Are u rooted. Modified anything recently?
TheMadScientist420 said:
They are mostly sensors just like on a car. Sometimes it's just there time. Electrical components fail all the time. Are u rooted. Modified anything recently?
Click to expand...
Click to collapse
No. I haven't touched it at all yet. I am pretty satisfied with the performance so I left it alone. The only thing worth mentioning is that I overheated taking a lot of pictures during an event. Maybe this did a number on it!
I have been discussing the issue with a technican today. It is a hardware issue, you cannot fix it. Apparently, the proximity sensor dies after ~2 years - at least somewhat. Why somewhat?
Check this out: You can check the status of your sensor using MINIOS, type *#546368#*815# (n.b. - swap 815 for your model number).
Now click device test - MT - ok - Individual Item - Sensor test - WAIT!
The proximity sensor will run a test and likely come up with a figure between 60~90. The actual value should be 220+.
Meaning: Your phone thinks it´s ~6-9 cm away from your face, that is not enough to trigger knock-on but it´s far enough to be triggered using the backside button.
My knock on doesn't work, but knock off does. Not a major issue, just annoying!
So i have an H812 model and last year i had the dreaded boot loop issue but got it fixed under warranty and no issue since with that. The issue that is irritating the hell out of me now is that the double tap to turn screen on just stopped working reliably. It barely ever works.
I've tried the sensor calibration from the hidden menu and i have a question about that also. My sensor acts like it calibrates fine but the # next it seems kinda low (# next to proximety cal pass ...). It's around 48. See screenshot for reference taken from xda https://forum.xda-developers.com/attachment.php?attachmentid=3513220&d=1445359160
Has my sensor just crapped out? and if so, is that normal. Any help would be appreciated, i've gotten so addicted to using that feature that people ask me what the hell i'm doing when i try to turn their phones screen on lol.
Edit: No screen protector on btw and the internal board as far as i can see seems fine too. And the double tap to turn screen off works fine.
Thanks
sunster said:
So i have an H812 model and last year i had the dreaded boot loop issue but got it fixed under warranty and no issue since with that. The issue that is irritating the hell out of me now is that the double tap to turn screen on just stopped working reliably. It barely ever works.
I've tried the sensor calibration from the hidden menu and i have a question about that also. My sensor acts like it calibrates fine but the # next it seems kinda low (# next to proximety cal pass ...). It's around 48. See screenshot for reference taken from xda https://forum.xda-developers.com/attachment.php?attachmentid=3513220&d=1445359160
Has my sensor just crapped out? and if so, is that normal. Any help would be appreciated, i've gotten so addicted to using that feature that people ask me what the hell i'm doing when i try to turn their phones screen on lol.
Edit: No screen protector on btw and the internal board as far as i can see seems fine too. And the double tap to turn screen off works fine.
Thanks
Click to expand...
Click to collapse
Is the little black rubber plug in the prox sensor. They may have forgot to put it back in. This little black plug is required for proper prox sensor to function properly.
Thnaks for the response but It worked perfectly for quite some time after the board was replaced by the service center so don't think that's it.
I'm guessing you dropped your phone. That's the problem
deltadiesel said:
I'm guessing you dropped your phone. That's the problem
Click to expand...
Click to collapse
Sorry man, never got an alert to this but better late than never . Can't recall but i might have. Why would you say that? Is there a possibility something moved or broke or just plain got whacked out of place? Of course the issue is still there. I was thinking about opening it up anyways so i'll take a look. Thanks
sunster said:
Sorry man, never got an alert to this but better late than never . Can't recall but i might have. Why would you say that? Is there a possibility something moved or broke or just plain got whacked out of place? Of course the issue is still there. I was thinking about opening it up anyways so i'll take a look. Thanks
Click to expand...
Click to collapse
So i opened it up and checked the rubber piece just to make sure and it's there. Everything else looks ok. I guess the sensor just crapped out and will just continue to live with it.
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