I'm thinking that the Speech Commands process is constantly "active," and so the inactivity timer that triggers Screen Saver/Energy Saver never hits the time limit.
In Activity Monitor I can see 'Speakable Items Server' process (starts when you turn Speakable Items On in System Prefs) and 'Speakable Recognition Server' always busy taking 0.2% and 0.6% CPU. Taking a sample of the first process I could see an uninterrupted loop that handles 'spoken messages' even though I set it up to listen when a key is pressed.
It seems like a bug. Can this be the desired behaviour? If yes, in the same note, the screen saver/energy saver should never run because the OS is always listening to keyboard input.
1. @solongpc: It can't (or at least shouldn't) be the "desired behavior"? If the CPU is supposed to be considered "busy" just because the "Speakable Recognition Server" is listening for the Speech Listening Key, then you could argue that the Screen / Energy Saver should never run even without Speech Commands because the OS is always "listening" for keyboard input to either: a) reset the Screen / Energy Saver Inactivity Timer or b) to input keys into the Active Window.
2. @musicwind95: Regardless of whether you can reproduce / verify the loop, the Screen / Energy Saver has consistently stopped working for me when Speech Commands is On and consistently resumed working when I stop the "Speakable Recognition Server" process or never turn on Speech Commands to begin with after an OS restart.
1. @newton69: That's exactly what I was hinting in my first reply. It cannot be the desired behaviour or else why are we having this discussion in the first place? 🙂
2. @musicwind95: You are right, I had tried too many combinations and have sampled the process for continuous listening, see below - this is the 3rd thread of the process by the way:
I have been having a similar problem with the screen saver and energy saver not working except if I run disk utilitie then it works for awhile. I use speech commands and I will turn it off to see what happens with the saver and sleep, but this problem never existed before snow leopard. Any advise is welcomed.
