#Bluetooth problems
4 messages · Page 1 of 1 (latest)
Iirc, and this is assuming that the VP2 uses the same bluetooth chip that the VP1 uses, the bluetooth chip never got a working driver made (by broadcom) that works with core integrity enabled. I dare say that this is a hardware design issue with that specific bluetooth chip. (Or if it was possible, broadcom simply never made one since it is a EoL bluetooth soc)
If it really bothers you and you really want to enable core isolation, you could make a backup of the drivers and then uninstall/disable them.
I am not fully sure if Vive console requires it, but I would be surprised if it does.
On OG vive, and Vp1, the chip is only used to communicate with the basestations (turning them on/off, and channel assigning) and firmware updates.
The tracking of the controllers are done by different, nrf based chips and are not impacted by the driver missing. Actually using the device should work just fine (minus the autostart/shutoff of the base stations)
But updating the drivers won't fix your issue, even if you did find a newer version. The chip used to communicate to the lighthouses has been EOL for a while now, there haven't been any driver updates in years.