yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
For those that seemed to decide that the app crashes were from the updated kernel. I'm pretty sure the culprit of the app crashes has to do with this...

This...

if (mode != null && mode.indexOf('w') != -1) enforceWritePermission(uri);

else enforceReadPermission(uri);

return ContentProvider.this.openFile(uri, mode);

Needs to be changed to this...

if (mode != null && mode.startsWith("rw")) enforceWritePermission(uri);

else enforceReadPermission(uri);

return ContentProvider.this.openFile(uri, mode);
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Not sure exactly what this is or where the code is located, but hopefully this would fix the issue. I'm not too bothered by the FC's though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
FYI. They're not force closes. They are crashes. Force closes go a little deeper than what you guys are seeing. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Haha my bad. Not 100% familiar with the proper terminology. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
You da man. Just curious, why would the old code cause issues on some devices but not others (yours). I know all devices are not created equal but having superior components doesn't mean the device is going to magically override permissions to avoid crashes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It all comes down to different circumstances I guess. Nothing to do with hardware in terms of this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
I have no idea how you do all this work. Just from those two lines you posted my eyes are crossing and my head hurts :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TEXASMADE1978:
Hopefully he wouldn't blend it (lol), i think he would definitely take it and hell maybe even dev for it. But he isn't going to come outta pocket for one..

(No more off topic for me):rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
Don't know too much about this sort of stuff but from what I've read I think that simple change could do it... ::Fingers crossed::
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
Could someone pm me on where to edit this line? Not sure where to look for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you're working with source then you really shouldn't need to ask this here. You should know how to grep for it. Learning the basics is necessary when trying to help troubleshoot these types of issues. ;)

P.S-It's in the framework directory. But it doesn't work so it would be no good to you dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
Whoops well sorry my bad. Trying to learn this stuff and Its been slow going. My computer is broke and want sure if this was an easy fix over the phone. Ha well I will just wait it out. Thanks for your work. I'm not working with source but we'll learn to soon. I want to help troubleshoot but need to get off my training wheels and find some time to dig in deep. Sorry again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
FYI. You can't change code like this on a phone. This is source work. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
Thanks! One day I will be big and strong like task and be able to troubleshoot. Lol that is seriously my goal here. I wish to learn more. Thanks for your help and wisdom and rom. Simply amazing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
Task are you by chance calling recycle() anywhere? From what I've seen in the logcats the heap sizes keep growing then the app crashes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewxp:
Lol!! I'm amazed so many non coders come to and post in a dev thread and have so many more posts than others. It's fine, it just made me lol after realizing. hahaha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
I cant install the rom coming from external sd, it should be installed from internal, I'm using CW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You need to take that up with the developer of whatever recovery you are using. This ROM has nothing to do with recoveries.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kafepuya:
Task, you know what you should do? Let the same people who have been complaining - instead of reverting for the time being, like you suggested - try and implement the code themselves, recompile and flash their own work. I mean, you already posted a possible fix. It contains less text that the average rant in this thread. Maybe a change of perspective would make them more grateful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
Your statement is confusing. I believe there should be some question marks in there. But anyway. It should install just fine from external. I used to do it all the time with CW and I still do it now with TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
You should read the thread. That change doesn't resolve the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kafepuya:
Yeah I read that after I posted. The point is still the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
It start downloading, and it stop giving me an error "code 7" did wipe data, cache, dalvik and format system. Tried installing it from internal and external sd. Coming from 4.1.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpasilliumNexus:
So... Ignore the post about your issue having nothing to do with this thread, right below your post, and continue posting your problem here? K.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
Thanks mate, I ignored it :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Go to the recovery thread if you want support for a recovery dude. The ROM flashes just as it should. Follow the instruction in the OP and you won't have any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
I did the searching for you and found everything from update your recovery to error if you edited your build prop (perhaps for Google wallet).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Search is cool.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amzi:
^Truth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Two updates this week while on ****ty Costa Rican hotel wifi... you do, in fact, rule.

0KE17376Y5726250S

Wifikill helped :)

One nation under a groove, gettin down just for the funk of it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maDIEmG:
4.3 working awesome so far man, also that new boot logo i laughed a bit. lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Laughed your, um, pants off?

See what I did there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Senor_Fuzzypants:
Haha, punny
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i5lee8bit:
yeah but can u see why kids love cinnamon toast crunch?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
The issue with the apps crashing is fixed. Just figured you guys would want to know. Next release. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
You're a beast!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
i eat wood for free!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
What was the reason?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This...

#ifdef QCOM_HARDWARE

Should have been this...

#ifdef QCOM_BSP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JeRrYFaR:
I still don't understand why it only affected a small portion of us though, myself included. Good news though. Looking forward to the next release. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Saw this in the cm changelog earlier and i was like zomg must sync and try and effectively. It works lol. One line who woulda guessed.. Surely greater men then i lol

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes. I think I covered the "it works" part pretty well in a prior post. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
so thats means new qualcomm drivers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] byte9:
Sent you a PM @blackwing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
http://review.cyanogenmod.org/#/c/35159/

