yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Can you give me an example of what stresses your phone to result in settings not sticking? I would like to test. I am still on 7-10b with stock rom and my settings stick like glue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 09CarreraS:
Just run any benchmark. Antutu or Quadrant, etc. Use a program such as spy CPU to check.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
I am using cpu spy already. I just ran antutu and it stuck at 1,512. CPU spy shows no use above 1,512 and so does Antutu in the attached result. I am using voltage control, 7-10b kernel version, on-demand, noop, set at boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
interesting...i didn't actually view that screen in Antutu, but i noticed that at boot up, when viewing CPU SPY, there were less than 10s on 1890 and the other times/usage were at 1512 and below. Using my phone for a few minutes it was fine and the CPU didn't go past 1512. I would then view CPU SPY again and notice that the amount of time spent at 1890 remained unchanged, i.e. less than 10s. I would immediately run Antutu and immediately after the run, i would check CPU SPY and notice that the time spent at 1890 increased by more than 2 minutes...which would indicate that the Antutu run caused the CPU to ramp up to 1890.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moneyover:
Ktoonsez can u please check your pm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Noop is a good one to use when screen is off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Like I said, I was running carbon 4/30 build. I've never had the flickering until this release. Up until this release, I was UV 25mv across the board and to mitigate the flickering I had to OV by 25. Makes no sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
This patch is what re-introduced the flickering (MDP underruns). Just a heads up KT.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Funny thing is yes I had the flickering yesterday but haven't had it today. Also I haven't had any static screen issues since the latest kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Why is everyone hating on SIO? It gives you the same battery life and smoothness as ROW, with a little bit of speed. Everyone seems to ignore it now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
I love SIO
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yep, hoping he is gonna merge more code to fix it before I revert it, there is alot more code on his end but he has yet to merge it. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Stupid patches...

Unfortunately, I still had one or two today after a full night's charge and running my normal clock speeds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidFiend76:
Been using the latest update KT and battery life is much improved. Haven't had an issue with anything yet. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Dan Rosenberg has the AT&T S4 bootloader unlocked...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Just read that! Very good news. Definitely can't wait to order my s4 next Friday

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
Still have to wait the month out until vzw joins the club. Still good news for AT&T or GSM in general on snapdragon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Oh snap......gonna have to see if I have a spare $600 laying around. And wait until CyanogenMod is in at least alpha stages. Can't even make it a year on a phone anymore.

I guess I might wait to see what Google comes out with at I/O. Nexus 5 and I'm totally there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheWyzeMan:
Is there anyway to run this kernel with the non-updated Bluetooth drivers? Seems the ones Ktoonsez uses doesn't like my Bluetooth OBD2 scanner. Or it doesn't like the ones he uses.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Sure there is. You can compile it yourself. His git is available in the OP. Just change what you don't want and run it on your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
So it seems you and task are going to parting ways? :( I'm pretty sure task will not be getting an s4 as he is fed up with Samsung and I believe he is waiting for the next nexus when his wife/fiancé allows him to buy another device.

I haven't decided what to do. I got $500 for my note 2 because I was gonna get an s4 but really I want to follow you and task seeing as I have been running your kernel and tasks ROM on my sgs2 and sgs3 for about a year and a half almost. A lot of devs I hear are moving to Sony, that's where Entropy went I believe. I want a Nexus phone because I love my Nexus 7, but the hardware just always seems underwhelming, especially the camera.

Sent from my SGH-I747

---------- Post added at 04:15 PM ---------- Previous post was at 04:08 PM ----------

I love these types of responses. While they are very truthful, if he is asking that question to begin with what gives you the notion that he has any idea how to compile kernels or any of that jazz? Being laid off work for a few weeks I've wanted to try to start learning Android dev'ing but I have no clue where to start.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] byte9:
Revert to an earlier build. Do you use it w Torque?

Via Tapatalk 2 (giggity)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
They are identical to all other kernels, that an old message from 10 months ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Considering there's boat loads of information including tutorials all over the internet, it isn't that hard. There was one specific ROM I was trying to build a while back but couldn't due to the way that dev put his stuff together. Had it been a CM or AOKP base, I could've done it easily following those tutorials. I didn't pursue it further as I'm in school full time along with being active duty with a family. I have a lot less time than I care to admit.

