Hervé

Well, there are various ways to connect to an iPhone (shared) data service: USB Bluetooth Wireless Personal HotSpot (Wireless + BT) You've mentioned HotSpot but, given your above description, it looks like you're doing things incorrectly and BT may not properly work on your Hack... 2 x obvious things: Personal HotSpot (i.e. connection sharing) needs to be enabled on the iPhone (we'll assume this is the case). USB cable not required for Wireless, Bluetooth or HotSpot service 1) Connection via USB: If you want to use your iPhone through USB, just connect the cable and disable/turn off Wifi/BT on your Hack. iPhone USB service will then be automatically selected. By default iPhone USB is disabled unless needed. If you have no Wifi on your Hack or if it's already off, iPhone USB connection will auto activate right after you connect your iPhone. 2) Connection via Bluetooth: If you have Bluetooth only (no USB, no Wifi), just pair your Hack with your iPhone and you'll be able to use the shared connection (Personal HotSpot) of your iPhone after a few seconds (it's not immediate). 3) Connection via Wireless: If you have wifi only (no USB, no BT), your iPhone will be offered as a wireless network if and only if you actually go to Personal HotSpot (connection sharing) on your iPhone. No iPhone SSID visible on the network otherwise. Select the wireless service and, if applicable, enter the password you may have set on your iPhone. 4) Connection via Personal HotSpot: This requires BT to be active on the iPhone and Wifi + BT on your Hack. Basically, this needs the same setup as required for continuity features such as Handoff. If both BT + wireless services are working properly, your iPhone will be offered as a Personal HotSpot on your Hack alongside wireless networks. Just pick-up your iPhone Hotspot and you're good to go. No BT pairing required. No need to be in Connection Sharing on your iPhone. Sometimes, on Hacks, these services do not work perfectly and require a restart of either the iPhone or the Hack, occasionally both. NB: All of the above tested and verified with: Dell Vostro 200ST desktop fitted with AR5B92 wireless card (wifi only (fully working), no BT), Catalina 10.15.4 Dell Latitude E6220 laptop witted with Apple BCM94360CD combo card (wifi + BT, both full working), High Sierra 10.13.6 Dell Latitude E6230 laptop fitted with Apple BCM94360CD combo card (wifi + BT, both full working), Catalina 10.15.4 Dell Latitude 7490 laptop fitted with DW1820a combo card (wifi + BT, both fully working), Catalina 10.15.4

Let's consider this topic of microphone resolved. Please open up a separate thread for your Bluetooth issue.

I believe we've already been there... https://osxlatitude.com/forums/topic/12702-spdif-gone-after-update-to-10146 If you've already updated your kexts, there's not much to do beside experimenting with codec layouts or reverting to whatever Mojave version last supported that S/PDIF fibre output of yours. And stop mixing VoodooHDA with AppleALC of course; should go without saying!

'arf, I thought so! More reason to use Clover configurator app...

I can only comment on what I found in the stuff you provided in post #1 and there was no such faking in the posted config file... And as I wrote above, use Clover Configurator app to modify your Clover config. It contains too many parameters/fields expressed in Base64 format for you to edit in plain text in a text editor if you're not an expert...

Follow Jake Lo's full guide. Bear in mind that your own laptop may be fitted with incompatible hardware (eg: NVME SSD, wireless card) that affects installation. That's the reason why we keep asking people to be thorough and post their full system's specs. Hackintoshing is not a natural thing and demands outmost precision...

I'm not aware of any link or relation between the audio codec layout and Bluetooth module.

Perfectly normal given you're not applying the necessary Azul framebuffer patch detailed in the guide I posted all those years ago: Without the HDMI patch, a Haswell laptop does indeed usually experience an immediate KP on plugging an HDMI cable. So, apply the patch and you'll find things work much better. You can apply the patch through Clover's on-the-fly patching facility (Kernel and Kexts Patches section of your Clover config file). Use Clover Configurator app to that effect. This being said, your Clover config shows that: you're not faking desktop HD4600 device id 0412; this is mandatory for all Haswell mobile HD4x00 iGPUs. you're not injecting Intel nor Azul layout 0x0a260006 (not required if you use Lilu + WEG as you seem to do) so, unless you apply those property settings in a patched DSDT, you can't even have graphics acceleration on your HD4400 iGPU at present, nor could you in 10.15.3... And same with HDMI.

