Related
Strange issue on my week old Note 2. All of the sensors stopped responding and when entering test mode (*#0*#), SensorHub test brings phone to locked/screen off state. When I wake up the phone it displays sensorhub failure. Did anybody else have something like this? Phone was not rooted and had standard ROM.
It's at warranty service now, will update with result.
Water damage
Guys from the Hungarian Samsung service apparently informed that it might be because of water damage and not covered by warranty, however phone was not exposed extremely to water, just few talks/sms in the rain/with sweaty face. I will still try to negotiate, but if it is the case that phone is so fragile that few rain/sweat drops can destroy the sensors, I would certainly not recommend it to anybody and would not buy it for myself. I'll keep you updated about any updates.
Sony's website displays two IP ratings for this one (IP58 and IP68), hence I don't think it is very reliable when it comes to basing a purchase decision on. Here are some spec-related questions:
So which one is it, IP58 or IP68?
As such, will it be safe to use during snorkeling?
Does it have WiFi? And if it does, are there any chances that they will develop a version (be it truncated, if not fully featured) of their PlayMemories Mobile app?
Will I be able to unlock my phone using SWR50's NFC?
Oh, yeah, and what's the DPI on this thing?
I am sure that it is IP68 rating. People have used it for swimming, but I don't know about going snorkeling since I am assuming that you would be doing it in salt water. The Wi-Fi thing is up in the air, since I read both that it has the hardware and it may have not. As for the Unlock thing with the watch, if you have Bluetooth unlock built into your phone then you can have the phone unlocked when the phones connect. If it is not available in your phone then you can download apps on the playstore for that feature or wait for the new Lollipop update. I am currently using the Xperia Z3 with the SW3 and that feature was built into the phone's OS. It allowed me to set a distance for the bluetooth as well to keep my phone unlocked up to a distance even if I am still connected to the phone.
Correction: On the WiFi the watch has the feature but it has not been enabled yet until a new update for Android Wear comes out that will utilize that feature.
I would guess that salt water is a no no.
The is an NFC "tag" in the upper region of the screen. If the phone is already unlocked, it opens the Android Wear app. I have it set up with lollipop's smart unlock, so that it can unlock the phone when tapped. Unfortunately, it's nearly impossible to hit with my Nexus 5. Too inconsistent for daily use, otherwise I'd have forget my pattern by now!
nobunnysapro said:
I would guess that salt water is a no no.
Click to expand...
Click to collapse
Why would swimming in salt water be prohibitive? Is it because salt water is more corrosive than fresh water? I've been snorkeling with my Seiko 5 Automatic with no issues for a long time now, even though it's only rated water resistant to 10'.
Hello, i only have my smart phone (my first one ever) since yesterday.
Managed to set some things up but i can already tell these devices consume a lot of time to do be set up and working right.
One of the first things i did was upgrade it to the latest Android version (7).
Today i took it to the pool to test it's water resistance - it is water resistant, that's the good news, but the bad news is that every time i held the phone under water it would stop recording the video after just a few seconds being submerged, and this with both, front and rear camera - it always showed some note saying something like "in this mode it can not zoom in and zoom out"!! Huh, i did not try to zoom in or out at all and have no clue why it would do this, anyone having an idea??
Next problem ... yesterday (with the original Android version it came with still on) i could connected the USB cord to the laptop and get my pictures out of the device .. today every attempt (except 1) gave me a Windows error message saying something like Windows can not recognize this USB device!! I tried everything, plug te cord into the USB2 port instead of the USB 3 port, same problem, i rebooted te laptop, same problem, i rebooted the phone several times same problem, what on earth is this and how can i fix it??
Hello, are you sure you have the android 7.0? Thanks
You should do factory reset, its highly recommended after android upradge. Be sure to back up everything important, as it will erase internal storage.
7.0 !!!
Rudme said:
Today i took it to the pool to test it's water resistance - it is water resistant, that's the good news, but the bad news is that every time i held the phone under water it would stop recording the video after just a few seconds being submerged, and this with both, front and rear camera - it always showed some note saying something like "in this mode it can not zoom in and zoom out"!! Huh, i did not try to zoom in or out at all and have no clue why it would do this, anyone having an idea??
Next problem ... yesterday (with the original Android version it came with still on) i could connected the USB cord to the laptop and get my pictures out of the device .. today every attempt (except 1) gave me a Windows error message saying something like Windows can not recognize this USB device!!
Click to expand...
Click to collapse
The phone being water resistant as far as I understand does not mean that it can operate normally under water. It means that being submerged in water (hopefully) will not destroy it. Your particular problem might have to do with the touch screen. Capacitive touch screens can wrongly detect humidity as touch - even if you use them with wet hands. So maybe the display just detects user input while under water?
For the other issue I am afraid I cannot help. Windows can have the most bizarre USB issues. Just make sure that if you ever you did submerge your phone, you do not plug it to the PC (or anything else) before you are absolutely 100% positive that there is no residual humidity in the USB port.
nurunet said:
The phone being water resistant as far as I understand does not mean that it can operate normally under water. It means that being submerged in water (hopefully) will not destroy it. Your particular problem might have to do with the touch screen. Capacitive touch screens can wrongly detect humidity as touch - even if you use them with wet hands. So maybe the display just detects user input while under water?
For the other issue I am afraid I cannot help. Windows can have the most bizarre USB issues. Just make sure that if you ever you did submerge your phone, you do not plug it to the PC (or anything else) before you are absolutely 100% positive that there is no residual humidity in the USB port.
Click to expand...
Click to collapse
Thanks for the useful reply, i can actually by now answer the issue with Windows not recognizing the USB port of the smart phone, and hopefully this will help others that i have noticed have come across this same issue in great numbers .... I noticed first that also quick charging only did slow charging, using the same port as needed to connect the device to a pc (USB port) than i also noticed that the speakers had no sound .... so i dawned on me ... there is HUMIDITY from the lengthy under water testing in these two "cavities"!! I mean, no water went into the device as such, but some humidity remained in there even though the rest of the phone was completely dried up and everything else was working just fine. Did what i learned online somewhere ... blow it out with the mouth as good as possible and than drop it into a bowl of rice (the rice sucks up moisture like a sponge or even greater). After an hour or so the USB worked just fine again, sound was not yet back in the speaker only in the headset, but after another 'rice hour" also that came back to live!!
Now i only have to find out if under water video taking is simply impossible .. but than again, i saw plenty of such under water videos taken by people in pools, so it should actually be possible, just how??
Yes, touch functions do not react well anymore when the hands are completely wet and this is something don't get, for photos we can use the volume rocker, but for videos not, but it would make a lot of sense to have the option as well for video when the device or the hands are very wet.
Rudme said:
Thanks for the useful reply, i can actually by now answer the issue with Windows not recognizing the USB port of the smart phone, and hopefully this will help others that i have noticed have come across this same issue in great numbers .... I noticed first that also quick charging only did slow charging, using the same port as needed to connect the device to a pc (USB port) than i also noticed that the speakers had no sound .... so i dawned on me ... there is HUMIDITY from the lengthy under water testing in these two "cavities"!! I mean, no water went into the device as such, but some humidity remained in there even though the rest of the phone was completely dried up and everything else was working just fine. Did what i learned online somewhere ... blow it out with the mouth as good as possible and than drop it into a bowl of rice (the rice sucks up moisture like a sponge or even greater). After an hour or so the USB worked just fine again, sound was not yet back in the speaker only in the headset, but after another 'rice hour" also that came back to live!!
Click to expand...
Click to collapse
I am not an expert, but to me it seems you were lucky the use of the USB connector containing residual water did not damage the phone (or perhaps even the PC). No matter how waterproof the device itself is, due to the open design of our devices' ports, water can collect in them. If you plug a USB cable or headphones, a current will flow. Water in a connection like that can cause a short-circuit. For that reason my old Xperia had little port-doors that sealed the USB port. Unfortunately, those are prone to break off - and simply a pain in the back side to open and close for every charge.
My A5 got wet once, and there even was a message along the lines of "Moisture detected. Please do not plug anything until 100% dry again." And I think that advice should be heeded.
Nope, it still says 6.0.1
Pandotaz said:
Hello, are you sure you have the android 7.0? Thanks
You should do factory reset, its highly recommended after android upradge. Be sure to back up everything important, as it will erase internal storage.
Click to expand...
Click to collapse
Hmm, i thought the update (pretty heavy one) was to Nougat and not just an updated version of Marshmallow .... bummer
I find it absolutely crazy that you tested your device by submerging it in water for an extended length of time.
Water resistant does not mean waterproof.
I highly doubt that Samsung actually intend the phone to be used under water. Moreover it's protection against accidently dropping the device in to water and gives a level of protection where the device won't be instantly ruined.
They don't make specific underwater cameras for nothing.
Secondly the error regarding the malfunction isn't surprising either. The focusing system probably isnt designed to cope with the refraction effect of the water.
It may work in fixed mode, I don't know. However I don't think it's actually intended to be used that way.
Let alone the damaging effect of electrolysis by passing a current through a water soiled port.
Fixed mode??
ashyx said:
I find it absolutely crazy that you tested your device by submerging it in water for an extended length of time.
Water resistant does not mean waterproof.
I highly doubt that Samsung actually intend the phone to be used under water. Moreover it's protection against accidently dropping the device in to water and gives a level of protection where the device won't be instantly ruined.
They don't make specific underwater cameras for nothing.
Secondly the error regarding the malfunction isn't surprising either. The focusing system probably isnt designed to cope with the refraction effect of the water.
It may work in fixed mode, I don't know. However I don't think it's actually intended to be used that way.
Let alone the damaging effect of electrolysis by passing a current through a water soiled port.
Click to expand...
Click to collapse
Thanks for your answer ashyx.
I did not submerge the Samsung Galaxy A7 (2017) without due prior research!
Meaning .... if you check on Youtube for under water videos taken with this particular smart phone you find a bunch that all seemed to have great fun with it for extended periods of time in the pool, so i assumed if it works for them it should also work for me .... but, of course, your point was also of concern to me, none of these videos tell me what happened to their phones afterwards etc.
On mine the headset, for instance, still works for sound, but the volume and mute buttons on the headset are currently no longer reacting and the speaker is off and on still .... on the other hand, the water resistance clearly points out "can be submerged in water for up to 30 minutes and i am not sure if it says a debt of 1.50 or only 0.5 meters, and i never put it further down than maybe 10 or 20 cm's and for less than 5 minutes each time, so, it this IP68 or whatever it is called is of any real life truth and value the device should have zero problems with being under water for a video of 2 minutes at 15 cm or so dept.
Your thought of the water interfering with the focus metering i can agree with, was also my thought, but in all the YouTube videos i did not see this type of problem , so i am not sure if this was a case that these people all new how to set the camera into some FIXED MODE - can you please let me know how to do this, i did not find any settings for this???
Won't the message about moisture warning appear not allowing you to charge?
It will - but will you see it??
Pandotaz said:
Won't the message about moisture warning appear not allowing you to charge?
Click to expand...
Click to collapse
Absolutely Pandotaz, but this message appears on the login screen and i have no login pwd or the like established, so it disappears quickly .. not to mention the small and hard to read print, in other words, easy to over look, exactly what happened to me, but that's what happens to not-so-smart- smart phone beginners who are already a bit older than average :crying:
At this point i would like to repeat my question in last reply, how do i set a smart phone camera to "FIXED MODE " anyone??
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 had this phone since September and came from Huawei P30 Pro, before that Honor V10, Huawei P20 which had fast fingerprint sensor and worked 99% of the time first time .
I cannot believe how bad this sensor is in real use, unlock success rate is about 5% no matter how many times I delete and Reregistered all fingers.
I scan my prints and test in the setup and they are acknowledged correctly but once I start using for real to unlock the phone or approve stuff it rarely works.
I have tried all kinds of angles and strengths of press but it's useless.
Running the beta in hope of improvement but it's still useless.
Did I get a bad unit here or is Samsung just totally crap with fingerprint sensors?
Sent from my SM-N975F using Tapatalk
After you've registered your fingerprints.... re-register them to improve the accuracy of the scanner. Also, if you find it sluggish, reduce the animations in the settings...
Sent from my [device_name] using XDA-Developers Legacy app
I am reregistering prints to try and improve and after every update hoping something is better.
As said when setting up and checking it is fine but when I have to use for example with 2FA app to approve a log in it just fails "fingerprint not recognised" before eventually going to pin.
Will try the animation setting and see if that helps.
Sent from my SM-N975F using Tapatalk
for a while, the Note10+ fingerprint reader had a terrible success rate, no matter what "hacks" i used to try to make it better (i.e. multiple fingers, the "test/learning" hack, etc.) — loads of "make sure you cover the entire sensor" and "no match found" etc.
this tip might be crazy, but it does work: MOISTURIZE LIGHTLY.
100% serious.
my right thumb was not able to unlock my Note while i was working at my desk. super frustrating. looked at my hands, thought they were looking dry, so i put a dab of glycerin hand cream on and BANG: every single damn time now, regardless of whether my thumb is vertical or sideways.
I got my Note 10+ today and have spend a long time setting it up. Once I registered my prints I had not issues (unless I didn't press firmly enough on the screen). It's been fine for me thus far.
You shouldn't compare ultrasonic fingerprint sensors that are in their early stages with optical ones that have been out there for years. Ultrasonic is much more secure. And saying that success rate is only 5% means that you either have a defective unit or need to change the way you use it. I have a success rare of no less that 90%... not as accurate and quick as my old note 8 with its optical sensor but I got used to it
I've had no issues with the fingerprint sensor, before or after the update.
AM Radio said:
for a while, the Note10+ fingerprint reader had a terrible success rate, no matter what "hacks" i used to try to make it better (i.e. multiple fingers, the "test/learning" hack, etc.) — loads of "make sure you cover the entire sensor" and "no match found" etc.
this tip might be crazy, but it does work: MOISTURIZE LIGHTLY.
100% serious.
my right thumb was not able to unlock my Note while i was working at my desk. super frustrating. looked at my hands, thought they were looking dry, so i put a dab of glycerin hand cream on and BANG: every single damn time now, regardless of whether my thumb is vertical or sideways.
Click to expand...
Click to collapse
heh yeah classic S10+ fingerprint reader from Samsung. I also found the same "you need to lick your finger first. Yeah, it's not a joke. " :laugh:
yep lick your finger first does actually work, if you have dry hands the scanner is mostly trash, use moisturiser/lick/damp your finger and it will work near 100% reliability. basically if you don't have clammy hands it will likely be hit and miss.
actually found myself in bars using the condensation on my drinks to help me unlock the phone, it seems an odd thing but it seems moisture in your skin is a massive deciding factor on it working.