Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature Request] LCD screen support for ASUS Ryujin III White (0b05:1ada / OLED Controller 0b05:1936)

Open
#869 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
cli, embedded-iot

Research direction

Start with the existing asus_ryujin driver and its set_screen stub, then compare how Ryujin II 360 LCD support is implemented. Capture and inspect USB HID traffic for the separate OLED Controller (0b05:1936) to determine the protocol. Done means liquidctl lists the controller and supports static images, GIFs, and brightness for the LCD.

Written by the indexing model from the issue text.

Description

Is there already an issue for this?
  • There is no relevant open or closed issue for this
Is this a request for support of a new device?
  • This is not a new device request
Is this a support request?
  • This is not a support request
Description

Device Information

Field Value
Device ASUS Ryujin III White
Cooler USB ID 0b05:1ada
OLED Controller USB ID 0b05:1936
Firmware AURJ2-S750-0108
liquidctl version 1.16.0
OS Ubuntu 24.04, kernel 6.8.0-49-generic

lsusb Output

Bus 001 Device 004: ID 0b05:1a98 ASUSTek Computer, Inc. USB Audio
Bus 001 Device 014: ID 0b05:1936 ASUSTek Computer, Inc. OLED Controller
Bus 001 Device 010: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 011: ID 0b05:1ada ASUSTek Computer, Inc. ROG RYUJIN III WHITE EDITION

Current Behavior

The cooler is detected and initialized successfully:

$ sudo liquidctl --match ryujin initialize
ASUS Ryujin III White
└── Firmware version    AURJ2-S750-0108

However, attempting to control the LCD screen fails:

$ sudo liquidctl --match ryujin set lcd screen static /path/to/image.jpg
ERROR: ASUS Ryujin III White: operation not supported by the driver

Inspecting the source confirms set_screen is a stub:

def set_screen(self, channel, mode, value, **kwargs):
    # Not yet reverse engineered / implemented
    raise NotSupportedByDriver()

Expected Behavior

LCD screen control (static image, GIF, brightness) via liquidctl, similar to what
is supported for the Ryujin II 360.

Notes

  • The LCD is exposed as a separate USB device (0b05:1936, labeled "OLED Controller"),
    distinct from the main cooler device (0b05:1ada).
  • Pump speed, fan control, and temperature sensors all work correctly via the existing driver.
  • The OLED Controller does not currently appear in liquidctl list at all — it may
    need its own driver entry or to be handled within the existing asus_ryujin driver.
  • Happy to assist with USB HID traffic capture (usbmon + Wireshark via Windows VM)
    if that would help reverse engineer the protocol. Please let me know what data
    would be most useful.

Related

  • #829 — Ryujin III EXTREME support (merged into 1.16.0)
  • #866 — Ryujin III White support (merged into 1.16.0, fan/pump only)
Dominant language
Python
Stars
2.7k
Forks
295
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from liquidctl/liquidctl

All issues in liquidctl/liquidctl

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.