yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
There's a discussion thread around here somewhere... The general thinking is that Verizon has changed something with the Network and it's exposed a problem in cm and cm based ROMs... It's not only 4.4.2 roms... Even 4.3 based roms are suffering the same issues and many of those roms haven't been updated in a couple months
[Verizon Samsung Galaxy S III] merdely:
Very interesting.

I never experienced the lost APN problem, but I was getting a constant reboot loop (receive text from friend, reboot, receive SAME text from friend, reboot, ...). So, I went back to 03/07 where I don't have that problem. I've received several texts from the same friend and others with no problems.

I *AM* having a problem with the camera again, though. I took video the other day and after the first video, the bottom edge of the preview screen was green and "off". Also, the bar code reader in MyFitnessPal works 0 or 1 times before I have to reboot (or I get the "cannot connect to camera" message).
[Verizon Samsung Galaxy S III] Jdelta9889:
Just as an FYI. I am on official 3/2 using stock SMS. Pic messages and text messages just fine.
[Verizon Samsung Galaxy S III] RedRumy3:
3/4 is last build I can use that works fine with stock messaging anything after that I get apn issues.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Do you think you could upload it somewhere and provide a link... 3/6 is the farthest back on cm site
[Verizon Samsung Galaxy S III] RedRumy3:
https://www.dropbox.com/s/f0juzguci2ekhh9/cm-11-20140303-NIGHTLY-d2lte.zip
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Appreciate the looking out but I still can't get messaging to stay working...I can get texts but after I send one... The rest fail... Happening on every non Touchwiz rom I try... I'm just at a loss on what to do or try... Ever suggestion that anyone had made, I've tried but no luck
[Verizon Samsung Galaxy S III] gt43aw:
Ditto. Exact same problem. Problem seems to be spreading and retroactively affecting ROMs that didn't have the problem. I've tried ROMs all the way back to 10.2.1. All clean installs.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
I've seen that as well... I wish the various rom devs were a bit more vocal just to let us know there thoughts on the issue... id certainly be willing to test anything they wanted lol
[Verizon Samsung Galaxy S III] darkknight1812:
I think the cyanogenmod team has fixed the issue judging by the change logs and code review.

http://review.cyanogenmod.org/#/c/60871/
[Verizon Samsung Galaxy S III] Div033:
Looks like they have a fix coming up in the next nightly:

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

Hopefully it works. I've been eager to upgrade to the latest, but have avoided flashing due to the APN issues.

*edit* beaten by batman, unsurprising considering he's a ninja.
[Verizon Samsung Galaxy S III] tonu42:
From the gerrit review.

"Apparently flashing to stock TW unbreaks all things LTE. D2LTE messed up something pretty damn hard, nothing else will undo it but an Odin to stock."

That sucks and people need to be careful not to take the update and screw themselves, my self included.
[Verizon Samsung Galaxy S III] EatonZ:
Latest nightly didn't fix APN issues. ):
[Verizon Samsung Galaxy S III] skrusrnmz:
Yeah, APN still not fixed with 3/12 nightly.

Dirty flashed first (wiped caches). That didn't fix it. Factory reset and formatted system next and that didn't work.

Based on the comments in gerrit are we going to have to odin back to stock to fix this?

The silence does seem strange.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
I have Odin back to stock but after flashing any cm or cm based rom... the problems come back.

I then wiped and formatted everything and flagged a Touchwiz rom and it came back... But lost again when trying another cm based rom

I believe Verizon has altered something in their network which is causing these issues... Around Feb 20 I and many others experienced some weird network issues and then something was committed around 3/4 that has really caused some major issues.

I'm on pacman right now and the only thing left that not working is my SMS...I receive but can't send after I send one

If you got the time... Try Odin back to stock then root with casual then format and wipe and clean flash the 3/12 nightly
[Verizon Samsung Galaxy S III] RedRumy3:
I'm gonna attempt to update and see what happens. I'm currently on 3/4 and have no issues with sms or mms with stock messenger. I will flash 3/12 soon.

Edit : so far no apn issues for me. But it's 3am I will test it out more tomorrow but last time it would just say no apn over and over. But it seems I am able to text I will try mms in the morning.

Edit2: Well I can't do mms but I can text fine. Mms gives me apn issue still.

