Humor obviously doesn’t always translate. I certainly did not mean any sort of condescension. My point was simply that wired headphones don’t have these issues and that in spite of being “old-fashioned,” it wasn’t (and isn’t) necessarily a worse system. Anything wireless is always going to be more sensitive to any sort of EMF. The most reliable headphones I have are a basic pair of wired headphones attached to a 5-year-old iPod Nano. And that’s what I use most often still for listening to music - and not just when I Zwift - because it just works.
We are extremely sensitive to the impact of EMF, because more often than not, it’s interference that is causing trainer dropouts or powermeter dropouts that are affecting Zwift.
When you have a bunch of wireless devices all transmitting across a relatively narrow spectrum of frequencies, interference is inevitable. We can test our code to make sure we aren’t unnecessarily adding to that interference by accessing BLE when it’s not needed, but we cannot test every combination of headphone/trainer/heart rate strap/powermeter/etc. And even if we could test them, we couldn’t actually do anything about it.
Unfortunately, this is just not a problem I can solve. The initial thread was “stop scanning on BLE.” And I was able to confirm that is exactly what we do already. We only access BLE during the initial pairing process and unless you connect a BLE sensor, we never again touch it. The fact that BLE dropouts happen because of EMF while riding Zwift is not because of anything we are doing; it’s just because of all the wireless devices in close proximity actively broadcasting and receiving at the exact same time.
I wish that I could fix this. But unfortunately wireless interference is a problem of physics, not of Zwift.