yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
You're using GEL? Mine are quite a bit bigger...but pretty sure they made it that way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No I'm not, I imagine this could be a possibility. Nice catch!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Yeah...Trebuchet has the option to change it...pretty sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Yup my icons look just like that when I flash kk rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rvash:
Is the 3rd party front facing camera bug fixed in the latest STABLE (10.2)? Kitkat isn't stable enough for me at this point - and I would rather just be on jellybean if this is fixed. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No it's not. Not in the last cm10.2 nightly either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Where is this problem present exactly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Front camera was broken in CM10.2 stable/nightlies unless the app you were using included a fix.

In CM11, they've worked and are still working really hard on a camera wrapper to handle everything. Sort of a buffer zone that deals with the camera that other programs access instead of the camera directly to put it simply. It's not an easy task, so it constantly shifts from decently working to breaking.

The maintainer for our device (invisiblek) has mentioned not wanting to port the wrapper back to CM10.2 for a real final version, although I almost tempted him. :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Oh, sorry. I thought rvash was talking about CM11...

I haven't seen any problems with front-facing camera in CM11,yet; although I only tried it in Instagram and WhatsApp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
For those who had the absent country code and incoming call issue, can you test out 0228 nightly and see if it has stopped? It has on my end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I quickly checked as well and caller ID looks to be working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
NO its not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
I have massive battery drain on the latest build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
Cyanogen did mention that he was working on Project Butter in the T-Mobile CM10 thread... ;)

Plus, Qualcomm recently released their Adreno drivers for JB, so I'm sure good work is being done :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Camera bug?

Does anyone else have a problem using the camera when the flash is on?

What happens is when i hit the button(to take the picture) the picture is captured first and only then the phone focuses and the flash goes off (so i have a blurred picture without flash). :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Isn't this a known bug (camera cannot focus)? I did a test in a dark room with flash on which I could take a very clear picture even camera couldn't focus properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
In the dark somehow it seems to work. What abt normal lighting? The picture is taken and only then the flash goes off for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrakifa:
Do we have crt off animation on this Rom? If not is there a way to get it? Thx

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
might want to think about bringing some of these questions over to the Q&A thread.

Do a search in the Themes thread for the CRT animation, there might be something there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enzyne:
Face unlock also force closes :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T3hBraveBoss:
Ill consider flashing onto this, any known issues not stating on main topic?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Yeah I know how to Google search the difference between ics and jb but can someone explain why it appears that this and other jb roms almost go backwards in its UI and menus, etc? Is it the roms or just jb in general? Cuz they remind me a lot if ics 4.0.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Not really. Is a very stable build. I have used it as my daily driver since it dropped. I'm on aokp currently but going to switch back when the new build releases.

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
This is a dev thread not a Q&A or discussion thread, everyone please post in the apporiate place.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
Please use the Q&A thread from now on. ICS and JB have next to no visual differences. JB is primarily a feature upgrade, not a GUI upgrade. Much like gingerbread and froyo were. The stock ROM on the SIII comes with an overlay that Samsung places over Google's interface called TouchWiz. This is why the stock ICS on the SIII looks different from CM10. the CyanogenMod project has always been an attempt to give users the pure Google experience on a phone. If you want TouchWiz back, you will have to stick with TouchWiz ROMs, which you can find in the Android Development section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Is it better to do a clean install or go from CM9 to CM10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
your going from ics to jb, of course, its required... even better is doing fresh installs every time...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dwd3885:
Absolutely. Unless you need Bluetooth, then it's fantastic. Not as buttery as the GNex, but it'll get there soon I imagine!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Actually you can make the jump from cm9 to cm10, but I personally wouldn't recommend it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Just installed this and WOW this is a huge improvement over CM9 speed wise. Where is the camera app on CM10? Its not in my listing of apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
You need to install the JB GAPPS after installing rom - found here http://goo.im/gapps/gapps-jb-20120726-signed.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dillonc:
Yes there are plenty of new issues that aren't stated in the first post and you can read all about them throughout this thread just like everyone else

Sent from my Samsung Galaxy S III rocking CM10 Jellybean
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Did you flash GAPPS after flashing the rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Check with betterbatterystats. Can't outright guess your problem to help you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I noticed the same today. It looks like it might be Bluetooth related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
Anyone running the latest nightly?

Is the LTE pickup fixed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
Hey guys, I'm still on cm-11-20140217-NIGHTLY-d2att, can I just make a nandroid of just my data and restore when I'm on the d2lte builds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
I would just backup apps and data with titanium and use that...not sure how it works with CWM.

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
No insane drain here. Doesn't look like anything Bluetooth related was even pushed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Just flash straight away. Live on the edge.

But seriously, you'll be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
I flashed 3 times, each time returning back to stock 4.3 to fix the Lte and then flash a newer nightly to see if the LTE is fixed but each time LTE pickup was broken. So now I'm scared and dont really want to go through the whole process again.

Soooooo does it work good?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Then no.

I don't see how tedious this can be... Backup in recovery, flash. Not happy, restore backup. 15 minutes in and out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
ya thats all fine but when I restore to cm 10.2.1 my LTE is still broken so I need to flash stock 4.3 and start completely clean... so it is very tedious...

