yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Update on the text/sms issue...

I just clean flashed the 10.2 stable and this issue still exists for me. I'm thinking it has to be a modem/radio thing. Have you other two guys with the problem flashed new modems? ...or new kernels for that matter?

Specifically I was on CM11 2/12 nightly with the ktoonsez kernel and the mk2 modem/radio. I hadn't just installed any of the things above either...texting just randomly broke this morning. Man this sucks..
[Verizon Samsung Galaxy S 4] Cilraaz:
I haven't used any custom kernels. I have only used the default CM11 kernel. I have tried both the MDK modem and the MK2 modem. Neither worked for me. I've tried both the KitKang (Euroskank) CM11 build and the official CM11. The issue occurred on both, which makes me think it's something in the CM11 base.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Well it may just be the CM base that is continuing the issue cause with 10.2 it was still broken for me. I also have voice+ disabled so it's not that. The issue is there right after a flash even before restoring old apps/settings.
[Verizon Samsung Galaxy S 4] thesoldier:
This may or may not be related (I have a strong feeling it may be) but I'm having a different issue running CM. WiFi causes my phone to black screen of death over and over. I tried every setting I can find and no luck. Flashing back to TW completely fixes it. I tried everything up to flashing a stock image and formatting my phone, and not restoring my Google account settings...still does it. Could these issues be possibly related?
[Verizon Samsung Galaxy S 4] joshm.1219:
Other AOSP ROM's are basically the same lol not like a different setup or anything.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
OK never mind...problem back...what the heck!
[Verizon Samsung Galaxy S 4] Whisk_33:
I wanted to give you some more weight behind your stick shaking. I have a gs3 and have been running mastamoons cm10.2 for over a year without making any changes and no problems. Suddenly on the 20th (is when I noticed it) same exact problem. I have tried all you have and met with the same success. Hopefully someone from CM figures this out.
[Verizon Samsung Galaxy S 4] S52Stu:
http://xdaforums.com/showthread.php?t=2659280. This is also happening to me too.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
OK this really does seem to work for me as a temp workaround...it sticks through reboots and all.* Go to the dialer and enter the trusty old *#*#4636#*#* then go to phone settings and change preferred network type to CDMA only then back out and reboot.

It kinda sucks cause it's slow on the go, but at least I can send texts reliably. I have WiFi most places I am anyway.

If anyone figures out a real long term fix please post!!!
[Verizon Samsung Galaxy S 4] qew204:
Just from previous experiences, I have not used an S4 on Verizon, but did flash a sprint phone to Verizon and something similar to this would happen. The flashed phone could not make calls or send text, but did receive text and could receive calls. I had to ask Verizon after several calls to "refresh" the account so the authentication could be allowed to the phone since it slightly didn't match the database record. I am wondering if Verizon is having some kind of authentication issue currently that is affecting random people.

Just my thoughts.
[Verizon Samsung Galaxy S 4] S52Stu:
Any update by chance?
[Verizon Samsung Galaxy S 4] Whisk_33:
It seems that a couple of us having this problem on the GS3 are located in Pennsylvania (Central/Northeastern portions) . Is anyone else having these symptoms located in this area?
[Verizon Samsung Galaxy S 4] thejudgement223:
Galaxy note 2 user on Verizon cm11. NEPA too
[Verizon Samsung Galaxy S 4] S52Stu:
Hershey pa
[Verizon Samsung Galaxy S 4] kev_39:
Galaxy S4 running latest CM11 nightly and I am from Northeast PA
[Verizon Samsung Galaxy S 4] mamill66:
I'm on a GS3 in NEPA (Wilkes-Barre) and having the same issue. It started on 02-19. Also, I have a co-worker on a GS3 who has the same problem. His started acting up 02-20. He is running CM10.1 and I was running CM11.

I've been putting my phone in CDMA only to make texts....real pain though.
[Verizon Samsung Galaxy S 4] S52Stu:
Anyone not from pa?
[Verizon Samsung Galaxy S 4] AnTiDoWn3r:
I'm from Hershey PA aswell. My brother and I are both having this issue and we both have GS3's. He's running CM 10.2 RC2 and I'm running the latest D2 Nightly. The issue started the 20th in the morning.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Mine started the 20th and I am from PA as well. What the heck!?

