Thanks for the pointer. And apologies for the cc to your email. Joe.
On Sep 28, 6:03 pm, Dianne Hackborn <hack...@android.com> wrote: > Nick has posted about this fairly regularly either on android-platform or > android-porting. > > > > > > On Mon, Sep 28, 2009 at 4:50 AM, jdesbonnet <jdesbon...@gmail.com> wrote: > > > Dianne, > > > Is there any chance you or someone else on the Android project can > > make a statement (if even a vague one) about the Bluetooth API plans > > and timeline. You can see from the issue tracker (http:// > > code.google.com/p/android/issues/detail?id=1725) that there is much > > wailing and gnashing of teeth over this issue.... > > > Keep up the great work on Android: I'm really looking forward to the > > Bluetooth API (I have great plans for an app which requires bluetooth > > which is why I'm anxious to know). > > > Best regards, > > > Joe. > > > On Sep 16, 9:06 pm, windstorm <likunarmstr...@gmail.com> wrote: > > > Agree with Jonas. We are not trying to break Android's rule but, > > > sometimes we have to play with things or tricks or whatsoever for > > > keeping on using Google's phone which rocks but with suckingBluetooth. > > Otherwise we have to change the platform, which is the last > > > thing I wanna see. > > > > On Sep 16, 1:04 pm, "Jonas Petersson" <jonas.peters...@xms.se> wrote: > > > > > 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 > > > >Bluetoothprojects 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 usefulBluetooth > > > > 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 > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
