yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
1512 is clearly used in the upper area, no need to worry about the lower area, it is picking up on the fake OC steps I label as 1512 for people that dont OC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Not for us end users ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jriv:
+1 4.2 is sweet as long as you don't have to dev for it

sent from a guy living in a van down by the river
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rekzer:
Ah i see, so nothing permanent is really affected here then. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
You're the man.

That killed those errors with KT governor :)

---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------

i had the same issue with watching netflix using KT governor.

video and sound was so lagged it just stopped playing and started buffering. To fix i had two choices that worked. hit pause every 20 to 40 seconds and then play (it would play for like a min and start again) or switch to stock governors and setup (load defaults) -- although even with defaults it still lags just a tiny bit, but acceptable..

ktoonsez any way to fix that lag you think?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Ktweaker is crashing on launch on the newest 10.1 nightly. Just thought i'd let you guys know. good luck ^ ^
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
It's not crashing anywhere else. Try clearing ktweaker's data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I'm running the newest kernel by Ktoonsez & the newest nightly & Ktweaker isn't crashing for me. Try clearing the app data like the guy above me said.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
This was happening to me aswell but I reflashed 01/05 and then the kernel and it works now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Clear it's data, it should work right after that, or like erbsmokah said, re flash.

I wanted to mash your thanks button for your signature but alas, I have hit my limit of 8. You had me laughing in stitches!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Great sig lmao
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
TEST Kernel for those that say ktoonservative is lagy in 4.2

http://www.mediafire.com/?25rr4xrtc40t2d1

Let me know if anything changes for you, since I can not reproduce it at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I like lagy. ;) :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
FLOAM, me too :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Ah sweet trying this out now I'll write back in a little bit. I do have a small bit of lag with the keyboard and other things but nothing serious. Its almost unnoticeable

Edit: seems flawless now! Using ktoonservative, row, no OC, stock touch boosters, screen off 486
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
I am testing this right now. I had some pretty bad lag on the previous kernel even after your suggested fix. Thanks for this and I will report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I've been running it for about 25 minutes now playing Modern Combat 4. When I played that game before, it would start the lag or whatever almost as soon as the game started. I haven't been able to reproduce it with this kernel so far. I'm gonna keep using it and if I experience what I was experiencing before, I'll let you know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
This new kernel is running great with absolutely no lag. I am currently running ktoonservative/ROW with the touch boosters off and was wondering if this would be better for battery life than having touch boosters on? Thanks again for all your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Only problem is, it keeps hotplugging like 2 kernels ago and is gonna kill battery. Looks like this test is a bust, yes it will be faster but chew battery like interactive :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Hm. Just the governed is ? Would switching back to on demand/sio for now be alright with the 1/5 test? Or will battery still get slain?

Edit: just watched In KTweaker with ondemand and ktoonservative switching from 1 and 2 CPUs like every second or so
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ktoonservative will always be better than any of the others since they hardly hotplug at all. Im just saying that ktoonservative wont be as good on battery as the previous version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
hey ktoonz..how come interactive (for me at least) seems to be so much better on battery then it ever was before?..10 hours overnight sleep and I only lost around 0.6 a/h..works much better on 4.2 then I remember on 4.1..also using sio..1600mhz-96mhz-50mv UV..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Interactive was specifically designed for 4.2 by google. Thats what is the default gov 4.2 for google. I am really surprised that interactive has given such good battery since it over-reacts to everything is is very yoyo'ie when it comes to Mhz and doesnt hotplug at all, its very weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
Do you know if the Kernel is responsible for the Low In-Call Audio, and if so, would your latest be able to fix that vs. the Stock CM10.1 kernel? If this is already known, I apologize.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
so this is weird,

on the 1/5 kernel, once installed the same errors started spewing out.

moved mpdecision to /system but errors still continued.

rebooted and errors are gone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
What about the continuous hot plugging?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Not weird at all.

You followed the instructions and it worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
That's still there add koontz said

---------- Post added at 11:35 AM ---------- Previous post was at 11:35 AM ----------

