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

[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?

Related

How To Enable "OK Google Everywhere" On TouchWiz Custom ROMs

I have only done this on custom TouchWiz ROMs, so not sure if it works on other ROMs. It's pretty easy, you must have Titanium Backup and Root Explorer(or similar).
1. Open Titanium Backup and find Google Search 3.5.16.1262550.arm(or whatever version you have). Convert it to a System App.
2. Open Root Explorer and go to /system/app/com.google.android.googlequicksearchbox.apk and move it to /system/priv-app/
3. Reboot ur phone and you should be able to see the settings to enable OK Google on any screen in the Google Search Settings.
Enjoy!!
norml said:
I have only done this on custom TouchWiz ROMs, so not sure if it works on other ROMs. It's pretty easy, you must have Titanium Backup and Root Explorer(or similar).
1. Open Titanium Backup and find Google Search 3.5.16.1262550.arm(or whatever version you have). Convert it to a System App.
2. Open Root Explorer and go to /system/app/com.google.android.googlequicksearchbox.apk and move it to /system/priv-app/
3. Reboot ur phone and you should be able to see the settings to enable OK Google on any screen in the Google Search Settings.
Enjoy!!
Click to expand...
Click to collapse
Have you had any issues with calls? When I run ok google from all screens it sometimes mutes the sound on ingoing and outgoing calls.
mrphotoman said:
Have you had any issues with calls? When I run ok google from all screens it sometimes mutes the sound on ingoing and outgoing calls.
Click to expand...
Click to collapse
I haven't experienced any problems whatsoever, so far.
why is this required as 4.4.2 and the latest google search supports this by default but requires audio history to be enabled.
When I try to say three times "Ok google" does not anything.
Works on my nexus 7 i could set it up but nothing on my S4 att
I have the settings, etc .. but each time i click "Ok google detection" then check "From any screen" and got the set up page where you have to say 3 times Ok google nothing happens
Any idea please ?
norml said:
I have only done this on custom TouchWiz ROMs, so not sure if it works on other ROMs. It's pretty easy, you must have Titanium Backup and Root Explorer(or similar).
1. Open Titanium Backup and find Google Search 3.5.16.1262550.arm(or whatever version you have). Convert it to a System App.
2. Open Root Explorer and go to /system/app/com.google.android.googlequicksearchbox.apk and move it to /system/priv-app/
3. Reboot ur phone and you should be able to see the settings to enable OK Google on any screen in the Google Search Settings.
Enjoy!!
Click to expand...
Click to collapse
There is a much easier way. I have the app. All you have to do is install it and open. When the google now screen pops up just hit back button and then open the settings. Under hot detection check the box that says from any screen and follow the directions. You just have to say "Ok Google" 3 times and then it works from every screen.
Google Search Box
https://www.dropbox.com/s/k7lhqah32ow37en/googlequicksearchbox.apk?dl=0
yea you dont need to manually do anything other then "enable" the option and follow the voice training module. all though if your method does not involve turning on audio location history you may be on to something.

notification fix

OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
sam00561 said:
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
Click to expand...
Click to collapse
Yes that seems to be the problem. I had made a post months ago. It's very hidden feature by Lenovo and I think it's wrong to pre-restrict all background data. User should decide what to do.
I think they lenovo did it to block unnecessary data usage but i agree it is not needed and people are thinking their is something wrong with their phones.
Thanks for the tip
Thanks Sam, I saw this on the JJ review of Nougat. Is this for Nougat as my MM P2 settings don't look like the screenshot.
Sent from my Lenovo P2a42 using Tapatalk
Hi yes it is for Nougat the comment posted on JJs review regarding this fix was posted by me also.
Confusing settings these as the first one makes it look like enabling the "Restrict background data" option will disable background data, when in fact it does the opposite. You need to have both of these options enabled so the sliders are green, then you need to open Settings > Power Manager > Battery Optimization
Then you need to search for the apps that you need to fix notifications and change the option so it says "Don't optimize". Then the phone won't 'helpfully' close the app when the phone has been unused for a long time. This is why notifications are stopping.
precisely i agree quite confusing it took me a while i had to get a friend to send me whats app messages continuously untill i figured all this out but im glad i finally did.
If you make the changes to fix the notifications, shut down and power the phone back on rather than do a reboot. The settings don't seem to work until the phone has properly rebooted.
Is it worth noting that elsewhere it's stated that turning off doze altogether (using ADB) might be a saner option? Consensus seems to indicate it's basically a curse with little value, and that would certainly hold water in light of the battery capacity of the P2.
https://forum.xda-developers.com/lenovo-p2/help/regretting-purchase-t3611968
I think the following helps. Credit goes to JasonMR and manototh (Taken from oneplus.net forum)
JasonMR
KitKat
JasonMR, Nov 2, 2016 :
Guys, to avoid having to run the ADB command after each reboot follow these instructions (please note, the files should be downloaded to a PC and then transferred to your phone via USB otherwise they mess up sometimes):
You need to enable USB debugging mode in Developer options first
Download and install this apk and transfer it to your phones storage - https://drive.google.com/file/d/0BxD...w?usp=drivesdk
Then connect phone to PC and allow the drivers to install
Download and install ADB here - https://drive.google.com/file/d/0B0M...ljU2NPR0k/view
Go into the ADB folder, hold shift, right click and select "Open command prompt here"
Type the command: adb devices (now hit enter)
It should return your phones serial number is connected correctly
Run this command in ADB: adb -d shell pm grant com.adamioan.scriptrunner android.permission.DUMP (now hit enter)
Download this file and transfer it to your phones storage - https://drive.google.com/open?id=0Bx...VA4YmxGTS1OX3c
Open the SH Script runner app and tap the three dots in the top right corner, select "Load" and locate the file from teh previous step
Click the Circle button with the play sign at the top of the screen
You should see the message "Idle mode disabled" which means that Doze has now been disabled.
Whenever you reboot your phone, open the SH Script runner and the command will still be there, just click the play button to run the script again.
And that is it, two clicks to disable Doze after each reboot.
Full credit to manototh for putting this together originally.
Doze does not need disabling iff you follow my advice in the initial post i have tried and tested this and can confirm it works fully.
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Spacedog79 said:
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Click to expand...
Click to collapse
Follow my ordinal post and also go into battery optimisation and disable optimization for things like sms eggs what's app Facebook etc all the things you need notifications for should be disabled from sleep mode under battery optimization.
Like this
sam00561 said:
Like this
Click to expand...
Click to collapse
Yes thats exactly how I've done it. I've also tried every combination of settings under Apps for Unrestricted data usage.
And also the setting here
sam00561 said:
And also the setting here
Click to expand...
Click to collapse
Yep doesn't work either.
Perhaps your only option left is to try the disable doze app which has worked for many people but it's a paid app.
Just to update it does seem to be working properly now. I'm not 100% sure but I think turning the phone all the way off and on again instead of rebooting with the settings correct had the desired effect.

Google Pay - Apps drawing over the screen stopping me adding a card

I'm on Havok Rom, and I've got magisk installed, and it passes all safety checks and is hidden from google pay. Google pay works fine until i go to confirm the card details, then i get a pop up saying "looks like another app is blocking access to the wallet, Turn off any apps that might be drawing over the screen and try again"
I've disabled all apps from Displaying over other apps in the settings, but this error keeps popping up.
Does anyone know solution to this?
Did you find a solution to this? I am on stock and have the same issue.
I don't get the same error message, but I can't use my credit card with Google Pay anymore... I get the error message "Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way".
It is rooted. Of course it is.
I'm using a OnePlus 6 with the latest firmware. My Recovery or Kernel aren't modified. Google Pay is hidden in Magisk and passes the SafetyNet test.
What gives? Google increased it's root detection? Is it happening to someone else?
Thank you!
licenced said:
Did you find a solution to this? I am on stock and have the same issue.
Click to expand...
Click to collapse
no solution found yet, even on a completely fresh ROM install with no apps other than Google it still gives me the same message.
I have the same problem with one banking app. Others work fine except one. Also on stock ROM
Paratax said:
no solution found yet, even on a completely fresh ROM install with no apps other than Google it still gives me the same message.
Click to expand...
Click to collapse
OK, I started thinking maybe this is something to do with the gesture area at the bottom of the screen, and I think I'm right as I have a solution that works (at least for me).
Go to Settings->Buttons & Gestures->Navigation Bar & Gestures
Under 'Choose Navigation Bar' select 'Back, Home, Recents'
Now go into 'Navigation Bar Customisation' and turn on 'Hide the navigation bar' - this will add an icon on the left of the nav bar allowing you to pin or unpin (autohide) it.
Now go back into the Google Pay app and start setting up your card. When you get to the point where the 'Continue' button is missing pin or unpin the navigation bar, depending on what state its in currently. The 'Continue' button will appear.
Doesn't work for me unfortunately, continue button has always been there but I can't click it in the confirming card details section due to the app drawing over the screen notification, and unfortunately removing the nav bar didn't change anything.
Majesty00 said:
I don't get the same error message, but I can't use my credit card with Google Pay anymore... I get the error message "Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way".
It is rooted. Of course it is.
I'm using a OnePlus 6 with the latest firmware. My Recovery or Kernel aren't modified. Google Pay is hidden in Magisk and passes the SafetyNet test.
What gives? Google increased it's root detection? Is it happening to someone else?
Thank you!
Click to expand...
Click to collapse
Had a similar issue. The only way I got it to work is go to settings: Apps -> Google Play Services ->Permissions -> Disable phone/telephone. Try again.
For me BLue light filter app was blocking the wallet to pay after recent update on wallet. By turning off filter app, wallet worked.
This is not working for me as well. Any possible fix? The fixes mentioned in the comments do not work for me. I have disabled drawing over apps for all apps
Possible solution
Make sure you arent using an app to dull your screen resolution. Turn it off in settings.
I don't know if this will work or not but I would suggest going through all of your apps yes I know it's probably a lot. Turning off the permission to draw over other apps one by one. Reboot your device and check to see if it's working
Paratax said:
I'm on Havok Rom, and I've got magisk installed, and it passes all safety checks and is hidden from google pay. Google pay works fine until i go to confirm the card details, then i get a pop up saying "looks like another app is blocking access to the wallet, Turn off any apps that might be drawing over the screen and try again"
I've disabled all apps from Displaying over other apps in the settings, but this error keeps popping up.
Does anyone know solution to this?
Click to expand...
Click to collapse
Try turning off smart pixels or any such thing
Try turning off battery saver. It worked for me.
Got the resolution
Just turn off the smart pixel if it's enabled
I found the solution guys. App notifications are the culprits here. You have to clear the notifications by dragging down the notification bar from top. It resolved the issue for me. Please try and comment.
The Problem I have also face, but I have resolved the issue by uninstalling the blue lite app, the screen will impact on the google pay and Irctc app
Sorry for posting in the wrong section. I am using Oneplus 5 with the crdroid pie based rom. For me the issue was fixed by turning off the smart pixels option in crdroid settings.
Developer options
The only thing that helped me was disabling developer options. I think Google Pay assumes that since the developer options are enable the device isn't safe.
Hope it helps.
(I have an ASUS Zenfone 4)
I had the same issue on android. Turned out it was the facebook messenger app. Force close it in app settings and should work

Manual FRP Bypass TCL 30XE Android 12 with Jan 2023 security patch.

I just manually bypassed FRP lock on a TCL 30XE device that is running the Jan 2023 security patch for Android 12. I could only find a single video done 4 days ago that manually bypassed FRP but my way was a step different. Pretty simple. Here is step by step instructions. Pretty sure it will work for Samsung and other android devices because the hardware is so similar that a phone kiosk thought the TCL30XE was a Samsung. Here are the steps...
STEP 1: On the opening menu after factory reset it done click on the eyeball where it says vision settings.
Step 2: Click on talk back. On the next screen at the top right click on the blue switch so it mover to the right turning on talk back. Hit the back arrow and you will be taken to the talk back tutorial.
STEP 3: Draw a backwards L on the screen by swiping from left to right and then up. A menu will come up that explains the voice control options. Click on highlighted line that says, Use Voice Control. As soon as you click on it say "Open Google Assistant" and the Google Assistant Screen will come up across the bottle of the device.
STEP 4: In the center of the Google Assistant screen there is a microphone. Click on it and say, "Open Device Settings" A option will pop in in Google Assistant screen that says, Device Settings, double click on it. When you do the Device Settings munu will open.
Step 4: Go to Apps and click, On next screen click on, Open all Apps,it will be in blue writing, next screen on top right click on 3 vertical dots and 3 options will pop up, choose show system apps.
Click on each of these apps and go to the storage and delete all data. Android Setup, Google Play store, Setup Wizard, and Google Play Services. The Google Play Services will have 3 lines on top of each other and say Manage Storage, click on it and the bottom option is Delete All App Data, click on it. The others you just click on storage, delete data.
Step 5: Restart phone, you should be able to put in your Google account once the phone boots up and FRP no longer active. That's it...
I have tried all the instructions lately for the TLC 20xe but when we get to the APPS list under settings, nothing happens when we click on the any of the apps (Android Setup, Google Play Store or any other).
It wont go to the next page for the Force Stop or Clear Data
Maybe google patched it? It's still running Android 11
Me too same thing can't get in
NoTime4Gamez said:
I have tried all the instructions lately for the TLC 20xe but when we get to the APPS list under settings, nothing happens when we click on the any of the apps (Android Setup, Google Play Store or any other).
It wont go to the next page for the Force Stop or Clear Data
Maybe google patched it? It's still running Android 11
Click to expand...
Click to collapse
Please PM me I can hlep you unlock your device.
Please PM me I can hlep you unlock your device.
Jennacyde said:
Me too same thing can't get in
Click to expand...
Click to collapse

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.

Categories

Resources