yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If you are monitoring it, do me a favor and PM me if someone finds a way to backup and restore it, since I have to flash 20 things a day. Dont want to have to halt development if that happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Not a prob..will do. I follow the 2 threads.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
Hey ktoonz, I recently tried out diet.ics on your sammy 7/19 kernels (b and c). I experienced some weird audio issue from the headphone jack. On aokp and your aosp kernel I have no issues. What happened on Sammy was:

A high pitched low volume whine in the background of certainaudio files. They are not present on aokp

After more than an hour, Idk specifically but definitely longer than an hour, of playback there is a tremendously loud high pitched noise. It's unaffected by volume control. You have to pause the audio. I paused the noise, disconnected my headphones and pressed play, then it started the noise again through the phone speaker. I had to restart the phone to fully stop it.

If you'd like more detailed information let me know. But I figured this was a problem worth posting about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cracjackson:
I have the same issue I'm on 7/19 as well running diet ics
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ya, its mentioned somewhere in here many times, search the thread and you will see some possible fixes. Sammy ROM's suck that what it comes down to, and I have not found a way yet to get my newest code to work on Sammy, no MTP and no WIFI.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
For the Flash Hesitant to keep in mind.

Honestly I think it might be the fact that there is so much similar development going on for the same type of phone from all different carriers I think you are getting a mix of carrier builds and guys/gals are getting flashed on the wrong carrier devices that it is causing the issue to arise. I think (And again I am only speculating for the spectators out there) that is truly the root cause that may be happening as I have not seen an issue and have tried all of the above mentioned (Even back from CM10 to Smartguy044's Resurrection ROM) and have seen no uncertain or suspicious activity that would lead to loss of the IMEI issue. I did speak with one of the ATT techs one day and just as a heads up they mentioned they are seeing allot of issues with bad micro SIM and are having to replace them at random...Don't know if this could be contributing factor to the issues seen but could be just a thought to keep in mind. Just thought I would add to the out loud thinking ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Well the way it's happened is if someone else flashes cm10 and then uses Odin to flash to stock.. That's when they lose their imei. Why? I have no idea. It could be because cm10 requires to push an img file to change recovery.

Which I was gonna ask if anyone knows how I can revert that file? Meaning how can I undo that step lol

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PattyWagon915:
Trouble turning on

Thanks for the awesome kernel! Just having one minor problem, Im running 22 for aosp ics and my phone has trouble turning on.

It'll vibrate a few times and show the charging icon but wont turn on. Sometimes after about a minute or so itll randomly turn on.

About half of the time itll do that, the other half it wont turn on at all. Not too sure if its charging while its off either.

Cleared all cache and fixed permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Going off topic...

Sorry, I didn't intend to take this thread off topic (ie, IMEI)

For discussion on that, there is a lot, and continuing, on this thread. Seems nothing nailed down on cause or repair.

At this point, there are probably several of us that will update ktoonsez here if something is resolved. JFYI...there is info on the thread I linked above about how to backup the partitions, with hopes that would provide a restore. But it is not known yet if it will.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
Sorry for the repetition.

I read this thread a lot, but I only remember seeing the "crackling" noise. This is definitely being crackling lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I think these were some pretty solid steps to go from CM10 back to AOKP, yea you're triple kernal flashing, but I did that just to ensure that the CM10 kernal was gone before loading AOKP (includes a kernal), then loading this kernal... I just merged all the steps together...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Looks like u need to make a nandroid, do a complete wipe, re-install your ROM, then my kernel and see if the problem goes away. I am not having that issue on AOKP or CM/AOKP-JB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PattyWagon915:
Thanks for the fast response. Shouldve known to do that before freaking out hahah

Did that and its now turning on more nicely. Its weird though, now it wont turn on while connected to its charger.

As long as its turning on Im happy though. haha Appreciate al your hard work! :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
LOL I just looked...Im still on 7-9. Running way to smooth to change.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
My girlfriend is having the same issue. I know it's not a problem with the device itself (since we traded and the issues still persisted for her). I made a thread but I haven't really gotten any help with the issue - http://xdaforums.com/showthread.php?t=1789552
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Hmmm that's weird. It says default voltage for some is 1187. I go to undervolt to that and it goes go 1175 instead
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Voltage apps only do it in increments of 25. Im gonna get around to that soon to just round them all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Bfq is beautiful<3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
More Test Results ...

Here's an up-date to my test results (on Rogers SGH-I747M):

ONDEMAND 1512/384: Works! (smooth)

PERFORMANCE: 1512/1512: Works! (smooth)

PEGASUSQ: 1512/384: Does NOT work

CONSERVATIVE: 1512/384: Works! (smooth)

LAZY: 1512/384: Works! (smooth)

It would appear that ONLY the Pegasusq governor causes a problem. At this time I would suggest that you don't use it. Perhaps others could test it.

Peter

I'm now running some AnTuTu benchmarks. Will do so on both the ONDEMAND and PERFORMANCE settings noted above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Good information, but everyone remember, this phone is no exception for the standard rule that everyone phone will react different. I am running PEGASUSQ without issue, so it will all come down to preference and what your phone likes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
So what doesn't work with pegasus? I was running it just fine. Does it give you a boot loop?

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
Pegasus works fine for me as well. I am running conservative @ 384 to 918 right now and its crazy smooth. Smoother than stock at default. Love it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
More results, and a commentary ...

I just read a few replies concerning the fact that some people can use the PEGASUSQ governor without any problems. This is true. Every device is different, which leads me to the following:

Here are some benchmark results I did over the last 10 minutes:

AnTuTu via ONDEMAND governor: 6628

AnTuTu via PERFORMANCE governor: 6859

It’s here where I need to explain a few things about benchmarks that everyone, especially those who aren’t familiar with benchmarking, need to know.

NEVER, under any circumstances, take benchmark values as having any real meaning. The final value is not important as there are far too many issues that can affect the result.

Remember, every device is different. What do I mean? Well, your device may have a certain number of apps installed, and these apps may be entirely different from what others have installed. Everything on your device affects results. So if you see someone else getting a particular result, and you cannot achieve the same result, so what! It means nothing.

There is ONLY one result that has potential meaning, and that’s when you’re comparing YOUR device to YOUR device.

What I mean is, if all testing parameters are the same, and you test your device with one kernel, and then test your device again with another kernel, comparing both numbers has meaning. Comparing your results with someone else’s has no meaning.

When I say “testing parameters are the same,” it means to perform tests under the same circumstances. You must compare apples to apples. So, if you’re going to perform two tests, make sure you do so equally. Do not perform one test after you’re device has been on for hours, or for days, and then perform a second test when your device was just rebooted. Comparing those results will have no meaning because we know that devices generally perform better after they have been running for a while.

Bottom line? Benchmarks mean nothing. They only have meaning when the testing is done under laboratory conditions, and I don’t think any of us have proper testing facilities at home. I know I don’t.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
There are some threads with folks having WiFi problems, specifically drop./reconnect issues

Can anyone here report they had those issues fixed by flashing this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
I am running your latest version of Diet ICS and I am not having any problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobapunk:
My AnTuTu score went up 500 points using vr/SmartassV2 (the same combo I have been using for a long time on my Captivate).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Ok let's get this correct before someone screws up and everyone's on the right page everyone needs to undo all mods all tweaks all everything reboot to factory rooted backup assuming everyone's done that..and then flash before posting as task would say 'wipe now questions later."

Sent from my SAMSUNG-SGH-I747 using Xparent ICS Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jroyalty7:
Isn't there a problem with CWM and ex fat??? I recall on their thread that the SD card must be formatted to fat32 in order for CWM to function correctly. If I were you I would copy all SD card info over to PC/Mac what have you and format to fat 32 to see if it fixes the issue. Worst case scenario it doesn't and you can just format back to exfat and put your stuff back on SD card. Just a suggestion since not too many others are having the issues you are :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
What app are you using to set clock speed? SetCpu?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdbeitz:
I flashed this over top diet ics with no issues. But I'm also running the 7.6 diet release based on rogers.

Sent from my heavily modified I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Not in version 4 of the cwm in the op posted required to use this kernel :)

