jeena/jtube-tv
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

docs: Agent container emulator workflow

Browse source 
Document how the host emulator is driven over adb from the agent
container: the start script now boots headless by default and trusts
remote adb keys via ADB_VENDOR_KEYS at launch, since the TV system
image is a user build that blocks pushing keys to adb_keys after boot.
AGENTS.md points to the new doc and fixes the stale SDK path.
This commit is contained in:
Jeena 2026-10-12 09:42:08 +00:00
parent ed65b77e90
commit 40a9d1e2c6
3 changed files with 93 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

7
AGENTS.md
View file

@ -5,7 +5,12 @@ for TV) that talks to a PeerTube instance over its REST API v1.
## Environment facts
- Host is Arch Linux with Android SDK at `~/Android/Sdk` (platforms 34/35/36, build-tools).
- Host is Arch Linux. The Android SDK the build actually uses is `/opt/android-sdk`
(`ANDROID_SDK_ROOT` — note `local.properties`' `sdk.dir` points to the outdated
`~/Android/Sdk`, which doesn't exist; platforms 34/35/36, build-tools).
- Emulator testing (host emulator + agent container over adb): see
`docs/agent-container.md` — covers start script, ports, and what to reinstall
after a container rebuild.
- The Gradle wrapper is checked in (`gradlew` + `gradle/wrapper/`), so builds need only a
JDK 17+ (`java`) on PATH. If `java` is missing, tell the user — do not install things on
the host without asking.