Its alright, I'll try again with the latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I do that nearly daily and my LTE works just fine upon restoring. Are you wiping before the restore? Are you restoring all partitions?

In my signature it says TW 4.3, but I test almost all CM11 nightlies, often switch to CM10.2 directly from that and then switch back to TW 4.3 when I have important work to do. Mix in that a bunch of different others roms too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Once you restore, you probably just need to go back to settings...mobile networks...and set LTE as preferred..it should stick then.

FYI, I did notice LTE sticking when I'm running 3-1-14 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Anyone else getting constantly dropping data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Disable LTE to circumvent that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Latest nightly causes problems with the phone apk, resulting in constant error boxes, and forcing you to revert to 3/3. This is your fair warning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Oh 3/5 is out! *doesn't listen to warning*

Edit: No issue here. Just made a call then took my voicemails. All working fine, using dalvik however.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I've been seeing hours of wakelock for "wlan_wake" for nightlies in the past week or so. Anyone else seeing this? If not, it would probably be due to me switching to a new wifi router.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Most likely router. Something is keeping your wifi awake either by receiving or sending data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
No problems here either. 2 hours running and 20 min voice calls.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
I'm using ART. I had to clear contacts storage after I flashed back. I suppose it's a ART related issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I've been running ART for close to a week, just made a call on 3/5. No issue here yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
+1 30 minute call on ART with 3/4, no issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Same issue here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Using 0-Day gapps, too?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Using 1702 pa gapps mini modular here, if that helps. No phone FC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
It does help. I must've messed up somewhere. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
The 3/05 build has constant phone process crashes. It happens pretty much constantly rendering the device effectively unusable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Yep, using Full. Interesting that some flavors work and some don't. I couldn't even flash back, as I'd end up in a boot loop after the flash of cm11-03-05-14. I ended up restoring a nandroid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
I take that back. Do not install! Youll be sorry. Its only a matter of time :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Weird, mine still doing good. Ah these flaky nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yeah, just made a call after almost a day of uptime. Worked well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grimez:
I was getting the constant phone process crashes as well, so I decided to do a little experimenting.

First time was a dirty flash over another D2LTE build (2/26 I believe) and gave the constant crash.

Clean flashed and worked fine for the time I had it set up.

Clean flashed then flashed LeanKernel (latest variation) and gave the constant crash.

So I am going back to the clean flash with the stock kernel to see how it works. Also, as another note, I do not use any GApps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greenro89:
How do I replace the CM camera? On CM11, my Snapchat app is stretched and stutters. Looking to get stock like nexus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
anyone flash 3/6 nightly yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yep.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yeah, got stuck on boot logo animation, but wiping cache fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Thanks and good bye!

What a group of great ppl here... need to say goodbye here and move on as my S3 died finally and not worth to pay for repair. I'd like to thank everyone who contributed the thread especially CM! Great guys, keep up! See you on another section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What did you do? =(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I put the LTE toggle in my quick panels, but it just stays lit. Is there another method to disable LTE?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Settings > More > Mobile networks > Network type

Select one without LTE in there. The LTE toggle is broken, and so is LTE since the d2lte merge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
There was intermittent power button issue (very close to the infamous issue from the Captivate). I had it but then it's gone then came back yesterday again. So sick of it... thought about to have it replaced but think might not worth the money.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah this is one of these things usually worth it if you do it yourself but a good excuse for an upgrade if you get it done. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
FWIW, after flashing 3/6 my power button would not lock the screen (neither would double tapping the notification bar). Rebooting fixed it.

Although I had the same issue with my captivate too. I was glad to see double tap locking in CM11, as it takes some of the wear and tear off constantly using the power button to lock the screen. Of all the hardware keys, it gets the most mileage for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
com.android.phone crashes constantly on 3/05 and 3/06 even after wiping the data for com.android.phone. Anybody else having this issue or any solutions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowner:
ditto here :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Well I ended up installing Xposed because I seriously thought I had read somewhere that KitKat support was now offered...

After installing it and testing out XuiMod I couldn't help but noticing a lingering lag on the whole system...looked into developer options and saw that Xposed had reverted my system back to Dalvik...doh! (I know it says this in the Xposed thread but I honestly remember seeing ART support somewhere).

Suffice it to say I deleted Xposed and restored my KitKat backup with working ART and am so much happier...a lot snappier.

Even after I uninstalled Xposed on my other install I tried to switch back to ART and it wouldn't...I hit ART, reboot, and was still on Dalvik...good thing I had a backup to restore to.

The stuttery animations on KitKat can sometimes be very annoying, but no where near as annoying as the lag Dalvik has in comparison.

So...uhh...yeah :D note to everyone.

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nope, definitely no support for ART because of how it works. Don't think there ever will.

As for ART vs Dalvik, I see little to no difference between both*.

I'm surprised it's night and day for you. I still linger on dalvik for the sole reason that's ART is in the dev section because it's definitely rough around the edges and some software that I use daily are not ART compatible yet. Can't hold it against devs to make their apps compatible right away when it's not even close to be official. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Well I can definitely notice it when I move from one app to the homescreen, and open another app quickly. Opening apps is faster on ART than on Dalvik...definitely not a placebo either as it was quite noticeable for me.

