United States SIM unrecognized (/e/OS 3.7.2 on FP3)

I am currently in the United States: when I slotted the physical microSIM card I have here (carrier: Tello, a T-mobile MVNO) into my FairPhone it works for a while (~10 minutes), then the phone reports that there is no SIM card inserted. If I turn the phone off and on again, it still reports that there is no SIM, but if I take the battery out, physically remove the SIM and then slot it back in, when I turn the phone on it gives me another ~10 minutes of normal functioning, before cycling back to not recognizing the SIM. The same phone and same SIM card worked fine when I was last here, 9 months ago.
It would seem not to be a problem with the SIM card itself, since it works fine with a different phone I own. It also doesn’t seem to be a problem with the individual SIM slot, because the same behavior occurs whether I put the SIM in one or the other slot, and, more importantly, does NOT occur when I put in my Italian SIM card (carrier: CoopVoce, a TIM MVNO), which still connects over here through roaming. Anyone seen similar behavior? Suggestions??

On a FairPhone3, running /e/OS 3.7.2

I can’t say for sure, but it sounds like Tello (or T-mobile) is disabling it, maybe after the network registers the IMEI.

I’m a little surprised it works for even 10 minutes, as the Fairphone 3 lacks some LTE bands recommended for the T-mobile network.

Expand the “Network” section to view frequency bands of the phone:

Compare: https://www.t-mobile.com/support/coverage/t-mobile-network

See “Will my phone work with Tello?” in the FAQ here: https://tello.com/bring_your_own_phone

Still, I don’t think anything has changed with that network since your previous visit (assuming it wasn’t very long ago).

Have you tried checking the IMS registration status by dialing *#*#4636#*#*?

You may need to talk to Tello’s customer service to see what’s up.

3 Likes

I will add, also, that in the past, whenever I used Tello’s online IMEI checker to see if my Sony would be approved, it was rejected… even though T-mobile itself and other T-mobile MVNOs approve it, as it has fully operational VoLTE with T-mobile’s network, and all the required LTE bands.

Try checking your IMEI here again: https://tello.com/bring_your_own_phone

2 Likes

Hi @Taurus, thanks for the reply!

That’s what’s stumping me! I was wondering if it was a software update or something-- The IMEI tool on Tello says my phone is good to go with a physical SIM, which is what I have. The bands 4 & 5 for 4G overlap between T-Mobile and the FP3 (but even if they didn’t, wouldn’t the phone say that there was no signal, as opposed to no SIM in the phone??).
Not entirely sure what ‘IMS registration’ is (sorry! I’m not technical!): when I dial *#*#4636#*#* I get a Testing menu with three options: Phone information, Usage statistics, and Wi-Fi information. When I choose the first, it gives me info for Phone 0 and Phone 1 (presumably the two SIM slots?), but it lists nothing beyond the IMEIs, and under IMSI it says: Unknown.
Thanks for the thoughts, though: it looks like my next step is talking to the Tello people…

Perhaps bring this up with the carrier. This is the IMS registration unique identifier. On my FP3 for instance the long number starts with my MCC, MNC.

The way that APN are set up changed in AOSP ~early 2026 so conceivably your SIM / phone relationship needed to update.

There’s a list of troubleshooting tips here No more mobile data - #8 by aibd

1 Like

Thanks, @aibd, this is good to know:

I am going down an APN rabbit hole, and will contact Tello shortly. With respect to your tips in the linked post, and in particular:

I am having trouble because when the FP3 indicates there is no SIM in the device there doesn’t seem to be a place to modify the APNs, that is to say, the options in Settings > Network & internet are greyed out…
Maybe I’m not looking in the right place??

First of all, do you see an error in existing APN compared with published?

If yes and you want to correct it you would hope to use the top right + button on the APN screen. (This is generally recommended over Edit an “existing”).

Hopefully your APN will Save … and the save will be (semi) permanent. You have to subsequently select your “new” APN. Hopefully you will be online with Wi-Fi and the setting will fully reset on reboot.

The need to remove SIM might happen if your “new” APN was not adopted (perhaps APN reverted to “old”). I guess the Remove SIM idea is an advance on the above … aiming to adjust the values such that the “wrong” one is overwritten if say the “wrong” one existed on the SIM card.

Well, that’s just the thing, @aibd : since the FP3 says ‘No SIM card - No service’, there seems to be no option in the Settings app for me to even view what the current APNs are. Even though I am on wi-fi, the Calls & SMS and SIMs options under Settings > Network & internet are greyed out, and it was under one of those (if memory serves) that one got access to the APN controls. So, if this is the problem it’s a sort of snake biting its own tail (no SIM service because problem w/ APNs, but no access to APNs because no SIM detected…).

Hmmm, did you use

Settings > :magnifying_glass_tilted_left: Search: APN

already?

I tried this, removing my SIM card, as you say, no APN found.

In one / some of the AOSP “Connectivity” pages I did see a reference that might suggest (reading between the lines) that particularly MVNO may find themselves having to reissue SIM cards for 2026. This has cropped as a solution two times, I think, on the forum.

1 Like

Yes, I did use the search function, same result.
I actually also used one of the small windows of activity of the SIM after I manually re-slot it to reset the APNs to default and chose the carrier’s (Tello) ones from the menu, and yet the same behavior followed, that is, eventually the FP3 reported ‘No SIM - No service’.

This is sounding increasingly likely, and I will try it next, when I get through to Tello support.

Just to wrap this up, I contacted Tello support, and they did a network reset for my account, which seems to work (3 days in now, so far so good…). So, looks like it was a service provider-side problem all along.
Thanks to @aibd and @Taurus for your help!

2 Likes