Yes in fact the shutdown of the 3G network was the reason I needed a new phone (was using a 10 years old Galaxy S5 previously) and went for the FP6. But VoLTE works without issue for me on the FP6. The only thing that doesn’t work is VoWIFI. I’m not sure whether ordering a new SIM could do the trick but I don’t think so. I also had an eSIM for travel a few months ago (incl calls with a foreign number, not just data) and that one did not work either on VoWIFI. So I guess it’s an issue with the FP6 firmware and/or e/OS. Unfortunately I did not test VoWIFI on the stock ROM before switching to e/OS…
Did Sunrise in some form confirm to you that Wifi calling is enabled for you on their end? (Perhaps you asked them, or it’s in the written details of your plan with them?)
1 Like
There are some parts of IMS registration not fully explained but the install page mentions
Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.
This implies that IMS registration happens (somehow) at an “original only” level, that the registration and the things it organises may not be possible in /e/OS firmware. While also, quite different, VoWiFI is something of a concession by the carrier depending on their charging protocols.
I am all for keeping devs fully informed on Gitlab but as Sunrise have disclosed to others that items may be “not by default” then it will be useful to speak to them … let Sunrise have a go at solving the problem.
I did already contact Sunrise and they confirmed that on their side VoWIFI is enabled for my number. They told me it must be something related to my specific phone or OS but on their side everything is enabled.
I know that I should probably have tried VoWIFI while still on the stock ROM but I only tried VoLTE at the time before moving to e/OS. Now I am a bit reluctant to install the stock OS back and then revert again to e/OS given all the hassle it would involve and the risk of bricking the phone… I was thinking that since VoLTE, SMS etc was all working fine, it was okay to move to e/OS.
1 Like
By the way, Murena sells the FP6 with e/OS preinstalled. How is this different from installing official e/OS afterwards manually on a FP6 that came with stock FPOS? Then it would mean Murena phones have no chance to use VoWIFI ever?
that warning (current text) is a template snippet from LineageOS wiki that goes back to 2022. It was relevant for some devices (and carriers). For devices with a market release past 2020 / Android 10ish it’s imo irrelevant.
Yes probably, and still that would be for LineageOS. Although e/OS is based on LineageOS, it is installed on some devices from the start e.g Murena FP6. These devices never see FPOS at all (AFAIK). So how would users of Murena FP6 be able to use wifi calling or any other feature that would require activation from stock OS? Like you, I guess such requirements are probably outdated now.
They do. Fairphones don’t come out of the factory with /e/OS installed, they all come with Fairphone’s Android OS.
As far as I remember to have read so far a service provider installs /e/OS on the ones Fairphone sell themselves with /e/OS installed, and Murena install /e/OS on the ones they sell themselves with /e/OS installed.
On my part, perhaps it was a little cheap to quote that 
but I did preface with
as you say @npjonson relaxes to
Make it clear you need to provision IMS on stock.
Even that leaves aside, is some dynamic magic missing in AOSP? … and how to ameliorate.
Fair point, but Fairphone/Murena is still unable to test VoLTE/VoWIFI with the carrier that the end customer will ultimately use…or do I miss something ?
@Manoj I have provided very detailed information both in the bug report and in my posts on this thread. I will now repeat myself here again, for your convenience. I have tested all eOS versions on FP6 up to the current 3.7.3, with the same result…wifi calling doesn’t work on eOS but works fine on FPOS, on the same handset (FP6), and every other non-Fairphone handset I have tested works with no issues with my SIM card. I agree with you that the developers probably do have 100% success, because they’re obviously not replicating the issue that myself and many others are experiencing. Also I’d like to re-iterate that it is not a problem that only impacts me, other people in different countries are also affected, as you can see from the many earlier posts in this thread, so it is not just a problem exclusive to Australia.
Can you please confirm when this wifi calling problem will be fixed?
Pl can you share the bug report which had these details. Pl share even if it has been closed. That will make it easier for the developers to track and resolve this issue.
@Manoj as per my post on March 27th, the bug ID is #9290. My expectation is that the bug ID on github will be investigated, are you saying that nobody has looked at the github bug ID 9290? Do you recall that I was specifically asked by yourself to raise this bug report so that the issue could be properly tracked and investigated? Are you now saying I need to post more details on this thread, instead of using github? I am very confused. I would sincerely appreciate it if there was more of a coordinated, consistent approach to actioning eOS bugs, rather than telling me to raise a github request to get a bug on the radar of the developers, and then asking me 2 months later to post details on this thread instead.
The bug has a status of awaiting development which means it is to be added to one of the next development cycles. Will ask the team to put some milestone dates around the issue.
Some Sunrise research deleted as unreliable
I do not mean to suggest that these are solely user level problems but should get reported as
On my side VoWiFi works pretty well on my FP6 3.7.3. (Carrier: Salt. Switzerland).
But I already heard here and there some VoWiFi troubles with Sunrise… I don’t remember if the issue is related to Sunrise with Fairphone of if it does affect other users as well..
I am having troubles with calls and sms using fp6 with e/os 3.7.3 on a old Sunrise SIM (previously UPC). Sometimes it works, mostly it won’t. The workaround is highly impractical because I need to do it before a call which is an issue for inbound calls..
After a long discussion with various AI models and other users here (@aibd ) and I came to the conclusion that the keepalive to the IMS registration likely fails due to some unknown reason. Even adb debug logs show that sometimes my phone just does not find the IMS. Configuration workarounds did not work (such as forcing LTE etc). One option would be to flash stock OS again, making a call and sending an SMS to force NVRAM update on my FP6 hardware. To me this sounds like a crazy approach but @MiaOst seems to confirm that this might be worth trying. The other option would be to use an eSIM since those come with the configuration of the network carrier, so no NVRAM needed.
@stanwood Did you run your stock android once using your SIM (Salt)? Or do you use an eSIM? In the first case, I’d wish this was stated on the official flash guide because if I remember correctly I’ve never inserted my SIM while stock OS was still there only after I flashed the e/os ..
If I recall correctly, I did indeed make an outgoing call on the stock ROM just before flashing /e/OS, as recommended in the installation guide.
That said, /e/OS receives firmware updates directly from Fairphone, so I don’t think this step is strictly necessary. In fact, many users haven’t performed this step, and 4G (VoLTE) calls still work perfectly fine.
Correct! VoLTE works perfectly, it’s just the VoWifi (wifi calling) that doesn’t work for me and various others. I’ve raised a bug report about it quite a while ago, so hopefully @Manoj will provide some more details about what the underlying technical issue is and how long it will take to fix. It would be good to know if it is a setting that users can tweak or if it is something buried deep in the code that we can’t resolve ourselves. @Manoj do you have any technical details to share about bug 9290?
VoWifi issue on FP6 appears to be carrier specific as you can see the last comment in the bug. You can ask the tester and developers in the issue if they need logs from your device.