yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] pie944:
Agreed on the Advice. It was set to NV. I set it to RUIM/SIM, no change. Do you need to reboot?

I'm using CWM.

Thanks for the help.

---------- Post added at 03:58 AM ---------- Previous post was at 03:55 AM ----------

Okay. Voice is back. Thank you!

One other question, if I flash the SlimRom again, will the data return? Voice stay?
[Verizon Samsung Galaxy S III] Rixanu:
I know I'm not exactly promoting reading the first few posts with my lengthy help replies, but Deevious is right, guys. Don't blindly flash without reading up on potential issues first. Not everyone is willing to answer your questions that have been asked god knows how many times before. It clutters the thread up something fierce.

---------- Post added at 10:05 PM ---------- Previous post was at 09:59 PM ----------

So, you still have no data? Before anything, I'd try toggling airplane mode on and off, see if that helps. Other than, that. I don't know what to say. I doubt that flashing back to Slim will fix anything, but you're welcome to try. The only method of fixing voice/data in this thread that seems to consistently work for everyone is flashing back to TW and doing the re-provisioning.
[Verizon Samsung Galaxy S III] pie944:
Yeah, no data. Thanks for the help.
[Verizon Samsung Galaxy S III] Chris123NT:
Tried the latest 12/21 unofficial (mastamoon's build)

Gallery will not play video, it is all scrambled on the screen and colors in the video thumbnails are way off.

And the CM team needs to support network extenders since the JB radios support recognizing it seperately from verizon wireless. CM thinks the phone is roaming when in range of the network extender.

NFC however DID work, which is a very nice change.

Oh yeah and the mic volume when recording is utterly atrocious, I would go as far to say it's worse than CM10
[Verizon Samsung Galaxy S III] pie944:
Instead of going back with ODIN, etc, do you think the update will just be a straight forward flash and data will be fixed? Or is this the only solution for a long time coming?
[Verizon Samsung Galaxy S III] juancaperez2000:
some help please, i just want to know how i can fix the activation screen after reboot thanks in advance
[Verizon Samsung Galaxy S III] iofthestorm:
It would be nice if someone could clean up all the posts about data. I was going to read the thread but seems like there's not much useful here for someone who is already on 10.1 with data working. Glad to know that the vibrate on all notifications is a bug though.

---------- Post added at 02:54 AM ---------- Previous post was at 02:42 AM ----------

If you don't mind my asking, who decides to merge it? Who is our maintainer anyway? I thought it was supposed to be cvpcs but I haven't seen anything from him since we got past kexec, so are you our maintainer now? You seem to do quite a lot for d2vzw.
[Verizon Samsung Galaxy S III] Restola:
Might be some issues specific to your installation phone. I'm also on masta's 12/21, videos play fine in gallery. Also I did a side by side with TW vc CM10 vs CM10.1 audio recording. 10 and 10.1 are identical except 10.1 records in stereo. So it's still soft, but its the same as 10.
[Verizon Samsung Galaxy S III] invisiblek:
^this

Someone with privs to merge to framework has to do it, most likely Ricardo or Steve

Officially cvpcs is still our maintainer, its obvious he has a real life now though... =)
[Verizon Samsung Galaxy S III] pie944:
If you have the data issue from flashing the official nightly, can you just flash back to TW using ODIN, enter *2767*3855#, then install ROM Manager, Clockworkmod, and flash your choice of ROM? As opposed to ODIN JellyBean after entering *2767*3855#, as described in post #2

I can survive on WiFi for a few days, so I'm just not sure if I should do this method versus waiting it out.
[Verizon Samsung Galaxy S III] Chris123NT:
Either that or because I installed the experimental KT747 kernel like an idiot, I realized there was a display related commit in the kernel in 12/21 that probably fixed the issue with video playback.
[Verizon Samsung Galaxy S III] peaceofpi:
Been like this for 10min. Running mastamoon 12/21. Any suggestions
[Verizon Samsung Galaxy S III] Zacharybinx34:
Is today's build working with data
[Verizon Samsung Galaxy S III] peaceofpi:
The CM one is not. Flashed it this AM and nothing. I'm running mastamoon 12/21.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Yikes, why isn't it fixed yet.'....?
[Verizon Samsung Galaxy S III] peaceofpi:
The God's are smiting us.
[Verizon Samsung Galaxy S III] odub303:
Build it yourself and cherry pick the relevant commits instead of whining.

