yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] iHelp101:
Looks like this is a busy week. I got an alert I set up for Google Search updates. It looks like the Google Search app was updated today. The second I get the new APK I will update the hooks. Anyone have the new update yet? Below is the link to the Play Store were you can see the changed date.

https://play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox
[Xposed Framework Modules] iHelp101:
Quick update it looks like they changed no hooks in the recent update. Bad news is I derped up and when adding the newer hooks for Google Search 4.0 and the custom Google Search 3.8.0.1 I messed up a little on the if statement logic. So it doesn't set the hooks for Google Search 3.6.15. My bad, but the fixed APK is below.
[Xposed Framework Modules] abuttino:
You want a fast way to get the latest apk?

Follow APK Mirror on G+
[Xposed Framework Modules] Cptnodegard:
Is there any way to cancel out the request being processed by Now itself? I.e. have it prevent Google Now from actually googling how to turn my lights off when I use it to instruct AutoVoice to do so? If not via canceling the request directly, then perhaps by adding a feature to automatically go back to the default screen after the request is sent off. I imagine that would have side effects, however, unless there's a way for the plugin apps to report back that "yep, this is a query that is meant for me, so go ahead and reset Now itself".

Then again, this might be something that you could build into AutoVoice instead, João. Perhaps have AV populate a Tasker variable with a boolean value for whether the command was received from Now? That would have other uses as well, especially if card integration ever becomes possible.
[Xposed Framework Modules] Drsela:
I'm experiencing some issues with this plugin!

Whenever I say "Play songs by Imagine Dragons", it opens Google Music, Google Music scans my libary for anything named "s Imagine Dragons".

If I say "Play song by Imagine Dragons", Google Music searches for "Imagine Dragons" but doesn't start to auto-play.

"Next/Previous track/Song" doesn't seem to work either

"Play song <title" is working just fine - just like "volume up/down/max".

"What song is this" opens Shazam as intended and starts to listen for audio.

Overall, pretty nice! I like what you've created, and can't wait to see the opportunities!
[Xposed Framework Modules] Wicked4u2c:
MohammadAG You are the man! Here is a video I put together on some of the things you can do with it, fantastic Job!

[YOUTUBE]wI4bSMiO_xY[/YOUTUBE]
[Xposed Framework Modules] matteo2:
Can I add italian language?

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Xposed Framework Modules] joaomgcd:
Oh, sorry! Missed it! Will make use of it tomorrow, thanks!
[Xposed Framework Modules] matteo2:
How?

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Xposed Framework Modules] Att.Fan1982:
1+
[Xposed Framework Modules] Dovidhalevi:
Great!

As I PM'd, like an interface to get on-line voice into Google Search (voice search assistant only works with ICS modded old version).

Installed lyrics and song player plugins

AZ Lyrics worked like a charm.

Could not play a song, maybe because I need another reboot after installing? Should not such a plug take name of the player app in its UI (or bring up the usual once or always chooser)? The lyrics plugin knows where to look, no az, no lyrics from the plugin.

When I have more fluid voice operations, the tasker and toggle plugins will be quite useful (toggles could as well be done using Tasker but the separate plugin makes Tasker not necessary for those functions!).
[Xposed Framework Modules] joaomgcd:
By the way, in your Google Now explorations did you find a way to send voice data to the voice recognition activity of Google Now, so you can send an intent with a question and Google Now would respond with voice rather then just visual results? I saw some videos of the Moto X and it seems that's what it does, because the voice is recognized prior to opening Google Now.

Thanks again!
[Xposed Framework Modules] Valounours:
Hi,

Your Plugin don't wok with autovice 1.5.5 ?

Thank's in advance, Valounours
[Xposed Framework Modules] scag21:
Same here, im pretty sure i got everything right but it is not responding. I have 1.5.5 autovoice as well.
[Xposed Framework Modules] Valounours:
Yes Autovoice is not listed in plugin list

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Xposed Framework Modules] matteo2:
With autovoice from play store i can speak only 4 letters...

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Xposed Framework Modules] Valounours:
You must bought Pro version
[Xposed Framework Modules] matteo2:
If I have autovoice, when i open Google Search can i speak directly?

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Xposed Framework Modules] MohammadAG:
It's an API, you need to make an app that makes use of it.

