RE: https://dragonscave.space/@TheQuinbox/117180235975355073 It's honestly depressing how bad stock TTS APIs are across the board. Paperback on mobile has truly shown me this; I outline how the iOS side of this works in the quoted post, and Android is its own flavor of hacky: we synthesize ahead to temporary WAV files and chain MediaPlayer instances with setNextMediaPlayer() to kill the inter-paragraph silence put there with the stock player. On both platforms, getting a seamless reading experience means treating the system TTS purely as a text-to-speech renderer and building the player yourself.