[Q] Universal hotword detection - Nexus 9 Q&A, Help & Troubleshooting

Has anyone else gotten this to work? I enabled the options in Google now and trained my voice but testing repeatedly, Google Now only recognized the hotword when I have Google now physically pulled up. Not even working when the screen is on and not in Google Now Launcher.

This works for me... I was curious if there was a way to enable wake on hot word? Anyone know? Silly when I see people on the moto x , but I still want it...

Hot word detection isn't working from the lockscreen or with the screen off for me, even though i have the options enabled. Is this a bug, or am i missing something?

So I'm not the only one with this problem...
For folks that don't know, you can enable Moto X- like hotword detection when the screen is off. You enable this through the Google Now settings under the Voice tab, selecting the "OK Google Detection" option. Enable all three options in the next screen to (try to) enable hotword detection at all times.
Unfortunately, it isn't very reliable for me. Hotword detection works fine in the launcher or in the Google Now app. But it often doesn't work the rest of the time.

Definitely you're not alone Same problem here. OKGoogle only works when I'm in the launcher.

Same here. I am using it with English US as primary and German as secondary language.
No results until i am on the Google Now Launcher....hopfully just a little buck in our version of Android L.

I have the same issue. Please everybody report this on the feedback within google now .
Voice detection is not working correctly on the nexus 9

THE_KINGDOM said:
I have the same issue. Please everybody report this on the feedback within google now .
Voice detection is not working correctly on the nexus 9
Click to expand...
Click to collapse
5.0.1 has fixed this issue for me.

Issue still exists here on 5.0.1

Related

What are you using for voice dial?

Hello,
I'm curious what software/app you use for dialing with your S4.
Most of the time my phone sits in my pocket and I use BT for voice dial. I've found the current voice dial seems to be a lot more tedious than my S3. Confirming who I want to call and half the time on confirm - e.g. call Mary Smith at work - there are two numbers what number would you like to call - I press the work number and then it says do you want to call Mary Smith at work and I will say YES and then it goes I can't find yep in your phone book and I have to start all over.
Is there a way to switch off confirmations? Is there a way to switch which voice dialer (I tried VLINGO but it no longer supports BT dial).
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I use the headset that came with the S4. Long press on the bottom button and make my calls when driving. I haven't hooked up my S9 to it yet but then again that one is a stereo headphone headset so it goes in both ears.
DarkMenace said:
I use the headset that came with the S4. Long press on the bottom button and make my calls when driving. I haven't hooked up my S9 to it yet but then again that one is a stereo headphone headset so it goes in both ears.
Click to expand...
Click to collapse
Thanks. I should have been more specific. I'm curious about the voice dial software people are using and if there are any options within the S4.
boe said:
Thanks. I should have been more specific. I'm curious about the voice dial software people are using and if there are any options within the S4.
Click to expand...
Click to collapse
I was having a similar problem. Except I wanted to change the default application that was launched when I hit my bluetooth function button in my car. It was launching SVoice by default. SVoice really sucks on my phone when it is connected to my car's bluetooth. Not so with my wife's S4. Not sure why.
I wanted to use Google Search- works flawlessly for making calls, navigation and finding points of interest, weather... but cannot do as much as SVoice or a few of the other apps available. Anyway- a couple weeks I did a series of searches and found the solution on these forums but can't find the the thread anymore...
So in case you are wondering how to change what is launched: you have to go into application manager (under settings) and disable svoice. Now, when you launch one of these apps it will ask you to pick a new default. If you would like to launch Google Search you have to download the app Bluetooth Launch which lets you assign any app to launch when bluetooth function button is pushed. You choose com.google.android.googlequicksearchbox.VoiceSearchActivity in the bluetooth launch app.
https://play.google.com/store/apps/details?id=com.kin.bluetooth_launch&hl=en
I tried a lot of other apps in the app store like vlingo, assistant, skyvi, maluuba, dragon voice, etc... a lot of them had problems with voice recognition, but had a lot more functionality. Oh and vlingo still supports bluetooth... The one that seemed to have the best voice recognition was assistant.... which i may eventually switch to.
fun4stuff said:
I was having a similar problem. Except I wanted to change the default application that was launched when I hit my bluetooth function button in my car. It was launching SVoice by default. SVoice really sucks on my phone when it is connected to my car's bluetooth. Not so with my wife's S4. Not sure why.
I wanted to use Google Search- works flawlessly for making calls, navigation and finding points of interest, weather... but cannot do as much as SVoice or a few of the other apps available. Anyway- a couple weeks I did a series of searches and found the solution on these forums but can't find the the thread anymore...
So in case you are wondering how to change what is launched: you have to go into application manager (under settings) and disable svoice. Now, when you launch one of these apps it will ask you to pick a new default. If you would like to launch Google Search you have to download the app Bluetooth Launch which lets you assign any app to launch when bluetooth function button is pushed. You choose com.google.android.googlequicksearchbox.VoiceSearchActivity in the bluetooth launch app.
https://play.google.com/store/apps/details?id=com.kin.bluetooth_launch&hl=en
I tried a lot of other apps in the app store like vlingo, assistant, skyvi, maluuba, dragon voice, etc... a lot of them had problems with voice recognition, but had a lot more functionality. Oh and vlingo still supports bluetooth... The one that seemed to have the best voice recognition was assistant.... which i may eventually switch to.
Click to expand...
Click to collapse
So I finally tried the latest dragon (I think they took over vlingo and their newer version supports BT). It BLOWS the doors off Svoice and google voice dial. I don't need to play music or anything else via BT command so I don't know if it is good or not for that sort of stuff but for calling my contacts from my exchange account, it is nearly flawless. I've only tested for a day but so far so good. If it ends up having issues, I'll be sure to post back.
fun4stuff said:
I wanted to change the default application that was launched when I hit my bluetooth function button in my car....you have to go into application manager (under settings) and disable svoice...If you would like to launch Google Search you have to download the app Bluetooth Launch ...choose com.google.android.googlequicksearchbox.VoiceSearchActivity
Click to expand...
Click to collapse
Thanks fun4stuff!! That's exactly what I was looking for!

