yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mgianni19:
Ah, thanks dude!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Just installed 03/11...man...what's with all the options in "mobile networks"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Possible fix for LTE issues coming tonight.

http://review.cyanogenmod.org/#/c/60871/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
My mobile network just keeps randomly dropping in and out. I'm set to the global option. Tons of issues over past few weeks with service at all, much less LTE. What is everyone using under their mobile network option?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah if you set to something without LTE it doesn't seem to drop, at least it didn't for me.

I've made an nvrestore after making a nvbackup back when I got the phone, then flashed the latest nightly and since then my signal didn't drop. Switching back to stock then latest nightly also fixes LTE/signal drops I believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
I saw that in a comment on the new commit. Would that require ODIN'ing back to stock? Couldn't just clear and flash, could I?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I think you can simply factory reset then flash, no ODIN. Not 100% sure though, I idle between a few roms myself so I have my own routine deeply ingrained and I fixed my issue using nvbackup/nvrestore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
I wish I had an actual nvbackup sitting around, but alas, poor planning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Not something most people do. No surprise here. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I'm still looking for a way to do this from a Linux computer, instead of the Windows executibles I have seen in the threads. I don't plan any upgrades past 4.1.2 until I find the method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You don't need a windows computer for nvbackup/nvrestore. Either do it with adb or from terminal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I did previously copy the efs folder and contents. Somehow I didn't think that was sufficient.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Can someone give me link to latest nightlies. The one in OP has builds only till Feb.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's not the best indeed. But nvrestore/nvbackup is an integrated solution, no executable or anything, simply "reboot nvbackup" or "reboot nvrestore" from terminal/adb.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Thank you, Polobunny. I had previously read several threads that had said to run

su
reboot nvbackup

I had not done so because each of the threads I read also had instructions to install a .qcn file, doing so with a qpst zip. This is what led me to think there was a windows executible that was used.

Subsequent to your post I searched and read more. I followed links to the thread on the Verizon SGS3 forums related to nvbackup, [HOWTO]Comprehensive IMEI/EFS Backup There is a very complete explanation here. I have now done as you and it recommended. My next step is the Synergy flash. Following that I am back to 4.1.1 for the unlock and then on to the custom world.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes I was just linking someone else via PM to this thread. It's a big thread but full of great information regarding EFS/NV safety.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
03/12 fixes the buggy mobile networks list, but my LTE is still FUBAR
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Same here, but haven't tried a clean install yet. No time this morning, maybe tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
Found under d2lte now.

Sent from my SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Flashed 3/12 coming from 3/10 and my phone switched back to Dalvik from ART.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Mine didn't. Isolated problem. Running a custom kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Anyone else notice a lack of those traffic arrows on the WiFi symbol on the status bar? They don't show up like they used to... They still do for mobile data, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Ha, no, not until you said it. Same for me here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
So still no LTE, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GlassRaven:
Running d2lte/03-12-2014 nightly. Encountering a problem with media scanner not recognizing external SD card (32GB; FAT32 format). ES File Explorer and default CM File Explorer can read the external SD card and play the MP3 but the media scanner won't scan the mp3 files and any other files from the external SD card.

EDIT:

Fixed the issue by deleting the .nomedia file on my SD card that was there for some reason (WTF?!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Nah they fixed that in a recent commit, bro. I think in the latest nightly.

LOL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Really? 2 guys on the previous page said their LTE was still not working on 03/12...just wanted to make sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
Maybe in 03/13 is fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Flashing to stock TW and then a newer nightly will fix any/all LTE issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
I don't even know what LTE issues you guys are having. Never had them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Is there any way to get LTE working without flashing back to stock?

Anyone know what the problem is exactly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
No, and no.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
Are you suggesting a full ODIN return to stock or just flashing a TW stock rom after wiping date and cache?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Odin. It's the only way.

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

Read the notes on patch set 4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
The d2att builds didn't have any LTE problems. There have been issues since the first d2lte build but there appears to be a commit for the 3/13 build that may fix it. It's a ROM/APN issue, nothing to flash back to stock over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Well I can confirm that LTE is still broken on 03/13 and still getting network drops if set to gsm/cdma/lte instead of just gsm/cdma.

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
The 03/13 commit has nothing to do with the LTE signal drop issue.

For those wanting to fix it, flash back to stock, verify LTE is working, reflash latest CM. Done.

Additionally, you can make a recovery backup of your current CM install, flash stock, then restore your backup and that works too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
What about flashing a 10.2 backup where LTE was working then flashing 11?

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No. That won't work. Unlike what RJantu said, making a backup in CWM/TWRP, flashing stock via CWM/TWRP or ODIN, verifying LTE work then restoring the backup works in restoring LTE. Don't need to absolutely ODIN to stock or clean install CM11 again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
Yeah. I'd like to know how to proceed with this as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Read my post above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Glad I checked this thread. Been having intermittent LTE issues since flashing D2LTE build.

Does anyone have a link to a flashable stock zip preferrably pre-4.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
wait wait wait!

It's important to note that if you have the MJB bootloader, you cannot flash a stock rom that contains a bootloader file prior to this. If it doesn't contain a bootloader, you're fine, but if it does, you'll end up bricking your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Yes, I know. I should have mentioned that up front. I am on MG2. I just made a nandroid, so now i need to grab a pre-rooted stock zip that is prior to 4.3, flash that. Then re-install TWRP and restore my nandroid. Does that sound accurate?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You can grab a 4.3 stock CWM/TWRP zip as long as it doesn't have the bootloader. That's the only inaccuracy. If there's no recovery in it then you won't even need to re-install TWRP! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I haven't touched TW since CM builds started on the S3, and I havent really noticed any LTE issues so I haven't been following the discussion. Can I just nandroid my current nightly, flash a CWM zip TW without bootloaders, and then restore CM? No issues with partitioning or anything? I'm on the MG2 bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes you can. But you don't have any LTE issues or data drop? If it's not broken, don't fix it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I don't get LTE in my office (but i do in the bathroom lol), and I'm on wifi at home. LTE works fine when I'm on the can as far as I can tell. Not sure if I'd notice it dropping back to H+ but I've never had data completely fail.

I'm just wondering if my ability to pick up LTE in marginal reception areas might be improved. I used to get it very clearly at my house (long before these CM issues came about), but over time it seems to have degraded.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Well I just turned LTE on at school and it magically started working...I'd say the signal is lower though because I used to get LTE at home and yesterday it wasn't connecting.

Then again...the LTE has always been crap on this phone because of the bands it has.

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Shouldn't affect LTE signal quality. If you flashed a modem/bootloader combo I would imagine this could be the cause for the degraded quality.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Eh, I think I'll give it a shot because I like to play with fire. Might as well get up to MJB anyway since I'm on MG2 bootloader and baseband, and I could probably use a clean flash for once in my life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No need for MJB though, go with MJ2. If anything, it's pretty much identical to MJB, minus the unability to return back to a previous bootloader.

http://invisiblek.org/d2firmware.html
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I can't hear anything in my phone calls now. Total silence. So I need to flash back to stock? What should I use so I don't brick my phone? Can someone share a link?

I've tried toggling between the ATT LTE and the ATT Phone APNs.

I'm on I747UCDMG2

So, I guess I need a stock rom that also has the MG2 bootloader to preserve what I have now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cristianpark:
I got similar issues with the last nightly I used, I'm in MJB so I can't flash stock from sammobile and didn't want to mess with removing bootloader or anything else so I flashed S3Rx that so far is pretty amazing, isn't CM but it has 4.3, modified touchwiz or even CM like theme and Cerberus app and HDMI output works (Cerberus is a deal breaker for me since I recover a lost cellphone with it). I'll give current nightlies a try soon to see if Cerberus is working fine already
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Well I might have "fixed" it. I made a call with Bluetooth and I could hear the call, and now I can hear my phone speaker also. Need to see if it survives a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Another reason to go with MJ2 modem is Pwncakes said it hangs on to LTE better than any other. See if you notice a difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Modem is showed under "baseband", right?

I had MJ2 before but now it shows I have "MF1"? How is that possible? All I did was flash a new nightly...

Maybe that's why my LTE signal is so bad now...

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, baseband is modem. Did you flash stock rom to fix LTE or something of the sort? Also you can't have MJ2 if you have a Canadian phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
No I did not...and I had MJ2 before on a Canadian phone..lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If you flash a modem meant for d2att you'll end up with baseband "Unknown".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Oh geez...I was thinking about bootloader and "MG2", not baseband and "MJ2" lol.:silly:

I don't see the bootloader info listed anywhere in my status menu on this nightly, though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Ok, my phone part of my phone is near useless, including now the data drops. So I guess I get to flash back to stock. Is there a particular ROM image I should use with the mg2 boot loader so I don't brick?

---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------

There's a bunch of stuff about lte in the 0314 build. Any magic fixes in there? Anything to keep me from being to flash back to stock? Downloading now for flashing.

---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------

One thing I can say is modem is not boot loader, and make sure you get it right so you don't brick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
You can flash any TouchWiz ROM and it will fix everything for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's alright, and that's normal, it's not listed there. :p

You can either use "adb bugreport" and check for bootloader or use an app such as Device info (here)

---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------

If you have the MG2 bootloader, no, there's no required special flash or anything.

One thing to note though, you don't need to ODIN to stock contrary to what you might have read or what people might have wrote in a hurry. You can make a CWM/TWRP recovery backup of your current install, flash a CWM/TWRP flashable TouchWiz based rom, verify LTE is working and then restore your backup an it works just as well.

Off the top of my head, some TW based roms: Dandroid, S3Rx, Wicked Sensations, Hyperdrive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
I checked using device info, and it still shows MF1. Is that an outdated boot loader?

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
MF1 is the last one before MK5. MK5 cannot be downgraded. I personally use MF1 just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Oh, man. This is interesting. I flashed Dandroid and it just sticks at the CM logo on boot. I let it run for 2 minutes. How long should that stock ROM take to boot, and should I be seeing the CM character? I thought stock based ROMs would boot pretty fast. I can't ADB, etc.

I'm restoring my nandroid to CM11 now, hopefully I can get the S3Rx rom to boot. Why is that monster 1.8G?!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Wasn't having any issues but I decided to go back to stock to see if I could get any better LTE performance. Wiped everything including sdcard, Flahshed LK3 stock, then MJ2 with MJB baseband, then the latest nightly. No noticeable change at all.

So if you were never having data problems, don't bother going back to touchwiz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Did you factory reset before flashing Dandroid? TW is longer on first boot, like quite a while. As for boot logo, it's "CM'ified". It looks a lot like CM10/11 so don't be surprised by the logo. :p

Thanks for the insight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Which stock ROM did you flash back with? I'm having trouble getting one to boot with TWRP as my recovery. I'm MJ2 bootloader also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I used the S3R version, and followed the nvrebuild steps under the fix for GPS section in the S3R post to be sure. Much better LTE since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
For those with LTE issues...

Dandroid worked for me, but only after I ODIN'd TWRP (I was using CWM and Dandroid doesn't like CWM).