Enough with the thread derail. Toons, I love your work and if there was a way to make love to this kernel, I'd do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Where there's a will, there's a way... :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Yeah there are a lot of tutorials, I guess I kinda get overwhelmed.

Anyways I've been flip flopping between underwear and kt. Right now I'm on underwear because KT started giving me random reboots, but I'll try this latest release. I usually stick with the if it ain't broke don't fix it but I prefer to run KT as my phone seems to perform better, and I like ktweaker.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you're getting overwhelmed it just means that you need to slow down, read, read more, read a little more, and then read again. Step by step is the best process. If one step f$cks up, go back and redo that step again until it works. Then move on. No one should expect instant results with this kind of stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Could not have said it better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
What Sony phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Ktoonsez a few updates back I mentioned the error under boostpulse for the Interactive Governor that says "Unsupported kernel, file not found" by any chance are you going to take that off in the next release? Just curious ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
The xperia T or TL something like that. Sony has become very developer friendly as of late I've been reading. They also have been coming out with some decent devices. I still haven't been sold on Sony but honestly I'll probably go where ever development is booming. Got lucky with ATT gs2 because any international ROM could be flashed via entropy hellraiser and then task begin to release AOKP and then I've only ran Tasks AOKP on my gs3 but I have a lot of options if I ever decided to switch. I don't know if the gs4 will have as much development, but as far as I'm concerned I'll probably just follow task360 and get whatever next gen device he gets because I see it as the OEM provides the hardware and task provides the software, each being equally important but I just can't run stock OEM ROMs they always feel clunky. Hell even my nexus 7 feels clunky on stock ROM after I've been running smoothROM on it for a few months.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats just crazy talk!!!!!!!!!! ;) :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Not enough time in the day, I gotta pick and choose what to brew up for you guys when time is available :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Yeah, I remember before I rooted my gs2 I did about two weeks worth of reading because I was so scared I was going to brick it, then when I actually did it couldn't believe how easy it was, think I used entropy's tutorial.

I'm completely unfamiliar with linux, never ran it on a PC before. I suppose getting that up and running is my first step. You and ktoonez are inspiration though because I can see how far you guys have come, so thanks for that as well as your awesome software :)

And what I meant by going separate ways was it seems you guys have different ideas on what your next device will be. I was gonna get an s4, sold my note 2 to get it, but honestly I decided I won't be getting another device until you guys do because when it comes down to it I've been running your ROM on my phone for a year and a half and that's just as important to me as the hardware, if not more.

Anyways on topic, flashed the latest release and no problems so far haven't touched any ktweaker settings yet.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Not a problem fair enough thanks KT!! :D:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crash822:
Had several reboots lately. This is the only one where I remembered to get a kmsg from. The error is from when my phone was updating some apps from the play store and screen was off. The other one that happened was while my phone was resting with screen off as well.

Min is 386, no UV is set, using ktoonservative with no modifications.

https://www.dropbox.com/s/ocls9dwltgtrkre/kmsg.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That looks like a super old version and is missing alot of info in the last_kmsg. What date/version (AOSP/TJ) is that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crash822:
4/30 ktoons and 4/26 aokp task. perhaps I did the log wrong? adb shell cat /proc/last_kmsg > kmsg.txt is what i did, only weird part about it was windows would always tell me file was in use until I rebooted my computer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That was correct, weird how its missing so much (anyway, nothing good in it), usually they start like this, which tells me date and version:

<6>[ 0.000000] Booting Linux on physical CPU 0

<6>[ 0.000000] Initializing cgroup subsys cpu

<5>[ 0.000000] Linux version 3.4.43-KT747-gbb16d81 (ktoonsez@ktoonsez-Virtual

Box) (gcc version 4.7.3 20130328 (prerelease) (Linaro GCC 4.7-2013.04) ) #1 SMP

PREEMPT Wed May 1 13:56:13 MST 2013

<7>[ 0.000000] CPU: ARMv7 Processor [511f04d0] revision 0 (ARMv7), cr=10c5387

d

