Quick answer: When a game has no sound on certain devices but works elsewhere, audio is failing to initialize or output on those devices: no audio output available, an unsupported audio format or configuration, audio device selection problems, or initialization failing without fallback. Capture which devices are silent, then handle audio initialization failures gracefully, support the audio formats/configurations those devices use, and handle audio device selection and changes.

No sound is a glaring problem for affected players, the game appears to work but is silent. When it happens only on some devices, it's a device-specific audio issue: something about those devices' audio output, formats, or configuration isn't handled. Fixing it means finding the affected devices and making audio handling robust across device variations.

Why Some Devices Have No Sound

Audio output varies across devices, and a game that doesn't handle the variation can end up silent on some. Causes: audio initialization failing, the game's audio system fails to initialize on that device (an unsupported configuration, a missing driver, an output issue) and doesn't recover, so there's no sound. Unsupported format/configuration, the audio format, sample rate, or channel configuration the game uses isn't supported by that device. Device selection issues, the game picks the wrong audio output device, or doesn't handle there being no default/available device correctly. And no fallback, if the preferred audio path fails, there's no fallback, leaving silence.

So no-sound-on-some-devices is a device-specific audio compatibility problem, those devices have an audio configuration the game isn't handling, where most devices work fine.

How to Diagnose It

Capture which devices are silent, the pattern (a platform, a device type, a certain audio configuration) identifies the cause. Check whether audio is initializing successfully on the affected devices (is the audio system reporting a failure?), and whether the format/output the game uses is supported there. If sound fails on a specific platform or device type, it's a compatibility/configuration issue for those.

Bugnet captures reports with device context, so no-sound reports and the devices they affect surface, revealing whether it's a particular platform or device configuration, which distinguishes a general audio bug from a device-specific compatibility gap. Capturing audio initialization failures (if you log them) also directly shows where audio init is failing.

How to Fix It

Make audio handling robust across devices. Handle audio initialization failures gracefully, if audio fails to initialize on a device, handle it (retry, fall back to a different configuration) rather than ending up silent, and don't let an audio init failure break the game. Support the formats/configurations devices use, use widely-supported audio formats and handle different sample rates/channel configurations, so the device's audio is supported. Handle device selection and changes, select an appropriate output device, handle the case of no default device, and handle audio devices changing (plugging in headphones, etc.) so audio follows correctly.

Provide fallbacks so a failed audio path degrades to a working one rather than to silence. After fixing, verify sound works across the previously-silent devices (or via field data, that no-sound reports on them stop). Robust audio initialization and device handling, with fallbacks and broad format support, is what makes audio work across the variety of devices and audio configurations your players have, rather than being silent on the ones you didn't account for.

No sound on some devices is a device-specific audio failure, init, format, or device selection. Handle audio init failures and device changes gracefully, with fallbacks instead of silence.