Contribute
Register

Audio jack and Camera won't work on Matebook 13

Status
Not open for further replies.
Joined
Oct 16, 2018
Messages
97
Motherboard
Matebook 13 Eu
CPU
i7-8565U
Graphics
UHD 620
Mobile Phone
  1. Android
Hi guys, after some days I've reached a nearly fully functional installation. The only thing is that camera won't work and audio works but if I connect headphone to the 3,5 jack, nothing happen. The audio is ACL256, with id 13 I guess.
The Matebook 13 is a wiskey lake with i7 8565 with Intel UHD 620.

Attached report and screenshot of IOreg of camera details.

Nb:don't mind of plist backups, it's here just for now to test
 

Attachments

  • screenshot.png
    screenshot.png
    244.4 KB · Views: 60
  • debug_16102.zip
    2.3 MB · Views: 55
Last edited:
Hi guys, after some days I've reached a nearly fully functional installation. The only thing is that camera won't work and audio works but if I connect headphone to the 3,5 jack, nothing happen. The audio is ACL256, with id 13 I guess.
The Matebook 13 is a wiskey lake with i7 8565 with Intel UHD 620.

Attached report and screenshot of IOreg of camera details.

Nb:don't mind of plist backups, it's here just for now to test
config.plist:
InjectKexts should be set to Detect

add these to Fixes:
Code:
<key>FixTMR</key>
                <true/>
                <key>FixRTC</key>
                <true/>
                <key>FixIPIC</key>
                <true/>
example of how it should look like (but with true and not false)

also this part should look like:
Code:
<key>PciRoot(0)/Pci(0x1f,3)</key>
            <dict>
                <key>layout-id</key>
                <integer>3</integer>
                <key>PinConfigurations</key>
                <data></data>
                <key>hda-gfx</key>
                <string>onboard-1</string>
                <key>no-controller-patch</key>
                <integer>1</integer>
            </dict>
check with the wiki of supported layout ID's you may need to trial and error to see which ones work:

MacBookPro14,1 would be a better choice

How and where to install kexts:
 
config.plist:
InjectKexts should be set to Detect
I selected to inject because I have to test Cpu Friend Kext before putting in Library/Exstentions

add these to Fixes:
Code:
<key>FixTMR</key>
                <true/>
                <key>FixRTC</key>
                <true/>
                <key>FixIPIC</key>
                <true/>
example of how it should look like (but with true and not false)

also this part should look like:
Code:
<key>PciRoot(0)/Pci(0x1f,3)</key>
            <dict>
                <key>layout-id</key>
                <integer>3</integer>
                <key>PinConfigurations</key>
                <data></data>
                <key>hda-gfx</key>
                <string>onboard-1</string>
                <key>no-controller-patch</key>
                <integer>1</integer>
            </dict>
check with the wiki of supported layout ID's you may need to trial and error to see which ones work:

MacBookPro14,1 would be a better choice

How and where to install kexts:
Changed smbios to 14,1 and fixed audio by changing layout id. Many thanks. Any suggestion with the camera?
 
I selected to inject because I have to test Cpu Friend Kext before putting in Library/Exstentions


Changed smbios to 14,1 and fixed audio by changing layout id. Many thanks. Any suggestion with the camera?
you will probably have to setup your usb ports correctly:
Hackintool:

or another usb setup guide:
 
you will probably have to setup your usb ports correctly:
Hackintool:

or another usb setup guide:
Tried to do, but in ioreg I see all the port, like before the SSDTs was placed
 

Attachments

  • SSDT-USB.dsl
    3.1 KB · Views: 44
  • SSDT-USB.aml
    527 bytes · Views: 42
  • debug_1681.zip
    2.5 MB · Views: 45
Tried to do, but in ioreg I see all the port, like before the SSDTs was placed
Per SSDT-UIAC-ALL, the 0x9ded port count should be 0x12 (18), you have 0xF.

For your own port documentation - HS10 seems like your internal Bluetooth. Use 255 connector type, as it's internal.

I believe the reason your SSDT doesn't take effect is the package name. Use 8086_9dxx instead of 0x9ded.
The EHCI-disabling code is not necessary on 100-series or newer, as only XHCI is available... Omit it from your SSDT, you only need the UIAC device there.
 
Per SSDT-UIAC-ALL, the 0x9ded port count should be 0x12 (18), you have 0xF.
For SSDT-UIAC-ALL, you mean my SSDT-USB?
0X12 or 0x18? 0x7 it's my maximum SS port
For your own port documentation - HS10 seems like your internal Bluetooth. Use 255 connector type, as it's internal.
Done
I believe the reason your SSDT doesn't take effect is the package name. Use 8086_9dxx instead of 0x9ded.
The EHCI-disabling code is not necessary on 100-series or newer, as only XHCI is available... Omit it from your SSDT, you only need the UIAC device there.
Delete EHCI. I have to put 8086_9ded or 8086_dxx?

Edit: it works, but now can I get camera working?

Many thanks
 
Last edited:
For SSDT-UIAC-ALL, you mean my SSDT-USB?
0X12 or 0x18? 0x7 it's my maximum SS port

Done

Delete EHCI. I have to put 8086_9ded or 8086_dxx?

Edit: it works, but now can I get camera working?

Many thanks
Your SSDT-USB is based on RehabMan's SSDT-UIAC-ALL, which specifies the correct names that should be used.
You should have 0x12 (hexadecimal) there, which equals 18 (decimal).
It's the highest SS port that your XHCI controller supports, not specifically your machine.

You might try UVC2FaceTimeHD.kext, once you verified your SSDT is working properly.
Find it here:
I think you should set idVendor and idProduct to your own values.
Vendor - 0x13d3.
Product - 0x56c6.
Notice you need to modify those:
Not the values within MergeProperties.
 
Your SSDT-USB is based on RehabMan's SSDT-UIAC-ALL, which specifies the correct names that should be used.
You should have 0x12 (hexadecimal) there, which equals 18 (decimal).
It's the highest SS port that your XHCI controller supports, not specifically your machine.

You might try UVC2FaceTimeHD.kext, once you verified your SSDT is working properly.
Find it here:
I think you should set idVendor and idProduct to your own values.
Vendor - 0x13d3.
Product - 0x56c6.
Notice you need to modify those:
Not the values within MergeProperties. wh
My values are id product: 0x56c6 , id vendor 0x13d3 fine. but in the plist in the kext I have to convert the value because it doesn't accept 0x****, how can I do it? The are UVC Device and UVC Device2 which one I have to replace?
 
Status
Not open for further replies.
Back
Top