Might have been just me, though.

Anyone try out 03/07, yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Does anyone else notice that with ART, that the device seems very I/O bound? I notice now that streaming music will cut out heavily when installing apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
I've been on 3/3 since the phone issue. Anyone who had that issue before have any success with 3/7?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Haven't tried it but there are doesn't seem to be any commits that could offer a fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
OK. I'm gonna fart around on 3/3 until I see a dialer commit then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I have noticed that. I don't use ART full time, but I've tested it and I didn't pay much attention trying to fix it since some apps I use aren't ART compatible.

I know it's no help since I didn't have an issue to begin with, but 3/7 runs just fine here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Is it possible that you are not seeing the dialer issue because you are not using ART? I'm using ART and have dialer issues. I would just switch back, but it takes a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Very probable. I've had issues with ART not too long ago (unrelated to my apps that don't yet support it) in CM11 nightlies. I test most if not all of them and switch between like 4 roms as of late. Can't be arsed dealing with finnicky ART. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm on ART without dialer issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Did you have issues before? Are you on 3/7?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
No issues before. Yes.

The only issues I've had is that I have to wipe the cache in recovery using cm updater. It keeps hanging while compiling for ART.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Damn. I'm banking on it having to do with my setup, then. KT's latest kernel, 0-Day Gapps, and ART. Something isn't right somewhere in there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I didn't think I was having issues until I tried to access the mobile network settings through the quick settings tiles and our consistently crashes phone that way. Oddly I can still access it through the settings menu.

I will switch if ART and see what happens.

---------- Post added at 06:11 PM ---------- Previous post was at 05:34 PM ----------

So I switched back to dalvik, and phone still crashes when I access the settings by pressing the 2g/3g tile.

To be clear, I can still use the phone. I just cannot access the settings through the tiles. That definitely worked back on 2-27.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
M4 Snapshot Incoming.... Just waiting for d2lte build from CM servers..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
No m4 for d2, jf, or h. Not stable enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
That seems likely.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
0308 nightly is buggy, don't touch it guys. Consider yourself warned.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So there won't be an M4 release at all, or is it just coming late?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
No problems here. Setup?

---------- Post added at 09:24 PM ---------- Previous post was at 09:22 PM ----------

Might you be speaking of 3/9?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nope. Reboot and see what I'm talking about. I was able to replicate the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
No issues here. Then again I'm now running stock kernel and Dalvik.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
No issues here either yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Hmm strange than. Rebooting on 0308 makes the phone act half like new, CyanogenMod account setup and whatnot, frozen apps become unfrozen, etc. 0307 is fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
KToonsez's 3/09 kernel fixed the phone crashes for me! I guess it relied on a kernel commit that wasn't yet present in custom kernels.

KT's 3/09 kernel and CM 3/10 nightly running smoothly here!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
How are folks with stock kernel and 03/10? The 03/09 commit went FUBAR for me with the merge: "Telephony: Fix network selection array" commit. Has anyone tried 10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
3/10 is running smooth for me with no issues so far. Stock kernel as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Seems like 0310 is messing my phone up just like 0308 did. Falling back to 0307 to see if I get the same issue eventually. Really strange, maybe my eMMC is going out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm on 0310 stock, all fine. Made calls, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah I'm not too sure what's up. 0307 all fine. 0308/09/10 sometimes when I reboot the phone acts as if it was knew, sort of. I get the cyanogenmod account prompt, timezone and location and my launcher select is reset. My frozen apps become thawed. That's the only issue I have, otherwise everything seems to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soccermon15:
If you're using a custom kernel that could be it. I was using KT's kernel and had problems. I switched to stock and my issues went away.

He just barely posted an updated version of the kernel yesterday and it sounds like it's fixed issues for a bunch of people. Haven't tried it yet myself yet, but sounds promising.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Did you have the exact same problem?

Interesting either way. I was indeed using a custom kernel. Will try 0311 with absolute stock and see if all is good. Never would expect something like this to happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soccermon15:
I didn't quite have all the problems you did but I had some of them. It sounds like any custom kernel built/released after the end of last week should be safe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
just wanted to post my two cents...

03/07 CM 11 + 03/07 Quantum Kernel = butter and long battery. At one point today my idle phone in a wifi network was using 1.9% battery / hr. Jumped up to about 4% / hr when i was out and about on nothing but cell data. Test GPS - quick lock, phone calls working from contacts, text working, camera working both front and rear.

I'm staying here until I hear something big happens. Itsh been tough to find a stable d2lte rom!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah it's a pretty good combo. That's what I was using mostly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Link to quantum kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
http://xdaforums.com/showthread.php?t=2390147

[ROM/KERNEL][4.4.2] Quantum 3.54 & QuantumKernel 3/9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mgianni19:
This may be a stupid question, but I'm only seeing Nightlies from February on the Cyan website, where can I find the latest?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soccermon15:
After that, all the GS3 builds were unified. So there's no longer a separate build for just ATT. It's now found under d2lte