not qualcomm but adreno. sorry i was confused
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
I may be wrong but it don't believe it's new drivers but how it's being called or initiated. I saw it a lot in the logcats shortly before the crashes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Covart:
Well, this surprised me yesterday. I keep my brightness at 75% and on a stock battery.

Guess the new kernel is settling in?

And I have no issues with the 4.3 release, so I guess I am lucky?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
Cool story bro?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release available for download in the OP or just check your OTA Updaters. ;)

AOKP 4.2.2 Jellybean 4.5.2013

Updated Kernel (Lots of code change)

Updated to the latest adreno drivers

Fixed apps from crashing

Fixed cLock

Allow enabling WebSockets from Labs Preferences in Broswer (HTML5)

Lockscreen: adjust layout of GlowPad

Fixed NavRing Icon size

Fixed potential deadlock between LockScreen and WindowManagerService

Graphics cleanup (qcom)

Fixed rebooting from recovery (Was writing to the wrong partition)

Updated Vibration Patterns

Fixed a cursor leak

Fixed a race condition in backlight adjustment

I know there's more that I'm missing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
Task - you rock dude!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpasilliumNexus:
Aww yiss mutha****** ROM update! Thanks dude!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Good Again!

Thanks,

New version running flawlessly so far. My only problem with last version and Playstore is now fixed. Opened first time and every time!!

Thanks for your efforts and tireless work!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Nice Friday surprise :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eortizr:
anybody using NBA League Pass? is your video ok?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I think this describes my previous issues. Can't wait to test it out. Thanks!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TEXASMADE1978:
This app has nothing to do with this ROM. Contact the app developer.

(Its a sub-par app to begin with, not worth the $$)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
http://xdaforums.com/showpost.php?p=38843439&postcount=24316

This is a development thread. Please refer to the OP. The Q & A link is very obviously posted there. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
task.. small thing i noticed on 4/5 release, recents apps key otherwise acts completely normal, but if i keep pressing it it shows Google plus (i believe it says, which is weird because i don't have it installed) minimizing and then disappearing. no adverse affect.. jus something strange i never noticed before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I have no clue what you mean by a "recent apps" key. We have a home, menu, and back button. No recents. Can you explain?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
yessir..i have navbar enabled, 3rd key being recent apps.

and small correction.. i do have the app installed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bob Simons:
recent apps?

maybe pressing and holding the home button?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
no, jus tapping the recents key on navbar. it shows it minimize whether i have other apps showing in the recent app switcher or not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Im not seeing it and ive been pressing this recents almost 50 times now. I would fully wipe your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
ok..thx. I'll give it a shot

---------- Post added at 01:30 PM ---------- Previous post was at 01:23 PM ----------

been running your roms on this device since the day i got it..awesome work man.

here's $10 for ur efforts sir

Confirmation number: 1MT064187V9014157
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jridda10121:
You mean you asked a question before doing that. Let me know if that works. I'm having same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
task, been running your roms on this device since the day i got it..awesome work man.

here's $10 for ur efforts sir

Confirmation number: 1MT064187V9014157

---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------

yep. because of the simple fact that ive been on tasks rom for at least the past 7-8 releases and dirty flashed every time and never had that issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
Solid ROM Task. Will forward another donation next payday. Tks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thanks dude. I appreciate it. :highfive:

Just because you have "dirty flashed" for every update doesn't really mean anything. Because of that, you are having issues. You have been running a bogged down system for as long as you have not been fully wiping your device. Your device has most likely not been running as good as it should have been. I'm not sure about you guys. But I want and need my device to work top notch when I use it. Especially when I'm out working. I fully wipe.

The installation instructions specifically say to fully wipe before posting here. Please use those directions. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A Ham Sandwich:
I avoided the past couple releases after seeing the app closing issues and just updated to 4.5 and I just want to say that whenever the ability to delete Gmails from the notification pulldown happened, that was a godsend. THANK YOU SO MUCH. I apologize that this post doesn't do much to contribute to the development of this ROM but I had to say thanks for this feature; I've been sorely wanting it for a long time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
Ya Ummmmm....... Gmail implemented that a while ago. So ya.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Task I tried activating the charging lights on the LED settings and for some reason I am not getting the Superuser permission for ROM control so the option can activate, what am I doing wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Follow the instructions that it gives you when selected that option dude. It's pretty straightforward. Actually look at the option this time around. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
I understand that I have to reboot for the option to activate but when you turn on the feature I should get the Superuser permission for ROM control so I can then reboot for the feature to activate but I just turned it on and I didn't get a Superuser permission and I tried rebooting the device and still nothing :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Then you'll have to go into the superuser section and try and figure out why. clear the logs for it if you have to. Gotta try and look around to figure these types of things out sometimes. Or fully wipe your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
I just did a FULL wipe on my device and I am still not able to activate the charging LED :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Then wait for the next release. Not sure what else to tell you at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Works for me reboot it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
OK not a problem I will wait for the next release thanks Task :good:

---------- Post added at 06:42 PM ---------- Previous post was at 06:36 PM ----------

Is not a big deal I am just going to wait until the next release ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Awesomesauce!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
yessir. full wipe and clean install fixed it. thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wtfdusk:
Just wanted to say good ROM! Brings many happy to my face it almost breaks it. I have been running it for 3 minutes and the battery life is crazy amazing. I shall be naming my first born task651 I'm so impressed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
I know this may sound crazy....and too obvious...but you don't have "Quite Hours" enabled right now do you? That will disable led if set correctly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Liptus:
Last time I made a five minute battery remark no one picked up on the sarcasm / joke and I got indefinitely flamed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You were lucky then. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Battery life shouldn't be discussed because it's relevant only to that user... :p:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
OMG, I just flashed this ROM and a minute later the battery dropped 1%. This is terrible!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markysd:
then fix the Terrible yourself:silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adam29617:
I been running this on my GS3 for 2 months and its only getting better I get 22 hours of non stop use! Im at 702mhz 347mhz no lag what so ever. Task good job and +1 on the pre boot, boot animation
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Galaen:
Wait... This phone has a battery!?

Sent from my AT&T GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NorskHelgen:
Loving this ROM but I am not sure why everything but stock and CM10.1 has audio that cuts out whenever you lock or unlock the screen. I also find the stock EQ shuts off briefly when you pause and play music (tested on Google Music).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not sure what you want in response to this statement. But if you're not sure about something, you can always take a look through the source and see if you can fix, modify, or add things to your liking. I make it open and available for everyone to see. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewxp:
I've attempted finding out why but ended up taking on work for a new client outside work (no more free time). Indeed frustrating. Until then, you can disable touch sounds in the config. That should clear up the issue temporarily until someone finds a fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Just a guess but does

Refer to the 'Surface Finger' process taking up memory very often?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Edgardo101510:
SPRINT GS3 Here! :)

