[Android Apps and Games] brandall:
Thanks - Seems as though I have a bug in Google Now for the notifications, which is why I couldn't replicate.

Agreed, it would be useful, but unless the app devs get in touch with me and support me querying the data, I'm afraid there's nothing I can do... :(

It's midnight. I think I've solved the issue for the coming release, as it looks like a timestamp storage issue, where it doesn't respect your timezone in the offset.... I think!

:good: Much appreciated, fixed for the coming release!

Thanks for reporting this :good: How often are you getting the audio recording error? Are you starting the permanent recognition any other way (for example with Tasker)?

It being disabled when you enter the app is by design, as you may want to use some of the menus that start the normal listening.

As [MENTION=907600]Dtrieb[/MENTION] said, you can change 'start listening' using Replace Words and the actual phrase 'wake-up' in the advanced settings.

I'm afraid I've no answer for this right now. I need to spend a couple of weeks solidly on headset support to try and improve it....... :(

Pleasure! :highfive:

The app should have alerted you to this? Did it not say there was something wrong with your Google Search installation? If not, I need to see where that one slipped through the net. Thanks for confirming :good:

Thanks for sharing, I'll check it out!

Fixed for the next release, thank you! :good: Utter! TTS is in private beta at the moment. Still a good few weeks away from launch.

Sounds like you're doing some serious tweaking! :good:

1) Fixed for the next release, thanks. I's are a little more tricky as I can only do this by entering each possibility.

2) In the next release by popular request!

4) I've actually just finished setting up server back-end, so the joke database can start to grow from now on. Appreciate your offer on the Tasker commands. You should be able to use 'tell me a joke' to trigger your custom command, as if one is detected, it will override the inbuilt command.

Thanks for sharing :good:

There's a few issues here

1) If you're using the Google Text to Speech engine, this is lagging the device badly. It was improved in the update a few days back, but is still causing an issue.

2) Google don't use the Recognition API, they have their own direct implementation. Without boring you, utter! has to keep releasing the mic resource, as you may at any time need it for another application. This initialisation causes major lag on some devices. It definitely has got worse recently, but I can't investigate why as it's locked inside the Google Search app.

3) Does Auto-voice not use the overlay to show the recognition? I think they do and that again uses a different implementation which is faster (Activity based).

I'm going to be moving away from using Google within the next two weeks (although it will remain as an option). The issues and bugs have been around for too long and are crippling to the user experience.

Appreciate you sharing :good:

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

Thanks as always for the interaction, bug reports and suggestions :good:

Had my head down working on the next test build, which should be with you with 12 hours.

More coffee time! :eek:

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

For back page arrivals, latest test build is here - http://xdaforums.com/showpost.php?p=52754860&postcount=6307

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