Android 9/10 crash in FMOD 2.00.09

here is the crash log:
17308-25 13:59:47.271 27617 28236 E CRASH : signal 6 (SIGABRT), code -1 (?), fault addr --------
17408-25 13:59:47.271 27617 28236 E CRASH : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
17508-25 13:59:47.271 27617 28236 E CRASH : Build fingerprint: ‘HUAWEI/LIO-AN00/HWLIO:10/HUAWEILIO-AN00/10.1.0.152C00:user/release-keys’
17608-25 13:59:47.271 27617 28236 E CRASH : Revision: ‘0’
17708-25 13:59:47.271 27617 28236 E CRASH : pid: 27617, tid: 28236, name: FMOD Studio upd >>> com.xxxxx.xxx.xxxx <<<
17808-25 13:59:47.271 27617 28236 E CRASH : r0 00000000 r1 00006e4c r2 00000006 r3 c13e3cc0
17908-25 13:59:47.271 27617 28236 E CRASH : r4 c13e3cd4 r5 c13e3cb8 r6 00006be1 r7 0000016b
18008-25 13:59:47.271 27617 28236 E CRASH : r8 c13e3cd0 r9 c13e3cc0 sl c13e3cf0 fp c13e3ce0
18108-25 13:59:47.271 27617 28236 E CRASH : ip 00006e4c sp c13e3c90 lr eba1f143 pc eba1f156 cpsr 00000006
18208-25 13:59:47.271 27617 28236 E CRASH :
18308-25 13:59:47.271 27617 28236 E CRASH : backtrace:
18408-25 13:59:47.625 27617 28236 E CRASH : #00 pc 0002a156 /apex/com.android.runtime/lib/bionic/libc.so (abort+4294795429)
18508-25 13:59:47.625 27617 28236 E CRASH : #01 pc 0000013f /system/lib/libstdc++.so (__cxa_pure_virtual+4294963210)
18608-25 13:59:47.625 27617 28236 E CRASH : #02 pc 0001931f /data/data/com.xxxx.xxx.xxx/xxxx/com.xxx.xxx.xxx/lib/libfmodstudio.so
18708-25 13:59:47.625 27617 28236 F mono : * Assertion: should not be reached at mini.c:2215
18808-25 13:59:47.626 27617 28236 E CRASH : chained_signal_handler 605 got 11

Is there anywhere I can download the android symbol file ?

In addition, in Android device, background music has noise, which needs to be set output to FMOD.OUTPUTTYPE.AUDIOTRACK,

Hi allm3,

This issue is fixed in 2.00.10. Upgrade to that version and the issue should be sorted.

Thanks , We’ve upgraded the version to 2.00.10 and will continue to focus on crashes.

But why is the music noise problem , which needs to be set outputType to FMOD.OUTPUTTYPE.AUDIOTRACK in Android device?

The issue you describe is related to audio latency and isn’t specific to background music.

On Android, there’s a lot of variation in audio latency between the different devices and OEMs. For instance, we haven’t had any reports, nor seen ourselves, this issue happen on any Pixel handsets.

To work around this, we make some dynamic adjustments to increase latency to avoid “noise” from appearing. We plan to add some additional latency adjustment in future versions to catch these additional instances that you are seeing, while avoiding negatively affecting handsets that have adequate support.

The reason AudioTrack does not encounter this is that it operates at higher latency (so more buffering). AAudio (where you would see this issue), is much lower latency, so assuming the device and OS are able to take advantage of it, will provide a more responsive audio experience.

I hope that clarifies what is happening.