Edit3: Had to restore back to my 3/4 build and can send mms and sms fine again. Guess I will stay on this build until they really fix this apn issue.
[Verizon Samsung Galaxy S III] merdely:
I've been on 3/7 without any issues related to signal or APN. The barcode scanner still isn't working and I think the video camera is broken, too.

Last night I installed 3/12 and I noticed this morning when I went off wifi that I'd go from signal to no signal to signal to no signal (constantly). So, I restored back to 3/7. I didn't think to try MMS, but I did send several texts back and forth on 3/12 last night with no problems.

Edit: I just tested sending an MMS and got the no APN specified for this device using 3/7. Boo! I wish I hadn't been so "delete backups" happy recently and could go back to when my barcode scanner, SMS, and MMS worked.
[Verizon Samsung Galaxy S III] NegativeOne:
Which builds are we talking about for APN issues?
[Verizon Samsung Galaxy S III] RedRumy3:
anything above 3/4 build gives me apn issues when sending mms.
[Verizon Samsung Galaxy S III] NedDasty:
I doubt it's a thing that Verizon changed; I've been on the 2/28 d2lte nightly and everything works perfectly fine. I haven't flashed a thing since then due to all the problems.

One thing I did notice; I don't know if it's a phone problem or cyanogenmod versus TW. I was in the exact same location as my mother, who is on a Galaxy S4. We both ran speedtest and her download rates were 2-3x faster than mine. I've never really tested, but does using CM really cause such a download speed hit? I might end up going back to a TW rom if this is the case. I've been using Cyanogenmod for years, so this would be a great disappointment to learn.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Well like I said I think it's something Verizon did because there are people still running 10.2 that ate having the same issues... I'm thinking Verizon changed which had exposed a problem with cm based roms especially those after 3/4...I have also noticed that most people having the issue are on the east coast, maybe that's a reason. In your case DON'T update till us others have verified everything working cuz right now your definitely lucky.

As for the download speeds, I'm not sure... I've ran speed tests on both tw and cm based roms in the same locations and haven't seen much of a difference but there's so many factors it's hard to tell
[Verizon Samsung Galaxy S III] stevey500:
I am coming from Galaxy S4 Verizon and HTC Incredible 4G development section to share that the MMS, data, APN issues the past while in CM11 nightlies are across all/most Verizon LTE devices are similar.

Attempting to flash back to 2/28 or earlier renders unbootable CM, having to clear-data in order to get smooth working 3g,4g, and MMS back. While there could be some network issues right now, the major APN bugs and MMS failure is due to the latest nightlies and awaiting a fix. It has been mentioned a few times in the cmxlogs
[Verizon Samsung Galaxy S III] d69oh:
Anybody have a dropbox copy of mar 1 2 or 3
[Verizon Samsung Galaxy S III] esjames:
Go back a few posts, someone else already provided a link.
[Verizon Samsung Galaxy S III] esjames:
Looks like the devs are working hard on fixing the mms issues.

http://review.cyanogenmod.org/#/c/61022/
[Verizon Samsung Galaxy S III] RedRumy3:
Awesome. Hopefully this fixes it.
[Verizon Samsung Galaxy S III] NedDasty:
GWallet spoofing

Unrelated to the MMS issue:

I saw there's an update to Google Wallet. I installed the Xposed region check remover (not sure it'll work for the new .apk), but I know that for initial GWallet setup, you still need to spoof your phone's ID.

I went to build.prop, and lo and behold, some of the old fields are gone, namely ro.product.model, ro.product.device, etc. These seem to have been removed on the switch to d2lte.

When I go to menu -> settings -> about phone, my phone still knows it's an SCH-I535. Does anybody know where this information is now stored, so I can modify it before installing Google Wallet?

Thanks.
[Verizon Samsung Galaxy S III] ecooce:
Ok MMS is working again, and Goggles/camera working also, thanks!!! N3/13
[Verizon Samsung Galaxy S III] EatonZ:
Seconded!:good:
[Verizon Samsung Galaxy S III] RedRumy3:
I can confirm latest nightly does indeed fix apn issue woohoo.

Now does any of you guys have instagram try talking a front camera picture does it reboot your phone after you take the picture with the instagram app.
[Verizon Samsung Galaxy S III] WarER4X:
I didn't even know SMS was broken on my phone until earlier this evening (I don't use traditional texting very much anymore), but the 3/13 build fixed it. Great work CM team!

