Repository navigation
v1.3.2.0
Two APKs — install BOTH
| APK | Package | Role |
|---|---|---|
bladewatch-service-host-* |
net.bladewatch.app |
Daemons, receivers, BYD integration. No launcher icon. |
bladewatch-ui-* |
net.bladewatch.flutter |
The in-car UI. The only launcher icon. |
These are UNSIGNED and cannot be installed as-is
Sign both with the same key before installing. The two packages share
one UID via android:sharedUserId, which only resolves when their signing
certificates are identical — the daemon authorises its loopback IPC by peer
UID, so a mismatched pair installs and then fails to talk to itself.
for f in bladewatch-*-unsigned.apk; do
apksigner sign --ks release.jks --ks-key-alias key0 \
--out "${f%-unsigned.apk}.apk" "$f"
done
# both digests must match:
apksigner verify --print-certs bladewatch-*-arm64-v8a.apk | grep 'SHA-256 digest'Adding sharedUserId changes the UID, so the first install after switching
keys needs an uninstall of both packages, not an upgrade. See CLAUDE.md for
the daemon-stop procedure and the ADB-key preservation recipe.
What's Changed
- v1.3.2.0: complete Java to Kotlin service host, plus vehicle/UI fixes verified on device by @andrewloable in #6
Full Changelog: v1.3.1.0...v1.3.2.0