Read my post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats NOT weird, you need to reboot after renaming:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The 1/5 will hotplug alot as I stated so I will have to revert that attempt at making it snappier. Most likely it will just have to be tweaks to the Adjustments of the gov.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Gotcha. I totally read his post out of context and thought he was talking about that and not the mpdecision error logs. My bad! :banghead:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Camera conflict problem (I think)

I am having some issues with reboots on this kernel. I am running AOKP 1/4 with the 1/1 JB AOSP Kernel. I run an app called smartstay ex which replicates Samsung smartstay on other roms. It is set to scan every 30 seconds, but if I am using the camera app when the scan occurs, it causes a hang and reboot. I have tested this on the kernel provided in task's aokp and this does not happen. I have attached the last_kmsg from after this occurred, the error seems to be "msm_ioctl_config: no active pcam instance." I am running ktoonservative/row. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Been using latest version and since 1/1 and also 1/5 no problems at all using ktoonservative and ROW and -50 and all speeds and NO Random reboots excellent battery life in conclussion very good :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rapproduca:
Does anyone have a mirror for 1/1?? The. mediafire link gets to no more than 5% and quits
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Attached.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Never seen that one before, Ill look around the code
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rapproduca:
Thanks a bunch!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
FYI, I can also reproduce it on conservative/sio with stock voltage, so it doesn't appear to be related to anything specific in my settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
which kernel?

So which is your best kernel out right now, the 12/21, 12/29, or 1/1. Did you write that the 1/1 has a bunch of debuggers in it that might slow it down or was that something else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Everything ive read and experienced points to 1/1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes u want 1/1:good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I've been using 1/5 all day today, watched Netflix with KT/Row UV -50 (you're recommended settings from few threads ago) and had no stutter our lag. Now you said its hotplugging like yoyo... I see that but still my battery life is not that bad, so far better than average in the past. With 1/1 KT/row would stutter when I was watching Netflix....

I guess all phones are not created equal. Will wait for the next one to try out but I'll stick with yesterday's kernel for now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ya, Im toying with the idea of adding a config item to let u guys choose from the 2 different ways, the current 1/1 way and the test way from yesterday. That should make everyone happy :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benefit14snake:
You are way too good to us. :D

Sent from my T999 GS3 @ 2. 1GHZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djtiko:
I have two questions just so I can understand better.

My settings right now are Ktoonservative, Noop. I have my clocks from 192-1512 and UV -100 across all steps.

1- I have touch boosters set on default values and I noticed a lot of people on here do too but if you disabled them wouldnt it save battery so your phone doesnt jump to 1124mhz every time you touch the first time? Like wouldnt it save more battery having it disabled so it doesnt jump everytime you touch until you load an app that requires the speed jump?

2 - Since my frequencies are from 192-1512.. is there a point to set a screen off profile? I noticed everyone setting it to around 484 mhz but I always assumed with my screen off it would just stay to the lowest frequency at 192.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I know that you asked KT, but I thought I'd add what I've found.

1. I disable the touch boosters without a lot of noticeable lag, and yes, it seemed to save a good bit of battery, especially when I am just reading and scrolling.

2.The screen off setting is a maximum. It will stay at 192 if nothing is going on. I jumps to 486 if something comes up instead of jumping to max of 1512, or whatever. This theoretically saves some battery since MHz is a square function in the power used equation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Been having a little ktweaker problem on 4.2 with ondemand

I set my screen off to 486, then when I check in ktweaker, my governor adjustments don't match, namely 'boost_freq' is still set to 486000 (which I believe is suppose to be my max freq which is 1512). This happens about 80% of the time.

On 4.2 12/29 kernel. Tried reflashing, clearing ktweaker data, anything else I can try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Just flashed this kernel on cm10.1 (haha 10.2) from today

I just upgraded from cm10 and performed a clean install everything wiped.

