yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] goldsmitht:
Any of you who are stuck in roaming, try this method. Worked great for me, and had done everything except Odin back to stock.

Also, the next time I flashed, it went back into roaming, and said, "waiting for activation" or something. At this point I did the four corner taps --- tap in each corner, clockwise, until it brings up main page, and profit! Back to normal.

Hope that helps, works for me.

:D
[Verizon Samsung Galaxy S III] bajasur:
Ok.

After clean install, stock ics *2767..yadda yadda, a soft brick and hellish reboot, I am STILL getting prompted to switch to global mode! Argh!

I give up, time for beer.

Good news is the roaming notification is not popping up yet... bad news is this global mode is... and I only have two beers!

Tonight is the end of the world right?
[Verizon Samsung Galaxy S III] M Diddy:
That was it. CDMA subscription was set to NV. Once I moved it to RUIM/SIM, I got my number and am up and running again.
[Verizon Samsung Galaxy S III] Chris123NT:
Interesting discovery, after going back to ICS and then re-flashing CM10.1 (12/20 unofficial) I have data UNTIL I install any Jelly Bean Modem, then it switches sub to NV on next boot and sticks in roaming, put an ICS modem back, set to RUIM/SIM, reboot, and data comes back.....This is weird.

BTW, this issue also occurs on CM10, flash CM10 after ICS and all is well, but if you flash a JB Modem, it goes to roaming and NV, and even switching to RUIM doesn't help until you flash back an ICS Modem.
[Verizon Samsung Galaxy S III] xCHPx:
I just flashed my synergy data/IMEI/NV backup and I got my 4g back...
[Verizon Samsung Galaxy S III] bose301s:
THANK YOU!!
[Verizon Samsung Galaxy S III] crazytalk151:
IT WORKED. I want to make sweet sweet love to you.
[Verizon Samsung Galaxy S III] peaceofpi:
Anyone get gps to lock on mastamoon 12/19? I was lost in a van in NYC for a bit due to this issue.
[Verizon Samsung Galaxy S III] c4v3man:
Yes, locks pretty quick. Compass seems accurate enough (not getting the bizarre 180* off issue I used to get on some JB kernels). Battery seems pretty decent... maybe 2-3% an hour with no screen usage.
[Verizon Samsung Galaxy S III] nscott69:
I've Odin'd twice have mobile data but no messaging or phone calls :(
[Verizon Samsung Galaxy S III] jager420:
Read it wrong... discard
[Verizon Samsung Galaxy S III] Stupifier:
I'm supremely happy with the 12/19 mastamoon build. I get fast GPS lock. Used it now for over a day and the battery life is awesome...coming from CM10 11/10 nightly where battery life was not good. Bluetooth audio also works great. NFC setting is on (haven't truly tested yet). I'm holding onto this build since it works for me until I see much more favorable feedback about these other builds.

I'm way too scared to flash any of this stuff with all these no data issues flying around
[Verizon Samsung Galaxy S III] Zacharybinx34:
Anyone know if today's has data working?
[Verizon Samsung Galaxy S III] Chris123NT:
I am going to assume no, there are no RIL related commits in 12/21, hell there's no new commits at all lol
[Verizon Samsung Galaxy S III] mastamoon:
Nope,

