Call Screening is working on the OOS Android 10 Open Beta 1 with the following instructions (ignore the first 3 steps if you're already on Android 10 open beta and rooted):
Requirements:
Android 10 Open Beta 1 (prior to OB1, there’s an issue with the caller not being able to hear the Assistant voice properly)
Root is necessary to make Google Phone a system app and to make the required mods to the XML file
Either the Pix3lify Magisk module or the Google Dialer Framework module (much lighter) to install the Google Phone app from the Play Store (might have to clear Play Store data/cache), or a patched Google Phone APK
App Systemizer and Busybox Magisk modules and Terminal Emulator
Preferences Manager Attached Google Call Screening Magisk module (all credit to thehappydinoa, I just updated it for the Call Screening flags on the latest Google Phone app)
Instructions:
install the beta
fastboot flash the patch root boot image from here (fastboot flash boot magisk_patched.img)
install TWRP and re-install Magisk both from Magisk, reboot
install Busybox and App Systemizer in Magisk
install Google Phone app using one of the above methods, enable all permissions and set as default Phone app, disable OOS Phone app, Systemize using Terminal Emulator (type su, then systemize, then choose the Phone app and systemize it to /system/priv-app), reboot
in Preferences Manager, enable system apps, scroll down to Phone, go to dialer_phenotype_flags.xml, search for ‘screen’ and set all the call_screen and callscreen flags to true, and search for ‘speak’ and set all the speakeasy and speak_easy flags to true. Install Call Screening Magisk Module, reboot
It seems Google Visual Voicemail seems to work only on certain phones with certain carriers, but not on the GM1917 with T-Mobile. I’ve tried putting the GM1915 software on my GM1917 but still can’t get it to work. It seems to work with GM1915s that have been converted to international firmware and rooted when Google Phone is installed as a system app as above.
Finally!!! I thought I was alone! Hope to see where this goes I really miss Google visual voicemail
Doesn't the "pixelfy" magisk module warn about bootloops on oxygen OS? Otherwise, wow, you got the screening to work, awesome! Unfortunately, I have nothing to offer on why the volume would be too low.
Cm4nXD said:
Finally!!! I thought I was alone! Hope to see where this goes I really miss Google visual voicemail
Click to expand...
Click to collapse
You're not alone! I really want the Google visual voicemail and transcription. I feel like it's an issue with my phone/account because there was someone with a OnePlus 6T with a very similar mod that got it working on T-Mobile. I might just need to wipe and try again.
jetfire245 said:
Doesn't the "pixelfy" magisk module warn about bootloops on oxygen OS? Otherwise, wow, you got the screening to work, awesome! Unfortunately, I have nothing to offer on why the volume would be too low.
Click to expand...
Click to collapse
It does give that warning, but I've had no issues with it. I've been using it since this phone first got Magisk. YMMV, of course.
Attempted everything included in the tutorial but I used dialer framework. Sadly, I could not get anything to appear. What was used in the guide?
Edit: I noticed the modified xml is about 28kb. Before I replace the xml in my root, it's about 14kb. I'll replace the file, and restart, only to see, I have a 14kb file again. Is this the issue?
It worked for me. Google Visual Voicemail and Transcriptions! I got the Call Screen options but did not receive any calls to test out out. Here is the rub... Google Phone went to sleep last night with everything set. This morning it had reverted to the standard set of options. Visual Voicemail, (no Transcriptions), and no Call Screen.
ozfive said:
It worked for me. Google Visual Voicemail and Transcriptions! I got the Call Screen options but did not receive any calls to test out out. Here is the rub... Google Phone went to sleep last night with everything set. This morning it had reverted to the standard set of options. Visual Voicemail, (no Transcriptions), and no Call Screen.
Click to expand...
Click to collapse
I'm noticing a consistency on the app resetting itself.
I would love to see if there was a way to keep the OOS Native call recording and get this as well...... any ideas?
jetfire245 said:
I'm noticing a consistency on the app resetting itself.
Click to expand...
Click to collapse
Can't seem to get it to re-enable after this morning either.
It's very obvious we need dedicated development for this project to work. Perhaps making a bounty for the successful and repeatable modification to get call screening and maybe voicemail.
We can just make a Tasker profile guys. I made one back in the day to constantly keep material design 2 enabled. I'm working on one rn that will Auto enable dark mode for the Google apps at sundown and whatever other phenotypes or bugle changes i need to make. Including VVM and CS
If you ever managed to solve problems , please update the post. Somehow , I did the exact same stuff before I saw your post and have exact same problems , low call screen volume , Voicemail can't activate
So I have had success using Preference Manger from the Google Play Store to kick in transcription visual voicemail. The settings stuck overnight too! I can't get Call Screen working yet though.
In Preference Manger I scrolled I enabled system apps from the three dot menu.
I scrolled down to phone (searching crashed the app)
I side scrolled to dialer.phenotype.xml
I searched "transcription" in the xml file
I turned every one from false to true
I force stopped the phone app
It works.
stealth658 said:
I'm trying to get Pixel Call Screening and Native Visual Voicemail working on my GM1917. I'm on T-Mobile US, and my phone is rooted with Magisk on OOS 9.5.8. From the settings I changed, it seems like the Call Screening should work in the US and Canada, and maybe elsewhere also. And it seems like VVM should work on Verizon, T-Mobile, AT&T, Tracfone, Freedom (CA), O2 (UK), and Swisscom.
So far, I've gotten the Voicemail tab to show up in the Google Phone app, but VVM won't activate on T-Mobile. And I've gotten Call Screening enabled with working transcription, but the Google Assistant voice is too quiet for the caller to hear. I'm hoping someone here can help me get these things working fully.
Requirements:
Root is necessary to make Google Phone a system app and to make the required mods to the XML file
Either the Pix3lify Magisk module, the Google Dialer Framework module (much lighter), or a modded Google Phone APK to install Google Phone
App Systemizer Magisk module
A root file explorer (I'm using Root Explorer)
Instructions:
Install Google Phone (I used Google Phone 34.0.253691707 from APKMirror)
Use App Systemizer Magisk module and Terminal Emulator to move Google Phone app to /system/priv-app/
Reboot Phone (You may also have to freeze/disable the OOS native phone app)
Force Stop Google Phone app
Using a root file explorer, unzip and copy attached dialer_phenotype_flags.xml to /data/data/com.google.android/dialer/shared_prefs/ (You may have to set permissions to 0660 rw-rw----).
Reboot your device (I've found that if you wait too long between Force Stopping, replacing the file, and rebooting, the Google Phone app will restart and override the changes)
When you re-open Google Phone app, you should have Call Screen in the menu ( It won't show up unless you enable the Microphone permission) and the Voicemail tab accessible (You may have to delete the Carrier VVM app for it to show up)
Screenshots of Call Screen and VVM tab on OP7Pro
Click to expand...
Click to collapse
What flags did you switch from false to true to enable call screen?
ozfive said:
What flags did you switch from false to true to enable call screen?
Click to expand...
Click to collapse
Anything with speakeasy, speak_easy, call_screen. For visual voicemail, change anything with vvm and voicemail (except a few flags that end in disable — they should be false). There are also a bunch of Duo related flags that I changed to integrate Duo more in the dialer.
I can give you a full list tonight when I’m home
A full list with be great!
I got Call Screen working and working transcriptions in visual voicemail as well.
The Call Screen assistant voice is too quiet to be useful at this time. Hopefully there will be a solution found for this too!
jetfire245 said:
Attempted everything included in the tutorial but I used dialer framework. Sadly, I could not get anything to appear. What was used in the guide?
Edit: I noticed the modified xml is about 28kb. Before I replace the xml in my root, it's about 14kb. I'll replace the file, and restart, only to see, I have a 14kb file again. Is this the issue?
Click to expand...
Click to collapse
ozfive said:
A full list with be great!
I got Call Screen working and working transcriptions in visual voicemail as well.
The Call Screen assistant voice is too quiet to be useful at this time. Hopefully there will be a solution found for this too!
Click to expand...
Click to collapse
Which carrier and phone model do you have?
I am using a t-mo converted to international
ozfive said:
I am using a t-mo converted to international
Click to expand...
Click to collapse
I'm not sure why my international on T-Mobile stays stuck on activating for VVM. Are you using Pix3lify or any other relevant mods?
I am using Google dialer framework vs pixelfy, maybe that is the issue?
Related
I use Google Voice as my main phone number and I never had a problem just installing the Google app and having my calls routed through it, but on this phone a get a "Call Not Sent" error. I searched and it seems this is an issue with other Huawei phones, but didn't find any solution. Any ideas?
Can anyone test to confirm it's an issue? Would flashing a Gapps package help?
maybe, cuz flashing gapps package would make them system apps. just make sure u have enough space left on your system partition...
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
I deleted some system apps and installed open gapps mini. No luck, still getting the same error. Is it possible to replace the phone apk (not dialer), or is that too tied to the hardware?
I've been using the phone for a couple days now, and I'd hate to give it for such a small (but fundamental) bug...
I found a solution: make Google voice a system app
adriangb said:
I found a solution: make Google voice a system app
Click to expand...
Click to collapse
please explain
i still can't figure it out
Actually it may have been a fluke... I placed one single call and confirmed with the other party it was my Google voice number. Now it isn't working again.
I think I may have fixed it. I copied in some telecom files from AOSP. So far I'm like 5 calls and 2 reboots in and it's holding. I'm going to try to update to the new L-29 OTA, root and then follow the same process. If it works, I'll post the ROM. If it's like what I'm on right now, it's a very nice mix of EMUI and AOSP since most of the Huawei stuff is gone, except some of the handy features, and all the Google stuff is loaded and working.
maybe you could also include a howto, which files to add where so that others may cook up their own emui/aosp mix
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
To be honest, I'm really not 100% sure, I kind of brute forced through the testing. What I do know: replacing a couple telecom framework and binaries from the 6P factory image (figured might as well use this), and installing Google voice as a system app, I have gotten it to work every time (for me) as long as it is set to prompt for every call. If set to "use Google voice for all calls", it breaks. My guess is it's a timing issue (emui telecom not giving Google voice the time it needs to make the connection).
I'll attach the ZIP file with all of the telecom components I used (NOTE THAT USING PRIV-APP COMPONENTS -IE TELECOM.APK, SEEMS TO CAUSE A BOOTLOOP).
Also, here is a link to my TWRP backup of my current system. It is 152 with a full Gapps package, Google voice as a system app and the telecom components Frankensteined in. Hopefully it will work on your devices, but just in case it bricks it I won't be giving out my address, least I get picketed
https://drive.google.com/a/adriangb.com/file/d/0B8hgJSh5NMsLVGpicmEwdWpDb00/view?usp=docslist_api
Still no real solution. The ask every time trick works without having to do anything with making Google Voice a system app and it only works 90% of the time.
Can anyone else confirm this issue? I'm discussing it with the vendor I purchased from, they're claiming it works perfectly
adriangb said:
I use Google Voice as my main phone number and I never had a problem just installing the Google app and having my calls routed through it, but on this phone a get a "Call Not Sent" error. I searched and it seems this is an issue with other Huawei phones, but didn't find any solution. Any ideas?
Click to expand...
Click to collapse
This is an old post with little activity, and yet I have this same problem. I have tried all the app setting and permissions, the battery setting etc, but the Mate 8 seems incompatible with Google Voice. The app install fine, sets up normally, and incoming calls to my Google Voice number work. It is just dialing out. All dials get the message "call not sent" and the dialer screen returns to befor the call was placed. The log also does not show an attempted call. I have tried alternative dialers from the play store, but none work. Has anyone solved this, or are there just very few people using Google Voice with this particular phone.
I've been having this same issue and have had the best results just setting it to "ask every time", no other tricks needed.
joburgslim said:
This is an old post with little activity, and yet I have this same problem. I have tried all the app setting and permissions, the battery setting etc, but the Mate 8 seems incompatible with Google Voice. The app install fine, sets up normally, and incoming calls to my Google Voice number work. It is just dialing out. All dials get the message "call not sent" and the dialer screen returns to befor the call was placed. The log also does not show an attempted call. I have tried alternative dialers from the play store, but none work. Has anyone solved this, or are there just very few people using Google Voice with this particular phone.
Click to expand...
Click to collapse
This is broken on the mate 9 as well
Anything on this? i just got a mate 8 and am having the same damned issue.
Has anyone been able to successfully get the Google Nexus dialer working on their phone? Google said they have blocked sideloading of the app but made it available to download from the play store. I have a HTC m8 on marshmallow and was able to see and download the dialer from the store on the day Google announced it. The dialer functions work for the most part until I place a call, upon which it will place the call with the HTC phone app. (Dial number on Google app, hit call, goes to HTC and places call). I gave the Google dialer all permissions it needed on the phone and was able to get it to handle to calls. The problem is that there are two active call buttons in the notification bar. One for htcs app and one for the Google one. I am unable to use the speaker phone on the Google app where it is working perfectly on the HTC one as it should. Finally, and the biggest problem by far, is I can't get the phone to ring. I set everything as loud as possible in the Google app, htc app, and in settings and nothing will ring. I've tried everything on vibrate too but the same issue occurs. I would try to uninstall the app and reinstall it from the store but when I went to search for it, it is no longer available for my device. I didn't side load the app and was able to download it from the store on the first day. Idk of Google pulled it from the store for bug fixing but if anyone was able to get the app working on a non Nexus marshmallow phone let me know. I would love to use this app fully!
I was able to get Google Call Screening working. However, the Google Assistant voice is really low on the other end. Not sure if there is a way to increase it, maybe there is a tweak in outgoing audio policy that can help.
For those of you wanting to give it a go, this was on latest rooted International ROM. It should work on AOSP based ROMS, but I haven't tested it . It will require 2 magisk modules: Google Dialer Framework, and App Systemizer.
1. Install the 2 modules above, reboot as necessary.
2. Clear Play Store data, then search for Google Phone. The Google Dialer Framework module should allow you to see and install it.
3. Download a terminal emulator of your choice. You will need it to run the systemize command the module created. You will use this to convert the Phone apk to /system/priv-app. Reboot after this process is done.
4. Go to app settings and set permissions on the Google Phone apk. Also set it as the default Dialer app. I recommend disabling the stock phone app to avoid confusion or freezing it using Titanium Backup.
5. Run the Google Phone app. This step is necessary to generate some XML files, one of which you will need to edit.
6. Using a root file browser of your choice (Solid Explorer for me), navigate to /data/data/com.google.android.dialer/shared_prefs. You should see a file named dialer_phenotype_flags.xml. Open this file in a text editor.
7. To enable call Screening, we need to change some booleans to true. You can do a text search for "speak_easy" to find the ones we are looking for. While you are here, you can also change the flags for "vvm" and "transcription" to enable Visual Voice Mail and Voicemail Transcription services. Remember to save your changes, and reboot.
8. Open your Google Phone app. You should see call screen and Voicemail options in settings if all went well. Enable Call Screen (need to be on wifi to enable, but not required for the service) and test it out. The Assistant voice is rather low, but hopefully if enough people get on board someone smarter than I can help find a solution.
Hope this helps anyone looking to try this out and gets the community interested in resolving the low volume.
LvDisturbed1 said:
I was able to get Google Call Screening working.......
7. To enable call Screening, we need to change some booleans to true. You can do a text search for "speak_easy" to find the ones we are looking for. While you are here, you can also change the flags for "vvm" and "transcription" to enable Visual Voice Mail and Voicemail Transcription services. Remember to save your changes, and reboot.
Click to expand...
Click to collapse
Which booleans do we need to change? There are quite a few.
Only works on Google phone v40 though anything above will break call screening
mjb337 said:
Only works on Google phone v40 though anything above will break call screening
Click to expand...
Click to collapse
Okay - well I did the magisk and systemize of the google phone dialer and I have v44.
If I am to go start this all over again and install v40 of the google phone dialer and framework, do I need to anything special to uninstall the v44 dialer?
---------- Post added at 05:51 PM ---------- Previous post was at 05:15 PM ----------
bodaciousbob said:
Okay - well I did the magisk and systemize of the google phone dialer and I have v44.
If I am to go start this all over again and install v40 of the google phone dialer and framework, do I need to anything special to uninstall the v44 dialer?
Click to expand...
Click to collapse
Desystemized the app, uninstalled it.
Installed V40.0.274600228 and systemized it. Changed all the "speak_easy" flags I could find to "true". Rebooted the phone several times, turned on and off wi-fi - no call screen option.
EDIT: Enabled all permissions for the phone app - AHA call screen is an option!!!
Enabled it, and tested it - and the phone with call screen doesnt ring. It goes to voicemail, and then I get a missed call notification? Forgot to set phone as the default phone app. Did this and now I HAVE CALL SCREEN AGAIN!
Works! I always passed on Google dialer never worked with Verizon voicemail on non pixels. Thanks!
Make sure to disable play store updates for Phone or you will have to start all over, even having to clear launcher data. It may take a while for Phone to show as an available update. You can detach the app as well. You may also need the BusyBox module to get systemize to work.
This version of the dialer seems to be the latest that works. If you don't want to download from here, look carefully on apk mirror for the one referenced in the previous post.
https://www.dropbox.com/s/drysa6iu1...PI24(arm64-v8a)(nodpi)_apkmirror.com.apk?dl=1
This I think
https://www.apkmirror.com/apk/googl...40-0-274600228-android-apk-download/download/
Anyone found a solution to the volume problem. I've been experiencing this for multiple pixel phones now. I'm not using a pixel 6 and the problem is still there. The caller on the other end can't hear the very low volume of the assistant.
Hi!
I can't believe how much time I wasted because Google messed something up with voice typing. I suddenly had a new version with a blue microphone circle instead of a mint green one and ever since the voice recognition is so bad it's unusable.
I reverted back to an 11. version and it works again, but Google keeps updating this app despite me having auto-updates disabled everywhere.
How can I prevent this auto-updating.
I have tried creating the directories com.google.android.googlequicksearchbox-1.apk and -2.apk in the data directory, but that hasn't helped.
I have xposed of course. Any other ideas? Titanium Backup isn't any help, for some reason it can't restore an older version and doesn't even report any errors...
If you are rooted, just flash the Magisk module : Detach , it will automatically remove all listed app from auto update
Unfortunately that, too, didn't work. I installed Detach and uncommented Google App and a day later it had auto-updated again.
It's really annoying, because Titanium Backup apparently cannot restore an older version of Google App. So I have to uninstall it first. But after a restore I then have to go into settings, activate Google voice keyboard, grant the app permission to the mic and set the rights in Xprivacy. On a "real" OS I could just write a script for all that. Grrr.
Hello everyone, i line in the UK and had call screening working and then one day it decided to deactivate and now it refuses to activate again. I can't figure out how to fix it or get it to activate. I'm in a supported country on a supported device. I am rooted but didn't think that would have anything to do with it but I used magisk to hide your from the phone app as well. Any tips would be grateful.
This happened to me once...
What I did was I force stopped, clear cache, & clear data.
If that didn't help, I uninstall updates. Then I updated from the Play Store. But when I did this, it was on Android 11 and stock phone app didn't initially have call screener. I imagine the Pixel 7's have it on the stock phone app, but doing this still might reset things and re-activate it.
Note: If it wasn't immediately available -- it didn't show the option of "Spam and Call Screen" -- it did take a while for it to somehow activate. Within the hour it all of a sudden popped up an alert when I opened the phone app spouting the feature. It might be that it takes activating through Google or your carrier somehow before it's enabled and displayed on the app. Then, again, this was on my Pixel 5 A11, so Call Screen isn't natively available off the bat -- so I imagine it would show up right away after uninstall updates and/or updating it from the Play Store.
If that isn't enough, you might consider clearing the cache & data from Play Services and Google Play Framework maybe....
Good luck and hope this helps...