11-24-2017 02:01 PM
Hello there, folks.
I certainly want to assist you all further with this matter. To better do that, can the Community have the exact model number and Baseband version (both under Settings>About Device) for your device as well as your service provider and what you've already tried to fix it? Thanks!
11-27-2017 11:52 AM
My model number (gear s3) SM-R770 and (Note 8) SM-N950U
Baseband (gear s3) (cannot locate) and (Note 8) N950USQU1AQI5
I've uninstalled and reinstalled the Gear app. Does not work.
I don't want to have to reset the watch at all just to take it back to the version before the update.
My phone freezes and the battery is draining at an exponential rate. My watch keeps asking me to set a pin number and it way out of sync with the phone.
11-28-2017 03:20 PM
I sure hope someone has a solution or someone can tell me how to back this version out to the previous version. The battery on my watch and phone are literally draining within a couple hours. I went to bed last night at 100% and woke up to my phone on 31% and my watch on 27%. I charged them that morning at 8 and before 11am they were both under 70%. Thanks
12-07-2017 01:16 PM
I tried to uninstall 3 or 4 times and it just keeps doing it. I finally just had to disconnect my watch from my phone. That's the only thing that allows the phone to work properly and I don't get the "put in you passcode" screen on the watch. Nothing of course syncs, which is a pain, but at least I can use my phone without it freezing every 2 minutes. Just wishing now I would have bought the watch from Verizon so it worked on its own. Surely all of these problems have been given to actual techs and not a regular forum moderator.
12-12-2017 11:11 AM
I have model SM-G955U (Galaxy 8+), Android version 7, I installed the latest updated on 12/12/17 and I still have the persistant Gear S Pluggin has stopped error message popping up. I have reinstalled the software but no help. I have done all I know to do but the error continues. When is this going to be resolved? There are several who have posted about this issue yet nothing has been mentioned about a resolution