What Is RapidLaunch For Android?
Blue SDK RapidLaunch for Android is an Automotive-Grade Bluetooth stack for Android (AOSP). It replaces the default Android Bluetooth stack, while preserving the existing Android API and seamlessly integrating with the existing Android applications and services.
Based on OpenSynergy’s Blue SDK Bluetooth protocol stack and profiles, the leading Automotive Bluetooth solution for over 20 years, Blue SDK RapidLaunch for Android can easily handle complex use cases such as concurrent multiple profiles, multiple connections, dual-phonebook download, and more.
Why Does Android Need a Replacement Bluetooth Stack?
Automotive OEMs have specific functionality and behavior requirements that cannot be met by Android’s default Bluetooth stack.
Blue SDK RapidLaunch for Android adds the necessary flexibility, robustness, and functionality for Automotive OEMs, enabling full control over Bluetooth behavior, advanced functionality, and complex use cases, while offering superior stability. This empowers OEMs to solve a multitude of common, fundamental issues exhibited by Android’s Bluetooth stack for Automotive use cases.
Blue SDK RapidLaunch for Android restores control and predictability to Android’s Bluetooth behavior for an easy Automotive solution.
A Highly Configurable Bluetooth Solution for Android Automotive
With over 20 years of Bluetooth engineering leadership and hundreds of millions of devices shipped, Blue SDK enables functionality that other embedded Bluetooth stacks do not. When desired, Blue SDK RapidLaunch for Android can extend the Android Bluetooth API for additional features and functionality. Fully controllable connection management is provided via a flexible API that makes it possible to control exactly when profiles connect and reject incoming connection requests. Concurrent multi-profile capabilities provide the power to enable advanced functionality, such as parallel PBAP download sessions or even pausing these PBAP downloads while streaming music. Blue SDK RapidLaunch for Android provides total control: Limitation of database size to prevent crashes, usage of dual SCO connections to mix in-band ringtones with audio from an ongoing call, connection of multiple phones to a single IVI system, and ease support of many other highly complex use cases.
There are limitless ways that Blue SDK RapidLaunch for Android can tailor the Bluetooth behavior to even the most complex functionality requirements while having full confidence of retaining a high standard of interoperability and stability
Reduces Costs & Accelerates Time-To-Market
Attempting to modify the default Android Bluetooth stack leads to an unmanageable, costly, and time-consuming development path, which requires forking and upstreaming changes to the Android Open Source Project, along with difficult and costly maintenance.
Waiting on chipset vendors to provide support for Bluetooth and in the BSP wastes valuable development time and can quickly become costly engineering services. The need to pay for expensive chipsets in order to get the support needed further deepens the costs of chip vendor solutions. Furthermore, the investment in chip vendor engineering services on a specific platform causes OEMs to be locked-in with a single vendor’s hardware making it difficult and costly to ever move to other chip vendors.
Blue SDK RapidLaunch for Android eliminates all of these challenges, speeding up the overall development schedule while providing both a significant cost savings and better quality. Blue SDK RapidLaunch for Android’s hardware-agnostic design means you are free to move to other hardware with minimal effort. Blue SDK RapidLaunch for Android removes the development risks and constant maintenance of interoperable Automotive Bluetooth from engineering teams and enables them to focus on delivering new technologies and innovations.
Restores Control and Predictability to Android’s Bluetooth Behavior
Works with Any Hardware
Easy Android Integration
Decreases Cost and Time-To-Market