http://review.cyanogenmod.org/#/c/28246/ is still unmerged. :sly:
[Verizon Samsung Galaxy S III] PerCompLLC:
Any reason for you to kang another build today? ;)
[Verizon Samsung Galaxy S III] Zacharybinx34:
Any reason they are not merging the fixes?
[Verizon Samsung Galaxy S III] Chris123NT:
I would be interested in mastamoon making another unofficial today, especially if he can fix voice search. It was broken in 12/20 (FC's). No idea if it was working in 12/19 or not.
[Verizon Samsung Galaxy S III] PerCompLLC:
They are waiting on code review approvals... 4 out of 11 +1's so far. I'm not sure how many +1's are required though.

http://review.cyanogenmod.org/#/c/28246/
[Verizon Samsung Galaxy S III] Zacharybinx34:
Ah, so do you think it will be added in tonight's build?

Also, have they done any work on fixing the wireless tethering?

Anyone else notice that it's really difficult to hear people? Super quiet.

If they fix the tethering, data, Skype Mic feedback problem, and the low audio problem, this build well be prefect imo.
[Verizon Samsung Galaxy S III] PerCompLLC:
Beats the hell out of me... Only time will tell. :)
[Verizon Samsung Galaxy S III] Chris123NT:
Did anyone read my posts about JB radios causing problems with CM 10 and 10.1? Funny part is I don't remember having the problem when I first got my phone, but now it's definitely an issue :/
[Verizon Samsung Galaxy S III] xenokira:
Anyone else have trouble tapping and holding widgets to put on the home screen? I can only pick up widgets on the first widgets page in the app drawer...if I flip to the second page or further, none of the widgets respond to tap and hold. Kind of odd.

Edit: forgot to mention I'm on mastamoon's 12/20 build.
[Verizon Samsung Galaxy S III] invisiblek:
None, its whenever someone decides to merge it

On a brighter note, nfc is "fixed" as of last evening

For those who want to fix it on whatever version they are running, flash this via recovery: http://invisiblek.chickenkiller.com/CM10.1-d2vzw-nfc-crapHax.zip
[Verizon Samsung Galaxy S III] gdanko:
If the unofficials have data, why don't the officials? Seems odd.
[Verizon Samsung Galaxy S III] Chris123NT:
The RIL Commit's haven't been merged in official as of yet.
[Verizon Samsung Galaxy S III] PerCompLLC:
Read the posts above... RIL code hasn't been merged yet. In the unofficials that work, the RIL code was cherry picked.
[Verizon Samsung Galaxy S III] Chris123NT:
I wonder if this will fix the issue with the JB radios that I was seeing. Probably not but it's worth a shot lol.
[Verizon Samsung Galaxy S III] PerCompLLC:
That one doesn't make any sense... I've been running VRBLK3 (which I believe is a JB radio) since it came out. Flashed it on CM10, and now I'm on 10.1 and I haven't had an issue. Obviously I'm running an unofficial build (by mastamoon), so I do have data.
[Verizon Samsung Galaxy S III] invisiblek:
No, it won't
[Verizon Samsung Galaxy S III] gdanko:
Thanks. Honestly I wouldn't post builds if this critical functionality isn't merged. Just MY opinion.
[Verizon Samsung Galaxy S III] Chris123NT:
Does your subscription mode switch to NV on reboot? Mine does.
[Verizon Samsung Galaxy S III] PerCompLLC:
No sir, mine does not.
[Verizon Samsung Galaxy S III] Chris123NT:
Maybe it's because of the network extender, I'm noticing other people reporting the same behavior on CM10 with VRBLK1 and K3 modems in the modem thread
[Verizon Samsung Galaxy S III] PerCompLLC:
Network extender??
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah the verizon 3G network extender. Got one because cell service is crap in my house and i don't feel like walking around in my street to make calls LOL.
[Verizon Samsung Galaxy S III] PerCompLLC:
Ahhh... VZW actually just recently put a tower less then 300 yards away from my house. :) It's not 4G though... :(
[Verizon Samsung Galaxy S III] goldsmitht:
wow... wouldn't think VZW would be putting up new towers that aren't the newest technology that they are moving to. but then again, that is vzw for you

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
**edit: I may have herp/derped something with my first build so im rebuilding now. If it works, ill upload **

I would put up my 12/21 build for you all, but apparently something that was merged last night is causing a blackscreen/noboot issue. Thinking kernel related. If they get it cleared up before I leave work today ill put up a build for you guys, if not probably no build till atleast the 26th or so from me. Im sure by then the official nightlies will be usable though.
[Verizon Samsung Galaxy S III] invisiblek:
yea, some display/kernel stuff got merged last night

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

i didn't clobber that build, so the nfc firmware blob is still in there which will cause the nfc problems we've been seeing (sorry about that) will be fixed on the next build, i promise!

for now, flash this via recovery AFTER the rom: http://invisiblek.chickenkiller.com/CM10.1-d2vzw-nfc-crapHax.zip (for working nfc)
[Verizon Samsung Galaxy S III] Restola:
I searched this and the CM10 thread and it looks like people have been reporting issues with key tones not sending since September.

Anyone know of a fix? I think I've tried all the different combinations of settings in the phone settings.
[Verizon Samsung Galaxy S III] mastamoon:
I dialed into work today to check a system message where I have to dial 7 after calling the main number.. worked flawlessly. Made the call, hit the keypad button, then dialed 7. No issue.
[Verizon Samsung Galaxy S III] Chris123NT:
Does voice search work in your 12/21 build? That was the only thing not working for me in mastamoon's 12/20
[Verizon Samsung Galaxy S III] mastamoon:
http://d-h.st/agN Here is the 12/21 build.. working data, mic, nfc, mms rotation, no screen flickering! :good:

Smoothest build yet so far I feel. It even built faster on my machine. Instead of 20 minutes, it only took 16! :D

Enjoy.

---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------

Voice search in Google Now works great, but has for all builds with the 'mic fix'.
[Verizon Samsung Galaxy S III] will.bates94:
They can upgrade the already capable 3g tower to a 4g tower
[Verizon Samsung Galaxy S III] Chris123NT:
Okay cool, thanks, i'll try this later, anything to do with voice search was FCing on 12/20 so hopefully it's fixed in this one then maybe i'll see about running 10.1 as a daily driver and see how it goes.
[Verizon Samsung Galaxy S III] bajasur:
Is there a way (there's a way for everything)... to disable global mode entirely and force your phone to stay on LTE?

THAT WOULD BE AWESOME
[Verizon Samsung Galaxy S III] peaceofpi:
giving it a shot - at least I have backup now - oh and awesome! the fatal triangle again! WTF WTF WTF WTF
[Verizon Samsung Galaxy S III] will.bates94:
so what do i do now since i had a 6x6 grid as my pattern unlock? I cant get into my device after id updated because it reverted to a 3x3 grid. What is there such a big problem with using the cyanogen updater vs flashing it off of the sd card?
[Verizon Samsung Galaxy S III] pyrostic:
Happened to me as well, restore your backup and hope it restores it to 6x6 then remove it. But remember unless you dirty flash back to 12-17 you won't have data. (Pointless if you ask me).
[Verizon Samsung Galaxy S III] peaceofpi:
why was this offered over the updater if all these problems were known???
[Verizon Samsung Galaxy S III] pyrostic:
It sounds like they forgot the commits for the data. You have to remember this isn't a final release and this kind of thing is subject to happening. They put out updates for testing, knowing stuff is broken, they can't fix problems if there are no testers.
[Verizon Samsung Galaxy S III] will.bates94:
well when you update via cyanogen updater does it run a backup of your current rom? if not im boned. and before i restored to an old backup file id had i backed up the broken one that wouldnt let me in. could i maybe flash back to the most recent 10.0 and remove it then update to 10.1 via flashing it from my sd. let me know if yourre confused about what i am saying
[Verizon Samsung Galaxy S III] pyrostic:
Then you are boned... as was I. I just said EFF it. As long as I have my pictures I'm fine with it. I flash knowing these risks are possible.
[Verizon Samsung Galaxy S III] kimsj756:
Can you help me out with this.

I understand and I can locate the backup folders when I'm booted and through es file manager.

But, when I'm in recovery, I cannot locate the the backup file.

Yes, I can navigate to the folder by clicking "install from zip" which gives me the option to navigate.

But, when I click "restore," it doesn't give me anything.

Any idea?
[Verizon Samsung Galaxy S III] will.bates94:
what ill basically be doing is restoring back to the one i couldnt get into because of the grid problem. from there while in recovery i would flash the most recent 10.0 then reboot, go in and disable the lockscreen, go back into recovery and flash 10.1 from the sd card and not cm updater. is that safe?
[Verizon Samsung Galaxy S III] NeoMagus:
I am using CWM 6.0.2.3 - backups are kept at data/media/clockworkmod/backup

I took my old backups copied and pasted them there then they show up in recovery
[Verizon Samsung Galaxy S III] pyrostic:
Sounds safe to me. Just remember you won't have data... so not really worth flashing until they release a new build. (Feel like I've stated this like 4 times)
[Verizon Samsung Galaxy S III] kimsj756:
Thanks a bunch!

