yashsingh1/xdaforums huggingface dataset:
[Android General] meffles:
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
[Android General] ih8legal:
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.
[Android General] meffles:
I checked and it looks fine to me, am I missing something?:

https://imgur.com/a/DCZYgm9
[Android General] ih8legal:
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)
[Android General] meffles:
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.
[Android General] ih8legal:
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.
[Android General] meffles:
I got the attached..
[Android General] ih8legal:
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.
[Android General] meffles:
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 :)
[Android General] meffles:
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?
[Android General] meffles:
It's not looking like the option is going to show..
[Android General] ih8legal:
I think 3 probably needs to be on.
[Android General] meffles:
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?
[Android General] ih8legal:
Yep, I don't think this would bypass a region lock. Although you might try changing some of the Google dialer shared prefs with the PrefEdit app. Here is a link to point you in the right direction, which flags. Don't know if it will work though, but good luck.

"Enable Google Pixel 3's Call Screening on Pixel 2 and Pixel [Root]" https://www.xda-developers.com/enable-pixel-3-call-screening-pixel-2-pixel/
[Android General] meffles:
After about half and hour it's still not there. Have disabled 3 again. Thanks for the guide although I'm fairly sure Google have changed all that since. I'll have a look today.
[Android General] ih8legal:
Changing this flag to true might work, in conjunction with the guide on this thread.
[Android General] meffles:
I used to have those options available to me on the old version of dialer but on the modern versions I only see the attached.
[Android General] ih8legal:
Hmmm, that's odd, but maybe there's a server side thing that's disabled. I don't have any more ideas. Sorry it didn't work.
[Android General] meffles:
No problem, appreciate the help.
[Android General] stmims1124:
After 6-12 months trying to get call screening working, this is the only thing that has worked immediately... And continued to work as well. So THANK YOU!

Question for you- Assuming you had RCS messaging working prior, did you lose it? I think it's possible that the Play Services wipe could be related, in which I'll eventually get the option back, but if that's not the reason, then it was a change in the props. I guess I'll find out one way or another.

For reference, I have a SIM unlocked 7 Pro GM1915 converted to the international firmware... Then obviously bootlocker unlocked and rooted. Open Beta 17 firmware (Android 10). Using Google's Android Messages because it uses the proper implementation of RCS.

EDIT: RCS did come back afterwards... Must have been the wipe off play services. So please disregard the question.
[Android General] wolfu11:
it's funny i have tried this with multiple updates and didn't even notice but following the steps and then after i removed 3,8,and 9 i let it sit of course nothing happened but when i called up google assistant on my one plus 8 pro on open beta 1 this popped up.

So i guess it semi thinks it's the pixel 4xl lmao
[Android General] ih8legal:
Yeah, I actually ended up disabling all the changes, because of this. Google assistant doesn't work properly. There are ways to make it work as it should, but they come with their own issues. I've been watching to see if anyone comes up with a solution.
[Android General] wolfu11:
The assistant is actually working exactly like it should for me. I also found that on open beta 1 using the 38-40 dialers still give call screen but I had to do a work around to systemize them.
[Android General] meffles:
I'm now on a different rom and willing to try again.. I'd I simulate a different device, would that likely mess with things like Google pay?
[Android General] stmims1124:
I did this mod AFTER I had already set up Google Pay, and because I had to wipe Google Play Services, it also wipes out everything in Google Pay as well. It's not the end of the world because Magisk Hide is a thing, but I had to re-add my bank cards and that was a bit of a hassle...having to call into my bank to reverify everything and wait for them to finalize it on their end (small regional bank), and I still had issues, though I'm not 100% certain it was related.

It definitely messed up how Google Assistant displays on screen, making it certainly look super broken, I gather because of the different display specs/dimensions between my OnePlus 7 Pro and a Pixel 4XL, but technically Assistant did still work...though it was best just through voice interaction only.
[Android General] meffles:
Gave it a try, it borked my assistant like you said (made it incredibly slow and didnt look quite right) and call screening did not appear. I did set all the speakeasy parameters to 'true' but I can only assume Google have made some adjustments somewhere and this might not be enough for me to get it working in the UK.