is it normal for benchmark apps to crash with this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yeah. I think so at least. They crash on my phone when I try to OC any thing above 1998 I think it is. I figured that my phone just couldn't handle that much OC. I think that 2106 is the only frequency that my phone will crash at & I haven't done much research but I think that it only crashes during a benchmark. It will run most other apps & games just fine. Still an awesome kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Where can I get this? Is it Android 4.3-based?

:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Close, its the new Android 5.0, just released and hot off the presses:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Lil wow I'm shot sorry I meant 10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Im pretty sure ktoonservative is setup to keep your cpu on the lowest frequency steps as much as possible to save battery. The touch boosters are there to jump start your phone so that it doesnt run lagy from idle. So yeah i guess you could save a little more battery at the cost of performance..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
I always use KT kernels on whatever ROM I'm currently trying and have recently switched to newer 4.2.1 ROMs but think I should maybe wait until more bugs are worked out.

Anyways have been on task's/KT 4.2.1 AOKP ROM and thought it was ROM that was causing occasional instability and reboots...but I have since tried others ROMs and same issue...but if left on stock kernels its okay so I *now* know the one common variable is the newer mr1 jb4.2.1 KT kernels.

And for 4.2.1 I haven't done any of my usual tweaking (yet) for UV and oc, etc..

So is this more common lately? Still being worked on or just hit and miss? I get total freeze and then reboot with camera app a lot on task ROM with this but also on other ROMs too but not as much...and just random reboots about 2-3 times a day on various ROMs while doing nothing or simply writing s text or viewing webpage...

Like I said...love KT kernels and always prefer to use them. Should I just hold off on 4.2.1 ROMs and this latest kernel for a while? Or anything I can do? Would any logcats after the reboots help at all? FYI I have 4 different S3's... 2 CA 747M's and 1 US (AT&T)747 and 1i9300 Intl..I only use the ROMs n kernels on the 3 north american models and same issues on all 3...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
Just reporting an issue... im assuming its kernel related because its hardare linking failure, i could be wrong. for no reason at random moment, my phone lose all input from touchscreen. Hardware keys still works, home, power, and volume rockers... needs reboot to get touchscreen to work again. Android still works normal... only touchscreen that fails.

im using ktservative+Zen normal voltages + aokp 4.2.1 1/4 happened twice in 2 days...

Ill try flashing 1/1

Sent from my toaster
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evolution36:
tried flashing this last night on CM10.1 and got nothing but reboots and freezing. Something I'm missing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Were you sure to flash the 1/1 build and wipe cache/dalvik and fix permission immediately after?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Seems to be running fine for me w/ the 1/8 nightly. I updated this morning & haven't had a reboot or freeze yet.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evolution36:
I'll update to 1/8 tonight and try it out. and yes I wiped cache/dalvik and fixed perms. got nothing to lose though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
********* OP Updated - AOSP 4.2.1 ONLY *********

Change Log 1.8.2013

1. Added Yoyo mode to ktoonservative (mimics the test from 1/5) and is DISABLED by default

2. To enable yoyo mode, set "use_yoyo_cpuload" to a 1, I recommend setting "cpu_down_block_cycles" to a 22 or 44.

3. You can enable yoyo if you feel ktoonservative is lagy since moving to 4.2. It does jump around the Mhz range and hotplugs the 2nd cpu alot more than normal mode but is very responsive!.

ENJOY!!!!!!!!!!!!!!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
You are the shiznit. Been waiting for your next release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
LOL@shiznit!! Sorry, just haven't heard that in a while. Appreciate the update KT!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kofrad:
Looking good!

Does all the extra hotplugging create any extra power consumption? I know in some instances it can be better to leave something on instead of flipping it on demand. Just curious :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
Can I ask a stupid question? What exactly IS hotplugging? A quick google search makes it seem like it's better with toning down cpu speed or turning off unneeded cores. But when you talk about it here (just taking this in context) it sounds like it's more about ramping up cpu speed. Either way, the 1/1 kernel has been amazing for me! I'm well into my second day on the battery and haven't been experiencing any of the lag others are reporting (though I'm working and haven't been able to actually use the phone much :p ).

