Some deployments need a single Player to show content across several monitors as one large screen. The Video Wall Configuration app, for Android Players with Rockchip hardware, lets you describe how the monitors are mounted and writes the matching configuration to the device, which then reboots with the picture split across the monitors.
How It Works
Video Wall Configuration is a small Android app. You set the number of monitors, the resolution and the arrangement. The app writes the matching configuration for the Rockchip hardware composer, which does the actual splitting of the image (Rockchip calls this feature splice). After the file is written, the device reboots.

App running on a 1 x 4 wall. The four monitors form one 7680 x 1080 screen, so the app, which sits in the middle of it, appears across monitors 2 and 3.
What Apply and reboot does
When you select Apply and reboot, the app runs these steps in order:
- Asks for confirmation.
- Makes the
/vendorpartition writable. - Saves the original file as
HwComposerEnv.xml.bak, only if no backup exists yet. The backup is never overwritten. - Saves a copy of the configuration that is active right now, used by the keep or revert step.
- Writes the new file next to the target, sets owner and mode, renames it over the target, then reads it back and compares.
- Sets
persist.vendor.framebuffer.mainto the canvas size, so the composer reports the whole wall to Android as the display size. The original value is saved once. - Clears any
wm sizeoverride. - Reboots. A full reboot is required because the composer only reads the file when it starts.
If any step up to step 5 fails, the app stops, shows the reason and the shell output, and does not reboot.
Keep or revert
After the reboot, once Android finishes starting, the app opens itself and asks Keep this layout? on every monitor of the wall. This prevents a layout that nobody can see, or one that is plainly wrong, from staying on the device. It also means an apply with nobody in front of the wall always rolls back.
Note: if nobody answers within 45 seconds, the app restores the configuration that was active before the apply and reboots the device.
Requirements
The app runs only on Android. It is not tied to a board maker and works wherever the firmware was built from Rockchip's Android kit with the splice feature included. The device must meet all of these requirements:
| Requirement | Why |
|---|---|
Rockchip firmware with HwComposerEnv.xml in /vendor/etc or /vendor
|
The Rockchip hardware composer reads this file and does the splitting. Without it, the app disables Apply and reboot. |
Root through su, usable by apps |
The file is on the read-only vendor partition. Platform signing alone is not enough. |
| Android 11 or newer | Minimum version of the app. |
| More than one video output enabled in the firmware | The app only offers the outputs the kernel reports. |
Note: a version of the app without root needs a firmware change, either a composer that reads the file from a writable location or a root helper service.
Install the App
Download the app on Download Link.
- Connect your computer to the Player with adb (ADB Connection Guide).
- Run
adb install -r Video-Wall-Configuration.apk. - Open the app once on the Player, so it can start by itself after a reboot.
Configure the Video Wall
The left side of the main screen holds three choices: number of monitors, resolution of each monitor, and arrangement. The right side shows the Wall preview, the Device panel, and the two actions, Restore original and Apply and reboot.

Under Monitors, select the number of monitors. The app offers up to 4, and never more than the number of outputs the device has.
Under Resolution of each monitor, select Full HD (1920 x 1080) or 4K (3840 x 2160). The resolution is the same for all monitors.
Under Arrangement, select the arrangement. The app lists every rectangular arrangement for the number you chose, for example 1 x 2 (side by side) and 2 x 1 (stacked). Sizes are written as rows x columns.

In the Wall preview, check the Total canvas. The preview is drawn to scale, and each cell shows the monitor number and the output that drives it.
To change the output of a monitor, select its cell and choose an output from the menu. If you choose an output that another monitor already uses, the app swaps the two. This fixes a wrong cable order without touching the cables. Narrow cells use short names, such as DP 1 for DisplayPort 1.

If needed, choose an output with nothing plugged in. These outputs are marked not connected and can still be selected.

Select Apply and reboot and confirm.
After the reboot, check the Keep this layout? question (see Confirm the Layout below) and select anywhere on the screen twice to keep the layout.
Note: while the app is open, it reads the list of outputs again every 3 seconds. Plug or pull a cable to find out which physical port is which output.
Read the Device Panel
- Connected outputs: what the kernel reports as connected.
- Configuration file: where
HwComposerEnv.xmlwas found. - Active canvas: the layout currently in the file on the device, which is not necessarily the one selected on the left.
- Backup state: whether the original configuration has been saved.
- Identify monitors: shown when a wall is active.
Identify monitors
Select Identify monitors to turn the whole canvas black and fill the slice of each output with its own color, the name of the output and the monitor number. Because the composer cuts the canvas the same way, every physical monitor shows which output drives it. The function labels the layout that is active on the device, not the one you are editing. Select anywhere to close it.

Confirm the Layout
After the reboot, the Keep this layout? question appears as a small card on each monitor, drawn over a pattern (frame, diagonals and a circle) that spans the whole canvas. When the monitors are in the right places, the lines carry on from one screen to the next.

