yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
Yeah its a bit whacky.. If you haven't lost your imei through flashing over and over likely your nvdata was fine. But if you have had your phone from release and never did an nvbackup you were just lucky you haven't lost your info. We don't know the cut off when the factory fixed it so it's hard to pin down and just tell people to do/not do.

Since NV repair is possible it's probably better to just do an nvrestore when you run into problems and see what you get. Either it's fixed or still broke, albeit a little more so than before but again, repairable.

Really you could back it up manually first then do an nvrestore and if it wipes your info, just restore the backup you made manually.

You may have to Odin back to stock shipping firmware and do a reprovision.. :)
[Verizon Samsung Galaxy S III] 250 or Point 65:
Yeah, this is such a weird problem. I have read a lot of threads from the time i bought my DroidX and never seen anything like this. Now that I'm on synergy, I can make calls, but there's no way to achieve LTE because there's no LTE option in that rom

Does reprovisioning mean completely wiping all my data before they do it?
[Verizon Samsung Galaxy S III] esjames:
I want to thank you for your advice, switching my CDMA to "Home only" made my connection very stable. :good::good::good:

I didn't think about it switching to the roaming tower and vice versa.
[Verizon Samsung Galaxy S III] 250 or Point 65:
Hey guys. Thank you all for all your input. Turns out that Verizon support said that *228 fried my sim. Went in and got a new one for free, everything works!

Now if I can just get my contacts to sync, i'll be good to go!
[Verizon Samsung Galaxy S III] darkknight1812:
I am glad it is working. I am trying the latest nightly and it is more stable than it has been but it will switch back and forth for me once in awhile. I still think the main issue is the extender is considered roaming which gives it a lower priority when it really should be given a high priority. I wish I knew how to change it in the code so we can find out.
[Verizon Samsung Galaxy S III] bmeek:
I made the *228 mistake with this gs3 once. deactivating and reactivating the device via the vzw web site got me back to reliable 4G LTE operation with the original sim. Did you try that? Swapping out the moto on the line like you mentioned earlier?
[Verizon Samsung Galaxy S III] cstone1991:
"Fried" isn't really the right word here. *228 cannot actually fry your SIM. It CAN cause your phone to try to download a 3G PRL which will fail causing you to have a corrupted PRL. The same thing happened to me when I tried it hoping to improve service at my parents house. The was to remove my SIM for about 2 minutes (not sure that this was necessary, but tech support told me to do it) then boot into safe mode and toggle to CDMA only and change roaming to home only, enable airplane mode, disable airplane mode, switch settings back to the normal ones and like magic I had LTE again. It took 2 tries for this to work on my phone. It has been good since then which was about 6 months ago.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] open1your1eyes0:
Horray! 4.4.3 in latest nightly. :)
[Verizon Samsung Galaxy S III] 250 or Point 65:
I did not get the chance to try swapping phones on that number because I was visiting my parents at the time and my DX was at home. I'm glad to know if I ever need to fix my PRL in the future, that may be a step to try since it's worked for someone else.

Also, I understand that calling *228 does not actually remove my SIM, throw it in a frying pan and fry it. Thought, as you said, it can scramble up the information on the phone and SIM, to become unusable.

But then again, I do make my scrambled eggs in a frying pan, so.....
[Verizon Samsung Galaxy S III] Skyrocketing:
Anyone have experience with ART on the nightlies?
[Verizon Samsung Galaxy S III] cstone1991:
It doesn't actually do anything to the SIM. It corrupts it on the phone side which prevents the phone from using the SIM properly. At least that's how it was explained to me. Makes sense, a 3G phone that you would actually use *228 on doesn't use a SIM card so why would there be any instructions to write to the SIM in the PRL update?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] wctaylor79:
Just a random side note to others.. I dirty flashed the latest with 4.4.3 and got constant error with android.process.acore . Guessing it tied back to the new dialer/contacts.. maybe not.. anyways.. clean flashed it and all is well. Rocking 4.4.3.. :)
[Verizon Samsung Galaxy S III] Gareee:
It looks like OK Google and messaging are not working properly yet on this. You gat get OK Google to pick up on desktop, it recognises to text someone and recognises the contact, but when you say send, sending the message fails.

