yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
That's where I had seen it but couldn't remember for the life of me where exactly that was.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
heres the post u guys are referring to

https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
The battery self calibrates so sometimes will not give tottally acurate readings, but will be close. Sometimes it will reset like 30% when you reboot... that is a BIG self calibration.

It does sound like you've covered all the bases. If you are draining battery fast and OS Monitor doesn't show anything running hard, then it sounds to me like you just have a weak battery. See if you can get ATT to give you a new one to try (by complaining that Verizon is looking good?). Or maybe just get one of those hopped up super bats!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djtiko:
So I'm at 35% now with 5 hours and 20 minutes of usage and 2 hours and 5 minutes of screen time.

Its still my first charge cycle though so after the next few hopefully it will get better.

Most of my on screen time is using Google chrome. So maybe that's killing my battery more vs using an app that doesn't require data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
From what I understand, Chrome is a hog. Not sure on that one. Have you tried taking it up with the dev or searching around?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
If you haven't been through a few cycles then just wait, but if you do want more control and the ability to see how much juice you're using, get ES Task Manager to monitor and control what runs. It has a startup manager that I use to stop all sorts of things from starting up at boot. You'd be surprised how many things are running in the background. And with a little app like Cool Tool, you can use a small graph to show the CPU speed in real time. I have caught things running in the background keeping the CPU pegged several times. You can tell at a glance if you are at idle like you should be, and kill the offending app if you are not.

2 hours screen time is as much as some get out of a battery... but if you just like to see what's going on with the phone, these apps are cool.

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
So I have a couple profiles in SetCPU that use ktoonservative and one that uses smartassV2. Am I going to be negatively affected by having qosmgr disabled with smartassV2 since the OP specifically says to disable it for ktoonservative?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I don't think you are really supposed to be usingSetCpu with Ktoonsez's kernel. You should use the Ktweaker app that comes packaged with the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I believe you can use tasker to do this. I'm not sure having qosmgr disabled will affect anything but then again it has to be there for a reason lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] muqali:
Yea, considering it comes with the kernel and provides the same or more functionality. The only difference would be learning a slightly different interface. But the terminology is similar enough to make it easy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Actually setcpu has better profiles functionality (like change governor for certain apps) that ktweaker doesn't do. But it certainly has enough to suit my needs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Exactly, I'm using SetCPU for the profiles. So far it seems to be getting along with KTweaker just fine. My concern is just that using a governor other than ktoonservative in certain profiles without qosmgr might cause some problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
What does qosmgr do exactly I have just edited it as it says to in the op, bit was wondering what its function is and if I do use another governor can I change it back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I don't know exactly, but in a router QOS (quality of service) deals with prioritizing traffic. For instance, if you want VOIP data to have priority over BitTorrent traffic, QOS can ensure adequate headroom for VOIP when the pipe would otherwise have been flooded by BitTorrent connections. So I'm guessing qosmgr has to do with prioritizing threads and whatnot in conjunction with the stock Samsung governor (pegasusq?).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The quality of service guess is NOT

what that ended up being. The qosmgr service ended up being a service to help control CPU hot plugging. Thats why it ends up screwing people when they are on a gov like mine that controls hot plugging within the governor
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Isn't ondemand what Samsung uses?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I'm not absolutely positive but I think that the Pegasuq governor is either the same Samsung governor or very similar to it. Correct me if I'm wrong please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pellel2:
I'm trying to use ez file explorer to rename the file but I get an error. Any suggestion?? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Thanks for the info man seems to have tamed the drain some I think I still need to cycle the battery a couple more times not quite getting the battery life I was on stock samsung kernel but I remain optimistic
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
For anyone else on cm10.1, the experimental build of ktoon works perfectly with he f4th experimental build of 12/29 cm. So glad to be running ktoonsez kernel again, thanks for all the hard work and hope you had a merry christmas/happy holidays.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] picklerick:
you have to remount the /system partition as RW before renaming the file and then set it as RO after
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Ok so after changing changimg said file to a .bak extension and clearing cache, dalvik and fixing permissions and my second baterry cycle. Seems to have completely fixed the drain and so far its perfect. I have not messed with the voltages or overclocked and ay this point I see no reason to......great work.im not a fan of tw bu t I am inable to run your aokp kernel but this is pretty smooth :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
You tube videos and my gallery videos won't work with the 12/21 kernel on CM10.1 12/29. Everything else is smooth