<7>[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cach

e

<7>[ 0.000000] Machine: SAMSUNG M2_ATT

<2>[ 0.000000] Truncating memory at 0xc0000000 to fit in 32-bit physical addr

ess space

<6>[ 0.000000] memory pool 3 (start f92ff000 size 6d00000) initialized

<6>[ 0.000000] Initialized persistent memory from bff00000-bfffffff

<7>[ 0.000000] Memory policy: ECC disabled, Data cache writealloc

<3>[ 0.000000] smem_find(137, 80): wrong size 72

<6>[ 0.000000] socinfo_init: v6, id=87, ver=3.1, raw_id=1717, raw_ver=4, hw_p

lat=1, hw_plat_ver=65536

<6>[ 0.000000] accessory_chip=0 hw_plat_subtype=0

<7>[ 0.000000] On node 0 totalpages: 428543

<7>[ 0.000000] free_area_init_node: node 0, pgdat c0d059c0, node_mem_map c136

9000

<7>[ 0.000000] Normal zone: 1722 pages used for memmap

<7>[ 0.000000] Normal zone: 0 pages reserved

<7>[ 0.000000] Normal zone: 151366 pages, LIFO batch:31

<7>[ 0.000000] HighMem zone: 2370 pages used for memmap

<7>[ 0.000000] HighMem zone: 273085 pages, LIFO batch:31

<6>[ 0.000000] allocating 11304960 bytes at c236f000 (8256f000 physical) for

fb
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
How much lag is seen when you UV 25 volts across the board? Is it noticeable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Should no lag with -25 what are min and max mhz

President of {Team Kernelizers}

Im Gman and I approve this message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
378 and 1512. normal values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
What kind of lag are you seeing?

President of {Team Kernelizers}

Im Gman and I approve this message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
Just a bit of choppyness, the whole smooth buttery feeling is lost sometimes!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Sorry, I should have PM'd. Tired and frustrated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
Happens to me too; gets stuttery fairly often, even on default settings. It's probably just the phone; everyone's is different.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crash822:
Had another reboot while phone was sitting with screen off. I was downloading newest task rom. I hope this time it has all the info you need

https://www.dropbox.com/s/rbwcvbk3j1180x5/last_kmsg.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its good enough, still missing the top stuff so weird. But seems to be something in the wifi module that pissing it off during sleep.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Cause it wants to play not sleep :-p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
[MENTION=4163122]justin860[/MENTION]

Never heard from you on the GPS gov and sched thing. Hoping that did the trick for you, going out of town for 2 weeks for work again and wanted to know what the scoop was. :D

P.S.

Love hearing crickets in here, that means everything is running AWESOME for everyone!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Did you say crickets? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I'm taking a long drive on Sunday to upstate NY and will be using the GPS. I can let you know then if that works for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Sorry haven't tested it cause I've been working but I guess it's a Good thing that I didn't because I trust your abilities to fix things and make your user base happy. I never once doubted the fix wouldn't work. ;)

Ps have a safe trip buddy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I'm going from eastern CT to a large car meet/ show in Stony Point. Well, we're expecting it to be pretty big. The meets my team hosts usually have a good turnout.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Guys, let's keep the OT outta this thread please. PM each other if you wanna continue the discussion. Thanks! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Naddict:
I am, however, a mod - and the thread has been lightly cleaned of off-topic discussion, take it to a social media website for that stuff.

Always be respectful in your posts...If there are issues, report them, there are plenty of moderators available to squash troll's with a quickness.

Follow the rules, or log off. Have a good weekend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, I'm wondering if you could update your kernel to use fauxsound's latest update? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I dont see it, last update he made was 2 months ago:

https://github.com/faux123/SGH-Krai...ffed034d/sound/soc/codecs/sound_control_gpl.c
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Kernel sound driver 2.1+ not sure what that means lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ya. Its no where in his Github that I see so I can't add it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Don't see that in mine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Update in the market
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Now I might not want to. Lol

Edit-crap! Stupid update!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Well its just the new power amp gain control that this 'kernel update' depends on. Everything else works like it did in the last version... I think
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
https://github.com/faux123/htc-m7/commit/acff15670bae39452662c641f46cd65ab670b927

There is the new commit, posted from his G+.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Thankfully, I had a backup of the previous version. I'll wait and see what toons and/or faux have to say about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Wanna try it buddy? U on AOSP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Wanna try, u on AOSP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Even though its the wrong phone, I merged it (just need someone to test) since it looks like he just added a few tweak files to sysfs for the most part.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I am indeed.

