# Problem with audio input in Android device (Galaxy S10) **URL:** \ **Category:** Unity\ **Tags:** android\ **Created:** [May 22, 2024, 4:39pm UTC](https://qa.fmod.com/t/problem-with-audio-input-in-android-device-galaxy-s10/21651 "2024-05-22T16:39:31Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![lingolooper](https://avatars.discourse-cdn.com/v4/letter/l/90ced4/32.png) [@lingolooper](https://qa.fmod.com/u/lingolooper)\ **Post date:** [May 22, 2024, 4:39pm UTC](https://qa.fmod.com/t/problem-with-audio-input-in-android-device-galaxy-s10/21651/1 "2024-05-22T16:39:31Z")
Hi there! We’ve run into a strange issue with a Samsung Galaxy S10 device. For some reason, RuntimeManager.CoreSystem.getRecordDriverInfo returns a channel count of 2 (stereo). Which shouldn’t be the case, as it doesn’t have a stereo microphone. I’m trying to force to mono, but the resulting audio is not usable / sample values are 0. This is the code we’re using: ```auto CREATESOUNDEXINFO exinfo = default; exinfo.cbsize = Marshal.SizeOf(typeof(CREATESOUNDEXINFO)); exinfo.numchannels = 1; exinfo.format = SOUND_FORMAT.PCMFLOAT; exinfo.defaultfrequency = deviceSampleRate; exinfo.length = (uint)(deviceSampleRate * sizeof(float)); var sys = RuntimeManager.CoreSystem; if (!Check(sys.createSound("recording", MODE.LOOP_NORMAL | MODE.OPENUSER, ref exinfo, out _sound), "Failed to call `createSound`")) return null; if (!Check(_sound.getLength(out _soundLength, TIMEUNIT.PCM), "Failed to call `getLength`")) return null; if (!Check(_sound.getFormat(out var st, out var sf, out var sc, out var sb), "Failed to call `getFormat`")) return null; Log.Debug($"FMOD Recording SoundType:{st} Format:{sf} Channels:{sc} Bits:{sb} freq:{deviceSampleRate}"); // Start recording into the sound buffer if (!Check(sys.recordStart(_deviceID, _sound, true), "Failed to call `recordStart`")) return null; IsRecording = true; ``` Is this approach correct? Should we try any other settings? The thing is that on this S10 device, other apps are using the device mic just fine. That means to me that there must be an issue with FMOD or our implementation. Maybe you have an idea what this could be about; and what we should try next. Thank you! ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [May 28, 2024, 12:23am UTC](https://qa.fmod.com/t/problem-with-audio-input-in-android-device-galaxy-s10/21651/2 "2024-05-28T00:23:34Z")
Hi, Thank you for sharing the code. Unfortunately, I was unable to reproduce the issue from our end. Can I get the version number of the FMOD and FMOD Unity integration plugin you are using? Also, would it be possible for you to download the [OboeTester](https://play.google.com/store/apps/details?id=com.mobileer.oboetester&hl=en_US&pli=1) to your Galaxy S10 device and run a `RECORD AND PLAY` test to check the `Channels` number and share a screenshot with us? ---
**Author:** ![lingolooper](https://avatars.discourse-cdn.com/v4/letter/l/90ced4/32.png) [@lingolooper](https://qa.fmod.com/u/lingolooper)\ **Post date:** [May 30, 2024, 9:53am UTC](https://qa.fmod.com/t/problem-with-audio-input-in-android-device-galaxy-s10/21651/3 "2024-05-30T09:53:56Z")
Thank you for looking into this! We are on FMOD Studio Unity Integration 2.02.19, and FMOD Studio itself shows the same version. This is what OboeTester shows us: ![s10_test_result](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/8/8e44b988c6303ad3c1461ae295cc48536fc48819.jpeg) ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [June 2, 2024, 10:59pm UTC](https://qa.fmod.com/t/problem-with-audio-input-in-android-device-galaxy-s10/21651/4 "2024-06-02T22:59:29Z")
Thank you for sharing the screenshot! It seems that Galaxy S10 does have 2 channels, and I can see clearly that you already force them to mono by setting the channel number to 1. I apologize if my previous reply was unclear. Could you please click the `RECORD` button while you are in `Recorder Test` and check if any bars show up at the bottom? Just want to confirm how many bars are shown up and if they are responding correctly based on the direction where sound comes from. ---
**Author:** ![lingolooper](https://avatars.discourse-cdn.com/v4/letter/l/90ced4/32.png) [@lingolooper](https://qa.fmod.com/u/lingolooper)\ **Post date:** [June 6, 2024, 7:56am UTC](https://qa.fmod.com/t/problem-with-audio-input-in-android-device-galaxy-s10/21651/5 "2024-06-06T07:56:22Z")
Here is a video pressing record and checking out the results: [VID\_20240605\_212838.mp4 - Google Drive](https://drive.google.com/file/d/1CpExIj5TFdGYJH7C-TkmRlihWgw9ERfH/view?usp=sharing) The bars at the bottom don’t seem to do anything. Does that mean it’s a device/os issue and not FMOD? I do wonder why other apps seem to be recording and using the MIC fine… ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [June 7, 2024, 1:54am UTC](https://qa.fmod.com/t/problem-with-audio-input-in-android-device-galaxy-s10/21651/6 "2024-06-07T01:54:45Z")
Thanks for the video! Yes, I agree with you, It doesn’t seem like your device’s issue if you can get other recording apps working properly. In your Unity project, could you please try ticking [Enable API Error Logging](https://fmod.com/docs/2.02/unity/settings.html#enable-api-error-logging), setting [Logging Level](https://fmod.com/docs/2.02/unity/settings.html#logging-level) to `Log` within your FMOD Settings? (FMOD =\> Editor Settings), **![](https://lh7-us.googleusercontent.com/docsz/AD_4nXf-586JoGwl2sh4Oe2U70Itdn4_0a9hznqsyuoNXoQEpf8tL_kWZgqkM1N5w2jPctqeihYYw5eaEj1VjoR44RF0G6l3Q6GKXCDdgN4e2SoaeQ5G2dXnG9W7jit3smFxVesOGlpY9Cabq35Eyl7ZQek5Vwo?key=IKAlXaYwqW14kGBCs6agoQ)** Would it be possible for you to share a Log file saved to a text file from your device while running the mono recording project? It would help us to pinpoint the issue if you could upload it to your [profiler](https://fmod.com/profile#uploads).