[APP 2.3+][V3.0.7] BETA! | utter! | Your OFFLINE voice controlled personal assistant

---

Hey folks, had my head down coding and just returned to 9 new pages! Sorry I've not been here to answer posts and thanks as always to those helping out - You've been keeping GLDavis busy especially!

I've got a busy weekend ahead of me, so I'll whiz through the answers below - If I've missed your post or don't clarify anything properly, feel free to ask again or quote your original post - I'll be back on Monday, so best to do it then! Right...Thank you! Link appearing in the app very soon!Thanks for reporting this - Is it still happening in the latest release? If so, could you press 'report' when given the dialog and stick your XDA username in the box so I know it's from you! Thanks in advance Hopefully Llama should work better with the updates I made in the Tasker Plugin link in the user guide. There's another Activity to start various commands. I need to look at what other Developer options they have.

Google Voice Search is muting the audio when the recognition starts - there's nothing I can do to override it I'm afraid. I'm working on a completely different implementation, but for now it's a bug I can't fix Thank you! Link appearing in the app soon! I need to have a play with a friends car who has such a kit and see what the problem is. I've not been able to pin her down to borrow her car yet though! Soon....Thanks for your post I think all of your questions were answered.Yes, this is the case. I need to add some boxes of when it would and wouldn't apply, without making it appear overly complex to the 'average user'.I'm on the case of this. I thought it was Android murdering the Service, but I found an issue that could be related. I've improved this for the next release which I'll try and get out before the weekend, but running out of time!Oops! Got spot! It's supposed to pass it to Wolfram Alpha, I'll fix for the next release, thank you. In the mean time, you can say 'question calculate +anything which will do the same thing'.Thanks for the heads up. I'll add it to my list to see what developer options they have, if any... That's the thing with Tasker, the Dev already has these plugins built and ready to go....Thanks for the translation help offer link appearing in the app soon!

Are you running the latest Play Store version? The synthesised voice should work for any device with the Google TTS Voice Engine installed.

With these 'hacked' versions of Google Now, they normally don't work well. If you don't have the options in the Android/Language & Input/Voice Search/Download Offline files, then it's still restricted I'm afraid.... Thank you I'll add it to the list to integrate.Glad you're enjoying it The interaction level is something that I've not been able to work on as much as I wanted from the beginning - too many core functions needed first. But it's coming....

Yes, bad planning on the name 'utter' - Google Voice Search refuses to understand it! It sounded like corrupt voice engine files - Sorry I wasn't around to help you sooner, but glad it's sorted now! Hope your son enjoys it - Google Voice Search does not work well with kids voices though, which is such a shame... If you set your default voice engine to Google TTS and turn utter! off and on again from the main app page, it will use the Network Synthesised Voice, with is much smoother than the normal Google TTS Voice. It won't/can't default to it though if you've got another engine such as IVONA set.I've so nearly finished putting all of the English words into files. A link will be available soon to all those that want to translate! Are the options in Android/Language & Input/Voice Search any different for you?

Google have excluded some JB devices from using the offline recognition due to hardware limitations. I'm not sure how they apply this restriction though, or how it could be circumvented... ?Not yet, but Italian is coming soon!

If you go to the Recognition and Voices Section. Press Google and it will say 'please say some random words'. Say the Italian introduction you want to use. If it always sends back the same English 'interpretation' then you can enter that as the wake up phrase and use Italian! I hope that made sense?Could you try a simple word only please? I wonder if I've messed up the matching using numbers.......It's device dependent I'm afraid. Activates quickly for some, but not for others. I'm also killing Google a lot more to release the memory, which isn't helping the start times.. I might have to add yet another setting!Replied to a similar post above, think it's Android murdering the Service, but spotted one hole I can fix which might be a cause....Thanks for your post. I've got to focus on a few more core features at present, then I'll return (to my roots!) to some more power user based functions. I've added what you've requested to my list.I think ewingr's answer below is highly possible, especially as I'm disconnecting and reconnecting so much so not to hog the headset....It's beyond scope for me at the moment I'm afraid. This headset control could be an entire application of its own... Made even worse by the many different ways to do it depending on OS and headset type... Perhaps when I work on the A2DP profiles I can look at adding in some form of pop-up confirmation or restriction... No promises though That's a strange one... I'd suggest reinstalling your voice engine files if it persists. It's not something I've had reported before...Thanks for this, I might have to talk to you over email more to see where you think this is happening.These are both strange! If it happens again, could you let me know please. Thanks.Answered similar post above, got a hot fix coming which I hope should help....

------------------

Thanks again for all of your feedback, bug reports and suggestions folks!

I'll check in again on Monday when I'll have a bit more time. Feel free to post again then if I've not answered your question, or overlooked it!

Cheers

Ben