The main complaint now with the new v0.9 Android SDK released by Google is that there is no Bluetooth support.
Google stated in their documentation, due to significant API changes in the upstream open-source project and due to the timeline of getting certain Bluetooth profile implementations certified, a comprehensive Bluetooth API will not be possible or present in Android 1.0.
Mark Murphy commented in the Android Google Group:
There are roughly three levels of Bluetooth support, not two:
– hardware
– OS (supporting some Bluetooth profiles)
– application (using OS-provided APIs)
It would appear that Android 1.0 supports the first two, not the third.
It sounds like Google/OHA had an unpleasant choice: either ship without application-level Bluetooth and irritate a percentage of their developer base, or ship weeks or months later than planned and irritate the ENTIRE developer base. Frankly, I can’t blame them for the choice they made.
Other concerns mentioned in the developer community about the latest Android release:
Although this may all be trivial if Android enabled gPhones and their service network can consistently make calls which the much heralded iPhone seems to have issues doing since there has been a call for a class action lawsuit against Apple over this as well avoiding the Atari path described by Rob Enderle since iPhone’s Application Store is allowing so much crap to be made for it unless you need more cowbell.
Understandably Android is in the teething stage so missing a Bluetooth can happen, but this should be resolved on the hardware end or in short order.
What other Blogs are saying on this topic:
Google Android Apps & G1 Phone Tips News & Info
Loading ...
1 Comments
Subscribe to the Comments
Thanks for the quote!
Regarding Flash, does any mobile OS actually have Flash baked in? iPhone doesn’t, near as I can tell. Flash is available for WinMo but doesn’t ship with it from Microsoft AFAIK. Symbian, maybe? In other words, the fact that *Android* doesn’t have Flash is no different than other major mobile OS’s. Of course, Flash at least exists and is licensable on WinMo, whereas it may not exist yet for iPhone or Android.
The Flash engine is still closed source, IIRC, so Flash might still be a binary blob that Android handset makers might choose to load, or possibly carriers might choose to load — not sure how those decisions get made.
So while it’s certainly worth some grousing that Flash might not be on the HTC Dream, I’m not sure it’s apropos to deposit that problem on Android’s doorstep outright. Ditto GPS, if indeed the Dream is lacking that.
Now, the GTalk API removal, on top of the XMPP removal from the M5 SDK, is interesting. While none of that prevents developers from doing it themselves via third-party JARs, it’d be nice if we got a little more info on the “security concerns” so those who *do* roll their own don’t cause problems.
And I pray to the high heavens the Bluetooth isn’t screwed up more than I’m thinking it is…
Leave a comment
Get a Trackback link