3 ms·

Android is getting a better BT stack for 4.3. Big improvements including LE and multimedia protocol (the name escapes me). Rumor has it, it was meant to be anno

Android is getting a better BT stack for 4.3. Big improvements including LE and multimedia protocol (the name escapes me). Rumor has it, it was meant to be announced yesterday. The Bluetooth group accidentally releasing something acknowledging new functionality in a new point release of Android (oops, not yet!)

HorizonXP 13y ago
AVRCP? Is that what you meant? I honestly haven't explored the Bluetooth stack too extensively, but I know the lack of a unified LE stack hurt a number of people I know developing products. And it will have ramifications for a long time due to the slow pace of OS updates on the platform. It's the decisions that Google made when implementing the Camera and MediaRecorder classes that hurt me the most, and will continue to for a long time going forward. What's easy on iOS and BlackBerry 10 is exceedingly difficult on Android. It's a PITA, but also a good thing for me since it makes the barrier to entry by my competitors much higher that I can rest a bit easier. And I can take a page from Google's book and port it back to older OS versions to fix it on all devices so that other devs can use it. Such are the pros and cons of the platform.
- drivebyacct2 13y ago
  I can't really speak to the other points in your post, I either don't know or have no experience, etc. That having been said, if you want more BT info, I can help :P edit: forget those links, I should've known to just seek out the Android Police article - most details including AVCHR or whatever it is: http://www.androidpolice.com/2013/05/15/bluetooth-low-energy-and-avrcp-1-3-coming-to-android-with-api-level-18/ http://www.androidpolice.com/2013/05/15/bluetooth-low-energy...
  - HorizonXP 13y ago
    Good to see this. But like I said, because they're so late to the party, the impact it has had on the peripheral and hardware scene will last for a few more years still.

HorizonXP 13y ago

AVRCP? Is that what you meant? I honestly haven't explored the Bluetooth stack too extensively, but I know the lack of a unified LE stack hurt a number of people I know developing products. And it will have ramifications for a long time due to the slow pace of OS updates on the platform. It's the decisions that Google made when implementing the Camera and MediaRecorder classes that hurt me the most, and will continue to for a long time going forward. What's easy on iOS and BlackBerry 10 is exceedingly difficult on Android. It's a PITA, but also a good thing for me since it makes the barrier to entry by my competitors much higher that I can rest a bit easier. And I can take a page from Google's book and port it back to older OS versions to fix it on all devices so that other devs can use it. Such are the pros and cons of the platform.

drivebyacct2 13y ago
I can't really speak to the other points in your post, I either don't know or have no experience, etc. That having been said, if you want more BT info, I can help :P edit: forget those links, I should've known to just seek out the Android Police article - most details including AVCHR or whatever it is: http://www.androidpolice.com/2013/05/15/bluetooth-low-energy-and-avrcp-1-3-coming-to-android-with-api-level-18/ http://www.androidpolice.com/2013/05/15/bluetooth-low-energy...
- HorizonXP 13y ago
  Good to see this. But like I said, because they're so late to the party, the impact it has had on the peripheral and hardware scene will last for a few more years still.