So if someone wants a way to do it with only ODINing a recovery (and not a stock firmware), this should work:

1) ODIN TWRP onboard

2) Backup in TWRP

3) Wipe

4) Flash Dandroid, Wipe Cache/Dalvik

5) Boot, check LTE (repeat as necessary)

6) Wipe

7) Flash latest CM11 nightly

8) Restore all your settings and the like from TB, etc.

9) Flash CWM (using ROM Manager)

10) Reboot, check.

11) Backup using CWM

12) Enjoy doing 5 hours of phone work because CM broke LTE then didn't know why!

13) Don't profit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
12 exaggerated. I do that process every so often I can pull the whole steps under an hour. Minus flashing a new recovery, but yeah. You can also just restore your CM11 TWRP backup instead of re-installing, not that's the longest part. Longest part has to be downloading a huge as heck TW rom. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
I could have used my backup and restored? I was worried this would let the LTE issue persist.

Also, Dandroid is on the smaller side of TW ROMs, thankfully.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yep, that's exact. All you really need to do is boot a TW rom, check LTE state, and then you can restore your backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
siggggggggggggggggggggggggggggggggh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
On the plus side, nothing feels better than a fresh install, and you're assured you're not having issues related to dirty flashing nightlies on top of nightlies since forever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Dandroid worked after I read all the instructions. Factory, wipe cache, dalvik, then finally it will boot. All working now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Odin'd to LK3, CF-Auto-rooted, flashed TWRP from goomanager, flashed MJ2 (actually bootloader/modem package from invisiblek, then rom, then fixed kernel - all from http://xdaforums.com/showthread.php?t=2498233). I'm pretty sure I could have just gone straight from LK3 back to CM11, but I had downloaded MJ2 already and then realized that it was CWM/TWRP only and some had said an ODIN flash was necessary.

