Classic and Low Energy based profiles differ substantially. Platform implementations may support only one or the other, even though several classes have interfaces for both, e.g.
Chrome OS and Linux are supported via BlueZ, see
Initial implementation OWNERS were firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, and email@example.com. They no longer contribute to chromium fulltime. They were responsible for support for Chrome OS Bluetooth features and the Chrome Apps APIs:
Active development in 2015 & 2016 is focused on enabling GATT features for:
Known future work is tracked in the Refactoring meta issue.
The android implementation requires crossing from C++ to Java using JNI.
Object ownership is rooted in the C++ classes, starting with the Adapter, which owns Devices, Services, etc. Java counter parts interface with the Android Bluetooth objects. E.g.
For testing, the Android objects are wrapped in:
and fakes implemented in:
Fake objects are controlled by