Incoming calls issue after Tizen 4 (different from the others) - Samsung Gear S3

Hi, after the 4.0 tizen update I am encountering an issue not described in other threads (at least I hope so). Apart from altitude calibration and contact sync issues and so on, my watch SOMETIMES do not vibrate on incoming calls. I can see the caller on the watch display, I can answer or reject the call by the watch but the watch just do not vibrate. It is really annoying. I have missed many calls since this issue appeared. I have endured several watch hard resets, each one brought a new issue. I have cleared caches of galaxy Wearable and Contacts apps on the phone. The only thing I have not made so far is phone hard reset. I refuse to make it until I am sure that anything else would not help. But I believe this issue is connected with Galaxy Wearable update to version 2.2.23.19021251 which took place on Tuesday 19th February I think. I was making another watch hard reset so I cannot tell if the cause is the watch hard reset or the application update. Even if one contact calls me more times, it happens that one call - watch do not vibrate (I missed the call), then the same contact calls me repeteadly, the watch do vibrate (and I answer the call). Any ideas? Do you think Samsung is working on any updates that would solve the myriads of Tizen 4 issues described here and everywhere else?
Thanks for any ideas.
Lubos
(Galaxy S7 Edge and Gear S3 classic)

Related

No longer receive notifications

Hey guys hope some one can help.
So new gear s2 for Xmas worked brilliantly at 1st received notifications no problem as of Monday iv stopped receiving them. Do receive txt messages but not what's app. Google weather all the old 1s I did receive. Iv got a samsung s6 edge all updated. Iv factory reset the watch still nothing. Don't want to send it back love it.
Cheers guys.
Hi,
can't help to solve your problem but got the exact same problem.
Receiving notifications once after soft reset and then never again - except incoming calls. Checked all settings - notifications are enabled in the gear app and the watch itself is also NOT set to "dont disturb". Very annoying! Can anyone help?
Cheers Thomas
Hello,
I have the same problem.
I used a Gear 2 before with my Galaxy S6 and that worked fine.
When I started using my S2 I did receive a Whatsapp notification on my watch but then it got an update via Gear Manager, it rebooted and now I get no notifications other then SMS, phone and standard mail. No FB, Google, Messenger, Whatsapp ect.
All my settings in Gear Manger are the same as I used with the Gear 2.
Samsung Gear 2.2.15111841
Gear Plugin 2.2.03.15111841
Gear manager, latest version.
Thanks. Toon
toonsol said:
Hello,
I have the same problem.
I used a Gear 2 before with my Galaxy S6 and that worked fine.
When I started using my S2 I did receive a Whatsapp notification on my watch but then it got an update via Gear Manager, it rebooted and now I get no notifications other then SMS, phone and standard mail. No FB, Google, Messenger, Whatsapp ect.
All my settings in Gear Manger are the same as I used with the Gear 2.
Samsung Gear 2.2.15111841
Gear Plugin 2.2.03.15111841
Gear manager, latest version.
Thanks. Toon
Click to expand...
Click to collapse
My Gear S2 Classic started missing notifications yesterday. Re-booted the watch (hold Home button to turn off, then same to turn on). Notifications working fine now!
My problem was that the setting in the Gear App, under Notifications got turned Off!!!
Once I turned that back on, I started getting everything.
Rob
Hello again,
I found a solution for my problem. I had tried rebooting before but that didn't help. After digging a bit on this forum I tried the following:
Deleted watch on phone in BT settings.
Rebooted phone.
Added watch again by just using BT settings (not via Gear manager).
Watch connected and all worked as it should.
I hope this works for somebody else as well.
Toon
Hi,
found my problem from this thread: http://forum.xda-developers.com/showthread.php?t=3285032: the watch needs to be "worn" in order to show notifications.
In my case the problem was the NATO strap I bought as an replacement for the leather strap. The new strap covered the backside of the watch (I do not use the pulse sensor anyway) which lead to the watch thinking that it was not worn - it seems to need contact with the skin on the backside in order to consider to be worn.
So I replaced it with an two-part strap and now notifications are received again. Weird that this is not mentioned by Samsung (I did not find it at least).
Cheers,
Thomas
Hi!
After the last update my Gear S2 Clasic no longer receive lost call notofications and the other ones enaled received with huge delay, my gear is connected to a Galaxy S5, I don't know what to do, maybe it's a bug ?! Any idea ?
Saw this thread and thought I would post my experience.
Received watch and worked well with all notifications that should be received being received. I was charging the watch and figured I would shut it down as well during charging. After boot up it no longer received notifications. I tried a bunch of stuff including restarting the watch, restarting my phone, changing notification settings and finally doing a soft reset requiring me to unpair and re-pair Bluetooth through the Samsung app. All of this was done with me wearing the watch and nothing worked.
I stumbled upon the thread above saying notifications weren't being received when the watch isn't being worn. So I tried taking it off and putting it back on but no luck. Finally, I took it off, turned it off, turned it back on with it still not being on my wrist and finally after waiting 5 minutes or so of it being on, I put it back on my wrist and voila, notifications!
So, my best guess is that when I started up the watch with it being on my wrist the watch believed it wasn't being worn and since I never took it off that never changed. Or maybe it just decided to work after the last reset but from now on, if I shut it down, I will boot it back up when it is not being worn and then put it on after a little time.
I like the watch a lot but it is a bit finicky.
Thank you so much!!! This fixed my problem! I've been looking for weeks now and nothing worked! I'm always wearing it when I turn it on so that must mess with it. Thanks so much for your post!
---------- Post added at 09:00 PM ---------- Previous post was at 08:54 PM ----------
toonsol said:
Hello again,
I found a solution for my problem. I had tried rebooting before but that didn't help. After digging a bit on this forum I tried the following:
Deleted watch on phone in BT settings.
Rebooted phone.
Added watch again by just using BT settings (not via Gear manager).
Watch connected and all worked as it should.
I hope this works for somebody else as well.
Toon
Click to expand...
Click to collapse
Thank you so much!!! This fixed my problem! I've been looking for weeks now and nothing worked! I'm always wearing it when I turn it on so that must mess with it. Thanks so much for your post!

