Hi, I’m trying to resolve an issue with VoLTE (4G calling) on my Fairphone 6.
I have Happybytes and are using my FP in Norway. Norway is closing down their 2G network (3G already closed) by the end of 2027. Many providers have already done so. Which means that 4G calling or VoLTE is required. Now, here is the issue. Whenever I activate VoLTE I am able to receive and transmit calls, however, when I recive a call, the caller ID is just saying Unknown. If i try the same, but with VoLTE deactivated, the number/name displays according to my contacts.
I’ve tried checking with my mobile network provider Happybytes, and everything seems to be working there. Is this a known bug with /e/os? or are there any configurations that need to be implemented?
I really need to have this in place well before 2027, or else my phone is ultimately bricked. Any suggestion or help towards resolving this issue would be greatly appreciated, and I am certain, that my combination of phone + service provider is not the only one having issues.
Maybe you can check the access point APN parameters that you are using and if that corresponds to the specifications of the carrier. Some rare carriers may have automatically configured APN with a slightly wrong parameter configuration
APN settings are according to the setup. Internet and MMS is also confirmed to work. To me, it seems like there is some missing IMS profiles for my network provider provided by software in Fairphone. Either by /e/os or by Fairphone. Not sure how this configuration bit works.
Edit, speculative, this warning from the install page
Warning: Make sure that you can send and receive SMS and place and receive calls (also via WiFi and LTE, if available), otherwise it will not work on /e/OS as well. Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.
hints, perhaps, that some aspects of IMS registration are not fully covered within AOSP (??).
Edit 2. Maybe not directly connected but the AOSP relationship with carriers “benefitted” from this change quite recently
I think your onto something here. I couldn’t set my MCC and MNC settings since they where effectively removed in Android 15. Based on what I found online, people seemed to think they where redundant settings, but maybe not? And from what I gather the settings provided from Happybytes is not in the list you provided.
I should have mccmnc_tuple: "24215". Possibly on Telenor since they’re the underlying network provider here. Could this be the issue?
As I understand it, the carrier (and thus their “paths”) is now “defined” by their unique name [1] so that any technical definition of paths by MCC and MNC are simply excluded from what we need to know or to define at user level or even at build level.
So, no, I think the issue of your last paragraph is not problematic (but perhaps it would have been relevant even really quite recently).
Is there anything that can be done on my end to fix? or must I wait for software updates from AOSP to cascade all the way into /e/os? I’m really, really, not well familiarized with this development stack, I just tried to debug this issue.
Yeah, I’ve checked and it says MCC: 242 and MNC: 1, which is not what I should have. According to Happybytes I should have MCC: 242 and MNC: 15. However I also know that Happybytes utilize the Telenor network, so it could just be the MNC of the connected tower?
Could the wrong MNC somehow cause this issue I’m having?
Also for info: IMS status says IMS registration: Registered and Voice over LTE: Available.
It seems to me that this has to be a problem originating from Happybytes, in that they’re not delivering Caller ID over VoLTE. Are you using a physical SIM, and are you able to try it in a different VoLTE-capable phone?
Question: Are you confident that your phone is actually using VoLTE when you have it enabled? You can tell by observing whether the network indicator drops to something other than 4G/LTE/VoLTE during a call.
How are you switching? Might it be that Preferred network type could offer a different way of achieving something which will work?
By toggling 5G on/off, and also checking phone information if it actully enabled VoETL or not.
Question: Are you confident that your phone is actually using VoLTE when you have it enabled? You can tell by observing whether the network indicator drops to something other than 4G/LTE/VoLTE during a call.
It shows 5G while in a call, and I am able to use mobile data during a call session. Also the incoming call shows HD. Although “Unknown caller ID” appears as usual. So I’m pretty certain VoLTE is actually enabled. But yes, I’m not the only one with a problem, I’ve seen many of these posts, but they are all getting closed without being resolved it seems.
Maybe the Caller ID issue is with 5G instead of 4G. Have you tried disabling 5G and then testing for Caller ID? (I dont know much about 5G, so I’m just hypothesizing here.)
EDIT: Searching for “no caller ID over 5G” turns up several reports related to various networks and phone models, Androids and iPhones.
It might be more useful to raise the issue with Fairphone (the company) and with Happybytes/Telenor, as it seems to be something that they need to work out between themselves.
Both have been informed. Happybytes/Telenor says they have everything configured at their end. Still waiting for response from Fairphone. Just want to make sure this isn’t a known OS bug.
I can’t help yet, but I just wanted to add in that I am having this exact same problem with the UK provider Three.
Three only have connectivity over 4G or 5G, their entire 3G or below connectivity was shut down a while ago. I’ve been suffering this problem for quite a while now, first on my Fairphone 3+ with lineage, and now with Fairphone 6 with eOS.
I’ve have spoken to Three who say everything is configured on their end, and I’m sure there must be an old thread on a fairphone forum by me talking about this somewhere, but I’ve had no success. I saw this post was relatively recent, so I thought I’d join in and see if we can get some movement!