Edit. Meant to say 12/20 kernel. Found the 12/21 and it works great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Very interesting. Thanks! So if qosmgr is disabled would it be advisable to avoid using pegasusq? Are there any other governors that depend on this service that you know of?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
Sorry to bug, but what page can I find the link to the 12/21 experimental build? Tapatalk search sucks :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Browser -> Google -> use XDA and Ktweaker as search terms -> profit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
Yeah, thanks but no thanks. Searching Google xda ktweaker doesn't help... Even including experimental 12/21 doesn't get me anywhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
Thought I'd give you a break.

But it took me 20 seconds to find!

http://xdaforums.com/showthread.php?p=35749668

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
Thanks, I usually don't have a problem searching. Maybe it was the dash instead of the slash that caused me trouble idk. Appreciate it bud!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I have not made a list. Ull just have to experiment. I believe pegasusq would want the qosmgr disabled
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
********* OP Updated - AOSP 4.2.1 ONLY *********

********* OP Updated - AOSP 4.2.1 ONLY *********

Change Log

1. Fully synced with CM 10.1 code

2. Data is BACK on CM 10.1!!!!!!!!!!!!!!!!!!!!!!!

3. Fix some issues with smartassV2

4. BFQ v5r1

5. Newest KTweaker 2.3 included

6. Im sick as hell with the flu so thats the end...

ENJOY
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Thanks man get recovered :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Hope you feel better man thanks for the update :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geomax45:
Liquids, rest and a bj...

Call me in the morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benefit14snake:
Anyone having touchscreen problems with the latest release? I'm using tasks aokp and I've wiped twice, downloaded and flashed twice.

I just flashed back to the 12/20 and the problem is gone.

Sent from my T999 GS3 @ 2. 1GHZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
Thanks for the drop. Get over your holiday-itis soon. Hate for you to be stick bringing in the new year.

Sent from a Horny Pink Pony
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
This might not work on mine and tasks AOKP. He has been sick as a dog like me and AOKP is being a pain right now but is being worked on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Possibly because it's AOSP only?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I am on AOKP with the kernel that was just released, and have not had any issues yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
I am having issues as well. Scrolling will go the wrong way sometimes and sometimes the screen seems a little unresponsive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
I'm using newest KT with cm's 12-29 nightly and have had no issues..thanks for the update ktoonz :):thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Get better man... and thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
Noticing this myself. Happens more often when making several small swipes up or down while scrolling.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I correct my previous post, I have also started to notice this on mine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Data is fixed, thank you Ktoons!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
CM10.1 nightlies fixed the data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well the bluetooth bug in 12/29 is still present on here. Garbled audio after a period of time seems to happen no matter what. This is with 12/21, 12/29 KT kernels AND 12/29 10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Just searched and no answer I can't back up my settings on tasks Rom any ideas why? I get this error
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Having the scrolling issues here too. Aokp kernel coupled with cm10.1

Edit: reverted back to 12/21 kernel and scrolling issue is gone. Tried stock kernel from cm10.1 and scrolling was fine also. Reflashed 12/29 kernel and scrolling problem came back. Its not a terrible problem but does seem to spawn from the latest edition of the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
This is running great on CM 10.1 12/30 nightly. Tested most things but not BT. Audio, video, data, GPS all seem ok. Feels really smooth. Thanks! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
is the 4.2.1 kernel cwm flashable

don't call me a noob or anything, im just being cautious. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
If it wasn't it would just fail when you tried to flash it and nothing would happen.

---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
deleted due to a technicality
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
This part of your statement is NOT true for me:

Tried stock kernel from cm10.1 and scrolling was fine also

I see scroll issue on stock and mine since I synced up with CM 10.1. Im testing with CM 10.1 12/29.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
What governor are you guys using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Ktoonservative. SIO scheduler.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Switch to interactive and see if it goes away. I bet the problem goes away :good:. FML!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
You are correct with that. Switched to interactive and have tried swiping around for a couple minutes, and it hasn't done any of that anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Yes Was using Ktoonservative and was having troubles with keyboard and touch :D now interactive no problem :D:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Maybe it takes awhile to appear. I flashed cm10.1 booted up opened twitter and scrolled around and it was smooth then I put your 12/21 kernel on and it was still smooth. And now its still smooth. Using 12/29 cm10.1 also.

Gonna reflash the new kernel and screw around with governor and scheduler. I was on ktoonservative/sio before
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Look above. 99% sure it is ktoonservative. SMP in 4.2 is all f..ked up, I think it is only my gov that is doing this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Yep you read it before my edit.. Put the new one on and switched to Pegasus and all is well. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I tried all the governors and it only does it with ktoonservative. I hate using interactive because it keeps the CPU at a high frequency all the time but I have no choice now. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
The scrolling issue is with on-demand too can't test more cause I'm working

edit snuck away and all of them are doing it.

Swype isn't responsive like it was before also
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yep, it appears so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Sio and interactive fixed the issue for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flak0:
Hope u feel better man. Any TouchJiz JB for tmo 12-29 KT?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
On my phone, Pandora does not play and crashes with the 12/29 kernel. If I go into recovery and flash your 12/21 test kernel it plays like it should. This is with the 12/30 nightly. I had the same issue with the new kernel last night with the 12/29 nightly. Bluetooth audio is borked on the latest nightlies for me regardless of the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
I'm having no issues with scrolling or touchscreen accuracy/responsiveness on AOKP 12/23 with ktoonservative and zen scheduler.. Am I lucky?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes you are, it is something with SMP functionality, basically the 2nd cpu keeps going on and off every 1-2 seconds messing up interupts (like scrolling or typing). I will try zen scheduler and see if it does somehow cure it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I believe it only seems to be an issue on the 12/29 JB AOSP with ktoonservative.

Edit:

Ktoonservative with zen definitely still has the issue for me on 12/29 AOSP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
That's what I meant..sorry for not being more clear. I'm using this latest 12/29 AOSP 4.2 kernel with task and ktoon's 12/23 AOKP release..haven't really noticed any issue, but maybe I'm not doing anything that would make this happen. After I read the last couple pages, I went and tested out scrolling through contacts, messages and home screens..didn't notice a thing. Can't test it out further for a while though as I'm at work :p

Just sharing my experience! Excellent work as always on this kernel! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoestar:
Try AOKP, no issues with Pandora here. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crazililazn:
I was reading through some VRZ GS3 threads and I saw that one of the devs, ziggy471, was on the verge of getting exFAT working in his kernel.

http://xdaforums.com/showpost.php?p=36060110&postcount=12564

Any plans on incorporating exFAT support if his methods are confirmed to work? Or are the VRZ and AT&T implementations of exFAT different?

Here's another update from the dev: http://xdaforums.com/showpost.php?p=36080282&postcount=12582
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I have been getting some kernel panics recently on AOSP 12/29 JB with the reason as "L1 cache error detected" . Is this caused by undervolting too much, or is this something else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
99% sure thats too much UV. Not enough voltage can corrupt memory.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
Sooooo when is a ROM coming? :D

I can't even judge battery life. I tether all day at work (HSPA+) so I stay plugged in. But it is smooth.

What governor is everyone using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
whenever you decide to build one. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
"Pay no attention to that man behind the curtain"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ill add it to the list of things to look into.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm on your list. :highfive: look into that. :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
that is a VERY LOW SCORE for 1890 MHZ! :confused:

I get 6900 points with 1512mhz!!! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I got some changes for today, if time permits. I modified initramfs to default the mhx back to 1512 stock so the people that dont have the knowledge can be at stock speeds and the rest of you can OC if you want :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
thanks a lot for taking this request into consideration :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Amazing thanks bro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
just say it dude. you know you want to. lol :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
Woah....New XDA theme is very....Touchwiz-ish :laugh:

I'm loving this kernel. Can't wait for some good roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
I just shot hot coffee out of my nose. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Vacation

Just a heads up guys, I am going on vacation from Thursday to next wednesday and will be pretty much out of touch. Pass it on so people arent wondering where I went.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
CPU1 disabler while in sleep

There seems to be some controversy as to whether that helps or not. I have no idea.

But if it does, maybe incorporating that may be an idea to consider. Or, of course, we just implement it ourselves.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes of course hotpluging is on my list, havent even looked into it so it may already be in there for all I know
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chopard:
Not sure what's wrong but I'm getting battery drain... Maybe my CPU settings but I just went back to the 7.8.12 for now. If anyone would like to share what they are running would be greatly appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
​

​

less likely to me missed:cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ohcie_evo:
has anyone got their init.d setting to stick, any help would be appreciated. thanks

for anyone interested, I had to increase the sleep time to 30 for the settings to stick after boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No worries. I'll be trolling your thread. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amgpower63:
Which governor and other settings are you using? Mine doesn't last like your phone...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
That does seem to be it, I cannot reproduce it on stock voltage, so I guess I just need to tweak my voltages again.

My current ones were stable for at least a month, but maybe the rom change triggered something to change a bit.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yep, it will be in flux for a while I am sure. I can run crazy LOWER voltages and frequency steps with 4.2 vs. 4.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] redrider54:
scrolling issues and YouTube video playback issues rolled back to the dec 20 and no issues on ktoons 4.2.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
12/29 4.2 kernel running great on cm12/30. No data issues and super smooth :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Menu>settings>system>notification drawer>power widget

Or

Menu>settings>system >quick settings panel. Whichever one you prefer. I like the newer tiles layout.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
OK, just because Task's thread has been locked for the time being, doesn't mean we will continue the off topic discussions here... Please stay on topic. This is a development/kernel thread, not a "how do I do this in 4.2" or "I like this better than that" thread.

Please keep your comments or questions relevant to the topic at hand.

Thank You.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Sorry. I was just trying to help em out. It shoulda been posted in another thread though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mtnichols04:
Thanks for the awesome update, get better bud, have a happy new year.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Any idea why the 12/21 test kernel fixes the streaming audio problem (i.e.Pandora crashes the system) present in CM10.1 with the stock kernel and your 12/29 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
Something must have broken it in the newer updates, because if the 12-21 kernel fixes these problems I'm switching to it right now to test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
My guess is Pandora is incompatible with 4.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
But it DOES work with the latest CM10.1 and your 12/21 kernel...

---------- Post added at 11:32 PM ---------- Previous post was at 11:30 PM ----------

Did it fix it for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Because 12.21 was not a full AOSP 4.2 kernel yet, it was still in its transition stage. Lots of google sound/soc updates since then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoestar:
Run AOKP, Pandora works great here.:)

Dual-booting would be awesome, but I got to thinking about it and doesn't sound feasible for this phone as it did the S2. With the S2, you could use the same kernel or TW & AOSP based ROMs. I don't see that being possible here.

I'm a flashaholic and I tend to get bored at times and just want to try something different.

I love this kernel setup with AOKP, it just saves so much on battry life. Surprisingly, I get better benchmark performance out of TW. I can almost hit 13k, while on AOKP, I might break 11.5k.

Anyways, keep up the great work man and hopefully you will get your personal governor worked out as I like it the best. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
LOL!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hokiemoto:
ktoonsez,

In governor adjustments for Conservative, sampling_rate and sampling_rate_min don't stick/save. Bug or is that on purpose?

(ATT, on latest of your TW JB version)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Anybody have the 12/11 release? I wana test something