Bluetooth 4.2 was released over a year ago. That’s the good news. But it’s still making its way very slowly to devices. Have you seen any real device using it?
iOS 9 is the most successful iOS update to date, with Apple reporting that around 52% of all iPhones are now running it. To the surprise of many, a lot of apps began crashing after users updated because of BLE changes in the release.
If you’ve read our previous article on developing Android apps with Bluetooth Low Energy (Bluetooth Smart), you know that developing an Android App can be more complicated than iOS. Android has had known issues with BLE support, but recent bug fixes and features have helped. Still, you have to make the right decision.
It’s no secret that Android has been difficult to work with when it comes to Bluetooth Low Energy. BLE support in Android has been problematic since Android 4.3 KitKat, with missing features, reliability issues, battery power drain and a lot of headaches for developers. Fortunately, Android 5.0 is better
Bluetooth Low Energy / BLE chipsets continue to evolve, with vendors constantly releasing new devices. We want to share some of the top trends we’ve seen in the chipsets that we’ve seen from vendor announcements, customer needs and our own experience developing products.
Plenty of vendors have announced new Bluetooth Low Energy devices. Nordic has just announced the new nRF52 series of devices, which take the popular nRF51 series to a new level. There’s a lot of excitement for these parts because they bring in better performance, lower power and more functionality.
TI has released a new family of Bluetooth and Wireless SoCs with the designation CC26xx and CC13xx which include the CC2640, CC2650, etc. These SoCs are MCU + Radio combo devices, similar to the CC2540 and CC2541 which are 8051 + BLE. The CC26xx focuses on 2.4GHz applications, while the CC13xx is intended for Sub-1GHz applications. The two families are highly cmopatible and include a Cortex-M3 ARM running at 48MHz dedicated to the application code.
Recently we were approached by a customer with a curious problem. They had an initial design for their product, but engineers were having a hard time getting it to work reliably past a few feet.