- Each card shows Monitor N of M and the output, so a missing monitor is easy to notice.
- Keeping the layout takes two separate selections (click, tap or Enter). A double click counts as one.
- With no answer in 45 seconds, the app restores what was active before the apply and reboots.
Restore the Original Configuration
Select Restore original to put back HwComposerEnv.xml.bak and the saved framebuffer value, clear the wm size override and reboot. The backups are kept, so you can repeat the action.
Note: Restore original brings back whatever was on the device before the app first changed it. This is the factory state only if the device was untouched until then.
Files and Settings the App Touches
All files sit next to the configuration file. The app changes nothing else on the device.
| Item | Purpose |
|---|---|
HwComposerEnv.xml |
The layout read by the hardware composer. |
HwComposerEnv.xml.bak |
Original file, saved once. |
HwComposerEnv.xml.framebuffer.bak |
Original value of the framebuffer property, saved once. |
HwComposerEnv.xml.applied |
Marker: the active file was written by this app. |
HwComposerEnv.xml.pending |
Marker: the layout still waits for confirmation. |
HwComposerEnv.xml.previous and related files |
What was active before the last apply, removed once the layout is kept or reverted. |
persist.vendor.framebuffer.main |
Size the composer reports to Android. |
wm size override |
Normally cleared. Used only as a fallback when the property cannot be set. |
How the app finds the outputs
The app lists /sys/class/drm, where the kernel keeps one entry per output (for example card0-HDMI-A-1), and reads the status file of each entry. The type and number from those names are exactly what goes into the configuration file. Keep two points in mind:
- DSI outputs, and ports behind converter chips, often report connected whether or not a monitor is attached.
- A port that the firmware does not enable does not appear at all, even if the connector exists on the case.
Tested Devices
| Device | Outputs reported | Result |
|---|---|---|
Giada unit reporting model dn84
|
HDMI 1, HDMI 2, DisplayPort 1, DSI 1, all brought out as HDMI ports on the case | Side by side walls with 2, 3 and 4 Full HD monitors confirmed working. Photos 1 and 2 are from this unit. |
Sunchip AD-0160 (reports itself as X3588-i), Android 12, build AD_0160-V1.0-12-PAPPER-8K+DP-SW0.1-20221122
|
HDMI 1, DisplayPort 1, DSI 1 | The composer reads the file and crops HDMI 1 correctly. DisplayPort did not join the wall. Not resolved. |
On the Sunchip unit, the second HDMI output on the case is disabled in this firmware (device tree node hdmi@fdea0000), so you need a different firmware from the vendor to use it. The board also has an HDMI input.
Known Limits
- The app needs root.
- The app supports at most 4 monitors, all at the same resolution, Full HD or 4K only.
- On the Sunchip unit, DisplayPort stayed outside the wall and mirrored the whole canvas. The cause was not investigated.
- A Player app that starts at boot can cover the Keep this layout? question. The countdown keeps running behind it, so the layout reverts unless someone switches back to the app in time.
- On firmware that ignores the framebuffer property, the
wm sizefallback cannot exceed twice the size the composer reports. This is not enough for walls wider than two monitors. - The app only knows what the kernel reports. It cannot tell in advance whether a given output can take part in a wall.
Recover the Device with adb
adb keeps working whatever is on screen. On devices with the stock su, the syntax is su 0 <command>. Run these commands in order:
adb shell su 0 mount -o rw,remount /vendor
adb shell su 0 cp -p /vendor/etc/HwComposerEnv.xml.bak /vendor/etc/HwComposerEnv.xml
adb shell su 0 rm -f /vendor/etc/HwComposerEnv.xml.applied /vendor/etc/HwComposerEnv.xml.pending
adb shell su 0 cat /vendor/etc/HwComposerEnv.xml.framebuffer.bak
adb shell su 0 setprop persist.vendor.framebuffer.main <value printed by the previous line>
adb shell wm size reset
adb reboot
Useful checks on a new device:
adb shell ls /vendor/etc/HwComposerEnv.xml
adb shell getprop persist.vendor.framebuffer.main
adb shell grep . /sys/class/drm/card0-*/status
adb shell su 0 id
adb shell wm size
Troubleshooting
- Apply and reboot is disabled, or the app shows an error and does not reboot: the device does not meet a requirement. If Apply and reboot is disabled, the app did not find
HwComposerEnv.xmlin/vendor/etcor/vendor, or the firmware does not include the splice feature. Runadb shell ls /vendor/etc/HwComposerEnv.xml. If the file does not exist, the device needs a firmware built from Rockchip’s Android kit with splice included. If the app shows an error and does not reboot, one of the steps up to step 5 of the apply failed, for example because the app has no root access or cannot make/vendorwritable. Read the reason and the shell output on screen, and runadb shell su 0 idto confirm root. - The layout goes back to the previous one after the reboot: nobody answered Keep this layout? within 45 seconds, or a Player app that starts at boot covered the question. Stay in front of the wall during Apply and reboot and, if the Player app is in front, switch back to Video Wall Configuration before the countdown ends.
- The image is in the wrong order across the monitors: the cables are in a different order from the configuration. Open the app, select the monitor cell in the Wall preview and choose the correct output. Use Identify monitors to confirm which output drives each monitor.
- The device is left with a wrong layout or no usable picture: the applied layout cannot be reverted from the screen. Recover the device with adb, as described in Recover the Device with adb.