Slashdot Mirror
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."
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.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
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.
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.
Help a man when he is in trouble and he will remember you when he is in trouble again.
Does the iPhone have a Bluetooth API? Nope. Whats the big deal?
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...
This isn't some CowboyNeal nonsense, this is about getting a product out in time for the Christmas buying frenzy. They have to get things done on time or there won't be any sales. A few missing features can always be added later, but if they don't sell any of those phones, they're done.
EagerEyes.org: Visualization and Visual Communication
They have to get FCC approval to be able to run their OS on consumer devices, this isn't some little program that people download and run on their machines. The idea of an open source mobile OS is a neat one in theory, but in practice it's just not that simple. The potential for exploits is huge, and with very severe consequences. 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.
EagerEyes.org: Visualization and Visual Communication
If this was MS, they would continue forward with the module and then either deny a security hole or call it a feature. MS does not include things that are absolute disasters, but they have included things that are known internally to be security disasters.
Gtalk was left out because of security. I highly doubt that Google would really want to leave out their own chat messenger from an OS they're releasing unless there was a pretty big reason to.
I'm not convinced that it was due to security concerns. I'd be willing to bet it's due to pressure from carriers. If Android's messenger were to catch on, carriers would say goodbye to text messaging revenue.
Hi, other A/C. I just wanted to say, "You're not convinced because you're not looking at the big picture."
This is an open phone, with a free, published SDK. The fact that they didn't do every detail of Open "just the way everyone else thought they should" is irrelevant. It's more than open enough to create whatever text messaging applications you want and forward your messages over Edge/Wifi. From release day forward there will be buggy little FOSS applications that do a poor job of this and they will get smoother and more polished over time.
If the little blue plastic clips on the bag of your store bought loaf of bread are too hard for you to operate, you can shake your fist at the sky and damn the bread companies for their obvious ploy to get you to waste bread... or you can think about the problem. No one can help you with that.
The idea of an open source mobile OS is a neat one in theory, but in practice it's just not that simple. The potential for exploits is huge, and with very severe consequences. 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.
As taken from the DRM lovers textbook. OSS software has been on unsecure networks for decades and if anything it's been more secure than the locked down stuff.
Not sure why you're complaining. This just means that a full release of Android will come sooner, and they can spend time ironing out the BT API while you're enjoying a bug-free release. They can always patch bluetooth in later with updates anyways.
As for Gtalk, even though I use gmail extensively, I hardly ever use gtalk, so it doesn't mean much to me. But as for your MS comparison, microsoft has no problem forcing you use win messenger no matter what the security implications behind it.
I highly doubt that Google would really want to leave out their own chat messenger from an OS they're releasing unless there was a pretty big reason to.
Nobody said they will be "leaving out their own chat messenger" - they said they will not include GTalkService API. I.e. you can not code a program utilizing gtalk services easily. That does not mean THEY (Google) can not code a chat messenger.