The Bluetooth and BLE scanner discovers nearby devices advertising over Bluetooth Low Energy, with optional classic discovery where supported. It can continue into device and GATT inspection.
How it works
BLE devices broadcast short advertisements that Android can report to an authorized app. Visibility depends on advertising intervals, radio conditions, permissions, and whether a device is currently discoverable.
How to use it in Network Toolkit
- Enable Bluetooth and grant the nearby-device permissions requested by Android.
- Start a scan and allow enough time for slower advertisers.
- Select a device using address, name, or signal context.
- Open device details to inspect available GATT information where permitted.
What information you can see
- Nearby BLE advertisements
- Device names or addresses when exposed
- Signal strength observations
- GATT services and characteristics when accessible
Common use cases
- Find a nearby BLE sensor
- Compare signal while positioning a device
- Inspect services during IoT development
- Confirm that a device is advertising
Limitations and Android considerations
Related network tools
Network Scanner for Android, MQTT Client for Android, WiFi Scanner for Android can help confirm the result from another angle.
Frequently asked questions
Why does a BLE device have no name?
A name is optional in advertisements and may only become available after connecting or resolving cached data.
Can signal strength measure exact distance?
No. RSSI changes with orientation, walls, interference, and device power; it is best used as a relative indicator.
Why are permissions required?
Modern Android versions protect nearby wireless discovery with dedicated permissions and platform controls.