Gimme gimme gimme! Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Here you go and for anyone else that wants to test the new Faux added stuff:

AOSP Linux 3.4 Faux Sound update Test

http://www.mediafire.com/?z50c5o5j2oc6ta1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Toons, you have pm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
Oops my bad, was the only one i saw he posted.

Supposedly ads support for some headphones power/amp controls according to the Google play change log.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Downloading and installing shortly.

---------- Post added at 08:29 PM ---------- Previous post was at 08:22 PM ----------

Ooooohhh! New goodies!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Any other changes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
1. Revert "msm_fb: display: allow backlight update after first update"

2. Linux 3.4.43

3. ARM: fault: assume no context when IRQs are disabled during data abort.

4. lowmemorykiller: make default lowmemorykiller debug message useful
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Great, glad it is working. And only 6 hours after he released it, hows that for service with a smile!!!!!!!!!!!!!!!!!!!!!!! :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Damn right! I don't care what anyone says about you or your work bro! You're the effing man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bullet2binary:
I'm getting ready to flash this on Task650's May 2 build. Any reason I shouldn't?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Ur allergic to awesome ?

Lol should work fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Not a single. Been off my charger since 6 AM and am still sitting at 52%. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bullet2binary:
Sweet. You guys on these forums rock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
FLOAM!!!!!!!!!!! Thats the BEST response ever!!!!!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I don't use faux sound but I flashed it anyway and this version fixed the screen flickering that reappeared when using auto-hotplug or any hot plugging governor since the 4.27.2013 release.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Like toons said, best response yet!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, just wanted to say thanks. My s3 w/ jellybam v7.7 and your latest kernel works great. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
One word from tango and cash movie FUBAR that's what you be without toons and task in our life

F**K

UP

BEYOND

ALL

RECOGNITION

President of {Team Kernelizers}

Im Gman and I approve this message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Running this with rootbox and it's so smooth. Nice job ktoonsez

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bullet2binary:
So far this is really freaking sweet. Love it with faux sound.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Yo ktoonz I had a reboot shortly after flashing today's kernel. Think there might be some cool stuff in this one. I'm on ktoonservative row and UV-25. No OC. Thanks man, FLOAAAAAAM!!!!!

http://db.tt/ABc5XsOr
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I would stop UVing to see if problem goes away
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 5/3/2013

1. Added GPS Scheduler and Governor option in "Extras" screen for TW USERS (used to automatically change sched and gov when GPS is IN USE

2. Patches from CM and google

3. Revert "msm_fb: display: allow backlight update after first update"

4. Linux 3.4.43

5. ARM: fault: assume no context when IRQs are disabled during data abort.

6. lowmemorykiller: make default lowmemorykiller debug message useful

7. Updated FAUX Sound

8. Renamed zip files a little to be shorter and easier to read
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alex2x3:
Is the 3.4 version exactly the same as the test version you posted earlier today? Making sure cuz it's the same file name.

Thanks again for the hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes, it is the same
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] allenlin:
Just flashed the 05/03 TW 4.1.2 version and did some simple test, it's ok.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bullet2binary:
Ktoonsez, thank you so much for adding the faux sound. I play bass and this helps me pick out the chords so much easier while using my head phones. Top notch work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I had the static screen just now. I changed disable over lays and it went away let's see if it comes back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
I am experiencing the same thing also, had to Disable HW overlays to make it go away :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Figured I would post this here too. :D

@ Everyone

This only applies to whoever might be moving over to the SGS4 or who have already moved to that device. I did this when me & Ktoonsez were on the SGS2 and wanted to get him the SGS3 so he could stay with me in terms of devices. We had great success. If any would like to help Ktoonsez get the SGS4 and want to donate to the cause we are accepting any help. You know ktoonsez's donation link HERE . I already have the SGS4 and might not be keeping it due to not being able to justify the expense for the device. So if you'd like to help me justify keeping mine the you can donate to me HERE. I already have AOKP builds for it, we just need the bootloader to get unlocked and within minutes my AOKP builds will be posted for it. Let me or Ktoonsez know if you would like to help. It's your choice. We are not beggars. Just seeing who would like to pitch in. Thanks. :D

P.S- WE will still be supporting this device. If you notice. I'm still supporting the SGS2 and I hate that device with a passion. ;)