Great work ktoonz!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
New ktoonservative is great very responsive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
No more jb tw updates? :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
There haven't been any new changes to apply, so no updates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
I flashed 1/8 and i'm having issues playing videos on YouTube. It starts to pay then the cursor moves to the end of the bar. I can still hear sound but the video seems "paused".

It worked fine on 1/4

Anyone knows how i could fix this?

I tried different governor/scheduler combination and it does the same thing

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats what we are trying to find out. Guess you havent read anything over the last 3-5 pages but people told me they saw no effect on battery so that why I made the yoyo addition.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Exactly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Hotplugging is the turning ON/OFF of CPU cores. The reason I call it the yoyo effect is it turns on and off the 2nd core much more for weird 4.2 reasons. The Mhz is pretty stabilized but does go a little "yoyo" here and there. Turning yoyo off will produce more stable Mhz stepping and very little CPU hotplugging.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zamula:
You could add the ROW scheduler, which would be great!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crash822:
ROW scheduler is already there, it is at least on my phone using this kernel anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
ROW is too cool for Touchjizz, it might melt the CPU :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zamula:
On a 4.1 version of the kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Awesome, thanks!

Can you share your settings file by chance? :good::good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Im on the 1-4 AOKP was running stock kernel flashed today's update and no ktweeker app or widget. I redownloaded and reflashed and still nothing. It showed up in settings and all your governers are there in performance control just no ktweeker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Today I am trying:

"use_yoyo_cpuload" = 1

"cpu_down_block_cycles" = 22
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ohhhhh, you are talking about AOSP, I got you now. No I have not built that one yet, it is in the kernel code, just not built and released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
what is the difference between 22 and 44 for cycles? did you notice anything?

i set it to 44 and i'm watching cpu, and its not yo_yoing not nearly as it did with 1/5 :) it's mostly keeping 1 cpu online while fairly idle...

seems like WIN:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Mine is still turning on CUP #2 every 1 to 2 secs. Off then on then off then on, you get the picture. I have cycles at 22 though.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
44 equals about 1 hotplug ON every 8-10 seconds, 22 equals 4-5 seconds. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
and you're on kt/row?

i think we were testing with those on 1/5 and it was going nuts with hotplugging but again at least on my phone battery life was not that bad, more than average than on stock settigns.

i kept kt/row

(i'm not UV anything at this time)

with YoYo and 44 for cycles.

let's see how she does.

---------- Post added at 02:58 PM ---------- Previous post was at 02:57 PM ----------

ahh :) makes sense so i'm seeing hotplug probably about one every 10 seconds :) better than with 1/5 it was doing that every 2 sec or so

nice, i'll give this a try and report back tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Still wondering if this 4.2.1 job aosp kernel is causing freezes and reboots to others? Happening on 3 phones Im testing...note often in the camera app but 1-3 times a day during regular use.

Anyone?

And KT, should I get a log cat or a last kmsg log after a crash reboot to help?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Ktoonz what do you have your touch boosters at?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Also having this happen a few times a day, but have mostly fixed issues with the camera by uninstalling a app that used the camera in the background. Attached is a last_kmsg from an unexpected reboot that just happened when trying to open the app drawer, but I don't think that had anything to do with it, since it usually happens when idling in my pocket during the day. I am running task's aokp 4.2.1 01/04/13 with the 01/01/13 AOSP JB Kernel (will be updating to 01/08 of both later tonight), if you could take a look that would be great, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats exactly what mine are:good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Last kmesg can help sometimes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
File was empty or scrambled. Not sure what happened there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Did you unzip it first? I tried downloading it and it opened fine for me, I couldn't upload it uncompressed, because it was over the size limit, if it still doesn't work I can try again, just let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I got it open, had to unzip with Winrar instead of Windows. That was odd. The issue could be that you are using the test kernel from 1/1, it floods the log with messages and could be the root cause. You should update since youare about 3 version behind now. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Ok, thanks. Will do when I get some time tonight, as I need to backup and update the rom as well, hopefully that will do it.