Sent from my Verizon SGS3
[Verizon Samsung Galaxy S III] peaceofpi:
Well said.

Or you could spend 45 sec and read about all the unofficial builds that are working great. I don't know like mastamoons 12/18, 12/19, 12/20, 12/21

And to those that care. NFC and wallet are working on all of his builds.

Still can't seem to lock GPS tho :-\
[Verizon Samsung Galaxy S III] Zacharybinx34:
I am running unofficial...

Stop being fanboy trolls plz
[Verizon Samsung Galaxy S III] Chris123NT:
Because the CM devs haven't approved the RIL commit yet.
[Verizon Samsung Galaxy S III] bajasur:
Just checking back in.

Has anyone found a fix for the GLOBAL MODE issue that this Rom causes? Donation to follow got whoever can help me fix this issue

Thanks
[Verizon Samsung Galaxy S III] Chris123NT:
FYI Invisiblek has a 12/22 unofficial up. Here's the link:

http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20121222-UNOFFICIAL-d2vzw.zip

Edit: Still has the flickering issue. Once this and a couple other things are properly fixed I think this ROM will be usable day to day.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Does it fix wireless tethering?
[Verizon Samsung Galaxy S III] CrucialBT:
To stop the flickering just disable HW overlay in developer options for now. Just note it doesn't stick after reboot.

