# \[FMOD\] Initialization failed : Output forced to NO SOUND mode : ERR\_INTERNAL : An error occurred that wasn't supposed to. Contact support **URL:** \ **Category:** FMOD Engine\ **Tags:** android, unity\ **Created:** [January 5, 2023, 9:42am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706 "2023-01-05T09:42:21Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)\ **Post date:** [January 5, 2023, 9:42am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/1 "2023-01-05T09:42:21Z")
Hi, we are currently using unity 2020.3.25 and fmod 2.02.04. On a release build we are getting a few bugsnag reports with the above exception. The range of devices is quite wide (huawei, samsung, oppo, asus), but we are unable to reproduce it internally. I did some digging related to this error, found a few suggestions/reasons (volume 0 disables audio device; change lowlevel api to sles i.e) but i’m kinda against doing blind changes and testing this in the wild. Any suggestions? ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [January 9, 2023, 11:36pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/2 "2023-01-09T23:36:58Z")
Hi, Could I please get a screenshot of your FMOD Settings `Unity Toolbar -> FMOD -> Edit Settings -> Platform Specific -> Andriod`: ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/a/a04e0070f79e9d86c56c4b4da2550d1dcd7571b1.png) And a screenshot of the Build Preferences inside your FMOD Studio Project `Edit -> Preferences -> Build`: ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/2/219a323a752bcc522e489570f1a0d353385852f9.png) ---
**Author:** ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)\ **Post date:** [January 10, 2023, 8:28am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/3 "2023-01-10T08:28:58Z")
in unity we are currently using defaults ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/8/828ddc6ddeb99e15067d09d857842cffd1aa7b20.png) ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/5/5d2de915253d9ffab3731ef1d1b85c9a1d07ca35.png) ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [January 13, 2023, 3:41am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/4 "2023-01-13T03:41:46Z")
Hi, Unfortunately, I was not able to reproduce the issue. Are there any other logs that you are getting when the error is thrown? ---
**Author:** ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)\ **Post date:** [January 13, 2023, 12:55pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/5 "2023-01-13T12:55:09Z")
That’s just it… we also cannot repo it. And the release version is, well release 🙂 no logs ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [January 20, 2023, 12:50am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/6 "2023-01-20T00:50:26Z")
I see, without more information to go on it is difficult to try to solve the issue. If at any point you get more information about the bug please let me know and I will keep an eye out for a solution as well. Apologies I can’t assist further. ---
**Author:** ![miha.rataj](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@miha.rataj](https://qa.fmod.com/u/miha.rataj)\ **Post date:** [February 3, 2023, 6:38am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/7 "2023-02-03T06:38:28Z")
If it helps, we saw that this issue is happening only on the following devices: 1. HUAWEI P30 lite (MAR-LX1A) 2. HUAWEI BAH4-W29 3. HUAWEI AGS3-L09 4. HUAWEI CDY-TN00 5. HUAWEI PPA-LX3 6. HUAWEI Honor 9X (STK-LX3) 7. Xiaomi Mi 9 (MI 9) 8. HUAWEI HONOR View20 (PCT-L29) ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [February 5, 2023, 10:18pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/8 "2023-02-05T22:18:45Z")
Hi, Do you have any error logs that you can share? ---
**Author:** ![miha.rataj](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@miha.rataj](https://qa.fmod.com/u/miha.rataj)\ **Post date:** [February 6, 2023, 9:54am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/9 "2023-02-06T09:54:19Z")
Not really, only the stack trace: SystemNotInitializedException: [FMOD] Initialization failed : Output forced to NO SOUND mode : ERR\_INTERNAL : An error occurred that wasn’t supposed to. Contact support. at FMODUnity.RuntimeManager.get\_Instance .()(Unknown:-1) at FMODUnity.RuntimeManager.get\_StudioSystem .()(Unknown:-1) at FMODUnity.RuntimeManager.GetBus .(System.String path)(Unknown:-1) ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [February 6, 2023, 9:50pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/10 "2023-02-06T21:50:12Z")
Can I confirm that you have disabled Unity Audio? Under `Unity toolbar -> Edit -> Project Settings -> Audio` ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/3/3227ad96d6a6fb45f4743ef363dc2ce1acd5a499.png) Alternatively, you can run the FMOD Setup Wizard in the FMOD dropdown ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/2/22da7b47110b0cc2a761fd3e6a3540d0fc6fda9b.png) ---
**Author:** ![miha.rataj](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@miha.rataj](https://qa.fmod.com/u/miha.rataj)\ **Post date:** [February 7, 2023, 7:16am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/11 "2023-02-07T07:16:47Z")
Yes, we have it disabled already 😕 ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [February 9, 2023, 2:20am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/12 "2023-02-09T02:20:32Z")
Are you using AAB or APK for release builds? ---
**Author:** ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)\ **Post date:** [February 9, 2023, 12:10pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/13 "2023-02-09T12:10:11Z")
we are using AAB ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [February 9, 2023, 10:23pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/14 "2023-02-09T22:23:42Z")
I was not able to reproduce the issue on a Huawei device. This was downloading it through an internal test in the Play Console. If you download the app through internal testing does it replicate the issue or it only on full release? ---
**Author:** ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)\ **Post date:** [February 14, 2023, 7:33pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/15 "2023-02-14T19:33:18Z")
Why would that make any diff? ---
**Author:** ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)\ **Post date:** [February 16, 2023, 2:34pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/16 "2023-02-16T14:34:53Z")
Hm, seems that this happens also on iOS: O7UnityException: SystemNotInitializedException: [FMOD] Initialization failed : Output forced to NO SOUND mode : ERR\_OUTPUT\_INIT : Error initializing output device. at FMODUnity.RuntimeManager.get\_Instance () in \<00000000000000000000000000000000\> at iPhone 6 Plus (iPhone7,1) iPad 9 (WiFi) (iPad12,1) iPad Air (iPad4,2) iPhone 5S (iPhone6,2) iPhone 7 (Global) (iPhone9,3) os versions: 12.5.6 15.6.1 12.5.5 15.5 ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [February 20, 2023, 9:42pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/17 "2023-02-20T21:42:07Z")
Can I confirm a couple of things as I am still unable to reproduce the issue. This is only happening when the app is released from a store e.g. Google Play store or the App Store and not with internal builds? You have disabled Unity’s Audio: [[FMOD] Initialization failed : Output forced to NO SOUND mode : ERR\_INTERNAL : An error occurred that wasn't supposed to. Contact support - #10 by Connor\_FMOD](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/10) This is using the AAB build type? You are using FMOD 2.02.04? Have you tried updating to the latest release? There are no error logs other than `Initialization Failed`? ---
**Author:** ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)\ **Post date:** [February 21, 2023, 7:03am UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/18 "2023-02-21T07:03:25Z")
Our game is using bugsnag library, which we use for reporting app data and errors. So all live builds are reporting crashes (exceptions). In these bugsnag reports we have found a few exception crashes which are related to fmod. One of them is this “Initialization failed”. We couldn’t reproduce this error on our local/dev builds, or even with live release builds. Release builds are stripped, without logs, so I cannot provide any more info. We do have a minimal support for some data which could be attached to bugsnag report and I was thinking about adding a “buffered log”, but that would still require building the app with fmodL libraries, and releasing the app for everyone, which is something we are really trying to avoid… As written above: yes, happening only on release builds yes, unity audio is disabled yes, we are using AAB yes, 2.02.04; no, we didn’t update yet no, there are no other logs ---
**Author:** ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)\ **Post date:** [February 21, 2023, 1:29pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/19 "2023-02-21T13:29:58Z")
Why would AAB and PlayConsole test make a difference? ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [February 27, 2023, 11:36pm UTC](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706/20 "2023-02-27T23:36:32Z")
Hi, thank you for confirming that. Does your bug-reporting software provide a stack trace? > [@marko.ravnjak](#): > > Why would AAB and PlayConsole test make a difference? I am trying to find variations that may be causing the issue and or point us in the right direction to finding a solution. Without more information about this issue, it will be hard to resolve. If you can provide anything that may have any more information that would be really helpful. [Next page](https://qa.fmod.com/t/fmod-initialization-failed-output-forced-to-no-sound-mode-err-internal-an-error-occurred-that-wasnt-supposed-to-contact-support/19706.md?page=2)