Not at the moment no, the second way might be doable in the sense that the app can request it, but it shouldn't be done automatically as there's no way for me to know if the request was handled by the app (sendOrderedBroadcast comes to mind though).

Oh, hmm, try Play song (without the S) by Imagine Dragons. If that works, then I need to change something in the plugin.

It's funny how it doesn't work in Google Play Music, but works fine in Sony's Walkman app.

Nope, haven't found anything like that, but it's probably an intent. The Moto X does indeed do that, it uses Nuance for recognition (kind of weird imo).

Please move AutoVoice related issues to the AutoVoice thread, this one is about the API.
[Xposed Framework Modules] matteo2:
I talk about the language... I'd like to speak italian

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Xposed Framework Modules] MohammadAG:
And I was answering your question. You need an app that makes use of this API, it can't do it by itself.
[Xposed Framework Modules] Drsela:
"Play Song by Imagine Dragons" is currently working! It performs a search for Imagine Dragons within Google Music!
[Xposed Framework Modules] ManHands:
Had the same issue w/ the plugin not showing up. And this worked!
[Xposed Framework Modules] Humpie:
Lately I updated my nexus 5 to 5.0, so sadly I cannot use this module anymore :crying: .

Is there maybe another way to get google now commands from android wear to tasker?
[Xposed Framework Modules] iHelp101:
I am working on a method currently that I believe AutoVoice will be implementing. It is a little buggy, so I am not opening it to the public yet. This method of course requires no root, so if Xposed has issues working we will at least have an alternate method in the future. Once I feel it is good enough that I won't worry about issues I would be happy to let you test it. I just don't like releasing unfinished work that may have bugs. I don't want people to complain about issues for an unfinished project.
[Xposed Framework Modules] Humpie:
Thanks for your reply, I will be looking forward to test it, soon I will be able to, when I receive my G watch R :)
[Xposed Framework Modules] etc6849:
This is great news! May I ask what method you plan to use (are you implementing a service on the watch itself and how might this impact battery life)? Will your new method work with native google search from Android Wear; e.g. can I say "ok google" followed by "turn on my bedroom lights," and still have Takser and Autovoice process the command? Also, please give us an email to send a paypal donation to once you've completed your work.

Not requiring root access to use Android Wear the way I am with my home automation system would be nothing short of awesome. Keep up the good work.
[Xposed Framework Modules] iHelp101:
The method is similar to the Microsoft Torque method. Instead I just of course start a service that monitors the axis and orientation of the watch. Before everyone shouts this will use a lot of battery you have to remember Googles Fit app already keeps these sensors on 24/7 to monitor steps. So I am using minimal power and I have not noticed any difference with my LG G Watch. The Moto 360 however was acting weird with my one tester.

It was draining quite fast, but the tester will be testing it for a full day and give me feedback (I know the Torque app had issues with the Moto 360 also). In terms of functionality you shake/flick your wrist and the Google Search dialog pops up. You say your command and the dialog closes (Requested feature). The command is sent to AutoVoice and then of course processed via Tasker. This will most likely not be released publicly by me, but instead implemented in AutoVoice/AutoWear.

I am just hammering out the bugs to allow an easy implementation. In terms of donations I have stated before I don't want any. I do this because I like programming and helping fellow home automators. Once you accept donations or payments people suddenly expect everything to work perfectly. The second you make that mistake with code and introduce a bug everyone states how they paid this amount of money and the product should be better. I may recruit more testers, but at the moment I am happy with my one.
[Xposed Framework Modules] iHelp101:
A quick update on the new method I spoke about before. First I would like to clear up that this method doesn't require root access and has very little battery drain. I now feel the method is stable enough that I have passed all code to João of AutoVoice. He is free to get it working like he wants and etc. The project is now his to release and I look forward to what I assume will be AutoWear.

PS: I have also posted a little teaser on the AutoVoice Google+ page!
[Xposed Framework Modules] vingar:
where is the post?

thnks
[Xposed Framework Modules] iHelp101:
Sorry for the late response. The post is at the link below. You shake the watch, the dialog pops up, and you say your command. That command is sent to AutoVoice for processing. Last the command is executed through Tasker.

