yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] lv128:
More information

Since there hasn't been any additional information garnered from verizon in the last few weeks, I'll fill everyone in on my situation:

Two S3s on a PA account, one with 570 area code, the other with 717

The problem started 2/19 at 5PM using cm10.2 on the 570 #.

All texting was perfect up until then and I txt A LOT.

the 717 number had no issue with the sending. All symptoms related in this thread fit to a T.

Also, if it hasn't been noted in the thread ALL MMS works without issue, only SMS sending (not receiving) You can send MMS to your hearts content with no failures be it a picture msg or just a text with a subject line added.

TWO days after the 570 number started with the problem, the 717 followed suite, same symptoms, using cm10.2 for over a year. During the two days before the 570 failed, there was no problem with sending on this phone.

I called verizon in the morning, went through all the BS to get level 2 tech, they opened a trouble ticket and said they might have an issue and they'll get back to me. a few days later I get an e-mail/mms from a NRB tech who is asking me to help troubleshoot the problem.

Three days later of MMS back and forth between him and testing, he tells me he's getting an SIP 403 Forbidden protocol error.

That was the last message I got from him. a few days later I call to follow up and they closed the trouble ticket with the note saying "custom OS is responsible"

I have them reopen the trouble ticket, and send a replacement phone. As expected touchwiz works file, however the replacement phone they sent me is a locked bootloader 4.3 which is a worthless piece of junk, as safestrap works with it, but no version of stock CM works in the SS rom slots.

I'm in the process now I doing a full backup of the 4.3 with titanium and then restoring apps and system data to a cm11 to see if that solves the problem, but I'm starting to think that it may be a kernel issue with CM10.1/10.2/11 that is at fault.

Note that I HAVE tried 10.1 stable, 10.2 stable and CM11 (several nightlies and the M3) all of them are not capable of sending SMS.

It seems that it's not terribly paranoid to believe that Verizon is starting active blocking of custom roms, but I won't jump on that bandwagon until I try some NON cm roms. I really don't want to move away from CM though.
[Verizon Samsung Galaxy S 4] efaden:
It just started for me this morning. My phone is a 240, but I'm in 585 with it. I was on 10.2 this morning working just fine without updating or anything and then the problem started. I tried just about everything including clearing data, factory reset, upgrading to CM 11, etc... nothing fixed it.

