DisplayHUB Encoder for Android
Encoder Android device: captures HDMI through a USB dongle and streams it to players. It is not the controller. Use a separate Android device for the DisplayHUB Controller app. Both apps use the DisplayHUB logo and have distinct app names.
Standard Android installation: no factory reset, Device Owner enrollment or permanently enabled ADB required. Use only on a trusted network.
Version: 1.1.24 · Build: Release · SHA-256: 3e002846fb665889ffedd8aac086628af3b0e18cff7b0d326e722534723b4b65
- Download the APK on an ARM64 Android device running Android 8 or later.
- Open the downloaded file. If prompted, allow your browser or file manager to install this app.
- Connect the powered USB hub, HDMI capture dongle and HDMI source. Open DisplayHUB Encoder and grant the requested permissions.
- Complete the one-time setup screen. Accept USB permission and choose Always open DisplayHUB when offered. Optionally select DisplayHUB as the Home app to reopen after unlock.
- The Android device screen shows a live program preview, status, LAN browser addresses and basic resolution/FPS, bitrate, battery, battery temperature, CPU and thermal stats. Open http://DEVICE_IP:8080/ to configure capture and overlays. The controller is discovered on the LAN. Start at 720p30 and 4,000 kbps.
Capture starts automatically when DisplayHUB opens after setup; no browser Start button is needed. Startup and permissions stay in on-device setup. Wi-Fi uses Android settings; there is no Pi USB Power Control.
Android may still require an unlock, opening DisplayHUB, or USB approval after restart. Selecting DisplayHUB as the Home app helps it reopen after unlock. An Android device that shuts down with an empty battery may not power on automatically when charging resumes.
Browser updates download and verify the APK. Open DisplayHUB on the Android device and tap Install update, then approve the Android installer. In-app updates request a result-only installer without the redundant completion-screen Open button; use the app icon to reopen after replacement if needed. Initial browser installations still use the browser's system installer. Automatic downloads do not mean silent installation.
Double-click the browser title to check for updates, just as on the Pi. CPU shows encoder-app usage normalized across logical cores, not whole-device CPU. Input shows negotiated capture resolution/format/FPS; Output pace compares measured encoded FPS with the target. Hover over stats for explanations; counters Android cannot measure are hidden rather than guessed.
Android now develops independently of the Pi while sharing styling and branding. Open /overlays for the layered editor: text, graphics, video files and full web pages; drag/resize, ordering, visibility, opacity, rotation, undo/redo and live apply. Use a live HDMI input preview (2 fps) or simple backgrounds. Existing text migrates once. Some sites block embedded browser previews; Android opens URL layers directly, so check the program monitor.
Uploaded graphics: PNG/JPEG/GIF/WebP. Video: MP4/WebM supported by Android WebView, H.264/AAC MP4 recommended. Limits: 64 MB/file, 256 MB library, 24 layers including six video/web layers. Designs export/import as JSON; copy uploaded files separately when moving designs. Video audio starts disabled. In Selected layer > Video audio, enable an uploaded video's soundtrack and set volume from 0 to 100%. It mixes with HDMI audio, or plays alone if USB audio is disabled. Hidden layers are silent. The editor stays muted; sound goes into AAC/HLS and Opus/WebRTC, not the device speaker. Remote video URLs and web-page audio are not supported. Adding audio to a video-only stream briefly recovers the pipeline to add its audio tracks (up to about 20 seconds); subsequent volume/mute edits apply live. Lower levels when mixing to avoid clipping.
Open the centered Overlay Editor button below the preview. Drag any corner to resize or enable crop mode to trim a layer without stretching it; use the round handle to rotate and drag layer rows to reorder. Opacity fades the whole layer; color transparency (chroma key) removes a selected color with adjustable tolerance. Six bundled, licensed font families join the three system choices; fonts work offline. Settings groups live apply and design import/export. Apply errors identify the layer needing attention.
Resize and position the actual HDMI video in the designer, or choose the 80% ad-space preset, to leave room for venue graphics. Apply sends the layout to output. Full-frame / hide overlays immediately restores full-size HDMI and hides all overlays and their audio; Restore layout returns to the saved video size and layer selections. Applying another design does not cancel full-frame mode. Upgrade the controller too for clickable layer names and the same full-frame switch in dashboard, Matrix and remote views. Physical Wi-Fi-button pairing is not included.
EPG appears beside Overlay Editor when XMLTV lineup and API key are configured. Use Advanced Settings > App Updates to check/download development updates, then approve installation on the Android device. Future Play builds use Google Play instead of the website updater.
The EPG is at http://DEVICE_IP:8080/epg; it uses the encoder as a same-origin gateway to the discovered controller. The preview reconnects after capture recovers. Resolutions above Full HD show a player-compatibility warning: older players may need 1080p30 or 720p and moderate bitrates, regardless of encoder power.
Upgrade the Android controller as well for its corrected guide-fetch job and encoder management ports. The EPG's Fetch guide button reports progress and failures. XMLTV credentials and provider download limits apply; a valid cached guide is required.
Settings always includes a USB IR Blaster row below the connected-device IP field, for every device type. Choose either network (IP) control or USB IR control, not both; leave Connected device IP blank when using USB IR. The row opens IR settings when the TView USB IR transmitter (VID 10c4, PID 8468) is connected, or provides adapter information otherwise. Approve Android's USB access prompt before sending. The adapter is send-only and cannot learn or record IR commands. Installing Flipper IR-DB profiles requires internet access; the Xumo profile is bundled.
Resolution/rate choices come from decodable USB capture modes and the device's hardware H.264 codec, including 1080p60 when both advertise support. These are USB capabilities, not HDMI-source EDID; sustained USB bandwidth, input decoding, GPU load and heat still need qualification. The encoder discovers its controller on the LAN and proxies device scans, rather than using stale browser addresses. Startup setup stays on-device.
Measured health is green/yellow/red; unavailable sensors stay neutral. Output audio is the mixed signal level in dBFS, not CPU or USB load. 0 dBFS is full scale; quiet audio is normal, and sustained peaks near 0 risk clipping. App CPU alone cannot guarantee whole-device headroom.
Support through the Controller: when the encoder is registered with a reachable DisplayHUB controller, the controller's support connection provides encoder management and logs over the LAN. The Encoder APK has no separate support tunnel or direct-support controls.
Download rotating diagnostic logs at /api/diagnostics. The program JPEG preview refreshes up to twice per second while the encoder's device screen is visible, and approximately every five seconds otherwise. Stopped capture shows a placeholder; configured resolution/bitrate are marked as set values rather than live measurements.
Upgrading from 0.2.x: production uses a dedicated signing key, not the old debug key. Save the settings from the old browser interface, uninstall the old app once, then install this version and configure it again. Subsequent production updates preserve settings and use the same release key. Do not uninstall for normal 1.x updates.
This release supports USB HDMI input, hardware H.264, AAC/HLS, Opus/WebRTC and layered overlays with uploaded-video audio mixing. Primary file inputs, GPIO IR, SRT and Pi-specific maintenance commands are not implemented on Android. Unsupported controls are disabled or return an explicit error. HDMI HDCP compatibility depends on the source and capture hardware.
Android device/hub/capture combinations still require charging, thermal, audio synchronization and reboot qualification before unattended deployment.
The device screen also links to the equipment guide and has a small More about DisplayHUB footer.