Interestingly, I didnt get the dim screen issue like before when simulating all of the options in props. I'm using Carbon rom.
[Android General] mintyur:
Can this be done in Oneplus 7 pro 5G GM1925?

I have follow your instruction but it still not work

Is it because of my impatient or my phone model?
[Android General] ih8legal:
It should work regardless of phone model, as it is is simulating a pixel device. Should start working soon after you clear the phone app's data and open it again if you followed all the steps.
[Android General] mintyur:
I have follow all your step but still not work

Simulate to pixel 4XL and enable all other (except the display.id like you said), erase data. even when I use preferance manager to edit the phone app it still not work. Please help!
[Android General] GuyInDogSuit:
It WORKED!!

[MENTION=4532159]ih8legal[/MENTION], you've done it, mah boi.

I followed your guide to the letter, using the PrefEdit app to make the changes instead, as the Call Screening zip wouldn't flash (along with some more details from GadgetHacks' guide here, which oddly doesn't link properly in your OP), rebooted again once I was finally finished, and force closed the Phone app after everything I did seemed to not work, and opened it up immediately after, discovering that the "Spam & Call Screen" option was now there! Voicemail once again can be listened to within the app without calling, but transcription isn't working (yet. I may have to enable it on my T-Mobile account but it costs extra, and I dunno if I really need it that badly). I might just to test it out, for a month. Maybe.

Thanks so much!
[Android General] ih8legal:
I'm glad you got it working. I'm wondering if your Google assistant works properly, if the UI is kind of broken. That's what happened to mine.
[Android General] GuyInDogSuit:
I've read about that, but I'm not sure which *part* of the Assistant UI is broken for you guys. Mine looks fine, at least in the voice prompt and Discover feed.
[Android General] ih8legal:
What happened to mine, it changed to the new Google assistant found on the newer pixel devices, but was missing part of the UI
[Android General] ih8legal:
Is there any chance you are in a country that Google has not enabled call screening for?
[Android General] GuyInDogSuit:
I'm in the USA. Fairly certain it's enabled here. I know it's not even working in Canada and parts of Europe (if at all, really).
[Android General] meffles:
Certainly not officially. When it was first released I remember editing the config to bypass locale checks, but that doesn't seem to be making any difference here now.
[Android General] warrencoakley:
Where do I go or select from here?

The call screening zip installs but doesn't show in Magisk.
[Android General] warrencoakley:
Ok since I'm on a Pixel 2 XL some of that doesn't apply but how do I enable device simulation?

I'd say switching it to the Google Pixel 4 will do it.
[Android General] warrencoakley:
Ok I'm getting there.

I enabled in props what you asked, but my phone seems a little laggy.

So I've changed the fingerprint to Google Pixel 4 XL like you said.

Cleared phone data and rebooted and nothing.

Any ideas what im doing wrong or causing the lag?
[Android General] warrencoakley:
Nothing
[Android General] ih8legal:
In thinking since you are already on a pixel device, it might cause some issues spoofing to a different pixel. Doesn't call screening come included with the pixel 2? I remember having it on my pixel 1.
[Android General] warrencoakley:
I had it before on my Pixel 2 XL with the older method and Magisk module using an older phone dialler apk but not now. It's region specific i think. I'm in Ireland and don't have it as standard.

I had to revert back as it was causing apps to stop and lag.

So no this is not for ALL devices as stated.

Anyone else on a Pixel phone and have successfully gotten it to work?
[Android General] GuyInDogSuit:
The UI on my Google Assistant may not appear to be broken, but certain call-up features, like the hotword and the "swipe inward from bottom left/right corner" gestures do not work.
[Android General] ih8legal:
This was a thing that led me to eventually have to disable this mod completely. But I have it working now. Google Phone call screening, and the new assistant.

