Woodridge, IL
Quoted from markmon:It should be impossible for a non-paired Bluetooth device to cause another non-paired device to reboot. The device that is rebooting is at fault and is not handling radio wave interference correctly.
As an fyi, jjp uses off the shelf Bluetooth adapter with Linux drivers. They did not write their own Bluetooth stack or manufacture the Bluetooth device or write the driver for it. That off the shelf stuff might suck, who knows. But it is unacceptable to have your device react to external signals with a crash and reboot. I'd be all over vive on this.
I have to agree with this. If JJP's system was the issue, there would be a lot more issues across the board w/generic Bluetooth & Linux Drivers. While I don't have any exact evidence to speak to, my guess is the Bluetooth in the Vive is proprietary and more likely to be the culprit of the issue based on shear numbers alone. Also the fact that the Vive is rebooting based on outside signals also speaks to it being the issue. This simply shouldn't happen. Reboots are serious things. This means there is a fault in the code that is making routines exit because it doesn't know what else to do.
Either way this must be frustrating. I would focus on the the fellow that is giving you feedback with a similar setup. Exactly what version of Bluetooth is JJP running on his machine? What rev of Vive do you have? There has to be a difference.
