Hi, I did some reading today and compiled this overview of bluetooth profiles.
These are available in android 1.5: # 1.1 Advanced Audio Distribution Profile (A2DP) # 1.2 Audio/Video Remote Control Profile (AVRCP) These would be nice for all kinds of applications: # 1.3 Basic Imaging Profile (BIP) # 1.7 Device ID Profile (DID) # 1.10 File Transfer Profile (FTP) # 1.13 Generic Object Exchange Profile (GOEP) # 1.16 Human Interface Device Profile (HID) # 1.21 Personal Area Networking Profile (PAN) or the older # 1.19 LAN Access Profile (LAP) # 1.20 Object Push Profile (OPP) # 1.22 Phone Book Access Profile (PBAP, PBA[1]) # 1.23 Serial Port Profile (SPP) # 1.24 Service Discovery Application Profile (SDAP) # 1.25 SIM Access Profile (SAP, SIM) # 1.26 Synchronisation Profile (SYNCH) ( as seen on: http://en.wikipedia.org/wiki/Bluetooth_profile ) Which profiles will be made available in the next android version and which will never be available? Philipp > Mark summed it up pretty well. We don't have support in the SDK for > Bluetooth right now. Getting some Bluetooth API's published in the SDK > is a priority for the Android Bluetooth team. I can't wait to see the > apps you guys come up with! > > Nick > > On Sun, May 3, 2009 at 6:05 PM, Mark Murphy <[email protected]> wrote: > > moa wrote: > >> Can someone explain the current situation with bluetooth from a > >> developer point? > > > > Android supports Bluetooth. It incorporates several profiles -- Android > > 1.5 adds A2DP, for example. > > > > Firmware developers can add additional Bluetooth support, either for > > their own devices or as contributions back to the open source project. > > > > Application (SDK) developers cannot interact with the Bluetooth hardware > > in any significant fashion. > > > >> I take it the latest 1.5 version still does not have development of > >> bluetooth apps? > > > > AFAIK, that is correct. > > > >> If not, when is this going to happen? > > > > http://android-developers.blogspot.com/2008/08/some-information-on-apis-r > >emoved-in.html > > > > Obviously, they weren't able to devote sufficient engineering time in > > the cupcake timeframe to address their security concerns. > > > >> I saw some post about it being available via compiling the framework, > >> what does this mean? Does this mean an app can be done that uses > >> bluetooth or is this just for developemt only? > > > > It means that device manufacturers or people contributing changes to the > > firmware via the open source project can do more with Bluetooth. > > However, those changes are distributed as firmware updates or > > deployments, not in the form of APKs downloaded off of markets. > > > > Learn more at: > > > > http://source.android.com > > > >> I am only just starting to look at Android, so totally new to this. > >> However, if I can't do bluetooth SPP connections then it's no use to > >> me for what I want, so I'll not bother for now. > > > > There may be ways you can help get the Bluetooth support you seek, but > > questions like that are best asked on a discussion list related to the > > open source project: > > > > http://source.android.com/discuss > > > > Otherwise, hope for BlueZ to be available in the SDK in the next release. > > > > -- > > Mark Murphy (a Commons Guy) > > http://commonsware.com | http://twitter.com/commonsguy > > > > _The Busy Coder's Guide to Android Development_ Version 2.0 Available! > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
