Can't make/receive phone calls

iphuqbutts

When you say you bought your phone from "Google" do you mean

https://store.google.com/category/phones?hl=en-US

Otherwise if you bought a refurb phone from a 3rd party vendor, there may be a region issue.

For example, If you use AT&T in the United States the supported Pixel 6A has a
Hardware SKU of GX7AS

On your 6a device go to settings and search for "Hardware SKU" it should be a 5 digit alpha numeric code like in the example above (GX7AS).

open a browser and search your phone carrier and compatible devices and you should see which Hardware SKU is compatible on their network.

if you're in the USA and have AT&T I found this site

https://www.att.com/scmsassets/support/wireless/devices-working-on-att-network.pdf

This site may be helpful for Verizon by searching your phone's IMEI number

https://www.verizon.com/od/prepaid/bring-your-own-device/?connectedCar=true#/checkDevice

This may or may not be the issue but my device is supposedly not compatible with my carrier but it works just fine. I bought a refurb from Amazon.

blernk

I have not tried a full reinstall. It was my next step, but hadn't done it since it's more work.. Guess I just needed someone else to second the idea. I'll post the results here after it's done. Thanks.

gentlefrog5168

gentlefrog5168 I'm back again- because it's happened, again, even after factory wiping. Not even had a GrapheneOS update or anything. After a couple of weeks of it being all fine again, it's just... happened. Entered *#*#4636#*#* to bring up the info menu, and it even says on IMS service status that it's registered and that voice over Wi-Fi works. Yet, I try to ring, and nothing. Not even attempting to WiFi call. Calls over SIM, doesn't ring, then drops.

blernk TEMP FIX: Reset mobile network (Settings > System > Reset options > Reset Mobile Network Settings).

The above is the only thing that helps fix it right now - and that doesn't even bring back WiFi calling. If it keeps being like this, I may unfortunately have to go back to stock or find another phone.

If any GrapheneOS contributors see this and want more details, happy to be a guinea pig.

DeletedUser286

gentlefrog5168
There is a very high probability that VoWiFi will not work if you are using a VPN.
Try no VPN and no custom DNS.

GrapheneOS

Lack of information about the carrier, etc. means there's little that can be done. It's likely either a carrier side issue, general Android compatibility issue with that carrier or hardware failure. GrapheneOS uses the same carrier configurations as the stock OS and doesn't make changes in these areas beyond enabling more toggles and adding the option of 4G, 5G or 4G/5G only modes.

MetropleX

Following on from the above, I note out of all the steps taken, trying another carrier SIM doesn't appear to have been mentioned.

This is also not an uncommon issue on stock, a quick cursory search for 'Pixel can't make calls' throws up results from Pixel Support like these:

https://support.google.com/pixelphone/thread/153524370/pixel-6-not-making-or-receiving-calls?hl=en

https://support.google.com/pixelphone/thread/138534946/my-phone-is-not-making-or-receiving-calls?hl=en

gentlefrog5168

MetropleX I'll be first to jump in on this, I've tried a different e-SIM on this, but that's had the same effect. One carrier is SMARTY (piggybacks off of 3 UK), another is Honest Mobile's Smart SIM (a mix of EE, O2, Vodafone and 3 UK, but is under the name Telnyx). Unfortunately, same issue occurs.

Feels weird, given this is an issue that doesn't discriminate against model number. Wonder what the permanent solution is?

gentlefrog5168

DeletedUser286 I'm aware. There are a few places I connect to frequently where WiFi calling is supported. Either they all work one day, or the other day they don't. Mid of this week they've all decided to work fine. Last two weeks before then, they didn't work at all. It's a coin flip.

EconomicSachs

Quoting from my own thread since I didn't find this thread:

Just found out that suddenly I can't make any calls with either my physical SIM or eSIM on the phone. Also can't receive calls on the physical SIM (haven't tested eSIM but I doubt it'll work).

Data/sms are working fine.

I don't really use this phone for calls much, but at least it was working well a few weeks ago. I tried the SIM in an older Pixel and it exhibits the same symptom. Both phones are running the latest GrapheneOS.

Also tested that the SIM works fine in a non-graphenos phone.

Tried rebooting/resetting the mobile network settings but no luck.

My guess is with the 0519 kernel update?

Note that two of my pixel phones with the latest graphenos are both having this problem.

stapel