FYI, I opened up a chat with Verizon today and they did a refresh/reauth/whatever on my account and it didn't help. They're sending me a new sim so we'll see if that helps. It's doubtful though because I also tried my wife's sim in my phone and the issue was still there...
[Verizon Samsung Galaxy S 4] Cilraaz:
I'm just outside Harrisburg.
[Verizon Samsung Galaxy S 4] Whisk_33:
What part of pa. It will be helpful if we can make a rough map. I'm going to Philly on Thursday so I can test if it goes down that far... It would be nice if someone was already there and could confirm one way or another.
[Verizon Samsung Galaxy S 4] TxdoHawk:
Now that's interesting...I live in NJ and have the problem, but I got my Verizon phone when I lived in Elysburg, PA (and still have a 570 number)!

I've been meaning to change my number to a NJ one, so I'm going to do this and will report back on if this fixes the issue.
[Verizon Samsung Galaxy S 4] TxdoHawk:
Well, I got good news and bad news, guys...I switched my number using My Verizon to a NJ one and my texting problems seem to have disappeared. That's the good news.

The bad news is that I have no idea what the actual fix is, then, for anyone still living in that area. But at least we now know that the problem is linked to PA numbers.

Maybe one of you should try using My Verizon to change to a new number from the same area and see if that fixes it?
[Verizon Samsung Galaxy S 4] joshm.1219:
I live in Philly no problems with texting on CM on Saturday... it was the only day I've ran CM recently.
[Verizon Samsung Galaxy S 4] bass0324:
Definitely seems to be 570 area code. I live outside Philly and work in jersey, I have been having intermittent texting issues using my s3 which seems to be the same as you guys with the s4.
[Verizon Samsung Galaxy S 4] kev_39:
What area codes are we having problems with? I am using a 570 area code and having issues. Is 717 having similar issues? The new 272 overlay was put in place last year, I hope they didn't mess up something with that.
[Verizon Samsung Galaxy S 4] thejudgement223:
570 area code here
[Verizon Samsung Galaxy S 4] S52Stu:
717 is having issues
[Verizon Samsung Galaxy S 4] Cilraaz:
717 with issues here.
[Verizon Samsung Galaxy S 4] thejudgement223:
Because of this problem I made the mistake of calling *228 and lost 4g on my sim card. Got a new one in the mail, and I can't get service. In setting/about phone/status everything is normal except my phone number is 000-000-0000, and min is unknown. Any ideas. Am I supposed to activate this card? I just took it out of the packaging. Turned off my phone and put it in. Any ideas? I still have can't send sms on my old card btw.
[Verizon Samsung Galaxy S 4] joshm.1219:
yeah you really messed up doing that :p You do have to activate the card with Verizon I believe, you can always call them and ask though.
[Verizon Samsung Galaxy S 4] thejudgement223:
Got 4g back, but still no SMS out. I'm calling them tomorrow.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
717 with issues here...new sim tomorrow will post results then...not hopeful...
[Verizon Samsung Galaxy S 4] Alarbus:
I have a Vermont area code, but have been texting fine on various versions of cm in the Lansdale and Wayne area. Haven't really ventured out of that corridor this week. Stock cm kernel.
[Verizon Samsung Galaxy S 4] aladd04:
I live in Michigan and have been having issues with an 810 number. Not as drastic. My messages don't send and I don't know they're not sending until the person sends back some ??'s because I haven't responded (even though on my phone it shows that it has). I was on 10.2.1 and noticed it start happening about a week ago. I just switched back to 10.2 under the assumption that it was a problem with WhisperPush because I also upgraded to 10.2.1 a week ago and it added that (with no way to disable it). Now I just have to get used to the bootloops and battery pulling again :P
[Verizon Samsung Galaxy S 4] Whisk_33:
Your description does not match the symptoms I have seen. Only the first SMS sends. The remained never register with your phone that they were even sent.
[Verizon Samsung Galaxy S 4] aladd04:
I wasn't very clear with my description. I am having a similar issue, but I do not know if they are related. Starting about a week ago only some of my messages will send while others will fail. However, they fail silently and I have no indication that they have failed. Usually texting starts off fine and then it just halts with no indication that it halted and I haven't found a consistent time or symptom for it to halt. Rebooting my phone usually temporarily fixes the issue until it decides to come back. I didn't notice this until I upgraded to 10.2.1 about a week ago and figured it might have something to do with WhisperPush, the text encrypter new to 10.2.1. Since you can't disable it (I didn't find a way), I've reverted back to 10.2 to see if the problem persists. My issue may be related or completely unrelated, I don't know. But it's a texting issue with CyanogenMod and the Verizon Galaxy S4. Similar issue starting at a similar time so I thought I'd add in my tidbit of information.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
So I got a new sim today and activated it but the issue remains as I suspected it would...uhg...
[Verizon Samsung Galaxy S 4] johnwaco:
717 in Carlisle PA and having same issue. SMS works fine on beans but not on cm11. Even tried flashing back to mastas build from 2/14 and issue remained. Would love to know why
[Verizon Samsung Galaxy S 4] Mistertac:
Very strange issues some of you are having here. Its possible for just certain numbers (pa) to have these problems? Never heard of that, not saying you're wrong
[Verizon Samsung Galaxy S 4] DreamFX:
Hey everyone I thought I was the only one. I am in 717 northern York County PA. I have tried everything under the sun to get this resolved. This is some crazy almost unbelievable issue. It's driving me insane. I hate touchwiz and want my aosp back. I have note 2 Verizon here is my thread on the issue. http://xdaforums.com/showthread.php?t=2662658
[Verizon Samsung Galaxy S 4] joshm.1219:
It would be the first time I've seen a specific area having a text issue on a rom.

I've ran CM11 on both my s4 and note 2 with no texting issues. I live in Philly.
[Verizon Samsung Galaxy S 4] DreamFX:
Totally agree with you but being someone with this issue it's def seeing is believing. I even restored an old twrp backup of cm10 and issue is the same. But all touch whiz roms work.
[Verizon Samsung Galaxy S 4] joshm.1219:
I believe everybody it's just a really weird issue.
[Verizon Samsung Galaxy S 4] DreamFX:
I need to talk to some devs and find out what the difference is between how aosp sends texts and how touch whiz does. And how multiple people in a centralized part of PA could all the sudden lose the ability to send texts. Airplane mode on and off allows you to send one and then done. And changing to cdma only temp fixes it. Which makes me lean toward and lte issue with Verizon but why tw works and aosp doesn't is whack.
[Verizon Samsung Galaxy S 4] Mistertac:
Very whack... maybe someone at Verizon is screwing with you guys in PA lol TW only!
[Verizon Samsung Galaxy S 4] DreamFX:
They choose the wrong area to mess with ;)
[Verizon Samsung Galaxy S 4] djdmbrwsk:
If it is a region specific Verizon issue (and I think it is), there is only one thing I can think of to explain why it works in TW and not CM. That is, maybe TW actually has some good programming where if an outbound text fails on 4g it rolls back and uses 3g to send it. Seems like a stretch but that would make sense. I wonder if there is any way to test that...thoughts?
[Verizon Samsung Galaxy S 4] Ostate24:
419 is having problems too! Toledo Ohio area. Same with me some send just find then out of the blue they fail and I just bought my GS4 yesterday so brand new SIM and everything! Heard Verizon was having network problems from the last couple of weeks but wasnt sure what was causing it.
[Verizon Samsung Galaxy S 4] S52Stu:
Tw is killing me... Dammit VZW and the fact that I'm in the one area in the country with an issue.
[Verizon Samsung Galaxy S 4] DreamFX:
I totally feel you. It's crap luck. Time to move out of PA or switch to AT&T. That's how bad I hate touch whiz.
[Verizon Samsung Galaxy S 4] DreamFX:
Anyone try aosp to see if fixed yet?
[Verizon Samsung Galaxy S 4] S52Stu:
Nope still doesn't work
[Verizon Samsung Galaxy S 4] DreamFX:
I just tried as well. Dead in the water. :(
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Has anyone tried one of the more recent builds of cm11? Any luck there?

Also, I hate to ask, but what is the best AOSP-feeling TW ROM out there?
[Verizon Samsung Galaxy S 4] heath2805:
I talked to a friend and he said the nexus forums are flooded with the same issues. Seems like a kk bug. I noticed this too on CM 11 ...2-14 build. Worked fine for a while and then my text messages started failing. Only seem to work on stock now. Even Liquids failed for me on 3-1 build and All network settings were correct.
[Verizon Samsung Galaxy S 4] jcbauerca:
Same issue with texting in Southern California with today's CM11 nightly 3-4-14
[Verizon Samsung Galaxy S 4] S52Stu:
This is interesting.. What is happening for you? You are the only one reported out of central pa.
[Verizon Samsung Galaxy S 4] DreamFX:
Verizon is slowly picking us off. Eliminating the use of custom roms on their network lol.
[Verizon Samsung Galaxy S 4] heath2805:
No doubt..I feel like im stuck on TW and I have a MDK.
[Verizon Samsung Galaxy S 4] jcbauerca:
It would say can't find APN, but when I checked the APN, it was the normal Verizon APN that I was using before. The text messages would say downloading and never comes in. If I dirty flash the 1/07/14 nigthly than it seems to work fine.

I have not reloaded it yet to see if today's nightly fixed it. Also my camera does work for banking apps to make deposits.

I am in Newport Beach, CA
[Verizon Samsung Galaxy S 4] S52Stu:
This is not the same issue we are having in pa
[Verizon Samsung Galaxy S 4] jcbauerca:
Ok well mine does not work either. I'll try again later today.
[Verizon Samsung Galaxy S 4] broscup:
Same Here

I am in Virginia and I started having this issue this morning. After a reboot my Verizon GS3 will send one text but nothing else. I was running the January M2 version of CM 11. I just updated to the latest nightly hoping that would solve the issue, but it hasn't. I can send MMS just fine, that includes adding text to an MMS. I also seem to be receiving SMS, but who knows, maybe I'm not receiving all of them.

I saw the Voice+ "fix" but mine was already disabled. If you have a Google Voice phone number and go into Voice+, you can select that account and it will use your Google Voice number to send and receive texts. On your end it will look the same, but then you have to explain to all of your friends and family that it's another number and that you want them to text that number, but it seems like that could get confusing to other people.

Things I've tried to no avail,

wiping cache

wiping dalvik cache

deleting all (7000+) text messages

deleting app data/cache, messaging/go sms

rebooting obviously

updating to the latest nightly

saying "Mother ****er" several times

uninstalling Google Voice (in hopes it was related to some sort of voice+ issue causing the problem)

Nothing is working. What the hell ??
[Verizon Samsung Galaxy S 4] hootyburra:
Temp Solution.

Same issues on Verizon S3 running latest Carbon Nightlies. 570 area code.

Have tried everything.

Lost 4G when i tried *228.

The only thing that I have found that yields the longest results is:

*#*#4636#*#*

Phone Info. > Update SMSC to ("+316540951000") and toggling radio.

It works for random intervals; sometimes hours.

Then the SMSC will revert back to ("+19037029920")

Hopefully a fix is figured out soon.
[Verizon Samsung Galaxy S 4] Mistertac:
Do you guys think it's something Verizon is doing intentionally? It seems like that wouldn't be possible, but now-a-days I guess you just don't know.

The more updates that come out for these phones the screwier things have gotten if you ask me. I wouldn't put it past big red that's for sure.

Forcing people to use TW .

I'd be more than pissed and feel bad for you guys.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Does anyone know someone with a Verizon Play Edition S4 in the area? I wonder if they're having issues too. I tried the Oct OS ROM which (I think) is built on a GPE base (rather than a CM base like most other ROMs) but the issue was still there. What I'm getting at is if we can prove to Verizon that a non-modified system is having the issue too they'll be more inclined to actually research and resolve the issue.
[Verizon Samsung Galaxy S 4] DreamFX:
Yes. My wife.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
And is she having the issue? I'm guessing not?
[Verizon Samsung Galaxy S 4] DreamFX:
She is having the issue. As am I with my Note 2.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Interesting. I just flashed this GPE based ROM and no texting issue...

http://xdaforums.com/showthread.php?t=2643031

At this point I'm thinking it HAS to be a combination of code that's been in the CM base for some time AND a network change on Verizon's side. That's the only thing that makes any sense to me.
[Verizon Samsung Galaxy S 4] DreamFX:
Agreed
[Verizon Samsung Galaxy S 4] djdmbrwsk:
I guess that will be my daily for now...closest thing to CM/AOSP. But man I already miss a bunch of subtle CM features.

Anyone have any ideas on how we can alert CM of the issue? It sucks its so isolated to a location. But after flashing the play edition ROM it seems like it's def something they should be able to fix.
[Verizon Samsung Galaxy S 4] Cilraaz:
Thanks for pointing this out! At least now I have a daily driver that can actually send texts and comes REALLY close to working like CM.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
No prob. With xposed and gravity box it's like we're running CM again! Woot!
[Verizon Samsung Galaxy S 4] Cilraaz:
Almost. I'm already finding things that are different. Definitely not deal breakers, but things like no notification drawer shortcut bar (aside from the "Quick Pulldown" option), no volumes shortcut when adjusting volumes (the button that let you change any volume level instead of just the volume rocker changing the current stream's volume), and it seems battery life is slightly worse. Like I said, all very minor things, and it's worth it to finally have SMS working and not needing to deal with Voice+.
[Verizon Samsung Galaxy S 4] nbvb:
Ran into this problem this morning. 757 number in VA. Traveled across the state today and noticed that I could send MMS in a group chat but no SMS.
[Verizon Samsung Galaxy S 4] broscup:
Check out my post on page 9. 757 area code too.
[Verizon Samsung Galaxy S 4] neolink1:
I doubt it's the area code, to many places. I'm in FL... With a 276 (VA) area code. And, have tried everything to resolve with no luck. I think it's back to TW or that GE alternative posted a few pages ago.
[Verizon Samsung Galaxy S 4] broscup:
Early in the thread it looked like nearly all Pennsylvania area code users were having the issue. Some, including myself, thought that it may be related to some sort of network update combined with something in CM.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Yep...I'm convinced it's a combo issue!
[Verizon Samsung Galaxy S 4] gt43aw:
Socal here. Exact issue for me started two days ago.
[Verizon Samsung Galaxy S 4] broscup:
M4

