Database Info

[Q] Odd classic voice dialer intermittently when using wired headset

Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3

bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.

joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3

take a screenshot of your classic looking dialer and post it here.

simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3

bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.

simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3

instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.

simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3

Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3

bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.

simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3

bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.

Touchless Control

Is anyone else having a problem with their touch less controls. I can say OK google now and the phone will make a noise. But when google now opens it says " Sorry can't reach google right now ". Same goes for any other kind of voice driven function , texting by voice in the stock messaging app, search in the maps app. They all hive me the same reply. I've checked all my setting. Im at a complete loss
Rooted & unlocked. Otherwise stock .

Have you updated your google search app?

I used HOM and fxz'd my phone . The google vioce app now works but the Moto touchless controls still don't

Google Now needs an active internet connection.

I have tried everything. I've spoken to Verizon who then refered me to Moto. Who had clear partition caches to no avail. Any and all voice recognition on my phone has ceased to work. Sometimes Google will open up to say " Can't reach google at the moment ". However if I manually open the search box Google now and all my cards are there. If I then hit the microphone icon It will again say "Can't reach google at the moment ". I'm at my wits end here. This will happen weather Im using my wifi or 4G signal.
I've fxz'd and that didn't work. I will entertain any and all ideas.

Any resolution with the voice control problem? I am having the same problem with my Droid Maxx running 4.4.4. It just started this week and I have reset it, but that didn't solve the problem. I figured the old apps wouldn't have the same problem as the newer versions. Guess I was wrong. I am trying Verizon Repair assistant to see what it can do for me. We will see.

tombaldwin6 said:
I have tried everything. I've spoken to Verizon who then refered me to Moto. Who had clear partition caches to no avail. Any and all voice recognition on my phone has ceased to work. Sometimes Google will open up to say " Can't reach google at the moment ". However if I manually open the search box Google now and all my cards are there. If I then hit the microphone icon It will again say "Can't reach google at the moment ". I'm at my wits end here. This will happen weather Im using my wifi or 4G signal.
I've fxz'd and that didn't work. I will entertain any and all ideas.
Click to expand...
Click to collapse
Post your touchless/moto voice version from settings/app. They are interchangeable in name now. If you have the newest you must uninstall updates & retrain touchless voice.

I ended up FDRing the phone twice. The first time I let my apps reload automatically and my touchless control still didn't work. So I did it again, but the time I reloaded each app individually. Testing the touchless controls between each install. I ended up reinstalling every app but the one I thought was the culprit. This is no knock on the app I used it and I wish I could put it back in. Elixor2 has a setting where you can control and or turn on/off each of the sensors including the microphone. When I was having the problem I would go into elixir and see that my microphone was off and inaccessible. With out elixor2 on my phone I've had no more problems.

I have done the same type thing as Tom Baldwin6. I "redid" my phone using the Verizon software installation assistant and did a "repair". I then rooted it using TWRP, and started adding stuff. I have not had the problem again as of now.
I was thinking it was the experimental app that was allowing me to mirror my phone using Chromecast, but I am using version 4 of that app and it is still working. I used version 5 before.
My phone hasn't had a problem again after 24 hours, but as I continue to add apps and check, eventually I may find another culprit. I will post here if I get it tracked down.

jmaclean62 said:
I have done the same type thing as Tom Baldwin6. I "redid" my phone using the Verizon software installation assistant and did a "repair". I then rooted it using TWRP, and started adding stuff. I have not had the problem again as of now.
I was thinking it was the experimental app that was allowing me to mirror my phone using Chromecast, but I am using version 4 of that app and it is still working. I used version 5 before.
My phone hasn't had a problem again after 24 hours, but as I continue to add apps and check, eventually I may find another culprit. I will post here if I get it tracked down.
Click to expand...
Click to collapse
I suspected the the chromecast mirror as well It was one of the 1st apps I reloaded. But it wasn't it. I'm certain it has something to do with the microphone

Same issue here. Been a week since I FDR'd (NOT rooted or unlocked). The apps restored, touchless control no longer allows to register voice (does not recognize sound ONLY for Touchless Control).
Saw that Touchless Control has been updated to "Moto Voice",
Uninstalled Moto Voice to return to previous version. No luck. Again updated to Moto Voice.
Wipe Cache Partition, no luck.
I've installed Open Mic+, which works for the most part (never got it to work from lock screen)
Stopped Open Mic+.
I then went in Language & input ---> Google voice typing settings (or Voice Search), disabled/re-enabled Speech Output. Clicked on "Ok Google Detection" and did the standard Google Now/OK Google setup again.
Went back to Touchless Control and this time it recognized my voice and allowed me to setup Touchless Control and all is working again.
Although the new "Moto Voice" on the "1st Gen [2013] Ultra/Maxx etc.., you cannot customize the "OK Google Now" at this time (coming feature for Gen 1's).
Rebooting now to ensure operation. Will updated/verify 'fix' in a moment.
Upon restart, my Open Mic+ restarted, and the "OK Google Now" was not working. Stopped the Open Mic+ and touchless control working again. Went in and re-trained to verify. Unintalling Open Mic+ and rebooting now.
Now again working 100%, now just awaiting Moto Voice update to allow additional features for 1st gen's.

