yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Cool. :cool: Is 3.6 still based on d2lte? I'm going to give it a spin to see if the car dock issue has been magically fixed (as soon as I get my car back from the collision shop, that is). If it's still present, then it's back to 3.36 for me. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It is :( d2att is essentially dead :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Ah. :( Not unexpected, I have to admit. Best thing now is to soldier on and try to make it work, I guess. Let's hope that this does the trick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Sucks for your car gramps, where did your reaction time go? Hehehe. My little tyke is crash proof. :p

It's all jokes, I like all you guys. Will try the new build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
What is the Android 4.4.3 fix ?

3.6 running Butter here :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
LOL, actually, mine came through mostly intact (I have a 2013 Dodge Dart), just some front-end damage. Someone turned left right in front of me; I had almost no time to react. I managed to slow down enough to avoid major-league damage, but my anti-lock brakes prevented me from stopping completely. If it weren't for them, ironically, I might have been able to stop within inches of the other car. But, since drivers turning left are required to yield to oncoming traffic, the other driver is technically at fault, which means I stand a pretty good chance of getting my deductible back from his insurance company. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the.teejster:
I'm curious to know how flashing STOCK resolves LTE issues.

I am using the latest bootloader / modem from Bell. How did I get / install them ?

In my situation, I reverted to stock 4.1.2 (flashed full sammobile stock image) so I got the official 4.3 OTA update (for Bell). I wanted to do this to ensure I got the correct modem and bootloader to avoid any potential issues.

I am aware that a number of people flashed modems / bootloaders that were downloaded from XDA or elsewhere which may / may not have been official releases.

In my case, since I got the latest and great modem / bootloader OTA, how will re-flashing stock resolve the LTE issue (my LTE is fine but I DO have to toggle the LTE quick tile on boot to get it to stick). ??

I did a nandroid backup of my stock 4.3.1 rooted OTA build. Would simply restoring that and then reinstalling ROM resolve LTE not sticking ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Glad to hear you got minimal damage on your car. The Dart is a nice little thing, really dig the look of it (especially the 2L turbo model).

And yeah I guess it's kinda ironic about the ABS, but then again it saves many people who can't pump the brakes and turn at the same time instead of slamming on them and being unable to turn haha. Good look with the deductible too, those things suck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Yeah, the look is part of what attracted me to it (I have a silver Limited [non-turbo, alas] with all the techie-techie trimmings), but the thing I liked the most was the great gas mileage, especially when compared to my old Oldsmobile Alero. :D

LOL, yeah, overall I have absolutely no problem with having the ABS. It's just the rare instances like this that make me wish otherwise. (I also wish I'd had the presence of mind at the time to yank the emergency brake, but you don't think of those things when you only have half a second to react.)

Yeah, and it's a nice chunk of change, too (deliberately, to keep my payments reasonable). Fortunately, my insurance company (Progressive) is handling all the details about getting reimbursement from the other driver's insurance company, so I just have to sit back and get status reports on their progress. It'll probably take a while, too, as I'm sure the other insurance company will fight tooth and nail... *sigh*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VanGool:
Is the new 3.6 better than what the 3.36 used to be?

Im currently using 3.36 with 3.9 kernel, is it worth to upgrade or should I just wait for the bugs to be fixed?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I don't know, flash it and tell us. All the bugs are able to be fixed already
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Hopefully this will be my last noob question I'll post ever, but I'm going to flash stock TW that has the LK3 baseband and I am on the MJ2 now. Will that brick my phone when I Odin back to stock tonight?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Baseband does not equal Bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
It depends on your bootloader:

If you are on MJB, DO NOT FLASH LK3, YOU WILL BRICK YOUR PHONE!

If you are on MJ2 bootloader, you are safe to flash back to LK3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
To add to what scorpionhd2 said, baseband is NOT bootloader. Baseband is modem. Downgrading modem won't brick anything, downgrading bootloader will!

Edit: Dang Pwn, didn't see your post. Beaten.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Guess I should have also added that my bootloader is MJ2 as well. So I guess I'll be fine?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Casadisole:
Can this be dirty flashed over 3.54?

+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
Some people that have flashed previous LTE builds have been having trouble with LTE (one being the simple one you have).

It seems flashing back to a stock ROM clears up something messed up with the old LTE builds.

[MENTION=1683096]PwnCakes193[/MENTION] mentions if you have not installed an old LTE build you can go straight to this build.

