Pixel 6a Android 15 Phone/dialer fails to show real origin country code on calls from phone's home country while roaming

[libove]

My Google Pixel 6a phone running Android 15 (January 2025 Security Patch, all other updates also applied) incorrectly shows the phone number of callers which call me from my phone's home country (Spain) when I'm roaming (at present in Germany; I've also seen this happen when I'm roaming in the US) as being calls made from the country in which I am currently roaming, instead of correctly identifying the originating country of the calls.
My OnePlus 5T running Lineage OS 22.1 does not make this mistake - it correctly prepends the originating country code +34 to these calls which come in with only the in-country part of the number.
The problem this creates is that it is neither possible to call back one of this incorrectly numbered calls, nor to report-block the calls.
See two screenshots, one from my Pixel 6a in which five calls from Spain (several but not all of them spam, as it happens) appear with no country code at all (and so my phone, being roaming in Germany, treats them as German local numbers, incorrectly), and the other from my OnePlus 5T running Lineage OS 22.1 which received the exact same call (I have a Multi-SIM service on this Vodafone Spain line of service) and correctly lists them as +34 ...
How do I configure Android 15/ a Pixel 6a/ the Google Phone-dialer app to correctly prepend the calling country's code to calls which don't arrive to the phone with that e.g. +34 already as part of the calling station ID? (I already asked Vodafone Spain, my carrier, about this, and they said it's a phone setting over which they have no control; the fact that the OP5T running Lineage OS 22.1 gets it right while the Pixel 6a gets it wrong suggests that Vodafone is correct about this).
thanks!

 

[B. Diddy]

Welcome to Android Central! Open your Phone app, then tap the 3-dot menu button at the upper right., then Settings>Assisted Dialing. Make sure that toggle is turned on.

 

[libove]

Welcome to Android Central! Open your Phone app, then tap the 3-dot menu button at the upper right., then Settings>Assisted Dialing. Make sure that toggle is turned on.

Two things.
1. Assisted dialing had been on at the time I captured the screenshots. So it didn't help.
2. Assisted dialing describes itself as helping to add the home country's country code to *dialed numbers* while roaming, in case the stored dialed number does not include the country code. But my problem is with how *received* phone calls fails to include a country code (and so are misinterpreted for calling-back or reporting-blocking as being in the roaming-in country's country code instead of in the called-from country's country code as they must be).

 

[B. Diddy]

Hmm, it's hard to find anything online about this specific issue. Can you confirm that your Phone app has Location permission turned on?

 

[libove]

I too was surprised to find little about this, as the problem isn't new; it just finally annoyed me enough to want to try to solve it!

Interestingly, Location was the only requested permission that the Phone app did NOT have enabled. I don't know why. I've now enabled it and will monitor the issue.

Though, Location should not be necessary, as the calling number and network provide origin information, and the phone's current roaming-on network provide current location. (Of course, this is just me trying to make sense; I have no idea how it's actually implemented. Probably, "badly"...)

I imagine it won't take a whole day before another call comes in and I can test whether enabling the Location permission for the Phone app solved the problem.

 

[libove]

Nope. Enabling Location permission for the Phone/dialer app did not make a difference. A call came in (a totally legitimate call this time) from Madrid, and my phone (roaming here in Germany) shows "919991770" "Kunreuth" as though it were the German city code for Kunreuth, not a call from Spain...

 

[B. Diddy]

Hmm, strange. First, send feedback to Google about this from within the Phone app (tap the 3-dot menu button at the upper right, then Help & Feedback).

Second, in case some 3rd party app might be interfering, see if it also happens in Safe Mode: https://support.google.com/pixelphone/answer/2852139?hl=en

 

[libove]

I sent Google feedback. (Not sure I expect that to produce much of use...)
I also tested in Safe Mode. That did not make a difference. :-(

 

[B. Diddy]

Also try posting here: https://support.google.com/pixelphone/community?hl=en

I'm pretty sure you indicated yes, but your Roaming toggle is turned on, right?

 

[libove]

Yes, roaming is on - I make and receive international calls regularly, and data roaming is fully functional.
I spoke with a Google tech support agent. They insist that it is a network setting controlled by the mobile network operator. (Whom I had already asked about it, and insisted it is a phone setting). I called my mobile network operator again (Vodafone Spain) and they again insisted that it's a phone setting.
I've just swapped the SIM cards between my two phones and am waiting for a friend in Spain to try to call my number, to see if the problem switches phones, in which case it really would seem like a mobile network operator line/SIM setting problem:
No change. Still only on the Pixel 6a the problem occurs; still on the OnePlus 5T running LineageOS the problem does NOT occur.
I replied to Google's summary email of my talk with them asking them to escalate.