Phone: Hold for Me and Direct My Call features

[drandrew1983]

Dear jacopotediosi, Thank you so much for your work and support. actually I have a problem activating hold for me and call screen. I followed your instructions but it always shows activating (require WiFi) and never get activated. please check the screenshot

[hehedemuse]

click "see how call screen works"

[drandrew1983]

actually call screen is behaving erratically, sometimes it works sometimes I have to revert back the settings and activate it again in Google dialer mod. but hold for me never worked, was wondering if it works only on google Pixel phones

[hehedemuse]

Yes

[jacopotediosi]

Hi, I know it's been a long time. I recently started updating GoogleDialerMod again.

Regarding the Call Screen feature, I just released the version 1.05 which should allow you to activate it correctly.

About Hold for Me, instead, I still need some more time to debug why it doesn't work.

[JJsheep11]

Hi, I know it's been a long time. I recently started updating GoogleDialerMod again.

Regarding the Call Screen feature, I just released the version 1.05 which should allow you to activate it correctly.

About Hold for Me, instead, I still need some more time to debug why it doesn't work.

Hello, I have tried the new version (1.05), but call screen always shows activating (require WiFi) and never get activated.

Thank you.

[jacopotediosi]

I have tried the new version (1.05), but call screen always shows activating (require WiFi) and never get activated.

Uhm it may be a stupid question, but have you tried to force close the Dialer, activate wifi and reopen it? It really needs wifi.

Also, what country are you in and what language is set on your phone?

[JJsheep11]

I have tried the new version (1.05), but call screen always shows activating (require WiFi) and never get activated.

Uhm it may be a stupid question, but have you tried to force close the Dialer, activate wifi and reopen it? It really needs wifi.

Also, what country are you in and what language is set on your phone?

Yes, I did all of them. I am outside of US, and using English (US). My phone is Pixel 7.

[shadyrexman]

Same here, the older version of google phone worked perfectly but after the latest update, the call screen stopped working and I tried to force close and restart my phone many times ,and it didn't work. After I used the newest mod and it keeps saying activating. But using the old build of google phone works though.

[jacopotediosi]

Could someone please share his logcat captured while viewing the "activating" screen, after having started the Dialer in debug mode with adb shell "am start -D com.google.android.dialer" command?

Also, I need to know:

• In which country you are
• Which language have you set in your phone
• Your Google Dialer version

(Call Screen currently working for me in Italy, italian language, Google Dialer 94.0.488803600-publicbeta, GoogleDialerMod v1.05)

[shadyrexman]

Same here, the older version of google phone worked perfectly but after the latest update, the call screen stopped working and I tried to force close and restart my phone many times ,and it didn't work. After I used the newest mod and it keeps saying activating. But using the old build of google phone works though.

Which Google Dialer version are you using?

Right now I'm using the old build 94.0.487380581- publicbeta and I can use call screening , but the layout of the settings is different in new build.

Im in Macau, and I'm using English in my phone

[jacopotediosi]

but the layout of the settings is different in new build

Yes, it is not because of a Dialer update, but because there are two call screening features:

• A basic one, managed by call_screen and speak_easy flags, which uses a separate "Call Screen" menu in Dialer settings
• An enhanced version, managed by the revelio flag (which requires also the basic call screen to be enabled), which merges with the already existing "ID/Spam" entry in Dialer settings

The suggested mod switch in GoogleDialerMod v1.05 enables the enhanced one.

[drandrew1983]

Country MaldivesLanguages English USDialer Version 94.0.488803600 Somehow I managed to activate it by enabling many parameters in Google Dialer Modwhat I can't enable by any means is Hold For meDon't know how to share what I did, don't know if it will work if someone calls me. Last time I had black screen on incoming calls after trying to do so On Thursday, November 24, 2022 at 08:46:39 PM GMT+5, Jacopo Tediosi @.***> wrote:

Could someone please share his logcat captured while viewing the "activating" screen, after having started the Dialer in debug mode with adb shell -c 'am start -D com.google.android.dialer' command? Also, I need to know:

• In which country you are
• Which language have you set in your phone
• Your Google Dialer version

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[jacopotediosi]

Currently it seems that Call Screen may not work in some countries (SIM-based): https://github.com/jacopotediosi/GoogleDialerMod/issues/42#issuecomment-1326709693 I'll try to find a workaround

[shadyrexman]

Currently it seems that Call Screen may not work in some countries (SIM-based): https://github.com/jacopotediosi/GoogleDialerMod/issues/42#issuecomment-1326709693 I'll try to find a workaround

Thank you so much for this.

[jacopotediosi]

