No offense, but one of the reason Bluetooth was removed from SDK is “timeline of getting certain Bluetooth profile implementation certified”. Bluetooth SIG certifies a Bluetooth product (read device), so we talking about “the phone” here. http://www.blueradios.com/Bluetooth_Global_Certification_Requirements.pdf The official certification process is available to Bluetooth SIG members at www.bleutooth.org For example, Apple had to go thru the certification process to have the iPhone listed here: http://www.bluetooth.com/Bluetooth/Products/Products/Product_Details.htm?ProductID=5777
There is only one Android phone that was announced and coming this fall: http://www.washingtonpost.com/wp-dyn/content/article/2008/08/18/AR2008081801201.html It is unclear when other Android devices will become available at retail. >From marketing standpoint, it is important to know if an application that uses RFCOMM to connect to a custom hardware via Bluetooth (e.g. SplashPlay from challenge Top 50) will be able to run on this phone immediately, in future or never. Both your and my questions are important. I hope Google will answer them all. On Aug 19, 3:30 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > viktor wrote: > > Which of the following is correct? > > 1. The phone does not have Bluetooth hardware. > > 2. The phone has disabled Bluetooth hardware that can be enabled with > > a future SDK update. > > 3. The phone has Bluetooth hardware and supports basic Bluetooth > > features such as pairing and RFCOMM. > > Arguably, none of the above, because there is no such thing as "*the* > phone" (emphasis mine). > > Android will most likely be used on a wide range of devices. These will > likely support various sets of Bluetooth profiles, no different than any > other phones made today. > > Many Bluetooth functions would likely work beneath the level of Android > applications, no different than with other smartphone operating systems. > For example, you don't have to be running some downloaded magical > Windows Mobile application to use the handsfree profile -- that's > handled solely by hardware and Windows Mobile itself. > > Given all that, *my* questions are: > > -- Which Bluetooth profiles will the Android OS handle on its own (given > hardware support for said profile)? > > -- What means do developers have for adding support for other Bluetooth > profiles not handled directly by the Android OS? If the answer is "not > at the application level, only by modifying the core Android OS", would > you consider addressing this scenario when writing up the documentation > for how the community can contribute back to Android, once it goes open > source? > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.1 Published! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new Android 0.9 SDK beta! http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