Only other real problem of note with the unofficial builds are I can't seem to use the "recent apps" function. It comes up for a split second then all I see is a black screen.
[Verizon Samsung Galaxy S III] Chris123NT:
Didn't try wireless tethering, nandroided back to my TW ROM until next build, hoping screen flickering is fixed soon.
[Verizon Samsung Galaxy S III] prophetjinn:
I had to hold the button down (if you're not using the home button) if held down the recent apps stays open... No idea how this is even remotely useful but in case you needed it, there you are.
[Verizon Samsung Galaxy S III] SymbioticGenius:
So far so good on Mastamoons build. Does anyone know if CM 10.1 supports 64 GB SD cards?

Thanks for the great work guys!
[Verizon Samsung Galaxy S III] Restola:
Nope. Tethering will activate but devices are unable to connect to it. (invisiblek 12/22)
[Verizon Samsung Galaxy S III] will.bates94:
Yes it does. I have one and it works perfect.

---------- Post added at 06:51 PM ---------- Previous post was at 06:36 PM ----------

Did masta push out a new unofficial for 12/22?
[Verizon Samsung Galaxy S III] mastamoon:
No build from me today, nothing really merged of significance, but download invisiblek or aerovan's build if you want a newer build. Both are tits!
[Verizon Samsung Galaxy S III] ka1z0ku:
Running Mastamoons 12/21 and Imoseyons LeanKernel v2 for 4.2, a little tough on battery life (I'm using the 1.9ghz OC) but great performance so far. Pretty stable, though my biggest gripe is H/W decoding for video has gone a bit wonky. Using S/W decoding works just fine, though.
[Verizon Samsung Galaxy S III] mastamoon:
Actually looks like the next build will stop the flicker w/o using the the work around.

Just don't know who will have it available. I believe invisiblek has his on auto build so keep an eye on his page.
[Verizon Samsung Galaxy S III] Hippoman13:
Is it possible to add HDR to the Camera? I hope this is possible and the S3 hardware is more than capable.
[Verizon Samsung Galaxy S III] will.bates94:
Thanks masta! Is his build in this thread or where can I get at it?
[Verizon Samsung Galaxy S III] Restola:
Post #2

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] bose301s:
Ok, so for those that have gotten their 64 and 32 gig cards to work, what did you do? I have it formatted in exFAT, have done it many many times on the PC and the second it see's CM it get's corrupted. Put it back in the PC and it needs to be formatted again. would really love to get this working, lol.
[Verizon Samsung Galaxy S III] will.bates94:
I didn't have to do anything man. Did u do a full clean install?
[Verizon Samsung Galaxy S III] bose301s:
Yes, many times. The order I did everything was root and unlock and get custom recovery. The thing is TWRP or CWM don't seem to recognize the card but I can get it working fine in TW ROMs, just really have no clue what the problem is.
[Verizon Samsung Galaxy S III] Chris123NT:
I guess I should as this here, but is there any progress on microphone VOLUME? Far as I can tell from searching this has been a problem since the 8/24 build of CM10. I guess I'm a little curious as to how this hasn't been fixed yet. I know 10.1 is finally recording in stereo, now the volume needs to be boosted.
[Verizon Samsung Galaxy S III] CrucialBT:
Well look at that. Thanks for pointing that out!
[Verizon Samsung Galaxy S III] Div033:
It's on qualcomm's end I think. We may not ever see a fix unless they do it first.
[Verizon Samsung Galaxy S III] CrucialBT:
I thought android couldn't read exFat? I have my 32 formatted for Fat32. If it reads exFat I'll change over to that so I can put 4GB+ files on my SD Card finally.
[Verizon Samsung Galaxy S III] Chris123NT:
Well damn, that kinda stinks. I wonder what changed after 8/22 that borked it.
[Verizon Samsung Galaxy S III] bose301s:
It supports exFAT.
[Verizon Samsung Galaxy S III] Deevious88:
Touchwiz supports exFAT, CM does not. You have to use FAT32 if you're going to use CM (unless something has changed in the past few weeks).
[Verizon Samsung Galaxy S III] bose301s:
NVM, found a program to formt it.
[Verizon Samsung Galaxy S III] Deevious88:
EaseUS Partition Master should work, although it's been a while and I can't remember exactly what program I used.
[Verizon Samsung Galaxy S III] joker713:
Having a storage space issue. Saying I only have 3 mb available on internal storage,,, Can't for the life of me figure out why. On masta's 12-19 build

Any tips? Is there a way to trick the phone into thinking my 32gb card if the internal storage and writing system and all that on there?
[Verizon Samsung Galaxy S III] cvo515:
Anyone find a good fix to the horribly low in call volume? Volume+ or DSP didn't seem to help nearly enough
[Verizon Samsung Galaxy S III] PerCompLLC:
Give this a try, it "may" help: Settings > Advanced > Sound > Extra gain in voice calls
[Verizon Samsung Galaxy S III] Stupifier:
You could use link2sd
[Verizon Samsung Galaxy S III] cvo515:
Yeah...I had that checked too. It actually made Me go to diff ROM its so bad. It'll be fixed eventually.
[Verizon Samsung Galaxy S III] Div033:
My issue with call volume was that I could not adjust the volume - it was stuck at the highest setting. Perhaps yours was stuck at the lowest setting? Just a guess.
[Verizon Samsung Galaxy S III] cvo515:
I'll give her another shot at some point in near future
[Verizon Samsung Galaxy S III] softwarestealer0:
So been loving 4.2. Quick question. Is it possible to turn off the widget areas on the lock screen?
[Verizon Samsung Galaxy S III] Div033:
Not saying there was anything you could do about it. I couldn't fix mine, soooo I guess we'll have to wait for a fix from the people who know how to do things!
[Verizon Samsung Galaxy S III] icon123:
I hear ya. Bring the old lock screen back.
[Verizon Samsung Galaxy S III] dpaine88:
+1
[Verizon Samsung Galaxy S III] Zacharybinx34:
+1

---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------

Low call commune is terribly low.

Also, speaker phone is broken, too much feedback
[Verizon Samsung Galaxy S III] jwoytk01:
For my own curiosity... why is data working on the unofficial nightlies but not on the official ones? I'm not criticizing. I'm just curious.
[Verizon Samsung Galaxy S III] wctaylor79:
The ones making the unofficial build are cherry picking the ril commits for data. They are still pending approval for the official..
[Verizon Samsung Galaxy S III] satadru:
FYI the 12/23 invisiblek build is up. The flickering is Not Gone. (It eventually cropped up.)
[Verizon Samsung Galaxy S III] Chris123NT:
I just tried the 12/23 from him and I still had flickering, but it didn't start until after a few minutes of using it.
[Verizon Samsung Galaxy S III] fillyfloater:
Where's the link for the new unofficial 12/23?
[Verizon Samsung Galaxy S III] icon123:
Did you dirty flash? I did and the flickering is worse than before.

---------- Post added at 12:41 PM ---------- Previous post was at 12:39 PM ----------

http://t.co/mpTXtZ3W
[Verizon Samsung Galaxy S III] PerCompLLC:
Delete
[Verizon Samsung Galaxy S III] icon123:
Deleted
[Verizon Samsung Galaxy S III] fillyfloater:
Thanks, found it on the early pages.
[Verizon Samsung Galaxy S III] icon123:
Actually it only seems bad when I'm using the keyboard. Otherwise I don't seem to be getting any flickering.
[Verizon Samsung Galaxy S III] Chris123NT:
Nope, clean flash.
[Verizon Samsung Galaxy S III] wctaylor79:
Tether still down on 12/23 build?
[Verizon Samsung Galaxy S III] dpaine88:
Any having MMS not showing notification sometimes and new messages just showing as read? Doesn't make notification sound either
[Verizon Samsung Galaxy S III] Stupifier:
I don't have any flicker issues....been on mastamoon's 12/19 build ever since it was released. Don't really see much point in flashing any of the later unofficial nightlies since I haven't had any issue with this one.
[Verizon Samsung Galaxy S III] Chris123NT:
The commit to fix the flicker went into the CM10.1 git last night but it's not in this build, checked build.prop and it's not using the debug switch to limit the MDP composition layers to 3 like the fix states.
[Verizon Samsung Galaxy S III] icon123:
Thanks. I saw that tweet last night and just assumed it was in this update.
[Verizon Samsung Galaxy S III] Chris123NT:
Compiling a build from source is way above my skill set but if someone could crank out a build with all the current commits plus the RIL fix I think we'll have a pretty solid build to run.
[Verizon Samsung Galaxy S III] jthomas84:
I odined the root 66 tar and it passed after 12 minutes. Now my phone is in what seems to be a boot loop. It is on the boot screen for 16 minutes now.... should I try odin again?

Edit: I figured it out. After odin I had to get into recovery to wipe data/factory reset. Am good now.
[Verizon Samsung Galaxy S III] EGill42:
do a factory reset in the recovery, then it should boot up with no problems.
[Verizon Samsung Galaxy S III] aooga:
Yup. The flickering was my only problem with cm10. Another small problem i've noticed is that when you leave the phone to charge overnight and use it the next day, it's a bit slower (not as smooth with the scrolling). If I flash the rom again, its buttery smooth again. Thats a really weird problem i've been having, but its nothing that stops me from using the rom.

EDIT: Anyone else having issues with mastamoon's 12/22 build and calls? Whenever I end a call the phone app fc's and goes into roaming mode.
[Verizon Samsung Galaxy S III] xenokira:
I had a similar issue with SDM earlier build. Fixing permissions seemed to solve the Phone app FC'ing. For the roaming issue, you sure you're set to RUIM/SIM in your mobile settings?
[Verizon Samsung Galaxy S III] Zacharybinx34:
NFC is broken
[Verizon Samsung Galaxy S III] Chris123NT:
it works fine for me, you coming from an ICS TW ROM or a JB TW ROM?
[Verizon Samsung Galaxy S III] Zacharybinx34:
I have been on cm from the start.
[Verizon Samsung Galaxy S III] iofthestorm:
For me when I flashed 10.1 NFC was broken and I had to flash a JB TW ROM and then 10.1 to get it working again. I think invisiblek or aeroevan said that it's because they're using the JB libraries now but forgot to include the right file in the ROM or something like that. Btw a smallish JB TW rom is clean rom lite. I think it might be the smallest but not sure. I dunno how TW ROM users live with those huge ROM downloads lol. So much bloat.
[Verizon Samsung Galaxy S III] PerCompLLC:
Broken on which build? In other words, which specific build are you running?

I'm on 12/23 unofficial (invisiblek) and nfc is indeed working (at least it is for me). It was also working on the last two unofficials from mastamoon.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Newest unofficial of invis

It says that it works but saves it to some folder that doesn't exist.
[Verizon Samsung Galaxy S III] pyrostic:
Flash this on any cm10.1 build with broken NFC and it will fix it.

http://invisiblek.chickenkiller.com/CM10.1-d2vzw-nfc-crapHax.zip

---------- Post added at 06:31 PM ---------- Previous post was at 06:28 PM ----------

The folder does exist or you would get an unsuccessful download. Try installing Goo Manager from the play store, hitting menu, then install OpenRecoveryScript.

This will install TWRP 2.3.3.0 which will fix the issues of not seeing folders associated with the multiple users portion of 4.2 in which it nests user data per user under a numbered folder.
[Verizon Samsung Galaxy S III] invisiblek:
Ril just got merged =)
[Verizon Samsung Galaxy S III] Restola:
Camcorder stereo recording and speakerphone echo got merged too. Could be a good day tomorrow for the official!

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] bobby janow:
From your mouth....
[Verizon Samsung Galaxy S III] Chris123NT:
Will there be an official tomorrow or will you be cranking out another unofficial kang that includes these fixes? I'm really optimistic about the mic fixes.
[Verizon Samsung Galaxy S III] invisiblek:
Both. I'm not sure these audio fixes are going to do everything we're expecting. Audio is still a work in progress right now. It's definitely being worked on though.
[Verizon Samsung Galaxy S III] Chris123NT:
For now as long as it fixes echo while on speaker I'll be happy. If that gets fixed and the flickering gets fixed this build should be money for me.
[Verizon Samsung Galaxy S III] cbrehob:
Roaming

