yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ohhhhhhhhhhhhhhhhhh, wait. So it does NOT work on BMS either in the 3.4 kernel? But works just fine in 3.0 correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beefgoat:
So far, so good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Dancedance works on easter bms 3.4 however asswax is broken on 3.4 in general. However dance dance pegs for 4-5 min on boot for bms also... It however fixes itself

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats what I see on dancedance on mine too. It pegs for a while then goes down. Also a screen on/off toggle seems to speed it up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok coooooooooooool. Building a test for u right now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Mine continually pegs... Does it auto hotplug? Cuz i had the toggle on that might have been in

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It does not do its own hotplugging and I did NOT have auto_hotplug on when testing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Ill check it out then a bit more

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beefgoat:
I will flash first thing in the morning. I have to wake up in five hours to take my lady to breakfast, and then I'm off to work. BTW, you rock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Here you go, try this one and see if auto hotplug is fixed :D

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

Maybe you can give this a try howtomen since beefgoat is out for the night? Also this one has an upgraded smartass, is now smartassH3!!!!!!!!!! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
No prob broski whats in this new smartass? Ill flash now and test smartass and dancedance to see if it pegs

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Never mind on the smartass, this one does the same thing (or I should say it does the full peg until you turn screen on/off once). Just test auto hotplug and see if scroll weirdness is gone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Pegs and has scroll mess up on smartass... However not on Wheatley... Idk wassup with that

Edit: go to gallery and pinch to zoom and y get scroll weirdness if u continually pinch to zoom... Other than that its mostly gone on all govs

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ya, my phone wont do it, I do use 189 as min, not sure if you are using something like 81 or 135, that could be ur issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
486 always however i have pretty hefty uv to be like 135 lol lemme check on stock voltage

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum

---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------

Actually looking at a logcat and pinching it seems fine on stock table and all the way to -100uv 135 and up seems to be my trouble haha. Prob solved for me at least

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beefgoat:
Your test kernel from last night is working very well. No scroll issues with interactive and hot plugging enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Loving the new kernel! It's been running great on carbon nightlies. I'm using sio for screen on scheduler and noop for screen off, is there a better scheduler than sio?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
ROW has been really popular recently.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Yeah, I believe toonz himself said he uses zen for performance and row for battery.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Ktoonsez what settings do you have for the KThermal Control? Do I leave the stock settings or do you have something else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes I leave them at the settings that I made it with :good:. When I do a benchmark, I add 10 to the 2 temp settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That is correct.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Awesome, BTW the new test kernel is running smooth as butter!! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nomoiphone:
ktoonsez,

Are your settings current?

- http://xdaforums.com/showpost.php?p=28399842&postcount=3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Yes read posts before u please...

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Ktoonz, I'm on the 4/6 kernel with CM10.1. Whenever I try to switch the the thresholds from 57,58 to 47,48 (respectively) it always goes back to 58,58. I want 47,48 because I seems to help with some lag.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
U r setting them in wrong order. Set up threshold first
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crash822:
I believe it was specifically made for mobile devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Scramble screen came back with the latest test kernel I'm gonna turn off hotplug and see if it stops cause that's the only thing I changed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
I can't seem to get KTweaker to overclock my CPU past 1674. Is that intentional? I even set the governor at performance, and it doesnt matter if my MAX is 1728, 1890, 1988. Still won't go past 1674.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nomoiphone:
A simple yes would have been fine, there's no need for you to educate me on how to use a forum. He said his settings were the same but he was going to try some others. I was curious if....Wait, I don't need to explain myself any further.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n023b:
I'm currently using task650s rom but its been buggy as of late closing apps and stuff if I flash this one will I lose anything like bluetooth or wifi or anything else I should know?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
Nope:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Regarding touch wiz and the ktoozeservative gov. Are still supposed to rename qosmgr. sorry to ask but have not been in here for awhile and couldn't spot the answer on my own
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
I am as well and find this kernel more stable than Tasks, which gives me the occasional spontaneous reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
I always am setting up threshold first. Then up threshold hotplug. It still does the samething.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Then you need to change down_threshold before both of them, ups cant be lower downs otherwise the cpu would never do anything but freak out, thats why it wont let you screw yourself, lol. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
If he changes them or tries others hes testing them... The third post are his most recent already tested settings that work great ;) and if ur curious about his experimental settings than ask what hes trying out... The only reason i said that is because lately a lot of people here need to be educated on how to use a forum. No disrespect to u

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Yes and gsiff_daemon
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiredofit:
Over the past few days with 04/05 and 04/06 I've seen major battery drain with the CPU spending alot of time in Max. I can't seem to locate the 0327 kernel for AOKP 4.2 - Can someone post the link? again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n023b:
What are the linux 4.2 versions and how is it different from the 4.1s?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
What exactly do u mean sir, because this question doesn't really make much sense
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n023b:
What are the differences in these? not sure which one to download