https://plus.google.com/114184280042413418350/posts/AJB6b9bxtPA
[Xposed Framework Modules] chrisnash:
Wow! I really look forward to seeing this implementation.
[Xposed Framework Modules] vingar:
Wonderful!
[Xposed Framework Modules] pcpimpin:
I'm running Google Now V 4.0.26 is there anyway this can be updated to work? I know if I downgrade I can get it working. :)
[Xposed Framework Modules] iHelp101:
My bad. Here is the working APK. Enjoy.
[Xposed Framework Modules] pcpimpin:
AWESOME! Thanks! It's working great!!!
[Xposed Framework Modules] iHelp101:
I noticed a new Google Search update has been pushed out. I am assuming everyone has switched to AutoWear/AutoVoice. I think this module is officially dead and that I have no need to update the API. Anyone that still needs it reply to this thread or look into AutoVoice/AutoWear for a non-root method.
[Xposed Framework Modules] etc6849:
I still use the module, pretty please post a fixed version :)

I also tried to download AutoWear and it doesn't show up in the Playstore? Is it still in alpha (and only available to subscribers)? I paid for and use AutoVoice and like it a lot and I'm sure you and Joao did an awesome job on AutoWear.
[Xposed Framework Modules] iHelp101:
I checked all the hooks and they look like they are still correct. Which Google Search version are you using? Also if possible go to Xposed -> Logs and take a screenshot of the latest errors if any. Also I believe AutoWear is still in alpha, so yes I think you have to have a subscription.
[Xposed Framework Modules] etc6849:
Thanks for taking a look. I installed the new version and can confirm it still works. Hopefully Google leaves the hooks the same for now on or comes out with a formal API.

I also subscribed for $1.30/month to try the alpha version of autowear. However, you still need to be a member of the autoapps alpha google+ group. I asked to join last night, but nothing yet.

I do want to check out the final android wear. Did it end up working by just shaking your wrist? Is it still the case that it doesn't work by touching the screen?
[Xposed Framework Modules] Mudvayne622:
Where do I get Autowear?
[Xposed Framework Modules] etc6849:
Install autoapps. Then do the steps from my previous post.
[Xposed Framework Modules] iHelp101:
I personally have not seen what Joao did with the code passed to him. I just use the original sample I made currently till AutoWear is officially out. For the LG G Watch and Moto 360 I know the shaking wrist gesture worked quite well. I am again unsure the progress and the direction Joao is taking, so I will continue to update this module until it is useless or destroyed by Google.
[Xposed Framework Modules] flash3d:
Sorry for my ignorance but where can i find the latest version of your apk? Getting a LG G watch tomorrow and would love to us voice commands (autovoice). One page back is a link to the 1.4d(20) version, is this the latest? thx.
[Xposed Framework Modules] iHelp101:
Yes, that is the latest APK. Sorry for the late response.
[Xposed Framework Modules] flash3d:
No problem, thx.

Still i'm not getting it to work with Google Search 3.6.16.1614640.

Even installed previous Google Search 3.6.15.1496928 , but no luck.

On phone google search/now is working with autovoice/tasker but on wear device I just get the search result page.

The plugins page on the api is empty, is this normal?

Any tips?

Got it working :D , had to remove and install autovoice! wooooooooo!!!!
[Xposed Framework Modules] mdamaged:
Uninstall and reinstall autovoice.
[Xposed Framework Modules] flash3d:
Thx! just did that
[Xposed Framework Modules] flash3d:
Now that Android 5 GPE is out for my S4 and Exposed is not working (yet) on lollipop. Does anybody know the status of AutoWear? Or some other solution that works with Lollipop?

Not really eager to upgrade to lollipop and loose this fantastic combo of wear/google now/autovoice/tasker.
[Xposed Framework Modules] steviehs:
Still need for Google Now API + Autovoice?

May be I am wrong, but my humble understanding right now is:

If I wan't autovoice to react on voice commands send after a "Ok Google" from my wear device, I still need Google Now API?

If I want to react to voice commands after shaking the wear device, I need Autowear?

So for me, although autowear is getting better and better all the time, I don't want to loose the "Ok Google" start way for controlling my smart home stuff. Therefore I encourage you to continue. Or am I completely wrong with the above statement?
[Xposed Framework Modules] iHelp101:
I apologize for the late response. This is entirely correct about Android Wear. The issue is that more phones as starting to push Android Lollipop, which Xposed isn't compatible with. This was one of the main reasons to move over to a new method (Shake). I have been using the shake/flick method with Android Wear and love it. I am saddened that AutoWear isn't completely available to everyone though. I'm sure Joao is working hard to get everything working to be considered out of beta/alpha.

