FP5 Wi-fi calling not working

/e/OS Devices Fairphone
, , ,
1

Dear community,

I have exyctly the same issue as described here: https://community.e.foundation/t/fp3-wifi-calling-no-longer-working

The only differences are the device (FP5) and OS version (3.0.4-t).

In a nutshell, wi-fi calling is not working but it has worked before. Living in a rural area with bad signal coverage this is a key feature for phone calls. Unfortunately I cannot tell exactly when / with what version it has stopped working.

Any pointers welcome. Thanks a lot.

Pam

2

the person in the linked FP3 thread really had necessary libraries missing and for other FP3 owners things worked. As in: your wifi call can be broken, but are you sure this is the same exact same case (“dlopen failed”) from looking at logcat errors?

There’s a gitlab wificall issue on a FP4 case, but if it’s not a general device issue, it’s very much scoped to device-carrier even. The issue gives general troubleshooting tips though.

3

Is it Congstar?




4

Indeed, that’s right. This issue concerns the Fairphone 4. However it does not appear to be related to a problem with the carrier. In fact, when the same SIM card is inserted into another device (an iPhone 8 in this case), WiFi calls work without any problems. Furthermore, other users have reported this problem with different operators.
It must be a problem related to version 3.XX specific to the Fairphone 4.

I don’t know if other devices are also affected.

5

Wow, that was a fast triple response, thank you all very much.

I haven’t checked logcat, I need to rephrase my statement, I guess. The symptoms are the same, I didn’t look so deep.

Thanks for the link. Could be related, the jump to /e/os 3 was also my first suspect but I cannot pinpoint to it.
I will try to put my SIM into my wife’s phone and tĂ©st it there.

Drillisch

I agree with that. My operator does not even seem to be contacted, the message just tells me to connect to a wireless network - but it is connected.

6

I don’t want to muddy this thread, it is on FP5 - but generally, if within the same device and version, other users can do successful wificalls, then it ceases to be a general device issue and gets to be more of a (carrier) config problem

7

I just did the test and swapped SIMS with my wife. With my SIM her phone uses wifi calling without any issue, that ultimately rules out the carrier.

A config issue - maybe. But since I don’t mess around in developer settings or anywhere else it was very likely not caused by myself.

8

Indeed, I had the same behavior with my FP4. Putting my SIM in my old I-Phone 8 and WiFi calling worked immediately.

So there’s a simple test to run to see if IMS VoWiFi service is well provisionned on your device:

Open the call dialler app, and dial *#*#4636#*#**

Then click on “phone information”. This will open a page about network configuration.
On the upper right three dots, click on ‘IMS state’.

Then check what’s the VoWiFi status. (in my case: VoWiFi: Unavailable)

9

image
image1224×807 78.7 KB

Same here. What I am going to do with this information?

10

What device is it, FP4 or FP6?

You may publish this - and all related details - on the Gitlab issue: (see above)

11

It’s FP5.

I don’t have a gitlab account. Yet. On my way to create one.

Thanks again.

1 Like
12

Just to be sure: Can you check your Wi-Fi calling settings? They are available in the public part of the phone settings, but quite hidden, and cannot be found with the search function of the settings.

Open Android settings > Select “Network and Internet” > Select “SIMs” > Your SIM card is listed (or several cards on multi-SIM phones). Tap on it. (This is IMHO not that intuitive because the toggle on the right suggests that you can just deactivate the SIM card with this entry.) > Scroll down to “Wi-Fi Calling” and tap on it > Configure as desired, i.e., activate “Use Wi-Fi calling”, set “Calling preference” to “Call over Wi-Fi”.

Is Wi-Fi calling available now if you check with *#*#4636*#*#?

I had to manually set my preference to Wi-Fi calling when I reinstalled my phone a couple of days ago.

EDIT: You can of course also use your favourite search engine for details :slight_smile:

1 Like
13

Hi @Tentos,

also thank you for your contribution. But yes, of course those settings have always been like that.

image
image1224×983 53.3 KB

1 Like
14

image

It doesn’t accept my email (Tuta), so I won’t be able to post in gitlab. Maybe someone else wants to transfer the infos I have provided.

15

@Manoj Is the registration on GitLab still limited? Can you contact @Pampelmops so that they may open a bugticket there? (See also Create User in Gitlab)

1 Like
16

@Manoj Yes, please? :slightly_smiling_face:

17

I sent you a message.

1 Like
18

Good new is that issue #8771 has now been assigned to a developer.

Things should now “going on” with this issue :wink:

1 Like
19

As anounced, the update to 3.2. a14 did fix the problem on my FP4. WiFi calls are now working consistently when the preference to always use WiFi is set.

However the calls are very unstable even in good WiFi surroundings. The FP4 even disconnects from WiFi sometimes. Anyone else with those problems?