Accessibility Resource Center Skip to main content
iPhone 15. Newphoria. Get it on us. Online Only. No trade-in req'd. Limited time offer. Buy  |  Details.
end of navigation menu
3.2M Members 4,090 Members online 268K Discussions 43.9K Solutions

emilenl's Posts

SUSDAR30​ there is nothing wrong with the FitBit app or the FitBit itself. The problem lies completely within the Bluetooth part of the Android OS that has for some reason become broken with the ... See more...
SUSDAR30​ there is nothing wrong with the FitBit app or the FitBit itself. The problem lies completely within the Bluetooth part of the Android OS that has for some reason become broken with the latest OS update. The reason the FitBit doesn't work when you try to connect it to your computer while the phone is on is because the phone "steals" the connection to your FitBit. While the FitBit is connected to the phone, it can't connect to something else. Notice that what's broken is that the Bluetooth part in the Android OS doesn't notify the FitBit app that it's connected (as it should). That's why it doesn't work. You will probably have no luck trying out other BLE devices since the whole BLE part of this OS update is broken.
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. Connecti... See more...
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).