:(
[Verizon Samsung Galaxy S III] Stealth111:
That is all I use, and it is running perfect as usual. Only issue I still have with this rom is that I still have the dreaded "No APN specified for this device" come up when sending/receiving MMS. Standard texts are fine, but and any other gets me the error, AND ONLY when I am connected to a Network Extender (which is 70% of the time I use my device!). Going to clean flash latest build for good measure...
[Verizon Samsung Galaxy S III] Gareee:
I'm using the nova launcher, and am seeing issues with the nightly and the phone dialer app crashing.

Seems I can get calls fine, but not place them. :(

I also noticed the phone rolled back to the stock theme after a few minutes off, and had to restore my theme.

I also checked with faster GPS, because GPS lock was dog slow. I switched to the proper satellite region, and I had lock in a second!

I'll try the next nightly and see if that resolves the dial issue.
[Verizon Samsung Galaxy S III] bmeek:
Although it's not "officially supported", I've found that ART provides me with a somewhat noticeable performance boost and better battery life. On the downside, it takes a long time for 1st boot after a nightly update or after clearing caches...
[Verizon Samsung Galaxy S III] rkerrddd:
How's the WiFi and 4g signal on this rom

LIVE FREE OR DIE
[Verizon Samsung Galaxy S III] darkknight1812:
I also have the same issue along with it switching back and forth from the tower to the extender. Does your network extender show up as roaming?
[Verizon Samsung Galaxy S III] thefuzz4:
So far I an really enjoying the nightly from 06/06 no random reboot and good battery life. I am using art so I keep getting a Google play sound search has died but I got that several ROMs ago anyhow.

---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------

Oh yeah and the new dialer is also nice
[Verizon Samsung Galaxy S III] bmeek:
You seem to be connecting use of ART with a Google play sound search issue.

No such problems here while running with ART.
[Verizon Samsung Galaxy S III] Jaegermeiste:
Same experience. Except for the annoying rebuild after every flash, ART seems to work very well for me.
[Verizon Samsung Galaxy S III] darklavalizard:
Anyone else get worse than normal reception on tonight's M7 release? Normally in my house I would get 1-2 bars, and now it shows 0 bars and -110 db on my phone status (used to be -96 or -103), yet I can still slowly browse the web. Did the update through the CM updater.
[Verizon Samsung Galaxy S III] cheekoo:
can you help me pls move to art? i tried the config in developer mode, but the phone reboots and still the config says dalvik. is there anything else i need to do?

nvm, i think, its because i have exposed...
[Verizon Samsung Galaxy S III] esjames:
You are correct sir! On a fresh install I can select art runtime, but if I install xposed afterwards, runtime will revert back to dalvik.

I only tested this on the M7 build.
[Verizon Samsung Galaxy S III] tedkord:
I was getting the sound search f/c error constantly on Carbon when I was using it. I used a root file explorer (root explorer in my case), deleted the GoogleEars.apk from system/app, rebooted and installed sound search from the play store. It worked every time.
[Verizon Samsung Galaxy S III] Jaegermeiste:
This has everything to do with Xposed and nothing to do with CM or any other AOSP rom. For the time being at least, ART is completely incompatible with Xposed - you must choose.
[Verizon Samsung Galaxy S III] ecooce:
A couple settings are not sticking after reboot, power save mode, and button backlight "off". Normally I change this in a .kl file, but know that is bypassed since the option is built in, but the setting will not stick...
[Verizon Samsung Galaxy S III] NedDasty:
Sorry if this has been mentioned (I searched and couldn't find anything).

I can't see my external SD card. Running the 6/11 nightly. Haven't seen it in a while. Can't access it from computer, can't access it via solid explorer. Anybody know if this is a problem for everyone, or if there's a fix?
[Verizon Samsung Galaxy S III] ryanstfl:
Me too. I noticed the button backlight. Also no custom ringtones will stick...
[Verizon Samsung Galaxy S III] merdely:
I noticed this as well. So far it seems to only affect the Power Save Mode for me.

---------- Post added at 03:40 PM ---------- Previous post was at 03:40 PM ----------

Maybe your SD card is bad. I can get to mine with no problem.
[Verizon Samsung Galaxy S III] rhcreed:
calendar events not sending notifications

Anyone else have an issue where recurring, all day calendar events (like birthdays) don't show any notifications?

Used to but then they stopped (can't say when). Not sure it's a rom thing, but wanted to ask.

yes, app info does show that notifications are allowed, and other appointments and stuff do throw up notifications..

thx
[Verizon Samsung Galaxy S III] swolfe2:
I'm getting terrible download speeds on the snapshot. Full bars of 4G, and .6mb makes me a sad panda.
[Verizon Samsung Galaxy S III] darklavalizard:
Yea there is something super jacked up with the M7 release, I'm flashing back to M6. Reception and battery life are significantly worse than on the last snapshot.
[Verizon Samsung Galaxy S III] ecooce:
Just to let you know...

Just a couple more bugs, themes provider crashes (I don't use themes), and on the 6/12 nightly "Display and lights" in settings is FCing now. Someone confirm please, because I have modded .kl files, Im wondering if its just me, because I dont have the 6/12 "keylayout" folder with stock files...
[Verizon Samsung Galaxy S III] Hybridnoob:
Display and Lights is FCing here too on 6/12 nightly.
[Verizon Samsung Galaxy S III] tv31284:
I get force closes as well too. I'm not sure how long the options been available to s3 users but I just noticed we can now turn on on screen navigation buttons without modifying anything. I never used it on my s3 but I'm trying it now and its kind of nice.
[Verizon Samsung Galaxy S III] esjames:
Has anyone else been getting an error "Unfortunately, Sound search for Google Play has stopped."?
[Verizon Samsung Galaxy S III] MartyMacGyver:
I'm running cm-11-20140531-NIGHTLY-d2lte currently, which has a tendency to reboot itself after a few hours of active use (and the GPS is far more wonky than 10.1 ever was). I see the latest builds (including m7) are not looking good, so I wonder, what cm-11 release has been reported to be the most stable and reliable lately?

(I miss seeing the nightlies and such in ROM Manager... the star ratings and reviews were extremely helpful in picking a build to update to!)
[Verizon Samsung Galaxy S III] JMooney5115:
I've had MMS issues, sending and receiving, on the last 3 nighties. Am I the only one with this issue?

--

Mooney
[Verizon Samsung Galaxy S III] RussianMenace:
Did you get this fixed? I just flashed back to M6 (clean) and it's still hitting a max of 1.57Mbit....when before I was hitting 30+
[Verizon Samsung Galaxy S III] bmeek:
+1 here - I noticed the backlight issue and confirmed the issue persists with the today's 06/12 build, then I reverted to the 06/08 build and find no such issue. Things feel pretty solid with 06/08 (which predated some pretty extensive change log entries).
[Verizon Samsung Galaxy S III] MartyMacGyver:
Is the 6/8 M7 build effectively the same as the 6/8 *nightly* build? I've noticed complaints about M7 though hopefully they're not general problems...
[Verizon Samsung Galaxy S III] bmeek:
Sorry, I was referring to the 06/08 NIGHTLY build.

FWIW, I didn't see any issues with the M7, though I didn't run it for long.
[Verizon Samsung Galaxy S III] MartyMacGyver:
It's hard to tell what the difference is between the snapshot (M7) and the nightly for 6/8... assuming there's a difference at all. I can readily see the changelog for 6/8 online, but not M7. Hmm...

Edit: I went ahead and installed M7 because it seemed like a good idea... now I'm going to install the 6./8 nightly because it seems to be OK and it's apparently ahead of M7 per the CM blog
[Verizon Samsung Galaxy S III] swolfe2:
Nope. Nothing I tried worked. Ended up switching to the newest AOSPA 4.4, and have had much better results.
[Verizon Samsung Galaxy S III] ecooce:
I normally won't post bugs in here unless Im trying to confirm with or warn others. I only really say anything other wise when it spans a couple nightlies, but yeah I went back to 6/08 also, still has a couple bugs, but not really bad. I actually found a couple others, but I'll wait till this next nightly...
[Verizon Samsung Galaxy S III] thefuzz4:
Yes I was getting that as well. If you go back a couple a page or two someone posted how to fix that and I thanked them. You have to delete an apk off of your phone and then install it from Play.
[Verizon Samsung Galaxy S III] bmeek:
For one thing, the 06/08 nightly build is Android v4.4.3 whereas the M7 snapshot is 4.4.2.

---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------

As another mere user, I appreciate your posts. For the developers, i gather they only take bug reports against a snapshot.
[Verizon Samsung Galaxy S III] tv31284:
I don't think today's build is any good. I got system ui force closes on boot from a dirty install over the 6/12 build. Too bad, there are some cool new features they just merged.
[Verizon Samsung Galaxy S III] Hybridnoob:
Same here - I should have heeded your warning.

Looks like 6/13 was pulled. I guess that's the risk we run by being early adopters!
[Verizon Samsung Galaxy S III] tehloxely:
Damn there is an M7. I guess there is a wee bit of time for an actual release for the S3.
[Verizon Samsung Galaxy S III] chowner:
huh?

http://download.cyanogenmod.org/?device=d2lte&type=snapshot
[Verizon Samsung Galaxy S III] tehloxely:
I meant a stable.
[Verizon Samsung Galaxy S III] bmeek:
FYI, the issue persists in the June 14 build (edit: also 06/15; ). Since I'm having no issues with June 8 nightly, I've been reverting to it along with the June 2 dkp kernel.
[Verizon Samsung Galaxy S III] buschbarber:
Display and Lights crashes Settings

I am seeing this on 06/14. I did a Factory Wipe, reflashed, and flashed Gapps 06/06. Still same issue.
[Verizon Samsung Galaxy S III] Hybridnoob:
Are you able to open the "Display and lights" section within Settings without an immediate force close? I can on 6/7, but not using any of the latest nightlies. I'm curious if you can, considering you clean flashed.
[Verizon Samsung Galaxy S III] buschbarber:
Despite the clean Flash, Settings crashes as soon as I click on Display and Lights.
[Verizon Samsung Galaxy S III] bmeek:
This issue occurs on June 8 nightly as well, but Buttons --> Backlight settings stick after a reboot.
[Verizon Samsung Galaxy S III] buschbarber:
What do you mean by "stick"?

---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------

I am finding the response time of opening, using, and closing any app is very slow.
[Verizon Samsung Galaxy S III] bmeek:
With more recent builds, "Buttons-->Backlight--> Illuminate buttons (unchecked)" will not stay unchecked after a reboot. This was reported earlier in the thread and has been confirmed to remain an issue on cleanly-flashed current builds.
[Verizon Samsung Galaxy S III] timedroid:
Apparently thermald is broken again. This results in a rather dramatic slowdown (often capped to 384 mhz) when my phone gets a bit hot. Seems kind of odd no one else would notice that happening?

Is it even broken for everyone else? (That is, does running "pgrep thermal" from a terminal return anything for anyone?)
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm on 6/14 and that command returns a 1. I'm guessing that means it's working? CPUspy shows my phone is using a range of speeds.
[Verizon Samsung Galaxy S III] bmeek:
That might explain why my phone slowed to a crawl yesterday while using navigation and Pandora at the same time...

"pgrep thermal" returns nothing for me.
[Verizon Samsung Galaxy S III] buschbarber:
Today, Gmail will not sync. I have to use a web browser to view my email. Also, when eCID reads my text messages, the audio is choppy.
[Verizon Samsung Galaxy S III] SDQB17:
I have a question since I havent been around here recntly, are you guys running xposed with CM? I am running the 07 nightly (4.3) and am interested in running xposed also. Is this ok?, are there any modules you recommend, and when I update my nightlies, do I need to update xposed again or leave it? Really interested if it is worthwhile to have on a custom rom like CM. Thx!
[Verizon Samsung Galaxy S III] bmeek:
I've only been tempted to run xposed on TouchWiz for a mod that I wanted, but I've not seen a need with cm11. I'm curious about your motivation.

Also, I've heard that xposed won't run with ART, and I like ART.
[Verizon Samsung Galaxy S III] razz1:
It's ok to run xposed. I run it for the scrolling mod, but if you use xposed ART won't work for you. otherwise your fine.
[Verizon Samsung Galaxy S III] lou1210:
I'm having issues with camera all together. The minute I try to take a picture, my phone shuts off. I've found an app called "a better camera" that will do pictures and video and save to the SD card.
[Verizon Samsung Galaxy S III] bmeek:
I made the same mistake recently with *228 on 4.4 and lost LTE as you did.

I fixed it on the vzw web site by temporarily deactivating my d2vzw (swapping it with my old Fascinate), and reactivating it. Still using my original SIM.

If you don't have an old smartphone lying around, you could also get vzw to deactivate/reactivate by calling their tech support folks.
[Verizon Samsung Galaxy S III] RayMcGrath:
Very smart work-a-round! ?
[Verizon Samsung Galaxy S III] ericsdeadinside:
Going to try now crossing fingers
[Verizon Samsung Galaxy S III] Defragger51:
Apparently I was the only one have Battery issues with the 12/9 nightly, because no one commented on my previous post about it. Just wanted to report that dirty flashing the 12/10 nightly solved my battery issues. Now I have the kinda amazing battery life like I did on unofficial 4.4 roms. After flashing 12/10 and charging back to 100%, I have been on battery for 7 hours and have 71% left and have used the phone a lot more than yesterday. Hope this helps someone.
[Verizon Samsung Galaxy S III] eeraider:
I was having battery issues as well with the 12/9 nightly but I was assuming that my phone wasn't playing nicely with the kernel. It had been picky in the past. Trying the 12/10 load now. Thanks for sharing your experience.
[Verizon Samsung Galaxy S III] baldwinguy77:
Hey everyone! So, running the latest CM 11.0 nightly on my Verizon GS3, I haven't been able to get mobile data to work whatsoever. Phone calls and texts work fine, i.e. I have cell service, but no data (1X, 3G, 4G) is coming through. Admittedly, I'm a bit new to the GS3 rooting and ROMing scene. The phone is running the latest radios (VRBMF1), so I'm wondering if downgrading could somehow help with this issue. The only problem is I'm not quite sure which radios I would want to start with if it's possible that the radios are causing the problem. If not the radios, does anyone else have any idea of what it might be? Any help would be greatly appreciated, thanks so much in advance!

P.S. I tried tinkering with the mobile data settings to no avail. I also tried searching the thread, but didn't come up with anything. Also, it doesn't seem to be an issue with any nightly because I haven't seen anyone else report it, but I figured it'd be a good idea to quickly post about it. Thanks again!
[Verizon Samsung Galaxy S III] Stealth111:
Baldwinguy77, what does it say under the status screen? Does it say mobile network state connected or disconnected? Does it have an IP address, is it roaming/out of neighborhood?

Sent using Tapatalk
[Verizon Samsung Galaxy S III] baldwinguy77:
Thanks for the quick reply!

Mobile network state reads "Disconnected," there is no IP address available and the roaming status is "Not Roaming". I've also confirmed that the SIM is working in another VZW 4G LTE device, so I don't think that's the issue. I've debugged a similar issue while developing for the GNex by using the "hidden dialer menu" to switch through different network modes, but it didn't give me any luck with the GS3. I'm now back to all of the default network settings, so I'm up for trying any suggestions! :)
[Verizon Samsung Galaxy S III] Stealth111:
Network mode on sim mode and not NV? Set on automatic and not home? Network on global? You are not by chance using a Verizon network extender are you? Tried toggling airplane mode off and on? Turn on data roaming? Just going through the motions... wipe caches, reflash latest nightly..

Sent using Tapatalk
[Verizon Samsung Galaxy S III] baldwinguy77:
All of the settings were as you described them, and no network extender. I actually didn't have the network mode on global for any length of time, because I don't think that's what it was set as by default. I definitely switched to it though during testing, and it didn't seem to work. I had a few "bars" worth of service this whole time, but data just refused to connect.
[Verizon Samsung Galaxy S III] TokedUp:
Thanks for this!
[Verizon Samsung Galaxy S III] thelangosta:
I wouldn't switch radios. I think you have to be on MF1 for cm11. Try wiping caches and format system (don't wipe data) then reflashing the ROM and gapps. You might just have a bad download. Sometimes the ROM will flash but, still act weird.
[Verizon Samsung Galaxy S III] Defragger51:
Has anyone notice or is this just me again.I notice last night on the 12/10 build my blue tooth ear piece would not connect on its own, I had to force it to connect as if it had never been connected to the phone and after I disconnected it would not reconnect. I can say for sure than I never had this issue on the unofficial builds.
[Verizon Samsung Galaxy S III] StormFreak:
I am very impressed with these nightlies and am easily using them as my DD. My only real issue has been with the camera. I've had several times where it just freezes and crashes, or goes to a black screen and I have to reboot to fix the issue. Would flashing a 4.3 camera fix this, or does anyone know a workaround? I use my camera quite a bit, so I'd like it to be a bit more reliable. Other than that, I am more than happy!
[Verizon Samsung Galaxy S III] annoyingduck:
I get data issues all the time. Usually on a reboot or a dirty flash. I'll actually have no data at all, no IMEI. A few reboots fixes it...
[Verizon Samsung Galaxy S III] FroyoBaggins:
same here
[Verizon Samsung Galaxy S III] titanshadow:
I'm having the same issue.
[Verizon Samsung Galaxy S III] Prack:
Yup this started on 12/10 for me as well. I thought something was going on with my bluetooth headphones.
[Verizon Samsung Galaxy S III] julesism:
D'oh! yea it crashes when I try and post. Sorry for the confusion. I was excite to not see the double vision video symptom that plagued CM10.2.
[Verizon Samsung Galaxy S III] SDQB17:
Thanks for the replies. I just like experimenting with different things. I can't leave well enough alone...lol :) Obsessed with tinkering:silly:
[Verizon Samsung Galaxy S III] lakingslayer:
Are you using the Google experience launcher? If so try another launcher and see if it goes away.
[Verizon Samsung Galaxy S III] dmginc:
using Nova and I get the same thing.