My last question is...

Is it safe to clean install TW roms?
[Verizon Samsung Galaxy S III] Zacharybinx34:
So when is Skype going to be fixed?
[Verizon Samsung Galaxy S III] pyrostic:
Please don't ask for eta's on bugs. It's possible the devas didn't even know it was broken. Instead log a bug report and wait patiently... that is all you can do at this point.
[Verizon Samsung Galaxy S III] will.bates94:
perfect thank-you. I guess ill just wait until the next nightly is out with the data fix.
[Verizon Samsung Galaxy S III] atc3030:
Those commits have been up for a while and still have not been officially merged. I am in the process right now of fixing it up and getting a data ready build and will post when I am done.
[Verizon Samsung Galaxy S III] pyrostic:
So were the unofficial builds just cherry picking these commits?
[Verizon Samsung Galaxy S III] tonu42:
Yea, those commits to add the RIL have been sitting there for a while I believe.
[Verizon Samsung Galaxy S III] pyrostic:
Anyone we can talk to about this to get them merged? They are obviously good commits....
[Verizon Samsung Galaxy S III] bose301s:
I am willing to bet that since the build bot is running now we will see those commits added fairly quickly.
[Verizon Samsung Galaxy S III] invisiblek:
CM10.1 changelog app, will contain the same information you'd fine here: http://10.1.cmxlog.com/

https://play.google.com/store/apps/details?id=com.invisiblek.cm.nightlies
[Verizon Samsung Galaxy S III] Restola:
I had issues getting into a conference last week and deleting a voicemail today (i dont get many voicemails, so not a lot of reason to check if its working), just dialed again and it worked...no idea why but I'm happy :)

Thanks
[Verizon Samsung Galaxy S III] ctyke:
Wondering if I am the only one where my headphones don't work with phone calls. Music works. It has happened on every nightly since 10.1 came to be.
[Verizon Samsung Galaxy S III] vdefender:
Just flashed this for my first 10.1 build. Came from CM10, but i did a full wipe. I can't get activated on Verizon. I don't have the right phone number and my signal just says roaming. My IMEI is there though. Was there something I missed to get activated?
[Verizon Samsung Galaxy S III] mastamoon:
I believe the fix in training is currently to bypass activation by tapping the 4 corners of the screen then checking to make sure your phone is set to RUIM/SIM in CDMA subscription.
[Verizon Samsung Galaxy S III] will.bates94:
Fixed my nfc!! thankyou!!! seems very smooth!! Ive also noticed that the ringtone is still distorted at high volume and the calls are very quiet even when turned up all the way.
[Verizon Samsung Galaxy S III] Stupifier:
Voice Search works for me on mastamoon unofficial 12/19. I'm about to flip over to mastamoon unofficial 12/21 tonight though. These unofficial builds are great.
[Verizon Samsung Galaxy S III] Restola:
FYI Wifi tethering activates on mastamoon's 12/21 but my pc cannot connect to it.
[Verizon Samsung Galaxy S III] vdefender:
Getting back Phone number / Data easy with no factory reset or ODIN

^^^ THIS!!!

