[Android Apps and Games] brandall:
V2.1.1A up! COULD IT BE PRE BETA!?! WHOOP!

Firstly, I'm feeling nostalgic, as I see this release as a bit of a milestone for utter! I want to thank all of you for your testing support, I wouldn't have got this far (or anywhere near) without you.

I also want to thank you for your patience in returning to this thread to assist me, despite (n)utter! being useless as far as a working application goes...

I honestly will remember every one of you should utter! make me a bit of cash.

Ok, so the milestone is that the features can now be accessed without opening the application. It can be done in the following ways:

1) Create a launcher shortcut to the activity 'LauncherShortcutActivity'. Creating shortcuts on your launcher can normally be done by selecting 'Activities' when you long-press on your home-screen. Alternatively, there are third party applications you can use to create such shortcuts, like Any Cut or Minimalistic Text (donate version) and many more!

2) Long-press-search button (if you have one)

3) Shake-to-wake. This still can only be done via a Tasker profile, as I've yet to get my head around the low usage implementation of it. The profile is attached below. Import it by following the instructions from codesplice here. You'll need the latest beta version of Tasker too from here or go to the Tasker Tab in (n)utter! to have it auto-install. This shake-to-wake profile is different from the previous one posted many pages back, so you'll need to delete the old one.

For the sake of visual interaction, I've reverted to the Google Voice overlay. My custom listener is still a little buggy and I need to make further alterations to it to use outside of the application.

I've excluded (almost) all of the voice interactions for now as (n)utter! was a little OTT on telling you what was and wasn't going on. I need to decide how vocal to make utter! as standard, prior to you having any options to manual decide this.

I was getting carried away with moving all of my code into this implementation and for the sake of bug-catching, I'm going to be boring and do it function-by-function. :( But don't worry, the next feature will be added within hours of your approval of the previous one! :eek: (for as long as I can keep my eyes open).

The attached V2.1.1A includes only the Wifi, Bluetooth and Mobile data functions.

I have to give myself a pat on the back at this point, as my algorithms appear to be working very well... I hope you will find the end-of-speech to command execute time ridiculously quick... I also hope that even if you mumble or have an unusual accent, utter! will still detect the command you were after. Let me know!

In fact, the detection appears to be working so well (for me!), that I'm almost certain I'll drop the 'Android System' trigger. Fingers crossed you agree!

As long as you start with 'Android System' you can continue with whatever natural speech you want to toggle/turn on off a connection. Hoping again that utter! will establish what you want...

Once utter! has completed your request, it will say "done". It will say this REGARDLESS of whether the command was successful or not. It's there to let you know that utter! has killed itself to use no further resource. It will of course be replaced by suitable confirmation and interaction soon.

Wow, this post is huge! Erm, I think that's about it for now... I'll continue my code copying-and-pasting whilst slurping coffee... :eek:

BUGS

If something goes wrong, your screen may be left with a transparent overlay. Don't panic if you can't press anything, the back button will get rid of it!

The first time you try to use the shortcut, Android and your text-to-speech engine may raise an eyebrow. If it crashes, the second time should be fine - please do let me know if you experience this.

Both IVONA and SVOX take much longer to initialise. The voice recogniser is only displayed once the voice engine has confirmed it has configured successfully. This delay can be annoying, but is currently the price one has to pay for using a custom engine. Switch between your different voice engines to see the difference. Perhaps if you have a super fast and/or overclocked device, you may not even notice? I'm on the case to try and work-around this and leave the voice engine active whilst using little-to-no resource.

I haven't included a notification that multiple commands or no recognisable commands were detected. I will in the next release - coming very soon!