Since the Goggles pretend to be ACM devices, the ModemManager service (remote controlled via NetworkManager) grabs the device, causing Chromium to fail connecting to it on the FPV.WTF PWA.
One option is to tell people to do systemctl stop ModemManager and systemctl disable ModemManager (or even mask), at least until they are done haxx0ring their DJI stuff.
However, people running broadband modems will run into problems, as they then cannot download packages from the internet onto their goggles.
I've spent far too long time diagnosing why the heck my Googles didn't connect. I hope this can help lead some documentation, ideally directly in the PWA's udev warning box! :)
Since the Goggles pretend to be ACM devices, the ModemManager service (remote controlled via NetworkManager) grabs the device, causing Chromium to fail connecting to it on the FPV.WTF PWA.
One option is to tell people to do
systemctl stop ModemManagerandsystemctl disable ModemManager(or evenmask), at least until they are done haxx0ring their DJI stuff.However, people running broadband modems will run into problems, as they then cannot download packages from the internet onto their goggles.
A solution would be to configure udev rules to explicitly exclude-list the DJI devices from ModemManager: https://www.freedesktop.org/software/ModemManager/doc/latest/ModemManager/ref-overview-modem-filter.html
I've spent far too long time diagnosing why the heck my Googles didn't connect. I hope this can help lead some documentation, ideally directly in the PWA's udev warning box! :)