JELLYBEAN 4.1 VERSIONS:

AOSP JELLYBEAN: Download CWM flashable zip kernel

http://www.mediafire.com/?99f7dn0gya0bb20

Touchwiz JELLYBEAN: Download CWM flashable zip kernel

http://www.mediafire.com/?1hdtn46pownyynj

Quote:

AOSP JELLYBEAN 4.2 Linux 3.0 VERSIONS:

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

Quote:

AOSP JELLYBEAN 4.2 Linux 3.4 VERSIONS:

http://www.mediafire.com/?cys1d7hp3a2vbjf
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
This is a kernel and there is two versions.. Linux 3.0 and 3.4

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
You have to use whatever version came with your ROM due to other dependencies. 3/17 was the last CM nightly to use the kernel based on Linux 3.0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n023b:
I still don't understand which one I should use. I'm coming over from tasks rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Task's latest? 3.4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n023b:
Yeah just updated it earlier today
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IAmReflex:
Okay download the 4.2.2, linux 3.4 one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Anybody have the Ktweaker Widget freezing? I have it set up on one of my main screens, but every once in awhile when I go check on it, the fast charge option and lock frequencies tabs are blank, and clicking on open Ktweaker won't open it.

Tasks JB 2.2 linux 3.4 with latest KT kernel but it used to happen when I was on TW too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
Great work on this kernel! So far it's the only one I've found for my d2att where everything actually works! I have one, small bug report though. BT audio streaming works fine (unlike every other kernel I've tried for this device save for stock), but I'm not able to get any track info on my receiver. The receiver says "reading" like it's trying to get track info, but none is ever sent. Is this an easy fix? I'm willing to help debug if you'd like. I'm currently running the 3.0 kernel, but BT track info doesn't work on either 3.0 or 3.4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
That's AVRCP. If it's not included in your ROM, you won't be seeing the infos on your BT system.

(Also, some music players don't have it)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I thought this was a android 4.2.2 issue with custom roms, like CM and anything based off of it. Has it worked with other kernels on a CM based 4.2.2 ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
You know, you could be right on the Android 4.2.2 thing. No 4.2.2 ROM has sent track info. The only one that has is the stock 4.1 ROM, but even running Dandroid (which is a TW 4.1-based ROM with the KT TW kernel) I got no track info. I'm using Power Amp which has in the past successfully sent BT track info from multiple ROMs on multiple devices. Also, AVRCP does work. I am able to fully control my phone from my deck's controls, just not display any track info. I mean, it's not a showstopper bug, but really the only thing keeping 4.2.2 from being 100% legit on my phone. Funny thing is that Pandora in BT mode does send track info. Just not mp3s played through Power Amp (or any other player).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Is (U)KSM enabled buy default? Does the KSM toggle in CM do anything considering the kernel's (U)KSM tweaks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Pandora is different. Does the same thing on my end.

And don't mix A2DP and AVRCP. A2DP is the BT transmission. While AVRCP will send the info to the BT system. (very basic description)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
Right, but AVRCP is what allows a remote device to control playback from the source, right? A2DP is just audio streaming with no control. I can control the device, just can't get track info. I've tried several different ROMs and kernels, none of them send track info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbmd:
Thanks KT for another amazing release. The new ktweaker ui is awesome. Thanks again for all the hard work.

sent from Task & KT JB AOKP ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nomoiphone:
It's all good and thanks for the extra info regarding his testing strategy...Makes sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
Will KTweaker send a toast message if device temp is exceeded?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No it doesnt, the kernel takes care of thermal throttling not KTweaker and kernel can not send toast messages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Toonsez do you have any touch wiz kernels 3.0?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
FLOAM, its buried in here somewhere. I believe it was a test release on 4/3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Copy that thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbogdann:
I think last 3.4 kernel is draining the battery more than previous kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats just insane
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I think the sun will rise tomorrow

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jordanetodd:
This latest release, uv'd to -25 across the board, ktoonservative/row, has given me some pretty great battery life so far. Can't complain, I think its just fine tuning at this point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I just had two reboots in a row while I was browsing the Flickr app. I'm not undervolting or OC'ing. Any idea what's going on here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
ktoonzes one question hope you answer me

I'm learning to compile and all that stuff and I did it I have cm10.1 compiled on my PC and I have one question

I have downloaded cm10.1 source and it of course has default kernel

How I can download your kernel source and use it to compile with cm10.1 instead of using cm10.1 default one hope you answer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
That don't make no sense. Each iteration gets better and better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
You are doing it wrong.

Im at 14h since unplugged, 3h screen on time and sitting at 40% remaining... How anybody could ever find a way to complain about this kernel is amazing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Looks like the usual, bad interface between video command in ROM to kernel. ROM will get it sorted out soon Im sure :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
3.0 kernel has had some time to marinate and get optimized. 3.4 is relatively new and needs the same level of tweaking to give you the same experience, I would assume.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I would just do a git clone of my stuff an build seperately, thats what I always do since I build AOKP almost everyday too, just easier to keep with updates and not get repo screwed. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Thanks so much :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Offtopic lol: I'm sad I compiled my first version all was fine and I installed it, get Black screen after Splash Screen so sad :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
So, I started up with the uv now, -25 on your second 04.04 kernel (with the working battery mhz high and low) that's 10 than my phone tolerated previously and still stable.

I'll report back when I finally get it low enough to destabilize.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Not sure if this is a rom or kernel issue. But when I turn on my screen it kind of flickers and you see all these colors. I have to literally turn it off and on and then unlock the screen to get past that problem since it becomes unresponsive. Then it doesn't happen until I turn on the screen 15-20 mins later. I know it's not the voltage because I put it back to stock and it still happens.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I had the same issue, doesn't happen right away but comes up randomly. Try increasing your voltage over stock. Go to a 975 min. That seemed to fix it for me but because it just randomly happened I'm not sure it hasn't actually come back. May just not have happened.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
None of that stuff helps you'll see it will come back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
so then what does help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Patiently waiting for a fix or reverting to 3.0 kernel and compatible rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
It's the first time i've seen it on any 3.4 kernel. And if a phone doesn't take to undervolting very well, increasing the voltage or even increasing the min freq actually can help things become a bit more stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I call that a bandaid it's been present since 3.4 release upping minimum to higher MHz seems foolish I have faith in our devs and the cm team that it will be remedied.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
If you have faith in the dev of this kernel, you might want to listen to his advice that happens to be exactly what rmead01 just told you. Have you tried using 384mhz minimum before calling it foolish? Many people find that their battery life is actually better than it is with lower a minimum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Obviously. I have even tested each governor I have tested adding more voltage I have tested so many scenarios it's not even funny I'm no noob to this.

Ps minimum is 378 mhz :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Guys let's slow down here..

Everyone's phone is different, therefor, what might work for one, might not work for another. Like it has been mentioned so many times already, the 3.4 kernel isn't working great on some phones still. If that's the case, feel free to go back to a 3.0 version (or try to pull logcats).

Now, let's all be happy :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
I've been running my minimum at 500mhz, otherwise sometimes the phone won't come back out of sleep.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phantomofheat:
I was having the wake lock issue also but that is the Rom cm 10.1 4/2 is latest that I have found with out the issue for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
It was happening to me on multiple ROMs if I set the min mhz too low. Cranked it up a little bit and I'm sitting at nearly 3 days of uptime now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Ktoonsez, just wanted to say I'm digging the new nightmare governor. Ktoonservative is giving me random but seldom black screens. Nightmare has been a good compromise with performance and battery. I only wish I knew what it's bazillion parameters do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
First thought is the new Ktweaker thermal throttle in extras at bottom. If its in your kernel version raise the two temps to see if that was all or at least watch the temps to ensure your lower at the time your checking MHz :) temp reading in thermal section in extra and in general section if its in your kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I can't find any specific info on nightmare, but the tunables look a lot like Pagasusq to me.

http://xdaforums.com/showpost.php?p=24233103&postcount=3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MorphiousGX:
I agree with BWolf and many others that keep emphasizing that not all phones are the same.

Rules of Kernel Testing:

DO NOT UV or OC right off the bat. Just use the default tables and default governor/scheduler to make sure it runs stable.

DO NOT use old settings (as in KTweaks) by loading the file. They may not be compatible. Best bet is to apply the settings manually, then saving them yourself. Unless you know they work with the new release.

Make sure you do test and can reproduce the issue at least 3 times before reporting it. It's a waste of everyone's time if you report something that could be a small glitch and before you have solid steps to reproduce it

PATIENCE :) Ktoons is a human being with a life too. He does this in his spare time. Be grateful.

