yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Since you have pro, best bet I think would be to create 2 filters in Titanium. Something like "Data" and "NoData" and just run each one. Requires 2 separate restore actions, but still relatively automated and quick.

Edit: Something like Tasker would probably even let you turn it all into one button press.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Not mine. I'll continue to rock my GS3 until it can't be updated anymore. I've never been one of those who get the itch to change phones every two weeks. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
Same here! This phone does everything I want, so I have no big need to upgrade. I ran the original GS for almost 4 years I believe before upgrading! I'm planning on doing the same with this one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
My apartment gets a ton of dust. Get a small vac that blows out so you don't suck up parts, or buy some canned air.

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chinmonkie:
Updated Kernel?

Whats the latest update on the Quantum Kernel, is it not 3/26? Or is there is 3/29 an official kernel update or just in beta right now? *just slightly confused*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
I wouldn't use any kernel after 3.28. Some things are broken after this one. Currently on 3.66 rom with 3.28 kernel. Running flawless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
In 3.67, getting a fc whenever I try to go into display and light. 3-30 kernel.

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
I am not using Nova launcher, what I showed was Google Maps. It only happens in Google Maps. Can't see much of anything to be honest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I upgrade every two years, which is the length of my contract. One phone at a time, which is all that i can afford.:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I crapped my phone twice for the greater good of Quantum.

Display and lights on Quantum 3.62 with Kernel 3/16 is good.

Display and lights on Quantum 3.62 with Kernel 3/30 crashes.

Safe to assume its a Kernel issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
It is silly not to update whenever you can. You're paying the same monthly rate whether you have a new phone or not. It'd make sense to always update to a newer phone whenever possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
if its just maps you might delete the apk from system and data/apps and reflash gapps, or try to uninstall and get it from the playstore. I'm about out of ideas before formatting the system and reflashing ROM and gaps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
"If it ain't broke, don't fix it." Why should I pay money for a new phone every two years when the phone I have is still one of the best you can buy? Especially when it's broken in and running just the way I like it. To quote Geordi LaForge, "Just because something's old doesn't mean you throw it away." ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbrian27:
I know someone mentioned an issue a few pages back with Netflix where 3/4 of the screen is gray. I'm having the same issue on 3.66 w/ 3/29 kernel. I've tried to find out how to get it to work - searched on here and Google, but found nothing. Is there a workaround or fix for it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I don't throw it away. I do a factory reset, and then sell it on eBay. I'm a retired Postal worker, who lives on a fixed income.:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
BlackNetflix.Apk (I think it's a team black out app) does the same thing on Quantum 3.67.

I was hoping to install, say it worked, and point you to a fix.... But I guess it's just another app that I can live without.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
How come I can't go below 700mv? It resets back to 700 if I go for example 650... My phone can handle it but trickster won't let me go down that road.

How do I change GPU voltages?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rescue9:
I installed xposed and the Netflix workaround. The workaround is listed as a 10.1(10.2) fix, but works fine.

Galaxy Note 10.1 - CM 10.2. Tapatalk Pro.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chinmonkie:
do you notice a difference between 3.26 and 3.28? (open question for anyone really)

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

heheh mad props on the star trek reference :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
People don't just say "I have a reboot" or "X isn't working" or other things without providing information. I'm not going Task650 mode, just saying to make Pwncakes life easier. Heres a tutorial on how to get proper info when something happens.

http://xdaforums.com/showthread.php?t=1520508
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
Installed the newest update dirty. No random reboots, but can confirm display and lights settings broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
If I remember correctly, Pwn sets his Kernel's bare minimum voltage limit at 700. Therefore, try as you might, you will not be able to UV below that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonesj8:
I can also confirm 3.67 display settings are broken. Other than that stellar ROM and kernel love your work. Anyway we can get the advanced settings put back in the ROM and accessible through the menu or interface settings? Just miss that feature and I'm sure a lot of others do as well. If anyone else agrees please thank this post to show pwn who all would like that feature back. Again best ROM I've had in a long time and don't plan on switching ever ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
I have formatted completely, reinstalled gapps several times and nothing. Even formatted internal and SD card. Only time it wasn't like that is when I went back to complete stock. I'll try deleting the apk this time, see if that might do it.

EDIT: Used ES File explorer to remove apk and reinstalled from store and its beautiful again! Thanks for the sugg!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yeah the limit is at 700.

And for those busing 3.67 remember that its not releasee yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
care to share how we can lower past with a init.d hack or could you release with min lower than 700? :D I would really like to see how far I can go lol. 700 at 486Mhz works for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Happy it worked out..... Was beginning to have me stumped
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
If you use the 3.66 and the 3 / 28 kernel you will have your display settings back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ShinyBuddha:
Just setup Pro to do a selective backup and +1 on Tasker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Originally Posted by btafoya View Post

So I am a little OT but hope someone here has a great suggestion. Anyone figure out a script/process of backing up and restoring apps? I currently use Titanium Backup Pro but spend a great deal of time on the restore telling the app which apps to restore with or without data. I am a programmer and would gladly use a script or aroma type scenario if there is one. Any suggestions appreciated!

this might not be what you are after and has no option for restoring data. but I am happy to share with you what I do for each clean install.

using winzip I open the rom and navigate to sys/app. this way I am able to delete any apps I know I don't want and drag my apk files here. It doesn't work with apps that install a framework, but has made my clean installs so much faster! there are only a few apps I need from the playstore and its a quick and easy. I have heard a ton of good stuff about titanium backup, but I never took the time use it- from what I recal backing up takes a while and I'd imagine restoring does too.

If what you are suggesting is creating an aroma installer with your apps please shoot me a PM, I would love to give this a try too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] allrockedout:
Thanks for this, I use nandroid backup from the play store
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Since we are on the topic I am hoping that there may be an easier way for me to speed up my clean installs.