Google has also been making is very difficult to decompile some of their apps, so if they find a way to prevent decompiling Google Search then of course I have no way to update the module. The last reason is some people are unable to root their phones or simply don't want to. With all these possibilities you can see why I push people towards a method that doesn't "break the rules" in terms of Android's normal operations.

Google is not going to prevent developers from accessing the accelerometer and gyroscope (AutoWear), but it looks like they don't appreciate people decompiling their proprietary apps. With all that I will continue to update this module until Google prevents me from or AutoWear takes over completely.
[Xposed Framework Modules] perissatto:
Hi there guys.

First of all, i would like to thanks the developer for this amazing creation. I have followed the instructions and everything looks amazing:

My report

- Galaxy note 3 N9005 4.4.2 rooted

- Moto 360 5.0.1

- Tasker 4.6u1

- Autovoice

- Google API 1.4 (Had to download here, since i was unable to see this version on Xposed module)

Everything works ok!!!!!!!! I am not really sure if this is a bug, but when i say the command, it work, but the search information still on watch.

I saved the command "open game" and redirect to an app that i have.... the games open on my Note 3 but on the watch, the search information still look like this:

[IMG="watch"]http://s4.postimg.org/78gywinb1/20141222_091504_resized.jpg[/IMG]

Is this right ?
[Xposed Framework Modules] iHelp101:
This is normal. Sadly I have no way to control the what the watch does. I can only hook into the information the watch sends to the phone. Another method (AutoWear) fixes this issue. AutoWear is however still in beta as far as I know, so while this can be annoying it is the only working current method.
[Xposed Framework Modules] wanted66:
Hi,

I'm using a LG G Watch R and Sony Xperia Z2 unrooted phone. (Tasker, Autovoice etc)

I really like the unrooted shaking android wear method as i dont like to root my phone and lose my warranty.

I have paid and subscribed to the alpha testing and sent a request to G+ community.

Hopefully you will allow me soon cause I still cant download autowear or join the test program.

Thanks :)
[Xposed Framework Modules] iHelp101:
Hopefully you have been invited to the test group since your post. I however have no control over who is accepted or invited. I gave Joao (Developer of AutoWear) some base code for the project. I knew he would have a larger audience and would be able to get the project working/looking pretty. AutoWear is entirely his and I have just helped him start a small part of the project. Maybe you can contact him directly and try to get in the test group. Good luck!
[Xposed Framework Modules] iHelp101:
I see a new Google Search update was recently released. I am looking into it and seeing if any of the hooks having been changed.

Edit: Looks like Google decided to change some hooks around. Give me a few minutes.

Edit2: Missing a few hooks. Finding last few and then testing.

Edit3: I think I found all the hooks. Testing to make sure.

Edit4: Looks likes Google broke some of the code too. Trying to find a workaround.

Hooks so far:

SearchControllerClassHook = "bpn"; -> cws

MyVoiceSearchControllerListenerClassHook = "bpy"; -> cwx

SearchResultFetcherClassHook = "cby"; -> dap

SearchOverlayImplClassHook = "cuc"; -> erb

mContextHook = "mContext";

mVoiceSearchServicesHook = "mVoiceSearchServices";

ttsManagerHook = "aCT"; -> aRm

ttsManagerMethodHook = "a";

SearchResultFetcherQueryHook = "x"; -> c

searchQueryTextHook = "bqk"; -> cxr

mCacheHook = "mCache";

mClockHook = "mClock";

mCacheResultHook = "a";

MyVoiceSearchControllerListenerMethodHook = "a";

CharSequenceClassHook = "hmu"; -> isi

CharSequenceClassHook2 = "cbs"; -> daj
[Xposed Framework Modules] iHelp101:
Google Search 4.1.21 Update!

Google has changed how hooking into text works. So I had to remove the feature that allowed typed commands to be hooked. Voice is however still being recognized. This should mean that Android Wear can still be hooked into. I would appreciate if someone could confirm this by testing the new update.
[Xposed Framework Modules] beauwilliams:
It working perfectly for me
[Xposed Framework Modules] iHelp101:
Just a heads up for everyone. AutoWear is now in beta, which means anyone can use it now. You just need to join the beta group and you can test the app. I have a link below to the promo video João made. In the description of the video it has the links to join the beta group.

