d2vzw cannot send sms - Verizon Samsung Galaxy S III

About 4 days ago, I started having problems with my Verizon Samsung Galaxy S3 running Cyanogenmod 10.2.1 . What it will do is send one sms per 24hrs. If I try to send a second sms it fails every time. I have tried modems ML1 and MF1 with the same results. Attached is a screen shot of my settings. I have tried searching the net but cannot find the answer. I see others talked about this in march of 2014 but no solved solution. Please help me, and thank you.

I've just begun experiencing this myself. Below is a copy of the message I've posted elsewhere. Just an FYI that you're not alone in this problem....
"I have the weirdest thing happening. I'm on stable 7 and have been for quite a while. It's worked perfectly until a couple days ago and now I can't send text messages out. I think I can receive OK. Just can't send out. I've even tried doing a clean install of this and other ROMs with same result. It gets more odd... After toying with it I can send only one text out. Just one to any person. But I can't send another unless I reboot or I think wait a few hours. Upon reboot I again can send only one text message out. And so on. I have no clue what could be happening. Any ideas?"
Sent from my SCH-I535 using XDA Free mobile app

I haven't had this issue (knock on wood) and I could be wrong but this is actually pretty common and reported in the forum a lot. Mostly it seems that the different modems 'might' make a difference and I think some had success going back to stock making sure it worked and then rerooting, iirc. I've never seen any definitive solution though.

Related

Phone Resending Texts When Powering On

Hmm. I've been on various XT720 ROMs over the past while so I can't say this happened on a specific ROM. Anyways, I've had now 3 people in the last month make me aware that I had sent them random texts (which were actually texts that I had sent earlier on in the day or previous day). All three times this happened was right after I turned on my phone. (It could have happened more than 3 times but I only am aware of 3). Anyone have any ideas what the issue is? Some error with my phone, or an issue with the network perhaps? Or something else? These texts aren't costing me anything extra but I'd still like to get an idea what exactly is happening.
Thanks
Not something I have experienced, I am using khalpowers galaxy V4, and have used several Dexter versions, using both standard messaging app and GoSMS. Some sms-apps have been known to duplicate messages, what are you using? If it's not the app messing up, best bet is network.
Sent from my XT720 using XDA App
Using stock.
I saw a different thread where someone seemed to have a similar issue - being caused by a message pending but not actually going through at the time it was sent and therefore when the phone was turned on it would detect an unsent message and send it through. Said to turn on delivery reports and then he would see if message actually went through. I'll try that since there's no downside.

Receiving Duplicate Text Messages

