# Android Crash (pthread\_mutex\_lock)

**URL:** <https://qa.fmod.com/t/android-crash-pthread-mutex-lock/18801>\
**Category:** FMOD Engine\
**Tags:** android, cpp\
**Created:** [May 25, 2022, 4:50pm UTC](https://qa.fmod.com/t/android-crash-pthread-mutex-lock/18801 "2022-05-25T16:50:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\
**Post date:** [May 26, 2022, 12:47am UTC](https://qa.fmod.com/t/android-crash-pthread-mutex-lock/18801/2 "2022-05-26T00:47:14Z")

</div>

I suppose it remotely resembles the call stacks here [FMOD crash on Android and iOS - #18 by maksimomelyanchuk](https://qa.fmod.com/t/fmod-crash-on-android-and-ios/15780/18) and here [Libfmod crash in android](https://qa.fmod.com/t/libfmod-crash-in-android/17964), which at the time were due to issues in headset detection, but I can’t really draw a correlation just on that call stack. We did recently have some more fixes to headset detection in 2.02.06, maybe you could try updating to the latest version of FMOD?  
Owtherwise, since this is your most prominent issue, I think it would be worth shipping with logging libs to get as much info as possible.

---

_[View the full topic](https://qa.fmod.com/t/android-crash-pthread-mutex-lock/18801)._