Skip to content

Octopus Planet (Android - HW Encode)

Highlights

  1. Android-based (Khadas vim2 Android 9) with hardware encoding support
  2. Customized kernel, removes the 2.2G ISO size limit
  3. KVM software runs in a chroot container; most Debian packages work; Docker is not supported

Installation

Short pads

Short pads for the silver Octopus Flanet version:

Short pads (silver)

Short pads for the black Octopus Flanet version (discovered by the author):

Short pads (black)

Flashing

Insert the dual-headed USB cable into the USB port closer to HDMI. Open USB_Burning_Tool and load One-KVM_by-SilentWind_Octopus-Flanet_250315.burn.img, then short the flashing pads to start.

USB_Burning_Tool

Usage

KVM Remote Control

The USB port near HDMI supports OTG. Connect it to the target host. Connect the other USB port to the USB capture card.

The web UI listens on 4430, H.264 hardware encoding is supported.

web

The web terminal is supported. After installing htop in the terminal, you can see that H.264 uses Android MediaCodec via the FFmpeg API instead of CPU encoding.

terminal

Remote debugging

SSH is not installed; SSH connections are not supported.

Control the chroot system via the web terminal. Android supports ADB over network, for example:

1
2
3
4
5
6
# Connect ADB (example IP 192.168.10.104)
./adb.exe connect 192.168.10.104
# Android shell; "su" is available
./adb.exe shell
# Android screen casting
./scrcpy.exe

adb

Notes

As a technical validation, this image demonstrates a practical approach: for platforms lacking Linux hardware video encoding, you can switch to Android to gain hardware encoding and use it in production.

This image was last built on 2025-03-15. Due to low interest, planned SSH and Docker support were dropped; they are unsupported by default and likely won't be added later.