yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] invisiblek:
wtf...what a ridiculous fix...i mean, glad its working and all...but wtf

For those that HAVENT done that (looking at you [MENTION=939687]efa[/MENTION]dan), please try this apns-conf and see if it fixes it for you before going that route. I'd rather not have to tell people to flash stock, blah blah...

http://invisiblek.org/tmp/apns-conf.xml

(You may need to right click and save the file or it might try opening in your browser)

(Push it to /system/etc/ and reboot)
[Verizon Samsung Galaxy S 4] efaden:
I'll give it a try tomorrow before I go through the flashing fiasco...
[Verizon Samsung Galaxy S 4] yooeee:
Where did this come from? Didn't read anything about it the past month. In regards to the apn xml
[Verizon Samsung Galaxy S 4] Kevin M:
Thanks for looking into this. Issue persists.
[Verizon Samsung Galaxy S 4] invisiblek:
Yea, figured that out =P

I have some patches in review that should hopefully fix it up.
[Verizon Samsung Galaxy S 4] Kevin M:
Great! Is this the APN config patch that will do it? http://review.cyanogenmod.org/#/c/60697/

Edit: Pushed this guy to my phone but the problem persists even after resetting the APN settings to default.
[Verizon Samsung Galaxy S 4] yooeee:
well, yeah, it sucks to have to do GPE and all that, but it's the only thing that's worked. until something better comes along, but I found my fix and it stuck.

can you explain the source of all the problem?
[Verizon Samsung Galaxy S 4] efaden:
The APN Conf didn't work... but the GPE then reinstalling CM worked. I am back up and running. WOOT!

-Eric
[Verizon Samsung Galaxy S 4] E01010100:
Work for me too.

I really think this works because it changes out the kernel. I'm now running kernel:

3.4.0-cyanogenmod-g5dc7548

Is there a way someone could provide this kernel separately. I think if the kernel could be flashed by itself it would save a lot of troubles.
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
Not sure how that could be - if flashing the GPE and then a nandroid restore of any ROM is all it takes - nandroid will restore the kernel packaged in the ROM. Though what ISN'T part of a nandroid that this 'fix' is leveraging is beyond me.
[Verizon Samsung Galaxy S 4] lowmanb94:
Upstream?

I would also like to chime in in regards to the proposed reprovisioning fix for the s3.

I have completely nuked my phone back to the day one factory image with heimdall to reprovision twice.

Even with a fresh sim the second time, the texting issue still prevails. In addition, I have had no luck with nvrestore or a manual efs partition restore I made some time ago.

Has anyone reported this upstream? I'm not exactly sure how that would work, but this certainly seems to be the result of some discrepancy between the information associated with an AOSP ams and an officially supported rom (TW or GPE in the s4 case) sms when routing through Verizon that wasn't checked for before some change was implemented on the network end.

Seems like a one line fix to me if the right people knew what the issue was.
[Verizon Samsung Galaxy S 4] DreamFX:
You by chance in PA or VA?
[Verizon Samsung Galaxy S 4] E01010100:
I thought nandroid would have restored the kernel too but ... *shrugs*

I would test further but I tried to do full disk encryption with 10.2 before I knew that there was a known bug that results in encryption failure. Due to that failure, whenever I install a GPE ROM my phone thinks it is encrypted (despite the fact that it is completely unencrypted). I've tried every type of wipe I can think of (cache, devalik, data, user, factory reset) and the phone still think it is encrypted. Put it back to CM or LiquidSmooth and it runs fine (after the GPE flash)

I did use this link to flash and before the flash I had KT-SGS4 kernel and afterwards I have the CM 3.4.0.
[Verizon Samsung Galaxy S 4] iamjonmiller:
Same Problem on HTC Droid DNA

I am in SW VA, is this a supposedly localized problem? I have been dealing with this for a little over a week on my Droid DNA. I was running Liquidsmooth 3.0 (KK), but also tried Sense ROMS, GPE ROMS and CM to attempt to fix it. Nothing has worked. I still kinda think Verizon is screwing with rooted people, but it might have just been a change on their end that needs to be worked into the base code.
[Verizon Samsung Galaxy S 4] DreamFX:
All these fixes work for people not in those states. Mostly myself and others in 717 / 570 PA area codes and parts of MD and VA no matter what fix you try nothing works. I have my own thread setup in the note 2 vzw question section with everything I have tried (everything under the sun) but I believe it's a vzw issue blocking aosp texts for us folks In these areas.
[Verizon Samsung Galaxy S 4] lowmanb94:
Yup. I hop between 540 and 434, but The issue started occurring when I was in 540 about a month ago. Like many others, I had been running cm10.2 since it went stable.

