Thanks for the reply.
The activity does create a new instance, I check and print pointer of two activity objects, it’s different.But FMOD::System was create in CPP and I am sure I did not create new one though new activity create.I am calling all fmod’s APIs on the same FMOD::System.
I want to know is fmod system depend on the app’s activity object for playing or does it do some initializing when activity is create internally?Since fmod system is in mixerSuspend status, if it does call some api internally, it will be deadlock.Is that possible?
Launch modes set to singleInstance is my first found solution, it did fix this issue, but I can’t use this for two reason:1.This will make some unnecessary memory holding in background. 2.It conflict with my some payment SDK.It doesn’t pop the pay dialog some times.
Is there may be other reason or hint would cause this problem?Or if you can, please open more inside detail on android platforms initializing and pause/resume process?