yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shiniyoyo:
Really? I haven't gotten around to flash it yet, I'm just going by what's on my brother's nexus 5 :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Remember [MENTION=4258784]MJPollard[/MENTION] I need to know about that dock!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
No problem. I'll install it tomorrow morning, then test it in the dock during my lunch break. I need an excuse to get out of the office for an hour anyway, especially on a Friday. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Smurf colors?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Nice update. Unfortunately I am unable to find a kernel where smartassh3 is stable. V2 was my favorite governor but h3 is pressing my CPU at 100%. Anyone else seeing that? It almost locked up my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Did Supersu come with the kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Oh come on :p

And yeah just noticed it. I'll add v2 in next. I used to love the hell out of it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Just flashed the 3/21 Kernel over 3.64 and it caused my phone to stick at the kernel boot logo. Luckily I still had 3.64 on my phone to reflash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxf250:
Same here. I waited a really really long time and the OS started to come up, very very slowly. Lockscreen (PIN code for me) came on and just sat there - did not accept any touch input at all. Did battery pull and wiped cache/dalvik - all no go. Reinstalled 3.64 and I'm back to where I was. Not sure what's up but Tommy will get it sorted out soon I bet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Dev host dizown
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Really.... I'll put out a fix at some point on Saturday. Go back to an older version as I'll be way too busy for the next few days :(

Whatever, **** it I'll fix it now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ppgregory:
Flashed with no problem. Running SMARTASSH3. Very smooth. Not sure what smurf colors refers to...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pssnn:
Works great for me

I dirty flashed the 3/21 Kernel over 3.64 and everything is working great.

Thanks Pwn!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
For me also, but just got random reboot while opening Tapatalk app. Reverting to 3.64
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Here's an excellent example of why I don't like mirrors. I have to post up a silent update to the old link, all kernels from here on out should be fixed past that boot logo.

http://d-h.st/wzH
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
The original dev host file was updated silently right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yep. If you download past 2:15 you'll never even know.. Dig around and you might find another goodie on my devhost as well...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Lol, Im downloading now.....lemme snoop around a bit :silly:

Yea...I dont see anything different, maybe later??

Wont pass the "Gimme Pwncakes" screen. Had to reflash 3/16 :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
3.65? Goodie goodie!

BTW, 13337 posts...

---------- Post added 21st March 2014 at 12:18 AM ---------- Previous post was 20th March 2014 at 11:22 PM ----------

Gah! So much buttery goodness! I feel like my phone is going to explode with godly powers! OMFG!!!

Another great job Pwn! Honest mass kudos and bowing to thy powers of production!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
See....3.65 that wasn't there before :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dortego63:
Kernel 3.21 working great with AOSB KITKAT 1.3.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Safe to install 3.65?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
So, 3.65 won't boot for me past gimme pwncakes screen until i flashed kernel 3/16.

anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I was able to boot, dirty flash on 3.64.. Was not able to hold until PwN confirms
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Flashed fine for me too. Also a dirty flash over 3.64. Now Pwn post the change log that tells us NEVER FLASH THIS BUILD! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Where does he say that? I haven't seen it.

Anyway, i am on 3.65 with kernel 3/16 and it seems fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
No, just kidding.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Oh..lol...ok [emoji106][emoji5]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well 3.65 is release quality except for those who can't handle the GPU overclock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I'll say it is. Is the GPU overclock the reason I can't boot up with 3.21 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
Is the GPU OC default when you boot up, or is it something you have to enable in trickster? I didn't flash it yet, gonna wait until I get home due to all these bootloops people are having.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Personally, I dislike silent updates. IMHO, if an update has to be made to a piece of software, it should be put out there as a new version number (even if you have to append a letter to it) instead of overwriting an existing release. It's too hard to keep track of things doing it that way, i.e. "okay, you're using the 3/20 release, but which 3/20 release?" This is a bitter lesson that's bitten me on the ass more than once, which is why I never make "stealth updates" anymore. Just a little perspective from someone who's been doing this little dance (professionally and personally) for over 35 years. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
+1

But then again most people use absolutely random versioning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
True, but the logic still applies. It even works with date versioning. For example, if Pwn puts out a kernel dated 3/20 and needs to make a change to solve a critical issue ASAP, the update can be put out as 3/20a. To quote Dennis Miller (before he turned into a giant douche), "That's just my opinion; I could be wrong." ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
The lockscreen boot bug only lasts after the kernel flash. Once the kernel settles it stops. When the screen won't take input, press the power button to kill the screen, then press it again and you're good. May take a few tries. It did it when I first flashed the new kernel. Once I reset nstools I was fine. Phone is butter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gocats7:
How does this battery compare with the stock one when it was new in terms of life,etc? I realize it is stated to be a larger capacity, just curious if your experience backs that up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Facebook

Sorry this is off topic, but I was wondering if Quantum has a Facebook Group. Might be a good idea where people can get together.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Yes like maybe 3/21 A or 3/21 Hotfix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
I flashed 3.65, and I never had a problem booting. No issues what so ever. Still have to try my bt earpeice, but I have no complaints at all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
Flashed 3/21 qk kernel. No problem on boot. No problem to report at all. Going to wait till I get home to flash new rom. And in case it helps I have had excellent results with bt headphones and earpiece both Plantronics.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Dirty flashed 3.64 and the 3/21 kernel (after wiping system, cache, and Dalvik, of course). Booted up just fine, with no issues so far. Pwn, I'll know in about 30 minutes or so whether or not the car dock fixes work. :)

EDIT: Oops, mean to say 3.65. My bad!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'll look into everything when I get back to school today. A few hours of driving lie ahead of me.

Also for those wondering about versions and whatnot, I did it this time simply because it was a minor change. Only 20 people got the earlier version, and it would cause a lot less confused posts. For those who can't boot, try a clean wipe of 3.65 as bad as that is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
I'll make one, if Pwn is interested. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
Tried both dirty flash of 3.65 over 3.64 and clean flash of 3.65.

All tries end up with ROMdb error.

I looked at build.prop and do not see any errors there.

Went back to 3.64 for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BottleB:
Omg page 1337 ...so leet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
Echo during calls - SOLVED

Hi. Not that anyone else is experiencing this problem, but just in case.

Everyone I talked to on my phone experienced an annoying echo. I did a bunch of testing and found a combination that works and wanted to share my results.

Phone: i747M with Telus MK5 bootloader and modem

Quantum 3.54 with included kernel = echo present

Quantum 3.64 with included kernel = echo present

Quantum 3.64 and KT kernel = echo present

Stock Telus 4.3 TW (MK5 root injected) and stock kernel = no echo

Quantum 3.36 with included kernel = no echo (wanted to try pre-d2lte build)

Quantum 3.36 and Quantum 3/21 kernel = no echo

So there you have it. For whatever reason, my phone does not seem to like the d2lte builds. This is an assumption on my part since pre-d2lte Quantum and stock TW do not exhibit the echo problem, while d2lte builds do exhibit the echo (although I only tested two of them). At least I know I can run the latest kernel with the older build and not be subject to the annoying echo.

Take this for what it's worth. Just sharing my experience. I'm glad I found a combination that works so I can stick with Quantum. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I think everyone in the world has had issues with the d2lte builds. They were kind of a step down from the d2att builds and we're still not back to where we were. Thanks for all the testing though, maybe more people have this issue but aren't aware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
It is a strange issue because the echo is on the other end, not mine. The only way anyone would be aware is if the person on the other end complained (guess I talk to a lot of complainers :p). I'll stick with the d2att build and the current kernel. So far so good with that configuration.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
On the intelliactive governor, which tunable value will the cpu go to first? The up_threshold_any cpu or the hispeed load?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Downloaded 3.65 rom and 3/21 kernel from Dev-Host. Can i flash both, or just the kernel?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Just flash 3.65. 3/21 is included
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
Hi just wanted to report that I dirty-flashed 3.65 over 3.64 without any problem.

Flashed in that order:

Cache/Dalvik Cache Wipe

+

Quantum 3.65

PA Gapps Modular (03/21 package)

Quantum Kernel 3/21 (just to be sure)

Trickster_reset (to reset back Trickster MOD to its default settings)

VM_Dalvik (thanks polobunny, to set back Dalvik as the default Runtime)

Xposed_toggle (to enable Xposed framework automatically upon reboot)

+

Cache/Dalvik Cache Wipe again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Never did it like that before. I'll give it a try. Thanks:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4b3ck:
Made dirty flash 3.65 over 3.6:

1. Wipe - system/cache/dalvik cache

2. Flash - 3.65

3. Flash - 0Day mini modular gapps 3/21

4. Reboot

5. Trickster Mod - I/O(384/BFQ), Intelliactive, undervolting -100 across.

6. Xposed/Greenify/Tasker

7. Viper4Android

8. Google+ - disable notifications

9. Reboot

Thanks to Pwn for awesome rom!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
where is 3.65? not in the OP and I searched back and just found the 3.21 kernel.

any help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Re: Car dock issues

Good news: the 3/21 kernel does indeed fix the issue of car dock mode not working. After dirty flashing 3.65 and the 3/21 kernel (just in case), I plugged my phone into my iBolt car dock during lunch. Car dock mode was enabled (the steering wheel appeared in the status bar), and Car Home Ultra started... eventually. More on that in a second.

To date, there are still two issues with Quantum (and, I'm assuming by extension, all CM 11-based ROMs) regarding dock functionality:

All audio output is still routed through the dock automatically, and there does not seem to be a way to turn this off. There is a setting in the Sound tab of Advanced Settings (which, as we know, can now only be accessed by creating a shortcut) to "use dock USB audio," but changing this setting does nothing about this issue. Bluetooth does not appear to be a factor here; in fact, I can hear Google Navigator through my car speakers when I'm on a call (so system audio must be routed through Bluetooth). This is a huge ****-up from the 10.0 days, when dock audio wasn't enabled unless you selected it, and still frustrates me no end.

Car Home Ultra (or whatever your car app happens to be) sometimes takes forever and a day to start up after plugging the phone into the dock. I timed it today, and it took around 15 seconds to appear. (By contrast, it used to appear almost immediately under 10.2.) It's annoying but not crucial, as I can just press the home button and CHU will then start, but having this fixed would be nice.

Note that I don't know where these issues actually lay, not having the detailed knowledge of Android's innards like you have. The 3/21 kernel fixed the big one, so at least I can now stay on 3.65 (kudos!) and keep my car dock functionality. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4b3ck:
Look here: http://d-h.st/users/TommyTarts/?fld_id=33215#files :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
When I dirty flash I don't wipe system. I find it causes problems. If you already have gapps, you can flash a newer gapps? I remember once reading you shouldn't do that. I've never had an issue dirty flashing without formatting system. Seems to be an extra step that tends to nuke the gapps on the phone. It also nukes Nova Launcher when I wipe system, so I just stopped doing it and have had no issue. About once a month, I do a fresh install and just restore with TiBu. Pain in the butt though. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
A flash isn't really a dirty flash anymore if you wipe system. It doesn't cause problem, but it obviously wipe system apps, which include gapps and whatnot.

But sure, you can go ahead and dirty flash gapps on top of it, but why would you? If you keep your apps up to date in the Play Store, including your gapps there, there's no real reason to manually flash gapps past the first install of them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4b3ck:
Maybe next time I should try that... but now as usual I wiped system... yes of course it's nuke gapps too so I installed latest gapps, hmm yeah nova Launcher... after install it's just popup which launcher I want to use.. I am choosing :p .. Nova and that's it it's holds all my customization's.

I am not doing fresh install looooooong time.... even I tried Carbon rom and switched back without any problem. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You can usually get through doing dirty flashes as long as you don't change rom base. Jumping from CM to Quantum or any other CM based rom you'll be fine. Jumping from CM to TW you'll end up wanting to kill yourself, if it even works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] biggem001:
Hmm well I'm assuming you're on the new BL. I'd do a full wipe, factory reset + system. Install goes like this for me:

factory reset > system wipe > install Rom > install gapps > wipe davlic > run

i had considerable more issues earlier roms. And are you using Pandora by chance... I had version 4.5 and it made me want to kill my phone by how much it broke the bluetooth. I use version 4.1.2 without problems now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Newest youtube update is out for anyone interested :D

I just installed via a file manager and that's it. Didn't have to uninstall older version / updates or anything.

The UI received a nice update, so I suggest you guys check it out

http://www.androidpolice.com/2013/08/19/download-youtube-for-android-v5-0-21/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x0ne215:
Not so much bluetooth not working for me, works great in my friends Jetta, but once turned on it won't turn off unless you reboot the phone (at least for me). But nbd hardly ever use it (I use an aux cord in my car)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
I had that problem on first version of ROM, I found out if I turn off the other devices Bluetooth first than the phones it works fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I'm going to try that the next time I'm in my car and using the built-in Bluetooth system.

(The annoying part is that Bluetooth worked perfectly [for me] in CM 10.0, which is what I was using before moving up to Quantum. Presumably, something changed between 10.0 and 10.2 that made Bluetooth go all wonky...)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Ditto...So far anyway. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
Phone dialer has dissapeared on the main screen.. How do i add it back? I tried searching but not relevant came up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juannicolas:
Apps drawer perhaps...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
CNAP

I hate to ask for features but do you know if its possible to implement CNAP (name display) into the ROM?

It use to work on 4.2.2 based on this commit - http://review.cyanogenmod.org/#/c/22590/

I'm not sure if its portable into 4.3 or if CM hasn't added it yet? Great ROM BTW!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
I've set up root in the developer options but seems like some things won't work. For example i can't edit and save build.prop

Any idea what's going on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Did you select apps and adb for root access?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
Yes i did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Are you using a build.prop editor to edit the file?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
Ya it use to always work before i updated with total commandwe. I came from cm 10.1stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x0ne215:
Try just using a file explorer such as ES File Explorer or Root explorer, and making the changes from there. Just wondering, what do you need to change the build prop for? The only thing that comes to mind for me would be Google wallet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Crazy hot battery on the car charger. The kernel needs some kind of a temperature control all dip for fast charge off the cigarette lighter adapter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x0ne215:
Not sure if I'm reading that correctly, but if you have fast charge on that would make sense why it's so hot. Also ANY type of casing in my experience causes this. Or if it's incredibly hot out, that too (I hate the NE in the summer)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
The ROM does have temperature control you just need to enable it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
I change a few things so i can view bell tv

Edit: well it seems to work with root explorer.. Strange though since it use to work with total commander prior to updating to 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
.... can i buy a vowel? Googling CyanogenMod Temperature Control isn't helping and I can't find it in the settings. Do | need to install a tweaking tool or set this from the terminal window?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4b3ck:
So, wiping system == fresh install??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Wiping system + data is a fresh install. But wiping any of the two isn't the usual "dirty flash" people talk about haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Just about. You'll lose any tweaks, such as host file alterations (from apps like AdAway) and Xposed Framework (just reinstall it and you'll be back up and running again), but your apps and data will remain intact. Me, I always wipe system (along with cache and Dalvik) every time I install a new version of a ROM, just to make sure that any leftover crud is wiped away. The handful of tweaks I have to redo afterward is nothing compared to reinstalling all my apps after a full system wipe!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
can I flash the 3/21 kernel with the 3.27 build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Sure. Until I upgraded to 3.65, I used the latest kernels with the 3.36 build, no problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
Thx, Just making sure. I had tried some of the builds past this one, even 3.36 and had issues like FC's and battery drain so I went back to 3.27.

Maybe I'll give 3.64 a try this weekend to see how it goes.If it doesn't back to 3.27 and try the new kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
i just flashed 03/21 kernel on 3.63 and it froze at boot screen :o but went back to 3.63 and all is working. very odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
3.21 kernel on slim kat touch screen Didnt work on initial boot and then would only boot to splash screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Who the hell wants TouchWiz? :p. I flashed that dirt just to fix lte. It was on my phone for 2 minutes.

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Once you get past the ugliness (and by past, I mean when you theme the heck out of it) and you remove all the apps you don't need it's pretty much the most stable rom you'll ever have on the S3. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
I agree TouchWiz sucks IMO. It's slow and a resource hog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BottleB:
Only reason I'd use touchwiz is for easier support for my galaxy gear and having working avrcp metadata for car radio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
I'm not very happy with this but... Gotta agree.

It's slow, it's ugly, it's not gentle on the battery, but... camera, bluetooth, NFC, GPS, name it... they all work! No tweaking required, it simply works as it should :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
3/21 took forever but booted past splash, all the way to lock screen on latest Slimkat. But touchscreen was nonresponsive, had to hard reboot to recovery and restore backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I wasn't super happy with it either but with a few Xposed modules it acts pretty much like CM-ish. S3Rx makes it easier to CM-ify the whole experience. Anyway, enough off-topic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sirdizzle415:
same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnknownTroll1:
Has the LTE been fixed yet?

I am like versions behind and decided to update. Are the LTE bugs worked out where it would drop LTE peridoically?