Haven't tried reverting to TW or stock rom yet...
[Verizon Samsung Galaxy S 4] gt43aw:
I went to alliance ROM. Texting comes back. I'll switch back to cm when it gets worked out.
[Verizon Samsung Galaxy S 4] DreamFX:
The problem is all aosp roms use CM code. I tried them all and same issue :(

403 Forbidden

The server understood the request, but is refusing to fulfill it.

This error only confirms that this is a Verizon LTE issue and not a CM issue. They are blocking (maybe they aren't aware they are) messages from aosp roms.
[Verizon Samsung Galaxy S 4] efaden:
Interesting...

---------- Post added at 05:09 PM ---------- Previous post was at 05:08 PM ----------

Alliance is TW based?... you have a link?
[Verizon Samsung Galaxy S 4] lv128:
During my follow up, I've done all the following:

Pieced together all the parts from the original rom for messaging, and restored them into a clean cm11 build, no dice there, so that means that it's further into the OS.

I'm thinking either User Agent, User Profile, both of which I don't know how to extract, but messaging programs like Go SMS allow you to set those manually, but they may only effect MMS and not sms.

Today I reverted back to 10.2 and using the info code changed the radio to CDMA ONLY which is 1x service.

I couldn't even use the CDMA PRL auto, which would give me 3g service because that did not fix the issue either. Only 1x service is allowing sms to go through it seems.

I'll honestly drop verizon before I use a touchwiz rom; and I've been with them for 13 years.

I did not check to see if this problem was reported in the CM bugfixes, but the fact that the problem occurred LONG after cm10.2 was final stable release, this looks more and more like an actual purposeful move by verizon.

Considering that with custom roms it's that much easier to use hotspot and other "unapproved" services, this might be their motivation.
[Verizon Samsung Galaxy S 4] DreamFX:
Came to same conclusion... I'll go with AT&T before using TW.
[Verizon Samsung Galaxy S 4] gt43aw:
It is tw. U can find it in the other Samsung s3 development forum. Not the original develop.
[Verizon Samsung Galaxy S 4] robblz:
fails after first text

I live in the 804 area code. About a week ago my texts all fail after the first is sent. As of today my messaging app has disappeared from app drawer. I can access it through system settings/apps but force closes immediately. Using current SlimKat.
[Verizon Samsung Galaxy S 4] joegard:
Same here, VA, CM11, airplane toggle fixes it, messing with mobile networks (change mode) sometimes works. ML1 modem, noticed this issue in the past 2 weeks, 2/10/2014 M3 d2vxw snapshot, seems to have issue coming back into LTE from EVDO only areas.
[Verizon Samsung Galaxy S 4] gt43aw:
Va as well. Still no solution. On clean ROM so I can text. Anyone else get it solved?
[Verizon Samsung Galaxy S 4] Neuspadrin:
757 phone from VA but live in RTP NC, was running an old 10.2 nightly from november when I noticed this issue the other week. Decided to update to 11, still same issues, and seeing now its more common.

Same as everyone else, toggling airplane or restarting will let a few through before breaking again.

Tried re-flashing, using TWRP vs CWM, flashing old modem, different modems, etc.
[Verizon Samsung Galaxy S 4] efaden:
I'd hate to have to jump from CM, but given that CM 10.2 and 11 don't work do any of the other AOSPs work? Or do I need to go to TW based to get it to work right?
[Verizon Samsung Galaxy S 4] DreamFX:
None work
[Verizon Samsung Galaxy S 4] efaden:
http://xdaforums.com/showthread.php?p=51119700

Checkout this thread. It seems that people have gotten the S3 functional again with NVRestore... still reading the thread though.
[Verizon Samsung Galaxy S 4] DreamFX:
I have been doing extensive testing to try and figure out why us folks in central pa lost texting on aosp roms on 2/20. I downloaded an app called android system info. I launched it on TW(where texting always works) and CM(where texting doesn't), Went to telephony tab and found something rather interesting. The network operator name for TW rom is Verizon Wireless and for CM it's Roaming Indicator Is Off. If you change the ERI file or use an xposed module to removing this from the notification area which it does but never does it change the hardcoded network operator name.

I am thinking for some reason on Central PA towers that they are enforcing the Network Operator name to be correct or it won't allow texts to go through. The reason I know Verizon is actually getting the texts I send because I sent like 15 in a row to myself they all in CM act like they didn't send. I immediately restored back to TW and I received all 15. Something in the CM code (why only for Central PA) which seems like its the network operator or some other similar setting needs to be changed to work.
[Verizon Samsung Galaxy S 4] dadoc04:
Having the exact same issue here in Florida.... Been running aokp, slim and liquid smooth

Not sure when it stated tho since i don't text much

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] S52Stu:
su reboot nvrestore fixed my issue. Thank god no more TW.
[Verizon Samsung Galaxy S 4] cooldman224:
What exactly does nvrestore do?
[Verizon Samsung Galaxy S 4] Cilraaz:
Best way to test that would be to find where in the code the network operator name is located, pull a branch of CM's source, modify the network operator name, and then build a custom build of CM. I don't have the time currently, but I may tinker with it tonight or tomorrow. If anyone else has the time and wants to find where in CM's code the network operator name is hardcoded, it would definitely be a help.
[Verizon Samsung Galaxy S 4] username115:
I'm with cooldman224. What does nvrestore do?

I just got the same issue on March 14th, I'm 240 area code in MD, but was in Raleigh, NC at the time. Now that I'm back in MD, the issue is still there.

Was running cm 10.2.1 and updated to the latest cm 11 snapshot hoping to fix the issue, when it didn't I did a full data, cache, and dalvik cache clear and reflashed it to no avail.

Reading some of the replies here, I agree that it was probably something Verizon did that unearthed a latent issue in CM's codebase.
[Verizon Samsung Galaxy S 4] efaden:
And can you nvrestore without doing an nvbackup at some point first?
[Verizon Samsung Galaxy S 4] S52Stu:
It didnt work. It fixes the issue for one boot. After you nvrestore and install a ROM (for me it was slimkat) you can send texts until you reboot the phone. Then it is back to its standard 1 text.
[Verizon Samsung Galaxy S 4] lv128:
Fixed for me

I've been on the phone every day with verizon since I originally posted in this thread, working with an NRB engineer, as of today, everything is working on both my lines using CM10.2 in both 717 and 570 area codes with LTE enabled, the texting seems slower than normal, roughly about 10-15 seconds to do a send, but they do go through, and it continues to work even after a reboot.

I'm not sure if they patched something on my account alone or if the general area that I'm in has been patched over. But my crisis is over for the time being, unless the problem resurfaces. I'm not terribly hopeful that I'll live happily ever after given Verizon's track record, but fingers and toes crossed! :fingers-crossed:

I can't say for sure if my constant nagging them is what helped or not, but everyone I talked to today kept telling me it reached the highest level of network operations and it's on their desk. I'm not about to tell them that it's completely resolved until I know for sure, otherwise they'll just close the ticket and pretend it never happened.

I'm leery about trying a cm11 rom because it might break the gypsy curse that is currently allowing me to text.

Maybe if this working streak lasts a few days I'll give it a whirl and let you all know.
[Verizon Samsung Galaxy S 4] DreamFX:
When did it actually start working? I tried earlier today 717 and it was still not working.
[Verizon Samsung Galaxy S 4] musicfreak58:
This worked for me

So I was having the whole issue with not being able to send text's but I could receive them. Couldn't call either. I remember a few days ago a text got hung up I started having issues with my texting so I deleted all my texts and it started working again. This time I did the same thing but I removed google hangouts and another SMS app I had installed to try to get my texts working and put it into airplane mode and turned airplane mode off and now it works. I have the latest nightly from today but I had flashed a couple different older nightlies to see if that would help and it didn't. I hope this helps
[Verizon Samsung Galaxy S 4] bryfry:
I'm having this same issue with my Verizon S3 (SCH-I535 aka d2vzw) in area code 717. It started about 4 weeks ago and I've been trouble shooting it any way I can. The whole 'first text message works but the rest fail' is really what has been bothering me. I can't think of any good reasons for this to happen.

Interestingly I am running AOKP. Started with 4.2.2 build (not sure the number as I've since upgraded) and is still an issue in aokp_d2vzw_kitkat_nightly_2014_03_01

Some googling around on the smsc that keeps showing up in the *#*#4636#*#* Phone info page (+19037029920) indicates that this probably a test string that has made it into the actual code base some how. Not sure if that is what is actually causing the issue.

In case anyone is just now picking up on the end of this thread, a workaround is to switch your Preferred network type between LTE only (for data) and CDMA only (for reliable texting). Sigh.

I may update my toro (Galaxy Nexus) to a latest nightly (it is on an older milestone) to see if it also breaks.

My ticket with VZW was squashed as soon as they found out it was a rooted device. I did make past the initial few and up to engineering though.
[Verizon Samsung Galaxy S 4] lv128:
As of about 7am on 3/15 I switched back to 3g from 1x data (where texting was working) and I was on 1x data for about 4 or 5 days, but it became unbearable so I switched to 3g and noticed the texting was working, I waited a few hours then switched back to LTE and the sms still was working, switched the 717 number over to LTE, texting still working, both phones are 10.2, not clean, they're restores of the phone from before the problem started on 2/16.

Like I said, it may be either a temporary fix verizon did for my account, or a regional fix, I don't know.

I'm basically back to the state that I was in before all this happened.

---------- Post added at 03:46 PM ---------- Previous post was at 03:37 PM ----------

I was able to bully my way through, and that may have to do with my threat of leaving after 13 years of service with them, I think they actually do value loyalty, at least a little bit.

I told them I was more than capable of restoring to stock, etc. and I did while I was on the phone with them since I have nandroid backups of all my major changes, and that might have helped convince them that they shouldn't brush me off.
[Verizon Samsung Galaxy S 4] gt43aw:
Update: I flashed back to stock tw (not Odin) did an nvrestore, rebooted, rebooted back to recovery and flashed latest cm11 nightly (0318). Text still didn't work after first one. Did another nvrestore and rebooted. Same thing. So I just restored my tw backup.

Ill try to odin back to ICS at some point and do the nvrestore and ota reprovisioning as described somewhere else as working but that's my update for now.

Also, after each nvrestore I got a bootloop and needed to battery pull and reflash whatever ROM I'd just flashed. Which was weird.

I did the nvbackup and synergy zip file flash when I first got this phone and it was on ics.

Short story: nvrestore method didn't seem to work for me.

Brian.
[Verizon Samsung Galaxy S 4] Supercutetom:
I just want to chime in and list off the 757 area code (South East VA) doesn't work either. I have tried all the different methods available and just didn't have a damn success. We should try and see if we could get the attention of some well known high up developers. Sin e we know about the 403 issue maybe they can assist us in addressing it. Seems like our only real hope at this point.
[Verizon Samsung Galaxy S 4] musicfreak58:
My phone is still working

So I'm pretty sure the issue is with google +, hangouts, and cyanogenmod. I removed the different cyanogenmod messaging caller apps hangouts google + and the other sms apps that aren't the stock one. No issues since I have done this and I was having problems for about a week. I have an S3 on Verizon with the newest nightly. I hope this helps some people restore use of their phone :D
[Verizon Samsung Galaxy S 4] lv128:
Could you be more specific on which com. components you removed/froze/whatever so I can try this as well?

My 570 line is working as expected but the 717 line on my account is not functioning as expected. The 717 line frequently has rejections.

Did you use titanium to remove or freeze them?

I've been having this issue for over a month, on every AOSP rom in existence (virtually).

Did the behavior of your handset exactly match the problems of the OP? i.e. able to send one message per reboot or airplane mode cycle and related to SMS sending only whereas MMS and SMS receiving were unaffected?

Thanks
[Verizon Samsung Galaxy S 4] musicfreak58:
First I deleted all my messages in my sms. Then I went to my apps and uninstalled the cyanogenmod voice and google hangouts and then settings >apps> downloaded and force stopped and uninstalled google + and uninstalled the 2nd sms app I had. Put it in Airplane mode and turned airplane mode off.

---------- Post added at 06:35 PM ---------- Previous post was at 06:11 PM ----------

And I forgot to mention that my phone was having the same issues. I could reboot and receive a text and send a text for like the first 30 seconds of my phone being back on.
[Verizon Samsung Galaxy S 4] yooeee:
dear god this is killing me. so no one really knows what the problem is. i'm on carbonrom, but have been through all the threads on how to try to fix this. is it this whole +19037029920 SMSC issue, or is it Verizon messing with all rooters?

has there been any input from cyanogen? the frustration is maddening
[Verizon Samsung Galaxy S 4] neganox:
This issue affects all CM based roms. TW (ugh) and GPE roms seem to work fine. I switched to a GPE based rom and everything is working fine. I will miss my slimkat until this issue is resolved.
[Verizon Samsung Galaxy S 4] yooeee:
thanks. maybe i will switch to GPE for the sake of work and communication. i waited so long for carbonrom to come back and now this. since it's such a major issue, I just want some input from the developers on what the problem is and a timeline.
[Verizon Samsung Galaxy S 4] dwitmer1989:
Yeah I've been having the same problem and tried to live with tw for a few weeks. At any rate the liquid smooth ROM I just flashed today seems to have no issue for me and every other aosp ROM has had it. Give it a shot you never know.
[Verizon Samsung Galaxy S 4] DreamFX:
LiquidSmooth didn't work for me.
[Verizon Samsung Galaxy S 4] dwitmer1989:
Hmmm. Did u try the liquid smooth ROM that just updated yesterday? I'm running the pa gapps modular mini. The only thing i did different is install the ROM with no gapps, send a few texts and then install the gapps package. I'm In the 717 area which was basically the first area to get the problem. Who knows maybe my region is fixed maybe not but I'm not about to flash another ROM to find out.
[Verizon Samsung Galaxy S 4] DreamFX:
I have a Note 2 and unfortunately they don't update past 4.3.1 Jellybean. But i tried the newest build. It's weird I actually got texts to go through for a few minutes and it completely dies.

In 717 as well
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Have you tried this method? http://xdaforums.com/showthread.php?p=51248360
[Verizon Samsung Galaxy S 4] xyrcncp:
I started having this same issue yesterday. There is a lot of info and I'm thankful at that, so I have a couple of questions as to which path to follow:

- I haven't flashed a ROM since the last release of Mastamoon's CM10.2 for the S3, I see above that a GPE ROM would work. I know this is the S4's forum, but what GPE ROMs would work on the S3?

- Does this method fix this text issue? GSM Patch: http://www.internauta37.altervista.org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android

- Or is the method above posted by djdmbrwsk (http://xdaforums.com/showthread.php?p=51248360) be preferred?
[Verizon Samsung Galaxy S 4] djdmbrwsk:
I'm not sure there are any GPE ROMs for the S3...was there even a GPE S3 released?

I would definitely try the method I linked to. I'm on an S4 and haven't had a chance to try it yet, but the post I linked to is in the S3 forums. Let us know how it goes!
[Verizon Samsung Galaxy S 4] lv128:
CONFIRMED FIXED on one line.

I can confirm, after the doing this process which was akin to torture (i.e. having to use touchwiz for a short while again) this DOES WORK.

I fixed one out of two phones on my account so far, I'll post again when I confirm that the other phone is working as well.

It appears to be an issue with NVram corruption, caused by god knows what, I wouldn't doubt that I've installed some less than questionable apps, but restoring to stock, making an NVram backup, then immediately installing cm11 nightly overtop it everything is running smoothly.

sms is working perfect and fast without having to dumb it down to 1x data. I'm crossing my fingers that it lasts from here on out, I did have short spurts where it did work before this, but never on LTE, at least not properly.

Signal is very good using the ML modem as well.

I took my phone back to 4.1.1 stock (not 4.0.4, like everyone suggested, because I couldn't find a 4.0.4 rom) so I used the odin for this one (BLK1) http://shipped-roms.com/index.php?category=android&model=Galaxy%20S3

restored to stock with odin 3.09, then used Casual r763 to root and install the insecure aboot, then I used ADB to do a "reboot nvbackup" then installed twp 2.7.0.0 and installed the 3/22 nightly of cm11.

I didn't want to risk restoring a nandroid or using titanium to mass restore my apps, so I'll restore a few at a time and I will attempt my same mod of the 717 line and I'll report back.

You can skip the dialler code portion of that link above, because that is only for ICS stock and all it does is reset stuff to factory anyway which if you're using the odin rom I posted, is completely unnecessary.
[Verizon Samsung Galaxy S 4] lv128:
Sigh

Ok, so 2.5 hours of texting like a fiend and installing NOTHING else, the problem returns.

No other programs installed, and I attempted an NVRESTORE which mucked up the system rom a little bit requiring me to restore the cm11 zip in recovery, and then I had to reinstall the gapps as well because I got a black screen boot loop right after doing the nvrestore.

So now it's up and running with cm11 again, and no sms sending, same as before.

I'm ready to give up.:crying:
[Verizon Samsung Galaxy S 4] Kevin M:
At least(?), I'm not the only one having this problem. I got a new SIM from Verizon and it did not fix the issue. Could the issue be in one of the recent telephony changes? http://www.cmxlog.com/11/jflte Maybe this?
[Verizon Samsung Galaxy S 4] PhilDX:
you do get gold star for effort though, too bad it didn't work
[Verizon Samsung Galaxy S 4] yooeee:
Nice try man. I tried the he same with no luck. The source of the problem is still unclear. Until we know that, we're stuck. Sadly I see no mention in cm or developers acknowledging the issue. Why are we the only ones with this issue? Did you guys always have Verizon? I switched from Sprint over a year ago. MMS has always been compressed and when people send multiple pics, some would be black and white. This mms stuff should be related, but just brainstorming the problem. #hopeless
[Verizon Samsung Galaxy S 4] Kevin M:
MMS seems to work fine, both ways. On Verizon I would assume this has to do with MMS being handled by LTE, which appears to still work. Some kind of CDMA modem problem.
[Verizon Samsung Galaxy S 4] E01010100:
Same problem but on 10.2

So I'm running into this same issue where my first sms message after reboot or airplane mode off/on or update smsc works but the second, and all subsequent messages fail. However, I'm on 10.2.1-jfltevzw

One thing that might be interesting to point out is that all of my troubles started when I tried to do full disk encryption overnight. When I woke up in the morning my phone had been completely erased and nothing was encrypted. At some point the encryption obviously failed and I don't know what happened. I have attempted restoring earlier nandroid backups as well as clean re-install of CM. In the end my smsc setting keeps bouncing back to 19037029920.
[Verizon Samsung Galaxy S 4] Kevin M:
So you were on an old CM 10.2 build and have never run a CM 11 nightly? If so that really helps isolate the issue. I don't think the failed encryption was the catalyst.

Is everyone who is having this problem on the MJ7 baseband? That's the first thing I can think of that might be similar across CM 10.2 and 11.