BLE Console FAQ
What is BLE Developer Console?
A mobile Bluetooth Low Energy development utility that can advertise configurable services, scan nearby devices, connect to supported peripherals, receive characteristic values, and send test payloads.
Is an account required?
No. The current version does not require registration or sign-in.
Does the app upload my BLE data?
No. Peripheral profiles, payload history, and activity logs are not uploaded to Jethva servers.
Where is my information stored?
Profiles, sent payload history, and activity logs are stored locally within the app on your device.
How do I delete my information?
Delete individual peripheral profiles, clear the Logs screen, clear the app’s storage in Android settings, or uninstall the app.
Does the app track my location?
No. Some Android versions require Location permission or enabled Location Services to discover BLE devices, but the app does not determine or upload your geographic location.
Why does Android request Nearby Devices access?
Android requires Bluetooth Scan, Connect, and Advertise permissions for core BLE functionality.
Can an iPhone act as a BLE peripheral?
Supported iPhones and iPads can advertise BLE services through Core Bluetooth. Background behavior and advertising details may be restricted by iOS.
Can every Android phone advertise as a peripheral?
No. Peripheral mode requires hardware and operating-system support for BLE advertising. Some devices can scan and connect but cannot advertise.
Why can’t another device find my peripheral?
Confirm advertising and Bluetooth are active, keep devices close, verify permissions and your service UUID, and make sure the peripheral is not already connected elsewhere.
What do Connected and Ready mean?
Connected means a central established a BLE connection. Ready means at least one connected central subscribed to the configured characteristic and can receive notifications or indications.
Why did payload delivery fail?
The central may have disconnected, not subscribed, moved out of range, rejected the payload size, or not implemented the app’s acknowledgement protocol.
Does acknowledgement work with every BLE device?
No. Generic BLE devices may receive a payload without understanding BLE Developer Console’s application-level acknowledgement format.
Which UUID formats are accepted?
Standard 16-bit, 32-bit, and 128-bit BLE UUIDs are accepted. Short UUIDs are normalized to the Bluetooth base format.
Does the app support binary payloads?
The current interface is primarily designed for text. Received non-UTF-8 characteristic values may be displayed as hexadecimal data.
How many logs are retained?
Up to 100 recent activity-log entries and 100 recent sent-payload records are retained locally.
Can I use it with production equipment?
Use caution. Connect only to equipment you own or are authorized to test, and verify commands against the manufacturer’s protocol.
Does it work in the background?
iOS and Android background behavior remains subject to operating-system scheduling, Bluetooth restrictions, and manufacturer battery policies.