DTRACTools and modules
| Item | Current setting |
|---|---|
| App module | :app |
| Gradle wrapper | 9.3.1 |
| Android Gradle Plugin | 9.1.0 |
| Kotlin | 2.3.0 |
| Java source/target compatibility | 17 |
| Android SDK | compile/target 36, min 30 |
| applicationId | com.hdil.datacollection |
Use the project's wrapper and version catalog. Java source compatibility and the Gradle JDK used by the build are distinct settings; check Android Studio's Gradle execution environment too.
Before building
- Prepare Android SDK 36 and a compatible Gradle JDK.
- Configure local development settings such as
sdk.dir. Obtain research-server configuration and service files from the study team. - Check the Samsung module's
libs/samsung-health-data-api-1.0.0.aardependency. - Align the study's UI, survey, collection, notification, and storage-mode assets.
- The debug signing configuration references
.android/debug.keystorein the user's home directory. Changing the signature can affect Samsung Health app verification.
Basic commands
Run from the repository root. These are build instructions, not a claim that a new Android build was validated during documentation work.
./gradlew :app:assembleDebug
To install on a connected device, enable its developer options and USB debugging first.
./gradlew :app:installDebug
App APK versus SDK artifact
A successful APK build does not establish that an external-app SDK can be distributed. Packaging a library with the original Samsung AAR has additional constraints. See the current assessment in the SDK integration plan.
Validation scope
After launch, verify enrollment, permissions, survey submission, local sensor/health records, and remote sync. Record release/R8, physical-device, and background collection validation separately from a debug compile result.