Database Info

Gear S3 + Pixel XL - Gear S plugin Crashes

I picked up a Gear S3 yesterday and am having difficulty with the Gear S Plugin crashing when attempting to add a location (for weather).
I've tried the usual uninstall/reinstall, force close, clear cache/data to no avail.
Anyone have any suggestions?
I'm part of the Android Beta Program so Android O is installed on my phone.
Any help would be appreciated - thanks

I have the same problem with my Verizon S3 and I do not expect Samsung to fix it any time soon or at least until Android O is officially launches. It may even be until they have a working Android O build for S8's.
I setup Samsung Pay on mine before I upgraded to Android O so Samsung Pay is still working on my watch even though plugin is crashing.

try this:
https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035

No notifications

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.

unlocked S7 on Oreo but showing Nougat icon???

Simply put, tapping the Android 8.0 inside settings (About phone--Software information--Android version 8.0.0) few times is revealing Nougat icon but not Oreo. Anyone had or is having similar issues? Doing the same on my other handset, the S7 Edge, is showing the Oreo cookie (as it should). Every version has always corresponded to the correct image (sandwich, lollipop, etc), but my S7 is acting weird. What could be the reason? I am eager to learn and know.
Any thoughts? Any one here with unlocked (or any other version), can you see what I am seeing, or is it just my firmware and handset?
My handset shows
Android version 8.0.0
Experience version 9.0
Baseband G930UUES4CRG3
Knox 3.1 API level 25
Kernel July 24th

Galaxy Buds and S6 won't Connect: UI stopped, H E L P !!!

H E L P !!!!
I just spent 3 solid days on this. Yes, there are some out there still rockin' the S6. I am running Android 6.0.1, have 128GB and BT 4.1 on-board, and my phone works perfectly.
I get the dialog "Unfortunately, the system UI has stopped" at the instant that the buds try to connect. They pair, but they don't connect. The dialog wont quit as long as the lid is open.
Despite this, I did manage to reset the buds between the dialogs, to no avail.
The earbuds are running version R170XXU0ASC4
The Galaxy Wearable app is v 2.2.24.19031361
The Galaxy Buds Plugin is v 1.1.19040351
I tried all kinds of resets, clearing of caches, removal or disabling of other apps, trying to connect in safemode, removing notification permission of other apps, restoring permissions of other apps (notably the system apps), turning off all power savings, deleting unused apps and cleaning the phone...nothing works
I suspect a conflict of sorts, or perhaps an inherent incompatibility.
Any ideas would be helpful, such as comparison of version numbers or connection experiences...
Thanks !

Have you checked with Nougat update? I don't know how exactly can any BT accessory crash SystemUI but something tells me Buds weren't made for Marshmallow-based phones.

You might be right, except that I don't want Nougat. All the documentation for the Buds said they were compatible with 4.4 and forward. FALSE !!
I returned them, and am waiting for the previous versions to arrive, the IconX 2018, which are BT 4.2, which is closer to the 4.1 of my phone.
(true wireless buds for BT 4.1 don't exist, at least not without sticking out of the ears horribly or having poor battery life...)
This time, I will give it 2 hours to make them work.

You have to upgrade to 7.0 to use them. Just for testing purposes I connected my Buds to my old S6 which was running 7.0 and it worked. However, when I downgrade it to 6.0.1, it doesnt work anymore. Nougat is just better than Marshmallow, you can customize it to look like 8.0 Oreo by installing never TW and S8/S9 versions on it

Android Auto + Android 10 = broken ?

Hi guys,
my android auto (in a certified compatible car AA) it's fully broken from Oneplus Android 10 versions.
Tried the beta3, beta4, and "official" android 10, always same problems.
Connections in not stable, sometimes audio glitch and interface (of my car) forced to reboot.
Almost always, the buttons from above interface disappear (in every app, like spotify, maps, waze, etc...) becoming fully unusable.
The vocal commands works only with navigator and music, no more google assistance questions (like what's the weather tomorrow) --> This seems confirmed that is broken in google side.
Now, I'm trying to understand if it's fully broken android 10 + android auto (the system AA level, not anymore an app to be lauched) OR it's only with these oxygen's roms, still broken in some way.
Please, someone have real feedbacks to give me ? I'm very disappointed, thinking to go back to Android 9 just for this, but i will loose every update (included the security monthly fix) because OPO is supporting already just Android 10.
What can I do ?
Tried all the throubleshoot I've found around of course, like wipe cache, delete app, use "new" AA interface, cables, etc...
Car: Mazda CX3 (it seems that Mazda + OPO7Pro is the devil match)

avid_droid said:
What I've learned from this phone and Android auto is that if you have USB debugging enabled, Android Auto will give you the worst experience.... EVER!
If you have it off, o don't know what to tell you honestly. If its on, TURN IT OFF! I have a 2017 Chevy RS Cruze and have no issues except when I have debugging enabled
Click to expand...
Click to collapse
Thanks for the tip, but unfortunately it was one of the things I've tried... Disabled the usb debug and also fully disable the dev. Mode...
BUT, are you on android 10 ? Really it's stable to you ?

Guys, some more feedbacks ?
My opo7pro with latest stable 10.0.2 it's still unstable with android auto (mazda).
Main selector icon disappear (becoming unusable), random crash/reboot, audio glitch...
Ufff

I've had my op7p for about a week. I have a Kenwood dmx 905 with wireless Android auto. Phone came with Android 9. Had no problems connecting without using the USB cord. Did the local update to Android 10. Now it won't connect unless I use the USB cord. Then I can disconnect the cord and go wireless. I have to do this every time now. Want to know to go back to Android 9.

m4ssnet said:
Guys, some more feedbacks ?
My opo7pro with latest stable 10.0.2 it's still unstable with android auto (mazda).
Main selector icon disappear (becoming unusable), random crash/reboot, audio glitch...
Ufff
Click to expand...
Click to collapse
Got the same with OOS in my Mazda. Switched to custom ROM, no more issues.

I can confirm the debugging issue making AA go weird. If I have it enabled it has a spastic, if I disable it, AA works flawlessly.

aoaleman said:
Got the same with OOS in my Mazda. Switched to custom ROM, no more issues.
Click to expand...
Click to collapse
man... I'm without hope
Really with custom's no problem at all ? I investigated more... I really think it's a problem also in Mazda side + OPO7Pro Android 10.
I didn't want this time go custom, I'm fully stock without root (for security reason etc...)
Ufff... very disappointed, 10.0.3 still has the same problem :crying:

Having huge problems with my 2016 Skoda Octavia Amundsen. I will try debugging mode off and report. Thx everybody.
-tapola
PS. As AA is not supported in Finland yet, how can I edit the power saving option of this App?