Philip Butin
Member
I have noticed this is an older thread but the connection problems with the Gear series are still serious in December, and this is the best place I can find to discuss them. Hopefully someone will read this who knows more about the Gear 2 Neo than I do.
I bought a new Gear 2 Neo from ATT for $99 on Black Friday. For a week it seemed to connect fine but then after the December 1 Gear Manager update the connection started to be intermittent. I uninstalled Gear Manager and reinstalled--tried various things with Bluetooth, the Gear Manager installation process kept factory resetting my Gear 2 (erasing all date and programs several times), and most of the time the two devices would pair but would not connect. Then if I did get a connection it would fail and the only way to make progress was to uninstall and reinstall, requiring all apps to be reinstalled as well. Talked for 3 hours with a nice Samsung tech who said he had had 5 calls that same day with the same problem with the new update. He thought the update was aimed at Gear S and Lollipop for Note 4 and Edge phones, and they had not given enough attention to how it would work with prior Gear models or phone models.
Finally went to an older (summer) version of Gear Manager that would at least maintain a reliable connection with at least the stock Samsung apps. That worked OK for about a week but it kept trying to update the Gear Manager, I could not use the App Store or any of the controls on the phone, and there was an error screen threatening to update the program and factory reset the watch that I had to ignore while the manager was running on the phone in order to keep the connection.
Then there was a new December 16 update and I took the plunge in the hope the concerns had been addressed. The new install factory reset the watch again. Then it took about 10 tries to get the December 16 Gear Manager and the watch to connect, but they finally did, and I reinstalled all my apps and data.
The watch is still connected to the phone a day later (and I'm not inclined to uninstall the Gear Manager again), but the connection is unpredictable and unstable, and has to be reconnected periodically by rebooting both devices. The results are still inconsistent. Stock apps tend to run fairly reliably (with the exception of S Voice, which is intermittent) but developer apps are very unpredictable. It seems like the Bluetooth connection from the watch to the phone is more reliable and stable than the connection from the phone (Gear Manager--updated for newer devices to the neglect of the Gear 2 Neo) to the watch. To me this suggests the problem is still the Gear Manager update(s) that have recently been forced upon us.
Samsung, this is not acceptable. I bought a brand new Samsung watch on November 29 that is still being sold, and I am running it with a Samsung Galaxy Note 3 phone.
I know this is an older thread but above one entry suggests the connection problems may be due to a caching difficulty within S Health. It suggests the S Health cache be emptied and everything rebooted. I have tried this and am hoping it will make a difference, but so far, I'm still having connection problems. Did anyone try any of the cache emptying strategies above?
Any thoughts would be appreciated.
I bought a new Gear 2 Neo from ATT for $99 on Black Friday. For a week it seemed to connect fine but then after the December 1 Gear Manager update the connection started to be intermittent. I uninstalled Gear Manager and reinstalled--tried various things with Bluetooth, the Gear Manager installation process kept factory resetting my Gear 2 (erasing all date and programs several times), and most of the time the two devices would pair but would not connect. Then if I did get a connection it would fail and the only way to make progress was to uninstall and reinstall, requiring all apps to be reinstalled as well. Talked for 3 hours with a nice Samsung tech who said he had had 5 calls that same day with the same problem with the new update. He thought the update was aimed at Gear S and Lollipop for Note 4 and Edge phones, and they had not given enough attention to how it would work with prior Gear models or phone models.
Finally went to an older (summer) version of Gear Manager that would at least maintain a reliable connection with at least the stock Samsung apps. That worked OK for about a week but it kept trying to update the Gear Manager, I could not use the App Store or any of the controls on the phone, and there was an error screen threatening to update the program and factory reset the watch that I had to ignore while the manager was running on the phone in order to keep the connection.
Then there was a new December 16 update and I took the plunge in the hope the concerns had been addressed. The new install factory reset the watch again. Then it took about 10 tries to get the December 16 Gear Manager and the watch to connect, but they finally did, and I reinstalled all my apps and data.
The watch is still connected to the phone a day later (and I'm not inclined to uninstall the Gear Manager again), but the connection is unpredictable and unstable, and has to be reconnected periodically by rebooting both devices. The results are still inconsistent. Stock apps tend to run fairly reliably (with the exception of S Voice, which is intermittent) but developer apps are very unpredictable. It seems like the Bluetooth connection from the watch to the phone is more reliable and stable than the connection from the phone (Gear Manager--updated for newer devices to the neglect of the Gear 2 Neo) to the watch. To me this suggests the problem is still the Gear Manager update(s) that have recently been forced upon us.
Samsung, this is not acceptable. I bought a brand new Samsung watch on November 29 that is still being sold, and I am running it with a Samsung Galaxy Note 3 phone.
I know this is an older thread but above one entry suggests the connection problems may be due to a caching difficulty within S Health. It suggests the S Health cache be emptied and everything rebooted. I have tried this and am hoping it will make a difference, but so far, I'm still having connection problems. Did anyone try any of the cache emptying strategies above?
Any thoughts would be appreciated.
Facebook
Twitter
Instagram