The watch takes all my calls since the Tizen 3 update

So I'm running a S7 Edge + Gear S3 Frontier (Wi-Fi) combo. I've never had a single issue up until I updated to Tizen 3 yesterday. Everything looks fancier and better and so far I really enjoy it. But there's that little thing that irritates the hell out of me. When I call someone or someone calls me, the Bluetooth icon in the Call app is turned on by defaut so everything goes through the mic and speaker of my watch. I have to specifically click it again to turn it off every single time I make a call. Sometimes I forget to do so and it turns out rather embarrassing.
This has always been the default behaviour with my car's bluetooth and I've been fine with that. But this happening with the smartwatch as well is absolutely irritating.
Is someone experiencing this issue as well and any ideas how to fix it?
gbuyukliev94 said:
So I'm running a S7 Edge + Gear S3 Frontier (Wi-Fi) combo. I've never had a single issue up until I updated to Tizen 3 yesterday. Everything looks fancier and better and so far I really enjoy it. But there's that little thing that irritates the hell out of me. When I call someone or someone calls me, the Bluetooth icon in the Call app is turned on by defaut so everything goes through the mic and speaker of my watch. I have to specifically click it again to turn it off every single time I make a call. Sometimes I forget to do so and it turns out rather embarrassing.
This has always been the default behaviour with my car's bluetooth and I've been fine with that. But this happening with the smartwatch as well is absolutely irritating.
Is someone experiencing this issue as well and any ideas how to fix it?
Click to expand...
Click to collapse
I have this issue
I made temporary solution .. from Bluetooth setting I unchecked phone call for gear s3
sobluedeep said:
I have this issue
I made temporary solution .. from Bluetooth setting I unchecked phone call for gear s3
Click to expand...
Click to collapse
Did the same thing yesterday. Definitly started after update.
Same here.
I've already tried everything possible (I think ) Would turning audio bluetooth off cut the watch from the phone? Audio is my only option in bluetooth settings... I'm using Gear S3 classic along with Samsung Galaxy Note 4.
gbuyukliev94 said:
So I'm running a S7 Edge + Gear S3 Frontier (Wi-Fi) combo. I've never had a single issue up until I updated to Tizen 3 yesterday. Everything looks fancier and better and so far I really enjoy it. But there's that little thing that irritates the hell out of me. When I call someone or someone calls me, the Bluetooth icon in the Call app is turned on by defaut so everything goes through the mic and speaker of my watch. I have to specifically click it again to turn it off every single time I make a call. Sometimes I forget to do so and it turns out rather embarrassing.
This has always been the default behaviour with my car's bluetooth and I've been fine with that. But this happening with the smartwatch as well is absolutely irritating.
Is someone experiencing this issue as well and any ideas how to fix it?
Click to expand...
Click to collapse
had the same issue, but after factory reset on my gear s3 it was fixed, have a try ...
Have this exact issue. Factory Reset the watch with no change.
Also turning off calls under bluetooth settings on the phone disconnects the watch from the phone thus this is not an option.
Gear S3 Classic paired to an Galaxy S10+

No vibrate on gmail notifications since Oreo

I have just upgraded to a phone with Android 8.0 Oreo. I factory reset my Gear S3 and connected to the new phone.
Since then, I can't get vibrations on gmail notifications of incoming mail. Other apps (eg SMS texting) vibrate ok.
This is frustrating, as without vibrations, the whole point of having a smartwatch is largely gone.
Am on Tizen 3.0.0.1
Does anyone know of a fix or work-around? Is it likely to be fixed in a future release?
Thanks
same here... After reset of Gear S3 and Honor 9 I'm quite sure it's depending on Oreo. Curious for solutions!

Sound problem during a call

Hello,
I have a fairly recurrent problem with my watch and I can't find solutions. I have a gear s3 coupled to an asus zenfone 3.
If the watch is connected to the phone, when I make a call it often happens (we will say 2 times out of 3 anyway) that the other party does not hear me. I try to call back several times without success. If he reminds me, it works. And if I ever disconnect the watch, it works.
The phone is of course in combined mode (and not Bluetooth) when calling.
Does this happen to you and do you have any solutions?
Thank you in advance,

Question Calls default to phone instead of watch

Does anyone else have this problem? I just got the Galaxy 4 smart watch (bluetooth, not lte version) a few days ago. When I initiate a call from the watch it dial and says "See phone" and the call is now coming through the phone. I can click a button on the phone to send the call back to the watch but obviously this defeats the convenience of not needing to have the phone in arms reach.
My husband figured out that its some kind of interference with other connected bluetooth devices (even though they are off), like my car and handsfree earpiece. If I unpair each of those items, calls work as they should. As soon as I re-pair another bluetooth device the problem resurfaces. I'd rather not have to pick one or the other to work if I can help it. Samsung support hasn't been able to fix it. Any ideas?
I should have clarified, I'm wondering both who does and who doesn't have this issue. Please comment even if yours works perfectly.
Samsung support seemed to suggest it was a software issue thar might be able to be fixed in a future update but I'm not sure if its an issue for anyone other than me.
Maybe you should take a look at this topic https://forum.xda-developers.com/t/...hange-default-behavior.4369423/#post-86031957

Categories

Resources