Can someone PLEASE PORT THIS TO THE SPRINT VARIANT OF THE GS3 PLEASE! :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I hate Sprint. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
Ditto with whoever else was experiencing random freezes and reboots. Seems to only happen when browser is open or running in background. Other than that, flawless version. Great work as usual :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Random Reboot

Got a random reboot while the phone was sitting on the charger. I wasn't touching it and hadn't for at least an hour. Last_kmsg attached if interested.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
A logcat will not help if you got a reboot. If you don't the proper information to post at the time of the bug report, then it's useless to post the "Me too, Me too" posts as it doesn't help in anyway. Just be patient and post when you have the proper information. Thanks. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Up your minimum clock speed and see if it happens again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Unfortunately I think you may be mistaken here dude. Not sure if you missed the title of the forum you are in and/or realize that this is a development thread. So when you come here to post the "+1" or "Meet too, me too" posts, it does absolutely no good nor does it help in any way with the development of this ROM. So who's the one trolling? Well that's an easy one to figure out here. You could've just posted the word "shoe" and it wouldve help the troubleshooting process just as much as your original post. So please try your best to grasp the concept of what a development thread is and what its for. If you don't think you can do that. Then there's a simple solution for that. Don't post here. Thanks. :D

I'm going to shut this thread down now to stop you from further acting out in a very unnecessary manner. Keep your emotions to yourself please. They do not belong here. I'm sure every one will appreciate and thank you for that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Naddict:
Well, a moderator was called, and the thread has been cleaned.

Respect the wishes of the developer and bring contributions to the conversation as posted/requested by task.

Also, being disrespectful is an XDA posting rules violation.

If you are not happy or not getting what you want from one thread, move on, there are plenty of others.

Have a good weekend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidFiend76:
Great update Task. No issues.

I used to rock the KT747 kernel but now wearing your Underwear Kernel. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Great update. Seems like raising the low frequency to 4xxmhz help with the deadlocks. Greets! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Same here no issues and the screen scrambling I was experiencing is gone. I love the kernel too very smooth and responsive. Had one freeze and reboot upped mhz and haven't had the issue since
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MColletti12:
Just a suggestion. Would it be possible to add a feature to the lock screen/clock that only minimizes the lock screen challenge when the clock lock screen widget has a calander event to display? My apologies if this post belongs in the q&a section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
Suggestion: It would be nice if there was an option to disable moving wallpaper without launchers. It really screws with live wallpapers. Just throwing it out there. It would be much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I will not work on the stock launcher at all because I think it sucks really, really bad. Nova Launcher has that option. Now that I think about it. I might actually just remove the stock launcher. I was going to a while back and just totally forgot to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I'd put on your flame retardant suits imo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
Ship it with no launcher :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 911Guy:
You guys kill me!! I read almost every post and sometimes the funny little rants over the noobs or lazies are hilarious!!

FR Suit is at the ready!

Have a great day guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] verosity:
Task, well done, yet again, on this Rom. The problem with apps closing is officially fixed on my device. I've never brought the problem up but watched and waited. Appears that it's fixed.

Thanks man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I used to use the stock launcher but got used to nova. I still use the stock launcher sometimes to import my settings. Like a 50/50 chance when I restore my nova settings that the app icons are all androids.

Could you maybe PM me and let me know what I'm doing wrong to avoid that? Don't want to turn this into a Nova discussion
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Yeah, asked if he could pm me, but thanks for the link to the thread I already frequent.