I'm at work we've had 3 bricked AT&T s3s since yesterday..just got the Intel when I clocked in.

Sent from my SAMSUNG-SGH-I747 using Xparent ICS Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
YES

YES!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdbeitz:
Works well ktoonz. Thanks :)

Sent from my heavily modified I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
What 7.6 diet? Did I miss it. Or are you holding out on us?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Haha ... I noticed the same thing ...

LOL

I noticed the same thing, but I didn't want to bother him because I know he's been working so hard on his ROM, and he's out of town this weekend.

I'm anxiously awaiting his next version. (drooling)

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Lol negative stock with Aokp wallpapers

Sent from my SAMSUNG-SGH-I747 using Xparent ICS Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
I'll give that a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdbeitz:
I posted a link in my thread. I've been holding out. Its not done yet. Ktoonz, this runs GREAT! UV coming soon I'm guessing and also the MHz steps need to be changed :) you da man

Sent from my heavily modified I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Wait til u try the new and improved bfq that ktoonsez added to his test version ;) heres a little preview

https://groups.google.com/forum/m/#!topic/bfq-iosched/HqxUOxhtJuA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Niceeee. This is what I used. Can't wait for the next version :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
ktoonsez has been hard at work on this. Tons and tons of fixes have been Added for performance stability and battery. Nice to have two people. One finds the good stuff the other adds it ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
If i had a million dollars i would give half to task and half to ktoonsez
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Change Log 7-22