Hi! Call Screen should work with latest v1.06 (for more details please see #42) I'll work on Hold for Me soon.

[drandrew1983]

Dear Jacob,It works fine for me now.waiting for "Hold for me", hope you can activate it.Thank you so much for your work  On Sunday, November 27, 2022 at 03:24:10 PM GMT+5, Jacopo Tediosi @.***> wrote:

Hi! Call Screen should work with latest v1.06 (for more details please see #42) I'll work on Hold for Me soon.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[Yoanndp]

Hello Jacob, I did some logging and there's what I have found on my phone (Pixel 7, HFM enabled from GDMod) :

11-29 08:27:53.496  6347  6402 I DialerTelephonyManagerCache: com.google.android.dialershared.telephony.TelephonyManagerCache.lambda$setUpNetworkMemoize$0:83 getNetworkOperatorName
11-29 08:27:53.498  6347  6402 I DialerTelephonyManagerCache: com.google.android.dialershared.telephony.TelephonyManagerCache.lambda$setUpNetworkMemoize$1:92 getNetworkCountryIso
11-29 08:27:53.498  6347  6402 I DialerTelephonyManagerCache: com.google.android.dialershared.telephony.TelephonyManagerCache.lambda$setUpNetworkMemoize$2:101 getNetworkOperator
11-29 08:27:53.500  6347  6402 I DialerTelephonyManagerCache: com.google.android.dialershared.telephony.TelephonyManagerCache.lambda$setUpNetworkMemoize$4:121 getSimCountryIso
11-29 08:27:53.502  6347  6405 D vulkan  : searching for layers in '/data/app/~~3k-Bq0A3wPtIf3DVSD1APA==/com.google.android.dialer-eODAIdVVeazpRsYKoeHf4w==/lib/arm64'
11-29 08:27:53.508  6347  6405 D vulkan  : searching for layers in '/data/app/~~3k-Bq0A3wPtIf3DVSD1APA==/com.google.android.dialer-eODAIdVVeazpRsYKoeHf4w==/base.apk!/lib/arm64-v8a'
11-29 08:27:53.558  6347  6431 I DialerAudioFileSuperpackProvider: com.google.android.libraries.micore.telephony.common.audiomessages.AudioFileSuperpackProvider.getFileInternal:316 Providing file /data/user/0/com.google.android.dialer/files/superpacks/call_screen_audio_messages/1613501903_en-us_cloud-en-US-Wavenet-F_71c80e40489676cc808b1e9df1b5b916/71c80e40489676cc808b1e9df1b5b916.opus from superpack
11-29 08:27:53.559  6347  6431 I DialerAudioFileSuperpackProvider: com.google.android.libraries.micore.telephony.common.audiomessages.AudioFileSuperpackProvider.getFileInternal:316 Providing file /data/user/0/com.google.android.dialer/files/superpacks/call_screen_audio_messages/1613501903_en-us_cloud-en-US-Wavenet-F_dc43808541a81bb4e880a0f246d8ce3b/dc43808541a81bb4e880a0f246d8ce3b.opus from superpack
11-29 08:27:53.635  6347  6440 I DialerAudioFileSuperpackProvider: com.google.android.libraries.micore.telephony.common.audiomessages.AudioFileSuperpackProvider.getFileInternal:316 Providing file /data/user/0/com.google.android.dialer/files/superpacks/call_screen_audio_messages/1613501903_en-us_cloud-en-US-Wavenet-F_e2f607685cf332b687aa5ca8fef61545/e2f607685cf332b687aa5ca8fef61545.opus from superpack
11-29 08:27:53.635  6347  6440 I DialerAudioFileSuperpackProvider: com.google.android.libraries.micore.telephony.common.audiomessages.AudioFileSuperpackProvider.getFileInternal:316 Providing file /data/user/0/com.google.android.dialer/files/superpacks/call_screen_audio_messages/1613501903_en-us_cloud-en-US-Wavenet-F_dede97e191c3d1b9389f44851ac7838d/dede97e191c3d1b9389f44851ac7838d.opus from superpack
11-29 08:27:53.636  6347  6440 I DialerAudioFileSuperpackProvider: com.google.android.libraries.micore.telephony.common.audiomessages.AudioFileSuperpackProvider.getFileInternal:316 Providing file /data/user/0/com.google.android.dialer/files/superpacks/call_screen_audio_messages/1613501903_en-us_cloud-en-US-Wavenet-F_8a1bfe69068649e82f270263888a69f3/8a1bfe69068649e82f270263888a69f3.opus from superpack
11-29 08:27:53.637  6347  6440 I DialerAudioFileSuperpackProvider: com.google.android.libraries.micore.telephony.common.audiomessages.AudioFileSuperpackProvider.getFileInternal:316 Providing file /data/user/0/com.google.android.dialer/files/superpacks/call_screen_audio_messages/1613501903_en-us_cloud-en-US-Wavenet-F_b53062dd3b2119adb3992d7e9fba9174/b53062dd3b2119adb3992d7e9fba9174.opus from superpack

It's still trying to use en_US files (en-us_cloud-en-US) even if my SIM locale is fr_BE. I can provide you full log if needed.