The only thing I haven't tried is an explicit nvrestore. I have reprovisioned (which I believe accomplishes the same thing), and restored a backup of the efs partition that I know is good, but I haven't run the native samsung utility. I believe others have had success with this exact method.

Ill test and report back when I get the free time to play with it -- I know this is really the only active thread on the topic, and its an infuriating issue.

..and every day I'm not on AOSP I die a little inside.
[Verizon Samsung Galaxy S 4] iamjonmiller:
Agreed...

I can't stand this either. There is no way in hell I am using sense over AOSP. I would rather toggle my Airplane mode every text than do that!

On another note...I am a 540 too. Neighbors?
[Verizon Samsung Galaxy S 4] DreamFX:
I die a little every day as well lol
[Verizon Samsung Galaxy S 4] Cilraaz:
While the process worked, it's definitely not related to the kernel. That kernel is from CM11, not the GPE ROM. Both a nandroid restore and normal flash of a ROM will install the new ROM's kernel. If it is the kernel that fixed the problem, then someone who is currently having the problem should be able to clean flash a current CM11 nightly and no longer have the issue.

Personally, I swapped to the GPE ROM back when the issue first happened a little over a month ago. I hadn't updated my ROM since. Today, I did a nandroid backup, backed up app data in TiBu, wiped system and data, flashed a current CM11 nightly (Euroskank's nightlies), and restored from TiBu. My texting issue is also gone. I have no clue why this worked, unless something was updated in CM11 that fixed the issue. I'd be interested to see what happens if someone who has the issue updates to a current CM11 nightly.
[Verizon Samsung Galaxy S 4] yooeee:
Well I am 301 area code and currently in Tucson. Was struggling with this issue for weeks until I flashed GPE. Not sure what to say, but that fixed it (I used this link http://xdaforums.com/showthread.php?t=2643031).

Can't speak for any over phones (GS3, or Note or DNA). I think I've counted 6 people including me that GPE fixed this issue. Everything else seems to fail. GS3 mentioned that Stock ICS and *2676.... to reset the phone / reprovision worked, but others said it didn't work.

I feel everyone's pain. good luck
[Verizon Samsung Galaxy S 4] DreamFX:
I'd love to try a GPE rom but we don't have them. Just touch whiz or aosp.
[Verizon Samsung Galaxy S 4] net-cat:
This is more or less the procedure I outlined for the S3 here, but I used a TouchWiz ROM. In the S3's case, it seems to be dependent on the radio flash you end up using after you've done the procedure.
[Verizon Samsung Galaxy S 4] Neuspadrin:
Just chiming in that the flash GPE -> send few texts on lte -> reflash to CM has resolved the issue for me as well.
[Verizon Samsung Galaxy S 4] Kevin M:
Looks like that is what I'll have to do. Unfortunate the process is so time consuming.
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
I guess I'm the first that the 'fix' of flashing GPE didn't work. Not sure why, but here's what I did:

Started: 3/7 Nightly (the last upgrade that had working SMS)

Created 3/7 Nandroid

Updated via CM updater to 3/29

Confirmed SMS would not send

Booted to recovery

Created 3/29 Nandroid

W/out leaving recovery:

Factory reset

Flash GPE

Started up, skipped adding google account to speed things up

Set the APN and Network per the GPE setup instructions

Confirmed I could send SMS - so far so good...

Booted to recovery

Restored 3/29 nandroid

Reboot - Things went south here...

Would only get the Samsung screen but would never show CM splash

Tried several reboots - nothing

Booted to recovery - installed the 3/29 update

At this point I booted up into CM, however:

1)I could not send SMS any more

2)Things were really messed up -

2a)The pull down shade had no settings button or any of the buttons actually for wifi/bt/etc, had to find in the app drawer

2b)Despite the settings under Settings->Buttons->Power menu showing every thing like screenshot/airplane/volume, reboot into recovery, etc, the power button menu actually only showed shut down and reboot(w/out submenus for recovery)

Finally got mostly back up and running (including sending SMS) at my original state of 3/7 by flashing the nightly from that date, then restoring the first nandroid, however it still didn't completely restore everything - I had no keyboards and had to re-enable swiftkey which I rarely use and completely reinstall swype from the store, which is my default keyboard. Before re-installing it I tried a titanium backup restore, and it failed.

So for whatever reason the nandroids really didn't restore everything like they should, and I was unable to move past 3/7 and send SMS.