The problem I find is that I can either use Google restore which will give me a lot of my system settings but will require me to manually restore the data for apps that it restores.

Alternatively I can use titanium to do a batch restore of my apps with data but then I have to manually do my system settings.

I am thinking maybe I should let Google restore my settings then go into airplane mode and use titanium to restore my apps!

Tapped it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
That's the way I'd do it if I were to clean install, but I have tried something similar before. Just watch which user apps are installed as system. You might run into a snag. It's happened to me before
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] weedolo9y:
Reechings just use zipme from the app store ... Pick what apps you want to keep zip them together then after you install new ROM and gapps install the zip you made first boot boom you have everything already there. Best way to do it I'm my opinion
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Going below 1000mv on 1458mhz causes immediate L1 cache corruption which causes a kernel panic boomboom reboot.

I'm on 700mv on 386mhz right now, stable as a motherf*cker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
I'm at 1065mV @ 1458.. Never clocked past 1.3ghz anyway.

I was hoping to see how much lower I can go with 486mhz - voltage side, which I can push to 700mV atm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonesj8:
Any reason why zram feature isn't working on a clean install. Using 3.66 and 3/28 kernel? I've had it working before but every time I try to set it with trickster it turns right back off. The setting won't stick. Also what is everyone's preference on the core limiting feature ex. 0,1,2 for least to most aggressive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Pretty sure I disabled it :) Not necessary on a 2GB of RAM device like ours at all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Agreed 101%

Currently on stock cm kernel, I miss the GPU overclock ha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonesj8:
What about everyone's preference on the multi core power save mode. Which option does everyone choose. I personally use 0 because I feel that taking advantage of both cores is better for multitasking and battery life, unless someone can correct me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
3/30 kernel has settings fc when choosing display options in settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Yeeaaaaaa.......its been noted quite a bit a few pages back.

