Increased Keyboard Backlight Levels/Steps using Windows Dynamic Lighting (API)?

[nathancdy]

Rules

• I made myself familiar with the Readme, FAQ and Troubleshooting.
• I understand that, if insufficient information will be provided, my issue will be closed without an answer.

Is your feature request related to a problem? Please describe

ASUS has very few steps/levels for their keyboard backlight, some people may want to a more precise brightness level for the keyboard backlight.

Describe the solution you'd like

(I haven't tested myself, but I've heard other accounts of people using the Windows Dynamic Lighting to have more precise levels of keyboard backlighting)

If there is a way to implement the Windows Dynamic Lighting to increase the number of levels or steps for the keyboard backlighting, similar to how MacBooks implement their keyboard backlight levels.

Describe alternatives you've considered

No response

Device and Model

ASUS Zephyrus G14 GA403UV

Additional information.

I'm sure this has been requested in the past though I haven't found the request myself. Feel free to close this request if it has already been addressed. Thanks!

[seerge]

@nathancdy hello, even if that's possible that needs to be reverse-engineered from scratch and I have returned my G14 2024 :)

[seerge]

@nathancdy

Ok. We need to figure out what exactly Armoury sends to keyboard.

Can you please do following

Install https://www.hhdsoftware.com/device-monitoring-studio (will require reboot)

1. Launch Monitoring Studio, pick Asus device from the list and double click on it
   
2. Add Packet View to Procesing and click Start
   
3. Change backlight brightness using Windows Dynamic Lightning
4. Check if Monitoring Studio catching a lot of data. If NOT - you probably have selected wrong Asus device on step 2 (so need to re-do it)
5. In Monitoring Studio select Tools -> Save to Log, and save data
   

Upload this data here.

[nathancdy]

@seerge will try to do some testing once i am home!

Does the communication between AC and the keyboard differ across year models? I assume you may have already done some testing with your G14s but need someone with the 2024 model

[seerge]

@nathancdy no, it's practically same across all years. Except G15 2022 is broken and has some own commands and is generally broken in many other senses.

But it could be that "new" approach of windows dynamic lightning is different tho

[nathancdy]

@seerge Not home at the moment, but I noticed in my Human Interface Devices section in Device Manager, I don't have an ASUS-labeled item on the list. The only ASUS-labeled item is the Precision Touchpad and the rest are HID _____.

[seerge]

@nathancdy any updates on the matter ?

[nathancdy]

@seerge sorry, was busy with school initially during the time I sent my last reply and just seen your reply just now. Should I be testing each device in Human Interface Devices? I'm unsure why I don't have an ASUS-labeled device under that section.

[seerge]

@nathancdy no, you just need a device with vendor id ASUS 0x0b05 and device id 19b6

(or any from this list )

    static int[] deviceIds = { 0x1a30, 0x1854, 0x1869, 0x1866, 0x19b6, 0x1822, 0x1837, 0x1854, 0x184a, 0x183d, 0x8502, 0x1807, 0x17e0, 0x18c6, 0x1abe };