I have a GS5, and since the update that occurred on Tuesday, I can no longer sync my Fitbit tracker. Many Fitbit users are experiencing the same issues per their forums. Is this being addressed by Verizon?
This same thing is occurring with our Polar H10 Heart Rate monitor connected by Bluetooth. Other devices can pair, but the phones cannot.
Ditto with the Garmin Vivofit 2. Won't even allow me to pair with the device although the device will pair with my computer. This same thing happened the last time they "upgraded"! I agree with DFWdad, time to change to a new provider.
Same here. Fix it, Verizon.
Same story here. I'm glad I'm not crazy. I'm about to loose this week's challenge because I can't sync.
*lose
FARRUGGIA_JOE,
Fitbit is a good way to keep track of activity, but let's not give up yet. When a phone updates software, any relevant applications, like the Fitbit app, would need to be updated as well to ensure compatibility. Have you reached out to the app developer via Play Store?
RussellM_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!
Being able to keep your fitness tracking device synced is crucial, TVGuy22. To ensure that your tracker is able to stay connected and synced, we do recommend checking the Google Play Store for any updates to the tracker's app. Here's a link with steps: https://www.verizonwireless.com/support/knowledge-base-105501/
LynnD_VZW
Being able to win those FitBit challenges is important, HARMONIEHONEY. Let's check to ensure the FitBit app is updated. Here's a link with steps: https://www.verizonwireless.com/support/knowledge-base-105501/
The link says, an unexpected error has occurred. Ahhh the irony. Pages and pages of people on Verizon and fitbit forums are having the same problems. Maybe Verizon and fitbit techs could work together to get this fixed. 6 days is ridiculous.
I'm having the same issue with Garmin Vivo Fit and my Samsung Galaxy S5 since the update
My husband and I have the same phone and Garmin vivo fit devices. I uninstalled the Garmin Connect app on his phone and reinstalled it. When I tried to pair his device with his phone, NOW IT WON"T PAIR!
My phone is still paired with my Vivo Fit, but I can't sync since the latest Verizon update.
This is clearly a Verizon issue.
I have this same issue. Many bluetooth low energy devices won't work after this update.
Exactly. It's an issue with Bluetooth Low-Energy Devices. Have any canned "cheer-up" responses to that?
Verizon, this is a an issue with Bluetooth Low-Energy Devices section of the ROM. Please have the dev team review this section of the code for errors. In the meantime, perhaps it would be best to re-release the previous rom version while this version undergoes troubleshooting.
Regards,
Stephen
I am having the same issue. Fitbit stopped syncing with S5 on Aug 10th. After automatic update. Have been on fitbit community with many others, looking for a solution.
Mwolfeaxon, I know how important it is to have your Fitbit working properly. Let's work on getting this resolved. What make & model of device do you have? Have you uninstalled and reinstalled the application? Also, is the Fitbit app up to date?
GersonG_VZW
Now I am having trouble with all my Flic buttons. The Flic people tell me its the Verizon update that killed off the Blue Tooth Low Energy connections on my Samsung Note 4.
Please fix this. What ever you changed I don't need or want it.
GARKUB17 wrote:Now I am having trouble with all my Flic buttons. The Flic people tell me its the Verizon update that killed off the Blue Tooth Low Energy connections on my Samsung Note 4.Please fix this. What ever you changed I don't need or want it.
GARKUB17 wrote:
GARKUB17 and TVGuy22, I suspect that, although Verizon is one of the main distributors of this "update," it originates with Samsung. If not with the Great Google, Progenitor of Android. Nevertheless, Verizon ought to at least be more forthcoming with any information they have.
Dear VZW responders, please tell me if I am wrong. It seems all you can do is read from a script of things to try. You don't seem to be able to do what we need:
- Research to see if Verizon technical people are even aware that there is trouble
- Research to see if anything is being done about it
- Report these issues to someone else in the company who can address these issues.
I encourage all of you customers to log on to your account on Verizon Wireless website, chat technical support, and reason with them until they open an incident. They did for me while saying they saw no other reports if trouble.
It seems that these community pages are just for us to sound off to each other.
DFWdad wrote:Dear VZW responders, please tell me if I am wrong. It seems all you can do is read from a script of things to try. You don't seem to be able to do what we need:- Research to see if Verizon technical people are even aware that there is trouble- Research to see if anything is being done about it- Report these issues to someone else in the company who can address these issues.I encourage all of you customers to log on to your account on Verizon Wireless website, chat technical support, and reason with them until they open an incident. They did for me while saying they saw no other reports if trouble.It seems that these community pages are just for us to sound off to each other.
DFWdad wrote:
I think that's right, most peer-to-peer support forums like this are for users to give advice to one another. VZW reps actually pop in here more frequently than is often the case in such forums. They are often helpful. But in this instance, they simply don't have the technical knowledge to tell us what is going on (and maybe not the corporate permission). I'm with you: all we want is information. Are VZW's technical people working on a solution for this? Are they communicating with Samsung? Will we see a fix or a patch sometime soon, or have to wait for next month's update to silently correct the problem without ever admitting it occurred?
Look no further help has arrived LOVE2CTHEMOON. I know how important it is to make sure your phone is working properly.
Are you able to pair other Bluetooth devices to your phone? Make sure the Bluetooth settings on the phone is turned on. Make sure the Fitbit is only connected to one phone or tablet, and the Always Connected option is turned on in the Fitbit app (Open Fitbit app > Account > select tracker > turn ON All-Day Sync).
JohnB_VZW
I do not have any other blue tooth devices. In response to your suggestions. I have already checked these things and more. This is clearly a more intense issue, then what you have mentioned. This is ridiculous that your reply would even make sense at this point. Clearly, several, and I mean "several people " are experiencing this identical situation. From the many posts I have read, both on Verizon website, and Fitbit, the majority of people have a Samsung phone and Verizon service. Everyone has stated that this issue has stemed from an automatic update. It can't be that difficult to diagnosis this problem and fix it. My only conclusion at this point, is to go with another wireless carrier, get another phone that is not a Samsung, and never buy a Fitbit product again! This is really unacceptable!
This problem goes beyond Fitbits. I have a Garmin Forerunner 220 that will not connect to my S5 after the aforementioned update, but it WILL connect to my Nexus 7, so the problem is not the watch. Additionally, I have a scale that refuses to connect to my S5 after the update. Neither device had any connection issues prior to the update.
The problem is unlikely to be anything except the update. Between your devs and Samsung, please get it together and fix this. In the meantime, please make the prior update (G900VVRS2DQD1) available so we can (hopefully) use BLE.
Having the same issue after OTA update. Polar Flow with A300 wristband device. Hoping for a hotfix.
Well, today is 8/22, and I have not been aware of either Verizon or Fitbit, coming up with a solution to sync my device with my phone, since the update August 10th. Very frustrating, to say the least. It would be nice, at the very least, to get a somewhat detailed response from someone that is actually working on resolving this.
Hi. I'm the developer for the Flic app that connects to Flic buttons which use Bluetooth Low Energy.
It's clear that this update breaks connectivity to ALL Bluetooth Low Energy devices. Connectivity to Bluetooth Classic devices seems to work fine. The problem lies within the Bluetooth part of the OS and not within the 3rd party apps (and it's also not a problem with some particular fitness tracker or peripheral). This means it is impossible for any user to get it working by "reinstall app/restart Bluetooth/reboot/clear cache/unpair/re-pair" and so on. The only way to get it working is if Verizon/Samsung fixes the bug in the OS and rolls out a new update.
If anyone wants to see where exactly it crashes, see this: https://issuetracker.google.com/issues/64731145
I suggest Verizon Customer Support forwards this information to the developers and push them to immediately release a new update, since there is nothing else we regular users/developers can do (we don't have their contact details for example).
Thanks, emilenl! It's good to have such a clear statement by someone who knows something about it.
Now here is some helpful information. If only the Verizon customer service bots could read.
Same thing happened to my up4 band. Updated app and did not help, removed and reinstalled and didn't help? Any suggestions?
Elizaorm1 wrote:Same thing happened to my up4 band. Updated app and did not help, removed and reinstalled and didn't help? Any suggestions?
Elizaorm1 wrote:
At this point, based on reports earlier in this thread from 3rd-party developers who have to deal with this, it sounds like the best we can hope for is that Samsung will fix the problem it created. By now, I'd say my most optimistic guess (and it's no more than that) would be that in the next week or so a monthly system update will roll out that will include a fix. I have no information at all to suggest that that is the case; I'm only guessing and hoping.
My 2-year contract on my Samsung Note 4 Edge is up. I have loved this phone, but when I head to the Verizon store I'm going to be looking at other manufacturers.
I've heard again that samsung definitely has fixed this issue and it's being validated by verizon now. Hopefully it'll be out very shortly.
mwolfeaxon wrote:I've heard again that samsung definitely has fixed this issue and it's being validated by verizon now. Hopefully it'll be out very shortly.
mwolfeaxon wrote:
Many thanks! That's kind of the best I've been hoping for--a fix in a regular monthly Samsung/Verizon update. Hope it turns out that way.
Just to add to all the happy comments. Appears that the last VZ update hosed pairing/syncing from my Galaxy S5 to my Garmin Vivofit 2. I have uninstalled/reinstalled the Garmin Connect app, have done a factory reset on my Vivofit, even installed new batteries in the device in case I was having an issue with low juice. Nothing worked. So I'm in line with everyone else for a fix to my Verizon provided Samsung Galaxy S5.
Just curious where/how you heard this information. I'm hopeful it's true. I think it's inexcusable that a user has been more helpful than Verizon and that Verizon appears to have stopped responding to these concerns altogether. It's infuriating to see so many complaints only to have Verizon try to pass off each one as unique, unrelated and previously unheard of. Verizon, it's time to stop treating your customers as fools, admit there is a problem and fix it.
Got the 8/1 security update last night for my Gal S5, said specifically to fix low energy connections, aND Polar H10 is working again.
After being told by Verizon rep they don't update phones over 2 years old I got a notice from Verizon that they needed to do an update on my phone. It was to fix the problem syncing to fitbit. Low and behold, I now can sync and update my fitbit! It only took 6 weeks to correct the problem, glad it's done. I hope your problem is solved as well.