[MOD][XPOSED][4.1+] GoogleOfflineVoice - Force offline voice recognition/typing

Introduction
The voice recognition API does not allow apps to choose whether they want to use offline voice recognition or not. There's no setting for the user either. Instead, if there's an internet connection, it'll always use the online services.
This module allows you to force offline voice recognition/typing. This is useful if you're using a slow connection, if you're connected to a local network (without internet access,) etc.
What does this module do?
This module can force offline voice recognition for apps that use Google Voice. It'll work if the app uses one of the following:
Voice typing (used by keyboards, e.g. SwiftKey)
Voice recognition (for apps that use RecognizerIntent such as utter!)
It does so by setting a variable that indicates whether a network connection is available or not to false.
Voice commands inside the Google Search app aren't affected. Note that if offline voice recognition doesn't work for you in the first place, this module won't fix that.
Requirements:
Xposed Framework.
Broadcasts:
You can toggle some settings from e.g. Tasker using broadcasts. Just use these action names:
com.germainz.googleofflinevoice.enable - Enables the module.
com.germainz.googleofflinevoice.disable - Disables the module.
com.germainz.googleofflinevoice.enable_voice_ime - Enables the module for voice typing.
com.germainz.googleofflinevoice.disable_voice_ime - Disables the module for voice typing.
Example from the shell:
Code:
am broadcast -a "com.germainz.googleofflinevoice.disable"
Source code:
https://github.com/GermainZ/GoogleOfflineVoice
Download:
http://repo.xposed.info/module/com.germainz.googleofflinevoice
Changelog:
Code:
[B]1.2.1:[/B] The widget now uses images to indicate the module's state. This should fix text getting cut off on some devices.
[B]1.2:[/B] Fix for the latest Google Search. Revamped blacklist. Added a simple widget to toggle module status (useful to quickly enable/disable GoogleOfflineVoice from e.g. your home screen).
[B]1.1:[/B]
The voice typing setting wasn't working correctly (because of a typo - offline voice typing was never forced.) Also, there was another typo in strings.xml, as a reboot is actually *not* required for the settings to apply.
[B]1.0:[/B] Initial release.
Thanks:
rovo89 for the Xposed Framework.
I need just the opposite! Want to force / route to online recognition. Armv6.possibilities here?
Sent from my LG-P500 using xda app-developers app
Dovidhalevi said:
I need just the opposite! Want to force / route to online recognition. Armv6.possibilities here?
Click to expand...
Click to collapse
I think the title and description are extremely clear.
Anyway, check this.
EDIT: actually, I don't understand what you want. Regardless, it doesn't seem related to what this mod does so no.
I don't know if I understand this clearly - this will able me to use Google Now voice recognition and Swiftkey voice typing when there's no data connection? But I'll still be able to use it when data is on?
Andrev01 said:
I don't know if I understand this clearly - this will able me to use Google Now voice recognition and Swiftkey voice typing when there's no data connection? But I'll still be able to use it when data is on?
Click to expand...
Click to collapse
No. On Jelly Bean and higher, you can already use offline voice recognition/typing. That only happens when you're not connected at all, though. You can't force it if you're using a slow connection or if you're connected to a WiFi that's local (no internet access.) This module allows you to do that. I personally use it for SwiftKey and utter! because I find online recognition is too slow - at least with my internet connection.
Good app, was looking for something like this since long.
sent from public phone using coins.
Tried it out anyway. Off-line recognition CAN work on Armv6--had it happen once, just once. Do not know how I got there but the armv7 code stands in the way. So maybe this module could bypass it.
I actually have two Google choices for recognition, one for Google Search (offline) and one for older Voice Search (online). Vlingo also exposes its engine as another working choice. I wish Nuance (they own it now) would expose there Dragon engine. Unfortunately, most apps no longer respect this choice. In fact, only Jeannie works now with the online recognition choice. The voice assistant does not work over KitKat Google Search and launcher.
So I enabled this module. Really did not change much. Jeannie still worked, seemed quicker but very subjective--I assume was still going online. Google Search did not FC but did not accept voice. Next browser's voice input pretended to work, as before. No results. Voice typing also pretended, no results. Dragon's (using Swype) works very well (online).
BTW, the linked kludge is for dictation, using an ICS modded Google Search to somehow retrieve a language file. Did not work for me but I have the file, manually symlinked to its presumably proper place. The poster does not use Google Search, only dictation.
Dovidhalevi said:
So I enabled this module. Really did not change much. Jeannie still worked, seemed quicker but very subjective--I assume was still going online. Google Search did not FC but did not accept voice. Next browser's voice input pretended to work, as before. No results. Voice typing also pretended, no results. Dragon's (using Swype) works very well (online).
BTW, the linked kludge is for dictation, using an ICS modded Google Search to somehow retrieve a language file. Did not work for me but I have the file, manually symlinked to its presumably proper place. The poster does not use Google Search, only dictation.
Click to expand...
Click to collapse
This module can force offline voice recognition, by changing the following, and only for apps that use Google Voice:
Voice typing (used by keyboards, e.g. SwiftKey)
Voice recognition (for apps that use RecognizerIntent such as utter!)
You're unlikely to notice a big difference unless you're using a slow connection or are connected to a WiFi network without an internet connection.
Voice commands through Google Search aren't affected, so your "did not accept voice" isn't related to this module. As I've said, this only affects Google Voice - Dragon and other engines will still behave as before.
If offline voice recognition doesn't work for you in the first place, this module won't fix that.
Can someone coment if this would have significant savings on bandwidth, for people who are trying to keep it under a couple hundred meg cap? For a user who uses heavy dictation.
Update:
Code:
[B]1.1:[/B] The voice typing setting wasn't working correctly (because of a typo - offline voice typing was never forced.)
Also, there was another typo in strings.xml, as a reboot is actually *not* required for the settings to apply.
Sorry
AaronCompNetSys said:
Can someone coment if this would have significant savings on bandwidth, for people who are trying to keep it under a couple hundred meg cap? For a user who uses heavy dictation.
Click to expand...
Click to collapse
It depends. Offline voice recognition isn't great for dictation unless you have a perfect accent and there's no background noise at all. You'll get unusable results otherwise.
Assuming it works perfectly, though, you'll save quite a lot, yes. Of course, it depends on how much you use it. But as I've said, offline dictation probably won't give you acceptable results, so you'll have to Try It And See™ and decide for yourself (also note that it wasn't working properly till this update.)
can't install, says apk not valid, nor from repository, apk problem
holymoz said:
can't install, says apk not valid, nor from repository, apk problem
Click to expand...
Click to collapse
OS version?
GermainZ said:
OS version?
Click to expand...
Click to collapse
ics 4.0.4
holymoz said:
ics 4.0.4
Click to expand...
Click to collapse
Read the thread's title.
GermainZ said:
Read the thread's title.
Click to expand...
Click to collapse
ops, thanks
Hello, does it work with TouchPal XKeyboard? Because I can't use voice recognition. Using KitKat
Enviado desde mi LG-E610 mediante Tapatalk
chrisdlc119 said:
Hello, does it work with TouchPal XKeyboard? Because I can't use voice recognition. Using KitKat
Click to expand...
Click to collapse
Maybe, if it uses Google voice recognition. Try It And See™.
PS. I'm not sure what you mean be "I can't use voice recognition" - if it's failing even with an Internet connection them your problem is elsewhere.
Well @GermainZ, because I was using Google Keyboard too and nothing happens. To be sure, voice recognition works fine with an internet connection.
Enviado desde mi LG-E610 mediante Tapatalk
chrisdlc119 said:
Well @GermainZ, because I was using Google Keyboard too and nothing happens. To be sure, voice recognition works fine with an internet connection.
Enviado desde mi LG-E610 mediante Tapatalk
Click to expand...
Click to collapse
Voice typing != voice recognition. Google Keyboard should use voice typing, so make sure that setting is enabled. Read the OP for more info.
GermainZ said:
Voice typing != voice recognition. Google Keyboard should use voice typing, so make sure that setting is enabled. Read the OP for more info.
Click to expand...
Click to collapse
Ok, I hope it works. Thanks, nothing's perfect, I know.
Enviado desde mi LG-E610 mediante Tapatalk

Remove Ok google(Not just the text)

I'm not a fan of google feeling the need to listen to everything I say. I did search for this, but all I'm coming up with is people wanting to disable the "Ok google" text on the screen. I'd like to disable to feature all together, but it doesn't seem there is an option anywhere. Am I missing something or do you need a custom rom to get rid of this crap? Thanks guys!
djscrew said:
I'm not a fan of google feeling the need to listen to everything I say. I did search for this, but all I'm coming up with is people wanting to disable the "Ok google" text on the screen. I'd like to disable to feature all together, but it doesn't seem there is an option anywhere. Am I missing something or do you need a custom rom to get rid of this crap? Thanks guys!
Click to expand...
Click to collapse
I do not know if there is anyone who would have done this... the "OK Google" is the core part of android wear...... If you do not like that feature, you may be better off with a different wearable.
I am not trying to be rude, just can not understand why you need to remove almost all functionality of your watch.
Milimbar said:
I do not know if there is anyone who would have done this... the "OK Google" is the core part of android wear...... If you do not like that feature, you may be better off with a different wearable.
I am not trying to be rude, just can not understand why you need to remove almost all functionality of your watch.
Click to expand...
Click to collapse
Actually he made an interesting question, indeed. The voice recognition of the "OK GOOGLE" hotword isn't fully used by everyone (as with on phone) so disabling that should spare some battery juice.
Milimbar said:
I do not know if there is anyone who would have done this... the "OK Google" is the core part of android wear...... If you do not like that feature, you may be better off with a different wearable.
I am not trying to be rude, just can not understand why you need to remove almost all functionality of your watch.
Click to expand...
Click to collapse
I can understand where the feauture may be useful, but I myself don't feel it's necessary to have google listening to me at all times. I wouldn't quite say that is "almost all the functionality" of the watch. Why can't I activate the menu an then begin speaking rather than it just listening at all times?
lparcshinoda said:
Actually he made an interesting question, indeed. The voice recognition of the "OK GOOGLE" hotword isn't fully used by everyone (as with on phone) so disabling that should spare some battery juice.
Click to expand...
Click to collapse
That's a good point too. I'm sure that "feature" is draining my battery.
I think the OP has a valid point. Personally I don't care if Google hears me. However, I would be okay if I could just tap the screen to give a voice command instead of saying okay Google. Everyone looks at me funny when I say that part. Probably save a little time too.
Also, I wish I could just tap on the watch to have it input voice to text on my phone when I'm in a text field. I like to use Swype, but hate there voice to text option when I want to use it.
I can see how having the option to turn off always listening would be good for some people, i thought he wanted to remove ALL of the google now functions.
Maybe someone will come up with a mod for it soon.
I'm fed up of this "OK GOOGLE" Logo everytime, Hope they will give us an option to remove the word in next update.!
riteshgpt60 said:
I'm fed up of this "OK GOOGLE" Logo everytime, Hope they will give us an option to remove the word in next update.!
Click to expand...
Click to collapse
just use it a couple of times, then the text will no longer be shown...so, just say "ok google" to activate the search (i think about 5 times necessary, correct me, if i am wrong), then you will no longer see the text when waking up your watch...
I'm interested in partially deactivating the "ok google" feature too, as I my main language is french and ok google works only about 20% of the time for me
bagster said:
I'm interested in partially deactivating the "ok google" feature too, as I my main language is french and ok google works only about 20% of the time for me
Click to expand...
Click to collapse
My main language is also French and the detection is working almost flawlessly
no solution yet?!
worst thing with the Hotword detection is, that it's too often wrong with the detection and starts recording .. it's like you have a bug on your wrist
for me, it records about 10 times a day without me saying "ok google"...
but check it yourself: history.google(.com)/history/audio (remove the () , i cant post links because of new member)
worst function ever. so anybody knows how to delete this ****ed up function?!
These devices were made with the hotword detection specifically in mind, I believe that the battery use should be negligible. I personally haven't noticed any battery problems coming from the Android Wear app or the Google app (on watch, through the battery statistics.) most of my battery problems were from watchfaces still using the 4.4w APIs and badly coded applications.
That said, because they were made specifically with hotword detection and Google Now in mind, it cannot be disabled without someone possibly making a custom ROM to turn it off, however no one has made a true custom ROM for wear yet (I'm not even sure they can honestly.)
What I ended up doing is going into the Google account options on the phone. Under search - voice there is an option for "OK Google detection" doing this seemed to completely disable it. I don't understand how people are comfortable having an open mic with them at all times. Just because you "have nothing to hide" doesn't mean something should always be listening.
djscrew said:
What I ended up doing is going into the Google account options on the phone. Under search - voice there is an option for "OK Google detection" doing this seemed to completely disable it. I don't understand how people are comfortable having an open mic with them at all times. Just because you "have nothing to hide" doesn't mean something should always be listening.
Click to expand...
Click to collapse
It may always be listening, but it isn't always recording. The Ok, Google hotword detection only records the first second before and after you say Ok, Google. It's not always sending things over to Google. Just because you have things to hide, doesn't mean you should be paranoid about it
The google services have indeed plagued many phones for their background services, alarms, and receivers.
What I cannot understand is how the 'Ok Google' still works even when I have switched my watch to Airplane Mode.
Not everyone buys an Android Wear to enjoy the google services. Some, including me, like only the Wear Faces. One watch, many wear faces, saves the money to 'collect' many different watches just for the sake of keeping up a lifestyle.

OK GOOGLE, why won't you work from lock screen!

Hi
I am trying to get google to work by using the OK Google voice recognition. it works well when phone is unlocked but it wont work when phone is on standby. I have tried following instructions, enabled what needs to be enabled but its not working. The option to enable the action on "any screen" doesn't work?
the S6E doesn't have as many options as the nexus series and I dont have these options on my BTU phone...
mackendw said:
there is an option in Google Now -> Settings -> Voice -> OK google detection ....a check box exists here stating:
When Locked
Allow "OK Google" to start a voice search or action from a secure lock screen
Click to expand...
Click to collapse
are you using this?
Thanks
this sheds some light for those who have the problem too..
https://productforums.google.com/forum/#!topic/websearch/xGiV6D4PMS8/discussion
if you download the google launcher, OK Google works when screen is on but still in a locked mode. closest thing to standby voice recognition I have found
Hi everyone,
We sincerely thank you for your patience again as this was sorted out. The team was working on smoothing out some compatibility issues, and this missing feature was an unintended result of it. However, as mentioned in previous messages, the engineering team was made aware of this high-priority issue when users initially reported it and they have been diligently working on providing a solution since.
Now, we are happy to share that the "From any screen" function has been fixed for S6 and S6 Edge devices on the Google Search App (GSA), and the fix is actively rolling out to users. To ensure that this feature becomes available to you soon, please ensure that you are running the most up-to-date version of GSA (4.5+). Please note that “Ok Google” from any screen will be available, however remaining compatibility issues mean that turning on the feature will limit the availability of S-voice hotwording to only when the screen is off. Users who prefer to avoid this can turn off “Ok Google” from any screen.
Thank you again for your feedback and patience as we got to the bottom of this!
So it doesn't work when screen is off. only when screen is on (in or out of lock mode)

Turning HP Touchpad into an sort-of Amazon Echo Show

Hello all,
I love my Touchpad. It got me through College, especially with its completely underrated out-of-the-box office suite. However now it just functions as my Alarm Clock on my bedside table on a Touchstone dock.
When the Amazon Echo Show came out, I think I can saw we all laughed a little. After all, who would would want a tablet with at-a-glance information that they can't carry around with them. Then I realized, that's *exactly* how I use my Touchpad in Exhibition mode. So that got me thinking: how could I transform the hardware I already have and love into a device similar to the Echo Show.
Now, in my mind, there are three ways to do this:
a) Keep webOS and install the somewhat buggy ACL made by Phoenix Communications then install the Alexa handsfree app from the new Fire10 tablet (if I can find the APK). Basing myself on this article: https://techcrunch.com/2017/09/19/a...s-as-a-cheap-echo-show-with-hands-free-alexa/
b) Install Android 6.0+, and make the Google Assistant my Alexa stand-in. I would therefore need to find a way to port-over webOS's Exhibition Mode. Also perhaps the Prelude fonts, as I find Roboto completely unappealing.
c) Install ANY version of Android, and use the same Alexa handsfree app from a), setting it to be constantly on (no screen lock).
Given the Touchpad's aging hardware, any Android ROM would need to be fast, minimal and barebones as I don't intend to use this for much else. It does, however, need to be stable enough to not crash every time I say "Ok Google" or "Alexa".
Any tips on how I should proceed?
Thanks in advance!
Sheik
Sheikboy said:
Hello all,
I love my Touchpad. It got me through College, especially with its completely underrated out-of-the-box office suite. However now it just functions as my Alarm Clock on my bedside table on a Touchstone dock.
When the Amazon Echo Show came out, I think I can saw we all laughed a little. After all, who would would want a tablet with at-a-glance information that they can't carry around with them. Then I realized, that's *exactly* how I use my Touchpad in Exhibition mode. So that got me thinking: how could I transform the hardware I already have and love into a device similar to the Echo Show.
Now, in my mind, there are three ways to do this:
a) Keep webOS and install the somewhat buggy ACL made by Phoenix Communications then install the Alexa handsfree app from the new Fire10 tablet (if I can find the APK). Basing myself on this article: https://techcrunch.com/2017/09/19/a...s-as-a-cheap-echo-show-with-hands-free-alexa/
b) Install Android 6.0+, and make the Google Assistant my Alexa stand-in. I would therefore need to find a way to port-over webOS's Exhibition Mode. Also perhaps the Prelude fonts, as I find Roboto completely unappealing.
c) Install ANY version of Android, and use the same Alexa handsfree app from a), setting it to be constantly on (no screen lock).
Given the Touchpad's aging hardware, any Android ROM would need to be fast, minimal and barebones as I don't intend to use this for much else. It does, however, need to be stable enough to not crash every time I say "Ok Google" or "Alexa".
Any tips on how I should proceed?
Thanks in advance!
Sheik
Click to expand...
Click to collapse
Good idea! I don't use my TouchPad very much anymore away from it being my alarm clock on the Touchstone dock.
I'd definitely try to upgrade it to an Alexa enable tablet if possible.
Will follow this thread with interest!
Sent from my Nexus 5 using Tapatalk
Quick Update:
Option a) does not work. As I suspected, the ACL simply doesn't work well enough to run the Google Assistant and listen for the Ok, Google hotword. I didn't run the Alexa app, but I suspect I'll run into similar issues with it.
This leaves me with options b) and c). I've been installing all sorts of different ROMs for the past day and I keep running into a recurring issue: the WiFi on my tablet doesn't seem to be working. It works fine in webOS, but in every single Android version I've run it gets stuck on "turning WiFi on".
I suspect I have an issue with the ath6kl driver, but I can't find a replacement driver updated for anything past CM9. Can anyone help me? I seem to be having the exact same issue OP is having in this thread: https://forum.xda-developers.com/hp-touchpad/help/wifi-wont-clean-flash-t3612062
Sheikboy said:
Quick Update:
Option a) does not work. As I suspected, the ACL simply doesn't work well enough to run the Google Assistant and listen for the Ok, Google hotword. I didn't run the Alexa app, but I suspect I'll run into similar issues with it.
This leaves me with options b) and c). I've been installing all sorts of different ROMs for the past day and I keep running into a recurring issue: the WiFi on my tablet doesn't seem to be working. It works fine in webOS, but in every single Android version I've run it gets stuck on "turning WiFi on".
I suspect I have an issue with the ath6kl driver, but I can't find a replacement driver updated for anything past CM9. Can anyone help me? I seem to be having the exact same issue OP is having in this thread: https://forum.xda-developers.com/hp-touchpad/help/wifi-wont-clean-flash-t3612062
Click to expand...
Click to collapse
Use the Evervolv ROM.
shumash said:
Use the Evervolv ROM.
Click to expand...
Click to collapse
That's what I'm currently running. I also changed the Kernel to see if that's what was causing the issue but it isn't.
I know for a fact it's not the hardware, because webOS's wifi works perfectly.
Sheikboy said:
That's what I'm currently running. I also changed the Kernel to see if that's what was causing the issue but it isn't.
I know for a fact it's not the hardware, because webOS's wifi works perfectly.
Click to expand...
Click to collapse
All I can tell you is that wifi works perfectly for me (and most others based on the devs-base forum). I have no problem with Google Assistant and "OK, Google" voice recognition.
shumash said:
All I can tell you is that wifi works perfectly for me (and most others based on the devs-base forum). I have no problem with Google Assistant and "OK, Google" voice recognition.
Click to expand...
Click to collapse
Hey !
Thanks to kernel and settings found here, my TouchPad is now usable.
I plan to use it as a control screen for my home automation system, and a echo show / google home like.
You told that the Google Assistant was active, and usable on your TouchPad. Could you please explain me how did you activate it ?
I tried some tricks found on xda dev, but i'm stuck with google now...
Thank you !
thedeathspirit said:
Hey !
Thanks to kernel and settings found here, my TouchPad is now usable.
I plan to use it as a control screen for my home automation system, and a echo show / google home like.
You told that the Google Assistant was active, and usable on your TouchPad. Could you please explain me how did you activate it ?
I tried some tricks found on xda dev, but i'm stuck with google now...
Thank you !
Click to expand...
Click to collapse
Get Assistant - Root works
I still haven't been able to fix the WiFi on my Touchpad. It works perfectly in webOS, but it just remains stuck on "Turning WiFi On" on every single Android ROM iIve tried. I'm not quite sure what to do at this point
shumash said:
Get Assistant - Root works
Click to expand...
Click to collapse
Thank you, I'll try.

Categories

Resources