Well, in my opinion that isn’t a bug, it’s expected behavior when moving an app to the front that has its own audio session. Mixing with another session is opt-in behavior for OpenEars but it would be a questionable default behavior since all development would have to proceed from the possibility that there might be other unknown incoming audio while running recognition.