1. Made a change to see if Foreign phones will show 192mhz

2. Linux 3.0.38

3. Reduced logging from chatty drivers

4. Lots of iosched treaks

5. 50,000 lines of code merge in from my other kernels...

This line reminds me that we have Linaro running through our blood. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, thats why Im so fast!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
And buttery! ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crash822:
Are you saying ktoonsez is fattening and bad for your heart?

I am on phone so expect errors
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
In a way, ever since I found him and Task the only excercise I get is sitting at my computer hitting my F5 button. :silly::good::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
That's what she said :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
I'm still experiencing some weird graphic glitches on touchwiz/nova and the loading circle also glitches. Other than that it runs smooth
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
touchwhiz is one HUGE graphical glitch. there's your problem. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moah9998:
My favorite kernel!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
The ONLY Kernel!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I'm starting to think this kernel does not play well with cm 10 aokp jb with force 2d gpu on. It's just too laggy no matter what setting I chose. When I go back to the original picked kernel the lag is gone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Below are the tests, now including Lazy. Not as good as OnDemand:

OnDemand/Noop - Stock Kernel, Rooted, G1

Overnight/11 hours/15% drop/1.362% per hour

OnDemand/Noop-Sammy Kernel, Rooted, G1

Overnight/12 hours/15%/1.25% drop per hour

SmartAssV2/SIO-Sammy Kernel, Rooted, G1

Overnight/8.5 hours/20%/2.35% drop per hour

OnDemand/Noop - Stock Kernel, Rooted, G1 - CPU Disabler installed

Overnight/10 ½ hours/12%/1.14% drop per hour

OnDemand/BFQ - Stock Kernel, Rooted, G1 - CPU Disabler installed: Power Saver off

Overnight/9 hours/6%/.6667% drop per hour

Lazy/BFQ - Stock Kernel, Rooted, G1 - CPU Disabler installed: Power Saver off

Overnight/9.5 hours/9%/.947% drop per hour​

However, I am not certain that CPU Disabler was operating. I had experimented with trying to see if I could turn it off. I"m going to do 2 more tests. One with Ondemand and one with Lazy, both with BFQ. I'll post back in a couple days.

Reminder to anyone interested in this topic: I am on 7/10b Sammy Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated:

AOSP ICS VERSION: Download CWM flashable zip kernel

http://www.mediafire.com/?6gq8n6oykq72qqz

AOSP JELLYBEAN: Download CWM flashable zip kernel

http://www.mediafire.com/?l2mmfnjt577efq5

FYI: CM10 does not want to cooperate with the max Mhz settings from my scripts, since it is a beta ROM, so you will have to set it manually with "Voltage Control" or run the script I put in "/system/etc/init.d/00post-init"

Heads up

