Google Releases the SDK For Version 1.6 of Android
Qwavel writes "This release includes improvements to the Android Market, the Search Framework, and Text-to-Speech. It now has support for more screen resolutions and CDMA phones. Android 1.6 is based on v2.6.29 of the Linux kernel and is expected in phones that will be available next month. The mystery of Android 1.6, however, is Google's continued unwillingness to commit to a Bluetooth API and any Bluetooth functionality beyond the basic audio functions."
From reading your post it seems the answer to my question is that Apple doesn't use a proprietary bluetooth protocol and you were mistaken in claiming they did. It's okay to admit it when you make a mistake.
If you want to create a peripheral or software that works with the Bluetooth of the iPhone or the iPod (excepting the basic audio peripherals) you have to apply for Apple's "Made for iPod Licensing" program.
Umm, that's a marketing program for developers. It lets you use Apple's trademarked terms and logos and gives you access to a bunch of developer docs for the iPod. It doesn't have anything to do with a proprietary protocol.
If you need a Bluetooth chipset supporting the Apple protocols you can buy them from CSR.
You mean the bluetooth protocol? You can get a bluetooth chipset from any number of suppliers. The one you linked to is marketing to people who want to work with iPods, but they are just bluetooth chips.
If Apple can achieve the sort of dominance in the consumer smartphone market that they have achieved with their iPods then this will pay off very well for them.
Umm, what will pay off for them? Charging people to join their "Made for iPod" marketing program? Actually, if Apple achieves dominance companies may stop using it since everyone will assume everything works with the iPod and not need to be reassured by a logo on the box.
...other companies phones won't be able to communicate with iPhones/iPods.
Umm. Wow. Why won't they be able to communicate with Apple phones? What exactly will be preventing them? I think you lost me again. Why don't you see if you can dig up anything to support your claim of a proprietary version of bluetooth and get back to me.
I'm sure that Google could have finalized their Bluetooth API by now if they wanted to.
The scary thing is the idea that Google might be considering going the same route as Apple: a proprietary Bluetooth protocol that they can license and control, rather then supporting the Bluetooth standards. That wouldn't be like Google, but it is otherwise hard to understand their hesitation.
yeah! and that way you can only connect to google web search bluetooth API. riiiigth.
apple sells crap expensive machines. they must lock you in.
Perhaps Google is hesitant to include a technology in Android that sucks as much as BT.