I installed Marshmallow on my Nexus 5, and then yesterday's Marshmallow updates from Play Store for Gear app, Gear Plugin, and the Samsung Accessory Service (Gear app asks if you want both of those for improved functionality).
All was well until I rebooted my phone, and now I can't reconnect to the S2. Did a hard reset of S2, and worked until S2 went out of range of phone. Then wouldn't reconnect. Kept saying invalid passkey, even though code on phone and S2 were the same.
I would either not update phone to Marshmallow, or not update Gear app, or both, cause I think you're gonna have the same problem.
I'm having the same problem on my Nexus 5X. Is there any fix for this yet? The latest update for the Gear App says it added support for Android 6.0, but that's not the case.
Checking in as well its really really annoying to have to "reset" the watch 3-4 times a day.
I can confirm that I have repeatedly been able reconnect my S2 to my Nexus 5 on Marshmallow after I installed the S2 firmware update that was available in the USA in the Gear app under the About Gear settings. I went from firmware version R720XXU2AOIL to R720XXU2AOJ3. I found that even after installing the firmware, I had to do one Light Reset on the S2 before the S2 would reconnect.
So far so good. Have intentionally gone out of range 6 times and reconnected all 6 times. Will report back if situation changes.
Related
Just got my Note Edge yesterday and I love it. But I can't get it to work with my Gear S watch? Very frustrating and I can't figure it out unless they just aren't compatible. Can anyone help?
I have a Note Edge paired with the Gear S that works great. I can use the Gear S via Bluetooth or cell. When you said that you just got the Edge, it makes me think that this Gear was set up with another phone prior to the Edge. If so, you'd have to factory reset the Gear.
My Gear Neo 2 is really finicky with the Edge. I think it is the flakey bluetooth on the entire Note 4 line. Every once in a while (maybe twice a week or more), I have to restart the watch to get it to talk to the phone again. I am totally awaiting the official Lollipop update for my Verizon variant as there are a large number of bluetooth changes in it. I am getting a bit concerned that Lollipop doesn't appear to be on the immediate radar for Verizon now that the S6 is out there
Anyway, I would try and factory reset the watch and start the connection process over. A bit inconvenient but I bet it will work.
i've got both and they're work very well. the bluetooth connection is stable and the reconnection after a disconnect is very fast. i see no trouble
Gregdec said:
Just got my Note Edge yesterday and I love it. But I can't get it to work with my Gear S watch? Very frustrating and I can't figure it out unless they just aren't compatible. Can anyone help?
Click to expand...
Click to collapse
download Samsung Gear Manager from galaxy apps..
So I have been struggling with this since opening day!
When the watch is connected to my 6P (and my Nexus 6 before that - which was not Marshmallow) I can answer and make calls from the phone, but the audio and mic always default to the watch. This is super annoying. Verizon sent me a new watch which does the same. Samsung says it's a Marshmallow problem. Google says its a Huawei problem. And they send me back to Verizon.
So, what I have resorted to is waiting for the call to connect and then on the phone override the BT audio to handset prior to talking. What a hassle!
If you override the BT audio on the phone's BT setting for the S2, then you are no longer given the option to take the call on the S2 (of course).
Anyone have a similar experience? What to do next?
I have the same exact problem with the S2 3G paired with the Nexus 6P. I unchecked phone audio in the phones bluetooth settings but as you said, it disables the option to use the S2 as a phone. Hope there is a solution soon.
Seems to not be fully compatible with marshmallow yes
I have this issue as well. Also when I make a call with my phone (Nexus 6) the call is always completed on the watch via Bluetooth connection. I have to switch back to the phone on the watch during the call.....
Sent from my Nexus 6 using XDA Free mobile app
Update - Sammy Boo
Spoke with Samsung again. I thought the Gear Manager update yesterday would fix this - no deal!
Samsung is now claiming this is a software upgrade with the Gear S2 and is intentionally programmed functionality! Really?
I requested an escalation to their development team as a software enhancement to revert to prior functionality - they assured me that would happen, and they'll send me a notification from their team; problem is, they did not take any of my contact info!
I'm having an issue with CM13 on a Note 4 with a Gear S2. I changed the build.prop from Samsung to HTC to allow the Gear app to function (it doesn't like CM on Samsung phones) and all seemed well. When I try to click send to take a call, nothing happens. When I receive a call I only have the option to reject it from my watch. My watch is not activated, I don't need 2 numbers.
After spending hours on the phone with Verizon and Samsung I flashed a TW based rom and calls instantly worked. I'm pretty happy with my CM rom and I'd like to find a way to get it to work with that rom.
Did this ever get resolved?
I had Samsung Gear S2 with my Note 7 and life was awesome! Then tragedy struck and my life with a good phone is put on hold for at least 6 months, until the S8 series releases in Feb?/March?/April? of 2017. Until then, I decided to limp along with a somewhat cheaper Nexus 6P. The problem is, it throws all my incoming calls over to my Gear S2 instead of picking up on the phone handset. I then have to choose the drop down option to use my handset instead. This is NOT the intended operation. If I wanted to answer the call on my watch, I would answer it on my watch. I don't want to answer on my phone and then have my watch pick up. There is no way that I have found to correct this. This is terrible functionality for an otherwise very promising piece of technology (the watch, no the phone).
I have the same issue on 6p on ATT. What I normally do is like said above is uncheck the Bluetooth handset under Bluetooth settings. Then just turn call forwarding on..Therefore when I want to take calls on the watch I just wait about an extra 10secs. Or of course answer on the phone.
BTW when i had a samsung S6 this was not an issue...
Hello All,
I recently purchased a Samsung Gear 2 running Tizen R380XXU0BOA2 and am using a Samsung Galaxy Note 3 running Android 5.0 and running Gear Manager version 2.2.03.16033141N with Gear Plug In version 2.2.03.16033141N
A full charge of the phone can last 2- 2.5 days with medium use and not connected to the phone. A full charge of the watch can easily last 3-4 day when not connected to the phone.
However, when I connect the watch to the phone using BT, I can only get 8 hours or so from either device. Both end up with less than 5% battery life after both sitting there overnight and not being used, but connected via BT
From what I been reading in the forums, this is not the norm.
Does anyone have any idea what I can do to remedy this?
Or is there another program out there like Gear Manager that may connect differently to BT and the Gear 2?
Thanks,
Also....FYI, neither phone nor the watch is rooted.
Well, I found out that Gear Manager version 2.0.14042803 is much easier on my phone and gear 2.... Only issue appears to be that if I go out of range, I get the message BT is disconnected. And when I get back in range the phone does not connect automatically.
I simply set the Gear Manager app not too look for updates, and when it advised me there is an update I am able to cancel it and it stays at the same version.
my new galaxy gear s8+ keep disconnecting from my gear s3 frontier when the phone is not on (as in not locked)
i can't figure out why as this has been an issue since getting the phone, is there a setting like the sleep or power save functions that i'm missing?
also i don't know if this has anything to do with it but my setting in the developer settings menus keep getting reset to the defaults (unknown sources keeps resetting to off and gpu settings keep reverting)
I have an s8 with the s3 frontier as well. I was having a possibly related issue as well. With me, any blue tooth headset I had was dropping the sound every few seconds. I tried everything until I did a factory reset as a last ditch effort before I returned the phone. It has been working much better after that.
Deleted
Mechcondrid said:
my new galaxy gear s8+ keep disconnecting from my gear s3 frontier when the phone is not on (as in not locked)
i can't figure out why as this has been an issue since getting the phone, is there a setting like the sleep or power save functions that i'm missing?
also i don't know if this has anything to do with it but my setting in the developer settings menus keep getting reset to the defaults (unknown sources keeps resetting to off and gpu settings keep reverting)
Click to expand...
Click to collapse
I think it's a nougat power saving thing. It does that with my Op3 once in a while. Got better after turning off doze, but battery life went down as well.
Sent from my ONEPLUS A3000 using Tapatalk
Have Pixel XL with Nougat onboard (latest 7.1.2, before 7.1.1) - no such problems so far. So i don't think it is directly related to Android core, but maybe to Samsung hands-from-ass developers making changes to AOSP
i think this is more likely to be the case as well; as i dont have issues with bluetooth headsets but only the gear
I have the S8+ and experience zero such problems. I strongly suggest you visit your sales outlet and request them to help you with this situation. Sounds a real pain.
Let us know how you progress.
Ryland
Hello…
I know it' isn't an Android phone : ) any help will be appreciated…I have an S3 connected to my iPhone but then when I open the gear app it’s isn’t detecting it? Attached SC
*iPhone, gear app and S3 are all up to date
Thanks
Reset the watch for new phone (in watch setting), erase BT connection in phone totally close the Gear app on phone and retry.
Just put my Gear S2 from my Galaxy S5 to my iPhone SE.
I have done that already and it seems okay for now, will the S3 drain it's battery more with iPhones vs Android because I turn off bunsh of stuff like HR, GPS...etc and I may make it 1 day with a single charge? I see other only are getting 2-3days with a single charge
Thanks