the solstone app for android, with retained android hardware research and validation evidence.
the phone and Wear OS apps are maintained release targets. the Wear OS app lives in apps/wear. the older apps/watch, Rokid/RV203 glasses, and Rogbid sources remain parked historical evidence. See repository target status. The phone build configuration declares targetSdk 36.
apps/
validation-rogbid/ Parked android 9 watch validation evidence
wear/ Wear OS app
watch/ Parked older watch app source
phone/ Maintained phone app
glasses/ Parked smart-glasses/RV203 app source
core/ Shared app/link/domain modules as they graduate from the validation app
platform/ android framework adapters: camera, audio, location, foreground service, permissions, power
formfactor/ Watch/phone/glasses UI and policy helpers
testing/ Fake sensors, fixtures, and link harnesses
tools/rogbid/ Parked Rogbid hardware-evidence scripts
Prerequisites:
- JDK 17
- android SDK with API 36
- android build tools usable by Gradle
adbonPATHfor hardware validation
On the android build host, load the existing android environment first:
source ~/android-dev/env.sh
make installFrom a development machine with SSH access to an android build host, the root Makefile can sync the tree and run the same gate remotely:
ANDROID_REMOTE_HOST=host.local make android-host-ci./gradlew :apps:phone:assembleRealDebugThe broad CI aggregate retains compilation of shared and parked hardware sources as a safeguard; it does not designate them as maintained targets:
make ciTo build on a remote android host from this checkout:
ANDROID_REMOTE_HOST=host.local make android-host-ciThe maintained phone APK is produced at:
apps/phone/build/outputs/apk/real/debug/phone-real-debug.apk
See the string catalog guide before editing phone or Wear OS copy.
The Wear OS app requires API 30 or newer. Build it with:
./gradlew :apps:wear:assembleDebugUse the same application ID and signing key on the watch and phone for Data Layer communication. the watch holds sealed material until the phone acknowledges durable receipt; only the phone connects to the journal. a tile, complication, notification, reconnect, or reboot cannot start the microphone. phone and watch must both come from Google Play, or both from the direct download channel.
make test
make ciPhone validation uses make ci, make ci-device, and make hitl-phone. The retained tools/rogbid/* scripts document historical hardware evidence and are not a routine validation path.
The following Rogbid commands remain available only for manual inspection of the historical spike:
make validate-rogbid-adb
make validate-rogbid-media
make validate-rogbid-qr
PAIR_LINK='https://go.solstone.app/p#...' make validate-rogbid-plThe validation app package is app.solstone.validation.rogbid, a retained historical artifact. Installable solstone android artifacts use the app.solstone.* namespace.
AGPL-3.0-only. See LICENSE.
phone release commands default to the phone. use SURFACE=wear for the watch's
changelog and publishers, and the pull-wear-apk / pull-wear-aab build targets.
Wear uses its own changelog, wear-vX.Y.Z tags and
solstone-wear/release/ download stream. phone tags and downloads stay unchanged.
make wear-bump VERSION=x.y.z
make changelog-cut SURFACE=wear VERSION=x.y.z
make pull-wear-apk ANDROID_REMOTE_HOST=build-host
make pull-wear-aab ANDROID_REMOTE_HOST=build-host
make verify-bundle-binding SURFACE=wearfuture phone version codes are even, starting at 52; Wear codes are odd, starting at 51. each surface advances by two. codes 1–50 belong to historical phone builds. the direct APK and Play bundle of one release share its code.
tools/release/play.py --help describes the controller-side Play rail. set
PLAY_SERVICE_ACCOUNT to a private service-account JSON file on the controller;
never copy it to the build host. prepare stages a hash-checked bundle and a
single explicit track, then commit commits the saved edit while refusing to
cancel an existing review. credentials and evidence stay outside this repository.