Dianne Hackborn wrote:
> Again, this code is using PRIVATE APIs. As we've said repeatedly, doing
> so is not safe, and you can expect your code to break in various ways as
> a result.[...]
Thank you, Dianne. I'm pretty sure that everyone involved in these two
Bluetooth projects are very much aware of this and try to make it clear
to the potential users too.
As I see it, the choice is between having basically no useful Bluetooth
API and to "boldy go where no man has gone before"...
Presumably, the main reason for changing that private API would be to
make a fully working public API. If (when) that happens everyone will be
happy. Until then, it should be reasonably safe to examine the build
number (and hw id etc) and see what can be done by hitting the metal, right?
Best / Jonas
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
