Repository navigation
Community Apps
For more details, please refer to this issue. I’ll keep it updated regularly. Community Apps
Native apps and homebrew that have been verified to work on clone devices running (d)ArkOS4Clone. Every entry lists the exact device and DTB it was tested on, so you know what to expect before installing.
Emulators and game ports are not listed here — this page is for standalone apps built for these devices.
| App | What it is | Tested on | Install |
|---|---|---|---|
| Pocket Clawd | A virtual pet that reacts to your Claude Code usage. Framebuffer + evdev, stdlib-only Python, no packages needed. | R36S-branded K36 clone, k36 DTB |
install/install.sh from the repo — adds a carousel entry, backs up es_systems.cfg, ships an uninstaller |
| Runner Protocol | An extraction game driven by your real Claude Code usage limits. Includes an offline demo mode (press Y), so it runs without any PC setup. | R36S-branded K36 clone, k36 DTB |
install/install-carousel.sh from the repo, or as a PortMaster port (submission in progress) |
Both apps need a 640x480 panel at 32bpp (the standard clone panel) and
use the system's python3 — nothing is installed into the OS.
- Wi-Fi: many clone dongles can't join 5GHz/WPA2-3 networks. A PC's 2.4GHz mobile hotspot works well as an alternative — both apps above document this setup in their READMEs.
-
Buttons: clones often report SELECT/START as
BTN_TRIGGER_HAPPY1/2(codes 704/705) instead of the standard 314/315. Both apps handle this out of the box; if you're writing your own app, handle both.
Tested something on a clone? Add a row above with:
- App — link to the source
- What it is — one line
- Tested on — device branding, clone type and DTB (identify yours with the DTB Analysis Tool)
- Install — how it gets onto the device
Apps should state their panel/firmware requirements honestly — "works on my device" with the device named beats a broad claim.# Community Apps
Native apps and homebrew that have been verified to work on clone devices running (d)ArkOS4Clone. Every entry lists the exact device and DTB it was tested on, so you know what to expect before installing.
Emulators and game ports are not listed here — this page is for standalone apps built for these devices.
| App | What it is | Tested on | Install |
|---|---|---|---|
| Pocket Clawd | A virtual pet that reacts to your Claude Code usage. Framebuffer + evdev, stdlib-only Python, no packages needed. | R36S-branded K36 clone, k36 DTB |
install/install.sh from the repo — adds a carousel entry, backs up es_systems.cfg, ships an uninstaller |
| Runner Protocol | An extraction game driven by your real Claude Code usage limits. Includes an offline demo mode (press Y), so it runs without any PC setup. | R36S-branded K36 clone, k36 DTB |
install/install-carousel.sh from the repo, or as a PortMaster port (submission in progress) |
Both apps need a 640x480 panel at 32bpp (the standard clone panel) and
use the system's python3 — nothing is installed into the OS.
- Wi-Fi: many clone dongles can't join 5GHz/WPA2-3 networks. A PC's 2.4GHz mobile hotspot works well as an alternative — both apps above document this setup in their READMEs.
-
Buttons: clones often report SELECT/START as
BTN_TRIGGER_HAPPY1/2(codes 704/705) instead of the standard 314/315. Both apps handle this out of the box; if you're writing your own app, handle both.
Tested something on a clone? Add a row above with:
- App — link to the source
- What it is — one line
- Tested on — device branding, clone type and DTB (identify yours with the DTB Analysis Tool)
- Install — how it gets onto the device
Apps should state their panel/firmware requirements honestly — "works on my device" with the device named beats a broad claim.