I wish Google would fix some of its own bugs this fast (we all know how long the Chrome black screen hung around and I still have a location locator in Maps that can never decide which direction I'm heading).

-SR-
[Verizon Samsung Galaxy S III] chowner:
Pictures MMS works now, but video does not.

Does anyone have any insight or a similar issue?

Nice work on quickly addressing this!
[Verizon Samsung Galaxy S III] esjames:
I assume the text issue is resolved on this nightly as well? I would like to move away from my M build.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Not really quick considering the issues started almost a month ago for people... video has been working for me...
[Verizon Samsung Galaxy S III] elreydenj:
Any word on the issue when recording a video? After the first or at times the second video recording, the video gets screwy and almost like blurry which then renders the camera unusable. Sometimes causes a reboot. I know some others have reported this in this thread. Thank you everyone.
[Verizon Samsung Galaxy S III] phillya:
MMS works again on 3/13 nightly! Thanks CM team!!
[Verizon Samsung Galaxy S III] alershka:
I installed 3/13 and could not connect to data with BMS kernel. I am in a low signal area. I tried clean and dirty installs and a bunch of airplane mode toggling. I did not try with stock kernel. Nandroided back to 3/5 and was able to receive data again.

Edit: forgot to reinstall gapps prior to installing kernel. Looks like that fixed the problem.
[Verizon Samsung Galaxy S III] ecooce:
The issue is with the "focus", I think they are still working on a patch... edit: Actually it looks like an old interlacing issue (I know its a progressive screen), could also be a rendering issue when in camera mode???
[Verizon Samsung Galaxy S III] skrusrnmz:
Somebody hug a developer today! 3/13 fixed the APN issue.

I know these guys were working hard fixing this over the past week.

Thanks!
[Verizon Samsung Galaxy S III] cheekoo:
SMS/MMS news is awesome! is camera battery drain fixed too in the latest ones?

Update - seems like it did. I clicked a picture after installing the new build and don't se the drain.
[Verizon Samsung Galaxy S III] NegativeOne:
So is 3/13 solid for everyone? Sounds like all the issues called out over the last few days have been covered and fixed?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Running with no issues at all brotha. Except for camera of course ;)
[Verizon Samsung Galaxy S III] MajicManDroid:
What exactly is the camera issue you're having?
[Verizon Samsung Galaxy S III] skrusrnmz:
Anyone else having Voice+ issues? It doesn't seen to be doing anything. Texts are going through my phone, not Google Voice. I've tried clearing data.

This appeared with the APN problem but didn't get fixed with it.
[Verizon Samsung Galaxy S III] bmeek:
Nasty boot-loop from CMUpdater...

I was running the 03/13 nightly build with no real troubles when I used CMUpdater to flash the 03/14 build.

It appeared to operate as usual until it failed to boot - it gets permanently stuck on the blue spinning CM logo. A battery-pull from there, and I tried the 3-finger boot to recovery, but it immediately boots to the CMUpdater script - the animated green Android with the progress bar... When that finishes, it reboots only to get stuck on the blue spinning CM logo again.

Grrr!!!

The only difference last night from the dozens of CMUpdater-driven nightly updates I've taken previously, is that I was trying out the latest Ktoonsez' KT747 kernel. Usually, I'm running the stock CM11 kernel or decimalman's dkp kernel, but either way, I never had this problem with a CMUpdater-invoked update before.

So, any suggestions as to the path-of-least-resistance through ODIN to get back to my CWM recovery menu?
[Verizon Samsung Galaxy S III] chowner:
Volume up instead of volume down
[Verizon Samsung Galaxy S III] BrUhNiGGs:
The infamous "Can't connect to Camera Issue" every now and then
[Verizon Samsung Galaxy S III] RedRumy3:
Quick question probably answered before but searching doesn't show it cause i think its to short to search. My friend is now running the latest nightly of this rom and he asked me why he can't send gifs through mms. Basically he sends a gif and when i receive it its just a still image but it worked on tw roms for him.

Is it the stock messenger not being able to send gifs ?
[Verizon Samsung Galaxy S III] razorloves:
A fix is coming

http://review.cyanogenmod.org/#/c/61094/
[Verizon Samsung Galaxy S III] mastamoon:
If you guys wanna test a build with this commit merged, try my build.. http://mastamoon.truelinux.net/ROMs/test/cm-11-20140314-UNOFFICIAL-mastamoon-d2lte.zip