Found the necessary files and instructions on a telegram chat

https://t.me/googlepixel4xml/120

Some of this I skipped, namely the flashing anothwr module to replace your props file with the pixel 4 one. It is unnecessary if you were already doing that with the Magisk hide props config module.
[Android General] warrencoakley:
It doesn't work on stock ROM. Causes lagging and overheating

---------- Post added at 04:31 PM ---------- Previous post was at 04:26 PM ----------

How did you get the call screening to work?
[Android General] GuyInDogSuit:
Directions unclear, got head stuck in dryer.
[Android General] ih8legal:
Same as before, call screening worked for me with the original instructions. Google phone needs to be a system app, and your phone needs have pixel build.prop.
[Android General] ih8legal:
Just install the invisible assistant fix v2 as a Magisk module. It downloads and installs a prefs file that enables Google assistant to work properly
[Android General] warrencoakley:
But mine is a pixel, I've tried your method bon stock and it doesn't work

---------- Post added at 03:04 PM ---------- Previous post was at 02:58 PM ----------

Again doesn't seem to work on a Pixel 2 XL on stock ROM
[Android General] ih8legal:
Space
[Android General] ih8legal:
Call screening is included with pixel devices AFAIK. For some reason it isn't for you, maybe you are in a region where it is unavailable. This method will not enable it if that is the case.
[Android General] warrencoakley:
It did work before on my Pixel with an old version of dialer and the call screening module so it's not that. It's just this method your are using is only for custom ROMs and cannot be implemented or work on stock Android
[Android General] ih8legal:
I don't remember if the original call screening module enabled the locale bypass flag. Can you use the PrefEdit app to go into Google phone and into dialer phenotype flags xml, and see if it is set to true.
[Android General] warrencoakley:
Yep done that. Now what else should I do?
[Android General] warrencoakley:
This is all I'm getting.
[Android General] ih8legal:
Force close the app a few times. The locale bypass might not work anymore.
[Android General] warrencoakley:
Yep closed it 5 times and rebooted and nothing. The Magisk module for call screening does not install on canary build.

Is there anything else I should be doing?
[Android General] ih8legal:
The call screening module is unnecessary, it just changes same flags to true in the dialer prefs xml. If you can find the original XDA article about the call screening module I think it mentioned exactly which flags those were, and then you can manually chance them with Prefedit.
[Android General] warrencoakley:
Read that, anything with speak easy in them which I did already and still no dice
[Android General] GuyInDogSuit:
Warren, try this. Check to make sure your device fingerprint and such are back to stock. Then flash this Magisk module (attached) and reboot. What this does is pretty much the same thing as the Magisk Hide Props settings (spoofs your phone model as a Pixel 4 XL), but it's systemless and can be toggled if needed. Force stop the Phone app and Google Play Services too for good measure, then wait a few minutes and open the Phone app again. I found it from clicking the "@pixelprops" link from that Telegram group ih8legal shared earlier. It worked for me, so I think it might for you. Let me know if it does. I know being in Ireland (which is not one of the supported call screening countries) is an issue, but there's still hope.
[Android General] Revancha:
Has anyone gotten this working on a OnePlus 8 Pro? Any time I try to enable the props from a Pixel 4 XL I lose control of my screen brightness and the call screen option still doesn't come up in the dialer app. I've tried it with MagiskHide Props Config as well as the Coral and Pixel 4 XL modules - same results. My friend got it working on his OnePlus 7t no problem though. We're both on stock OxygenOS 10.
[Android General] warrencoakley:
I have a MagiskHide config Props module already installed for GPay etc. Does that matter? Do I need to remove. it and put the one you mentioned attached on instead? As i said it did work before the old way with the call screening module but they must of patched that. I know considering their EU head quarters are based in Dublin, you would think we would be on the list of any new features rolled out.

