Foundation.e.mesaage - missing "messaging center" number

I’m having trouble receiving SMS texts. ISP suggested to try an alternate messaging center number.

I cannot find this in stock messaing app settings anywhere.
I tried another app from fdroid and same thing.

See image below for reference.

Would appreciate if anyone can check if this is shown for you. Thanks.

I’m suffering the same problem after switching my carrier to Mint Mobile (USA) which uses the T-Mobile network. The phone is a OnePlus “dre” running /e/os 2.9 with a physical SIM.

Calls work both directions but SMS only works outbound. I’m going to call my carrier today and see if they can help me. Hopefully they won’t ask me to mess with the SMSC number because I don’t see it anywhere on my /e/os phone.

Fortunately my /e/os phone is a secondary so I’m not under any pressure to resolve the issue. My primary phone is a Motorola Razr+ running stock Android with T-Mobile and I can see the SMSC number under Messages->Settings-> Advanced, but I don’t see anywhere to modify it.

Funny. My device is also DRE OnePlus Nord N200.

I was getting incoming SMS but suddenly stopped gettng them.

1 Like

Hello AnotherElk,

Thanks for your detailed response.

I reset network settings to default already.
I had my carried provide me with a new physical SIM.

SMSC field is empty.
Got update error…
But then number was added.
I confirmed is the correct value for my carrier.

I checked the SMSC on my phone using the *#*#4636#*#* menu. It’s correct. Both Mint Mobile and T-Mobile use the same number;

“+12063130004”,145

I saw a post on XDA Forums stating it’s an obscure and uncommon provisioning problem that can occur on the carrier’s end. It was mentioned to try sending yourself a text then a text including a pic to force the provisioning.

Since Mint is on the T-Mobile network, if the above doesn’t fix it I’m going to try using the T-Mobile APN on the Mint Mobile phone. I read one post where someone said to try that.

If I can’t fix it myself, I may be in tech support hell with my carrier because it sounds like an issue with provisioning they rarely see. I guess if all else fails, I’ll get a new SIM card with a new number.

Hey Craig, I tried texting myself w/o any luck.

My provider told me exactly the same, a provisioning problem on their end which they are investigating.

Something else for you to check, see if you get notified on voicemails. I’m not.

Yeah I don’t get voicemail notification either.

Your provider is probably assuming there’s no issue with the phone or software on your end so they would have to look at provisioning to rule out anything on their end.

So I have two SIMs and two different accounts, one with T-Mobile and one with Mint Mobile. The T-Mobile SIM is my primary number that runs on stock Android and the Mint Mobile SIM is my secondary that runs on /e/os. I put the primary T-Mobile SIM in the /e/os phone and the problem persists. The T-Mobile SIM has no issue on the primary stock Android phone.

So it looks like it’s not a problem with the carrier. It’s something weird with /e/os or there’s some hardware issue with the phone. I’m kind of at a loss at what to do now. I’ll have to try something on the software side. Maybe try a different message app or a different OS altogether.

Since we are expriencing the same exact problem, on identical devices, we must rely on each other for a solution?

Is that how it goes @Manoj ?

This issue has been seen before based on a post I found in XDA Forums. Unfortunately cycling the SIM off and on didn’t resolve it. At this point I’m probably going to try flashing the phone with LineageOS to see if it makes any difference.

In general, this is how it goes … Report an issue

1 Like

Have reported a few issues.

They are sitting there in the gitlab queue aging for months without any attention.

Issue created.

1 Like

So I can’t install LineageOS because it’s firmware dependent on Android 12 and my N200 is on Android 14. Taking an N200 back to the stock OxygenOS on Android 12 is not a trivial task

I Found this post on XDA forums which makes a couple points, firstly there’s a case of someone having trouble receiving SMS on LOS. Secondly the post provides a way to take the phone back to stock Android 12.

The downgrade process outlined in the post is a bit involved, but it’s the only way to do it. If I go back to stock I’ll be able to confirm the SMS issue is software related.

I have a feeling it’s an AOSP issue since it happens in both /e/os and LOS. If that’s the case then the issue will never get fixed because the phone is EOL. Not being able to receive SMS renders the N200 a paper weight. Though it’s not a pressing problem for me as my /e/os phone is a secondary and I plan to buy a new one to run /e/os next year.

BTW, those people at LOS are harsh. I tried to get some LOS support at their discord channel. I only got rude and unhelpful replies. Plus Discord seriously sucks as a support platform. Reddit is better, but it’s Reddit. I don’t understand why they don’t set up a proper forum. Those are the best for community support. /e/os community support is a night and day difference from LOS.

I can confirm issue is DRE.

Used a BLU phone.
Switched SIMs between phones.
Incoming SMS work -only- on alternate device.

LOS claim the issue has been fixed on their latest release.

https://xdaforums.com/t/rom-official-dre-15-lineageos-22.4731692/

S.O.S. @Manoj urgently need to expedite release of new e/os based on LOS 22.x

Can’t get SMS for 2FA purposes for both job and perosonal matters

Have passed the links to the development team to evaluate and add in the code if possible.

Thank you.
Keep me posted if I can be of any help!

The LOS fix is in A15 or LOS 22 and should be coming as part of the A15 builds we should be releasing towards the end of this month.

3 Likes

Wow that is amazing news.
Looking forward to this.

Thank you Manoj and dev team!!!

That’s good to hear there’s a fix for this issue coming soon. However I killed my n200, dead as a doornail. I went to take it back to stock Android to try LOS partly because of this issue. I had to use EDL mode on this particular phone with some screwy software from OnePlus. It threw an error during the process which completely killed the phone.

Anyway I have a Pixel 7a coming in the mail, should get it tomorrow actually. Though I’m still going to try LOS because I want to try it. Pixels are hugely easier to take back to stock, just fastboot flash the image from Google.

Hey man,

So sad to hear about the N200.
Post your issue in xda, I’m positive you’ll get help to unbrick it.