Related
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!
Is anybody having issues with Gear S3 classic disconnecting very frequently? Any fix for this? I'm using Galaxy S4 GOC1 (5.0.1) ROOTED Verizon.
Mine has never disconnected from my Moto G4. You say you're rooted, are you still using the stock rom?
Sent from my SM-T530NU using Tapatalk
eddyo1993 said:
Is anybody having issues with Gear S3 classic disconnecting very frequently? Any fix for this? I'm using Galaxy S4 GOC1 (5.0.1) ROOTED Verizon.
Click to expand...
Click to collapse
Same for me with Gear S2 on my Galaxy S4 Android 5.0.1 rooted not frequently but happen too often for me
Seem bad/old BT on S4 ?
Most of time the S2 do not reconnect automatically. I'm trying workaround to reconnect auto..... (trigger app)
Tel864 said:
Mine has never disconnected from my Moto G4. You say you're rooted, are you still using the stock rom?
Sent from my SM-T530NU using Tapatalk
Click to expand...
Click to collapse
Yes I am currently running the stock rom. Its modified a little bit to keep the KK bootloader from updating to LP's bootloader
dersie said:
Same for me with Gear S2 on my Galaxy S4 Android 5.0.1 rooted not frequently but happen too often for me
Seem bad/old BT on S4 ?
Most of time the S2 do not reconnect automatically. I'm trying workaround to reconnect auto..... (trigger app)
Click to expand...
Click to collapse
Maybe, there is time that it doesn't disconnect at all for awhile then randomly starts doing it and continues right after the other .
My workaround with "Trigger" app works fine. Each time the watch is disconnected my script reconnect the watch after 3min disconnected. Worked every time this last days.
dersie said:
My workaround with "Trigger" app works fine. Each time the watch is disconnected my script reconnect the watch after 3min disconnected. Worked every time this last days.
Click to expand...
Click to collapse
Hi, can you please walk me through which settings you set up for this matter.
Also are you running pro version? Thanks
I not use the pro version.
You can select a trigger -> bluetooth and select wich device supervice for disconnect, so select the Gear in the list.
Then you can select action after this disconnection -> so for example : wait 10s or 3 min , turn off BT, wait 10s, kill Gear Manager, turn ON BT, select connect the Gear device, launch the Gear Manager.
Can confirm, Trigger is the answer
I used the Trigger suggestion posted above and have experienced zero issues since setting that up. The free version works fine for this so no need to get the pro subscription.
KILLDOGG said:
I used the Trigger suggestion posted above and have experienced zero issues since setting that up. The free version works fine for this so no need to get the pro subscription.
Click to expand...
Click to collapse
I can't wait to give this a shot. My Gear Frontier disconnects from my Galaxy S8 almost every time I use AndroidAuto (odd since that's USB), and i have to go back to the Gear app and press Connect to get it connected again. It must have 4 times a day, nearly every time I'm in my car. It's frustrating.
I suspect it's because Android Auto uses bluetooth for call audio or such, and I tried removing the bluetooth connection to my car, but Android Auto sets it up again every time you use it. And that seems to be the issue: Auto connects to the phone advertising the same capabilities (call audio) and so the phone drops the watch connection off. I'm not positive on the cause, but I'm positive that I'm tired of this experience.
skeene85 said:
I can't wait to give this a shot. My Gear Frontier disconnects from my Galaxy S8 almost every time I use AndroidAuto (odd since that's USB), and i have to go back to the Gear app and press Connect to get it connected again. It must have 4 times a day, nearly every time I'm in my car. It's frustrating.
I suspect it's because Android Auto uses bluetooth for call audio or such, and I tried removing the bluetooth connection to my car, but Android Auto sets it up again every time you use it. And that seems to be the issue: Auto connects to the phone advertising the same capabilities (call audio) and so the phone drops the watch connection off. I'm not positive on the cause, but I'm positive that I'm tired of this experience.
Click to expand...
Click to collapse
My Gear 3 disconnects when Android Auto connects as well. I have a Samsung S8+ which was just updated to Oreo. I am going to try the trigger app.
I buy samsung products from retail upgrades and over stocks. I got some classics and some frontiers. The watches are on the older firmware. I kept one for myself. After a few days of everything working great, including the battery, I decided to update the watch which is 2 days ago. Since then, my watch keeps disconnecting constantly, and the range is much shorter
Not sure if it's a phone issue or Android Auto issue but I'm not getting a pop-up in Android Auto when a call comes in so the only way to answer the call is to swipe my phone. I did a reset on the phone today for other reasons but I swear it was working before. Can anyone think of a setting that's blocking this? I've checked the Android Auto permissions and they're all checked.
Sent from my MHA-L29 using Tapatalk
Little more info. I deleted and repaired my car to my phone, rebooted the phone, deleted and reinstalled Android Auto and still the same thing, no call control. Messages work as they should with an on screen pop-up.
Sent from my MHA-L29 using Tapatalk
No such problems here. All works as it should. Not sure what to recommend.
Got it finally. I unplugged the phone and stayed connected to Bluetooth. Called my phone from another phone and the call came through on the Ford sync 3 system giving me the options to accept or reject. I accepted it and while in the call plugged the phone back in which brought me to the call screen in Android Auto. Hung the call up and while still in Android Auto I called it again and the notification showed up and gave me the call screen when I clicked it. Unplugged and retried again about 5 times and the notification pop-up and phone screen work as they should.
Sent from my MHA-L29 using Tapatalk
same issue
Having the same issue, will try your solution. Thanks!
Sorry to resurrect the thread but I wanted to thank you for the solution. While my Pixel in 7.1.2 was working no problem, having to switch out of the M9 just for this issue wasn't ideal. Followed the outlined steps and sure enough, I can take calls as expected whether I'm connected to Auto or not. Turns out the 100th Google search is the charm. Thanks!
Same issue with huawei honor 8
I am having the same issue with the huawei honor 8, and the fix does work for a time. The darn issue keeps coming back, which is obnoxious. Any one have an idea of what is causing to bug?
i heard its an EMUI issue and not an issue the phone particularly, and its up to Huawei to fix this. Im having the same issue which is tough considering i just came from a galaxy s7e that gave me tons of issues, but worked perfectly in AA
Since I updated my Pixel to Android 8.0 Oreo about a month ago, I don't get any notifications any more. The only thing that seems to be working is phone calls which I can see on my gear.
What I've tried to do, to solve it:
- Cleared data for the Gear app
- Uninstalled and reinstalled all Samsung applications
- Factory reset the Gear
- Checked that the Gear app has permission to notifications
- Checked that the Gear has the latest firmware
- Rebooted my Pixel
- Tried to connect my Gear S3 to a Huawei phone running Android 7.0 (notifications worked)
- Contacted Google that said the issue probably is because the Samsung app doesn't support Oreo
- Contacted Samsung that said Google is "probaby right" and I'll have to wait for an firmware update for the Gear which they have no ETA for?
If Google is right, everyone with Oreo should have this problem? Or atleast someone else? Is that the case?
I have Oreo beta on my Nokia 8 and have no problems which weren't present on nougat.
No issues with notifications.
Sent from my TA-1012 using XDA-Developers Legacy app
Ok, does anyone else have any idea of what can be the issue for me?
I'm having the same issue. Also with my pixel. Tried everything you have also done. Almost at the stage I'm about to switch back to my old moto 360 until they release a patch. Not being able to receive any type of notification is a deal breaker for me.
have you tried to clean cache, stop the Bluetooth process on pixel and run it again?
Anybody got solution for this?
I upgraded OnePlus 3 to Oreo and notifications stopped showing on Gear.
Soon afterwards I upgraded Gear to Tizen 3 but that didi't solve problem.
The new software update that was released a few days ago solved the issue for me.
Exactly the same problems and frustrations
In short, have tried all the same actions as set out by yourself. No Gear 3 notifications started with Pixel upgrade to Android 8.0. Like others have stated here, makes wearing and relying on Gear watch very marginal. I bought Gear watch to pickup notifications when doing outdoors, relatively hands free sporting activities.
Everyone: please keep THIS discussion thread alive in search of eventual solution. Thanks. John, Sydney Australia
Same issues
I recently purchased a gear s3 Frontier watch, after much researching, it was the one that most fit my wants.
It is paired with my Pixel phone and for the first 3 or 4 days it worked great but now I don't receive any notifications at all except for Samsung Health... Notifications are all turned on but nothing comes through?
It seemed to have started with the Tizen 3.0 update. But could't say if it was immediately after or a day or two later. I've done multiple resets but nada.
Phone calls do come through to the watch but my phone doesn't ring anymore when the watch is connected..
No settings were changed on the watch or the phone app.. One day it worked fine, the next day, everything quit...
This is very disappointing... these notifications were the reason I wanted a smart watch in the first place.
Any idea whats going on?
The watch is SM-R760 running Tizen 3.0.0.1 version R760XXU2CQL1
Knox 2.2.0
Know Tizen 2.2.0
SE for Tizen 1.0.0
TIMA 3.0.0
Pixel Phone on Android 8.1.0
Snapdragon S8 on nougat with a similar problem. My notifications will disable themselves and the switch to turn them back on will be grayed out and unselectable. Only way to get them to work again is by rebooting the watch and the phone, but it will only work for a few hours until it's broken again.
I have a similar problem with my Oneplus 3.
Evertyhing worked fine until I updated my phone to OxygenOS 5.0.3 Android 8.0.0. Since then the Gear S3 doesn't receive any notification. The only one are phone calls.
The settings for notifications are on (in the Gear App and OS settings unchanged). Resetting the watch didn't change anything. Round about 2 times a day the gear looses the bluetooth connection for ~30 seconds which is new as well.
Resetting the phone is no option.
Any ideas or new information about this problem?
nouseeme said:
I have a similar problem with my Oneplus 3.
Evertyhing worked fine until I updated my phone to OxygenOS 5.0.3 Android 8.0.0. Since then the Gear S3 doesn't receive any notification. The only one are phone calls.
The settings for notifications are on (in the Gear App and OS settings unchanged). Resetting the watch didn't change anything. Round about 2 times a day the gear looses the bluetooth connection for ~30 seconds which is new as well.
Resetting the phone is no option.
Any ideas or new information about this problem?
Click to expand...
Click to collapse
I reinstalled the Gear app, repaired and resetted the watch which didn't change anything.
Though I forget about the Samsung Accessory Service app. After reinstalling this, rebooting the phone and repairing the watch the notifitications are working again.
In the matter of connection loss I can't tell not yet.
nouseeme said:
I reinstalled the Gear app, repaired and resetted the watch which didn't change anything.
Though I forget about the Samsung Accessory Service app. After reinstalling this, rebooting the phone and repairing the watch the notifitications are working again.
In the matter of connection loss I can't tell not yet.
Click to expand...
Click to collapse
I know this is an old thread, but I stopped getting notifications on my Oneplus 7 Pro - Android 10. I had to turn off battery optimization for the three Samsung apps - Galaxy Wear, Gear Plug in and Samsung Accessory Service. I now have notifications back.
Recently on my Note 10+ (SM-N975U1) running stock Pie and Dec 1 2019 update, I have been experience 2 issues.
Notifications for some apps are delayed
App updates hang on Google Play Store
For the app updates, they stall with "Download Pending" or the download stalls with <100% complete.
Resolution steps that have NOT worked
Clearing cache and data for Google Play Store
Rebooting phone
Rebooting into Safe Mode
Changing from Wifi to Cell Network Data and vice versa
Stop/starting app updates
Current Workaround
Closing/swiping the Google Play Store and opening it again. It will eventually complete downloading after multiple attempts and install/update an app - you will have to repeat this continuously for every app you want to install or update.
Is there anyway to debug this without doing a complete reset?
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
mtweisenbarger777 said:
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
Click to expand...
Click to collapse
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
selector said:
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
Click to expand...
Click to collapse
I have no idea why this happens. What I do know I have had this issue on LG phones, Pixels, and Motorola's. It isn't a Samsung thing. I think it's an Android Bluetooth issue.
This is an old thread - but in case someone else finds it, I came across someone's suspicions in another thread that their Plantronics headset was causing some kind of problem with their Bluetooth. I began unplugging my Savi headset when not in use and it seems to help... YMMV.
This has been going on since Pie; made me upgrade from my Note 8 to Note 10 and it came right back. Infuriating.
You may also want to try to rub a lucky stone and do some chanting as well, because it's about as effective as hoping for a fix after all this time.