Slashdot Mirror
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."
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.
http://developer.apple.com/ipod/apply.html
If you need a Bluetooth chipset supporting the Apple protocols you can buy them from CSR.
http://www.embeddedstar.com/weblog/2009/07/28/csr-ipod-touch/
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. They will make money from licensing and other companies phones won't be able to communicate with iPhones/iPods.
On the other hand, whether they are successful or not, this is bad for their users. This being /. I probably don't have to explain why standards are good.
At this time, if you want to e.g. sell a Bluetooth garage door opener for smartphones (yes, this really exists) you could support it on RIM, Nokia, MS, and even some LG and Samsung phones. I hope that Android phones join this camp.
I'm interested to see some of the things that people will do with Bluetooth now that the quality of the hardware and software support is getting good enough (it wasn't good enough on a lot of the older phones). It would be sad if the lure of proprietary were to curtail the potential of Bluetooth.