- Joined
- Jul 3, 2014
- Messages
- 931
- Motherboard
- Dell XPS 9360 (KabyLake R)
- CPU
- Intel i7 8550U
- Graphics
- Intel UHD 620
- Mac
- Mobile Phone
I am running a laptop with Yosemite installed making use of a BCM94352Z NGFF M.2 combo card.
The BCM94352Z WiFi is Vendor ID: 0x14E4, Product ID: 0x43B1.
The Bluetooth USB is Vendor ID: 0x0930, Product ID: 0x0223
WiFi is working with a simple DSDT patch from Toleda: https://github.com/toleda/wireless_half-mini/blob/master/Patches/arpt3-bcm4352.txt.
This successfully loads AirportBrcm4360.kext, a pre-requisite for Handoff.
Additionally since the card is marked compatible with 0x43a0, whitelisting on Mac board ID should not apply.
Bluetooth is working normally with the Bluetooth Firmware uploader.
However Handoff is not showing enabled in System profile:
On an original MacBook Pro it looks like this:
Interestingly enough the chipset ID is the same between both devices and both are USB connected.
Maybe since its the same chipset some native Apple Kext can be used instead of bluetooth firmware uploader?
Also there is an interesting discussion on some Russian sites that Bluetooth is not at all relying on Bluetooth 4.0 or Bluetooth Low energy.
There is a check in /System/Library/PrivateFrameworks/Sharing.framework which checks against a variable deviceSupportsAWDL.supportsAWDL which is a boolean value.
Ideally figuring out how this variable is set, and ensuring its set properly should enable hand-off on most if not all computers irregardless of exact hardware specifications.
The BCM94352Z WiFi is Vendor ID: 0x14E4, Product ID: 0x43B1.
The Bluetooth USB is Vendor ID: 0x0930, Product ID: 0x0223
WiFi is working with a simple DSDT patch from Toleda: https://github.com/toleda/wireless_half-mini/blob/master/Patches/arpt3-bcm4352.txt.
This successfully loads AirportBrcm4360.kext, a pre-requisite for Handoff.
Additionally since the card is marked compatible with 0x43a0, whitelisting on Mac board ID should not apply.
Bluetooth is working normally with the Bluetooth Firmware uploader.
However Handoff is not showing enabled in System profile:
Code:
Apple Bluetooth Software Version: 4.3.0f10 14890
Hardware, Features, and Settings:
Name: -----
Address: -----
Bluetooth Low Energy Supported: Yes
Handoff Supported: No
Instant Hotspot Supported: No
Manufacturer: Broadcom
Transport: USB
Chipset: 20702A3
Firmware Version: v14 c5553
Bluetooth Power: On
Discoverable: Off
Connectable: Yes
Auto Seek Pointing: Off
Remote wake: On
Vendor ID: 0x0930
Product ID: 0x0223
HCI Version: 0x6
HCI Revision: 0x15B1
LMP Version: 0x6
LMP Subversion: 0x220E
Device Type (Major): Computer
Device Type (Complete): Mac Portable
Composite Class Of Device: 0x38010C
Device Class (Major): 0x01
Device Class (Minor): 0x03
Service Class: 0x1C0
Auto Seek Keyboard: Off
On an original MacBook Pro it looks like this:
Code:
Apple Bluetooth Software Version: 4.3.0f10 14890
Hardware, Features, and Settings:
Name: ----
Address: ----
Bluetooth Low Energy Supported: Yes
Handoff Supported: Yes
Instant Hotspot Supported: Yes
Manufacturer: Broadcom
Transport: USB
Chipset: 20702A3
Firmware Version: v147 c5799
Bluetooth Power: On
Discoverable: Off
Connectable: Yes
Auto Seek Pointing: On
Remote wake: On
Vendor ID: 0x05AC
Product ID: 0x821D
HCI Version: 0x6
HCI Revision: 0x16A7
LMP Version: 0x6
LMP Subversion: 0x2293
Device Type (Major): Computer
Device Type (Complete): Mac Portable
Composite Class Of Device: 0x38010C
Device Class (Major): 0x01
Device Class (Minor): 0x03
Service Class: 0x1C0
Auto Seek Keyboard: On
Interestingly enough the chipset ID is the same between both devices and both are USB connected.
Maybe since its the same chipset some native Apple Kext can be used instead of bluetooth firmware uploader?
Also there is an interesting discussion on some Russian sites that Bluetooth is not at all relying on Bluetooth 4.0 or Bluetooth Low energy.
There is a check in /System/Library/PrivateFrameworks/Sharing.framework which checks against a variable deviceSupportsAWDL.supportsAWDL which is a boolean value.
Ideally figuring out how this variable is set, and ensuring its set properly should enable hand-off on most if not all computers irregardless of exact hardware specifications.