*#*#4636#*#*
I went there messed with some GSM WCDMA settings. When I set it to GSM I can send text messages without error.
After reboot I am getting errors again but my friends can receive my messages.
Anyone know whats wrong? I think I need to reset my /efs. I do not have a backup however :/
I had a similar issue once before though I could recieve text but not send.
All I had to do was rewrite the SMSC number which is based off the carrier your with.
Related
Hi! I'm using the stock sms app. I have had zero trouble before with messages, but a couple of days ago my messages wouldn't just get sent. I can receive fine, but afted sending an error only pops up saying message not sent. I believe this is some sort of problem with my smsc number, because when I use Go SMS and type in my smsc number manually, I can send messages fine. Calls and internet are working.
When I call *#*#4636#*#* and go to phone information, the smsc box is empty and if I hit update, it just comes up with an error.
I think I accidently pressed update before this problem came up and the box said 00. Any help would be very much appreciated because I prefer the stock sms app to 3rd party ones.
Lookinen said:
Hi! I'm using the stock sms app. I have had zero trouble before with messages, but a couple of days ago my messages wouldn't just get sent. I can receive fine, but afted sending an error only pops up saying message not sent. I believe this is some sort of problem with my smsc number, because when I use Go SMS and type in my smsc number manually, I can send messages fine. Calls and internet are working.
When I call *#*#4636#*#* and go to phone information, the smsc box is empty and if I hit update, it just comes up with an error.
I think I accidently pressed update before this problem came up and the box said 00. Any help would be very much appreciated because I prefer the stock sms app to 3rd party ones.
Click to expand...
Click to collapse
I'm not sure if that is the problem, as my smsc field is empty and I'm not experiencing the same issue. What is your preferred network type?
WCDMA Only, but it seems I got it fixed. I didn't reaize that I had to encode the sms centers number. Working now
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
I had not had this problem until a few weeks ago, and i haven't changed ROMs, radios, or plan services in the time. I receive SMS as usual, EXCEPT from numbers such as 79710(Espn Alerts) or 32623(Pens Alerts). When i attempt to send a message to either number, i receive a message saying
Free Msg: Unable to send message - Message Blocking is active
I have called T-Mobile and nothing is being blocked they're saying. When going into *#*#4636#*#* and looking at SMSC number, it is blank, and if i enter a number or hit refresh and update it, it does not stay the same. When i re enter is is blank again. Has anybody experienced any of this? Any help would he appreciated
After several hours of troubleshooting and a hard reset, I've been told that the reason I am unable to SEND picture messages is due to a incorrectly configured "Short Message Center" number. All other functions (make/recieve phone calls, send/recieve text messages, browsing the internet, and recieving picture messages) work fine.
I have verified the APN settings are correct, and supposedly everything looks good on the carrier's end but I'm still not able to send picture messages. The carrier (Solavei, an inept T-Mobile reseller), expected this to be displayed after entering a code into the dialer app, but instead displayed on the most recently called number. (The code was *#*#4636#*#* which did not work). Any ideas on how to set this on the Motorola Atrix 2?
Android Version 4.0.4
Sys Ver 67.21.125.MB865.ATT.en.US
Forgot to mention that using another carrier's (Cellular One) SIM card on this unlocked phone with the correct APN settings is able to succesfully send/recieve picture messages on this phone, and that I am able to send/rec picture messages when using my SIM in another phone.
Update: I am able to send MMS messages using a 3rd-party app (Go SMS Pro), with a custom-set MMSC, which matches the MMSC in the APN settings. Does anyone know how this works?
Also, does anyone know if the ROM I used when flashing my phone could have known issues with particular MMI codes, (as apparently suggested HERE: http://forum.xda-developers.com/showthread.php?t=737594)?
Does anyone know how to remove the call back number on every single sms message I receive? Even if the person has it turned off on their phone it still shows up on mine when they send me a message. I would just use another messaging app because that fixes the problem but then I can send mms messages. I'm on a local carrier and can't find the settings to put in to fix this either. Any help is appreciated thanks.
*can't send mms I meant to say.