I know this is probably something that can't be fixed without working with T-Mobile, but they can't seem to figure out what the problem is and I'm getting desperate
Whenever someone sends me a text I get duplicates of it over and over until I turn on WiFi calling, which seems to work fine. I have had this problem with two different G2x (I sent the first one back thinking it was a hardware issue). This also does not happen on my Nexus One (I moved the SIM card back over and the issue disappears).
I am thinking it has to be something to do with the communication between the G2x and my T-Mobile cell network. Any information anyone has about this that could help me help T-Mobile find the issue would be great.
Thanks.
You don't have another messaging app installed, do you?
First thing I did when I got the replacement was sync Google contacts and tell someone to text me and it started happening. I factory reset the original one I had 3 times and the problem persisted.
Are you running juicedefender? I get duplicates of some messages because juicedefender shuts off mobile data, so the network doesn't receive the notification that the MMS was received. It will try and resend every 5 minutes for a specified number of times until the message is received.
Nope, had no apps installed. Plus I get the duplicates sometimes less than 1 minute apart.
Thanks for the responses so far. This problem is really starting to get irritating.
I was getting a lot of duplicates. Seems to have spied for now. No clue what was doing it
Its really irritating because I love the phone, but I can't use it if I am constantly getting spammed by duplicate text messages.
yea i got 55 texts from 12 am to 11 a m from the same person 2 different texts and it kept going for a couple hours after too idk why i just got a new one today though but it's got a bad bleed so im just returning it and going to wait a week or two hope they solve it by then already sent lg a pic so
If your problems anything like mine a replacement won't fix the problem, unless I somehow got stupendously unlucky.
Anyone figure this out. I have the same problem. It is not every text message and not every person. It is pretty random. The same person can send me 4 texts 2 are normal, one repeated twice and one 24 times over a period of time, usually a couple hours.
Check any of the apps/widgets that have anything to do with calls/texts, even just showing a number of unread texts. If there are any that have the permission "Your Messages: Send SMS-received broadcast" uninstall it and see if the problem persists. I think I may have had an app called Organizer Widget that was blocking my phone from sending that broadcast.
I had your problem.
I was running on stock G2X, and I was receiving text after text after text.
I spent time on the phone with the T-Mo reps, and he concluded that:
"it's a server problem. You see, our messaging database isn't reading that your phone got the text, and thus it re-sends it in hopes that it receives it."
Basically, he is saying that the messaging server is tripping. But, this is not exactly true, because if it was the messaging server, then it would be universal. It is simply a G2X stock-rom problem.
I think it actually might have something to do with the baseband, but I am not sure if CyanogenMod updates it or fixes it when flashing.
I have a fix.
After I flashed myself some CyanogenMod, the problem was instantly fixed.
So, I think its a problem with the stock rom. Definitely. The CM rom works perfectly, no repeating messages. Also, the current nightlies are mighty stable.
I have this issue as well. It doesn't happen often but when it does it sends 10 or more duplicates.
I have handcrafted sms and launcher products which displays the number of texts on the dock. Running rooted stock.
It hasn't happened in a while, so I doubt it is related to the Apps.
Sent from my T3 Motion GT3 (look it up)
I've had this issue on ALLLL my android phones I've owned . Even non Android phones and my unlocked iPhone. I have tried different similar cards as well.
I have noticed it happens the most when I receive messages from a Verizon user; followed by AT&T users. I never (not that I've noticed) had duplicates from Sprint or other T-Mobile users. Only Verizon and AT&T.
My point being I think it's a T-Mobile issue. Or a communication issue between providers.
Sent from my LG-P999 using XDA Premium App
JRudnik said:
I had your problem.
I was running on stock G2X, and I was receiving text after text after text.
I spent time on the phone with the T-Mo reps, and he concluded that:
"it's a server problem. You see, our messaging database isn't reading that your phone got the text, and thus it re-sends it in hopes that it receives it."
Basically, he is saying that the messaging server is tripping. But, this is not exactly true, because if it was the messaging server, then it would be universal. It is simply a G2X stock-rom problem.
I think it actually might have something to do with the baseband, but I am not sure if CyanogenMod updates it or fixes it when flashing.
I have a fix.
After I flashed myself some CyanogenMod, the problem was instantly fixed.
So, I think its a problem with the stock rom. Definitely. The CM rom works perfectly, no repeating messages. Also, the current nightlies are mighty stable.
Click to expand...
Click to collapse
I'm actually having this problem running CM7 Nightly 63, it's irritating as hell.
Dont know, but I'd like to know the problem too. I have chompsms installed but it shows duplicate in the stock messaging app too.
I really don't think it has anything to do with the phone...
Like I said earlier, all my phones have done it. Even my crappy clamshell Samsung back in the day. Or my unlocked iPhone.
Server makes the best sense.
Sent from my LG-P999 using XDA Premium App
I have the issue as well...although it seems to be only with certain contacts, however across every carrier. Averages 3-4 duplicates. Never had this problem before with any phone. SIM card went straight from my N1 to my G2X. Kind of an old SIM. Maybe I'll try a re-provision on a new SIM to see if that makes any difference.
Thank you @shaneledford, uninstalling organizer widget solved my problem... everything's back to normal
Sent from my LG-P999 using XDA Premium App
I've also had this problem with previous phones, though it tends to happen much more often when one of them is an Android phone. Only started happening with my phone before this one, though, but that was a Nokia non Android, so it's a fairly recent thing but not Android specific.
Sent from my LG-P999 using XDA App

Text messaging issue, one number.

I have text one number from my phone for months and thousand of messages at that, suddenly tonight in the middle of the conversation I can't get any text through to her. Says unable to send. I can mms her and she can text me. I can call her as well. I was on bamf gb 2.05. I have now restored back to the mr1 updated rooted only still can not text her. I have deleted the contact tried with and without 1 in front of the number. I can text any other number on the phone normally. Anyone have a clue since Verizon no longer offers 24hour support? How ****ed is that?
Sent from my ADR6400L using Tapatalk
I'm having the same problem with my moms number....worked great,then bam...nothing tried taking the 1 off,it works occasionaly.
this only happened when I went to BAMF gingerRemix worked flawlessly w/other BAMF ROMs
Have you tried changing ROMs?
Since I went from gb back to stock I would say yes... Mysteriously started working again this morning...very odd it was like it was blocked...
Sent from my ADR6400L using Tapatalk
This happened to me for 6 hours one night. I couldn't receive any SMS but I could send. After 6 hours it started working again. If you google this issue, other people are having it. I don't think it is ROM related.
I don't think it's a TB issue.. I haven't experienced it on my TB, but I did experience it on my LG Voyager way back when..
Unless they have the same bug..
Which would suck..
Greetings! I would like to assist with this issue. I see that these concerns have been posted recently. If this is still occuring, please tweet me your details and I'll get back to you ASAP. Thanks!
DionM_VZW
Please follow us on Twitter @VZWSupport
woah new verizon rep on the form

Wifes S3 Wont send MMS

So my wife switched from a razr to the s3. And has been complaining of not being able to send messages unless she restars, and ALL the "stuck" mms all send fine. I figured maybe she messed somehing up with an app so i just rooted, unlocked and flashed beans b9 (b6 on my note2) still not able to send...
SO i put her sim in my note2 and it sends. SO i know its somehting with the phone. WHat could it be if ive flashed it and still have issues?
Another interesting thing is, i noticed while he mms is stuck, if i send her a picture she will recieve it, and then her phone WILL send that "stuck" mms. weird.
anyone? thanks
PS - I bought from Best buy over a month ago, so if i put back to stock will Verizon swap it?
thanks !
Bump
Sent from my SCH-I605 using Tapatalk 2
I have also had this issue on my GS3 but it only started happening after the Jelly Bean update. I still cannot send pictures unless I restart my phone. Every time I want to send a picture I have to hit send on the message and then reboot my phone and the message will send when my phone restarts. I just now started looking for a solution but have yet to find one. I have found SEVERAL threads regarding this issue and apparently this is a problem with Jelly Bean but none of the threads or websites that I have been to have a solution. If anybody out there has a solution PLEASE do share.
imeraz said:
I have also had this issue on my GS3 but it only started happening after the Jelly Bean update. I still cannot send pictures unless I restart my phone. Every time I want to send a picture I have to hit send on the message and then reboot my phone and the message will send when my phone restarts. I just now started looking for a solution but have yet to find one. I have found SEVERAL threads regarding this issue and apparently this is a problem with Jelly Bean but none of the threads or websites that I have been to have a solution. If anybody out there has a solution PLEASE do share.
Click to expand...
Click to collapse
Do you know if this effects all s3? Will putting back to stock before update fix it
Sent from my SCH-I605 using Tapatalk 2

SMS not sending, but able to receive. MMS + Data Working.

Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SMSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.
AnTiDoWn3r said:
Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SCSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.
Click to expand...
Click to collapse
Not sure if I'm doing this right usually I use the app but since I can only text on touch wiz based Roms xda app keeps crashing. Anyway I have this issue too mine seems to have started on 2-20 but same thing reboot or toggle airplane mode and I can send one that's it till next reboot. Was running carbon kit Kat. Hopefully Odin tomorrow will fix it touch wiz sucks!
tonybahr said:
Not sure if I'm doing this right usually I use the app but since I can only text on touch wiz based Roms xda app keeps crashing. Anyway I have this issue too mine seems to have started on 2-20 but same thing reboot or toggle airplane mode and I can send one that's it till next reboot. Was running carbon kit Kat. Hopefully Odin tomorrow will fix it touch wiz sucks!
Click to expand...
Click to collapse
Odin does not fix...
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Odin does not fix...
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yeah I figured that out.
Having the same problem....just wondering if anyone tried unrooting and rerooting?
mamill66 said:
Having the same problem....just wondering if anyone tried unrooting and rerooting?
Click to expand...
Click to collapse
Yes doesn't fix anything.
Sent from my SCH-I535 using Tapatalk
Just kinda bumping to see if anyone found anything?
Sent from my SCH-I535 using Tapatalk
I talked to Verizon again yesterday night, my support ticket is still open, meaning they're looking into the possibility of it being an issue on their end, so nothing new. I'm convinced it's something with them, because of the timing. I'll keep you posted.
Sent from my SCH-I535
AnTiDoWn3r said:
I talked to Verizon again yesterday night, my support ticket is still open, meaning they're looking into the possibility of it being an issue on their end, so nothing new. I'm convinced it's something with them, because of the timing. I'll keep you posted.
Sent from my SCH-I535
Click to expand...
Click to collapse
Do they know you are running a form of CM? Or are you just saying your texts aren't working?
Just for my own info?
AnTiDoWn3r said:
Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SMSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.
Click to expand...
Click to collapse
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.
Whisk_33 said:
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.
Click to expand...
Click to collapse
I'm in Hershey pa as well... interesting
Sent from my SCH-I535 using Tapatalk
Whisk_33 said:
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.
Click to expand...
Click to collapse
Yes, I'm from Hershey PA, my brother and I both have GS3s, but he's running 10.2 RC2 and I'm on the latest D2 nightly. The issue started in morning on the 20th. From what I can tell, it's only Verizon customers in our area that have been affected, my buddy on AT&T with a CM Nightly hasn't had any trouble. I tried disabling Voice+ but it didn't help anything. As of this point, my ticket is still open, so no new news yet. I'll keep you posted.
Dex954 said:
Do they know you are running a form of CM? Or are you just saying your texts aren't working?
Just for my own info?
Click to expand...
Click to collapse
I haven't told them I'm running a custom rom and I won't unless I actually need to. They don't seem to take kindly to people who like to get the most out of their phones.
AnTiDoWn3r said:
I haven't told them I'm running a custom rom and I won't unless I actually need to. They don't seem to take kindly to people who like to get the most out of their phones.
Click to expand...
Click to collapse
That's why I think this is going to be a hard road..
Sent from my SCH-I535 using Tapatalk
This is actually quite fascinating. All of those who seem to be having this issue are in Central Pennsylvania, started having the issue around the 20th, and are running a version of Cyanogenmod. I'll be sure to bring that up in my next chat with Verizon. Stay posted.
Hershey PA here
Cm11 m3 d2vzw
I've been having the same problem since ~20th as well. In glad I found this thread as I couldn't find much else when searching. I've temporarily switched to a TW ROM and it worked fine but any aosp seems affected. I even got Verizon to give me a sim but it didn't help.
My cell number starts 570-57*-**** (Scranton area number ) though I now live in Hershey pa.
This is where I wish I knew someone who worked at vzw and was a reasonable person.
Sent from my SCH-I535 using Tapatalk
I am just outside Philly, I started having this issue on the 20th as well, occurred on both paranoid android beta 4 from notta and slim kat stable 3.0. Seems to be intermittent for me as there is times where it works freely and times I need to toggle airplane mode for every text
Edit: my number is from northeast pa (Hazleton Area). I'm wondering if it is an area code issue or something because I know people with s3s down by philly who don't have this issue with Verizon.
Sent from my SCH-I535 using xda app-developers app
bass0324 said:
I am just outside Philly, I started having this issue on the 20th as well, occurred on both paranoid android beta 4 from notta and slim kat stable 3.0. Seems to be intermittent for me as there is times where it works freely and times I need to toggle airplane mode for every text
Edit: my number is from northeast pa (Hazleton Area). I'm wondering if it is an area code issue or something because I know people with s3s down by philly who don't have this issue with Verizon.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Been having the same issue. I live in mountaintop so maybe you're right
Central PA 570 here as well. Both my mom and I's phones are experiencing the same. What baffles me is that it happened to be people who had already flashed the ROM prior to the 20th, which means it isn't an AOSP specific SIM activation issue, because that happens on first boot. Touchwiz works fine, although I can't stand it. Whatever it is, I desperately hope it's fixed soon.

Categories

Resources