I have an FP3 and an FP4. Wifi calls work perfectly on my FP4. On the FP3, however, they work fine after rebooting the phone for about 24 hours, after which no more calls are made over Wifi. The phone’s OS /e/os is up to date.
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Does anyone have an idea for correcting this problem?
you could look at the gitlab issues of both /e/ and lineage, and the fairpone forum if other users report similar.
This FP3 user writes of a faulty SIM card - Device keeps loosing cellular/mobile connection (#6382) · Issues · LineageOS / issues / android · GitLab
I’ll do my research following your advice. Thank you for your help
I wonder if putting the phone into airplane mode quickly and back restores your ability to use wificall without reboot.
How did you determine its 24h ?
I’ve tried rebooting, airplane mode, call-wifi deactivation/reactivation without solving the problem. About the 24 hours, I mean it’s not 10 minutes or 3 days. The order of magnitude is a day. Since yesterday I’ve updated to /e/OS V3.0; I’ll see what happens.
My problem is that my FP4 has also updated to V3.0 and the wifi calls seem to be working very badly now!!!
I have a FP3 to do debugging, wificall works with my provider, but never paid close attention when it’s used. Checked now and will retry in 24h if it continues to work.
When you compare the 24h, are you still in the same network (home wifi) that you’re in the beginning, or any other wifi, even at work?
… and how do you determine “work badly now” on the FP4?
Yes, when I do my tests, I stay on the same wifi. I have a first configuration: my home with a wifi from an Orange fiber optic internet box. A second at another address: wifi from an Orange 4Gbox. I’m testing FP3 for several days in one configuration, or several days in the other.
About FP4: it worked 100% wifi-call until yesterday’s V3.0 update (all calls went through wifi). Since then, I’ve managed to make wifi calls for about 20% of calls (I’m currently where I’m using an Orange 4Gbox). The test is simple because I’m in a geographical area where there’s no basic coverage, only 4G. In 80% of cases, the FP4 tells me that there’s no network and that I need to connect to a wifi, even though I’m already connected to wifi.
Translated with DeepL.com (free version)
and both devices, FP3 and FP4 have in the Dialer app:
“Settings (upper right menu) → calling accounts → your-provider-name → Wifi-call enabled and preferred Call over Wifi (WLAN?)”
These are the parameters that were configured
I can’t replicate a fundamental issue - last few days the FP3 will continously make wificalls, no modem firmware crash or the like that’d necessitate a reboot.
At times it used the radio instead of wificall, but could be up to my provider (it was nationally roaming when it chose gsm).
Haven’t yet a grip on understanding where Android components decide either way:
If you want to look yourself, it’s
adb logcat Telephony Telecom Dialer SubscriptionUtil ImsCall QImsService *:S
and add a filtering pipe at the end for what is an indicator how the phone sees it
| grep -E '(isWifi: [YN]|isWifi=[a-z]+|isVoWifiEnabled=[a-z]+)'
but *#*#4636#*#* is as truthful if VoWifi is available and its register status known.
after a few more days there are times when the FP3 will not build up an ipsec tunnel on wifi and register for VoWifi and goes on to use the radio for VoLTE. I can’t see the determinism. But it will do a wificall a few minutes after it did a VoLTE call happily, so it doesn’t need a reboot in principle
Hello, my feedback since the V3.0 update is that my FP3 is finally working well. I needed a few days to be able to say it!
What is confirmed, however, is that my FP4 almost never works with a wifi call since I upgraded to V3.0. When a call (rarely) manages to be established over wifi, I’ve noticed that the screen doesn’t display the wifi call logo, but that once the call is established, the quality indicated is HD, i.e. via wifi. I’m hoping for a future update to put things right.
Thank you very much for your willingness to help me. I’ll take a look at the adb commands for cultural purposes!
HD can also be an indicator for VoLTE, not necessarily for WiFi.
yes, separate properties that the Dialer gets from the Telecom subsystem and uses to show indicators.
If it’s wifi call, it will say so. HD just for audio quality. During the lifetime of a call those properties get added and removed from a prop array.
I Telecom : InCallController: Sending updateCall
[ ...
handle=tel:*************, vidst=A, childs(0), has_parent(false),
cap=[ sup_hld mut],
prop=[ HD wifi] <== properties
],