If you have not had trouble with previous builds of LTE you can flash over it, but if you have troubles with LTE don't mention it here, just go back to stock and try 3.6 again.

The subtle message is do not talk about LTE issues unless you have gone to stock and then done a clean install of 3.6 to see if that clears it up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Read.

God you guys make me feel horrible, but I mean seriously learn to search!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
You da man!!

Now i Have something to do during this 2hr meeting. Lol!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Yes, you are safe to flash lk3 if you are on mj2 bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
whoops
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Read before you ask a question. And search

Do NOT answer another question about the bootloader or the LTE issue for ANYONE. Let them search

Unless you have a brand new question that hasn't been answered, then don't ask it! Simple as that. You are not unique. Directions have been posted over 10 times.

ONLY 3.6 DISCUSSION FROM HERE ON OUT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I figured I would be but wanted to check with the brain trust.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
3.6 discussion time!!!

Got a few Exchange Service force closes during CM setup, as well as one com.android.phone force close, but that's all. Currently restoring via TiBu/putting all my stuff from my internal SD back on my phone, I'll play with my kernel settings and give you a verdict on performance.

No service drops so far! Amazing. LTE stuck!!! Double amazing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the.teejster:
I'll be damned... It worked !!

I did a Nandroid of my current 4.4.2 rom (with LTE not sticking), restored my Nandroid of Stock 4.3, booted it up and it went right into LTE.

I then restored my current 4.4.2 rom and it boots right into LTE everytime !!

Thank you ! (love the new Kernel BTW (3/7+) !!! getting wicked battery life... 3+ days on standby)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Which gapps? No problem here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
I think the 3/7 stock package. It didn't come back after the first two, so it might have just been a weird boot thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sewermike:
Dude... I hate to say it, but I can clearly understand why Task650 runs his thread the way he does. >>>"""READING""" <<< the last 10 pages... WOW, people are STUPID.....

Thanks to you and all the senior members here, for your patients, time and efforts.

:silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kaflex:
I wouldn't say stupid, more like being lazy, they don't read before they post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Definitely not stupid, just lazy. Even though it's frustrating, let's please please *please* not let this thread turn into a Task thread. We're better than that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
There's a point where everything reaches some ridiculous level, and we surpassed that earlier today and I had to end it. I love seeing new posts, but not ones that are completely unnecessary. I never understood how people never used search. I was using it when I was 11 on the Nintendo NSider forums.

I have no problem helping with issues, but not helping with the same issue a hundred times in one hour, when literally 99 could be fixed by just reading a little.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Found flashing the new ROM has fixed my issues with screen randomly turning off

