WhiteDragon

My apologies, I had not checked this site in quite a while. Since my Matebook is a different model than yours (mine is an i7-8550), my DSDT and my SSDT patches may not work for you. Did you start with the files I pointed at in my initial post? If not, what did you start with? Note that my post was for exactly my model. Are you using the latest version of the following Voodoo kexts?: VoodooI2C.kext Voodoo I2CHID.kext For ACPI DSDT patches, these two are the relevant ones for the touchscreen on my system: SSDT-GPIO.aml SSDT-TPL1.aml I will try to give advice if you send me more info, but I cannot guarantee anything. - Mark

I've continued to update my Matebook as new versions of kexts become available. The most exciting update is that the native Intel WiFi is now working using a new itlwm kext and the new HeliPort app. They also work on the ASUS laptop I configured back in May. I have attached the versions I'm currently using. Here are the links to where I got them: https://github.com/OpenIntelWireless/HeliPort/releases https://github.com/OpenIntelWireless/itlwm/releases Cheers! - Mark HeliPort.dmg.zip itlwm_v1.0.0_stable.kext.zip

You are correct that the second step is not necessary for the #08PKF4 version of the DW1820A. I removed them and it is still working.

I got my DW1820A (#08PKF4) in yesterday and soon found out that the specific combo of a Latitude E7270 and the #08PKF4 variety of the DW1820A was not posted. After looking around a bit and making appropriate guesses, the following worked for me: Using the config.plist and CLOVER folder from Jake Lo's Latitude E7270 installation guide, do the following: (1) Uncomment the "PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)" line in the Devices Properties area using Clover Configurator. This will bring in the DW1820A device patches. (2) Add the following boot args: brcmfx-country=#a, brcmfx-driver=1. Cheers!

LOL! I tried it out the other day and yes, great view of my ugly chin unless I look a little bit down. Not too bad, with regard to my nostrils... (see the attached image)... If you do not look down a little, it mainly looks like you are staring up into the air. Still, I love the overall design!

Thanks about the view, arsradu! It's in Northern California in the SF Bay Area. I had been in the tech industry about 10 years when I bought the place about 20 years ago.

The kext I provided in my last post works with my Latitude E7270, too. I'm planning on replacing the internal WiFi card with a DW1820A card, but in the meantime, it is nice not needing the dongle.

The Matebook has an AC 8275 wireless card. I successfully got the Matebook to connect to WiFi using the attached kext. You need to modify the kext's Info.plist as follows (shown using PlistBuddy commands): /usr/libexec/PlistBuddy -c "Set :IOKitPersonalities:AppleIntelWiFi:IFConfig:NWID SSID" Info.plist /usr/libexec/PlistBuddy -c "Set :IOKitPersonalities:AppleIntelWiFi:IFConfig:WPAKEY PWD" Info.plist Where SSID is the SSID of the network you want to connect to and PWD is the WPA password of the network. Everything I have read about the kext warns to manually kextload it when you want to use it and to not put it in /S/L/E, /L/E, or Clover kexts/other because it can fail too easily and prevent the system from booting. Here is a convenient set of commands for manually loading the kext: sudo mv ./AppleIntelWiFi.kext /tmp sudo chown -R root:wheel /tmp/AppleIntelWiFi.kext sudo kextload /tmp/AppleIntelWiFi.kext The kext causes a KP if you try to kextunload it (I tried), so if you want to change to another network, you need to reboot, edit the kext, and load it. AppleIntelWiFi.kext.zip

When I updated my ASUS to the latest 10.15.5 update, it broke the touchscreen and touchpad. I then updated VoodooI2C.kext and VoodooI2CHID.kext to version 2.4.3 and the touchscreen worked perfectly (click, select, gestures, everything!), but the touchpad still didn’t work. I then backed out VoodooI2C.kext to version 2.3 and kept version 2.4.3 of VoodooI2CHID.kext and now both the touchscreen and touchpad work perfectly. I finally have everything on the touchscreen working along with a working touchpad!

I will look into the Intel Wi-Fi kexts and see if anything works out. I will post if anything is successful.

Thanks! I really like it -- about as close to an actual MacBook as you can get with a PC laptop. That is not the default touchpad. It is dbrand skin.

Unfortunately, soldered to the motherboard, so not replaceable.

Successfully created a Huawei Matebook X Pro Hackintosh today starting with Catalina 10.15.3. 2018 stock model: i7-8550U GeForce MX150 16GB RAM 512GB SSD The CLOVER from gnodipac886's Github worked for the 10.15.3 install: https://github.com/gnodipac886/MatebookXPro-hackintosh Thank you gnodipac886! I created a UEFI-bootable USB with a Cover partition and a Catalina install partition. I used the direct CLOVER folder from Github and the config.plist provided, not the config-install.plist, and the install worked without issues. I then upgraded the laptop to Catalina 10.15.5 and it hung on loading the Intel graphics firmware, so I added -disablegfxfirmware to the Clover boot args and successfully upgraded to 10.15.5 through system preferences software update. All major features are working: Touchpad Touchscreen Battery Status Backlit Keyboard Sleep I'm using a dongle for the Wi-Fi. Cheers!

In response to the Elan statement from Jake Lo, on the ASUS laptop I hacked, I had an Elan 9008 touchscreen that I got partially working using VoodooI2C.kext and VoodooI2CHID.kext and GPIO pinning. Cursor follow and gestures wok, so I can move the cursor and scroll with the Elan touchscreen. I have not been able to get clicking/selecting to work, yet.

In response to Jake Lo: Yes, my E7270 touchscreen is an Atmel. The vendor ID x03EB is the Atmel vendor ID.