Can't change keyboard lightning #2973
Comments
|
@Rooie100 hello, Is it only backlight modes that don't work or also backlight brightness ? Cause I see that brightness controls seem to exist on your device and work While backlight modes are absent What happens if you start asus services, does the backlight mode selection in G-Helper itself start suddenly working ? Or how do you change backlight otherwise ? |
|
Hi, thanks for the response.All the backlight modes don’t work, even within windows. I also can’t change the brightness or color. When i start the asus services, the lightning control within g-helper all of a sudden starts working. If you need anymore info let me know!On 13 Aug 2024, at 17:43, Serge ***@***.***> wrote:
@Rooie100 hello,
Is it only backlight modes that don't work or also backlight brightness ?
Cause I see that brightness controls seem to exist on your device and work
8/13/2024 5:31:08 PM: TUF Brightness = 128 : OK
8/13/2024 5:31:09 PM: WMI event 199
8/13/2024 5:31:09 PM: TUF Brightness = 129 : OK
8/13/2024 5:31:09 PM: WMI event 199
8/13/2024 5:31:09 PM: TUF Brightness = 130 : OK
8/13/2024 5:31:09 PM: WMI event 199
8/13/2024 5:31:09 PM: TUF Brightness = 131 : OK
While backlight modes are absent
8/13/2024 5:30:27 PM: AuraMode: AuraStatic
8/13/2024 5:30:27 PM: TUF RGB = B4-00-FF-80-40-EB : 0 <-- 0 means it's not there
8/13/2024 5:30:27 PM: TUF RGB = B4-00-FF-80-40-EB : 0
What happens if you start asus services, does the backlight mode selection in G-Helper itself start suddenly working ? Or how do you change backlight otherwise ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
@Rooie100 then it looks like your device is quite unique and asus services work as a proxy between actual backlight and apps that want to set it, since when they are running all backlight commands work in g-helper. It may be very difficult to find a way to directly set backlight in your case without having access to the actual device. Can you make a DSDT dump as explained in Method 2 and upload it here ? |
|
@Rooie100 any updates with the dump here ? |
|
I have this same issue with Asus ProArt P16. When Ghelper is running amd Asus service are stopped, I am unable to change backlight color, modes, or brightness just nothing happens at all when any changes made. Even when I restart services, I am now able to change backlight brightness and modes, but still not the colors. |
|
@GDisco0730 does your device even support different colors? Cause Proart X13 does not for example. As for the rest, same question please upload DSDT dump from Method 2 here (and log from the app as well) |
|
Hey Seerge, Sorry to keep you waiting, i attached the dsdt in ZIP form/ |
|
@Rooie100 hello, thanks. Can you check if this build makes any difference ? |
|
I have the same issues with the vivobook s 16. Testing the new zip you added. So far, the colors are now indexing again like it was new, constantly cycling through the colors (was just static blue prior). I have my Asus uninstalled as well as having run the armoury crate removal tool. Edit: Just to clarify, even with changing the color mode and/or color, the observed behavior remains with color cycle. |
|
@gbassani i don't think that you are similar to other people here :) as they can't control backlight (due to some unknown method specific only to that devices?) If you had static blue - that's a sign of windows Dynamic Lighting being ON and taking over. Just make sure to disable it and regular mainstream build should work fine. |
|
Thank you for the info, missed that in the FAQ's. Even with dynamic lighting off (both globally and under the keyboard), the colors continue to cycle. I also tried setting both the personalization color and within G-Helper to static red. This is under the mainstream build. Model is the M5606WA with the AMD stack. Also checked and it isn't in the list of compatible devices, I can submit for it there. |
|
Hey, It semi fixed it! I can control the brightness now, but not the color. It stays in breathing mode.... |
|
@Rooie100 ok, good news, can you try this build and post a log from it ? |
|
P.S. @gbassani @GDisco0730 you both can try build above as well |
|
Hi, Here is the log! Thanks for the effort already, i'm happy that i can change the brightness at least. |
|
@Rooie100 ok, but do backlight modes work in this build or not ? |
|
Cause if it does not, it looks like not only endpoint (i.e. where to set backlight setting) but also structure of the command itself is different. Try this build instead, to see if it makes any difference (and again post a log) |
|
If even that build does not work, it means we need to monitor actual commands Asus Services send to hardware in order to change backlight modes I have a guide on how to do that |
|
Hi, Last build does not change a thing, can't change the lightning withing G-helper. |
|
@Rooie100 ok, thanks for checking. Then the only way would be to intercept actual payloads that Asus service sends to the device in order to set backlight modes as explained in https://github.com/seerge/g-helper/wiki/_ACPI-Monitoring-and-Debugging You will need to follow the guide, and then change backlight using Asus software (not G-Helper!) and record payloads Ideally would be good to :
|
|
Try deleting %AppData%/GHelper folder. Fixed it for me. Unfortunately I didn't it backup up so I couldn't do the diff. |
|
@kennycoder G14 2023 backlight control is 100% supported (and used by dozens of thousands of people). Config removal won't do anything except erasing of own G-Helper settings. People in this thread have new (mid 2024 devices) that use different backlight controls. |
Apologies for delay, tried the latest zip package above from 3 days ago and still stuck on static white. Dynamic is disabled globally and at keyboard level. Also attempted to set to static red in personalization and in g-helper. Attached the log.txt, screenshots of the dynamic lighting/g-helper, and the dsdt Edit: clarified about package used |
|
@gbassani hello, thanks for checking. As I have explained in a comment above i need someone to record actual payloads asus service sends to the device. As new Vivobooks seem to use different protocol completely :) |
|
@Rooie100 any updates here ? :) |
Working on this--spinning up a sandboxed installation. I'll use that tool after clean install prior to installing MyAsus to use the windows dynamic lighting and then will try after installing MyAsus for a second file. Command Interface v3 will be installed for both prior. Edit: do you want me to also try capturing for this AsusKeyboard driver? The attached is all I was able to generate over several minutes when clicking through the colors as well as the lighting types. |
|
@gbassani hello, thanks. Your log contains only 2 commands, just for toggling backlight brightness, but both of them are already in G-Helper since the very beginning (and as I understand it works for you anyway) What I need is a payloads for changing backlight modes using Asus software :) |
|
@gbassani it's a free trial, just click download. You don't need to pay anything of course |
|
@seerge |
|
@lazer15 that's quite strange, as usb device is 100% there (g-helper can see it). May be try to reboot ? :| |
|
@seerge |
|
@lazer15 ok, great! There is indeed some new init commands there Try this build (and post a log) |
|
@seerge |
|
@lazer15 hmm, strange. I have copied full payload from your capture now, try this build |
|
@seerge It seems I need to click the mode button in g-helper after a reboot in order for that profile to apply. It will have silent mode selected when I open g-helper after a reboot but it doesn't actually seem to apply it (processor temp rises like it isn't in silent mode and fans come on) until I click silent mode myself. I do not know if that's at all potentially related to initialization of the keyboard. To me it seems like it isn't apply setting on boot at least for the performance mode. Also is it normal for the battery to slowly creep up from 80%? It was 80% earlier (set the 80% charge limit) but it's now 81.2%. It was sleeping. It is charging with the stock charger. Since I've had the laptop and ghelper, it seems the battery level creeps past 80% even when windows is reporting smart battery charging mode. I've never had a laptop that supported the windows smart charge feature. It would creep up with asus services running or without. Never seemed to stay exactly at 80%. |
|
@lazer15 ok, one more attempt As for your other questions.
|
|
@lazer15 from the log it looks like you
Can either replace your usual GHelper.exe with a new build, or just run a new build from any location - but uncheck and check "Run on startup" ? (it will re-create startup task pointing to that exe) |
|
@seerge My mistake: Changed to: I cleared the log for this retest the EXEs from today.
The latest version works.
I also just retested this one. This one doesn't work. Stuck with the breathing pattern.
Here is a log from retesting the first one from today: Should I use the latest one or the 1st one from today? Is one preferable to the other? |
|
@lazer15 ok, great! To keep it simple - when you use latest version all the time - everything works as it should? |
|
@seerge |
|
@lazer15 no, you don't need to test old ones. Last one is definitely correct :) Ssince you are already can record USB. Can you try to capture one more payload (not related to backlight but to FN-Lock)
|
|
@seerge |
|
@lazer15 it doesn't matter |
|
@seerge On the P16 the brightness, volume ect functions are the default action when pressing F# keys. You have to press FN if you want to use those keys as F1, F2 ect. But I believe that's common on a lot of laptops now, defaulting to actions instead of F#. It was the same on my last 2 laptops a lenovo and a dell xps. |
|
@lazer15 ok, amazing. Apparently part of "init" payload you recorded before was setting FN-lock OFF on device start (logical). So I have cleaned up "init" from that and also added hardware fn-lock handling in g-helper (before it was software imitation as app can do for any other device that doesn't have native fn-lock) Can you try this build w/o any asus services and check if
|
|
@seerge On the prior version I was able to toggle FN-Lock on and off without issue. On reboot it would default back to FN-Lock OFF which matches up with what you described the payload said. I thought that was normal because a dell XPS I used to have did the same. Here's a log if needed: |
|
@lazer15 ok, amazing In "old" versions FN-lock was imitated on software level. There is a downside that when it's ON and you press FN+F1 for example, it would still emit special function (mute). In "new" version FN-lock is handled by hardware (g-helper is not involved). So I assume when it's ON an you press FN+F1 it should just emit regular F1 key. And thanks for testing :) |
|
@seerge Do you know how to uninstall irpmon? When I ran the uninstaller, it said the uninstall was incomplete and components would need to be removed manually. It didn't say which components were left behind though. Maybe you've tried to uninstall it before after testing at some point? |
|
@lazer15 i think that's enough. At least I did same, also got same message and never had any issues after (including gaming). And I couldn't find any leftovers from irpmon neither anyway. You can enable back secure boot if you want after :) Btw in latest builds I have also added an option to udnervolt Ryzen 9 AI (migrated latest changes from the UXTU library that g-helper uses under the hood for undervolting), so if are interested you can test if it works as well. |
|
@seerge Sure I can try the new changes. I assumed that tab wasn't present in g-helper for me because maybe the proart line doesn't support it despite having the same processor as G14/G16. I was trying to improve battery life so some undervolting would be good. |
|
Ok, To summarize all changes a result of this thread
Therefore closing as resolved. Thanks everyone for testing and information! |
Rules
What's wrong?
As the title says, i cant change the lightning in G-helper. Only when i click ''run Asus services'' then it works. Dynamic lightning is disabled via windows.
I'm also using the latest version of G-helper.
How to reproduce the bug?
Go to G-helper
Click on a different color
Keyboard stays in breathing
Logs
log.txt
Device and Model
ASUS Vivobook S 15 OLED M5506NA.
Additional information.
No response
Armoury Crate
Uninstalled
Asus Services
None
Version
0.184.0
OS
Windows 11 H
The text was updated successfully, but these errors were encountered: