Unable to find a solution, I have tried everything from developer options , app permissions, resetting device, usb redirect etc. I placed this under tablet however same issue with my s24 ultra. While streaming with OTG cable connected and app sound working through OBS, when the in game voice chat microphone is activated the sound is redirected to the tablet or phone. The specific app is call of duty mobile and devices are Tab S9, S24 Ultra. Is this a android issue more than a Samsung issue?
This is almost certainly an Android issue, rather than a Samsung-specific one, though Samsung's implementation of Android can sometimes add its own quirks. Here's why and what's happening: * Android's Audio Routing Complexity: Android's audio routing is notoriously complex, especially when dealing with multiple audio inputs and outputs (like your device's internal mic, external mic via OTG, game audio, voice chat audio, and OBS). * Voice Chat Priority: When you activate the in-game voice chat microphone, the game (or the underlying Android system) likely attempts to take exclusive control of the microphone input and, in some cases, redirect all audio related to that communication (including the output) to what it considers the "default" communication device. In your case, it's defaulting back to the phone/tablet's internal speakers/mic rather than the external path you've set up for OBS. * App-Specific Behavior: Call of Duty Mobile, like many games with built-in voice chat, has its own internal audio management. It might be designed to prioritize its voice chat audio through the device's default communication channels, overriding external audio routing settings. This is a common challenge for mobile streamers. * OTG Limitations/Conflicts: While OTG cables allow you to connect external devices, Android's handling of complex audio scenarios (like simultaneous game audio output and voice chat input/output through different paths) isn't always seamless. Why your previous troubleshooting steps might not have worked: * Developer Options, App Permissions, USB Redirect: These settings often give you control over general audio output or input, but they don't typically allow for granular control over how an application's specific voice chat module routes its audio, especially when it tries to take over. * Resetting Device: This mostly addresses software glitches, but not fundamental design choices in Android's audio framework or how a specific app like CODM interacts with it. Is there a solution? It's difficult. Many mobile streamers encounter this exact problem. Common workarounds or potential solutions often involve: * External Mixers/Interfaces: Using a more advanced external audio interface that can mix multiple audio sources (game audio, mic audio) before sending it to OBS might be a more robust solution. This involves the interface taking the audio from the phone and routing it, rather than relying on the phone's internal routing. * Software Solutions (Less Common for Mobile): On PC, you'd use virtual audio cables or routing software. Mobile Android has fewer robust options for this. Some apps might offer more granular control, but they often require root access or might not be compatible with all devices/Android versions. * Using a Separate Device for Voice Chat: Some streamers use a separate phone/tablet for their game audio capture and then a different headset/mic connected to their streaming PC for their voice chat, bypassing the mobile device's in-game chat entirely. This means they are listening to in-game chat on their phone/tablet, but speaking into a mic connected to the PC. * Game-Specific Settings: Double-check all audio settings within Call of Duty Mobile itself. There might be an obscure setting that allows for different output/input devices for voice chat, but it's often limited. Given that you've tried extensive troubleshooting on two different Samsung devices with the same Android version, it strongly points to a deeper Android audio routing behavior that's particularly problematic with in-game voice chat when using external audio setups like yours.
This is almost certainly an Android issue, rather than a Samsung-specific one, though Samsung's implementation of Android can sometimes add its own quirks. Here's why and what's happening: * Android's Audio Routing Complexity: Android's audio routing is notoriously complex, especially when dealing with multiple audio inputs and outputs (like your device's internal mic, external mic via OTG, game audio, voice chat audio, and OBS). * Voice Chat Priority: When you activate the in-game voice chat microphone, the game (or the underlying Android system) likely attempts to take exclusive control of the microphone input and, in some cases, redirect all audio related to that communication (including the output) to what it considers the "default" communication device. In your case, it's defaulting back to the phone/tablet's internal speakers/mic rather than the external path you've set up for OBS. * App-Specific Behavior: Call of Duty Mobile, like many games with built-in voice chat, has its own internal audio management. It might be designed to prioritize its voice chat audio through the device's default communication channels, overriding external audio routing settings. This is a common challenge for mobile streamers. * OTG Limitations/Conflicts: While OTG cables allow you to connect external devices, Android's handling of complex audio scenarios (like simultaneous game audio output and voice chat input/output through different paths) isn't always seamless. Why your previous troubleshooting steps might not have worked: * Developer Options, App Permissions, USB Redirect: These settings often give you control over general audio output or input, but they don't typically allow for granular control over how an application's specific voice chat module routes its audio, especially when it tries to take over. * Resetting Device: This mostly addresses software glitches, but not fundamental design choices in Android's audio framework or how a specific app like CODM interacts with it. Is there a solution? It's difficult. Many mobile streamers encounter this exact problem. Common workarounds or potential solutions often involve: * External Mixers/Interfaces: Using a more advanced external audio interface that can mix multiple audio sources (game audio, mic audio) before sending it to OBS might be a more robust solution. This involves the interface taking the audio from the phone and routing it, rather than relying on the phone's internal routing. * Software Solutions (Less Common for Mobile): On PC, you'd use virtual audio cables or routing software. Mobile Android has fewer robust options for this. Some apps might offer more granular control, but they often require root access or might not be compatible with all devices/Android versions. * Using a Separate Device for Voice Chat: Some streamers use a separate phone/tablet for their game audio capture and then a different headset/mic connected to their streaming PC for their voice chat, bypassing the mobile device's in-game chat entirely. This means they are listening to in-game chat on their phone/tablet, but speaking into a mic connected to the PC. * Game-Specific Settings: Double-check all audio settings within Call of Duty Mobile itself. There might be an obscure setting that allows for different output/input devices for voice chat, but it's often limited. Given that you've tried extensive troubleshooting on two different Samsung devices with the same Android version, it strongly points to a deeper Android audio routing behavior that's particularly problematic with in-game voice chat when using external audio setups like yours.
Wow thanks for the in depth reply, much appreciated! Sounds like I should have went with apple instead, bummer! Ill look into the External Mixers/Interfaces option. Thanks again.
