Obsolete
Status Update
No update yet.
Comments
sa...@google.com
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
Description
in addition to Lollipop and Bluetooth 4.0 hardware.
But the current solution offered by Google is to detect this hardware support for BLE advertiser (peripheral) at runtime and fallback.
As stated in this I/O video, BLE is designed for very different use cases. Falling back cannot be an option as Bluetooth classic API add overhead would require wildly different code.
In addition, detection at runtime means apps designed to only use BLE advertise mode cannot be sold in Play store (imagine a user buys the app, and the app says "sorry, turns out you don't a very specific BLE feature)
therefore please add a permission to the manifest to require Bluetooth LE Advertising so we can at least filter out such devices from a horrible user experience. There are already permissions for BLE but these do not cover BLE advertise filtering.