yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] theraptscallion:
I thought that might be the issue as well but couldn't find a way to turn it off. I tried freezing the WhisperPush ask as well as outright deleting it.

All of my installs have been after formatting system and wiping. I haven't gone back to Ics builds yet, but the problem arises seconds after a fresh install before restoring any apps and without enabling WhisperPush. I even tried forgoing Gapps for some of my testing. No effect. Now it's back to TouchWiz for the first time in almost 2 years.
[Verizon Samsung Galaxy S III] zcmack:
same thing happened again today. left my phone in the locker room (no service) and when i came back, it wouldn't connect to data anymore (orange bars showing but no data connection). i do not have the SMS issue. what is the APN issue being referenced?
[Verizon Samsung Galaxy S III] neolink1:
What version of TW are you using, is there an official kitkat one?

---------- Post added at 03:42 AM ---------- Previous post was at 03:40 AM ----------

When I flashed 3/5 my phone constantly showed a pop-up with "No APN on this device" or something like that. I didn't stay long on the build, and restored a nandroid. Issue went away.
[Verizon Samsung Galaxy S III] elreydenj:
Any one else having an issue with the camera borking after taking a video? Eventually causes a reboot.
[Verizon Samsung Galaxy S III] zcmack:
tried clearing cache and my data didn't come back. i restored a backup and now it is working fine. i expect it will happen again - is there anything i could or should be doing to capture a log for this issue? it seems that when data is toggled off and then back on an IP address can no longer be assigned.
[Verizon Samsung Galaxy S III] lostwhat83:
No APN specified on the device is driving me crazy. I reset APN defaults, created a new one with recommended Verizon APN settings. Still nothing, i even reflashed lastest build.
[Verizon Samsung Galaxy S III] TwistingSoul:
+1 for the no APN issue on the latest build.
[Verizon Samsung Galaxy S III] Jaegermeiste:
This exact issue has been driving me nuts.
[Verizon Samsung Galaxy S III] dmginc:
Switching to the AIO seemed like a great idea...
[Verizon Samsung Galaxy S III] TwistingSoul:
I remember the AIO from, I think, CM 10.2 days. Is there one for CM 11, or is it the same one?
[Verizon Samsung Galaxy S III] dmginc:
Not the aio firmware..I'm talking about switching from d2vzw to d2lte builds. So much is broken.
[Verizon Samsung Galaxy S III] fluffman86:
Voice+ appears to be busted in the 03/05 and 03/07 builds. My SMS in Hangouts are going out on my mobile number instead of my Google Voice number, costing me 20-ish cents a pop. :(

I think it may have started after someone texted my old mobile number. Now I've received SMSs on Google Voice, and they don't show up in Hangouts at all (even after wiping system / cache / dalvik and the app data for voice / voice plus / hangouts). At one point I wiped and some of the old messages showed up, so I responded to one that definitely came to my G Voice number, and it still went to them on my mobile number.

I've of course checked the settings in Hangouts itself. It lists my Google Voice number first, followed my my mobile number. If I click to verify the number, I can type in my google voice number again but it still doesn't work.

Going to try the official next and see if that changes anything.

Edit: Think this is part of the d2vzw vs lte change? I can't install an old d2vzw from february. acore and phone start force closing and I can't do anything. I don't have a recent nandroid (last one was january, woops) and it takes hours to get everything set up like I like it if I do a full wipe. :'(

Edit 2: Found this issue here as well: http://forum.cyanogenmod.com/topic/89591-voice-issue-in-nightlies-342014-and-on/
[Verizon Samsung Galaxy S III] BrwnSuperman:
Fixed this in Hangouts -> Settings -> SMS -> Access point names

Name: Verizon

MMSC: http://mms.vtext.com/servlets/mms

MMX Proxy: not set

MMS Port: not set

MCC: 310 (or whatever you have default here)

MNC: 002 (or whatever you have default here)
[Verizon Samsung Galaxy S III] TwistingSoul:
This worked like a charm! Thank you!

However, I still have the toast message about no APN specified for my device, but as long as I can get MMS messages, I can live with that for the interim.
[Verizon Samsung Galaxy S III] mastamoon:
Today's build might just fix the sms/mms issue!

Please give it a shot and let me know. Thanks!
[Verizon Samsung Galaxy S III] TwistingSoul:
I knew you wouldn't let us down, masta! Well done!
[Verizon Samsung Galaxy S III] Whisk_33:
Masta, Have you been able to reproduce or see any information on the 1SMS issue that some people are having? I had to switch back to TW in the mean time and this is a sad fact.

The problem popped up this February 20th while I was on your last 10.2 and continued into a clean flash of your 11 and official 11. I'm on a TW based now that got rid of the 1SMS issue, but going back to a CM based ROM brings it back. I appreciate all your work. So regardless. Thank you.
[Verizon Samsung Galaxy S III] lostwhat83:
Masta first off I want to thank you for all your hard work and dedication to sharing your build with others. I have been running your roms since... Forever it seems.

The new build didn't fix the MMS issue (not being able to send) for me, still getting the apn error every 15 sec as well. Just providing you with info you asked for.
[Verizon Samsung Galaxy S III] mastamoon:
Try deleting /data/data/com.android.providers.telephony/databases/telephony.db and the other telephony file and reboot.
[Verizon Samsung Galaxy S III] lostwhat83:
Didn't work. Im willing to try anything else. If there is nothing else i can do to help I'll do a fresh install after work tomorrow. Yes I admit I do dirty installs until I hit an issue (who doesn't though lol) Thanks for your help.
[Verizon Samsung Galaxy S III] mastamoon:
I havent clean installed in ages, im soooo dirty.

:eek:

Still working on it. My MMS is still working. :mad:
[Verizon Samsung Galaxy S III] elreydenj:
My mms worked and so did sms even though the no apn message appeared at times. My mms only stopped working after I decided to to a clean install unfortunately. After I wiped system and data I was no longer able to send mms.
[Verizon Samsung Galaxy S III] lostwhat83:
In that case ill hold off on the clean install.

I noticed that the stock messager is keeping my phone from entering deep sleep. "Mms connectivity" is keeping it awake. I received that info from Wakelock detector.
[Verizon Samsung Galaxy S III] lostwhat83:
Ok. Todays build gives me the sames issues. I made hangouts default app with the settings above mms works! I have to freeze the default message app to stop the cpu wake locks. I dont get the apn toast messages anymore. Im guessing its because of the hangouts apn settings or the frozen stock messenger.
[Verizon Samsung Galaxy S III] LongLiveCappy92:
I clean installed yesterday's build (3/10) after I experienced MMS issues. It didn't fix it, so I upgraded to today's build and it was still messed up. I tried the Hangouts settings others have mentioned and that IS working for me at the moment. I just don't like Hangouts, so I'll switch back and forth from stock when I need MMS abilities.
[Verizon Samsung Galaxy S III] mastamoon:
Today's build might really really really fix MMS issues... :)

LMK

EDIT: THANK YOU [MENTION=4727035]Desterly[/MENTION] :good:
[Verizon Samsung Galaxy S III] neolink1:
Giving it a try, will report shortly... Thanks a lot for your continued efforts to fix this. :good:
[Verizon Samsung Galaxy S III] fluffman86:
Any news on fixing the Voice+ bug?
[Verizon Samsung Galaxy S III] mastamoon:
What bug?
[Verizon Samsung Galaxy S III] fluffman86:
Asked about it here, a few pages back. Not an official bug.

Since then, I made a nandroid and did a fresh install, which didn't help. The nandroid failed so I'm back on a late February build, fresh install, and everything is working fine.
[Verizon Samsung Galaxy S III] neolink1:
Looks like I'm still having some SMS issues. The first SMS goes out fine. If I send another one shortly after, it's stuck "sending". MMS seems to be working well. I've sent a few back to back without issue. (I also don't have the APN issue on 3/12)

All those tests were on the stock messenger app, and a dirty flash.
[Verizon Samsung Galaxy S III] LongLiveCappy92:
Dirty flashed today's update (3/12) after clean flashing 3/10 and dirty flashing 3/11. All my MMS issues are fixed, I can send and receive MMS through stock messenger, not just Hangouts.
[Verizon Samsung Galaxy S III] ef-civic:
Mine seen to be fixed now too.
[Verizon Samsung Galaxy S III] lostwhat83:
Masta you are the MAN! Dirty flashed 3/12 and BAM! Stock messenger works and no more apn toast messages. Thank you for sharing the fix with us.
[Verizon Samsung Galaxy S III] fromthesticks:
I came from the last d2vzw and flashed d2lte of Fridays build I believe. Worked well until Monday, had a new sim card inserted need to reboot notification.. Rebooted and while on WiFi at work everything seemed fine. Left and had no data/calling.. Changed data/mobile settings and data came back and calling. Later that night same sim card notification message appeared. After the reboot had no data or calling.. I got data working but couldn't make calls, flashed Tuesdays nightly to try to fix and same results (data no calls) used groove IP to make calls. Wednesday same, flashed 3/12 no help. After work today I wiped system/data and flashed dtvzw and am. Currently having no issues. Maybe my issue was a fluke, I searched the forums yesterday and today but didn't see anyone with the same issue.
[Verizon Samsung Galaxy S III] ef-civic:
This morning I'm back to messages not being sent.

But if I reboot the phone, they are sent.
[Verizon Samsung Galaxy S III] mastamoon:
sms or mms?
[Verizon Samsung Galaxy S III] mastamoon:
Can you pull a log cat of the sms getting stuck? One that contains it working and then not would be best.

Grab a logcat app from market if you dont know how to use ADB.
[Verizon Samsung Galaxy S III] Whisk_33:
Masta,

I've been having this problem on the S3 since Feb 20th even on your last CM10.2 , but it seems to also be on the S4. An user TxdoHawk has a logcat posted here (Thread OP) http://xdaforums.com/showthread.php?t=2654822

I can't get to my S3 at the moment.
[Verizon Samsung Galaxy S III] ef-civic:
Sms
[Verizon Samsung Galaxy S III] mastamoon:
Have you tried re-registering with whisperpush?
[Verizon Samsung Galaxy S III] tv31284:
I didn't switch sims but I had the same issue. Flashed the 3/13 coming from 3/6 and lost the ability to make calls. Did a clean install with the 3/13 and everything's fine now.
[Verizon Samsung Galaxy S III] jkabaseball:
I am having an issue with cell signal quality. I no longer have 4G and 3G seems lower then normal.

I tried changing my prefer network and that didn't help. Any ideas?
[Verizon Samsung Galaxy S III] theraptscallion:
I have tried that with no result. If you need another logcat, just pm me and I'll install the latest, capture the logcat, and restore a terrible TW nandroid.
[Verizon Samsung Galaxy S III] Supercutetom:
I really don't think it has to do with Whisperpush. I have tried different versions of CM all the way down to 10.0, various version of Slimbean, slimkat, carbon, paranoid... All to no avail. Literally any non-touchwiz does not work for me.
[Verizon Samsung Galaxy S III] mastamoon:
Your imei and meid info is correct?

I'm thinking that somebody should try flashing back to stock, then do a NV restore.

It's very odd indeed.
[Verizon Samsung Galaxy S III] mastamoon:
if this doesnt get merged today, ill build with it..

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

Hopefully this will fix things up.
[Verizon Samsung Galaxy S III] neolink1:
Yes, I'll try to grab those and post later. Sorry, been pretty busy lately.
[Verizon Samsung Galaxy S III] mastamoon:
Anybody having that sms issue (1 send then no send), try this build please ... http://mastamoon.truelinux.net/ROMs/test/cm-11-20140314-UNOFFICIAL-mastamoon-d2lte.zip
[Verizon Samsung Galaxy S III] tv31284:
I've noticed something weird. Since clean fishing to the new build from 3/13 I'm unable to use certain sites (bank of America) and apps (bank of America and scramble with friends) if I'm on LTE. The sites and apps won't load. However if I'm on Wi-Fi or 3g everything works fine. Thoughts anyone?
[Verizon Samsung Galaxy S III] fluffman86:
Yay! Dirty flashed to the latest 2014-03-14 and Voice+ is working again!

search tag: google voice plus
[Verizon Samsung Galaxy S III] mastamoon:
You didnt also happen to be having the 1 sms before having to reboot or airplane mode problem also were ya?
[Verizon Samsung Galaxy S III] Supercutetom:
I'll definitely attempt to flash your test build tonight Masta once I'm off work. That is if nobody else beats me to it and reports back.

Another thing I want to pass along is I flashed back to a stock TouchWiz rom and started from there but that had no effect either. I also odin'd but that did nothing as well except kill an extra hour...
[Verizon Samsung Galaxy S III] Whisk_33:
Masta,

I'm having the 1SMS issue. I factory wipe/cleared cache and dalvik cache. I flashed the one you posted on (post 655 today). I loaded the gapps you have post it. Let everything settle. Rebooted the phone. I open Catlog. Sent a text. Waited a minute and sent another text. That text failed.

I have attached that program. Please let me know if there are additional steps you would like me to take. Thank you.
[Verizon Samsung Galaxy S III] tv31284:
In fact, I just tried this on my other banking apps (discover and chase) and they don't work. I can access the app just fine but I can't sign on.
[Verizon Samsung Galaxy S III] ef-civic:
Yeah. 1 SMS sent. Next one failed
[Verizon Samsung Galaxy S III] dmginc:
Hey all,

Have you guys tried using Invisiblek's latest gapps (Linked here)? I haven't been having any SMS or MMS issues on any builds and this is the only thing that I can think of that could be different between my phone and yours.
[Verizon Samsung Galaxy S III] mastamoon:
Somebody should flash back to stock and do a nvrestore and then reflash back to cm11.
[Verizon Samsung Galaxy S III] mastamoon:
Although now that voice+ and whisperpush should be working correctly, maybe one of them is needs a refresh or data wipe or something.
[Verizon Samsung Galaxy S III] mastamoon:
Maybe you guys having problems should flash to the latest CWM and official gapps, just to take those variables off the table.
[Verizon Samsung Galaxy S III] Whisk_33:
I can do that right now. I used the CWM you posted here. I'll download the gapp from 20130813. I don't have an image of rooted stock. If you point me in the right direction I'll do that asap.
[Verizon Samsung Galaxy S III] mastamoon:
Use the official gapps from CyanogenMod wiki http://www.androidfilehost.com/?fid=23311191640114013

Use the official cwm, I'd just download rom manager and use it to flash cwm.
[Verizon Samsung Galaxy S III] Whisk_33:
Ok. I have the gapps from 20140105 signed.

I'll download rom manager and update to whatever CWM version it wants.

Is there an original rom I should be flashing or did you want me to do?
[Verizon Samsung Galaxy S III] mastamoon:
I would just try a clean flash with that stuff to be sure.

I'd that doesn't work, I'm hoping somebody will try going back to stock, and try doing an nvrestore. Then should be able to flash back to CM and see if sms work.
[Verizon Samsung Galaxy S III] ef-civic:
I did a clean install after you update today along with the latest gapps. Still can only send one text after reboot. I will try to Odin back to stock later and reinstall everything
[Verizon Samsung Galaxy S III] mastamoon:
The reboot nvrestore is probably what everyone will have to do. Something ain't right with your connection to vzw or something. And I believe you can only do that while on stock.
[Verizon Samsung Galaxy S III] fromthesticks:
How do you nv restore? Is that when you type the *#66774 or whatever number in the dialer to reset the phone?
[Verizon Samsung Galaxy S III] mastamoon:
No you do it from terminal.

su

reboot nvrestore
[Verizon Samsung Galaxy S III] ef-civic:
Can this be done in terminal emulator?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah but you might have to be stock to do it.
[Verizon Samsung Galaxy S III] fluffman86:
Never had that issue, but all of my texts go through Google Voice and Voice+ via hangouts.

For the day it was broken, on the 03-05 and 03-07 build, SMS was sending just fine via hangouts, albeit from the wrong number.
[Verizon Samsung Galaxy S III] theraptscallion:
I will odin back to stock tomorrow and nvbackup/restore (My SD card fried since last time I backed up). The problem happens even if you don't install gapps at all, which seems to indicate it's not related in any way to Gapps. For instance, I clean flashed to the latest official nightly and to yours, and didn't bother doing anything else, just to see if sms would work. Sends the first one fine, but not the second without toggling airplane mode or restarting.

There are now several threads in the S3 and S4 forums which suggest it's ALL AOSP roms in the affected geographical areas.
[Verizon Samsung Galaxy S III] mastamoon:
Don't nvbackup, If there is something wrong you will just back up the problem. The nvbackup isn't stored on an SD card.. Its on Internal memory somewhere, somewhere in the flash memory or something.

I would try just an nvrestore if you have done an nvbackup previously.
[Verizon Samsung Galaxy S III] Whisk_33:
OK. I used Odin and went back to a "stock.vzw_root66.tar" file I had laying around. I'm back on

Android 4.0.4;

Baseband VRLF2;

Build VRALF2;

(As with all TW Roms texts are working fine at the moment)

I just download Rom Manager to make sure my CWM is up to date. I just downloaded Terminal Emulator. You want me to type the following in to the terminal?

su

reboot nvrestore

After that what would you like to see? Flash back to a version of CM? Any preference for a 10.2/11/stable/nightly? Logcats at any point?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah do the nvrestore part (do you remember doing an nvbackup at some point?) then make sure everything is still fine in TW. Then install the latest official nightly. Keep my stuff out of the picture for now. So use the latest CWM, latest official gapps and latest official nightly.

Clean install.
[Verizon Samsung Galaxy S III] Relentless D:
Someone correct me if I am wrong but isn't this extremely important? I've seen some people in here talking about doing a nvrestore but this is the first time I have heard mention of the nvbackup. It's my understanding that if you haven't done a nvbackup then a nvrestore will restore blank data to a critical area.

Just making sure we are all playing safe :)
[Verizon Samsung Galaxy S III] mastamoon:
Early phones left the factory without the nvbackup done and is why so many people broke their phones. Later phones had this performed at the factory so it should be ok to do a nvrestore if you had either done a nvbackup previously, saving good data.. Or have a newer phone that should have had this done at the factory.

I dont know the cut off date, it should be safe if you haven't lost your imei during all the flashing lately.

Problem is you can't do an nvbackup on a broken phone as your just overwriting possibly good data with bad.
[Verizon Samsung Galaxy S III] Whisk_33:
I pre-ordered my phone so I would imagine I was one of the early ones. But when I was flashing regularly there were many people that were having problem with their IMEI and such. I think I remember going through the process of backing that stuff up, but I really don't know. Is there a file I should have to confirm? It sounds like nvrestore my be bad unless I can confirm a backup.
[Verizon Samsung Galaxy S III] mastamoon:
No, there isn't a file generated by nvbackup. Before nvbackup was found there were other methods of backing up your efs, but once nvbackup was found, it was the only solution needed.

If your not sure you did nvbackup in the past, not sure you should do nvrestore. I thought everyone does it as a precaution since for some reason our efs is easily corruptible.
[Verizon Samsung Galaxy S III] Whisk_33:
OK. Well how about I do this.

I just backed up my current using plan B from http://xdaforums.com/showthread.php?t=1852255&highlight=nvbackup

Lets Assume I did a nvbackup correctly before. I should be able to just do the su nvrestore and everything should be gravy.

If I restore a blank file. I can still manually flash my current back up that I just made manually. Worst case I'll be where I am now.

I'm trying to get you the information you. If you have other ideas, I'll do it.
[Verizon Samsung Galaxy S III] mastamoon:
If your willing I'd like to know if it works, as will many others having the same problem.

I just don't want to be responsible for messing up anybody's phone.

Thankfully these phones are almost unbrickable so there is very little you can do to permanently kill your phone, as long as your willing to do some work if something goes wrong.
[Verizon Samsung Galaxy S III] ef-civic:
Nvrestore seemed to have fixed my phone. Still early but texts have worked all day
[Verizon Samsung Galaxy S III] neolink1:
I'll have to give this a go. Incidentally... if you did an nv backup you should see blue text on boot (top left corner). I'm not sure of this is also the base for phones that had it done at the factory.

Thank you all for your continued efforts to resolve this.

PS: I'd they're a specific version. Of TW I should Odin back to?
[Verizon Samsung Galaxy S III] mastamoon:
You might not need to Odin at all, might be able to flash a stock based rom. Not 100 percent sure though.

Glad it's working though!
[Verizon Samsung Galaxy S III] neolink1:
It wasn't much of a pain to just odin and start clean compared to all the stuff we've tried... Either way, this (nvrestore) fixed it. No more issues with SMS or MMS.

Thanks again.
[Verizon Samsung Galaxy S III] tv31284:
I just went back to a touch wiz ROM and everything works fine. Can anyone else comment on this? I've tried clean flashing the latest CM but that didn't help. I thought it was an APN issue but the settings seems to be the same on the touch wiz ROM. Any help would be appreciated.
[Verizon Samsung Galaxy S III] Supercutetom:
Well on any Stock TouchWiz rom nvrestore doesn't allow my phone to boot afterwards. Am I doing it wrong? I know it is...

su

reboot nvrestore

I guess I'll have to try Odin later on today. I haven't used Odin in well over a year. I'll need to find the files.
[Verizon Samsung Galaxy S III] ef-civic:
I had to pull my battery to get my phone to reboot after I did nvrestore. Working good so far. I was on mastas cm11 though
[Verizon Samsung Galaxy S III] mastamoon:
I believe going back into CWM and flashing either a stock rom or factory reset and flashing cm would work at that point.
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
Okay can someone explain this to me from the beginning. I was on one of the latest Cm nightlies when my texts stopped working. I tried carbon and doing a bunch of restores like most to try and get my texting back. I'm in the 717 area code. I'm now on AllianceROM because I need to be able to text. How do I go about doing this backup and restore you all are referring to? I've never heard of it. Any help would be greatly appreciated.
[Verizon Samsung Galaxy S III] gt43aw:
If u flashed a ROM and lost your imei (or have a corrupt one which this thread is speculating is causing the texting issues) and u never backed up your imei using the synergy zip file or nvbackup then you're out of luck and should not do an nvrestore. Its in the stickies in all the s3 forums to make sure u do this or risk beaucoup problems. Sorry dude. I just heard on another thread that if you have a newer s3 the nvbackup may have been done at factory. It's a gamble if u didn't do it yourself and u may end up with a phone that can't get on Verizon's network. Good lluck man. I lucked out and did the nvbackup. I'm on a tw ROM now. But I may try it and report back if I ever get time and motivation. Kind of tires of mucking with my phone.