Was on an OFFICIAL 18 CM10.1, everything working great except the screen flashing. Then wiped and tried out an UNOFFICIAL 23, data was all roaming. I still have IMEI and phone #, but stuck on roaming. Go to grab my backup, and it cant be found cause of the \0\folder bs. I clean install the official 18 again, still roaming.

Now ODIN back to start, gonna make sure I get my data back. Just a heads up, that \0\ folder creation each time you install CM 10.1 can be a *****, make sure you get the latest CMW, I had an older version that couldnt find the backups.

EDIT: Went back to Stock, still stuck with roaming.. F ME.
[Verizon Samsung Galaxy S III] PerCompLLC:
Data has never worked on the official cm10.1 nightlies for the d2vzw...
[Verizon Samsung Galaxy S III] cbrehob:
Funny cause it did-

http://get.cm/get/jenkins/15528/cm-10.1-20121218-NIGHTLY-d2vzw.zip

No worries, I recovering roaming by ODIN + re-provision.

Back to CM 10.1..
[Verizon Samsung Galaxy S III] Chris123NT:
No idea how you got data working on the official 12/18, the RIL commit that gets data working was just merged today, so it will be in tomorrow's build.
[Verizon Samsung Galaxy S III] PerCompLLC:
^^ This ^^
[Verizon Samsung Galaxy S III] ricecake2000:
I flashed one of the unoffical builds amd now I am roaming. I restored a back up of another rom and still roaming. I odined back to the ota and I'm still roaming. Any ideas?
[Verizon Samsung Galaxy S III] Chris123NT:
Odin back to an ICS TW ROM (root66.tar will work best for this) and dial *2767*3855# in the phone app. Back up anything you have on the internal storage as this will wipe it and re-provision your phone. Your external SD card will be fine.
[Verizon Samsung Galaxy S III] ricecake2000:
Thank you for the speedy response! Im now in search of that file! Ha
[Verizon Samsung Galaxy S III] Chris123NT:
Here you go:

