NOT RECEIVING TEXT MESSAGES

[Oreofudge]

For over a month now I've been having issues receiving text messages in a timely manner in Note10+. I need to daily contact Sprint to have them troubleshoot, refresh, etc and be able to receive messages again for a couple minutes or hours, and then stop receiving messages again. Sometimes I send a text to myself to unclog or prepare to receive messages I know are coming, but it does not work all the time. Had SIM replaced twice and issue persists. Had phone replaced, and issue persists. Stopped using Samsung's Messages app and stated using Google's and issue persists. Had raised a ticket with Sprint, although nothing wrong with their network as they say, and are still checking things on their end, issue persists. Settings on phone are kept as suggested by Sprint (Mobile network set to LTE/CDMA, Rich Communications settings disabled), and issue persists. Walked into A uBreakiFix and tech suggests it might be Sprint, since issue repeats itself on two same model phones, but received a year apart, he suggests it may be a phone model issue, that I should try with a different device, despite the hassle it is. Any of you out there experiencing something similar, if so, have you solved it? please let me know, thanks.

[latoplano_6_625]

does it happen on both sms and mms? or just mms?

[Oreofudge]

...for sure it happens with SMS, not sure about MMS. Today Sprint called after having checked things on their end (network-wise, towers, etc), and confirmed they did not find anything that would prevent a message to reach my phone. They went thru the troubleshooting process for my phone, and then suggested that I should get the device checked further. This is a bummer!

[latoplano_6_625]

try download samsung members app and submit a ticket.

After you download click on + sign, then click send report.

they might be able to tell if its the sprint server issue or your device's issue.

[Oreofudge]

...thanks for the tip, I'll do that.

[Oreofudge]

...forgot to update on this, I did follow your recommendation and ran a test that got uploaded to Samsung; they responded back saying that no issues on their end were found, and to contact Sprint, because it was an issue on their end. At that point I had given up, since Sprint had already run their test and came up empty handed. But your suggestion taught me about this new way of forwarding info about your phone to the techs, thanks.

[userpeE3P8cJWF]

I've got the same problems (note 10+) and went through the same steps. Nothing works except to stay on cdma network. the problem first started after an update i did first week of Sept 2020. now they are speaking of shutting cdma down this upcoming year on t-mobile. hopefully this gets fixed in an android update due soon.

[Oreofudge]

...I was told to keep in LTE/CDMA by Sprint, who recommended you to stay on CDMA? ...are you still experiencing the issue? what message app are you using?

[userpeE3P8cJWF]

Sprint told me to do the same thing but it still doesn't work that way even after resets, new sim cards, and troubleshooting. Sprint suggested I get a new phone through them because I purchased mine unlocked through Amazon. So I have decided to just stay in cdma until some software update comes out that they say should also fix the problem but they don't know when. I'm assuming they are referring to android 11 since this is what the internet seems to speak of. My phone worked fine for a year until an update I installed on Oct 5th 2020.

[Oreofudge]

...in a way it is a relief to find someone with the same issue I have, and it is surprising you technically were told the same thing I was told. I did get a new phone for free through Samsung's Protection Plan, since it is the insurance I have on it, so discarded the device itself being the issue. I also think for sure it was an update, and the dates you mention matches when my issues started. So keeping your phone under CDMA let your messages come in in a timely manner without having to do tricks on your phone? if so, I'll switch as well and see if it works for me. Thanks again for your input.