Obsolete
Status Update
No update yet.
Comments
jg...@gmail.com
[Comment deleted]
jg...@gmail.com
Upvote. Not only should the documentation include the list of BLE devices that support peripheral role, the guide at (http://developer.android.com/guide/topics/connectivity/bluetooth-le.html ) should be updated as it uses classes that no longer exist, e.g.: 'BluetoothAdapter.LeScanCallback' deprecated in favor of 'ScanCallback'. The whole guide should be updated.
pr...@gmail.com
These guys seem to be doing what Google should really be doing, though they rely on users contributing data by installing their app.
http://altbeacon.github.io/android-beacon-library/beacon-transmitter-devices.html
Surely this information is already harvested by Google via Google Play Services... I feel there is a device database Google holds, as how else would
1) you get stats on top devices that have installed your app (Google Play Dev Console)
2) Google analytics displays similar device install stats... and includes a stock picture of the device mode :/
Interesting uses of BLE API can't really take off unless traction is gained, and accurate info is provided.
Surely this information is already harvested by Google via Google Play Services... I feel there is a device database Google holds, as how else would
1) you get stats on top devices that have installed your app (Google Play Dev Console)
2) Google analytics displays similar device install stats... and includes a stock picture of the device mode :/
Interesting uses of BLE API can't really take off unless traction is gained, and accurate info is provided.
pr...@gmail.com
Added a request for additional manifest permission for BLE advertising ... so we can at least filter out devices without BLE advertising support.
https://code.google.com/p/android/issues/detail?id=183332
cl...@gmail.com
Upvote.
jo...@google.com
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
Does not mention BLE advertising is hardware dependent. A device may support BLE but might not support peripheral role. There is an indication of such limitation in the method description
But this really isn't enough and is the only mention. Other more visible documentation suggests all API level 21 devices can act as peripheral.
Examples:
"In Android 5.0, an Android device can now act as a Bluetooth LE peripheral device. Apps can use this capability to make their presence known to nearby devices. For instance, you can build apps that allow a device to function as a pedometer or health monitor and communicate its data with another Bluetooth LE device."
The misleading documentation should be updated to include a list of BLE devices that support peripheral role.