i have got mine working gain too. I still haven't reinstalled everything though. I will reinstall x tether this weekend. I am hoping that it isn't cuseing any problems. Can't imagine why it would, but we will see. Do you guys have it installed?

Did you happen to open the Google app, scroll to the bottom, tap the three dot menu control on the bottom right, tap settings, voice, OK Google detection, and turn off the setting "On any screen"?
If that is on, I think it block touchless controls, maddeningly. I know it stops the Assist driving feature from being able to capture voice when it prompts you.

doogald said:
Did you happen to open the Google app, scroll to the bottom, tap the three dot menu control on the bottom right, tap settings, voice, OK Google detection, and turn off the setting "On any screen"?
If that is on, I think it block touchless controls, maddeningly. I know it stops the Assist driving feature from being able to capture voice when it prompts you.
Click to expand...
Click to collapse
I set "on any screen" option and touchless controls does work from any screen, needing only "OK Google".
I am not driving now but will check Assist in about 2 hours.

iamtek7 said:
I set "on any screen" option and touchless controls does work from any screen, needing only "OK Google".
I am not driving now but will check Assist in about 2 hours.
Click to expand...
Click to collapse
I don't think that's touchless controls - I think that's the Google search app listening and responding to ok Google , and, with that setting on, that's probably why you couldn't train in the Touchless controls settings (though I haven't tested that myself, since my phone is already trained.)
I know it's a subtle difference, but Touchless controls is a front end to google search most of the time, though sometimes it does its own thing (ok Google now, what's up?)
I do know that the any screen setting screws up some other things, like preventing the camera app from capturing video (because the microphone is in use).

I'm all set now. If this is still an issue for anyone, let me know.
Sent from my XT1080 Developer Edition using Tapatalk

Android Wear voice action to play music only works if the phone screen is on & unlock

Android Wear voice action to play music only works if the phone screen is on & unlock
Using Android Wear voice command "listen to..." or "play ..." will basically queue up my music and won't start playing until I unlock and/or turn my screen on. I've spent a bunch of time trying different music on my phone locally and streaming and each time I have to have my phone on for it to start playing. How can I fix this?

legato89 said:
Using Android Wear voice command "listen to..." or "play ..." will basically queue up my music and won't start playing until I unlock and/or turn my screen on. I've spent a bunch of time trying different music on my phone locally and streaming and each time I have to have my phone on for it to start playing. How can I fix this?
Click to expand...
Click to collapse
These could the reasons but I would need more information
Do you have any app which hibernates your apps in deep sleep mode (screen off) Like Greenify /Amplify etc?
Are you on a custom rom ?
do you use battery saver mode while trying this ?
Quote me back in case you expect a reply!

Hnk1 said:
These could the reasons but I would need more information
Do you have any app which hibernates your apps in deep sleep mode (screen off) Like Greenify /Amplify etc?
Are you on a custom rom ?
do you use battery saver mode while trying this ?
Quote me back in case you expect a reply!
Click to expand...
Click to collapse
I do not use Greenify /Amplify. The only app I have that's close or allows changes to how my phone behaves is 3C Toolbox, and I haven't enabled or changed anything in that app.
I do not use a custom ROM. I am stock rooted on the Tmobile ROM, so locked bootloader.
I have turned off stamina mode, which I have set to activate at 15% anyway, with the same results.

legato89 said:
I do not use Greenify /Amplify. The only app I have that's close or allows changes to how my phone behaves is 3C Toolbox, and I haven't enabled or changed anything in that app.
I do not use a custom ROM. I am stock rooted on the Tmobile ROM, so locked bootloader.
I have turned off stamina mode, which I have set to activate at 15% anyway, with the same results.
Click to expand...
Click to collapse
So according to you, you do not use any battery saving apps or stamina mode neither hibernation apps or any custom ROM or kernel and still you need to turn on screen to run music player. You send commands via your android wear to your phone via bluetooth and both devices are paired. Try removing the toolbox and see any differences ..
Which version of android are you running and secondly have you tried restarting devices and re-pairing as well.
Seems to me some compatibility issues. Are you using stock music player or some different app?
Try google music and see if that helps.
Quote me back for a reply.

