The leading library for detecting beacons on Android.
What Does This Library Do?
It allows Android devices to use beacons much like iOS devices do. An app can request to get notifications when one or more beacons appear or disappear. An app can also request to get a ranging update from one or more beacons at a frequency of approximately 1Hz. It also allows Android 5.0 devices to send beacon transmissions, even in the background.
What kinds of beacons does it detect?
The library may be configured to detect a wide variety of beacons. By default, it detects beacons meeting the open AltBeacon standard, but it can be easily configured to work with the most popular beacon types on the market. See the documentation for the BeaconParser class for more info.
New: Eddystone-EID Support is in the the 2.8.1-beta1 version. Read more here.
Library versions 2.3.5 and higher provide full support for Eddystone™, the new beacon format from Google. The library will wake up your app when it detects Eddystone-compatible beacons in the background and provides regular ranging updates while they are in the vicinity. Eddystone-UID (identifier frame), Eddystone-TLM (telemetry frame) and Eddystone-URL (URL frame) are all detected and decoded. Details are here.
Who uses this library?
Over 4,000 mobile applications use the Android Beacon Library, including some of the world’s biggest brands. These apps have over 150 million installations.
What devices can detect beacons?
Any device with Android 4.3+ and a Bluetooth Low Energy chipset can detect beacons with this library. As of June 2015, this is approximately 56 percent of Android devices according to the Google Play Store and growing quickly.
To transmit as a beacon, Android 5.0+ and firmware supporting Bluetooth Low Energy Peripheral Mode are required. As of May 2015, only a few dozen devices are known to have firmware that supports Bluetooth Low Energy Peripheral Mode.
Changes from the 0.x Library
This library has changed significantly from the 0.x library version and is now designed to work with open AltBeacons which fully support Android without any intellectual property restrictions. For more information on how to migrate projects using the 0.x APIs to the 2.x APIs, see API migration.