Added a comment on github bug 9290 asking for troubleshooting steps from the devs.
I am unable to access the link you provided. Also I cant find it manually entering issue Id 9290 in e/ gitlab. Is this item maybe not public?
It is marked as confidential, so perhaps not open to everyone. Thereās only one device log file I uploaded. I donāt know if the devs even looked at the log or not, they didnāt even say. I need to talk to the devs to confirm what else they want to check. The only thing the devs have said is āwifi calling works fine on this one particular network in India that we testedā so their testing methodology leaves a lot to be desired. For example, if they asked me to review my device logs and look for specific wifi calling-related events, or lack thereof, then that would be much more constructive and we might actually find out why it isnāt working. @Manoj can you ask them to improve their communication with me, please?
Have passed on your comments to the team. They will get back to you on the thread in Gitlab
Yes, sorry, I misspokeā¦ I meant both VoWiFi and VoLTE are were performing on my FP6 with /e/OS on the carrier āSalt.ā (Switzerland).
Im also with Sunrise and did try e sim and physical sim (very rƩcent one). None of them worked for vowifi. I also have the poor signal problem.
I sometimes receive SMS hours later (really painful for double authentications). The āsolutionā i found is to make a phone call whenever i need to receive a SMS (it boosts signal reception and i receive the SMS). Not really a fix and really annoyingā¦
And my FP6 (which was on e/os 3.6 official back then, 3.7.3 now) had been repaired and motherboard replaced. Still no Vowifi nor SMS reception without having to pass a phone call. Bought it with e os preinstalled so not possible to try with Google android. During the repair of my FP6, i used my FP4 with e os 3.7.1 official Android 14. There was no vowifi but i had no problem with SMS reception or poor signal (same physical sim from sunrise). But the FP4 was on Google Android when purchased.
New e os version v4.0-a15 changed nothing.
Still got :
- No vowifi
- Bad signal reception (calls go directly to voicemail and sms received hours later) => almost convinced it is e os related since people in my home with the same carrier (Sunrise, Switzerland) have no problem. I tried e sim and physical sim. And got brand new motherboard (got charging problems that ābrickedā the phone)
@kilou i can confirm the vowifi issue is on the carrier side.
I tested my fp6 (e os 4.0) with a Coop Mobile sim (on Swisscom network) and vowifi was working.
@manoj I dont know if this has to be resolved on e os side or Sunriseā¦
1 Like
There is an issue for this in Gitlab which is awaiting development. The creator has marked it as confidential as it contains logs.
I created Bug 9290 for this issue which is āawaiting developmentā with what appears to be a deadline of 19th July 2026. I have requested technical details of what might be causing the issue however havenāt had a response yet from the dev assigned to this bug. What I can say is that my physical SIM with the same physical handset and with stock FPOS android installed, has functional wifi calling, and e OS up to and including 4.0 doesnāt, with the same physical SIM and handset. Multiple other brands/types of phones work with my SIM on my carrier without issues. Once the developers get back to me Iāll post the technical details, hopefully they can enlighten us about why it is happening and whether it is something missing in e OS for my specific carrier, or whether it is something else. Donāt know yet.
The commit by the developers added the following APNs, which are specific to Telstra in AU:
mnc="01"
carrier="Telstra Broadband"
apn="telstra.internet"
password=""
authtype="0"
protocol="IPV4V6"
roaming_protocol="IP"
type="dun"
user=""
user_editable="true"
user_visible="true"
/>
<apn
mcc="505"
mnc="01"
carrier="Telstra Internet"
apn="Telstra.wap"
type="default,supl"
carrier="Telstra IMS"
apn="ims"
authtype="0"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
type="ims"
user_editable="false"
user_visible="false"
/>
<apn
mcc="505"
mnc="01"
carrier="Telstra Internet"
apn="telstra.wap"
password=""
type="default,supl"
user=""
authtype="0"
protocol="IPV6"
roaming_protocol="IP"
type="default,ia,supl"
user_editable="true"
user_visible="true"
/>
<apn
mcc="505"
mnc="01"
carrier="Telstra MMS"
apn="Telstra.mms"
apn="telstra.mms"
authtype="0"
mmsc="http://mmsc.telstra.com:8002"
mmsport="80"
mmsproxy="10.1.1.180"
protocol="IP"
roaming_protocol="IP"
type="mms"
user_editable="true"
user_visible="true"
/>
<apn
mcc="505"
mnc="01"
carrier="Telstra MMS"
apn="telstra.mms"
mmsc="http://mmsc.telstra.com:8002"
mmsport="80"
mmsproxy="10.1.1.180"
password=""
port=""
proxy=""
type="mms"
user=""
carrier="Telstra XCAP"
apn="hos"
authtype="0"
protocol="IP"
roaming_protocol="IP"
type="xcap"
user_editable="false"
user_visible="false"
/>
<apn
mcc="505"
The only Work item I see for Sunrise Switzerland is
which links to Problems with phone calls and text messages.
1 Like
Those are exactly the issues Iām having aside from the voWifi. Hope this will be solved soon as the LTE switch āfixā is really not a good oneā¦
I had a long discussion with technical support of Sunrise. They do not consider the Vowifi nor the missed calls/sms as a problem on their side. For them, everything is in order by them and they wonāt be investigating any further. Even when āthreateningā to cancel my subscription, they kind of donāt care at allā¦
I think it would require someone to draw attention to the possibility that the AOSP āpresetsā for Sunrise APN should be reviewed.
I suggest one way to do that would be to add your case to the above Sunrise work item including a link to #9290 (while this link is ānot foundā to readers, the link is active and visible to devs).
- Edit, I have made such link, but actual user comments are much preferred.
1 Like
Hello @Fibo16 and @aibd, I would suggest that gitlab issue #9269 needs to be updated to specifically mention that it is specific to your carrier āSunriseā. Thatās what I did with #9290, as it is specific to Telstra in Australia and the devās fix was to specifically add Telstra APN info into e OS (but yet to be confirmed as fixing it). The other thing I did was reproduce the issue on the device so the most recent logs show the issue, and then immediately capture a āadb logcatā log output and copy and paste that āadb logcatā output into the gitlab issue, in your case #9269. That way the devs are able to specifically focus on fixing issues with the specific carrier āSunriseā. As they have now seen a carrier-specific VoWifi issue with my carrier, it may just be a rinse-and-repeat process to fix the next affected carrier, in this case, Sunrise. Hope this helps!
1 Like
Iāll try to do that when I have some time, which might be very rare in the upcoming weeks/monthsā¦ Especially the logging part @FP6User mentioned.
The gitlab comment I could make but logging not very sure Iāll have the spare time
There is another user there, @Jotufo I think, offered to take logs. I suggest initially to try to give full info of your experience and offer to take logs if requested. A work issue is likely to see traction if there is user activity.
Incidentally as I understand Sunrise offer 2 plans with and without MMS. It will be important that users are able to Select their correct plan from the /e/OS APN page. I suggest you mention the plan you use and that you have been successful in selecting it from the APN page ( ā¦ or any problem in that area).