This is mostly correct. This seems to be a Samsung bug as it hasn't been confirmed on any other devices. While not all BLE devices are actually broken, most of them are. More specifically tho...
See more...
This is mostly correct. This seems to be a Samsung bug as it hasn't been confirmed on any other devices. While not all BLE devices are actually broken, most of them are. More specifically though the devices that are broken aren't doing anything wrong. They're simply not implementing behavior that is not required by the BLE specification. We've figured out how to fix this in our BLE device firmware but it's not something many companies would have the time and to figure out. (P.S. see the issue tracker on the google website). More importantly, this is something that worked fine according the BLE specification before and now it doesn't. Not sure what the process is of getting the bluetooth certification group to de-certify samsung but at this point it may be more effective than yelling in verizon forums. Seriously Verizon and Samsung, figure this out! No amount of restarting your phone, clearing cache, factory resets, toggling bluetooth, deleting apps, starting in safe mode will ever fix this issue. A phone firmware update is required to fix this. You've broken standard BLE and turned most 3rd party product into paper weights! You've also caused headache to all of these companies who now have to deal with customers yelling at them for breaking something that is clearly and demonstrably a problem with these samsung phones, specifically the note 4 and s5 with the July 1 security update.