Closed eirinaios closed 10 years ago
Sorry for double posting. My browser doesn't work well with Github I guess :)
That should not be happening. What does the Notification Log show for subsequent notifications? I might have just reproduced it, or a similar issue where VN doesn't speak after shake, and am looking into it.
The issue I had was "speak failed: not bound to TTS engine". I restarted the service to fix it and have not been able to reproduce.
I do see an issue where one or two notifications after the one intentionally silenced by shake are also "silenced by shake" even without shaking, but after that it's fine. It's far from perfect and I'll need to improve it. Until then, you can disable shake-to-silence by leaving it blank if it's too much of a problem.
I've found my voice notify silenced. I press test and it puts a notification into the stream but does not read it out it defaults to a notification tone. shake to silence set to 100. now setting to blank as a check.
I believe there is an issue with the Shake-to-silence feature. When the device is shaken with Shake-to-silence turned on, Voice Notify immediately stops announcing the current notification, but also stops reading any further notifications after that, until one manually restarts the service (or the device). I don't know if this is the intended behavior, but I'd think that it should affect only the notification being read when the device is shaken. Tested on Samsung Galaxy S4 (Android ver. 4.2.2 and 4.4.2).
Thanks!