Recently had a user with this issue. Pixel7a, Carrier is US Cellular. Was working fine for weeks, then all of the sudden, after the most recent update, user could hear incoming calls, but no way to answer.

No issue with outbound calls and missed calls showing in call logs. In this case, some of the permissions for the phone app had been reset, notably:

Display over other apps (disallowed)
Music and audio permissions (disallowed)

Set 1 to Allowed...Tested still no notification popup to answer call
Set 2 to Allowed...Issue resolved. Not sure why GrapheneOS presents this particular permission for phone, but it's the one that seemed to resolve the issue completely.

Incoming calls now showed notification at top, when tapped, call answer screen appears, user is able to answer call.

If you haven't checked already, I would make sure these two permissions in particular are allowed.

Note: Compared these settings with CalyxOS which is how the Display over other apps permission was id'd. Hope this helps someone.

riemann

stapel thanks for sharing. Adding Music and audio permissions did the trick for me.

blernk

FOLLOWUP TO INITIAL POST FOR THOSE INTERESTED.
Short story: reinstalling the OS fixed the calling issue on my Pixel 6a

Details:
Last night I FINALLY reinstalled GrapheneOS. I used the web-based installation method. My computer OS (openSUSE Tumbleweed) isn't officially supported, but the install went smoothly. I read through the instructions for Linux and double checked my ADB install, udev rules, & fwup. I initially tried installing from Brave, but it didn't work so rather than spend time with it I switched to a fresh install of Chromium and had no problems after that. It has only been roughly 24 hrs since the reinstall, but I've been able to receive and make calls normally.

I'm about to restore what I can via SeedVault and SMSBackup. I will post again in another day with info on the phone's post restore preformance.

Cheers!

other8026

blernk reinstalled GrapheneOS

Sorry you went through all the trouble. You don't need to reinstall the OS like you would on a computer. Factory resetting achieves the same thing.

But glad you got it to work, though!

blernk

other8026 I was unaware I could have done a factory reset. Well, hindsight and all that. Thank you.
I do wonder though, would a factory reset really do the SAME thing, or would it be, more or less, functionally similar?

blernk

Reinstalling Graphene restored SIM calling on my Pixel 6a. I was somewhat trepididitious about restoring my settings and data, but the phone still works after doing so. Since the cause is still unknown and knowing that the issue returned after a factory reset in Gentlefrog5168's experience, I'll be performing more frequent backups to make any future reinstall less painful.

I'll search the forum or start a new thread for the following, but want to mention it here. The calling issue is fixed, but the data restore completely borked my text messages leaving me with a new problem. The restored contacts all appear normal, and there doesn't seem to be any SMS missing, but the messages are all attributed to the wrong contacts and I can't seem to send new messages to the correct contact. Manually entering a phone number to send a new text message to auto-corrects to the wrong number. Starting a new text by selecting a contact name sends the message to the wrong contact even though the contact's number is correct in the Contacts app.

other8026

blernk You're right. A factory reset isn't the same thing as flashing again, but the result is the same.

gentlefrog5168

After experimenting with this, I kind of got a solution - but it wasn't what I expected. I actually ended up switching provider temporarily, and when I did that it worked completely fine. Granted, it was only for a couple of days before I switched back. I got a new SIM from the provider I was having Graphene signal issues with about a month ago, and... it's fine now. Not dropping signal nearly as much as I was when I last posted. No resets or anything, just switched SIM card.

TLDR; new SIM card worked, same provider. Try asking for a replacement SIM and see if that changes anything!

mira

Experienced something similar on Pixel 9a. Temporary fixed it by disabling 4G calling in:
Settings-->Search for Calling

My settings are now:

4G calling disabled
Preferred network type 5G recommended
Wifi calling enabled (call over mobile)

This works for calls, but I think I am not using VoLTE now?
I assume so, because when I switch Wifi calling enabled to be over Wifi, I can not see any requests in my opnsense firewall.

However, I also tried with Preferred network type 4G and 4G calls enabled but this didn't worked - it seems whatever settings I use with 4G calling enabled calls do not work.

Would like to know which of the mentioned settings are the VoLTE settings and maybe the settings above help others to temporary fix it. However, I assume this won't work forever, since non-VoLTE calls are going to be disabled in my location.

Temporary the settings are ok for my threat model, since I usually even do not use phone calls anyway, but be aware that I guess VoLTE ist this way disabled and adapt this to your threat model please.

Any permission settings did not helped in my case.