DisplayHUB / Knowledge wiki

Build your first Android setup

Coming soon. The Android Controller and Encoder are currently in beta. Contact us for consideration into the beta program. Public APK downloads are paused; accepted testers receive installation instructions directly.

Plan the three roles

Use just one Android controller per location. Start with one separate Android encoder input and add as many HDMI inputs as you need as your network allows. Install a supported player per screen. Do not combine roles on a device.

Install the controller

Use an ARM64 Android 9+ device on reliable power. Once invited to the beta, follow the supplied Controller installation instructions, open the app, allow notifications, and permit background operation. First launch prepares the bundled runtime and can take several minutes.

Open http://displayhub.local:8081/ from the same trusted LAN, or use http://CONTROLLER_IP:8081/. Keep the port. Reserve its IP in your router. See controller.

Connect one encoder

Use an ARM64 Android 8+ device with USB host support, hardware H.264 encoding, compatible UVC capture, USB audio if required, and a powered hub that supports simultaneous data and charging. Once invited, follow the supplied Encoder installation instructions and complete the on-device permissions. See equipment and encoder.

Open http://ENCODER_IP:8080/. Confirm the controller address includes :8081. Start with 1080p30 (Full HD) at approximately 6,000 kbps when supported. Lower quality if the network or a player struggles.

Install a player and prove the path

Follow players, install the correct player app, and accept pairing prompts on the actual screen. Assign one source to one screen. Check video, sound, delay, charging, and heat before expanding.

Never expose the controller or encoder management ports to the public internet. Confirm commercial viewing and distribution rights with your source provider.

The browser dashboard is served locally, not from a public cloud service. Local control and available local-source playback can continue during an internet outage while the LAN and devices stay powered. Extended loss of license checks may cause a watermark. Internet-fed programming still needs internet.


Knowledge home | Getting started | Ask in Discord

Read-only public knowledge base, maintained through the site's deployment files. Powered by DokuWiki. Device and firmware behavior must be qualified on your actual equipment.