Ugh.
[Verizon Samsung Galaxy S 4] dadoc04:
After I flashed the gpe rom and confirmed texting was working, i clean flashed the aosp rom of choice, not nandroid restore.

Give that a shot.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Neuspadrin:
Did you factory reset before restoring backup? Just didn't mention that step.
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
I don't think I did the first time around. I may have the second time but I can't remember for sure. Regardless, a Nandroid shouldn't need a wipe ahead of time anyway as far as I am aware?
[Verizon Samsung Galaxy S 4] yevgenydev:
Does a nandroid backup retain the device-id?

I am hesitant to do the flashing trick, as my work requires an RSA-Soft token. And it is a pain in the ass to have a new one re-issued everything I reflash a rom.
[Verizon Samsung Galaxy S 4] Oishikatta:
Titanium backup should be able to backup/restore the Android ID.

I'm not sure how exactly to access the feature, but it should pop up if you backup an app and make/flash a flashable zip of titanium backup (in settings).

There's a screen of what I mean here: http://xdaforums.com/nexus-4/general/titanium-backup-android-device-id-t2006461
[Verizon Samsung Galaxy S 4] FernBch:
Open TiBu, choose "Menu", choose Manage Android ID, and choose restore from backup.

If you restore a from a nandroid the ID should be the same. If you flash clean when you open TiBu the first time and choose your existing backup folder it should ask if you want to restore a previous ID. If it doesn't you can restore it using the above steps.
[Verizon Samsung Galaxy S 4] dadoc04:
I always wipe before restores... But i didnt do a restore for this texting issue. All clean flashing

1. Factory reset wipe including system

2. Flash gpe rom

3. Follow Lte enable steps

4. Test text, reboot, test text more

5. Factory reset

6. Flash slim, cm, liquid smooth + gapps

7. Text... Reboot... Text

Hopefully InvisibleK gets an easier fix for u guys soon. This "ridiculous fix" has been the only thing thats worked so far and it kinda sucks... Good luck yall

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] iamjonmiller:
Long Term

So, what's the long term plan here? It seems to be a rather large, but still isolated issue, so will a fix make it's way into the source code?

I just am so confused by this whole thing. Is it Verizon doing something nefarious? Is it just a change that they made to SMSC that needs to be added? Did we all somehow break our devices through our silly hacking? Are our SIM cards going bad? Is this some geographically confined thing? Like WTF is going on?

I have done so many wipes, tried every type of ROM, radio, firmware etc. As a DNA user, I don't have an official GPE ROM, so my only option seems to be stock. I consider myself quite proficient, I know what I am doing.

Also, we should remember that it just happened. Almost randomly on perfectly functional ROMs across numerous devices SMS stopped working.

So yeah, I guess us DNA users that are unlucky are screwed for now.

What do you guys think?
[Verizon Samsung Galaxy S 4] DreamFX:
Tried everything you did but with note 2. We also have no GPE rom. I also am good with this stuff and never felt so helpless in my life.
[Verizon Samsung Galaxy S 4] PhilDX:
have any of you guys filed an official bug report with CM? it sounds like its fixable (since GPE works), but since it's a relatively localized problem, they might not even know about it yet.
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
My fingers are crossed - this update has been tweaked several times this month and the latest update is pending for the next build. I'm really hoping this resolves the problem one of these days :)

http://review.cyanogenmod.org/#/c/60697/
[Verizon Samsung Galaxy S 4] DracoDan:
Been having this problem for about a week now, just found this thread today. I just tried the latest build that should include that fix, but no such luck, still getting error code 34.
[Verizon Samsung Galaxy S 4] iamjonmiller:
If you read the changelog the fix was for MMS not SMS.
[Verizon Samsung Galaxy S 4] Kevin M:
I might be incorrect in thinking this but our problem is more than just an APN configuration problem. Wouldn't copying the GPE APN config fix it? I though that's already been tried.
[Verizon Samsung Galaxy S 4] Cilraaz:
Of the people who "fixed" their problem by flashing GPE and then a CM11 build, have any of you flashed an updated CM11 nightly after that? I'm slightly afraid to flash a new CM11 nightly on top of a working setup at this point.
[Verizon Samsung Galaxy S 4] dadoc04:
Yes.... Flashing updates is fine... Im on liquid smooth 3/31 still texting. ;)

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Cilraaz:
Thanks for the info!
[Verizon Samsung Galaxy S 4] lowmanb94:
Possible GS3 Solution?

I know this is a GS4 thread but the issue seems to prevail across both devices and this is the only active discussion on the topic.

So I have done a few things and outgoing SMS is now working for me on the 4/03 CM11 nightly.

