These instructions are prepared for 1.1.4 build 51, the next planned release. Android logging and ZIP export were first included in build 42, with updated export colours in build 43. NFC scan links request GPS from build 44.
Use this when OnSight Support needs to investigate delayed Bluetooth detections or unexpected scan locations.
Record a short test
- Open Settings > Experimental > Scan diagnostics.
- Tap Start logging. The status changes to Logging is on.
- Return to Scan, turn GPS on and start scanning.
- Repeat the activity that caused the problem.
- Return to Scan diagnostics and tap Stop logging.
Start and Stop logging apply immediately. You do not need to tap Save for these controls. Logging starts off on a new installation. Once enabled, it stays enabled when you reopen the app until you turn it off.
Logging does not start Bluetooth scanning or turn GPS on. It records the activity that occurs while it is enabled. Background scanning is a separate setting.
Save or share the logs
Tap Save to phone to choose where to save the ZIP, or Share ZIP to open the phone's sharing options.
The ZIP contains:
- beacons.csv: Bluetooth observations, timing and the GPS position selected for each observation, when available.
- gps.csv: location fixes, speed and accuracy.
- battery.csv: available samples from experimental background scan sessions.
- raw: the original logs.
- metadata.json and README.txt: app version, counts and an explanation of the fields.
The files include precise locations, beacon identifiers and sensor readings. Share them only with the people who need them. Exporting does not send the files to OnSight automatically.
These local logs are separate from app usage analytics. From build 51, background usage analytics also count supported observations, GPS attachment and GPS fix freshness on Android and iPhone. Usage analytics exclude the beacon identifiers, GPS positions, sensor readings and raw logs in this export. The export does not include credentials or MQTT message payloads.
What the logs can tell you
The logs help compare when Bluetooth data was observed, when the app received it and which GPS fix was available. They do not correct scan locations or change upload behaviour.
Upload results in the logs describe submissions accepted by the phone's messaging client. Check Command to confirm that readings arrived.
Battery samples describe the whole phone. Charging, screen use and other apps affect them. Background scanning records battery samples independently of the Start/Stop logging control.
Storage and troubleshooting
Stopping logging keeps the collected files. The oldest records are replaced when storage limits are reached: an 8 MiB scan file plus one previous file, and a 2 MiB battery file plus one previous file. Export soon after the problem occurs.
- No logs yet: start logging, then run a short scan with GPS on.
- Some logs could not be saved: check the phone's free space and repeat the test.
- Could not export logs: free some space and try again.
- Save cancelled: the collected logs remain on the phone.
When contacting support, include the app version and build, phone model, Android version, time of the problem and what you expected to happen.
See Configure mobile gateway settings for background scanning and Use GPS tracking for location controls.