Editions report: differences, version codes, results, risks
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,72 @@
|
||||
# Household and Play editions: report (10 November 2026)
|
||||
|
||||
Code only. Nothing was signed or installed, and the real debug key, any future key, Google Play and both TVs were left
|
||||
alone. Branch `editions-0.127` (commit 11af81c8), built on `launch-server-0.126`.
|
||||
|
||||
## What differs between the editions
|
||||
|
||||
Both are `tv.orbit.classic`. Everything not listed here is the same code in both: Rooms discovery and joining, room
|
||||
sync, profiles and Who's watching, Taste, Continue Watching, the Arcade and its records, the Companion, the guide,
|
||||
channels and the player.
|
||||
|
||||
| | Household | Play |
|
||||
| --- | --- | --- |
|
||||
| Updates | From another room: Install? card, newer and same key only, Android confirms | Google Play only. Never looks, never offers, never fetches. |
|
||||
| Shares itself with other rooms (`/room/version`, `/room/orbit.apk`) | Yes | No. Another room asking gets "not found". |
|
||||
| `PackageInstaller` code | Yes | None in the bundle |
|
||||
| `REQUEST_INSTALL_PACKAGES` | Yes | Not in the manifest |
|
||||
| adb install check (snapshot, rollback copy, restore) | Yes (`InstallSnapshotReceiver`) | Not in the manifest or code |
|
||||
| adb test hooks (shadow comparison, provider and player switches, playback test, intro trial, series inspection) | Yes | None. Play keeps the saved setting, so those switches stay off. |
|
||||
| Playtest build | Household only | None |
|
||||
| versionName | `0.127.0` | `0.127.0-play` |
|
||||
| Signing | Unsigned | Unsigned (APK and .aab) |
|
||||
|
||||
How it's split: one `Edition` object per edition (`src/household`, `src/play`), called from the shared code in five
|
||||
places. The household-only files moved whole into `src/household` (RoomUpdates.kt, InstallSnapshot.kt,
|
||||
PlaybackTestActivity.kt), along with their tests (`src/testHousehold`).
|
||||
|
||||
## Version codes
|
||||
|
||||
`versionCode = build × 10 + channel`, where 0 is household, 2 is Play and 9 is a recovery build of that release.
|
||||
|
||||
| | Code | Notes |
|
||||
| --- | --- | --- |
|
||||
| Highest earlier household build | 323 | 0.126.0 (not installed) |
|
||||
| Reserved recovery build | 390 | 0.122.1 fix-forward. Still above both TVs' 322. |
|
||||
| **Build 40, household** | **400** | First under the scheme. Above everything, 390 included. |
|
||||
| **Build 40, Play** | **402** | |
|
||||
| Build 40, recovery slot | 409 | Above both editions of build 40, below build 41 |
|
||||
| Build 41 | 410 household, 412 Play | And so on |
|
||||
|
||||
A TV can go from household 400 to Play 402, or from Play 402 to household 410, and never needs a downgrade. The gate
|
||||
checks all 39 known codes (tools/known-version-codes.txt), plus every APK in the apks folder when it's there.
|
||||
|
||||
## Test results
|
||||
|
||||
- **Release gate:** passed. Household: 1,156 tests, 0 failures, 0 lint errors. Play: 1,144 tests (the 12 household-only tests aren't in it), 0 failures, 0 lint errors. The contract suite runs in both.
|
||||
- **What was built and inspected** (by `tools/check_editions.py`, run on the built files, with the bundle's own manifest converted by aapt2 and read back):
|
||||
- All three files are `tv.orbit.classic`. Household is 400, and the Play APK and bundle are 402.
|
||||
- The Play APK and bundle contain none of: PackageInstaller, RoomUpdates, ROOM_UPDATE, /room/orbit.apk, InstallSnapshotReceiver, INSTALL_SNAPSHOT, PlaybackTestActivity, orbit_play_test, the adb switch names, the playtest hook, or a server address.
|
||||
- The household APK still has its updater, install permission and install check.
|
||||
- RoomSync, Profiles, TasteEvent, ContinueWatching and the Arcade are in all three files.
|
||||
- None of the three is signed.
|
||||
- **The check catches mistakes:**
|
||||
- Given the household APK as the Play one, it failed on the codes, the permission and 11 hook names.
|
||||
- Given an old signed APK, it also failed on "signed".
|
||||
- **Manifests as built:** the Play APK declares MainActivity and two standard AndroidX components only. The household APK adds the install receiver and the playback-test activity.
|
||||
- SHA-256: household `c996a12e…8864`, Play APK `2e84e0c5…c8e`, Play bundle `513df60e…dcd`.
|
||||
|
||||
## Remaining risks
|
||||
|
||||
1. **Not run on a device yet.** The outputs are unsigned, so nothing can be installed until you approve signing. A run on the emulator, with a throwaway key on a copy, would need your OK too.
|
||||
2. **The 390 recovery build covers less from build 40.** It still covers both TVs (322) today. Once a TV is on 400 or above, 390 can't fix it forward. The replacement is a recovery build in the 9 slot (409 for build 40), made only when it's needed.
|
||||
3. **Play can't change the four adb switches** (provider catalogue, frame-rate matching, AVI, even volume). They stay at their saved value, which is off on a new install. If any should be available on Play, it needs a proper setting.
|
||||
4. **A TV that moves to Play loses the adb install check and restore.** Its own data and room sync are unaffected, but restore-tv.sh wouldn't work on it.
|
||||
5. **install-tv.sh expects a signed APK.** The next install needs the approved signing step first.
|
||||
6. **The key rotation and the Rooms updater still need settling.** It accepts only "exactly the same keys", so the first rotated build goes to each TV by adb (see the signing plan).
|
||||
7. **CI on Gitea** runs the new gate on this push. I'll report if it fails there.
|
||||
|
||||
## Next signing step I'd propose (needs your OK)
|
||||
|
||||
Checking the backups (you type the passphrases), then creating the new app signing key on your machine, away from this
|
||||
PC's agent-readable folders. Nothing else changes until then.
|
||||
Reference in New Issue
Block a user