Also don't forget, its still a "test release" really, not official yet. Hopefully Pwn will be able to get to it today as he stated. If not, we will wait like good little boys. [emoji106]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
[MENTION=1683096]PwnCakes193[/MENTION] If it helps, I flashed Kernel 3/16 on Quantum 3.67 and Display and Lights worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yeah it fixes it for that, but fr some reason it won't fix it on anything else I've made since then. I have no idea what's going on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Do you want me to test kernels after 3/16 just see where it breaks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
3.67 with 3-28 kernel is running nicely for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
Ok I went to the play store to find this app and 2 of them popped up. I'm almost certain it's the JRummy app but I want to make sure. Could you possibly say for sure if it will install the data as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Don't forget, for some of us, 3/28 didn't work. We got 5-10 minute boot time and no response on the touch screen with it. Since my phone is the strangest around, I offered to keep testing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
I remembered the issue but forgot which kernel caused it. When 3-30 caused the fc's in settings, I just rolled back to 3-28. I have faith that Pwn will get it sorted though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Actually, the problem started I believe around the test versions of 3/23. But i tried 3/16 for the hell of it. I can try the others if Pwn needs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Never undervolting to more than 50mv... It causes massive battery drain, most probably due to hardware not receiving enough power and hanging too long on a single task, thus causing drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Your phone will be a good test bed, that's for sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
I wonder what overvolting does...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Try this and tell me if it still FC's

http://d-h.st/bLG
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Flashed it and display settings still force closes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Anyone on 3.67 notice how if you change your ring mode to mute on the power menu then to normal the notifications are at 0 volume and ringtone is really low?

Never mind, just remembered 3.67 isn't officially released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Someone needs to try 3/31 on anything else and tell me if they still get an FC. No idea why it's still doing that at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brobinson2102:
Still force closing.

Back to the S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Is it possible to downgrade to 3.66 and only wipe cache, dalvik and system because I'm encountering issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Mine works fine.

+1 confirmation

Maybe this can help?

https://www.dropbox.com/s/yl61f9bezc5kiqt/Display Crash.txt

Last time I tried to down flash from 3.67 (last night), to any version, I had to clean flash because lock screen, volume, home button stopped working and that was the only way to fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
No issues on Slimkat 4 for Sprint.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
GPS...yes, still

Ok so I did find something quite a bit different from complete stock to this ROM and Slim. In GPS status & Toolbox on the two custom ROMs I get around 9-11 sats out of 20-23.

Now on complete stock 4.1.1, quite a big difference, I got 18-22 sats out of 23-26. Not to mention the lock time differences are huge across the board. GPS status locks almost instantly on stock, whereas with the custom ROM's they took a considerable amount of time, greater than 45 seconds!

Is this a CM thing? Any ideas? Sorry I keep bringing up the GPS, but I really like this ROM and would like to continue benefiting from the other parts of the ROM that are so great!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
3/31 gives fc on display settings with 3.66. Hardware V7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Are you sure that's the one you're using? I can't believe this is happening.

Someone flash 3/31 on the latest CM nightly and tell me if this stupid **** ****ing FC's. I'm out of this thread and with all this other stuff until this settings FC is through. Nothing is fixing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
FC on display settings on CM nightly 20140331. Also got a FC on CallRecorder (which I never get usually). Other things might be FCing.

Brb with logcat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I give up :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T_D_H:
LOL looks like you are having tons of fun, I started getting random reboots after upgrading to 3.66, downgraded to 3.64, now only reboots during charging randomly some days, I'm gonna do a titanium backup, do a hard wipe of everything just because, check TWRP for any updates, do everything twice and report back with logcats if I must, I know this post tells you nothing, but I havent posted in a while and holy crap this thread fills fast and I cant keep up. So for now consider this just a bookmark for me :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I'm still on 3.65 with the 3/21 kernel, and I'm afraid to upgrade and possibly ruin a setup that's been working perfectly so far. I'll just keep my eye on things and see how they shake out. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Try the latest kernel and see if it FC's settings. You're pretty far back, do it before I go haywire :) It has a ROM and kernel component, and I completely removed the kernel component. Don't know why it's happening on anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Pwn, don't burn yourself out. Everyone can wait. Take some refresh time. Maybe talk to Decimalman?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
Same here... No issues on d2att... However 3/26 kernel with intelliactive, deadline 128, and slimkat 4 is rocking it. Rest defaults. Getting 17195 on an antutu.. 16740 with the same settings and 3/31

Thanks for the great kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wyelkins:
0331 runs fine on AICP 0331 nightly. I have had no force closes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Go to Setting>Display and Lights and see if settings FCs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cybrgeek 45:
Q3.27 with kernel 3/31

