Troubleshooting
Common connection, pairing and update issues, and how to resolve them.
My device doesn't appear when I scan
Check the device is powered on and in range, Bluetooth LE has a short range, so bring the phone close. Make sure Bluetooth is on and that you granted the app Bluetooth permission. The app filters for ZeroTrace devices, so if nothing shows at all, the device may not be advertising: power-cycle it and scan again.
The app connects but shows the wrong screens
The app picks a screen set from the device's reported firmware type. A re-flashed or custom-firmware device that the app doesn't recognise falls back to the HID screen set on purpose, so it stays usable. A USBLogger seen over Bluetooth also appears under the HID-style view; review it through its own Wi-Fi web interface instead.
The connection keeps dropping
Bluetooth LE range is limited and affected by walls and interference. Keep the phone near the device. If a device disconnects, the app remembers it and reconnects when it is back in range.
A license key won't activate
Confirm you are scanning the QR for the device you are connected to, and that the device is connected. The app tells you the specific reason a key was rejected. See Licensing & activation.
A firmware update stopped partway
Keep the device powered, in range, and the app open for the whole update. If an update was interrupted, start it again from the device's firmware screen. See Firmware updates.
Wardriving has no map or route
Mapping needs location permission. The app asks for it when you start a wardrive; if you declined, capture still runs but there is no map. Grant location to the app and start the wardrive again. See Wardrive & location.
A USBLogger connects but I don't see a keystroke stream
That's expected, USBLogger has no dedicated screen in this app; it falls back to the HID-style view over Bluetooth. Its actual live keystroke review happens on its own on-device Wi-Fi web interface, not here. See USBLogger Live Mode.
I can't unlock the app after enabling app lock
App lock uses your phone's own biometric system. If Face ID, Touch ID or fingerprint fails or isn't set up, your phone's own passcode fallback applies, the app does not maintain a separate password. See App lock & biometrics.
The app shows an unfamiliar device model I didn't expect
If you re-flashed a device with custom or in-progress firmware, or connected hardware running firmware the app doesn't yet recognise, it will show under the HID screen set on purpose so it stays usable, rather than refusing to connect at all. This is not a bug, see Pairing & auto-detect.