Hnk1 said:
So according to you, you do not use any battery saving apps or stamina mode neither hibernation apps or any custom ROM or kernel and still you need to turn on screen to run music player. You send commands via your android wear to your phone via bluetooth and both devices are paired. Try removing the toolbox and see any differences ..
Which version of android are you running and secondly have you tried restarting devices and re-pairing as well.
Seems to me some compatibility issues. Are you using stock music player or some different app?
Try google music and see if that helps.
Quote me back for a reply.
Click to expand...
Click to collapse
Correct. As soon as I turn the display on, Google Play Music is opened ( I can't tell if it loads when I unlock/turn the display on or if it gets that far and doesn't play) and starts playing. I will try removing 3C.
I'm on 5.0.2, the latest Tmobile firmware. I have Google Play Music set as the default action, for that voice action.

After much troubleshooting I was able to find my answer: I need to say either artist+album, artist+song, or Album to get playback to start while the screen is off and phone is locked. Saying "listen to *artist* does not start playback until the screen is turned on, and it appears it will pick a random song to play.

[Guide] [Magisk] How to Enable Google Call Screening on "Unsupported" Devices

[Guide] [Magisk] How to Enable Google Call Screening on "Unsupported" Devices
This should work on any device that is able to replicate the instructions here, there may be some things that I forget to mention that have an effect on if it works, just report back and I will try to add more details.
Tested on my OnePlus 7 pro, with everything updated, no special app version for Google Phone or anything like that
I take no responsibility for anything that happens with your device, although this should all be relatively safe and reverseable.
You must be rooted with Magisk, this is mostly done with modules that are available on the official repo.
1. You will Need these Magisk Modules installed
App Systemizer
Google Dialer Framework
MagiskHide Props Config
Google Call Screening or if this doesn't work you can just edit the prefs xml manually with Prefedit . If you do use this module you will also need:
Busybox for Android NDK.
2 I just realized this part was an exact copy of the guide over at gadgethacks[/URL] , and they did a way more detailed job than I could do, so credit where it's due.
Summarized :
Google Phone should be installable from the Play store after a reboot, if not try clearing Play store storage, if that doesn't work, try clearing Play services storage, if that doesn't work, try installing it from Apkmirror.
Systemize Google phone according to the Systemizer, gadgethacks really breaks this down, you need a terminal emulator, and you do a "su" command, and then a "systemize" command, and its pretty straightforward after that, just find it and select it and reboot. I think you might want to disable your stock dialer in your settings as well.
Make sure Google phone has all the permissions granted and is set as your default spam app (Search for spam in your phone settings).
3. Now for the new part, as the one on gadgethacks doesn't work anymore.
Open terminal emulator again, run a "su" command, and a "props" command.
Select device simulation, (You might have to enable it first) and navigate through the menu, to Google Pixel 4(XL). You might have to go all the way back to the main menu, as it only applys half the props, and go into device simulation again and apply all the props ( I skipped display.id as I don't know if that would mess up anything, and I didn't need it).
4. Reboot. Now just wait a little, clear Google Phone Data, Play Services Data (Don't know if this is necessary). After a bit you should be able to go into Google Phone settings and it should say call screen there, I think you need to be on WiFi for it to enable, and it takes a bit, I had to wait for a while and then it started working.

In for later

Currently on OnePlus 7T Pro McLaren 5G TMO, running AOSiP, and the option shows up. But upon trying it, caller cannot hear a voice and no transcription shows up on my end. Using app from play store.

What version of the Google dialer are you using?

Fatmonk8 said:
What version of the Google dialer are you using?
Click to expand...
Click to collapse
Latest available on the play store.

Thanks this worked for me on OnePlus 7 Pro on latest beta firmware.

Funny. On my OP7Pro, after following the instructions and enabling call screen successfully, I disabled the MagiskHidePropsConfig module and Call Screen is still there, even after a reboot. I'm guessing it will go away if I clear the phone and maybe Google Play Services app data...
Edit: Nope. Thought disabling PropsConfig was okay but Call Screen went away later on. Oh well...

ih8legal said:
This should work on any device that is able to replicate the instructions here, there may be some things that I forget to mention that have an effect on if it works, just report back and I will try to add more details.
Tested on my OnePlus 7 pro, with everything updated, no special app version for Google Phone or anything like that
I take no responsibility for anything that happens with your device, although this should all be relatively safe and reverseable.
You must be rooted with Magisk, this is mostly done with modules that are available on the official repo.
1. You will Need these Magisk Modules installed
App Systemizer
Google Dialer Framework
MagiskHide Props Config
Google Call Screening or if this doesn't work you can just edit the prefs xml manually with Prefedit . If you do use this module you will also need:
Busybox for Android NDK.
2 I just realized this part was an exact copy of the guide over at gadgethacks[/URL] , and they did a way more detailed job than I could do, so credit where it's due.
Summarized :
Google Phone should be installable from the Play store after a reboot, if not try clearing Play store storage, if that doesn't work, try clearing Play services storage, if that doesn't work, try installing it from Apkmirror.
Systemize Google phone according to the Systemizer, gadgethacks really breaks this down, you need a terminal emulator, and you do a "su" command, and then a "systemize" command, and its pretty straightforward after that, just find it and select it and reboot. I think you might want to disable your stock dialer in your settings as well.
Make sure Google phone has all the permissions granted and is set as your default spam app (Search for spam in your phone settings).
3. Now for the new part, as the one on gadgethacks doesn't work anymore.
Open terminal emulator again, run a "su" command, and a "props" command.
Select device simulation, (You might have to enable it first) and navigate through the menu, to Google Pixel 4(XL). You might have to go all the way back to the main menu, as it only applys half the props, and go into device simulation again and apply all the props ( I skipped display.id as I don't know if that would mess up anything, and I didn't need it).
4. Reboot. Now just wait a little, clear Google Phone Data, Play Services Data (Don't know if this is necessary). After a bit you should be able to go into Google Phone settings and it should say call screen there, I think you need to be on WiFi for it to enable, and it takes a bit, I had to wait for a while and then it started working.
Click to expand...
Click to collapse
Thanks for this quide - although I'm a bit confused as I haven't done any props simulation before.
I've enabled simulation by setting the phone as my OnePlus 8 Pro (INC2023) and have enabled all of the props, but I'm unsure of what you mean by 'and navigate through the menu, to Google Pixel 4(XL)'.
The only way I can find the 4XL is by changing my device fingerprint, is that righjt? (I have tried that, but the screen is set to the lowest brightness and can't be changed and the call screening option doesn't appear in the Phone settings). I've changed back to my IN2023 and its functioning as normal again.
Thanks again

You need to set your phone as the Pixel 4 xl. Your screen might be acting up because of the screen ID property, which isn't necessary to change. See the attached screenshot in the OP.

ih8legal said:
You need to set your phone as the Pixel 4 xl. Your screen might be acting up because of the screen ID property, which isn't necessary to change. See the attached screenshot in the OP.
Click to expand...
Click to collapse
I checked and it looks fine to me, am I missing something?:
https://imgur.com/a/DCZYgm9

That looks right, but according to your first post I think you might be simulating your own device, you need to simulate the pixel 4(xl)

Sorry, I meant that in order to enable simulation I had to set up the initial fingerprint so I set up the op8p, from there I enabled simulation and then set the props as the pixel 4 XL.

On the main screen of the module, in the terminal, select option 1 ( edit device fingerprint) should look like this. If not change it within the submenus.

ih8legal said:
On the main screen of the module, in the terminal, select option 1 ( edit device fingerprint) should look like this. If not change it within the submenus.
Click to expand...
Click to collapse
I got the attached..

meffles said:
I got the attached..
Click to expand...
Click to collapse
Ok looks right. If everything else is good, I think Google phone needs to be a system app, set as default phone app, and maybe clear Google play services data, it should pop up in google phone settings where you can enable it.

ih8legal said:
Ok looks right. If everything else is good, I think Google phone needs to be a system app, set as default phone app, and maybe clear Google play services data, it should pop up in google phone settings where you can enable it.
Click to expand...
Click to collapse
Yeah, but I'm guessing something isn't quite right if I'm getting this dim screen.. I've reset my props and am going to try again from scratch. Will let you know how it goes

ih8legal said:
Ok looks right. If everything else is good, I think Google phone needs to be a system app, set as default phone app, and maybe clear Google play services data, it should pop up in google phone settings where you can enable it.
Click to expand...
Click to collapse
Ok so I just had the fun of going through each of the props parameters to see which one(s) caused my screen to dim. 3, 8 & 9 need to be disabled, else the screen goes dim.
I've just cleared the phone and play services data and now waiting to see if call screening appears..
Or do you think 3 and 9 need to be enabled?

It's not looking like the option is going to show..

I think 3 probably needs to be on.

Ok, I've enabled 3 just to see if it appears, just waiting to find out. Does it matter that I'm in the UK and it wouldn't normally appear if I had a pixel?

Question Google Assistant Confirmation Beep

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