I am sure that Ktoons has done a superb job testing each kernel release, and also testing with a small subset of users before he releases.

So relax and just let the man take a breather so he can get refreshed and continue his good releases :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Is there any way that we can compile the kernel for ourselves with all the newest CM updates and such?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
now justin i know ur not new at this as well as u know im not new also and upping ur minimum to 486 or 378.. i personally do 486 is a lot better for ur phone and for the phones battery life... the task gets completed faster at 486 therefore ur phone goes to sleep sooner saving u battery life and ur phone is always much more responsive... possibly solving ur issue... i think that ur phone doesnt handle the low min settings... upping the min isnt foolish its smart... i got the tip from entropy and its solved all my issues and i keep using it on all my devices. and the cm team wont solve... the min for their rom is 384.... because they know lower is unstable for a lot of devices.

---------- Post added at 04:13 PM ---------- Previous post was at 04:13 PM ----------

clone the git repo and compile urself... by merging in the cm updates... but u might break stuff if i dont know what ur doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Ktoonz, got a question for ya. I'm starting to think that SetCPU is responsible for all the reboots I've been having. I know it's not recommended, but until recently it got along with KTweaker just fine. The killer feature of SetCPU is the profiles, which allowed me to have a profile for charging, one for unplugged screen on, and one for unplugged screen off. Is there any chance you'd consider adding something similar, maybe just an option to the screen on/off Mhz settings that allowed them to be activated when charging/unplugged/both?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I was using setcpu also but stopped because the profiles were actually causing the phone to lag especially when turning the screen back on. Good thing ktweaker has a screen off profile which is all I really need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
*chirp* *chirp* I can't believe how quite it is, everyone is enjoying their nice stable kernels :)

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cowhow:
Hey, I'm happy as a pig in a mud puddle. I dropped this into CM10.1 04/09 nightly and I'm good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Had a my phone go randomly haywire today.. Ktoonservative/ROW. For some reason the frequency was staying pegged until the phone got too hot and rebooted.. Not sure what caused it.

Tried switching governors back and forth and it eventually settled down. Didnt get a kmesg log :(

I know this doesnt help much but I thought I would share anyways. My phone is usually very stable this is really the first hiccup I have ever had.