Obsolete
Status Update
No update yet.
Comments
sa...@google.com
FYI. Here is a very hacky workaround.
I use appcompat support library quite a lot. Changing the compileSdkVersion only results in massive compile errors. If you are using appcompat-21, you must compile against api 21 or you will get compile errors.
This works fine if you are debugging against version 21. But when you are debugging on Jelly Bean (API 17), your debugger keeps dropping you to the API 21 source. Very annoying and hard to debug.
The solution I've ended up using is very hacky but works! Let's say you are trying to debug against API 17. Do the following:
1. mv $ANDROID_HOME/sources/android-21 $ANDROID_HOME/sources/android-21-orig
2. cp $ANDROID_HOME/sources/android-17 $ANDROID_HOME/sources/android-21
3. restart android studio so it will pick up the correct paths.
4. Debug
Just don't forget to put all the directories back after you're done.
I use appcompat support library quite a lot. Changing the compileSdkVersion only results in massive compile errors. If you are using appcompat-21, you must compile against api 21 or you will get compile errors.
This works fine if you are debugging against version 21. But when you are debugging on Jelly Bean (API 17), your debugger keeps dropping you to the API 21 source. Very annoying and hard to debug.
The solution I've ended up using is very hacky but works! Let's say you are trying to debug against API 17. Do the following:
1. mv $ANDROID_HOME/sources/android-21 $ANDROID_HOME/sources/android-21-orig
2. cp $ANDROID_HOME/sources/android-17 $ANDROID_HOME/sources/android-21
3. restart android studio so it will pick up the correct paths.
4. Debug
Just don't forget to put all the directories back after you're done.
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.