Legacy interface #9
Labels
enhancement
New feature or request
help wanted
Extra attention is needed
Matebook E
Matebook E
Matebook X
Matebook X
Comments
|
I might need updated data from Matebook X (2017). @janbaer could you please provide me with DSDT/SSDT tables? Just make sure you're on the latest BIOS update. Also, do you know if this model supports battery protection and fn-lock? |
|
Battery protection and fn-lock were added and can be controlled through the driver. You can access these features under Charge thresholds accept values from 0-100 and fn-lock takes either 0 or 1. These attributes directly access AML code using WMI commands, specifically method This method is found in most Huawei models. However, some models have other methods as their WMI BIOS controller such as Matebook X (2017). From what I have, this model supports fn-lock control using this method but not battery or micmute led. There are many other methods that this WMI device can control but I haven't found what they're for yet. |
Closed
|
@aymanbagabas I'm sorry but I just read this issue today. Do you still need the DSDT/SSDT tables. |
I don't know which model you're running, but for MateBook 13 it has been figured out. Probably works on other MateBooks, too (if you use correct device GUID for your model), but I don't think anyone tested it. |
All huawei laptops that I have seen have a common BIOS WMI device controller. Except the old matebook, it has this common device but it also has another one that controls most of the features. I wanna see if the latest BIOS adds support for this common device so that we don’t need to implement the “legacy” controller.
You’re awesome. I tested it and it worked on my x pro. You know that when you edit the .fd file in a hex editor there is a config section that you can change allowing you to do things like downgrading the bios. I’m wondering if anyone tried that |
|
@janbaer if you're still interested in helping to implement the "legacy" BIOS interface that's found on laptops such as Matebook X (2017) I will be glad to work with you. Right now, with tag |
|
Right now, I'm trying to figure out a way to detect laptop available features. I created a simple bash script that uses From the output of this script, I've come to this AML method
Maybe these values mean something maybe not. Any ideas? |
|
@aymanbagabas I'm sorry for the late answer. Yes the Matebook X 2017 has also fn-lock and it's also working for me (if me mean the same). The mic-mute fn key is actually not working, but till today I didn't miss it, because I never used it. About battery protection I have no idea, what feature it's. Unfortunately I still don't know how to generate the DSDT/SSDT tables you asked for. But how about this one from @cytrinox https://github.com/cytrinox/matebook-hotkeys/tree/master/acpi |
Did you remap the micmute key? Fn-lock works by inverting the behavior of the function keys. It's not when you have the Fn led on. With Fn-lock, and Fn led is on, the function keys would be the multimedia keys NOT F1-F12. For battery protection, it sets charging limits so it protects the battery from wearing out.
It is unlikely that the vendor updated the BIOS with the new management interface that's equipped with their newer devices. I just want to make sure that that's the case so we don't have to implement the "legacy" interface. You could get these tables using |
|
Hi guys! @nekr0z @wasakakero @janbaer Please test the following while watching dmesg for any errors, you could use
I would also need someone with a MateBook X (2017) to test this and/or to help with implementing the "legacy" interface, @nekr0z @wasakakero if you guys know someone it would be really really appreciated! This is one of those times where your code isn't complete but works. As a dev, I'm really really annoyed that this part isn't complete because I don't have the hardware and can't use debugging tools to figure it out since this old freaking interface has parts tied to the hardware level that won't be emulated with software such as LED stuff. Finally, thank you guys for your contributions toward this project, without you guys, and the latest news regarding Huawei and the US 👎, we wouldn't get this far with the driver. |
|
OK, here's for MateBook 13:
Works as expected, no issues, all correct.
Works as expected.
Again, works as expected.
What do you think, works as expected!
Well, here we go... Not sure whether this is expected or not, but let's go on... The last command here brings micmute led on (I kinda expected the first command would, but what do I know). From this moment on, micmute led doesn't react to actual ALSA micmute settings and can only be switched on or off manually through the driver, not sure if this is expected either. Again, the last command (not the first one) kills micmute led. After All along, nothing in dmesg other than initial registering Huawei WMI hotkeys as input. |
@lidel, care to join in? |
|
@cytrinox @thisisshi care to join? |
|
@aymanbagabas sorry, i didnt see that you also added the matebook-e label here. Can i still help with this issue? |
Yes, the Matebook E has the same interface. However, unlike the Matebook X, keyboard keys are not handled through this WMI interface, it uses USBHID instead. You can see from the files attached that the WMI event handler has the same guid that the Matebook X has MBE WMI mofMBE WMI decoded mof |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most of Huawei devices have the AMW0 WMI device which has a GUID of
ABBC0F5C-8EA1-11D1-A000-C90629100000. This WMI device has a method AMW0.WMAA with GUIDABBC0F5B-8EA1-11D1-A000-C90629100000which seems to control most of the features.Right now, one of controlling the mic led only works with devices that implement method
\_SB.PCI0.LPCB.EC0.WPINand\_SB.PCI0.LPCB.EC0.SPIN. Models that don't have one these methods simply don't work! Like #7Using WMI calls, specifically AMW0.WMAA, #7 could be solved and #8 could be integrated. The only model that might not work with this update is the Matebook X (2017).
The text was updated successfully, but these errors were encountered: