Buried deep in the list of new features revealed for the L release of Android, whenever that comes out and whatever it will be called when it is, was BLE Peripheral Mode. This addition to Android is part of the Bluetooth Low Energy profile. Previous versions of Android could use BLE-enabled devices, but only as a primary device. The newly-enabled Peripheral Mode should allow apps on any Android phone, tablet, or what have you to send data to other devices.
It's no secret that Bluetooth has been a problem child for Android, plagued with poor audio quality and connectivity issues. I've already covered a handful of common problems in a previous post, but another issue has been emerging in the last few months that threatens to virtually kill all Bluetooth operation on a device in the right conditions. The culprit is a nasty little oversight in the Bluetooth Low-Energy code added with Android 4.3 Jelly Bean.
It's 4 a.m., I just read the 6th mention of the same misleading story in the last 24 hours, and it's time for a rant.
Yesterday, several "independent" reports all claiming to arrive at the same conclusion at the same time (does anyone properly credit their sources anymore?) appeared on the web suggesting HTC had just (*gasp*) leaked two new Android 4.3 features: Bluetooth Low-Energy and OpenGL ES 3.0. And it's done so via a public meetup organized by the San Francisco Android User Group.
For quite some time, we've been hearing about the potential advantages of the Bluetooth Low Energy (BLE) spec, and a seemingly endless list of gadgets that could benefit from it. Unfortunately, while many modern flagship devices are equipped with the necessary hardware, Google has allowed the Android OS to languish without official support for the standard. Most of the top OEMs have built their own proprietary versions for the energy efficient protocol, but until now, only Motorola has freely shared access to its API.