1. Heimdall back to day one (ICS) stock. This includes EVERYTHING, including the "Pre-Release" GL1 Modem. Be careful not to let your phone update -- it only took about 5 minutes of being idle for the 4.3 update to automatically start downloading for me.

2. Complete "factory format" with *2767*3855#

3. Root, unlock bootloader, and flash twrp 2.7

4. Flash CM 4/03 nightly from twrp.

SMS continued to work after flashing the MF1 firmware, but when I flashed the ML1 modem the issue recurred. Flashing back to the MF1 firmware did not resolve the issue. That is, I had to start over and flash all the way back up to MF1.

I hope this might help someone, although I really don't have enough knowledge or extra time to speculate on what is causing the issue (or what steps above are superfluous).

***EDIT: It seems as if I had spoken to soon. After exactly two reboots, the problem persists.***

I am out of ideas and patience. I have spent almost a month trying to resolve this to no avail. My guess is that a solution to this is simply out of our hands (at least for the GS3). To TW I go...

..sigh.
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
Maybe this from the 4/4 Nightly will fix our problem?

http://review.cyanogenmod.org/#/c/62148/
[Verizon Samsung Galaxy S 4] DreamFX:
That's only for mms
[Verizon Samsung Galaxy S 4] broscup:
Over it

Well, I'm a little over explaining to people why they are getting a different number from me when I text them, and I'm not going to add a subject line to every text to convert it to mms.

I'm not someone who jumps from ROM to ROM. I hate going through the task of backing up and restoring.

What's a lean, stable, TW ROM that's out there?

I'm really going to miss CM.
[Verizon Samsung Galaxy S 4] Odd_Sam:
I've been plagued with this SMS issue for a month or so. In the 540 area code. I've finally taken the time to do this process and it worked perfectly. Really strange this process works.
[Verizon Samsung Galaxy S 4] dadoc04:
Glad its working for ya...

#RidiculousFix
[Verizon Samsung Galaxy S 4] st33med:
I know this is the wrong place, but it's an active thread here, so...

I have a Verizon S3 with CM 10.2 and have been plagued with issues like everyone else. I stopped updating my phone some months ago around a nightly release of CM 10.2, which is really old (like last Fall I believe). It then started acting up some weeks ago. I did not change any settings on my phone, did not change SIM card, whatever. Decided it was a bug and updated to the recent stable version of CM 10.2.1 through the CM updater(so I don't have to wipe and reinstall). Did nothing to solve my problem. Tried changing my SMSC through the Phone app, nothing.

Right now I'm trying out GoSMS and using it as the default SMS app with a regular SMSC. Don't think it will work, but worth a shot...
[Verizon Samsung Galaxy S 4] st33med:
Did not work.

Switching to CDMA/EvDo mode seems to work. I had it stop working when I hit refresh on the SMSC. It also maybe because it switched to EvDo mode. No idea. I'll report back later.
[Verizon Samsung Galaxy S 4] Chopes:
Still interested for a fix for this. Having to resort to GV for services to get around this currently.
[Verizon Samsung Galaxy S 4] dwitmer1989:
Trying rediculous fix as we speak

---------- Post added at 09:13 PM ---------- Previous post was at 09:10 PM ----------

Wow gotta admit I'm befuddled. That ridiculous fix seems to have done the trick for me too. Very odd. 717 area code ose ROM.
[Verizon Samsung Galaxy S 4] neganox:
ridiculous fix works. its a pain, but at least its something.
[Verizon Samsung Galaxy S 4] thebeen:
interesting issue

hey everyone! so i have a very interesting, but seemingly opposite issue. It's happened to my verizon device before.

so I have no problems using SMS on my verizon s4. I have a 310 area code, and I travel from los angeles and chicago often. SMS has never been an issue.

MMS, however, is a different story. Group TXTs, as you know, are handled by MMS. I am running Vanir's 4/8 nightly, and will have frequent issues with sending MMS messages after the first few go through on a reboot. Airplane mode on/off/on sometimes helps, but rebooting works....and then I can usually send 3-4 MMSs or do a group text for 5-6 convos, then it just stops sending. Pretty annoying. here is what makes me think its a ROM issue. I am not a daily flasher, more like a monthly, two monthly flasther

Sorry I can't particularly remember which versions or nightlies I used. I also keep the kernel that comes with the ROM.

STOCK TW -- no problems. hated tw and wanted root.

Hyperdrive RS11 -- MMS problems began

Beanstalk -- MMS problems persisted

CM 10.2 stable -- woah, MMS problems gone. No issues. It felt amazing

Vanir 4/8 nightly -- MMS problems restart, almost even worse.

I've read through the entire thread. There seems to be two "fixes" in progress -- not sure if i can try them out on my vanir

http://review.cyanogenmod.org/#/c/62148/

http://review.cyanogenmod.org/#/c/60697/

---------- Post added at 09:06 PM ---------- Previous post was at 08:55 PM ----------

also, just for fun sakes, I used to own a verizon galaxy nexus. Similar problems. Happened to my friend too. MMS issues.... where are they coming from?
[Verizon Samsung Galaxy S 4] DreamFX:
All the folks trying to get aosp texting working on Note 2's and no method worked please PM me your phone number I'm going to let VZW know everyone on here who is having issues so I can have some engineers work on this.
[Verizon Samsung Galaxy S 4] kamunist:
Just did this but instead of clean flashing the new ROM (step 6) I restored from nandroid. So far so good, fingers crossed it holds up. Thanks dadoc for the solution! As you said, it wasn't that hard after all.
[Verizon Samsung Galaxy S 4] dadoc04:
Good **** man..... That's cool nandroid is working for u. Maybe more people will try this ridiculous fix now

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] warblade24:
I am experiencing this issue now too. I followed the ridiculous fix and I'm still having issues sending MMS. Receiving seems to be working fine however. I am on cm11 now after coming from the GPE flash. I'm out of ideas now...
[Verizon Samsung Galaxy S 4] PhilDX:
what state are you in? and please don't tell me you live in NJ... we have enough problems here already :)
[Verizon Samsung Galaxy S 4] warblade24:
PA. Right outside Pittsburgh
[Verizon Samsung Galaxy S 4] mcbeat257:
Reply

