Google Drops Bluetooth API From Android 1.0

Ian Lamont writes "Google has dropped Bluetooth and the GTalkService instant messaging APIs from the set of tools for Android 1.0, but says that handsets using the Android OS will work with other Bluetooth devices such as headsets. According to a post on the official Android developer blog, Google dropped the Bluetooth API from the mobile OS because 'we plain ran out of time.' The GTalkService API was removed because of security concerns that included the possibility of applications revealing more details about users than they might want to let out, such as their real names and e-mail addresses."

Comments

I think I've seen this before

[bigtallmofo]

Google: The Microsoft of cell phones.

If they continue to follow the play book, next they'll drop several additional previously planned features and end by hiring a 90's sitcom star to convince people their product isn't as bad as they think.

Re:I think I've seen this before

[volpe]

Google: The Microsoft of cell phones.

You think Microsoft would drop a feature due to security concerns?

Re:I think I've seen this before

[mrsteveman1]

Apple has in fact severely limited bluetooth on the iPhone, and that includes even specific profiles for external devices. As far as i know the headset is the ONLY thing that works with it.

Re:I think I've seen this before

[justdaven]

Actually, no different. It uses the same profile

Huh?

[$RANDOMLUSER]

Google dropped the Bluetooth API from the mobile OS because 'we plain ran out of time.'

I don't get it. Aren't they going to Beta it for a couple of years?

Re:Huh?

[Van Cutter Romney]

Seriously, they can afford to Beta hosted applications running on their website and claim that if it crashed it was in "Beta". But software running on consumer devices? I don't think so.

Re:Huh?

[Colonel Korn]

The way Apple has locked down the iPhone may look draconian, but it also protects its users from all kinds of stuff you really don't want to worry about on your phone.

Like reliable reception?

So they say

[bockelboy]

Plain ran out of time? ... or CRAZY CONSPIRACY THEORY!?!

Re:Uh, bluetooth's kinda important for cell phones

[outZider]

If you read the article, you'd see the API was for third party applications to extend bluetooth. Android phones will be able to connect to headsets just fine, and a software update will add further support.

Re:Uh, bluetooth's kinda important for cell phones

[LWATCDR]

You should read the post link first.
"The 1.0 version of Android and the first devices will include support for Bluetooth; for instance, Android will support Bluetooth headsets."
So headset and I hope A2DP will be supported. I will also bet that some other other functionality like file transfers will be supported.

What will not be supported is direct access to the Bluetooth API to applications. So it will probably be impossible to write things like a bluetooth remote control for it :(. At least in the first release.
The thing is with APIs is if you don't get them right the first time you are left with supporting broken code forever OR you break a lot of apps.
See Windows for an example.

Android *will* have Bluetooth+IM

[jsharkey]

Android 1.0 phones *will* still have working Bluetooth and IM. This announcement is specifically referencing developer APIs that would allow hackers like us to do awesome stuff. Bluetooth headsets, etc and normal IM will work on Android just like we've always expected.

Re:How come developers never do this?

[jonnythan]

There's a reason companies don't just put up polls for decisions about how to develop products.

Customers don't know what they want, and most of the responders will not be people who have any intention of buying the product anyway.

iPhone doesn't have it either

[Anonymous Coward]

Does the iPhone have a Bluetooth API? Nope. Whats the big deal?

Re:IM and bluetooth

[Shade of Pyrrhus]

Read the summary. It's going to be on the handsets, but not accessible via the API. In other words, you can't develop a program that specifically uses bluetooth.
This doesn't mean you won't be able to have something like Skype, and use a bluetooth headset - that's simply the audio input/output that the device will use.

Bluetooth isn't really that big of a deal in this instance. I'd be interested in seeing what applications people would make that need to communicate via bluetooth, though - maybe some interesting games or computer-sync apps...

Verizon

[zubikov]

Verizon has consistently limited Bluetooth capability in all of their devices up to date. They do not want you to send messages and transfer files to/from their devices without charging you every step of the way. It's that simple. Oh, Verizon also happens to be a major backer of Android and is in cahoots with Google. Does anyone think there's a chance that there are external influences to this decision?

Re:Uh, bluetooth's kinda important for cell phones

[TheRaven64]

Headsets are a tiny fraction of what makes Bluetooth useful. Actually, it's a fraction I don't care about at all. OBEX is essential, because it's how you give people your phone number (send them your personal vCard via Bluetooth OBEX) - it's about three button presses on any recent phone. File Transfer is not essential, but is nice since it lets you browse the phone from a computer and copy files on and off it easily (photos, music, a copy of a map for somewhere you're going).