TTS settings in ICS not taking effect

[Nolan Darilek]

In previous versions of Android, changing TTS settings took effect
almost instantly. If I changed an engine or rate, Spiel started speaking
with the new values after only a short delay.

Under ICS, I'm noticing that this doesn't appear to be the case. It
takes a full phone reboot, Windows style, to make these changes take effect.

Am I missing something in my code, some new intent that I should be
receiving to re-initialize TTS when the settings change? A brief skim
through the Android sources didn't reveal anything.

I'm about to implement code that monitors the secure settings content
provider, notes any TTS setting changes and re-initializes TTS. Is there
any point to this? I'd hate to implement all of that only to discover
that the system will not use the newly-set values even if I do
re-initialize. I'm noticing that Android doesn't respond when apps opt
to use a new engine, so I can't for instance have my screen reader use
the responsive but low-quality Espeak, but my ebook reader use the
higher-quality Ivona. This has me thinking that there's more to this
problem, and that I'd be wasting a lot of time trying to monitor the
secure settings content provider.

Thanks.