Is there a way to get this to work on the pixel 3a? The tasker action speakerphone->on seems to have no effect on the 3a. I have also tried adding a delay first but it didn't make a difference.
The assistant is able to turn on the speaker when you say 'call [someone] with speakerphone.'
I've done some searching as this question has been asked over the years but haven't found anything that works yet on 3a.
It would be very useful to be able to do things like turn on the speaker automatically if the phone isn't at your ear.
Thanks!
Literally the first thing that comes up. It's from 2014, so it might be a little outdated, but I bet it still works.
But that is exactly the guide I am using! The function to turn on the speakerphone does not work on the pixel 3a. Did you try it or only run a search
yaconsult said:
But that is exactly the guide I am using! The function to turn on the speakerphone does not work on the pixel 3a. Did you try it or only run a search
Click to expand...
Click to collapse
Sorry, I misunderstood your inquiry and I had only run the search. I did just try it however and run into the same issue as you are finding.
sic0048 said:
Sorry, I misunderstood your inquiry and I had only run the search. I did just try it however and run into the same issue as you are finding.
Click to expand...
Click to collapse
Thank you for confirming that the posted method doesn't work on the pixel 3a! I tried adding some delays but it had no effect. It must be due to changes made in android since that post was made.
I have made a post about it to the tasker support google group and will post any useful info I get here.
I am rooted with Magisk and Tasker has root permission. I'm on the play store version of Tasker and have the December android update.
I will say it does work sometimes. It certainly isn't consistent, which is probably worse then not working at all.
Related
I thought the OnePlus was going to have touchless voice commands. I cant find it anywhere.
I saw in a video "hi snapdragon" but doesn't seem to work
it was removed in the last update.
The Jack of Clubs said:
it was removed in the last update.
Click to expand...
Click to collapse
Why was it removed? Is the feature coming back?
I know you can use 'OK Google' but there are problems with the mic volume, which can be fixed by editing a file, but it isn't a perfect fix. This has been patched in the latest update though, which should be pushed out shortly.
Also, OK Google doesn't seem to be listening everywhere even if it has been set to. I'm hoping they fix this as well.
it didnt work well and they are working on replacing the "hey snapdragon" with "ok oneplus".
Qualcomm was not satisfied with the quality of the pre-recordings that oneplus sent to them.
7ewis said:
Why was it removed? Is the feature coming back?
I know you can use 'OK Google' but there are problems with the mic volume, which can be fixed by editing a file, but it isn't a perfect fix. This has been patched in the latest update though, which should be pushed out shortly.
Also, OK Google doesn't seem to be listening everywhere even if it has been set to. I'm hoping they fix this as well.
Click to expand...
Click to collapse
If you go in to the Google now settings and change the default languae to US you should then be able to activate 'Ok Google' from any screen includong the lock screen and while the device is in standby
I tried to activate this but does not seem to work from the lock screen for the oneplus one. I have 44S update I think but would really love to see this functionality coming back. I was quite impressed with my moto x primarily from this perspective and am looking forward to having this on my oneplusone device.
Any idea when it might come back?
TIA
Anyone else having inconsistent results with saying "OK Google" while the screen is off?
It seems to work fine when actively using the phone, but if I hit the power button to turn off the screen then it may (or may not) turn the screen on with the Assistant after saying "OK Google" (nothing happens).
I tried turning on fingerprint/pin security, but this will still sometimes not respond to the command. Additionally, it will also still sometimes ask me for a pin even though I have "Trusted Voice" enabled.
Not sure if it's a hardware issue or software related (again, everything works perfectly if the phone screen is already on and in use).
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
kinetic758 said:
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
Click to expand...
Click to collapse
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
ryken229 said:
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Click to expand...
Click to collapse
xShadoWxDrifTx said:
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
Click to expand...
Click to collapse
I was not connected to wifi but the signal seemed fine. I'll keep an eye on it next time.
nednednerb said:
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
kinetic758 said:
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
Click to expand...
Click to collapse
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
nednednerb said:
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
kinetic758 said:
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
Click to expand...
Click to collapse
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
nednednerb said:
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
What is scary for me, is any time there is a Pixel commercial on TV and the guy says "OK Google", my phone wakes up. So quite the opposite from the OP experience. Actually scary from a security standpoint. The old Motos used to allow limited functionality via voice but not full unlock (smart idea). There should be a way to remotely disable voice detection if you lose your phone.
kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
dispatch said:
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
Click to expand...
Click to collapse
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Sent from my LG-D801 using Tapatalk
kinetic758 said:
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
Click to expand...
Click to collapse
I really don't think it's the hardware, but you never know. I don't yet have a large enough sample size to say if 1 in 10 is accurate in the long run or if it is truly closer to 1 in 100 that it fails to wake. I always assume we're beta testers for Google anyway so I have come to expect things like this.
aquatarkus said:
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Click to expand...
Click to collapse
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
dispatch said:
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
Click to expand...
Click to collapse
This. I've embraced (at least for now) the fact that Google is collecting information about me. I've bought into it (also purchased a Google Home) with the hope that this will make my life easier (if slightly). A double-edged sword, for sure.
dispatch said:
However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do.
Click to expand...
Click to collapse
I figure I'm smart enough not to need Google to run my life for me. I will first root the Pixel and remove the stuff I don't want. When a suitable version of CyanogenMod becomes available, I'll flash that into it, as it provides additional security/privacy controls.
Anyway, I hadn't meant to highjack this thread....
Sent from my LG-D801 using Tapatalk
kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
Also try training the voice by saying Ok Google at 3 slightly different volumes and with varied pace. Do say it clearly each time. I found voice recognition doesn't work as well if I train it with a forced or monotone rhythm. Cos real voice is more fluid and not always the same.
Good luck
Sent from my sailfish using XDA Labs
Mine works every time.
This was never the case on the Nexus 6P.
The only time the Pixel DIDN'T wake up is when it was on low battery and save mode got enabled. I believe this disables the always listening feature of this app.
Sent from my Pixel using XDA-Developers mobile app
Has anybody had success with waking/unlocking your phone with the "Ok Google" voice command? I enjoy using it but I don't want to have to unlock my phone to use the voice assistant every time, particularly when it's for simple questions (I know, first world problems). I enabled Trusted Voice but that doesn't seem to work when my phone screen turns off. Any help would be appreciated.
Same here. I also tried to do that. Ultimately i came up with nothing.
same here man.
I can't recall the source, but I'd read somewhere it only wakes up to the Dear Honor voice command activated in settings. Seemed to work when I tested it. Also found an automate module that senses the honor voice app open, closes it and loads the Google one. It's pretty sluggish but that's the only workaround I was able to find.
The okay Google command only works with screen off on Nexus and Pixel devices. Honor has another command that you must use, but it doesn't tap into Google assistant.
Extinguished said:
I can't recall the source, but I'd read somewhere it only wakes up to the Dear Honor voice command activated in settings. Seemed to work when I tested it. Also found an automate module that senses the honor voice app open, closes it and loads the Google one. It's pretty sluggish but that's the only workaround I was able to find.
Click to expand...
Click to collapse
Care to link to that module please?
pyromayniyak said:
Care to link to that module please?
Click to expand...
Click to collapse
Looks like it's been removed from the list. I went ahead and zipped a copy of the flow so I can upload it here.
Does your "OK google" work properly when the screen is locked? Mine doesn't.
Here is the situation with my phone, and I don't know if this is normal or not.
1. With my phone unlocked, I say "ok google" and it pops up. I then give it a task/ask it a question, and the colored bars at the bottom move indicating it hears me, then it proceeds to perform my task/answer my question. This is the correct behavior.
2. With my phone LOCKED, I say "ok google" and it pops up. I then give it a task/ask it a question, and the colored bars at the bottom DON'T move at all, indicating it doesn't hear me. I then proceed to tell it a task/ask it a question, but it doesn't do anything (since it doesn't appear to be lsitening). This seems like incorrect behavior for me.
Is this by design? Or is there an issue?
Have you a notification app like Notifybuddy installed?
That was it! I have Glimpse notifications installed. I disabled the app and now it works. Thanks!
Is this a one plus bug or an Android bug? This is my first Android phone in years so I have no idea.
EvoXOhio said:
That was it! I have Glimpse notifications installed. I disabled the app and now it works. Thanks!
Is this a one plus bug or an Android bug? This is my first Android phone in years so I have no idea.
Click to expand...
Click to collapse
Not sure what's causing it, but it's an issue with a few apk. Use pixel pulse. No issues
Thanks I will check out that app. I guess what I meant was does this issue only occur on One Plus phones, or all Android phones.
EvoXOhio said:
Thanks I will check out that app. I guess what I meant was does this issue only occur on One Plus phones, or all Android phones.
Click to expand...
Click to collapse
No idea mate.
EvoXOhio said:
That was it! I have Glimpse notifications installed. I disabled the app and now it works. Thanks!
Is this a one plus bug or an Android bug? This is my first Android phone in years so I have no idea.
Click to expand...
Click to collapse
I'm the dev of Glimpse Notifications and was referred here from a user.
Were you able to solve this issue? I have a hard time getting why this would even be, I see no logical connection between Assistant and GN.
What might help would be a full logcat while the effect happens, could you pm that to me?
I was able to use accessibility settings on my OG Pixel and Pixel 3 to enable a confirmation beep when Google Assistant has been activated (after I say "OK Google") but I can't seem to find a way to do that on my Pixel 7 Pro. Can anyone help?
You have to enable "switch access" in accessibility settings.
lsirg said:
You have to enable "switch access" in accessibility settings.
Click to expand...
Click to collapse
I've done this on my OG Pixel and Pixel 3 but it doesn't seem too be working on my Pixel 7 Pro.
I've done it twice now, first setup, and again after a factory reset. Worked both times. Strange.
lsirg said:
I've done it twice now, first setup, and again after a factory reset. Worked both times. Strange.
Click to expand...
Click to collapse
I'm using a Verizon P7 Pro. How about you?
bobo-the-drunk said:
I'm using a Verizon P7 Pro. How about you?
Click to expand...
Click to collapse
Unlocked P7 Pro.
Also here it is not working to enable switch access...
In Google Assistant settings through the Google app you go to accessibility and the options are there and working for me. Not sure if they've recently moved or been changed but I've never used whatever switch access is.
Can confirm that you have to have both of the settings enabled in the screenshot above in order to hear a beep. I don't even have voice active enabled.
JakeDHS07 said:
In Google Assistant settings through the Google app you go to accessibility and the options are there and working for me. Not sure if they've recently moved or been changed but I've never used whatever switch access is.
Click to expand...
Click to collapse
bobbarker2 said:
Can confirm that you have to have both of the settings enabled in the screenshot above in order to hear a beep. I don't even have voice active enabled.
Click to expand...
Click to collapse
Nobody's ever mentioned that setting before but I already had that enabled. I get a confirmation beep when I'm using Bluetooth or Android Auto but not when it's just my phone.
I screwed mine up recently. The above settings were set before, and I've gotten a beep since I got it. Post-screwup, I tried accessibility settings to no avail. Things that were changed beforehand (perhaps - new P7P and I've been both tinkering around and busy - plus I sometimes plug in a DAC and use Neutron Player, which is very possessive. So I can't recall when I noticed the lack of a beep precisely within a day's usage).
So, things that might have affected it:
I allowed Google Assistant to access my screen, and I enabled flash screen when it does so.
I upgraded from the December to January patch.
I upgraded, afterwards, with the small Play Store patch.
I enabled... what's it called - verbal shortcuts like "Answer" that don't require "Hey Google" first. <- Given that Google's reason for zapping the beep was to save response time, I'm suspicious of this, but I've changed quite a bit, so further testing is required.
I'll post if I get the beep back.
***What follows isn't necessary to the topic.***
It's daft that this is even an issue that can't be solved simply with a toggle. Or better, actually asking Assistant to reply when summoned with a beep or phrase, perhaps "Yes, Sir?" In an era with ChatGPT, we ought to be able to at least choose efficient or chummy. Google knows more about me than most friends, they could at least be friendly about it.
[I'm using an unlocked P7P from Google. I'm on Verizon with an eSIM. I have Assistant set so that it's constantly listening. And I've generally got things set to try out everything no matter how intrusive. Hey - it's the first phone I've actively chosen since my Note 4; I wanted to see what we've been given for all that's been taken away. I'm disappointed at all the features that ought to be helpful to my aged father, but are too difficult to use for someone intelligent that can't learn new things well. I'm also seeing just how vastly intrusive it is while saying, carefully, that it isn't. GrapheneOS may be in my future - perhaps because I simply can (goodbye forever, dedicated Verizon phones).]
Just tried Hey Google and ok Google. Both produced the same result, the Google Assistant pops up without a beep.
schmeggy929 said:
Just tried Hey Google and ok Google. Both produced the same result, the Google Assistant pops up without a beep.
Click to expand...
Click to collapse
Yeah mine's been that way for awhile