# Crash on Android 16 in "FMOD mixer thre" After Migrating from FMOD Ex

**URL:** <https://qa.fmod.com/t/crash-on-android-16-in-fmod-mixer-thre-after-migrating-from-fmod-ex/23397>\
**Category:** FMOD Engine\
**Tags:** cpp\
**Created:** [September 25, 2025, 6:14am UTC](https://qa.fmod.com/t/crash-on-android-16-in-fmod-mixer-thre-after-migrating-from-fmod-ex/23397 "2025-09-25T06:14:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bettercallNick](https://avatars.discourse-cdn.com/v4/letter/b/3be4f8/32.png) [@bettercallNick](https://qa.fmod.com/u/bettercallNick)\
**Post date:** [September 25, 2025, 6:14am UTC](https://qa.fmod.com/t/crash-on-android-16-in-fmod-mixer-thre-after-migrating-from-fmod-ex/23397/1 "2025-09-25T06:14:48Z")

</div>

Hi everyone,

We are in the process of migrating our game from FMOD Ex to the latest FMOD version and have run into a consistent crash on Android 16. The game runs perfectly on older Android versions (14, 15), but on Android 16 we get a fatal error.

The crash occurs when the application is paused and then resumed. The logcat consistently points to a segmentation fault in the “FMOD mixer” thread.

```auto
Here is the key information from the crash report:

```

`pid: 19913, tid: 22464, name: FMOD mixer thre >>> com.my.game <<<`  
`signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0`  
`Cause: null pointer dereference`

We are currently investigating our implementation of the application lifecycle functions (`onPause`/`onResume`) and our FMOD initialization settings, as this seems to be the likely cause.

Before we go too deep, we wanted to ask the community: are there any specific, known changes or requirements for FMOD on Android 16 that we should be aware of? Are there any common pitfalls when migrating from FMOD Ex that could cause this kind of crash on newer Android versions?

Any advice or pointers would be greatly appreciated.

Thanks!

---

<div class="post-metadata">

**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:** [September 29, 2025, 12:03am UTC](https://qa.fmod.com/t/crash-on-android-16-in-fmod-mixer-thre-after-migrating-from-fmod-ex/23397/2 "2025-09-29T00:03:28Z")

</div>

Hi,

Thank you for sharing the information!

> [@bettercallNick](#):
>
> Before we go too deep, we wanted to ask the community: are there any specific, known changes or requirements for FMOD on Android 16 that we should be aware of?

We haven’t received similar reports on Android 16 so far.

> [@bettercallNick](#):
>
> Are there any common pitfalls when migrating from FMOD Ex that could cause this kind of crash on newer Android versions?

There’s some information on moving from FMOD Ex to FMOD Studio here :  
[https://fmod.com/docs/2.03/api/advanced-core-api-topics.html#transitioning-from-fmod-ex](https://fmod.com/docs/2.03/api/advanced-core-api-topics.html#transitioning-from-fmod-ex)

---

<div class="post-metadata">

**Author:** ![bettercallNick](https://avatars.discourse-cdn.com/v4/letter/b/3be4f8/32.png) [@bettercallNick](https://qa.fmod.com/u/bettercallNick)\
**Post date:** [September 30, 2025, 10:00am UTC](https://qa.fmod.com/t/crash-on-android-16-in-fmod-mixer-thre-after-migrating-from-fmod-ex/23397/3 "2025-09-30T10:00:46Z")

</div>

Hi FMOD team,

I appear to be the first to report a crash in the FMOD mixer thread on Android 16. No other developers have posted similar issues yet. The crash is reproducible after pause/resume, and only occurs on Android 16 (works fine on 14/15).

Is there any internal testing or roadmap for Android 16 support, especially regarding new memory protections (PAC, address tagging)? Should I expect a future FMOD release to address this, or is there a recommended workaround?

Thank you for your attention.

---

<div class="post-metadata">

**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:** [September 30, 2025, 11:43pm UTC](https://qa.fmod.com/t/crash-on-android-16-in-fmod-mixer-thre-after-migrating-from-fmod-ex/23397/4 "2025-09-30T23:43:43Z")

</div>

Thank you for sharing the extra info!

> [@bettercallNick](#):
>
> Is there any internal testing or roadmap for Android 16 support, especially regarding new memory protections (PAC, address tagging)? Should I expect a future FMOD release to address this, or is there a recommended workaround?

I wasn’t able to reproduce the crash on my end. Would it be possible to share the full crash tombstone as a text file? You could upload it to your [profile](https://www.fmod.com/profile#uploads).