I recently updated my Defy to the latest CM11 2014-07-25 build.
Everything seems to be great, but I realized that I cannot send SMS anymore, whenever I send an SMS to any number I get "Message Not Sent" error immediately. I am able to receive all SMS without any issues.
I did find related threads for other phones with CM11, which suggest to disable voice+, but there is no voice+ setting for the Defy build.
Does anyone else face similar issue ?
Anyone has any solution to this ?
No one else faces this issue? Today I updated again to the latest 2014-07-31 build and I still cannot send an SMS
Check SMSC from the dialer hidden menu (dial *#*#4636#*#*)
Sent from my Nexus 5 using Tapatalk
My defy use CM11 2014-08-24 nightly.
I get the same issue with "Message Not Sent" error.
But i can receive all SMS without issues, too.
After checking SMSC number. My outbound SMC works fine now.
You could check it with your telecom, or just google it by "SMSC number <your telecom company name>".
Hope it is helpful for you.
Related
Is anyone experiencing timestamp issues with their Hero?
I sent an SMS at 8.20 am, and when I got the reply at 8.23 am, it shows the message arriving at 8.13 am, and is displayed above my message in Messages.
Does anyone know of a fix for this?
Apparently fixed in new Dream/Magic ROMS that are just out http://www.htc.com/ca/SupportDownload.aspx?p_id=270&cat=2&dl_id=653.
Haven't found Hero ROM yet, but assuming it has similar fixes.
Hey, thanks for the quick reply!
I've just been doing some testing and here's the weird part -- I don't get timestamp issues if I send and receive SMS messages between 2 SIMs on the same network. But if I receive SMS messages from other operators, the timestamp is off by a few minutes.
This has me wondering if my operator's SMSC's clock is off. Will have to check
Hey guys,
I'm having some issues here. When receiving sms, the senders number doesn't always appear. Instead, it shows the first word of the SMS as the sender.
This happens when the length of sender number is less then 5 digits e.g. if you receive a text "test message" from 224 or 2244 then instead of showing 224 or 2244 as sender's number, it will show "test". I don't know what these kind of number's are called in other countries but we call it SHORTCODE. I've also heard people calling it SNO. Normally these messages are sent from the mobile operators or VAS providers.
No matter what I do, I can't see the sender number. I've tried using Handcent and ChompSMS. I've checked the message details etc but nothing helped. I've even tried using different ROM's. Currently I'm using Cyanogen's latest ROM.
I hope someone out there knows how to solve this problem and will help me as well Thanks in advance.
Guys! Has anyone else faced this problem? Looking forward to your replies...
I haven't rooted but when I used to have problems with custom builds on my g1 I would usually just wipe and flash...that fixed my problems almost every time
I had this problem even in the stock ROM. It's not specific to custom ROM.
With the nightly from 12/5 for this ROM installed (I would post there directly but I can't!):
http://forum.xda-developers.com/showthread.php?t=2383143&page=400
Everything is working well, but I can't send an SMS from Hangouts to a 5-digit number (specifically, Discover card's alerting service). I instantly get a force quit from com.android.phone immediately.
Anyone know if this is specific to this ROM or a KitKat problem, or if there are things I can do to get around that?
I have been unable to send or receive MMS using Textra or Messenger. I restored a month old Nandroid backup and the ability to send and receive MMS using those apps was restored. I then updated Google Voice to the latest version (v5.01 from 4.7). Bam!!! Lost the ability to send and receive MMS from Textra or Messenger. I use Google Voice for work and my regular number for family and friends. I am on model XT1644 US variant Marshmallow build 139.64. The odd thing is that when I restored the backup again with
MisterSteve said:
I have been unable to send or receive MMS using Textra or Messenger. I restored a month old Nandroid backup and the ability to send and receive MMS using those apps was restored. I then updated Google Voice to the latest version (v5.01 from 4.7). Bam!!! Lost the ability to send and receive MMS from Textra or Messenger. I use Google Voice for work and my regular number for family and friends. I am on model XT1644 US variant Marshmallow build 139.64. The odd thing is that when I restored the backup again with
Click to expand...
Click to collapse
You might want to finish the post...
LenAsh said:
You might want to finish the post...
Click to expand...
Click to collapse
lol You are right. I thought I finished it.
It turns out Google Voice was not responsible for me being unable to send and recieve MMS. Was trying to save people some headaches. It turns out it was AdBlocker Plus causing my problem. I did the same test on stock MM and Resurrection Remix MM. I sent texted a photo to my wife's phone and from my wifes phone without ABP. I then reinstalled ABP and attempted to text a photo to my wife's phone and was unable to. I also did not receive the text I tried to send from my wife's phone to mine. ABP did not affect my ability to send and receive MMS using Google Voice or Allo. I just wanted to share this in case anyone else had this problem or to prevent others from experiencing it.
I switched to Verizon on my OP6T about 2 weeks ago. I've never had this issue before, but it is quite strange. About the device configuration:
Stock Rom
Magisk installed
Using Google Messages, but can re-create the issue in the stock Messaging app
There is one particular person that I cannot seem to send or receive text messages with. Note that initially, after moving to Verizon, I was able to. But then it just stopped working. Whenever I try to send a message, I just get an error message back saying "Not Sent. Tap to try again". Any new messages or retries fail immediately.
This is the only contact I have had issues with, and I can send and receive messages if they are in a group.
I have also tried clearing the cache and data for both Google Messages and the default Message app, as well as removing that message thread.
Any ideas about logs stored somewhere where I could get a better handle on what is causing this issue?
Are they blocking your text messages (in error or on purpose)? I would look there first. If you say no then we can go from there.
Never had this issue with Verizon. I had cricket for a while and both my old phone and the 6t could not send SMS to my brother, I could send mms and call and received everything fine. It was an intermittent issue where I would call support every couple weeks it would be fixed then randomly happen again. This was a contributing factor in my carrier switch lol.