Anyone heard of an M4 update for the S3 Verizon? Hoping it will have a fix.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
I think at this point, now that it's been narrowed down pretty far, we need to file an official bug report with CM...how you do that I have no clue, lol. But an extensive writeup with all the info found in this thread and the other thread should be part of the bug report.

Does anyone know how/where you would actually submit something like that to CM?
[Verizon Samsung Galaxy S 4] DreamFX:
If you have been following the threads you will see that even flashing old cm builds, even jellybean ones no longer work. It's not a CM issue. It's a Verizon LTE issue.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Not true. I have been following the threads since the very beginning. Recently I flashed a Google Play Edition based ROM just to try something not CM or TW based and texting works. This leads me (and others) to believe, yes, there was some Verizon network change that triggered the issue, but the change Verizon made isn't necessarily wrong it just surfaced a longtime bug in the CM code base.
[Verizon Samsung Galaxy S 4] DreamFX:
A CM bug that killed texting for everyone including HTC devices, etc. And magically only affects certain areas mainly just central pa. And older CM code including jellybean and kitkat just suddenly stopped allowing texting. I can remind you that being on cdma and switching between airplane mode allows texting temporarily. This is an LTE issue. While it's out of my scope to say what on Verizon's end needs fixed. It's def their problem as the whole country would be out of commission if it was a CM issue.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Meh, who really knows...just what I've concluded from all my testing/reading.
[Verizon Samsung Galaxy S 4] DreamFX:
Neither one of us truly no the issue. I think we both can agree it's bizzare as hell! I say you pursue your angle I'll pursue mine and we can conquer this together.
[Verizon Samsung Galaxy S 4] S52Stu:
I really don't think it would hurt to send a official bug report to cm. But I wouldn't be surprised if someone did already. I too am leaning towards Verizon LTE in our area though. I check these threads daily and appreciate any feedback or ts options anyone brings to the table. I can't do more than test seeing as my phone is a work phone changing my number or calling Verizon is out of the question for me.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Yeah, srsly!