:)
[Verizon Samsung Galaxy S III] razorloves:
Right. The stock messaging app doesn't handle gifs properly, but Hangouts and several mms apps in the play store do. So if he sets Hangouts as his default messaging app and he sends the gif to someone using anything other than the stock cm messaging app, then it will work.
[Verizon Samsung Galaxy S III] bmeek:
Anyone else bootloop on the 03/14 build?

Well, thanks. I knew how get to ODIN and use it (although it's been a while...), so I was basically asking for a way to re-flash a working recovery via ODIN without going all the way back to VRBMB1 and having to step through obtaining root, unlocking the bootloader, etc...

Anyway, I referred to open1your1eyes0's "[GUIDE] No-Wipe Jelly Bean Factory Images ***Final Update: 6/1/13***". This includes a pointer to an old "VRBLK3 Bootchain with ClockworkMod Touch Recovery 6.0.3.1" image that I flashed via ODIN. Then, when I did a 3-finger boot to recovery, the CMUpdater process started up as before - but due to the down-rev CWM version, the script failed and returned to the CWM 6.0.3.1 menu. From there I was able to wipe data, format /system and flash CM10.2.1 with jb4.3 gapps (an older ROM I still keep on my SD card).

From CM10.2, I updated to CWM 6.0.4.5 via ROM Manager and I'm back in business with KitKat after a recent nandroid restore.

Whew...

So, has anyone else gotten into trouble flashing the d2lte CM11 03/14 nightly via CMUpdater, or was I just unlucky / stupid?
[Verizon Samsung Galaxy S III] skrusrnmz:
Thanks. I don't know why I don't start there when I hit a problem.

So if I'm reading that right we should see it tonight. I think I can wait that long.
[Verizon Samsung Galaxy S III] razorloves:
you're welcome.

and yea, it will be in tonight's nightly
[Verizon Samsung Galaxy S III] kick069:
i been shying away from CM11 since the unified builds (APN issues, boot loops etc.) If i flash a fresh install of 3/14 how is it looking so far?
[Verizon Samsung Galaxy S III] RedRumy3:
Working good, no issue atm.
[Verizon Samsung Galaxy S III] RedRumy3:
Yeah we tried hangout made it our default message app and when I send him a gif it shows it working on my end but he gets a still image. And when he sends me a gif it's same way working on his end but not on mine.

Anyone recommend another message app that has gif working?
[Verizon Samsung Galaxy S III] xs11e:
Total weirdness with CM 11 3/14 nightly!

I downloaded, hit the update and the S3 rebooted into TWRP and began the install. I got a bunch on text on the screen I'd never seen before* but it finished and started to reboot but hung up on the first boot screen.

I did a battery pull, booted into TWRP and re-flashed the 3/14 nightly and the phone rebooted as it should but.... a whole bunch of apps were gone including the Play Store, making it impossible to add any of the missing apps back so...

Rebooted into TWRP, installed a backup (CM 11 several days back). It installed, booted up OK, did a bunch of updated and all seemed well so I again did the update and it worked perfectly!

All is well but what happened?

*I haven't a good recollection of the text I saw, it was "formatting this", "clearing that", "wiping this" way too much to be normal. I dirty flash EVERY nightly so I have some idea of what the screen should say during the flash...

I did not re-download the nightly, just re-flashed the one that had failed the first try.

I'm puzzled. Any ideas?
[Verizon Samsung Galaxy S III] razorloves:
hmmm, that's strange. I sent a gif to a friend on tmobile htc one that has latest cm11 nightly using hangouts for sms and it worked. also to another friend on sprint galaxy s4 with touchwiz using the tw messaging app and it worked.
[Verizon Samsung Galaxy S III] skrusrnmz:
3/15 nightly fixed Voice+. Things are pretty smooth so far.

Thanks!
[Verizon Samsung Galaxy S III] darkknight1812:
APN Issues/Cell Connection Problems

I am still having issues. I am trying out 3/15 nightly and when it boots, the mobile connection is constantly going from full signal to no signal. I some how managed to at least maintain a connection once, but it will not send/receive mms and data. I have messed with the radio settings but still the same problem. I have tried modifying an APN connection along with creating a new APN but the settings do not show up in the menu. When I modify an existing one and save it, it disappears from the list. Any one else having the same issue?

I have found out that when I am on my Verizon network extender, the cell radio freaks out. The cell radio works fine when I unplug my extender though. I have logs if anyone is interested.
[Verizon Samsung Galaxy S III] Hybridnoob:
It sounds like your woes were kernel related. That happened to me a couple of times a while back when testing that kernel, so now I stick with the stock kernel - no issues now.

---------- Post added at 02:48 AM ---------- Previous post was at 02:41 AM ----------

Oh, and I think you could have just gone into recovery (interrupted the boot process), wiped caches and manually flashed the ROM you already downloaded. That would probably have saved you from having to Odin and start over. I know that doesn't help now, but maybe will next time! You definitely solved the problem, but used a nuclear weapon, when a bat may have worked.
[Verizon Samsung Galaxy S III] bmeek:
Thanks for the info. Since the kt747 kernel was the only variable in place when the process went south, I thought it was likely to be the cause, but since I never had an issue with dkp running when I use cmupdater, I wasn't clear on how the KT747 could get in the way like it did...

I generally agree with you about sticking with the native cm11 kernel, but I've had such good battery life with the dkp kernel's freelunch CPU governor and its smooth undervolting that I've lost my resolve to stick with the nightly kernel, so I was experimenting... FWIW, I'm back to stock or dkp only (for the time being).

Every time I did interrupt the boot process to get into recovery, a remnant of the cmupdater script would kick in and start applying the update, which would end with another useless attempt to reboot to android... It was truly in a messed up "loop". Do you know of a way to interrupt that cmupdater script that I didn't try?
[Verizon Samsung Galaxy S III] Hybridnoob:
The times I had 3rd party kernel related bootloops, I hadn't used CM Updater. Maybe only use CM Updater when using the stock kernel? Sorry that happened to you...
[Verizon Samsung Galaxy S III] Reznor7:
For what it's worth, if anything, I only experience recording problems with 1080p. Anything lower works without a hitch, taking pics while recording, switching between camera/vjdeo/etc.
[Verizon Samsung Galaxy S III] k.electron:
hi,

is there any news about m4 release for d2vzw. it seems after the broken unification fiasco they are waiting on that. in the meantime would there be a d2vzw only build?
[Verizon Samsung Galaxy S III] mastamoon:
Our maintainer is on vacation so nothing till he gets back.
[Verizon Samsung Galaxy S III] Hybridnoob:
"As a team, we leave it to the maintainers to opt-in to releases. If for any reason your maintainer does not flag a device as ready for release – be it for technical reasons, lack of time, or anything else – we will not issue a release for that device.

For some examples, I’ll point you to the d2lte, jflte and hlte devices. These are the unified builds weannounced last month. The maintainers decided that the unified devices were not ready to be issued outside of the nightly release stream and so no builds for these devices were generated."

http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items.
[Verizon Samsung Galaxy S III] joedajoester:
So this means that the new nightly's do have the new features that the m4 has since the nightly's are newer than the m4?
[Verizon Samsung Galaxy S III] Hybridnoob:
Absolutely. M4 on my N7 is missing things that were merged 4 or so days prior.

The M releases are just a different, but supposedly more stable and tested track. Definitely behind the nightlies in the latest features, if that's what you're looking for.
[Verizon Samsung Galaxy S III] Binge:
I'm helping a coworker with the S3, and put this ROM on it. Should I install a TW ROM for him, since he consistently gets the "Camera not connected" error? I figured CM would be a good low maintenance ROM for him, since I only see him once every week or so. But he wants the camera to work, and didn't want a stock ROM. Other than the camera part, he absolutely loves it. I'm torn on what to do about it.
[Verizon Samsung Galaxy S III] :
Send me logs so I can fix the camera is what you should do.

---------- Post added at 09:34 PM ---------- Previous post was at 09:29 PM ----------

Liquid has 1080p turned off. We did at one point too but I was hoping it was fixed. Can you grab a log next time this happens?
[Verizon Samsung Galaxy S III] k.electron:
got it. thanks. i read that post but was just wondering if our (dear) maintainer was going to release individual builds for m4 (i prefer a little more stability over bleeding edge). who is our maintainer if i may ask (so i can follow)?
[Verizon Samsung Galaxy S III] bmeek:
Texting and mms works fine for me on the 3/15 build. Sorry I can't be more helpful on your negative error code...
[Verizon Samsung Galaxy S III] RedRumy3:
Well I just installed textra sms and I can send gif and see them from friend as well now. He's also using it. Don't know why hangout wasn't working. But it's fine cause this is working good now.