I have switched my scheduler to bfq (since I added the new version) for all those that follow what I do. Still using ondemand.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
I see u took my suggestion about bfq? ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Whatever you did to this new kernel completely fix the lag issue I was having even with the two-dimensional GPU selected thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
This thing is really shaping up :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
This thing is a beauty ktoonsez :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Can I use this with the cm10 AOKP ktoonez released yesterday?

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
Obviously
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Damn. All my time spent looking for good patches really was worth it. This runs awesome now. Been running since last night with bfq and ondemand and am loving it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EthanMG:
does this mean there is a ui included with the kernel that allows us to change voltages? i unzipped the kernel zip and didnt find an apk or anything. if not, what should we use to make changes to the voltages and clock speed? in the past ive used setcpu, voltage control, nstools, and system tuner. any suggestions? read through a lot of pages this morning but didnt find any suggestions from that, so i thought id ask. thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
The voltage setting interface is enabled on Voltage Control with the newer kernels
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EthanMG:
is this true for the Sammy kernel as well? I'm sticking to stick Rom for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
On jb AOKP rom. The phone is running much cooler with new kernel it was running very hot with stock jb AOKP. Thanks for working your magic:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
indeed a fine piece of work and collaboration, thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Give it a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polish_pat:
is it normal that sammy kernet link is still on 7-19??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
If I am running a stock ROM (Diet ICS) and your sammy kernel (7-18 as I had audio issues with 19c) can i use one of the other up to date kernels with my current rom to benefit from the new changes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No, wont boot or even work. Totally different animals.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
7-19 is the latest kernel for Sammy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EthanMG:
yes, ktoonsez hasnt been able to merge the new changes into the sammy kernel successfully yet. when he does, hel update it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Still no love for stock users?

[Edit] Never mind, the answer was posted while I was posting this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Which one did you flash? Aosp jb?

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If he's running mine and tasks AOKP-Jelly Bean then its JB, if he is on ICS AOKP/CM then he's on AOSP. They can not be mixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sultanqasim:
This is a truly superb kernel. It is rock solid stable, super fast, and gives outstanding battery life. With this kernel, I'm getting better battery life in CM9 than the stock ROM and kernel, even though I have set the Max CPU frequency to 1890 MHz, plus the amazing performance from overclocking this already super fast phone. Thanks so much ktoonsez!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theMAGNUM:
I'm not seeing anyone having this issue however, does anyone have issues with random icons and text blinking on and off randomly? I've had this issue with both AOSP ICS and now JB with this kernel. When I don't apply this kernel, I do not have this issue.

I installed the kernel, wiped cache and dalvik, and fixed permissions. I have been using task and ktoon's ROM. I have utilized voltage control but that has not fixed the issue. I have also wiped everything re-installed the ROM as well as the kernel and I still receive the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polish_pat:
im stock and i use sammy kernel. IM OCd to 1.9Ghz and still get a full day of mild use and have over 45% remaining when i get home around 10pm

This using in conjunction with CPU sleeper
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man, love hearing that :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Umm will this work on my captivate running cm7:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Only on wednesday's :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
God bless you man, I dropped a 6 pence in your thanx box.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neubauej:
But of course! You just have to flash a froyo secondary bootloader first!

:D

Awesome kernel!

I'm hesitant to report the following possible bug as I'm sure the answer is "well then don't do that" but here it is anyway.

I'm running the latest AT&T stock ROM deodexed and the jb domination theme. With your latest sammy kernel I get an "SD card damaged you may need to reformat" message upon every boot, yet all the info is still there and accessible.

Switching to that other kernel or stock and its fine.

Its also fine on aokp both ics and jb (excellent work there too btw!)

I did a full wipe back to stone stock, and was able to reproduce it.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Format card to fat32
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
hey man, which side is the theme chooser usually from, yours or the ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Take it to Q&A.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Haha that's funnie
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Believe it's ROM side... systemui, framework, etc, etc...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Hey ktoonsez. Can this kernel intervene with the gps? When I flashed the new jelly bean aokp last night I got an instant lock 3seconds. Today I flashed your latest update and the gps takes much longer. Not sure why this is happening. I did experience the same thing on cm10 when I flashed your kernel.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Thanks bro, that's what I was thinking, but I seem to remember getting themes capability on sgs2 when ktoonsez became involved. So I was thinking it came from kernel side...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Kind of a valid point though - can't expect the noobs to follow the rules if we don't :D

"From you, alright? I learned it from YOU!"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It isnt kernel, but yes it was me that got stuff working on AOKP ROM code :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Only on a driver level and that code is untouched. Whatever you are experiencing is the area or tweaks that need to happen in the ROM. JB is experimental so dont go into the AOKP thread and ask there :D