Repository navigation
Android TV
Sideload the companion app onto an Android TV or Google TV set, let it download an engine for the television, and play streams from the remote in an installed player.
| Report | Details |
|---|---|
| Source | Outpace maintainers |
| Reported | 2026-11-14 |
| Versions | Android app v0.1.0 at the time; the steps below are for app v1.0.0 and later. Engine downloaded by the app (v1.0.2 or later on 32-bit sets). |
| Device | TCL 55T69C, Google TV (Android 12) |
| Player | VLC for Android |
| Works on | Android TV or Google TV sets and boxes with an ARM CPU (64-bit or 32-bit) and Android 5 or newer that allow USB debugging. x86 devices are not supported. |
The app is not on the Play Store, so a computer on the same network installs it with adb.
This is not the Termux install: the app manages
the engine for you.
- the television and a computer on the same LAN;
-
Android platform-tools (
adb) on the computer; - a video player on the television, such as VLC. The app has no player of its own.
From the Android app releases,
download outpace-android-<version>.apk and its .sha256 file. The examples use v1.0.0; use
the version you downloaded.
sha256sum -c outpace-android-1.0.0.apk.sha256 # Linux
shasum -a 256 -c outpace-android-1.0.0.apk.sha256 # macOSWindows PowerShell prints True when the hash matches (the comparison ignores case):
$hash = (Get-FileHash .\outpace-android-1.0.0.apk -Algorithm SHA256).Hash
$expected = (Get-Content .\outpace-android-1.0.0.apk.sha256 -Raw).Split()[0]
$hash -eq $expectedOn the television:
- Open Settings → System → About.
- Select Android TV OS build and press OK seven times, until the set says you are a developer.
- Go back to System → Developer options and turn on USB debugging.
Then check whether Developer options lists Wireless debugging. Which path you take depends on it:
| Developer options | How the computer connects |
|---|---|
| No Wireless debugging row (the TCL 55T69C) |
adb connect on port 5555; see 3a. |
| Wireless debugging listed | Pair first, then connect on the port the set shows; see 3b. |
Find the television's address under Settings → Network & Internet, or in the router's client
list. The examples use 192.0.2.10.
Not every set without Wireless debugging listens on port 5555. If adb connect is refused, the
set needs network ADB turned on once over a USB cable:
- Connect the set to the computer and accept Allow USB debugging? on the screen.
- Run
adb devicesand wait until the set is listed asdevice, notunauthorized. - Run
adb tcpip 5555, unplug the cable, and continue at 3a.
Televisions whose USB ports only accept storage cannot do this and need Wireless debugging instead.
adb connect 192.0.2.10:5555
adb devicesdevice means the television accepted this computer. unauthorized means it is waiting on an
Allow USB debugging? dialog.
That dialog is not drawn while the panel is off: a connection made in standby queues a prompt you cannot see. Turn the panel on, press Home, then Back until the dialog is in front, and choose Allow (tick Always allow from this computer if you will install again).
If Back never shows it, open Developer options → Revoke USB debugging authorizations, return
to Home, and run adb connect once. Each extra adb connect stacks another hidden prompt,
so dismiss the stack with Back before trying again.
Turn Wireless debugging on and open Pair device with pairing code. The screen shows a pairing address, a pairing port and a code. The ports below are examples; the pairing port and the connection port are different.
adb pair 192.0.2.10:37123 # enter the code when asked
adb connect 192.0.2.10:39555 # the connection port, not the pairing port
adb devicesThe connection is ready when the line says device; this path shows no Allow USB debugging?
dialog. Don't use Revoke USB debugging authorizations here: it removes the pairing, and you
pair again instead.
adb install -r outpace-android-1.0.0.apkOpen the app from the television's app row. The APK does not contain the engine, so Home shows Local engine not set up with a Configure button:
- Configure opens Settings. Under Local engine, choose Manage versions.
- Choose Install on the newest release. The app downloads the engine for this device (64-bit or 32-bit), checks it and selects it.
- Back in Settings, choose Start engine.
Start on boot is on by default on a television, so the engine comes back after the set restarts. If an Outpace engine already runs elsewhere on your network, for example the home server setup, choose Add a remote engine under Engine connection instead of installing one.
Play from Home or Search and pick the player in the chooser. Open as HLS suits
players that handle .m3u8 better than MPEG-TS. Recently played on Home restarts a stream
from the remote. The other screens are in the
app user guide.
USB debugging leaves port 5555 open on the LAN, and anyone who can reach the television can try to connect. Turn USB debugging (and Wireless debugging, if you used it) off once you are done installing. Playback needs neither.
- Menu names vary by brand. Look for Developer options under System or Device Preferences, and for the build number under About.
- A set whose OS is not Android (LG webOS, Samsung Tizen) cannot run the app. Run the engine on another device on the LAN, such as a router or a home server. Then cast to the television, or open the stream URL in its player.
- On a set with little RAM, turn on Low-memory mode in the app's engine settings. It applies the smaller buffers described in Routers and Small Devices.
- For quicker channel changes, set Startup buffer to Balanced or Fast. Shorter buffers stutter more on weak swarms.
This wiki is generated from docs/wiki/ in the main repository. To fix or improve a page, open a pull request there; the wiki is republished automatically when it merges, and edits made in the wiki web UI are overwritten.
Start
Watching
Publishing and peers
- Broadcasting
- Seeding and Peers
- Engine Camouflage
- NAT and Port Mapping
- Private Peer Mode
- Outbound Proxy
Running it
- Deployment
- Routers and Small Devices
- Migrating from AceStream Engine
- Support Sources and Operations
- Troubleshooting
- Releases and Versions
Success stories