Hi,
Well, the intention is for Flite to do its own suspension and resumption on an in-progress listening loop – the usual situation is that listening is either stopped, or it is not stopped and not suspended, so Flite does the right thing since it has to suspend listening for TTS and then handle its own resumption. I can document that if Flite speech is used while listening is already suspended, the suspension state has to be reasserted in the callback at the end of speech.