https://www.youtube.com/watch?v=amEMmucbJ_w
[Xposed Framework Modules] iHelp101:
Checking new Google Search 4.1.26 for changes.

Edit: Nothing changed.
[Xposed Framework Modules] TheCrowing:
I got the new Google Search Update and it broke my AutoVoice on my phone and my Moto 360. Not sure what I'm doing differently than you. I reverted back to the previous version for now.
[Xposed Framework Modules] iHelp101:
Are you using this Xposed Module or just AutoVoice/AutoWear? Also what was the Google Search update number? Last did you download the recent update to the Xposed Module if you are using it?

Edit: I see that the Play Store is reported the Google Search app was updated on January 12th. No APK sites have an new update that I can find. I am not sure if a new update (Past 4.1.24) was released or not.
[Xposed Framework Modules] TheCrowing:
I'm using the Xposed Module, I couldn't get the Moto 360 watch working unless I used that. The Google Search update version I have is 4.1.241672412.arm. My Xposed Framework Installer shows it is version 2.6.1 which is the most recent one. The Framework itself shows app_process of 58 and XposedBridge.jar of 54. The Google Search API module that I have installed is version 1.4 and that appears to be the most current one as I was unable to find anything newer.
[Xposed Framework Modules] iHelp101:
A page back version 1.5 of the Google Search API was posted. It is 4 posts before your original post. After you install that everything should be working.
[Xposed Framework Modules] TheCrowing:
Well now I feel really stupid... I didn't realize that was a newer version of the Google Search API. Thank you so much for pointing it out! It works like a charm now!
[Xposed Framework Modules] flash3d:
Lollipop

First let me say that this Xposed plugin is (for me) still the best way to control AutoVoice/Tasker.

Spend some hours to get AutoWear and GPE Lollipop working on my S4.

Under GPE KitKat I had everything working with the Api and AutoWear so I could already practice with shaking my watch.

With lollipop i could only get AutoWear work properly when selecting the English language as primary in Google now, as I have all my commands in Dutch this was not an option for me. When selecting the Dutch language as primary and English as second I was getting the error: "Can't reach Google at the moment". Sometimes it would work (1 out of 10).

Just wanted to share my experience, hopefully this API stays working and updated till they ironed out the bugs in Lollipop.

Ideally somebody will make it work in Lollipop like it does with KitKat/Exposed.
[Xposed Framework Modules] iHelp101:
Thanks for the feedback and information. I am happy that you like the work put into this Xposed module/plugin. I never thought of that issue with foreign languages. A small tip for fixing the error "Can't reach Google at the moment" is to download the offline language packs for both English and Dutch. I know this helped fix that dialog when I used the English pack (Primary). Hopefully this helps fix your issue. I will update the API as long as it is possible. Happy tasking!
[Xposed Framework Modules] flash3d:
That's a good tip, didn't try that. Maybe I will give it a shot in the weekend. Have a nandroid from the lollipop installation but still prefer the kitkat "ok Google" method.

Wish somebody could make it work that way on lollipop. I had the impression that the ok Google way is also a lot more successful with recognizing my Dutch compared to autowear.
[Xposed Framework Modules] iHelp101:
AutoWear uses the same voice recognition as Google Now. Hopefully this fixes the issue if you decide Lollipop is an OS you like. If it doesn't I recommend contacting João (AutoWear developer). I simply gave him some base code for AutoWear and he expanded on it and got everything working how he wants it.
[Xposed Framework Modules] Mudvayne622:
Is it safe to take the newest Google Search update? Not gonna break anything?
[Xposed Framework Modules] flash3d:
It's safe, just install the latest api from a few posts back.
[Xposed Framework Modules] lorddunlow:
Well, you will apparently lose the ability of this module capturing text searches. Voice search still working as before.
[Xposed Framework Modules] flash3d:
Just for my understanding: Is there not a way to get this API worked without Xposed on Lollipop? Or in other words if we forget Xposed, is there a way to make this API (or something new) work with Lollipop and Google Search.

Thanks.