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

[66mhz]

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

• asus_ryujin: support the ASUS Ryujin III EXTREME #829 — Ryujin III EXTREME support (merged into 1.16.0)
• Adding support for the Ryujin III 360 ARGB White Edition #866 — Ryujin III White support (merged into 1.16.0, fan/pump only)

[notthatwillsmith]

I'm happy to grab USB capture data as well. I also have access to other variants of the same AIO at work if it's helpful to grab similar captures from other hardware.

[rebasecase]

Best off looking at that third party app, there is a command that writes directly to the frame buffer. AIDA or whatever it is called.

Anyway did a pr #872

[rebasecase]

@notthatwillsmith

I'm happy to grab USB capture data as well. I also have access to other variants of the same AIO at work if it's helpful to grab similar captures from other hardware.

Can you try my branch?

If you’re interested I have made a custom firmware (incl toolchain) for these models. If you are comfortable soldering a debugger to it. Or I can write in a recovery mode for it like the original one does

[rebasecase]

If you want gif upload I can work that out, I think there is another issue with the full protocol on it but probably incomplete. I have the entire thing reversed. There’s a fat16 partition on the spi it writes to which is why it takes 3 to 4 working days to upload 4MB.

[rebasecase]

The device is very capable. There’s also dead code to allow compositing of stats over a custom background but was never implemented. Big sad. 😔

[notthatwillsmith]

@rebasecase I'll give it a try when I have a minute. It's the ryujin3-screen-support branch, I assume?

I don't think I'm quite ready to replace the firmware on it...

[rebasecase]

Yeah the one in the pr. Should work across all the devices as long as the identifiers match