First let me state my current phone is s-off and rooted, but otherwise stock. I have been playing with some lockscreen replacements but not much else altering the phone.
I do also have google voice running for voicemails (I like the notification system, the inbox style tracking and the transcribing) and this was running on my rezound as well so may very well be the issue but not sure.
This occurred a lot on my last phone (rezound) and I chalked it up to it being a little older. But last night it happened on this phone (at home where I have excellent service), my girlfriend called twice and I got no notifications until google voice picked it up and notified me I had a voicemail (she normally doesnt let the voicemail hit so I often never know she calls until its much later and she is much angrier).
Has anyone else experienced this? Is it a verizon thing, a google voice thing or something that just happens sometimes regardless?
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.
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)
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.
I'm an experienced programmer, but a complete novice when it comes to android development. I also hope I'm posting this in the right place...
I have recently bought a OnePlus Nord (AC2003) which I'm *fairly* happy with, and a Samsung Galaxy Watch3. I'm having an issue with it in that the watch and phone will fairly randomly disconnect from each other, even when they're in close proximity to each other. I have read extensively about the possible issue*, and reset both the watch and the phone, and cleared the bluetooth cache, which appears to have made a difference, at least in the long term. The disconnection now only happens about once a day, rather than the every half an hour that was happening originally.
* One school of thought is that the watch is absolutely at fault, as the users have no problems with other bluetooth devices. Another school say it's definitely the phone, as they have no issues when they use the watch with a different handset. Go figure.
My programmer's hunch (which I've learned to trust over the years) is that a service or app in the phone is stopping and starting, and I'd like to get a log of when the phone is stopping and starting apps and services. I've enabled developer mode, and I can see the option for 'Basic Log' and 'Power Consumption Exception' log in the OnePlus logKit.
My question is - Has anyone looked at the logs for this sort of data before, and is there anything in particular I should be looking out for, with particular attention to when the battery management on the phone decides that a process can be stopped or hibernated.
(Obviously, if anyone has anything to share about any Eureka moments regarding smart watch disconnects with this phone, I'd love to hear those too )