When it works:
Apple Watch: Address: xx-xx-xx-xx-xx-xx Random Address: Yes Resolvable Address: No Services: Paired: No Configured: Yes Connected: Yes Manufacturer: Apple (0x9, 0x3D30) Bluetooth Core Spec: 5,0 Class of Device: Low Energy AFH: On AFH Map: ffffffff1f RSSI: -86 Role: Peripheral Connection Mode: Active Mode Interval: 0 ms
After the connection is lost:
Apple Watch: Address: xx-xx-xx-xx-xx-xx Major Type: Miscellaneous Minor Type: Unknown Services: Paired: No Configured: Yes Connected: No Manufacturer: Apple (0x9, 0x3D30) Bluetooth Core Spec: 5,0 Class of Device: 0x00 0x00 0x0000
Then it has to be reconnected again manually for unlock to work (in my case via the annoying procedure above).
Don't know how it works on a real Mac, but I guess it should re-connect automatically?
good for uI've found the solution for my 94360 based card.
It turns out the serial port being enabled in BIOS is the culprit of the Apple Watch unlock failure after sleep.
The latest BIOS F8 doesn't have the option to disable serial port, so I had to downgrade to the previous BIOS where this option was available. After disabling serial port in BIOS, voila, AW unlock works like a real Mac.
As per my hardware spec on the left, it's GPU without IGPU.good for u
i would like to know wether you are using Integrated or dedicated graphics,
in another thread i read, it seems that using a dedicated graphics will case the unlock failure after sleep
As per my hardware spec on the left, it's GPU without IGPU. 9400F (no IGPU) + RX570. I've also found that Opencore is much more reliable than clover ever was. If you are still on Clover, that's the first thing I would try. Also proper USB is required for sleep/wake to work properly.