Jump to content

SMS/MMS issues


JWMaloney
 Share

Recommended Posts

Anyone else having issues with SMS/MMS recently? I've had an intermittent issue where all of my sent messages will get stuck in "Sending" state, and the only thing that will fix it is a reboot (also tried toggling airplane mode and forcing 3G unsuccessfully). Also had an issue this past Saturday where I didn't get any messages until I rebooted that evening (and then about 30 messages from 3 people all came in at once).

 

This is on a Nexus 5 using the default Google Messenger app. I had RCS enabled at one point but disabled it after this first started happening frequently. It doesn't seem to have had any effect either way. The issue also doesn't seem to be isolated to any specific cell site.

Link to comment
Share on other sites

I have had problems on my Nexus 6P with RCS enabled, its in poor coverage or highly congested areas.  I do an airplane mode to make the messages fail, then resend and everything appears to be fine

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Let me take a look tonight. 
    • Actually, I notice it says whole clusters were skipped because of invalid TAC values.  It says "File exported for inspection."  I do have Log Sites with Missing TAC checked. Robert
    • I was able to figure this out by looking at your diagnostic reports -- you're seeing n7 because your Galaxy A32 is reporting it natively as n7.. Samsung will have to fix that on their end unfortunately. Do the engineering screens report it correctly? I have an A32 test device but I have not seen it connect to n41 (or "n7") yet. If I do, I'll try to troubleshoot and nag Samsung. EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.
    • I appreciate the feedback today -- another new is SCP beta rolling out right now! It should resolve the force closes that started with yesterday's beta release; I also made additional improvements that hopefully(?) will reduce ongoing issues with overall app stability.
    • I'm noticing a spike in instability while driving around testing the app today also.. more freeze-ups than crashes, but it's probably all related. Hopefully any crash reports that are collected can shed some light on it for me. I'll be looking into it later tonight.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...