Do you cache CodecCommander kext from /L/E? It cannot be injected from E/C/k/O. Given that you could not get microphone to work with AppleALC v1.4.7 before but that you do now, maybe you also ought to revert to layout 11. Still works fine for my 7490...

Rather than boot option cpus=1, you should probably use Kernel LAPIC patch. You also forgot to add the specs of this laptop. It's kind of essential to ensure interested parties understand what this guide applies to. Refer to existing guides on that matter. Once you've adjusted your post, we'll move it to the Guides section. Oh and I'm sure you can remove the statement about you not knowing what you're doing. It's hardly the right introduction for a guide, don't you think ? Same applies to the mirror guide you posted at IM. Re: Latitude E7270, Jake Lo already posted very thorough guides so it's all covered on that front...

Make your sure you cache CodecCommander kext from /L/E.

No quoting for replies please!

Yeah, I wonder why we bother with an FAQ section that most people are too lazy to even consult... It is not always necessary need to update Clover. I found it's only required on most recent platforms, probably Skylake onwards. I could update to 10.15.4 on my old C2D desktop + Ivy Bridge laptop with older versions of Clover (r5093 and r5103 respectively). OP would be well advised to boot in verbose mode to see where the boot process hangs... I've also posted boot parameters to use during the update process in the 10.15.4 announcement but that probably wasn't read either.

AppleALC v1.3.8 was the version I used at time of writing. I'm currently using AppleALC v1.4.7 in Catalina 10.15.4 and microphone is working Ok. What does your Audio PrefPane show for input? Volume Ok?

You need to identify the exact Realtek Ethernet card; if you can't, look up its PCI id (it's available in Windows Device Manager -> Driver tabs for instance). No support for Intel Wireless cards, yours will have to go and be replaced by a supported card or USB dongle. Next things you'll have to identify will be items such as: audio codec SD card reader

Probably, there are normally quite a few additional patches in those DSDT!

-> moving from FAQ section (???) to correct Latitude 7xxx one... Please! Mine works OOB as per my guide. But you did check in BIOS setup that your mike was enabled as per our posted recommended settings, right?

You can of course open up the compiled file directly. From memory, the E6x20's DSDT are not affected by the Intel iASL bug.

There is renewed development on the matter of Realtek's RTS52xx SD card reader building on Sinetek's initial work : https://www.insanelymac.com/forum/topic/321080-sineteks-driver-for-realtek-rtsx-sdhc-card-readers/?do=findComment&comment=2713476 https://github.com/cholonam/Sinetek-rtsx I've tried out Cholonam's Sinetek-rtsx kext v1.0 on my Latitude 7490 and it's now possible to read (and only read) an SD card once inserted in the reader. It can be ejected and re-inserted at will; it's just a little slow to mount (~10s) and Read-Only. Works after wake too. Supported models appear to include: RTS5209 / RTS5227 / RTS5229 /RTS522a / RTS5249 / RTS5286 / RTS5287 / RTS5289 / RTS525a

No, audio control normally works OOB with keyboard buttons on those E6x20 models.

That's exactly what I meant. 1) In method _Q66, add this code between the 2 x lines NEVT () and Return (Zero): ^^^^AMW0.WED0 (One) Mid (^^^^AMW0._WED (0xD0), Zero, 0x06, Local2) If (LEqual (Local2, Buffer (0x06) { 0x02, 0x00, 0x10, 0x00, 0x50, 0x00 })) { Notify (PS2K, 0x0365) } If (LEqual (Local2, Buffer (0x06) { 0x02, 0x00, 0x10, 0x00, 0x48, 0x00 })) { Notify (PS2K, 0x0366) } 2) In method _BCM of IGPU->LCD device , add this code before the Name (BRT3, ...) line: If (LGreater (OSID (), 0x10)){} 3) in method BRT6, all the 2 x LPVB.PS2K notifications under the LCD notifications as follows : Notify (LCD, 0x86) Notify (^^LPCB.PS2K, 0x0366) and Notify (LCD, 0x87) Notify (^^LPCB.PS2K, 0x0365) That should do it.

The DSDT Patch required to get brightness control out of the legacy BIOS E6x20 is available in my E6220 High Sierra guide. Have a look.

You misunderstood, RTCMemoryFixup is for BIOS/CMOS resets (on some computers), not for KP at shutdown/restart.

Using those same drivers on my Lat 7490 and I've not experienced any trouble with Sleep/Wake since upgrading to 10.15.4. I guess this issue was indeed specific to your own build.

It's called a "no entry" sign... .