I'll install this and let you know how I get on. I'll report back.
[Android General] warrencoakley:
Nope still nothing. Any other ideas?
[Android General] freddienuxx:
Hey guys when receiving call the person says they can't hear google call screen. Is there a fix? Thx in advance
[Android General] Nosferatu.:
Has anyone gotten it to work on either Android 11 or on a OnePlus 8 Pro? Haven't rooted the phone just yet but if Call Screening can be enabled I'm going to root it.
[Android General] TheUndertaker21:
tried this on sammy phone

was unlucky lol because the app doesn't show up some prefs lol
[Android General] warrencoakley:
Must of tried a half a dozen suggestions but nothing works on stock to spoof the region. Changing prefs don't work however it works to get Assistant 2.0 Editing props don't work or changing from false to true etc.
[Android General] TheUndertaker21:
I got this to activate on gsi but the assistant isn't working

It's just echo of my own voice

It doesn't read it back to the caller

Can anyone help ?

Thanks
[Android General] Fireflykid:
Activated but no assistant voice (for caller) or transcription (for me).

Oneplus 6t OOS 10.3.6

Dialer version 38.0.265137157-publicbeta

Google play services version 20.39.15 (120400-335085812)

(It's worth noting that it will activate on any dialer version)

Spoofing pixel 4 XL (everything but display.id) with props

If anyone could provide insight into why it isn't working and how it could be fixed I would greatly appreciate it.

Also, the phone is systemized to priv-app. I also flashed google-call-screen v 2.0 to get all of the flags set up right.

Emulating the pixel does seem to help, but could it be causing the inability to hear?
[Android General] ih8legal:
That dialer version is really out of date. Just checked mine and its on 56. Maybe updating will help.
[Android General] ih8legal:
You mean the assistant in call? Is your phone app updated?
[Android General] Fireflykid:
I tried the most recent dialer, and I can enable them, but the caller can't hear assistant and I get no transcript no matter the version.
[Android General] warrencoakley:
Your lucky mine is spoofed to 4a and i can't get it to show up at all on stock on the latest dialler. No idea why
[Android General] Fireflykid:
You still need the flags If you don't have them
[Android General] warrencoakley:
The magisk modules don't work on stock in canary build with Android 11.

I've manually changed them and nothing
[Android General] Fireflykid:
There's also some you can find under "screen" (these are all "easy")
[Android General] warrencoakley:
Yep no dice
[Android General] TheUndertaker21:
Yeah same here

Any fix?
[Android General] Fireflykid:
Not that I have found so far, but I'll let you know if I figure it out!
[Android General] fuadhdmini:
I believe it has something to do with voLTE? Are your calls on voLTE or still on 3g when receiving calls?
[Android General] Fireflykid:
voLTE, oneplus6t doesn't have cdma so no 3g on verizon
[Android General] GnyanadBhatt:
lets try this

i hope it works well on my 7 pro and s20 ultra .. thanks man .. will start using it soon enough
[Android General] fuadhdmini:
Thus . Any luck to get the sound?
[Android General] Fireflykid:
Not yet, but it sounds like it potentially can break a lot of google features. I'm still trying to find an answer.
[Android General] GuyInDogSuit:
Yeah, not just potentially, but it actually WILL. I mentioned the bit with flashing kernels/zips meant specifically for your device, and how the script will abort if it doesn't detect the correct one. That's because of the device footprints and props being changed to Pixel devices. I've also had issues with Oxygen Updater not working, either. I'd assume the same with the built-in system updater as well. I've had to change the props abd whatnot back to the 7T, and install those things, then redo the changes and hope Call Screening kicks in again. In short, it's just not worth the hassle.
[Android General] BostonDan:
I found somewhere (not sure where) that if you use Google phone versions 38-40, that it is possible to enable call screening without changing the device fingerprint. I will try to find the post with instructions. It does take changing some of the app's preferences, but otherwise it is fairly straightforward to install and get working, as I have it working on my OP8 5g.

Edit: instructions are here:

https://xdaforums.com/oneplus-8-pro/help/how-to-google-call-screening-t4105851/post82690617

Edit 2: I am using Google Phone version 40.0.273421183publicbeta(4673469)

Cheers,

B.D.
[Android General] fuadhdmini:
The caller can hear the screening voice?
[Android General] BostonDan:
Yes. I tested this on my personal phone and called from my work phone. I heard the screening voice (work phone) and received a transcription on my personal phone.

Edit: Google play auto-updated. I had to change some additional preferences to get it back after uninstalling the updates and blocking auto-update. Can't recall all of the changes I made.

Edit2: lost this ability yesterday and cannot re-enable. Nov 23, 2020

V/r,

Daniel
[Android General] Ary2260:
same doubt

I too am confused about the app version..
[Android General] jefinhodatnt:
thxx bro
[Android General] tendiez01:
link not working
[Android General] ih8legal:
This is the Magisk module you need to flash. It downloads a different gsa.prefs xml that works and places it. I believe this is the last thing you need to install. If you need to uninstall it, delete the module and clear Google app data and it should reverse the change. I had to do that once as I didn't install it in the right order.
[Android General] vetle666:
Anyone have a working fix for the caller not being able to hear the voice of Assistant?

I have a Mi 10 note lite with a pixel ROM, and i have activated call screening with the use of Market Enabler. Ive been trying different versions of Google Dialer but no matter what i try (different versions, turn off VOLTE, turning off wifi) the caller cant hear the assistant.

Could the Assistant be the issue? Should i try downgrading it too?

I feel like im so close, but i cant get it working :(
[Android General] jwarrior319:
Followed those uninstall instructions but safety net still wont pass anymore.
[Android General] ih8legal:
I think that might be related to the security patch. Have you totally uninstalled the propsconfig module?
[Android General] jwarrior319:
So i completely removed magisk hide props config and reinstalled and toggled magisk hide and have safety net passing again. Thanks
[Android General] mrlb:
What work around did you do?

I can't get systemize to list "Phone" as an app.

Searching the /data/app directory and com.google.android.dialer isn't installed there. I'm guessing it's installed else where and you manually moved it to /system/priv-app
[Android General] wolfu11:
Wow it's been so long I don't even remember exactly how I did it but I had to turn it into Phone Base apk. I gave up on the OnePlus 8 pro a long time ago.

Sorry
[Android General] megapinky:
was someone able to get it to work on A12 in unsupported countries?
[Android General] sjamie:
I am in the same situation with my OnePlus 5. Did you ever find a solution?
[Android General] cabagekiller:
So I got this working on lineageos 18.1. You can hear the voice and all. But when I call out it shows nothing on the screen. Any tips or anything?
[Android General] TheRomFan:
Same problem, using Pixel Experience Plus gsi rom on Xiaomi 11T Pro
[Android General] snappyapple632:
OnePlus 7 Pro running crDroid 8.9, I've managed to get call screen to activate. A peculiar problem I've discovered is that call screening works fine if I initiate it manually (from the incoming call screen), but does not work if done automatically. Could this be because I've disabled Assistant in the Google app, or is the Invisible Assistant module the last thing I need to install to get it working? I'm running Magisk Delta 25.2 with USNF-mod. Thank you in advance.
[Android General] Barrel Titor:
Sorry, I couldn't find this question answered anywhere in this thread: Does this hack also remove the geo-restriction?

So; will i be able to use call screening outside the officially supported countries with a SIM card belonging to a provider outside the officially supported countries?

I live in austria which, in many ways, is basically germany, yet it's not officially supported here. I get the feeling that this is a common theme at google...
[Android General] luffy_19081:
Hey I'm new to root now I'm using magisk delta 26.3 on OnePlus 11r /ace 2 can you please help me enable this feature.