It's not working on mine - is this feature removed on GW4?
Just checked my watch 4 LTE 44mm and it goes dark when placing Palm on it for some second's...
I guess mine has a faulty sensor. Old Gear S3 worked fine with palm turning off the screen. Not a very big deal though...
galaxys said:
Just checked my watch 4 LTE 44mm and it goes dark when placing Palm on it for some second's...
Click to expand...
Click to collapse
Like, how many seconds? 15...?
LarasLTU said:
I guess mine has a faulty sensor. Old Gear S3 worked fine with palm turning off the screen. Not a very big deal though...
Click to expand...
Click to collapse
You're not alone - it doesn't work on mine either. I concluded that Samsung removed it/it's not a Wear OS feature, as it wasn't in the setup tutorial, and there's no setting for it. Although I have seen others like galaxys claim that it works, I'm not convinced...
jtOttawa said:
Like, how many seconds? 15...?
Click to expand...
Click to collapse
Depends if you're in a hurry or not
Works on mine, too. The obvious questions are:
A. Is your always on display setting activated?
B. If yes, does your watch face have a dimmed view?
If a is yes and b is no, then placing the palm on the watch won't cause a change even if the sensor works. I had that issue for a while with a watch maker face that didn't have a dimmed view.
tinuthir said:
Works on mine, too. The obvious questions are:
A. Is your always on display setting activated?
B. If yes, does your watch face have a dimmed view?
If a is yes and b is no, then placing the palm on the watch won't cause a change even if the sensor works. I had that issue for a while with a watch maker face that didn't have a dimmed view.
Click to expand...
Click to collapse
What if a is no and b is sorta, as auto brightness is on? *Edit*: Just checked with auto brightness off, still doesn't work. Are you sure your screen isn't just timing out as you try this?
If a is no, then b is irrelevant. If AOD is off, then the palm gesture should turn off the screen, period. The fact that the screen goes a bit darker proves that the ambient light sensor works, sure, but I'm unsure if that's the only sensor that determines whether the palm was placed on the watch. Might be multiple sensors?
Just saw your edit. I will test it.
Edit 2 after testing: my screen timeout is 15 seconds - the palm gesture is maybe 1 second. So that's not it.
tinuthir said:
If a is no, then b is irrelevant. If AOD is off, then the palm gesture should turn off the screen, period. The fact that the screen goes a bit darker proves that the ambient light sensor works, sure, but I'm unsure if that's the only sensor that determines whether the palm was placed on the watch. Might be multiple sensors?
Just saw your edit. I will test it.
Edit 2 after testing: my screen timeout is 15 seconds - the palm gesture is maybe 1 second. So that's not it.
Click to expand...
Click to collapse
Interesting. Thought maybe it might be related to using AOD, but nope, doesn't work either. Your's the regular Watch 4 or the Classic?
I use this feature a lot it works perfectly on my gw4
For me it works in both the cases aod on and off... Difference being with aod on it dims the screen and with aod off it completely blacks out the screen
It also silences the call and stops the vibration when a call is received
jtOttawa said:
Interesting. Thought maybe it might be related to using AOD, but nope, doesn't work either. Your's the regular Watch 4 or the Classic?
Click to expand...
Click to collapse
Classic.
I found in manual, that it should be working: https://downloadcenter.samsung.com/...210722/lock_or_unlock_your_device_d1e772.html
Not sure if watch reset could help, also potentially could be fixed with next firmware upgrades, unless there is faulty sensor
LarasLTU said:
I found in manual, that it should be working: https://downloadcenter.samsung.com/...210722/lock_or_unlock_your_device_d1e772.html
Not sure if watch reset could help, also potentially could be fixed with next firmware upgrades, unless there is faulty sensor
Click to expand...
Click to collapse
Reset didn't do anything - other than show me how poor the backup is on the watch, and force me to install SHM Mod again... I doubt it's a faulty sensor (as everything else, i.e., auto brightness, works fine) - maybe my palms are too translucent?
Works on mine when bought new and then now. In between I had issues. After buying the watch I tested everything. Then about two days after my screen protector order arrived. PLaced it on the watch and I thought all was good. Eventually this topic came up in another forum and I checked mine. It wasn't working. Whatever I did it just seems that the palm to screen off wasn't working as it should. So I did a reset, etc. Still not working. I thought, who cares? It's not really a feature I use everyday anyway but somehow for me that means there was an issue. Then as I was looking at the screen I realized there were some lifts on the perimeter of the screen protector. I removed it. Then I tested the palm to screen off. Not once did it NOT work. I let it go without a protector for a day or so and it was still working. Since then I didn't use the tempered glass protector anymore. I bought one of those film type protectors and now the palm to screen off is working.
Thanks @thephantom for the hint! Apparently it's working on mine as well, I just needed to put my palm much closer to the watch screen (in comparison to my Gear S3 where it was enough to put palm over the watch and not touch it at all), I'm pretty sure it should work for others too on GSW4, once you press your palm against the watch (touching the bezel with your palm with light pressure ) - it was just wrong expectation on my side from the other model...
LarasLTU said:
Thanks @thephantom for the hint! Apparently it's working on mine as well, I just needed to put my palm much closer to the watch screen (in comparison to my Gear S3 where it was enough to put palm over the watch and not touch it at all), I'm pretty sure it should work for others too on GSW4, once you press your palm against the watch (touching the bezel with your palm with light pressure ) - it was just wrong expectation on my side from the other model...
Click to expand...
Click to collapse
Well, I'll be damned - that does work. In fact, using the ball of your thumb seems to work well, and every time.
Related
I had to finally shut this option off. My watch kept coming on all of the time. My 360 is much better, normally only coming on when I lift my watch to look at it. Does anyone else have this problem, or is it just a problem with the one I have?
I find it works well. I often couldn't get my 360 to turn on with a basic wrist raise.
Sent from one of my many devices.
Mine will turn on just laying my arm on my lap. I have the Classic coming. Maybe it is just the one that I currently have. But there was one reviewer on Amazon that complained of the same thing.
Mine turns on too easily, too. Lay my arm on my thigh while laying horizontal on couch will make it come on every few seconds. Also sitting with my arm on chair arm.
My classic is fine. Only turns on when I lift it to check the time.
my non-classic works fine, only turns on when I lift my arm
My classic works extremely well for this. I love how if you tilt the watch away it auto turns off and for me really only turns on when I raise my wrist to view it. It very rarely turns on unexpectedly! I am coming from an LG G Watch R and it was not nearly this good.
bullet2300 said:
My classic works extremely well for this. I love how if you tilt the watch away it auto turns off and for me really only turns on when I raise my wrist to view it. It very rarely turns on unexpectedly! I am coming from an LG G Watch R and it was not nearly this good.
Click to expand...
Click to collapse
I've had the exact same experience with mine. Loving it so far!
hi
I have the gear s2 classic I was just wondering if using the always on feature with a digital face burn the screen ?
no one?
I think if it's as much of a concern for you, just disable it as I did. AMOLED screens from my prior understanding are prone to burn-in that's why with devices such as the S7 and S7 edge that have an always on interface they move the display around every so often to prevent burn in. I had an always on watch face enabled for my gear S2, however, i watched it for a little bit (really small amount of time) and didnt see it change anything so I thought why risk it and just disabled it. There's really nothing I need to see on the watch itself [ever] real-time so simply moving my hand up to enable the display was not a huge deal for me, and saving the display from possible burn in was worth not having the always on display. Just my 2 cents.
batteriesNI said:
hi
I have the gear s2 classic I was just wondering if using the always on feature with a digital face burn the screen ?
Click to expand...
Click to collapse
When in ambient mode the watch face moves around by several pixels every minute or so to make sure there isn't burn in.
However if you have an app to keep the full power watch face on, then you may have burn in issues. It is an AMOLED screen.
Rob
rlichtefeld said:
When in ambient mode the watch face moves around by several pixels every minute or so to make sure there isn't burn in.
However if you have an app to keep the full power watch face on, then you may have burn in issues. It is an AMOLED screen.
Rob
Click to expand...
Click to collapse
ah I didn't know that, I just use the default digital face that dims when set to always on. after having several Samsung phones screen burn is an issue I had hoped it wouldn't be a issue with the watch
batteriesNI said:
ah I didn't know that, I just use the default digital face that dims when set to always on. after having several Samsung phones screen burn is an issue I had hoped it wouldn't be a issue with the watch
Click to expand...
Click to collapse
The "dimmed" watch face that is all white/grey with fewer elements, is the ambient mode watch face. So, you should be good to go with that feature enabled. This is what I have enabled.
However, there are some users that want the full watch face on all the time. There are apps/ways out there to do it. That is what could cause burn in.
Rob
The dimmer the screen is the less chance of burn in.
Sent from my SM-G935T using Tapatalk
ah so it will still burn? I like the thought of using always on but it's a expensive watch to ruin
has anyone that's using always on with a dimmed face noticed burn in?
Has anybody got an issue with their proximity sensor? Mine seems to be misbehaving randomly after the 8.1.0 update. Last day the phone was stuck after a call and had to reboot. Is this a known issue? Are there any fixes yet?
Nope, no issues here. Please describe when and how your sensor is not working properly?
PuffDaddy_d said:
Nope, no issues here. Please describe when and how your sensor is not working properly?
Click to expand...
Click to collapse
It just doesn't work. The screen mostly doesn't turn off and when it does it doesn't turn back on.
JosephECorson said:
It just doesn't work. The screen mostly doesn't turn off and when it does it doesn't turn back on.
Click to expand...
Click to collapse
You mean while on a phone call with the phone pressed to your ear?
Do you have a screen protector?
JosephECorson said:
Has anybody got an issue with their proximity sensor? Mine seems to be misbehaving randomly after the 8.1.0 update. Last day the phone was stuck after a call and had to reboot. Is this a known issue? Are there any fixes yet?
Click to expand...
Click to collapse
So I had this problem. I tried all the solutions I could from the Google Forums and the Google Pixel 2 help support themselves. I discovered that the 8.1 update broke the proximity sensor. So I just received my replacement. Some people "claim" that taking off the screen protector works, but I was skeptical because the phone worked with the screen protector on when I was running 8.0 (Moreover, as I transferred the SAME screen protector onto my replacement running 8.1, the replacement works to perfection. I also played around with my previous Pixel 2 XL after resetting the phone and the proximity still does not work, even without the screen protector). You can go to the Google forum (under the calls link, because my assumption is that calling on any app on your phone just leaves you with a black screen) and test out all possible solutions. If none work, just call Google and explain the problem and ask for a replacement :good:. Hope this helps, man.
PuffDaddy_d said:
You mean while on a phone call with the phone pressed to your ear?
Click to expand...
Click to collapse
ya
DatGuy_Shawnaaaay said:
So I had this problem. I tried all the solutions I could from the Google Forums and the Google Pixel 2 help support themselves. I discovered that the 8.1 update broke the proximity sensor. So I just received my replacement. Some people "claim" that taking off the screen protector works, but I was skeptical because the phone worked with the screen protector on when I was running 8.0 (Moreover, as I transferred the SAME screen protector onto my replacement running 8.1, the replacement works to perfection. I also played around with my previous Pixel 2 XL after resetting the phone and the proximity still does not work, even without the screen protector). You can go to the Google forum (under the calls link, because my assumption is that calling on any app on your phone just leaves you with a black screen) and test out all possible solutions. If none work, just call Google and explain the problem and ask for a replacement :good:. Hope this helps, man.
Click to expand...
Click to collapse
Thanks, man! I know the issue is not the screen protector even though they claim so.
Okay, this is what you need to do. Buy airduster and nicely blow air over the top speaker. Not sure this phone is dust proof. There seems a small gap between the lower edge of the speaker grill and phone screen. You can test by yourself, take a paper the edge of paper goes for a mm or so. Use air duster few times and your proximity sensor works. I think it's not software problems, seems this pixel 2 xl has serious quality control. Google needs to recall this phone!!
Sounds logical, because I can turn my screen on and off by bringing a metallic pen near the sensor and away from it, so if you get metal particles in that little "slot" by the speaker, they'd probably affect the sensor. (Especially if they were magnetized - and a lot of seemingly "where id it come from" dust is actually from construction projects. [We used to rent two way radios to construction companies, and they came in about once a week with "dead" speakers - it was tiny steel particles loading the speaker up to the point that the cone couldn't move - and they traced a sample back to a particular steel beam - that the phone had been near when some rivet holes were drilled in it.]) So keep the phones away from cities that have hi-rise construction projects in progress. (This phone is designed for use on a different planet - using a USB 3.0 port and a USB 3.0 cable to flash a ROM bricks the phone. I'm surprised that it's not allergic to air too.)
I can make the sensor revert back to far from near by pressing gently the top bezel next to lateral edge of the speaker grill on left side. Sensor reverts back to far from near. Don't know the mechanism and definately doesn't look like software issue.
June security update has just fixed this for me
All - My S3 got wet and went into a bootloop. I sent it to Samsung and they sent it back without fixing it claiming that it was too expensive to fix. It is up to me to fix it myself.
I managed to resolve the bootloop problem by opening it up and letting it air out. (see other thread for details)
Question - the only problem I have now is that when I rotate the bezel, it doesn't register anything on the watch. The connector/ sensor seems to be dead.
Anyone know how I could fix this? Do I need a new entire display unit (Samsung Gear S3 frontier (SM-R760) Display unit complete grey GH97-19658A) or is there something else I should try? A part to replace?
I did take off the bezel and I cleaned it. (did it very carefully as there are pieces that can be easily lost)
The watch works well and I can do almost everything without the bezel working but would like to get it working to 100%.
Thanks for any ideas people may have.
Same problem
same problem on my Galaxy Watch. Any update on how to fix?
redbeard07 said:
same problem on my Galaxy Watch. Any update on how to fix?
Click to expand...
Click to collapse
I took mine apart again hoping I could get the bezel to work but no luck.
I assume the sensor connects to the top part of the watch. There are two connecters that attach to the main part of the watch, a big one and a much smaller one. Perhaps the smaller connector is the problem.
Not a super big deal but I would love to get my watch working at 100%.
Any Samsung techs with an idea?
I figured out that my problem was just that I was wearing a watch band with a magnetic clasp. If the magnet was too close to the watch, but bezel wouldn't work. If I switched bands everything was fine.
redbeard07 said:
I figured out that my problem was just that I was wearing a watch band with a magnetic clasp. If the magnet was too close to the watch, but bezel wouldn't work. If I switched bands everything was fine.
Click to expand...
Click to collapse
You sneaky son of a gun. That worked.
For what it's worth: the bezel sensor is a set of 3 hall effect sensors. If you take the bezel ring off the watch (various youtube guides show how) and look at the underside, you'll see 24 indents and 8 of these (1 in 3) will be a different color. If your watch isn't registering anything, these magnetic spots may be de-magnetized.
https://www.ifixit.com/Teardown/Samsung+Galaxy+Watch+Teardown/117519 <-- explained here (see step 15 ... and if you look closely at the bottom right of step 8 first picture you can see the 3 hall effect sensors in place)
On my watch it sometimes didn't register the bezel turning. I thought it might just be gummed up. I eventually noticed that it would miss 3 "clicks" in every rotation.
Now I finally understand why: one (only one of eight magnets) has become de-magnetized and the hall effect sensor won't read it as it passes across.
Now I just need to work out how to re-magnetize the one spot.
V
Hi
I've been trawling through the forums for a couple days now to see if anyone has come up with a solution to, or a reason why Samsung doesn't leave the proximity sensor on while the always on display is active anymore (since the Note S10).
I know the sensor has been moved behind the screen. But it seems to function in the same way it used to. It still blanks the screen during a call, if I hold something over it up to about 20mm away. Just not with the always on display.
I'm currently using aodNotify as a sort of workaround. But would much prefer if the always on display just worked like every other damn phone!
Does anyone know the reason why Samsung has disabled this? Uses too much power? I Don't know.
rancid990 said:
Hi
I've been trawling through the forums for a couple days now to see if anyone has come up with a solution to, or a reason why Samsung doesn't leave the proximity sensor on while the always on display is active anymore (since the Note S10).
I know the sensor has been moved behind the screen. But it seems to function in the same way it used to. It still blanks the screen during a call, if I hold something over it up to about 20mm away. Just not with the always on display.
I'm currently using aodNotify as a sort of workaround. But would much prefer if the always on display just worked like every other damn phone!
Does anyone know the reason why Samsung has disabled this? Uses too much power? I Don't know.
Click to expand...
Click to collapse
Working in what way ? Mine works as in, it gets brighter or dimmer according to the light around me.....or are you wanting/expecting AOD to turn off when the screen is covered ?
seczdbz said:
Working in what way ? Mine works as in, it gets brighter or dimmer according to the light around me.....or are you wanting/expecting AOD to turn off when the screen is covered ?
Click to expand...
Click to collapse
Exactly, the former of what you said is all it* does when AOD is active.
In any case this is now normal operation possibly done to help save battery.
*I'm not sure that the proximity sensor is the ambient light detector?
I think what the OP is saying is that for example if you cover the screen whilst the AOD is on, it used to turn the AOD off before. It no longer does this.
Behavior started with the S10 series.
Limeybastard said:
I think what the OP is saying is that for example if you cover the screen whilst the AOD is on, it used to turn the AOD off before. It no longer does this.
Behavior started with the S10 series.
Click to expand...
Click to collapse
So if you had it in your pocket it use less battery?
Interesting.
On most other phones, and Samsung's prior to the Note 10. If you put the phone face down, or placed it in your pocket, the always on display would turn off to save battery. They no longer do this.
I wonder if there's a work around for this somehow.
blackhawk said:
So if you had it in your pocket it use less battery?
Interesting.
Click to expand...
Click to collapse
Yep, or if you're posh and use a leather folio case .
(sticks pinky finger out while opening phone)
Limeybastard said:
Yep, or if you're posh and use a leather folio case .
Click to expand...
Click to collapse
Lmao
More heavy metal, you know... with the finger eating indestructible case