DTRACMatch permissions to collection
Check permissions against the study's selected items. A manifest declaration does not prove that a participant granted access or that records were collected.
| Purpose | Permission or condition to check |
|---|---|
| Location | ACCESS_FINE_LOCATION and location services |
| Network/call state | READ_PHONE_STATE |
| Voice responses | RECORD_AUDIO |
| Notifications | Notification access for the Android version and channel settings |
| Precise scheduling | Exact-alarm availability and related settings |
| Sensor foreground service | `health |
| Samsung Health | Data read access granted through Samsung Health |
| Health Connect | Per-record read access and feature availability |
Bluetooth and Wi-Fi code use additional permissions, but neither is in the baseline sensor list. Check them separately if enabled by a study.
Background behavior
Sensors use a foreground service and startup/restart paths. Several collectors start with a 60,000ms window. This is not a system guarantee of one-minute execution in every condition. Android applies restrictions to starting foreground services from the background.
Test the research device with the screen off, the app in the background, and after a reboot. Resumption after force-stop or manufacturer battery management requires device-specific validation.
When records are missing
- Check whether the collection item is in the study configuration and allowlist.
- Check revoked permissions and disabled location services.
- Confirm that health records exist in Samsung Health or Health Connect first.
- Check whether a sensor batch has
sampleCountzero and whether its payload contains a measurement. - Separate local collection failures from server synchronization failures.
Participant information
The study team should explain what is collected and why, storage destinations, how to stop participation, and how to contact the team. This documentation describes implementation behavior; it does not replace a study consent document or privacy policy.