DisplayHUB / Knowledge wiki
This is an old revision of the document!
Table of Contents
Android controller setup
Dedicated local control
The controller manages discovery, screen assignments, network remotes, and configuration. It is not an HDMI encoder. Use a separate device for every role.
- Use ARM64 Android 9 or later and reliable charging.
- Download the signed Controller APK.
- Open the app; allow notifications and background operation.
- Wait for initial runtime preparation.
- Open
http://displayhub.local:8081/orhttp://CONTROLLER_IP:8081/on the same LAN. - Save a router DHCP reservation and use the full controller URL on encoders.
The .local address requires multicast DNS support and no conflicting hostname. For a .lan address, configure your router's local DNS yourself; the app does not set router DNS.
Android boundaries
Android-hosted management does not supply desktop ADB/SDB/SSH player deployment, Android TV/Fire TV ADB remote-key tooling, operating-system reboot, or router Wi-Fi administration. Use supported store/manual installation methods. Samsung first-use discovery remains device/firmware dependent and requires qualification.
Force-stop prevents normal automatic restart until you reopen the app. Boot/unlock behavior and manufacturer battery rules need real-device testing. Check power and background behavior.
Updates and support
Use App updates to check/download, then approve installation on the Android device. Keep the existing installation for normal production updates. Remote support is initiated from the controller only when instructed by a trusted agent.
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.
Start here