How did you install TWRP? I usually just use goomanager then delete the app, it's the safest way IMO (dd is nicknamed disk destroyer for a reason!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Because people have fat fingers. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Northerntouch:
Nightlies

Why is the latest d2att nightly on the download page time-stamped for Feb 16th. Are they not supporting d2att anymore?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yeah, goo manager or fastboot on other devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Yes, someone please update the OP with the latest developments in the world of CM11 for d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
All the d2's were merged into d2lte.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
The thread title should still be updated, or a new thread started with up to date information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
If it doesn't matter who does it, I'd be willing. I just don't want to infringe on anyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Thing is, I don't think it can be changed by anyone except the OP or a moderator. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
I'm talking about creating a new thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I second this: someone please create a new thread with updated flashing info. Many thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Ah. I say do it. What's it going to hurt? I doubt the OP is going do anything about this one any time soon, especially since CM 11 has been out for a while now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
The original post is from cyanogen. They work on tons of phones. They won't come in here and update the thread as I'm sure there busy and it's really not an issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Sure, and I don't expect them to, but it is an issue when the current releases are CyanogenMod 11 and the thread title still says CyanogenMod 10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
NEW CM11 THREAD LOCATED HERE.

http://xdaforums.com/showthread.php?p=51117813
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] v1nsai:
Everything seems to work, I was getting the "searching for GPS" problem until I installed the gapps. That seems to have fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Was this on CM11 or CM 10.X?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] v1nsai:
Oh right, this was on 10.2.1-d2att. I'm still debating on whether I'll be switching to Android, so I'm sticking with the stables for now.

One other issue though, the auto brightness is really dim, is there any way to increase the auto brightness's intensity?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Settings > Display > Brightness

Make sure it's set to A (Auto) then click the cog wheel at the right. Then click adjust and you can input your own settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Post in the new thread guys! We can't have two active threads.

Well I guess if you're gonna talk about 10.2 post here but that isn't really supported anymore [emoji15]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] v1nsai:
I don't have time to play with nightlies unfortunately, on the cyanogenmod website 10.2 is the latest stable so that's what I'm on. And since this is the 10.2 thread, I'm gonna go ahead and keep posting stuff about 10.2 here. Unless there is a stable of 11 that I missed? I got an update notice but the filename looked like a nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
"Stable", no. But that nomenclature is vague anyway. I've been on 11 for a while now and it is pretty much as stable as you can get.

I don't exactly "mess around" with nightlies either...flash one and that's it.

I just posted that to warn people that most of us have moved on to 11 so support here is gonna be slim even if it is the technically the most "stable"...and we didn't want people posting about 11 in this 10.2 thread because it just causes confusion.

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
But this is the original cm thread. There should be one thread for cm period. You guys added a thread that was not needed. Most info is on this thread anyways.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Of course it is. Unfortunately the creator of this thread is not around to change the title...so we're talking about 11 in a thread that says 10.2.

If a newcomer came here looking for the 11 thread, do you actually think that he would come here to the 10.2 thinking that "oh they must have not updated it yet after months of 11 being out"?

Sent from my S3