Don't know if this helps, but restored Quantum 3.27 & flashed kernel 3/31....it DID fc display & lights in settings. Restored to version 3.66.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dortego63:
Kernel 3/31 is working on AOSB KitKat 1.3.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xbiker321:
I'm rocking 3.5 and 3/26 kernel still, and using ART. Very pleased with this setup. Take some refresh time like scorpion said :beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Can you go into display under settings menu? That's when we get fc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit68:
3.66 with 3/31 fc on display settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
Here's a logcat for 3.67 with 3.31. Looks like Display & Lights gets called with bad argument?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
3/31 working flawlessly on slim kat stable 3/31
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Can you access the display settings without any fc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Yes sorry kind of implied that when I said was working
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Are you running a clean flash of Quantum 3.67 and QuantumKernel 3/30?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wyelkins:
I unclicked and clicked all the options. No problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Installed the 3/31 kernel on top of my 3.65 setup. Settings FC's when selecting Display & Lights. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Yes I am.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4b3ck:
AdaptiveBacklight.java:

public static boolean isEnabled() {
if (Integer.parseInt(FileUtils.readOneLine(FILE_CAB)) == 1) {
return true;
} else {
return false;
}
}

Replace with (hard fix... not ideal):

public static boolean isEnabled() {
boolean result = false;
if(isSupported() == false) return result;
try{
if (Integer.parseInt(FileUtils.readOneLine(FILE_CAB)) == 1) {
result = true;
} else {
result = false;
}
}catch(Exception ex){
setEnabled(false);
}
return result;
}

:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Who are you quoting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Why is this bug only affecting these builds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
For some reason after cherry-picking the key-disabler Display and settings won't work at all. I even went to a whole new Git, nothing is working. Tried builds without the disabler commits, the button settings commit, and all different variations. I think it's something with my actual Ubuntu installation, so I'm gonna reinstall that as well later today.

Even doing builds just as a plain CM with no tweaking to the source gives me issues now. I'll figure it all out later, it's just driving me absolutely insane.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Oooh looks like my logcat. :cool: lol

Problem is I don't think it's only displaysettings, other things were crashing on my test environment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
On 3.66 I'm using the 3/28 kernel, which is the last with no display fc. I have a sim pin and a pin lockscreen. When I boot my phone, I enter the sim pin, and when it goes to the lock pin, keypad freezes. No biggie. I wait a few seconds and hit the power button. Screen goes off. Hit power again and I can enter my pin. On 3.67, the power button trick won't work. Phone gets stuck on the lockscreen. So, 3.66 and 3/28 it is.

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
I know nothing about ubuntu/linux and trying to format my sd card with gparted for my asus tablet was stupid wonky (having to split it into fat32/f2fs partitions). Switched to x64 from i386 distro and it worked ok (using saucy salamander). Lucky it's so easy to install compared to re-installing windows. I need to do that on my home computer and 2 days staring at a monitor hitting 'reboot now' isn't my idea of fun.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Anybody still on d2att, I tried the 3/28 kernel on Quantum 3.36 and it would not boot. Back to 3/16.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Oh never mind, it worked today. It seems to happen when you switch in the sounds menu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
However I switch, it seems to work fine. I do have a volume mod though, so I don't know if that would affect it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
April fool? 4/1 was my logcat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dortego63:
every thing is working for me without any fc with Kernel 3/31 on AOSB KitKat 1.3.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I meant to say it looks like my logcat. Not it is my logcat. Now I see the confusion. :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
I am really happy with Quantum ROM and I'm confident that we will still get update, in the future, just take your time, I understand that the display settings FC is hard to resolve... I also found a similar FC when I click on "SMS message limit" in the Security section. The Settings app FC when I click on this option (I'm on Quantum 3.66 with 3/28 kernel). Otherwise, the ROM is rock solid, I was even able to undervolt it with TricsterMOD for better battery life. Also, I'm able to change screen colors settings by pushing this apk in /system/priv-app, so that the ROM is even easier to work with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
What the hell is that apk? NO ONE INSTALL IT.