Edit- Looks like problem is still persistant
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sewermike:
I agree... I do not wish to see this become a task style thread either. He`s at the extreme end and his development thread does not come across as very welcoming, unless you spend time and read the pages that are there. Then you will get all the info you need on your own without having to ask anything.

Just very fustrating seeing people asking the same questions over and over and over and over in the last 10 pages....... :eek:

maybe stupid was harsh, but where I work and come from, being lazy by not taking initiative to learn something on your own by researching it, constitutes stupidity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Couple of odd deals:

Install route was stock - 3.36 -> 3.6

scrolling seems to be 'jumpy' and when you lift your finger, it 'jumps' a little further down extra

maps isn't working - map not loading

yahoo weather on the lock screen isn't getting the location

SwiftKey keyboard fc's

ROMdb dev tool reports 'isn't configured correctly'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
SwiftKey Beta works like a charm with me, try clearing data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4b3ck:
Dirty flashed from 3.5:

- scroll behaves normal way

- maps works correctly

- ROMdb reports that not configured correctly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Oh damnit. Just disable RomDB. I derped up actually :/

You can go into build prop and go to the bottom, just make ro.romdb.hash it's own line :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
I dirty flashed and gapps got nuked. Clean flashed and 3.6 is looking sweet so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
You mean add a new property name? If so, what value should be specified for ro.romdb.hash?

I see there is a ro.romdb.version with a value of 30.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I just use Titanium Backup to freeze ROMdb. When one reads this thread religiously, one does not need ROMdb. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4b3ck:
hahah ... I should count how many times I refresh tab on chrome per day :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
I think my F5 key is about to break... :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
flashed stock as instructed for the last 50 pages and flashed 3.6, everything is running very smooth LTE is working great!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Yup. I'd pay to know what that Cm11 broke. I've been butter. 3.6 is looking tight. Phone is lightning fast. If Pwn retires I'll go back to my Captivate!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
I've never used it since it downloaded mobiegenie apk with quantum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Meh. I check the thread enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I fixed it in the link, so nobody should experience it going further. It's a simple fix to be completely honest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
As instructed, I like that!

I put my apk files in the sys/app folder and deleted Romdev. Flashed 3.6, su, volume blaster, gapps and wiped cache. Flashed my inverts and booted into the goodness. Zero fc and it's lightning fast. Swift works flawless. I'm gonna insert a Sim after dinner.

Way to go pwn. I'll try to dig something up for you soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
I edited the line. Still doesn't work. Perhaps I'm dumb.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
My apologies. Just took some time after reboot. Works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
Did a flash back to my rooted stock TW 4.1.2 Let it set in for about 10 minutes. Went right to LTE. Started up CWM, complete clean install of 3.6, gapps and reboot. Started up got LTE right away. Ran my TiBu and all is running well. PWN you are the man. THANKS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
New kernel incoming!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Thank you so much! :D What's planned?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mojar7070:
Shamefully edited....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksd316:
I agree on the laziness being annoying. I basically read this thread two or three times a day, more if there has been a really recent update. My wife drives me crazy sometimes asking me questions about **** and I'm just like, "You have Google at your fingertips, someone has asked this question before you, I guarantee it" :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
CM sync and that's about it.

http://www.google.com/url?q=http://...sntz=1&usg=AFQjCNEtqBOzCM9oX5ue2qpDGFWTnb4wsQ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Awesome!:D

Just wondering, what does CM sync do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It just means I update my kernel in line with what CyanogenMod has merged in their kernel. It's basically just making sure everything is up to date!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Just another merge to keep us up to date with CM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
After spending about 3 hours on my whole revert-to-stock extravaganza, I'll wait until tomorrow to flash this. If I have to flash one more thing I'm gonna be sick xP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Thanks for the update Pwn!!! Slick azz rom!

Just wondering....is instagram video crashing y'alls phones?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btafoya:
So far all is great! Fantastic ROM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Mine takes me about 15 minutes :/

ODIN or in my case zip

Boot, then open maps and get a GPS lock, then reboot

Reboot again into download mode

Flash TWRP

Install Quantum

Shouldn't take long at all!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
This kernel has been amazing for the past few days for me running slimkat for sprint.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
Ohh boy, lemme tell ya...

After gathering everything (and I mean EVERYTHING), the MD5 of the stock ROM was screwed up. So, I had to redownload, re-extract the MD5, and see if it worked then (it didn't). Took me a while to realize that WinRAR doesn't play nice with .7z files, so I had to extract it with 7zip. After that mess, the Samsung bootlogo wouldn't go away. I realized I forgot to factory reset, went into the stock recovery and did that. After half an hour, I finally got to 4.1.1 TW. 5 or so minutes to flash CF-Auto-Root and CWM. The next 15 minutes were sideloading everything I needed onto my phone (there was more than I had anticipated), then another 15-20 minutes to let everything restore via TiBu. It was a blast, lemme tell ya... :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
is it me or is the google dialer still not behaving correctly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btafoya:
Is this supposed issue related to Samsung devices and the modem an issue with this ROM? Or is this just BS?

http://mobile.slashdot.org/story/14...utm_source=rss1.0mainlinkanon&utm_medium=feed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] natefish:
I wish I could report the good results others are having, but I can't get Play Store to connect on 3.6. Keep getting a request timeout error. I tried three different versions of the latest gapps. I even tried going back to 3.54, but now that won't even let me connect to the store. Never seen anything like it. I've cleared all the usual caches and stuff. What the heck is going on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
I've had that issue before, did you reboot? That's probably a silly question but it happened a bunch of times with me and a simple reboot fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
What's everyone's experience with the camera in 3.6? It keeps crashing for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Doesn't affect us as we don't use that blob!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
Seems related to ART. The problem was gone for me after I switched back from ART to Dalvik

I can reproduce the problem at will by enabling ART

Sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Honestly right now ART is slower than Dalvik, AND it uses a little more battery life. Everything is optimized for dalvik.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BottleB:
This definatley did the trick for me. Was about to give up!

Thanks for sharing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Thanks.... but cra*p... just hit reboot after enabling art.. and right before seeing pwn's post right after yours... :p that was after a line of odin's / reflashing etc to get everything set backup. I was just about to test it since I had the problem again after going directly from lk3 -> mj2/mjb -> 3.6 and then switching to art right away. Well... after about 20 minutes or so when it's finished building the art complex, I'll switch it back! I'll check when it's done, but I bet that's why the map was screwed up also. *Confirmed*

--

Why don't you flash the pre-rooted stock? :confused:

Anyways, when it's stuck at that samsung logo you should have adb access anyways so do the: adb reboot recovery then go into wipe the sdcard (in cwm mounts/storage - format data/media (something like that that formats the sdcard).

I've reflashed stock via odin about 5 times in the last 24h, so it's really not that bad. But, when you go back to stock TW, you should go into the 3e recovery and do a factory reset. Then after you push the new recovery, wipe it again. Just be careful and don't format/sdcard 1 like I did one time... :crying:

Hey [MENTION=1683096]PwnCakes193[/MENTION] - what route did you take to odin twrp? I'd love an easy way to push cwm or twrp that way without worrying about mmclbk typos
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I have frozen it before, when it was causing issues way back when....I just like all things to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
I installed Quantum 3.6 (did a clean install) tonight but, I now have a wakelock which I didn't have with Quantum 3.54. I'll have to investigate with BetterBatteryStats
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Harshpatil:
Camera working here. Try clearing data of camera or/and use 3rd party launcher like nova. Using GNL crashes camera for me.

---------- Post added at 10:30 AM ---------- Previous post was at 10:27 AM ----------

I am having a wierd sound skip glitch right after I lock my screen while playing music. Same happens when changing track using volume controls. Never happened before on 3.54. I am on stock kernel no voltage changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] natefish:
Yes. That would have been part of wiping the cache. Thanks, though :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I would like to thank [MENTION=1683096]PwnCakes193[/MENTION]. Flashing stock Touchwiz did indeed restore my LTE. It looks like some of the nightly builds from the beginning of March corrupted the NV ram in some d2att's. Unfortunately CyanogenMod does not reset the nv like stock does (believe me we would be setting it if we knew how). If you don't want to flash stock and you have an nv backup you could try to restore it as an alternative (although this just led to bootloops on cm for me)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I can confirm that mine crashed also. I cleared cache for camera in settings>apps and then reboot. That fixed it. Snap a photo, switch to video WITH a snapshot during the video, and back to cam. All's well!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Ahhhh I'm having bluetooth issues. As soon as my phone connects to the car radio, it freezes.

After restarting the phone, bluetooth starts working.

Weird. Anyone else experiencing this issue?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Dirty flashed 3.6 over 3.54, then kernel 3.13. GPS fix in under 3 seconds, no FCs, reboots, unexpected loss of LTE or other weirdness thus far. Haven't flashed stock in months...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
I'm curious to see if a factory reset in 3e recovery would accomplish the same without having to go through flashing back to stock. Once upon a time, I had an error with a task rom that was only solved after a factory reset with 3e. Even odin back to stock didn't fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Internet:
On 3.6 and it is working flawlessly thus far. Pwn, you are a beast. I was on 3.54 and here is how I got to 3.6

I had LTE problem so I flashed prerooted stock 4.1.1 (came with I747UCDLK3 bootloader) with ODIN.

Got LTE right away, but GPS wouldn't lock so I went through NV Backup reset process and GPS locked immediately afterwards.

Flashed MG2 bootloader (staying away from MJB since I've no need to jump to it).

Used ROM Manager to flash CM 6.0.4.7 touch.

Flashed 3.6, latest GAPPS, and Volume Blaster Light.

Switched to ART after bootup, but noticed that menus were "jumpy" and for whatever reason Google Maps would not display map at all. Switched back to Dalvik and all is great.

This was just my road to 3.6. Didn't take too long.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brokeddid It:
Haven't had a chance to run 3.6 thorough the gammit. Working a 24hr EMS shift with phone idle except for a couple calls. Still not bad battery for a completely fresh install. 16 1/2 hrs with only 5% lost. I'm usually around 50 or less in same time frame on a settled set up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corey103:
This is strange. I flashed in 3.6. It was fine for a day until I rebooted it. It suddenly locked me into a boot loop. It was weird, so I restored back to 3.4. I might be a rare case, but has anyone else had that problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
FWIW -

3.36 with ART, intelliactive, deadline, performance mode:

3.6, Dalvik, intelliactive, deadline, performance mode