Database Info

Surely there's a solution

I've searched here, google, etc... and the solution still escapes me
How in the world do I launch Google voice search (rather than S Voice) via bluetooth when the phone is locked? This is for bluetooth dialing and navigating (push and hold BT headset call button, say "CALL ......" or "NAVIGATE TO ......."
I don't want to flash a new ROM for this, but I'm willing to consider it IF:
- Above function works
- GPS locks are just as fast as stock
- Stability is top notch
- Battery life is as good or better than stock
- UI must be smooth
Stock ROM is great!!! I'd hate to deviate, but I hate even more not being able to use the BT dialing (S Voice SUCKS and rarely works!!!)
I have to have my phone locked (exchange server rules for my employer email)... it's a good policy anyway.
I am currently Stock Rooted, bootloader locked (I can unlock if necessary)
I've seen suggestions to use the Bluetotth launcher app, which works, but not when phone is locked.
The stock ICS has this feature. I hate the Samsung forced S Voice without giving us the alternative to go back to the google apps (which is MUCH better).

I have no clue. How about random ideas?
Try clearing defaults for S Voice and Google Search in the App Manager
Check the settings in both apps (I'm fairly sure I saw an option regarding launching S Voice from the Home button in it's settings)
Try disabling/uninstalling S Voice

Sycobob said:
I have no clue. How about random ideas?
Try clearing defaults for S Voice and Google Search in the App Manager
Check the settings in both apps (I'm fairly sure I saw an option regarding launching S Voice from the Home button in it's settings)
Try disabling/uninstalling S Voice
Click to expand...
Click to collapse
I've frozen S Voice with Titanium Backup. All that did was completely remove any ability for voice dialing through bluetooth.
The settings you refered to is a good suggestion, but only disables the home button (pressing it twice) from launching S Voice
Google Voice Search has no usable settings and I'm unable to use it as a default rather than S Voice

Have you tried to disable S voice from the applications settings menu? Certain launchers will allow to to assign actions to buttons. Not sure if BT is included.
And don't call me Shirley.

bobloblaw1 said:
Have you tried to disable S voice from the applications settings menu? Certain launchers will allow to to assign actions to buttons. Not sure if BT is included.
And don't call me Shirley.
Click to expand...
Click to collapse
Freezing in titanium is the same as disabling in the applications menu.
I feel like i read somewhere that synergyROM had this feature of google now replacing s-voice when you froze it. Ill try to find what im talking about for you. Thats the only solution i can think of.
Sent from my SCH-I535 using xda app-developers app

Ok Google with Home Button

Ok So pretty simple request. I want to activate "Ok Google" using the home button just like S Voice or Siri behaves. With Google set as the Device Assistance App a long press of the home button pulls up the google app, then I have to click the mic button. Or I have to activate it by saying "Ok Google" which is super annoying. I've searched everywhere for a solution and the only thing I found was the following:
https://www.reddit.com/r/AndroidQue...t_possible_to_activate_ok_google_with_a_home/
Which doesn't work at all on the S7. A long press of the home button opens the Launcher App which asks me to select google. Basically adding a 3rd step.
I'd appreciate any help!

I use the Google Now Launcher and I had that ability. I will have to play around with my settings to get it back because I installed Labs so when I hold my home button down it waits for me to say a contact name and it calls them. I will have to get back with you on that when I can get access to my phone.

Ok, maybe the new version of the launcher doesn't support that. Now long press doesn't do voice search, it instead shows Now on Tap, but different than what I remember.

Outbreak444 said:
Ok, maybe the new version of the launcher doesn't support that. Now long press doesn't do voice search, it instead shows Now on Tap, but different than what I remember.
Click to expand...
Click to collapse
Yup.. I still haven't found a workaround. Having the mic always on to detect "OK Google" seems to be a waste of battery.
Hopefully a solution comes up. Thanks for trying.

H3lipil0t said:
Yup.. I still haven't found a workaround. Having the mic always on to detect "OK Google" seems to be a waste of battery.
Hopefully a solution comes up. Thanks for trying.
Click to expand...
Click to collapse
I have found a solution that works great! I just tested it myself.
Download this app here:
https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en
You'll want to open it up, select the 3 dots, and then select add.
Add Voice Search, then do the same steps but remove whatever else was there by default.
Now if you're on marshmallow, which I assume you are, then you'll need to go to Settings -> Applications -> Default Applications -> Phone assistance app
And change it to Home Launcher
Give that a try and let me know if that works for you.

Outbreak444 said:
I have found a solution that works great! I just tested it myself.
Download this app here:
https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en
You'll want to open it up, select the 3 dots, and then select add.
Add Voice Search, then do the same steps but remove whatever else was there by default.
Now if you're on marshmallow, which I assume you are, then you'll need to go to Settings -> Applications -> Default Applications -> Phone assistance app
And change it to Home Launcher
Give that a try and let me know if that works for you.
Click to expand...
Click to collapse
You are the man!!!! This worked.. "Auto Start mode" had to also be selected but this finally got the job done.
It wasn't perfect at first. for some reason the responses to my questions where not audible.
For Example.. If I held the home button, the voice prompt shows up and I say "What's my next appointment?". It displayed the calendar item but didn't read back the result. If I activated it saying "OK Google" and asked the same question, I was shown the response and it read back to me. "You're next calendar entry is tomorrow at 7am...".
I tried it again a few more times. Now it seems to be working properly with the home button.
You've made my day. Wish I could buy you a pint of beer remotely.
Cheers!

A simple thanks is plenty, I've got all the beer I need in my fridge. Lol

Was looking for a solution as well. Works great. Thanks.

How do you enable OK Google?

The title says it all. It is grayed out whether custom choice wake up is selected or not.

Go to the Google menu km the Settings, from there "search and now" and enable what you need.

Thanks for the advice but that option is grayed out. ""Ok Google" detction" Under "Search & Now". I will post a screenshot later on.

Try cleaning the data of the google app, then uninstall and reinstall.

As far as I know, OK Google works from the app or google launcher home screen

This is what it looks like. I tried clearing cache and data. I will now try uninstalling the updates.
Edit: I cannot uninstall or disable the Google app. What gives? I want to avoid factory reset if possible.

Look for permissions given to the google app, enable mic if disabled and try google now launcher

Thank you for the advice. I was able to get the "OK Google" command to work. The option is still grayed out in the setting, but I did it via Google Play app. It is an odd bug (if it is). Maybe it has to do with Huawei's voice command option (that wakes up the phone)?

It can, since EMUI is kinda aggressive with apps

lopri said:
The title says it all. It is grayed out whether custom choice wake up is selected or not.
Click to expand...
Click to collapse
Forwarding the instruction how to enable OK Google voice command from everywhere if someone is interested...
https://www.xda-developers.com/enab...ord-detection-on-huawei-honor-phones-no-root/

[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 Per-app volume?

Is there any way to set a specific apps volume?
I am literally going mad over the fact that Google assistant is linked to media volume. Since I always have media volume at 25% I can't hear what the assistant says...
I've tried Google with no avail, I can only find threads leading to a Samsung store locked app and to apps removed from play store.
I am rooted and I've looked at magisk modules but can't find anything there either.
Is it just impossible on pixel devices to adjust assistant volume seperate from media volume?

Macrodroid/Tasker would work.
Would be something like:
If "google assistant" in foreground set volume to "x%".

xtcislove said:
Macrodroid/Tasker would work.
Would be something like:
If "google assistant" in foreground set volume to "x%".
Click to expand...
Click to collapse
I tried looking at tasker but I can't find Google assistant as an app there.
And also, I couldn't understand how to get it to turn volume back to previous value afterwards when I was testing around on other apps.

BunnyPig said:
I tried looking at tasker but I can't find Google assistant as an app there.
And also, I couldn't understand how to get it to turn volume back to previous value afterwards when I was testing around on other apps.
Click to expand...
Click to collapse
idk about tasker but im sure you can do it with macrodroid.
You can pick the app or define the package name.
You can pick actual volume probably with macrodroid internal tools but 100% with command line (adb shell dumpsys audio) you can store the value in a custom variable and restore this value if assistant is not in foreground anymore.
I sure its doable with macrodroid

xtcislove said:
idk about tasker but im sure you can do it with macrodroid.
You can pick the app or define the package name.
You can pick actual volume probably with macrodroid internal tools but 100% with command line (adb shell dumpsys audio) you can store the value in a custom variable and restore this value if assistant is not in foreground anymore.
I sure its doable with macrodroid
Click to expand...
Click to collapse
I tried using macrodroid now but it doesn't do anything when I speak to assistant. I allowed accessibility option, root, disabled battery optimization etc but it won't do anything. Tried using screen content as well but same result unfortunately.
Is it anything wrong with the macro itself?
Edit: added another image to show some other triggers I've tried.

BunnyPig said:
I tried using macrodroid now but it doesn't do anything when I speak to assistant. I allowed accessibility option, root, disabled battery optimization etc but it won't do anything. Tried using screen content as well but same result unfortunately.
Is it anything wrong with the macro itself?
Edit: added another image to show some other triggers I've tried.
Click to expand...
Click to collapse
Its working for me.
If i say hey google media is set to 100%, if i exit it get set to 25%.
You only need a way now to capture the volume you used before. Thats pretty easy too. I can look tomorrow or later if you cant get it to work.

xtcislove said:
Its working for me.
If i say hey google media is set to 100%, if i exit it get set to 25%.
You only need a way now to capture the volume you used before. Thats pretty easy too. I can look tomorrow or later if you cant get it to work.
Click to expand...
Click to collapse
Tried your macro but still doesn't do anything. If I just try it on something else, say phone app it works flawlessly same as mine did, but not Google assistant. Have you installed the play store version (asking because I can install the store version but it's already installed with the stock os so I haven't)?

BunnyPig said:
I tried looking at tasker but I can't find Google assistant as an app there.
And also, I couldn't understand how to get it to turn volume back to previous value afterwards when I was testing around on other apps.
Click to expand...
Click to collapse
I tried to make this work in Tasker, and at least on QPR3 I couldnt get it to work....the app is Assistant so should be one of the first apps in the list.

BunnyPig said:
Tried your macro but still doesn't do anything. If I just try it on something else, say phone app it works flawlessly same as mine did, but not Google assistant. Have you installed the play store version (asking because I can install the store version but it's already installed with the stock os so I haven't)?
Click to expand...
Click to collapse
I made a full wipe today and installed latest A13 stable release from march 13.
You might like to tick the box to show system apps and try it with the 2 assistant apps (xenrollment and the other).
You might need to install Macrodroid Helper app....

xtcislove said:
I made a full wipe today and installed latest A13 stable release from march 13.
You might like to tick the box to show system apps and try it with the 2 assistant apps (xenrollment and the other).
You might need to install Macrodroid Helper app....
Click to expand...
Click to collapse
I have the assistant boxes checked (both of them) in the previous image I've posted.
I also tried installing the play store version of assistant to see if that made any difference but no, macrodroid does nothing when assistant opens.
I'll try macrodroid helper later to see if that makes any difference.

Update: it now just works, well, wonky but it works. I set a timer instead of the trigger fired and it works, but only when the phone is unlocked. If it's sleeping and I ask the assistant something it won't raise the volume, or rather the triggers won't work. Is this normal or have I missed a setting that prevents macrodroid from working while the phone is sleeping?

If you're rooted you could use this:
https://www.xda-developers.com/app-volume-control-individual-volume-levels-android/
It allows to individually set volumes per app.
I'm using it to be able to let Spotify run as background music while playing games.

wooki said:
If you're rooted you could use this:
https://www.xda-developers.com/app-volume-control-individual-volume-levels-android/
It allows to individually set volumes per app.
I'm using it to be able to let Spotify run as background music while playing games.
Click to expand...
Click to collapse
Doesn't work either, I tried it earlier and I tried iy again just to be sure, I manually add Google and Google assistant at 100% volume but it doesn't do anything. I made sure to disable macrodroid as well just in case it would interfere but it made no difference.
Also, that app won't recognize assistant in the audio stream, so I don't think it will be able to control the volume from assistant. That's what I gathered from reading the documentation as well.