You might want to also try to reinstall the module drivers to your system. Flash this file using Odin or SafeStrap, and you should be good.

Verizon Wifi and LTE Drivers:

https://dl.dropboxusercontent.com/u/17588097/jfltevzw-MK2-modules.zip
[Verizon Samsung Galaxy S 4] snael:
I am ready to try this as my texting has been completely unreliable. In odin which slot do I put this in?

EDIT: Nevermind, flashed it in TWRP and it seems to have worked? will see if my texting is better.

EDIT2: lol don't flash in TWRP, broke my wifi at least. (yes I just wanted to see if it worked)
[Verizon Samsung Galaxy S 4] dadoc04:
U try this??

http://xdaforums.com/showthread.php?p=51502032

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] snael:
I actually hadn't. I skipped it and went for a full ODIN back to stock and did a clean flash to AOSP and still had the issue. Upon you mentioning it I remembered reading it and gave it a shot aaaaaand it worked. I tried every other method and so far flashing GPE and then to AOSP was the only thing that worked for me. Thank you for bringing it up to my attention! Was afraid I would be stuck with TW for a while.
[Verizon Samsung Galaxy S 4] dadoc04:
Dope!!! Glad it worked for you. Go enjoy that c-rom or liquidsmooth now. :)

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] shot211:
Hello,

I've been dealing with the exact problem. Replacing the Sim card did not help. I've tried everything you guys have tried to no avail. I hope someone else chimes in...
[Verizon Samsung Galaxy S 4] DreamFX:
Me too. I have note 2 and nothing posted here and then some works.
[Verizon Samsung Galaxy S 4] jackdubl:
Now S4's running the very GPE rom you guys are flashing as a fix are having LTE problems here in Kansas. No uploads while on lte, which affects(guess what?) outgoing texts, among other things. I think the xlte rollout is affecting aosp roms in regional areas. Confirmed all GPE roms in much of Kansas affected since a few weeks ago.

Free storage from Copy:

https://copy.com?r=cScoov
[Verizon Samsung Galaxy S 4] Mistertac:
I know this is a cm thread and there's a huge cm following but there are other ROMs for our phones that don't have this issue . seems like quite a pain to do that just saying

Sent From My Verizon S4
[Verizon Samsung Galaxy S 4] Cilraaz:
Yeah, and if CM doesn't fix the issue soon enough, I might try one. I've just gotten so used to the way CM works and where everything is that seeing something different is tough. I'm a creature of habit above all else, apparently.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Kinda cross posting, but w/e. I have the exact same issue! I literally woke up this morning with the issue. I've been runnin the 2/12 nightly with no issues at all and then suddenly this happened! I do remember seeing that Twitter and Chrome Beta updated overnight, but I doubt they're the issue. If I flash back to TW I experience no problems. Different modems and a clean flash of M3 didn't seem to help either. What the heck?!