I was wondering if any of you with straighttalk reading this with an ATT Samsung infuse with the att sim could quickly hit *#*#4636#*#* then under phone settings scroll down and look for the smsc line and hit refresh and write down and post it for me.
I have been using straighttalk for the past couple of months and suddenly I don't have SMS anymore I can't send or receive. My phone does say message sent but no one is receiving it. I've tried deleting my messages, factory reset changing the smsc to the AT&T settings different messaging apps and I cant get it. Customer service says the problem is ony end but I'm not sure how it is from night to morning without any changes.
I'm running Scott's. 2/3/2012 build
** I am able to call and use the data
Like the title says.
BASIC INFO
Here's some basic info. I live in NYC, have t-mobile, have experienced the issue with with my Moto X (T-mobile - aka GSM unlocked) and in the past T-mobile HTC One. both running 4.4 and 4.4.2. Using the stock apps, no third party stuff.
THE ISSUE
My MMS have been hit or missed. They all show as sent on my Moto X but don't always get received (I confirm with the people I'm sending to & check "view details")
This has been going on for like 2 months. 2 days ago, I've been getting SMS really late. for example, receiving SMS 2 days later (I check the timestamps)
TROUBLESHOOTING
So far i've done EVERYTHING lol:
factory reset
3 moto x warranty exchanges
Tried using a T-mobile HTC One
reset app caches
tried not installing any (just factory apps and settings as a controlled variable)
tried different locations (with without WiFi)
sent MMS with images below 1mb limit and even smaller just to be safe
Using new SIM cards with EACH phone
I have concluded that T-mobile has network issues they refuse to acknowledge and I plan on leaving them for a better carrier, cheaper isn't better in T-mobile's case.
Any wanna offer some wisdom, Could someone help a brother out? Thanks in advance!
Motorola (along with my own testing) has confirmed that the stock messaging app has bugs for sending receiving MMS/SMS
I am having a smiliar issue with sms and mms. I am working on a S4 clone (w/ 3G only). It use to be able to send sms to other phones. Recently, it can only send to T-Mobile carriers only. I can receive sms, mms from any other carriers. Sometimes, I can rarely send sms and mms to other carriers. Maybe once in every 20 times. Most of the time, it says "Sending..." and then auto notification saying "not send". Sometimes, the auto notification are instant (pops up right after I hit send button). I am using the stock msg app. any idea? I triple checked my APN and it goes online fine.
I'm going nuts trying to figure out how to fix my MMS issues — maybe you guys can help. I have an unrooted N5 running 4.4.4 that is inconsistently receiving MMS messages (both photos and group texts). I'm currently using StraightTalk, though I was having the same issue with Cricket.
My APN settings are correct (from what I can figure), and sometimes I receive incoming MMS. I currently have Textra and GoSMS installed as my texting apps, with GoSMS currently as my default. Occasionally I'll receive an error in GoSMS that an MMS message was unable to be downloaded, and try as I may, I can never get the app to download and display it. However, if I open up Textra, the message will have come through there with no problem. So basically, unless I have 2 apps gathering MMS, I'll miss half of them. I only installed GoSMS after seeing it as a suggestion/solution in another forum - this was happening before I both installed. I was originally using Hangouts for SMS/MMS, which was having the same problem (and why I initially DL'd Textra).
I occasionally have issues sending out an MMS. It's a less frequent occurrence than the issues receiving, though it does happen.
I am thinking that if this was a network issue, the MMS wouldn't come through to my phone at all, so I've stopped trying to mess with my APN. Does anyone have any ideas on how to solve this?
I have Straight Talk too and been having issues with MMS i'm using 8sms. I have the old 3g sims card. what about you ?
breannesp said:
I'm going nuts trying to figure out how to fix my MMS issues — maybe you guys can help. I have an unrooted N5 running 4.4.4 that is inconsistently receiving MMS messages (both photos and group texts). I'm currently using StraightTalk, though I was having the same issue with Cricket.
My APN settings are correct (from what I can figure), and sometimes I receive incoming MMS. I currently have Textra and GoSMS installed as my texting apps, with GoSMS currently as my default. Occasionally I'll receive an error in GoSMS that an MMS message was unable to be downloaded, and try as I may, I can never get the app to download and display it. However, if I open up Textra, the message will have come through there with no problem. So basically, unless I have 2 apps gathering MMS, I'll miss half of them. I only installed GoSMS after seeing it as a suggestion/solution in another forum - this was happening before I both installed. I was originally using Hangouts for SMS/MMS, which was having the same problem (and why I initially DL'd Textra).
I occasionally have issues sending out an MMS. It's a less frequent occurrence than the issues receiving, though it does happen.
I am thinking that if this was a network issue, the MMS wouldn't come through to my phone at all, so I've stopped trying to mess with my APN. Does anyone have any ideas on how to solve this?
Click to expand...
Click to collapse
I just got my SIM card last month, so I'm pretty sure it's the new one.
thasarkastic1 said:
I have Straight Talk too and been having issues with MMS i'm using 8sms. I have the old 3g sims card. what about you ?
Click to expand...
Click to collapse
breannesp said:
I just got my SIM card last month, so I'm pretty sure it's the new one.
Click to expand...
Click to collapse
I'm currently having the same issue with a non rooted device.
I was originally with H20 (an AT&T mvno) and would have periodic issues with MMS. Both sending and receiving. I am using Google Hangouts.
I recently switched to Cricket (owned by AT&T) earlier this month (reasons unrelated), and have not been able to send or receive an MMS since. I have spent several hours on the phone with both Cricket and LG, even going into a store to have my SIM replaced. I came across this thread accidentally while looking for suggestions on the best way to do a backup before I try a factory reset as a last resort to resolve the problem.
APN has been verified correct numerous times and unfortunately, Cricket's cust service is next to useless. After two and a half weeks and numerous calls, I still have yet to hear back from a Tech Support rep. I'm not sure whose network straight talk uses, but I wonder if it's a network issue with AT&T subcarriers?
The most frustrating part is every time I talk to somewhat at Cricket cust service, they say that the Nexus 5 is not "officially supported" on their network and that it is probably a phone issue and try to sell me a new phone. When I explain that the Nexus 5 runs stock Android, they try and tell me that that might be the problem *SMH*.
Anyone else?
steelcity1 said:
I'm currently having the same issue with a non rooted device.
I was originally with H20 (an AT&T mvno) and would have periodic issues with MMS. Both sending and receiving. I am using Google Hangouts.
I recently switched to Cricket (owned by AT&T) earlier this month (reasons unrelated), and have not been able to send or receive an MMS since. I have spent several hours on the phone with both Cricket and LG, even going into a store to have my SIM replaced. I came across this thread accidentally while looking for suggestions on the best way to do a backup before I try a factory reset as a last resort to resolve the problem.
APN has been verified correct numerous times and unfortunately, Cricket's cust service is next to useless. After two and a half weeks and numerous calls, I still have yet to hear back from a Tech Support rep. I'm not sure whose network straight talk uses, but I wonder if it's a network issue with AT&T subcarriers?
The most frustrating part is every time I talk to somewhat at Cricket cust service, they say that the Nexus 5 is not "officially supported" on their network and that it is probably a phone issue and try to sell me a new phone. When I explain that the Nexus 5 runs stock Android, they try and tell me that that might be the problem *SMH*.
Anyone else?
Click to expand...
Click to collapse
Yes me too. I found out today that my G2 can't get MMS at all. I've tried tons of fixes and nothing seems to work.
No sure if anyone is still experiencing the MMS issues on Nexus 5 as I am. I have a stock, unrooted N5 running Android 4.4.4 on Tmobile. GoSMS is my default sms client. What happens totally randomly is that I COMPLETELY lose the ability to send/receive MMS picture messages (group messages that come in as MMS are unaffected). Once I lose MMS, ALL text I have which have picture messages attached change from viewable icons to blank images or "Xs". All MMS messages in go become white boxes that say "picture does not exist). It has not mattered if I have taken all other text clients off the phone and used ONLY Hangouts as the default, it still happens. This is the ONLY solution I've found to fix the issue:
1) Set Hangout as default sms client
2) Reset APNs to default (settings-->SMS-->Access Point Names--> hit three dots-->reset to default)
3) Go to main phone settings (Settings-->More-->Mobile Networks-->Access Point Names), reset to default
4) Select the APNs that your device normally uses (for me, its fast.t-mobile.com), set MMS Port to 8080 and save APN
5) go back into Hangouts, select the same APN (fast.t-mobile.com), set the MMS Port to 8080 and save APN
6) Reboot phone
Once its rebooted, if your MMS images are once again viewable in Hangouts, its fixed and you can send/receive picture messages again. You can now switch to whatever default client you chose. This has worked for me EVERY time to 'fix' the MMS issue, but what I have never figured out is WHY its happening and I can't pinpoint exactly when it started. I want to say the update to 4.4.2 may have triggered it, but I honestly can't recall. I know this wasn't ALWAYS an issue. If anyone else has any theories/ideas, I'm all ears. Its just a pain in the a** to have to reset the APNS in two spots and reboot every time this happens (I think I read that Hangouts' APN settings can override the system APN settings so that's why I reset in both spots). I've tried ONLY resetting the main phone's APN and it didn't fix the issue.
breannesp said:
I'm going nuts trying to figure out how to fix my MMS issues — maybe you guys can help. I have an unrooted N5 running 4.4.4 that is inconsistently receiving MMS messages (both photos and group texts). I'm currently using StraightTalk, though I was having the same issue with Cricket.
My APN settings are correct (from what I can figure), and sometimes I receive incoming MMS. I currently have Textra and GoSMS installed as my texting apps, with GoSMS currently as my default. Occasionally I'll receive an error in GoSMS that an MMS message was unable to be downloaded, and try as I may, I can never get the app to download and display it. However, if I open up Textra, the message will have come through there with no problem. So basically, unless I have 2 apps gathering MMS, I'll miss half of them. I only installed GoSMS after seeing it as a suggestion/solution in another forum - this was happening before I both installed. I was originally using Hangouts for SMS/MMS, which was having the same problem (and why I initially DL'd Textra).
I occasionally have issues sending out an MMS. It's a less frequent occurrence than the issues receiving, though it does happen.
I am thinking that if this was a network issue, the MMS wouldn't come through to my phone at all, so I've stopped trying to mess with my APN. Does anyone have any ideas on how to solve this?
Click to expand...
Click to collapse
two messaging apps is like,
having two firewalls apps on one computer,
their both getting in the way of each other..
---------- Post added at 09:48 PM ---------- Previous post was at 09:43 PM ----------
sitinon327 said:
No sure if anyone is still experiencing the MMS issues on Nexus 5 as I am. I have a stock, unrooted N5 running Android 4.4.4 on Tmobile. GoSMS is my default sms client. What happens totally randomly is that I COMPLETELY lose the ability to send/receive MMS picture messages (group messages that come in as MMS are unaffected). Once I lose MMS, ALL text I have which have picture messages attached change from viewable icons to blank images or "Xs". All MMS messages in go become white boxes that say "picture does not exist). It has not mattered if I have taken all other text clients off the phone and used ONLY Hangouts as the default, it still happens. This is the ONLY solution I've found to fix the issue:
1) Set Hangout as default sms client
2) Reset APNs to default (settings-->SMS-->Access Point Names--> hit three dots-->reset to default)
3) Go to main phone settings (Settings-->More-->Mobile Networks-->Access Point Names), reset to default
4) Select the APNs that your device normally uses (for me, its fast.t-mobile.com), set MMS Port to 8080 and save APN
5) go back into Hangouts, select the same APN (fast.t-mobile.com), set the MMS Port to 8080 and save APN
6) Reboot phone
Once its rebooted, if your MMS images are once again viewable in Hangouts, its fixed and you can send/receive picture messages again. You can now switch to whatever default client you chose. This has worked for me EVERY time to 'fix' the MMS issue, but what I have never figured out is WHY its happening and I can't pinpoint exactly when it started. I want to say the update to 4.4.2 may have triggered it, but I honestly can't recall. I know this wasn't ALWAYS an issue. If anyone else has any theories/ideas, I'm all ears. Its just a pain in the a** to have to reset the APNS in two spots and reboot every time this happens (I think I read that Hangouts' APN settings can override the system APN settings so that's why I reset in both spots). I've tried ONLY resetting the main phone's APN and it didn't fix the issue.
Click to expand...
Click to collapse
**com.qualcomm.qcrilmsgtunnel** is your gn0me in the engine;
where sms/ mms is *natively* transported via the native phone functions & hooks, hangouts provides the same functionality *over the top* of the carrier's route, strictly IP; call it hi-jacking in a sense, that's what you en-able hangouts to do on reboots, hijack those functions..
*SIM toolkit
*Phone/Messaging storage
*Phone
is what com.qualcomm.qcrilmsgtunnel is tied to, which hangouts, isn't..
Last update to hangouts screwed up my APN setting. ?
Sent from my Nexus 5 using Tapatalk
Idk how but messaging is working for me
Way to troll an old thread for no reason
Sent from my Nexus 5 using Tapatalk
Wife has an unrooted VZW Droid Mini XT1030. running JB (not sure which version, will check). KitKat 4.4.4
recently have been having intermittent texts not delivered. no error message on sending. they just never get there. in a back and forth conversation 1 or 2 messages out of 10 might not arrive. Happens for multiple recipients on different carriers. MMS is fine. Using default Android messaging app.
all messages show up on VZW's online message log (website login from PC, so the message hits their network somehow.) Posted support request via VZW forums. so far we've verified that a reboot doesn't fix it.
Only thing I notice that seems odd is under message details, the last line for all sent text messages is : "Cause Code: Addr.Vcnt., 0"
Googling brings up a number of old threads back in the Android Gingerbread days, people were often getting that as an error message when messages wouldn't deliver. Also, noticed a number of threads with intermittent delivery issues, similar to mine, and they were almost all Motorola devices of one flavor or another.
Anyone know what that message actually means? I've seen several quite contradictory explanations. Think it's relevant? A red herring? At this point I'm not even sure the problem is the phone vs. something with VZW. Could something on my phone be intermittently messing up delivery?
Second, recommend troubleshooting? If it's the phone, I figure a factory reset's in order at some point. If that doesn't help, other suggestions? Assuming the mini version is right, root/reflash? If it's not the phone... any suggestions for resolving? I was going to port to a VZW MVNO, but if it's a network issue, decent support goes away at that point...
EDIT: correction, running KitKat 4.4.4
Could it be a sim issue? Pull the sim card out and put it back in.
Sent from my XT1254
Will try.
Also, on KitKat not JB
I have an Axon Mini imported into the US running on AT&T. I had to get a new sim card since my Lg G3 sim card was too big. When I went to the att store, he set my APN settings and no text messaging worked at all. People sent me messages, but nothing came through. So, I went through and added my APN settings from my Tmobile LG G3 running on AT&T. I can now receive messages, but when I receive images it says there was an error downloading and the same issue when trying to send. When I get on Wifi it works fine and I can download the older messages. I have attached screens of all my settings. Since this is my first dual sim phone, I was wondering if I did anything wrong?
shaxs said:
I have an Axon Mini imported into the US running on AT&T. I had to get a new sim card since my Lg G3 sim card was too big. When I went to the att store, he set my APN settings and no text messaging worked at all. People sent me messages, but nothing came through. So, I went through and added my APN settings from my Tmobile LG G3 running on AT&T. I can now receive messages, but when I receive images it says there was an error downloading and the same issue when trying to send. When I get on Wifi it works fine and I can download the older messages. I have attached screens of all my settings. Since this is my first dual sim phone, I was wondering if I did anything wrong?
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. For the best results, please ask your questions here:
Android Q&A, Help & Troubleshooting
Good luck!