http://xdaforums.com/showthread.php?t=1762204
[Verizon Samsung Galaxy S III] ricecake2000:
So I just flash that file in Odin? It says extract the tar file yet im downloaidng stock.vzw_root66.tar already?
[Verizon Samsung Galaxy S III] Chris123NT:
No don't extract it, just flash it by selecting it via the PDA section in ODIN, with the device in download mode of course.
[Verizon Samsung Galaxy S III] ricecake2000:
Ha that was going to be my first thought, just wanted to double check. Sorry for the minor hijacking of this thread. Thanks again for all the help!

---------- Post added at 05:46 AM ---------- Previous post was at 05:13 AM ----------

Unfortunately I am now stuck at the boot screen and it has been there for about 10 minutes.
[Verizon Samsung Galaxy S III] msburr87:
Do we know if the data commit in tomorrows release is the one in all unofficial and liquid builds? Or is it (hopefully) something different and more stable?
[Verizon Samsung Galaxy S III] Chris123NT:
boot into recovery (volume up + home + power) and wipe data/factory reset, then it will boot.
[Verizon Samsung Galaxy S III] ricecake2000:
Im stil in roaming mode, should I take the OTA and see if that fixes it?
[Verizon Samsung Galaxy S III] EGill42:
...Also lost voice/texting today. I just restored back to a stock rooted rom. If I re-install CM 10.1, would I likely lose voice/texting again?
[Verizon Samsung Galaxy S III] Chris123NT:
Did you dial that number I gave you in the phone app? That should fix it as long as your IMEI is still intact.
[Verizon Samsung Galaxy S III] ricecake2000:
Double Derp! Forgot how to get into recovery mode and completely forgot that number! All is good! Thanks!

