-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Phone: Automatic Call Screening not activating #54
Comments
Same issue here, additionally, the setting keeps disappearing after a device restart
|
I think that it's working but it's very difficult to test if it's actually working |
I confirm automatic call screening only working if the call screen is enabled in English and the caller is English (based on the international prefix number, I guess). All the other call screening features, except the automatic one, should work. |
Does it only work if it's a new number? |
Update: Got a ring from a new number and no the call screening hasn't been activated. Maybe I can try something with logcat if that'll work? |
Nothing happens when I enable call recording or call screening. I'm on Google Dialer v96 and it is installed to system. I also tried Pixelify and that worked for me once, but then it broke afterwards. Tried this on a fresh new install of PixelOS Android 13 custom ROM on my Poco F1. I tested this first, before trying Pixelify (which again, allowed Call Screen to work once and then stopped working). |
Are you saying both automatic and manual call screening aren't working? Because from where I live automatic doesn't work but manual does so maybe that could be a location thing
…On Wed Jul 26, 2023, 10:33 AM GMT, chaoscreater ***@***.***> wrote:
Nothing happens when I enable call recording or call screening. I'm on Google Dialer v96 and it is installed to system.
I also tried Pixelify and that worked for me once, but then it broke afterwards. Tried this on a fresh new install of PixelOS Android 13 custom ROM on my Poco F1. I tested this first, before trying Pixelify (which again, allowed Call Screen to work once and then stopped working).
—
Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHBFVTXLV7PSQVGUOR2PS5LXSDXBJANCNFSM6AAAAAAUM5DHY4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I'm saying that I don't get the call screen setting at all. I can't even trigger it manually, because it just isn't there. The whole point of this mod is to enable this regardless of what your location is. |
That's true, but at the end of the day it's really just trying to force the app to enable flags. If google double checks the geolocation of the feature, then I'm unsure if there's anything that can really be done |
This past month, I've bypassed Microsoft Teams and Company Portal from detecting root on my device, by using a combination of Magisk modules and LSPosed modules and various other tricks. Intune policies are quite hard to bypass and most MSP companies I've worked at all use InTune as the MDM to control users' devices. So the fact that this can be bypassed is already an achivement. On top of that, I've also spoofed location for various apps, which also detects root and detects whether you have mock location enabled. These are apps such as big petrol brands like BP and Caltex, as well as banking apps. So when someone says XYZ doesn't work, I call BS on it. This week alone on XDA forum, I've seen plenty of comments from various people about how they can't get the unlimited Google Photos mod to work. And yet, there are plenty of custom ROMs (like PixelOS) that unlocks unlimited Google Photos right in the ROM itself and I'm using it right now. Pixelify at least changes the Google Dialer menu slightly, even when it's not fully working. But this mod just doesn't change anything at all. So pretty sure the problem aint related to Google checking your location, especially if no data is available (i.e Wifi and mobile data off). |
actually you probably are correct. maybe it could be only activating call screening on certain locations from certain number prefixes, but afaik this activates hidden flags in each google apps |
Okay, IDK what to do. Pixelify module hasn't done much to help it, and I remember getting the Google app to show search labs by using a VPN (and after some restarts/clear datas) to get it working. I don't know how Google obtains its geolocation but it is one of the main things to be found |
Overview
So automatic call screening is available on the phone and does activate through Wi-Fi, however when it comes to actually testing the feature, it doesn't work at all.
Steps to Reproduce
Expected Behavior
Automatic call screening taking the phone call
Actual Behavior
It just rings me instead
Other Notes
If I force stop the dialer app and re-open it, Call Screening doesn't stick and I need to stop the app again for it to run through it once more. And everytime I do open the Automatic Call Screening section it shows 'Activating Call Screen (Requires WiFi)' and then disappears once activated.
Screenshots
System Information
Device and model: Pixel 6 Pro
ROM and Android version: Stock, TQ1A.230105.002
Is Google Dialer installed as system app: Yes
Installed Magisk / other SU Manager version: Magisk
Installed GoogleDialerMod version: 1.06
Installed Google Dialer version: 96.0.499579918
Your device language (locale): en-AU
Your location (country of the SIM and country where you are): Australia
Logcat
logs.txt
The text was updated successfully, but these errors were encountered: