Google has dropped the Bluetooth and GTalkService instant messaging APIs (application program interfaces) from the set of tools for the first version of the mobile phone OS, Android 1.0, according to the Android Developers Blog. The company opted to drop the Bluetooth API because “we plain ran out of time,” said Nick Pelly, one of the Android engineers responsible for the Bluetooth API, on the blog posting. But the company made clear that handsets using the Android OS will work with other Bluetooth devices such as headsets, for example. Ed note: To be clear, only the APIs are delayed, not the features. This suggests third party apps will not be able to access these frameworks.
Google drops Bluetooth, GTalkService APIs from Android 1.0
Submitted by stonyandcher 2008-08-26 Wireless 11 Comments
It is a huge task that they’re undertaking! – so I think its fair enough, and reasonable explanation. Still a shame though.
Copying the iPhone I see, by having totally useless Bluetooth.
(If you can’t see the sarcasm above, please adjust your set)
You will be able to use your headset etc.
And those APIs will come in the future.
My guess is that the FCC had problems and so Google decided to drop the BT API for now.
For Bluetooth they disabled access to third party apps until it’s audited and hardened enough. It’s targeting mainstream public, security should be taken seriously.
For gtalk…I believe operators became nervous about free instant messaging, though this limitation could be very easily worked around with any kind of browser, but then it makes it not-installed-by-default (check IE share in the browser market:)) and much harder to integrate with phone functions like ringing, easy typing, popping up when active etc.
I hope both becomes in some form available in next version however (OTOH, it could become “forgotten”).