Turning an Android Phone into a BLE Beacon (iBeacon/Eddystone) Without Root

Why turn an Android phone into a BLE beacon?

Bluetooth Low Energy (BLE) beacons are tiny transmitters that broadcast a short identifier. Developers use them for indoor navigation, proximity‑based triggers, and IoT testing. Buying a dedicated beacon costs a few dollars, but you can prototype instantly with a device you already own. This tutorial shows how to make your Android phone act as an iBeacon (Apple’s format) or an Eddystone beacon (Google’s format) without any rooting or flashing.

Before you start

• Android version: 5.0 (Lollipop) or newer. The BLE advertising API was introduced in Android 5.0.
• Hardware support: The phone must support BLE advertising, not just scanning. Most mid‑range and flagship devices from 2015 onward do.
• Battery: Advertising runs continuously; keep the device plugged in or ensure a full charge.
• Permissions: Android 6.0+ requires location permission and, for scanning, location services must be turned on. Advertising itself only needs Bluetooth.
• Apps: We will use two free Play Store apps – Beacon Tools (for configuration) and nRF Connect (for verification). Both are lightweight and do not need root.

Understanding iBeacon vs. Eddystone

Both formats encode a UUID‑like identifier, but they differ in the fields they expose:

Choosing one over the other depends on the client app you plan to test. For pure Android development, Eddystone is often simpler because you can broadcast a URL directly.

Method 1 – Using Beacon Tools (recommended)

At this point your phone is acting as a BLE beacon. Any app that listens for iBeacon or Eddystone frames will receive the identifier you configured.

Why each step matters

• Location permission & services: Android treats BLE advertising as a potential location source. Without these, the system will silently block the broadcast.
• Tx Power: This value tells scanners how far away the beacon is. The default of -59 dBm works for most indoor tests; adjust only if you need a different range.
• Verification: Scanning with a second device confirms that the payload matches what you entered, preventing silent misconfiguration.

Method 2 – Using Bluetooth LE Advertiser (alternative app)

If you prefer a lighter app without the extra iBeacon/Eddystone UI, Bluetooth LE Advertiser (by app2sd) provides a raw advertising interface.

This method gives you full control over the raw bytes but requires you to construct the payload manually. It is useful when you need a custom frame that Beacon Tools does not expose.

Keeping the beacon alive

Android may pause advertising when the screen turns off or when the system applies battery‑optimisation policies. Follow these steps to ensure continuous broadcast:

• Disable battery optimisation for the advertising app. Settings > Apps > Beacon Tools > Battery > Unrestricted (or Allow background activity).
• Keep the device awake. In Settings > Developer options enable Stay awake (screen stays on while charging). If you cannot keep the screen on, use a small WakeLock‑type app to prevent deep sleep.
• Use a power source. Continuous BLE advertising draws ~10 mA; over many hours this can drain the battery noticeably.

Troubleshooting common issues

Beacon not visible on the scanner

• Bluetooth is off. Verify both devices have Bluetooth enabled.
• Location permission denied. Re‑open the advertising app and grant the permission.
• Location services disabled. On Android 6.0+ you must turn on Location for BLE scans; otherwise the scanner will see nothing.
• Device lacks advertising support. Some low‑cost phones can scan but cannot advertise. Check the spec or try a different device.
• Advertising stopped after screen off. Apply the "Keep the device awake" steps above.

Wrong payload appears

• Double‑check the UUID/Namespace you entered. A single transposition will make the beacon look different to the scanner.
• When using the raw advertiser, ensure the byte order (big‑endian) matches the specification.

App crashes or freezes while advertising

• Some manufacturers (e.g., Xiaomi, Huawei) add aggressive background‑task killers. Add the advertising app to the whitelist in Security > Battery manager or similar.
• Restart the phone to clear any stale HCI state, then start advertising again.

Regulatory and privacy considerations

BLE beacons broadcast in the 2.4 GHz ISM band, which is globally unlicensed, but you should still respect local regulations:

• Do not increase the transmit power beyond the device’s default – Android limits the power to safe levels.
• Avoid broadcasting personally identifiable information (e.g., a phone number) in the UUID. Use random or test‑specific identifiers.
• If you plan to deploy the beacon in a public space, inform nearby users that a Bluetooth signal is being emitted.

Practical use‑cases

• App development. Test proximity triggers without buying hardware.
• Indoor navigation prototypes. Simulate a network of beacons by placing several phones around a room.
• Education. Demonstrate BLE concepts in a classroom setting.
• Temporary event signage. Broadcast a URL that points to an event schedule, then turn off after the event.

Wrapping up

By following the steps above you can turn any compatible Android phone into a fully functional iBeacon or Eddystone beacon without rooting. The process is reversible – simply stop advertising in the app and, if desired, uninstall the app. This low‑cost approach lets developers and hobbyists iterate quickly, test proximity‑based features, and explore BLE fundamentals without purchasing dedicated hardware.