I had no Data and no Phone number when I flashed todays unofficial CM10.1. I nandroided back to my CM10, still no data or phone number. I went into airplain mode, then turned it off. Then I noticed that my mobile network setting was already on NV, so I switched it to RUIM/SIM and it grabbed my number and popped onto LTE immediately. Whew!
[Verizon Samsung Galaxy S III] M Diddy:
Odd.

Installed Mastamoon's 12/21 build. Had to switch the CDMA Subscription to get data, and everything seems to be working fine. However, when I check system status, both the Phone Number and MIN are unknown. How is the phone working without knowing these values?
[Verizon Samsung Galaxy S III] Amore514:
i flashed an earlier build and the headphones didint work, do they now?

---------- Post added at 12:09 PM ---------- Previous post was at 12:02 PM ----------

Can someone confirm is the headset is working on the 12/21 build? i saw CM Change log has this fixed a few days ago..
[Verizon Samsung Galaxy S III] Droosh:
You're not alone.
[Verizon Samsung Galaxy S III] littleneutrino:
Just flashed 10.1 and it saddens me to say that Dock Audio is broken again :( it was working perfectly fine on the latest 10 nightly :(
[Verizon Samsung Galaxy S III] NeoMagus:
Is anyone elses signal strength in status borked on masta's builds? Is this because of the RIL commit? Phone number, IMEI all that stuff shows up fine but on 12-20 and now just tried 12-21 signal strength doesnt seem to work. Nandroiding back to the 12-16 and its fine again
[Verizon Samsung Galaxy S III] will.bates94:
10.0 is very different than 10.1. everything is being looked at im sure

---------- Post added at 02:21 PM ---------- Previous post was at 02:19 PM ----------

my signal strength is working perfectly, but i am also not on 4g. all my stats in that menu are perfect.
[Verizon Samsung Galaxy S III] NeoMagus:
yeah this is on LTE I have not looked at it on 3G it may work but I always run it on 4G
[Verizon Samsung Galaxy S III] will.bates94:
go to settings and change your network mode to cdma/evdo auto and see what it says then. if it shows the signal strenght properly then the 4g signal strength is broken ill assume
[Verizon Samsung Galaxy S III] NeoMagus:
I already flashed back to 12-16. Works fine on there thats why I am wondering if its on my end or something RIL did since did not work for me on mastas 12-20/21. Don't know if the 12-16 had that commit in it or if anyone else has noticed that in their status.
[Verizon Samsung Galaxy S III] will.bates94:
Well 30 minutes north of me just got 4g today so if i head up that way ill be sure to look and report back here...
[Verizon Samsung Galaxy S III] swirly05:
Any fix on the screen flicker?
[Verizon Samsung Galaxy S III] mastamoon:
Click disable hardware overlays in developer options seems to help.
[Verizon Samsung Galaxy S III] k1ska:
Well, I'm curious whether there's going to be an upcoming fix for the extra loud, distorted speaker settings as well as the extra quiet, nearly inaudible sound in call.. On 12/21 Unofficial build, I'm still getting screen flickering D:
[Verizon Samsung Galaxy S III] Zacharybinx34:
Speaker phone doesn't work, it gives a bad echo to the caller on the other end.
[Verizon Samsung Galaxy S III] WhammyDroid:
Mastamoon, I have found a problem with your builds (currently on 12/20 build; not sure if this is a general 10.1 issue). When connecting the phone to a Win7 laptop via USB and trying to write to the internal storage, the file being written is always being written to the SD card (and vise versa if trying to write to the SDCard; file will appear in Internal Storage).
[Verizon Samsung Galaxy S III] Phush:
edit: nevermind
[Verizon Samsung Galaxy S III] bchi49:
Fix the roaming issue by fixing missing IMEI using this:

http://xdaforums.com/showthread.php?t=1867442
[Verizon Samsung Galaxy S III] Rixanu:
Is anyone having issues with notifications vibrating when they shouldn't? I have both Gmail and Facebook set to not vibrate on incoming notifications but they vibrate anyway. This is after a clean install of Mastamoon's 12/21 build. It also happened on a dirty flash of the 12/19 build.
[Verizon Samsung Galaxy S III] ming3r:
It seems to be a 4.2 problem.

My battery seems to drain faster than before...odd. 2 hrs on and down to 80...before this would still be at 90
[Verizon Samsung Galaxy S III] blackguy101:
So i am coming from clean rom 5.1 and im really tempted to flash the mastermoon build right now. On a scale 1-10 how stable is it as of now? are many people having data issues on this exact rom after doing complete full wipes?
[Verizon Samsung Galaxy S III] Rixanu:
I'd give it an 8. I clean flashed the 12.21 build today and I had data issues. The phone would activate and then force me to reboot every time to "finish activation" I ended up having to do a four corner tap to bypass activation and set my CDMA subscription mode to RUIM/SIM. That fixed the data issues, but bypassing activation meant that I had to manually link my phone to my Google account and set my settings up manually. So it's a bit of a headache to set up, but otherwise it's fine. If you don't want to deal with data-not-working shenanigans then I would suggest flashing mastamoon's 12.19 build. I think that one should have working data from the get-go.

Some other issues I've been having are low volume in calls and screen flickering, but the latter can be fixed by disabling HW overlays in the developer options. Also, like I said earlier, all incoming notifications seem to make the phone vibrate whether you want set that particular app to trigger vibration or not. They're all pretty minor issues, in my opinion. However, this is just my personal experience so far, there may be other issues that I haven't found/discovered yet.
[Verizon Samsung Galaxy S III] blackguy101:
Ok so i flashed this and it turns out that i am unable to make or recieve any phone calls. I can get text just fine though. Is there any way to fix this?
[Verizon Samsung Galaxy S III] odub303:
Nope. You're screwed.

Sent from my Verizon SGS3
[Verizon Samsung Galaxy S III] pie944:
Hi,

So just flashed the latest nightly, was running latest Slim. Did a full wipe, flashed the nightly, got the error saying it needed me to place my SIM card in. Now I have no Data, it shows a signal but all calls go straight to voicemail. No Data. WiFi only. I tried to find my nandroid backups but it says the folder is empty?

Any help??
[Verizon Samsung Galaxy S III] Rixanu:
Hmmm...odd. Your CDMA subscription mode is set to RUIM/SIM, yes? If it is and you still can't make/receive calls, I would suggest flashing back to a TW rom and dialing *2767*3855#. This will re-provision your phone on the network and should fix any voice/data issues. It also wipes your internal sd, so be careful.
[Verizon Samsung Galaxy S III] Deevious88:
I'm gonna go ahead and assume no one is actually reading the first and second posts... If you have no Voice or Data, READ POST #2.
[Verizon Samsung Galaxy S III] odub303:
That's why I responded in a less than helpful way lol. I read this thread for issues or news, not so I can read the same questions over and over and over. :mad:

Sent from my Verizon SGS3
[Verizon Samsung Galaxy S III] Rixanu:
The official nightly? Word of advice: don't flash nightlies before reading up to see if they are causing any issues. All of the official (and some of the unofficial) nightlies are causing data headaches for everyone.

They probably got moved. I'm assuming they were on the internal sd, yes? Check for a folder at the root directory called "0". They might be in there, along with the old contents of your internal sd. I guess you could move them back to their original location to get recovery to find them. Are you using TWRP? I think the latest one is supposed to still find your backups in this sort of situation. I don't know about CWM. Links to the latest recoveries are in the first post.

At any rate, nandroiding back isn't going to fix your data. Make sure your CDMA subscription setting is set to RUIM/SIM. If that doesn't help, the most effective course of action would be to flash a TW rom and dial *2767*3855# to re-provision your phone on the network. It also wipes your internal sd, so be careful to back it up.

Finally, don't flash any official nightlies anymore until data is fixed. If you must have 10.1, then try mastamoon's builds, but I have no promises that they won't have data issues for you as well.
[Verizon Samsung Galaxy S III] blackguy101:
Its fine I understand. I just flashed back to TW