This is like the happiest moment of my life haha
[Verizon Samsung Galaxy S III] aquaurchin99:
What should I do to fix the sdcard0 stuff? I reverted back to cm10 for the moment. Gonna wait a few days till the nightly's become more stable.
[Verizon Samsung Galaxy S III] vaffanculo403:
Is the data back in the 12/24 nightly?
[Verizon Samsung Galaxy S III] danstar:
Flashed the official 12/24 nightly. Once again had to bypass the activation screen and had to go to settings and change cdma subscription to ruim/sim. I had to reboot because my phone number was screwed up. Once I rebooted numbers were correct and I was able to get both 4g and 3g(being that I am in my basement, it switches back and forth.) I had to reflash, not because of an issue with the rom itself, but because I also flashed an inverted gapps program for 4.2.1 and had black on black text when trying to compose an email in gmail. Did another clean wipe and reflashed the rom. Once again had to bypass activation screen and fix the cdma subscription. And once again had to reboot since phone number was screwed up. Once up and running, I was able to send an email between my two gmail accounts while on 3g with wifi off. I have noticed that the signal strength in the db readings is not as strong as it was in the unofficial nightlies and some other 4.2.1 roms. So, I believe that even after all of this, that data is working to the best of my knowledge.
[Verizon Samsung Galaxy S III] OneNutShort:
I just dirty flashed the official 12/24 nightly over InvisibleK's unofficial 12/23 nightly, and can confirm that data works. Bear in mind that since this was a dirty flash over an already working rom it is possible that a clean flash of the official nightly might require the same RUIM/SIM solution as has been mentioned in the OP.

(Edit) Danstar, totally beat me to the punch. Forgive the redundant answer.
[Verizon Samsung Galaxy S III] Stupifier:
Even after hearing that.....I'm still hesitant to flash the official 12/24. I'm holding out
[Verizon Samsung Galaxy S III] danstar:
Yeah I am thinking it is the same problem that arose with the slim rom. A clean flash produced the ruim/sim problem every time, but a dirty flash didn't.