Google employee Dan Morill of the Android Developer Blog has revealed that the first version of the Android platform to hit the market with a phone will not have OBEX or GAP Bluetooth profiles.
The omissions, preventing Bluetooth file transfers and Bluetooth device connection, are expected to come in a later version. Google was quick to allay accusations that the omissions were one of negligence, rather than for the sake of getting it right.
“Rather than ship a broken API that we knew was going to change a lot, we chose not to include it. We absolutely intend to support a Bluetooth API in a future release, although we don’t know exactly when that will be,” Morill said.
Planned features for the eventual inclusion of a Bluetooth API include:
- Bindings to GAP and SDP functionality.
- Access to RFCOMM and SCO sockets.
- Potentially, L2CAP socket support from Java. (This one is under consideration.)
- An API to our headset and hands-free profiles.

Post a comment
Tweet this
Share on Facebook
Print this article

RSS Feeds