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?
I recently moved to rooted android 11 (pixel 4A) from jailbroken iOS so I'm very new to Android.
I've read through googling that disabling RECEIVE_BOOT_COMPLETED permissions will stop the apps from autostarting but whilst this stops a good proportion of apps, a number of apps such as Termux are still getting through. Some apps don't even have RECEIVE_BOOT_COMPLETED but they're still able to start. I have disabled app syncing on my device. I've tried multiple apps such as Task Manager and SD maid and this small proportion of apps are still autostarting.
Does anyone have any clues as to how to fix it?
If an app doesn't listen to BOOT_COMPLETED broadcast then it doesn't care about this event.
jwoegerbauer said:
If an app doesn't listen to BOOT_COMPLETED broadcast then it doesn't care about this event.
Click to expand...
Click to collapse
Hmm, so maybe there's some kind of service running after the boot that starts it? Or some kind of delayed boot? I thought it might have been due to sync reopening apps or something but when I disabled that it still kept showing up. And those apps aren't listed in the Services part of the Developer Services either...
ok I figured it out, my pixel remembers what apps I have open before a reboot and reloads them afterwards. so remove all apps from the memory before rebooting and nothing will be remembered
Hi, I'm planning to buy the Motorola Edge S (not G100) as it is cheaper.
Previously, I owned a Moto P30 (the phone that looks like the iPhone X) and China ROMs even on other OEMs have this weird bug where you won't receive any notifications say, in WhatsApp unless you open the app itself (already enabled app in background/disabled optimizations etc..).
Is this "bug" still persists in latest Moto phones using China ROM?
Hope someone can confirm. Thanks.
I personally bought it from AliExpress and the vendor already unlocked the bootloader and flashed the global ron with Google Play. My edge S with the global rom from the vendor has no problem with the notifications. Depending where you buy it you can have it with the global rom already instead of needing to do it yourself.
Keep in mind you wont pass safetynet, you may need to install Magisk for it
Thanks. I don't intend on flashing it to Global ROM. There is no issue with Motorola global ROMs as notification is working fine. I just need some confirmation if China ROM still has this weird bug. This is true for any Android phone without GMS (a lot of complaints in Huawei forums with this problem).
There should be some battery optimizing setting behind. If you cannot set it via whatsapp & phone setting, you will need to kill such background app by adb
Disabling battery optimization and putting the app with "unrestricted data usage" didn't help (on my previous Moto P30 running China ROM). Same case as the Lenovo z6 Pro based on China ROM. Android will kill the app (ex. WhatsApp) regardless whether you put it on whitelist.
But both are old devices running an old version of Android. Anyway, I would still buy the Motorola Edge S (Pioneer Edition). An irritating bug (for devices without GMS) which Android developers should have squashed a long time ago.
Settings Edge S with Chinese firmware.
1.Settings - System - Advanced. Google Play Services - On.
2. Download, unpack, and install Google Services.
3. Configuring notifications and application operation.
a) System-Apps & notifications-Special app access-Battery optimization.
For the necessary applications and notifications: Enable - Don’t optimize
b) Launch the application - Device shield.
Background running – Allow app running in background.
Auto start apps - Enable the applications you need.
My order is still on the way. I'll try that once I received my purchase. Thanks.
So I got my phone already setup with all Google-related apps installed.
I configured the settings by whitelisting Google and all apps important to me like WhatsApp.
In Device Shield, I ensured my apps are whitelisted to allow background processing at all times and put them in auto start.
Adding to that, in battery settings, I put them in Do Not Optimize. I also ensured to allow background data.
For now, everything works PERFECTLY. Notifications arrive on time and I don't even miss any WhatsApp calls. It is either that OR my I'm still using my phone too much (not even 12 hours since I got it).
ijuanp03 said:
So I got my phone already setup with all Google-related apps installed.
I configured the settings by whitelisting Google and all apps important to me like WhatsApp.
In Device Shield, I ensured my apps are whitelisted to allow background processing at all times and put them in auto start.
Adding to that, in battery settings, I put them in Do Not Optimize. I also ensured to allow background data.
For now, everything works PERFECTLY. Notifications arrive on time and I don't even miss any WhatsApp calls. It is either that OR my I'm still using my phone too much (not even 12 hours since I got it).
Click to expand...
Click to collapse
Hi, I got the same problem. WhatsApp calls don't work properly. If any one knows how to remove/kill the background app procedure through adb, please share the same.
When I got the phone there wasn't all the apps on it. Now if I boot and clear the cache, re mount and reboot. It still has all the apps like bixby etc. even though during the setup I skip all that. WHat can I do. This is a US ATT locked phone which I could never send a mms or sms over 1mb.
I don't care if it is a ATT image. I don't need all the junk apps, but the advance messaging needs to work.
Quick Debloat ATT (SM-711U1)
No for non-rooted/stock/bootlocked phones This is my debloat list, simply copy paste into ADB. I still run some Google and Samsung services but this takes out all the carrier, Microsoft, Facebook and Samsung garbage that they lock into the...
forum.xda-developers.com
I'm running crDroid 8 on a Poco X3 Pro, with NikGapps Omni.
[The issue]
Recently my phone's battery has been draining very quickly. I realized that a com.google.android.gms process is constantly using a lot of CPU to spam hundreds of log messages per second.
Apparently this happens because crDroid is pretending to be a Pixel Phone, so Google pushes OTA updates for Pixels for its services, but the updates fail on the X3 Pro and a crashloop occurs.
I found a bunch of threads about this issue going back to longer than a year, but couldn't find any solution, besides disabling some components of Google Play Services which break syncing of Google Apps.
[Questions]
Is there any decent solution to this issue (that doesn't break sync) and stops the issue from reoccuring?
I tried to blacklist a bunch of domains where the OTA updates are supposedly downloaded from, then clear Google Play Services data and cache, but it wasn't enough: logs are still getting spammed.
Would it work permanently, if I re-flashed crDroid and blacklisted those domains before any update happens?
Why is crDroid pretending to be a Pixel Phone, if it periodically results in this issue for every user (at least the ones who use gapps)?
Would you recommend switching to a different ROM that doesn't do this? I'm open to suggestions.
peoro said:
I'm running crDroid 8 on a Poco X3 Pro, with NikGapps Omni.
[The issue]
Recently my phone's battery has been draining very quickly. I realized that a com.google.android.gms process is constantly using a lot of CPU to spam hundreds of log messages per second.
Apparently this happens because crDroid is pretending to be a Pixel Phone, so Google pushes OTA updates for Pixels for its services, but the updates fail on the X3 Pro and a crashloop occurs.
I found a bunch of threads about this issue going back to longer than a year, but couldn't find any solution, besides disabling some components of Google Play Services which break syncing of Google Apps.
[Questions]
Is there any decent solution to this issue (that doesn't break sync) and stops the issue from reoccuring?
I tried to blacklist a bunch of domains where the OTA updates are supposedly downloaded from, then clear Google Play Services data and cache, but it wasn't enough: logs are still getting spammed.
Would it work permanently, if I re-flashed crDroid and blacklisted those domains before any update happens?
Why is crDroid pretending to be a Pixel Phone, if it periodically results in this issue for every user (at least the ones who use gapps)?
Would you recommend switching to a different ROM that doesn't do this? I'm open to suggestions.
Click to expand...
Click to collapse
Magiskmodule Gms dozen
Told devs that Pixel spoofing will come and bite them in the a$$.
Use Arrow OS.
Tomo123 said:
Told devs that Pixel spoofing will come and bite them in the a$$.
Use Arrow OS.
Click to expand...
Click to collapse
Dev should remove pixel spoof from the rom and if someone really want it then Pixelify is already there
The solution with a root.
Solution №1
Add file-script GmsOff.sh at data/adb/service.d (its magisk folder to autostart scripts)
Write in file:
sleep 130
su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService
In the permissions of the script-file, put 3 checkboxes for execution.
Install app Terminal Shortcut Pro. you can create link there, and you must use it to turn service ON before you wanna restart or shutdown phone.
Write at link:
su -c pm enable com.google.android.gms/.chimera.GmsIntentOperationService
You also can just use terminal, if you dont like Shortcut program.
If you not turn service ON again BEFORE you reboot, there will be problems with receiving notifications AFTER your phone start.
Solution №2
Install Magisk Universal GMS Doze module (I use 1.8.8)
Create file 123.sh at data/adb/service.d
Write there:
sleep 130
cd /data/data ; su -c "find . -type f -name '*gms*' -delete"
In the permissions of the script-file, put 3 checkboxes for execution.
Also there is an option to create a script that will launch the service immediately after the system start, but before Google services fully load, and then disable it after a while.
It turned out like this for me, but your system startup time may be different, you need to select "sleep" values according to the situation.
sleep 20
su -c pm enable com.google.android.gms/.chimera.GmsIntentOperationService
sleep 80
su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService
For the future - install only ROMs without "Pixel Spoofing for unlimited Photos storage"
Check my Reddit Post about this problem.
There will be some enhancement to solutions.