yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jamesino:
If I understand correctly, the interactive governor ramps up instantly to max clock rate when a load is placed on it and stays at this max clock rate for x amount of time before stepping down right?

Where in the Ktweaker governor adjustment settings dictates how long it stays in this max cpu state for? Is it safe to adjust this to be longer if I would like it to stay at the max cpu state for long time?

Edit: I noticed that when I switched the timer rate on interactive from the default 20 000 to 10 000, scrolling up and down pages in apps became much smoother. Previously, in apps such as Gmail or the settings menu, the scrolling would occasionally jerk towards the end as it began to slow down. I'm thinking this was because the CPU began to step down the clock rate before the page was down scrolling? Does it make sense that when I decreased the timer rate, the smoothness would be gone because the governor is sampling more frequently and choosing the proper CPU clock rate?

Are there any downsides to decreasing the timer rate? More battery consumption?

EDIT 2: I changed the default timer_rate setting from 20000 to 10000 and noticed that the scrolling of pages became a lot smoother. However, every time I boot up, KTweaks says "Your saved CPU governor adjustments does not match current, apply CPU governor?"

What does this mean? Is current refering to electical current? Will this damage the phone?
[Verizon Samsung Galaxy S III] jzd5032:
I'm probably completely wrong but by "current" I think it's referring to your settings at that very moment. That it doesn't match your saved settings.
[Verizon Samsung Galaxy S III] sipock97:
Yeah, I get the same when I change a setting from a saved file. It is referring to current settings not electrical current.
[Verizon Samsung Galaxy S III] Neverendingxsin:
I'm still getting major graphical glitches on the 4/7 aosp kernel. Stock voltage and all governors. Went back to stock cm kernel until it's fixed. I'm on the latest Rootbox 4-5 nightly
[Verizon Samsung Galaxy S III] Äptiva:
Just wondering if it's my build or not so I'm posting my question here intentionally.

When running @ 1890MHz, is anyone else having an issue with the camera?

If not, what are your settings(Voltage, Governor, and Scheduler)?

I just got this built from source for d2cri (Cricket S3 which we had no build for) and I've noticed that at 1809MHz everything is fluid with no glitches or FCs. At 1890MHz, the camera won't work but everything else does where as if I step up to 1998MHz the camera works again, but the phone becomes super unstable no matter what the voltage setting is and 2106MHz just freezes like crazy even @ 1400.
[Verizon Samsung Galaxy S III] masri1987:
Getting graphical glitches on latest cm Nightly with this kernel
[Verizon Samsung Galaxy S III] srs731:
So wouldn't just running at 1809 make the most sense and forget about anything else since it runs "fluid"?
[Verizon Samsung Galaxy S III] jamesino:
I'm on interactive on the latest v3.4, my CPU only spends time in the max 1512 Mhz, 378, and deep sleep.

Is this normal? Am I incorrect in assuming that interactive slowly steps down?

Also, is interactive the second fastest governor after performance? Or is there another governor that offer better performance than interactive?

I've been tweaking the governor adjustments by reducing the timer_rate from 20000 to 10000 and reducing the go_hispeed_load from 99 to 80 and it's been pretty fast.

EDIT: actually, you can experience a similar improvement in performance if you leave timer_rate at 20k and instead just drop go_hispeed_load to 50. The previous configuration caused the clock rate to constantly jump from 378 to 1512 and back even when the screen is completely idle.
[Verizon Samsung Galaxy S III] shawn01:
So I have a kernel wake lock of powermananagment services. They have started up like 2500 times in 8 hours.. How do I fix this. This isn't kernel related is it?
[Verizon Samsung Galaxy S III] thornev:
post deleted. I misunderstood the question I was answering.
[Verizon Samsung Galaxy S III] ktoonsez:
Yes its normal, thats how interactive gov works.
[Verizon Samsung Galaxy S III] ktoonsez:
Unplug your phone :good:
[Verizon Samsung Galaxy S III] shawn01:
Sorry I'm not understanding.
[Verizon Samsung Galaxy S III] ktoonsez:
Powermananagment activates when its charging or hooked to USB, so unplug your phone. If it isnt plugged in then you go something stuck in the micro port or maybe something bent.
[Verizon Samsung Galaxy S III] Äptiva:
This isn't what I asked. Another user on our forum had this issue and I was unable to recreate the problem myself. I was just wondering if anyone on another variant was having the issue so I knew whether to update my build =\

My question remains still but it seems no one is having the issue but him. He's only having this problem on CM10.1 (built with a 3.4 kernel) using KT747. I personally tried the same nightly build he did and a couple others and reproduced it once, but nothing after that. :confused:

I just told him to do a clean install of his rom and the kernel to see if it persisted
[Verizon Samsung Galaxy S III] PoLoMoTo:
Is KTweaker currently unstable? I'm on 4/10/13 linux 3.4 and can configure KTweaker fine once after force closing and clearing data but then if I close it then try to reopen it it fore closes on start and if set to apply 30 seconds after boot it kernel panics (I'm pretty sure thats what it is, freezes then reboots) when it actually tries to apply the settings.
[Verizon Samsung Galaxy S III] ktoonsez:
You probably have an old KTweaker in your system, start searching in /system/app and data/app folders.
[Verizon Samsung Galaxy S III] tihsllub:
Whoa I didn't realize their was a 4/10 release?
[Verizon Samsung Galaxy S III] tprophit:
Me neither. I have 04/07
[Verizon Samsung Galaxy S III] ktoonsez:
4/7 is latest but am brewing up a quick AOSP 3.4 release before I leave town :good:
[Verizon Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 4.11.2013

1. Optimizations for ROW scheduler

2. Optimizations for CFQ scheduler

3. Optimizations for DEADLINE scheduler

4. Some backgound scheduler optimizations and entropy stuff

5. Merge in codeaurora JB_2.5.04.02.02.40.236

6. Fix composition issues when framework rebooted in suspend

7. REVERT regulator fix up that was causing high power drain and instability

8. Merge in codeaurora JB_2.5.04.02.02.40.242

9. 100% synced with CM
[Verizon Samsung Galaxy S III] masri1987:
Boom shakalaka
[Verizon Samsung Galaxy S III] Stranger_84:
Sweeeet
[Verizon Samsung Galaxy S III] airmaxx23:
I can't get the download to start for some reason.
[Verizon Samsung Galaxy S III] mike216:
First time trying your kernel. Feels like butter. Not that cheap **** neither... Land O Lakes smooth

Edit. Smooth as **** and the colors are nice and cool. Makes whites actually white. Nice job
[Verizon Samsung Galaxy S III] duarian:
One thing I'm noticing on the ICS kernel is that when using any governor but on demand; CPU 1 does not go offline like it does using on demand. Tried various reboots but it always stays at your minimum. Anyone else experiencing this by chance?

Might just be an issue with my synergy nightly...
[Verizon Samsung Galaxy S III] masri1987:
i think my selection of lock frequencies in is what's causing the SOD's and random reboots. so far so good now running badass and SIO.
[Verizon Samsung Galaxy S III] ka1z0ku:
Set to max OC 2.1ghz and lulzactive governor, running CM10 official 9/1. getting a nice score but lower than ICS and I/O in particular seems to be cut in half compared to ICS ROMs. Is this a CM10 issue or a kernel issue? Thanks!

Sent from my CM10 SGSIII
[Verizon Samsung Galaxy S III] 1900mcm:
Encryption supported?

I was playing around and performed an encryption of data using the 8/31 (sammy) kernel on top of a stock deodexed. For whatever reason, the encryption failed (or failed during the startup/mounts)

I was left with a system which would boot up into an 'encryption process failed to complete screen', with a prompt to reboot.

So, I just wondered if the Kern has all of the 'required' stuff to mount an encrypted data partition?

(good backups... got everything back - i guess i'll have to try this again but either with a future kern and or a stock kernel)
[Verizon Samsung Galaxy S III] azbobs:
Curious how this is now running on synergy nightly r68

Just was thinking about loading this kernel

So your seeing running on the on demand

governor the CPU 1 is not going offline?
[Verizon Samsung Galaxy S III] faehsemc:
I'm at 96min 1024max smartassv2 with deadline UV -75 on everything and its running amazing on paranoid. Thank you for the kernel
[Verizon Samsung Galaxy S III] duarian:
No. For some reason I rebooted it smd it went offline as normal with any governor I tried.

I went back to on demand as it seems to give me the best battery life personally.

Currently at 96/1.24 and running smooth, cool and great battery life
[Verizon Samsung Galaxy S III] azbobs:
Good to hear

Thx good to hear this, been reading all the posts

trying to decide to switch from the kernel that

is with synergyROM from ziggy which has been

gr8.

Just seems my signal is somewhat weaker

since going from stock to custom. I have used

IMO's and was running 1512 - 124 at that time.

Liked the kernel, just my phone always seems

to run hotter than I Iiked. I went back to the one

that is with synergyROM nightlys, "ziggies"
[Verizon Samsung Galaxy S III] faehsemc:
As far as signal, the bars show weaker but when I look at dBm its still the same. Don't trust the bars. With data drops, the only time I get them is in a non 4g area. Aka my house, which seems to have a 5 mile 4g dead zone... wtf for, I dunno. But all I do is switch to CDMA auto prl and I have no drops in data. As far as AOSP goes, this is definitely the #1 Kernel.
[Verizon Samsung Galaxy S III] ktoonsez:
ktoonservative also supports hotplugging like ondemand. Ondemand is a great governor and is optimized for battery without giving up to much in performance.
[Verizon Samsung Galaxy S III] jgrimberg1979:
Can you look into why some of us are having major issues with lag and over heating with the last two asop kernels. I really wanna use this kernel again
[Verizon Samsung Galaxy S III] ktoonsez:
Has to be ROM. What ROM r u using? Have you uninstalled the KTweaker and then re-installed the kernel to get it back so you know you are starting with fresh data? Some have had issues with the data not getting updated for some reason when upgrading. I run my AOSP kernel along with tasks and I ROM (AOKP) day in and day out, runs better than any previous releases using my ktoonservative gov.
[Verizon Samsung Galaxy S III] jgrimberg1979:
I have done all of those and tried 3 or 4 different roms. I am pretty sure I have tried just about everything. I was also having a similar issue with the Sammy ics kernel. Very strange
[Verizon Samsung Galaxy S III] ktoonsez:
When u get the lag, have u checked the min/max setting for Mhz? Dont use the KTweaker, use Voltage Control just to see if somehow the max speed got stuck at something low (this was a symtpom of my first 2 KTweakers, just want to see if that is the issue).
[Verizon Samsung Galaxy S III] bgolden84:
Im not having any issues what so ever. As usual ktoonsez. Great work bro. Hope to see a task650 and ktoonsez aokp rom. For underwear sake of course.
[Verizon Samsung Galaxy S III] ktoonsez:
Never mind, lol
[Verizon Samsung Galaxy S III] jgrimberg1979:
Voltage control? Is that an app? Can I just un install ktweaker all together? I have checked and the min and max are what the should be..
[Verizon Samsung Galaxy S III] bgolden84:
you guys got some flak in the sprint forum for the und$%we@r comments . Thought it would give you a laugh. Thanks again bro

I used to have a sprint sgs3 and ran your guys rom. I would be willing to donate again for a vzw rom. Lol. I think you will remember me. I'm the one that "ported" your att rom and got in trouble w task. All good now though.
[Verizon Samsung Galaxy S III] ktoonsez:
Yes u can uninstall it. Voltage Control is an app in Playstore. The reason I said use that, is because of all the check and questions u have to answer when opening mine and wanted a 3rd party app to show u the actual min and max. I would bet that the max somehow got set to 384 or something so the phone is running at a really slow Mhz. So if you can leave KTweaker in there, install VC and try to get the lag situation going and then quickly check the min max using VC or Ill never be able to track it down.
[Verizon Samsung Galaxy S III] samg77:
Do you know if this kernel will work with JellyWiz (a port of the offical TouchWiz Jellybean, ported from Tmobile), and if so would it be the ICS/Touchwhiz or the JB/AOSP?
[Verizon Samsung Galaxy S III] Stranger_84:
This ****s better then government cheese ;) Lol ... Thanks for the update ktoonz!!!
[Verizon Samsung Galaxy S III] MorphiousGX:
Nice!!! I will be trying it right now on ChameleonOS. Thanks :)

I know you are going of town, do you have any updates for those who are using TW?
[Verizon Samsung Galaxy S III] keynith:
Wont download the whole file for some reason
[Verizon Samsung Galaxy S III] Hybridnoob:
The latest AOSP link ktoonsez posted worked fine for me...
[Verizon Samsung Galaxy S III] ktoonsez:
Nothing new for TJ right now.
[Verizon Samsung Galaxy S III] tprophit:
Thank you.

Do you still recommend your same recent settings for ktoonservative/row combo?
[Verizon Samsung Galaxy S III] masri1987:
Wtf is chameleon os? AOSP?
[Verizon Samsung Galaxy S III] mademan420:
http://www.chameleonos.org/

Yep!
[Verizon Samsung Galaxy S III] what be up:
Looks interesting, gunna try it out
[Verizon Samsung Galaxy S III] midnight assassin:
So the newest tw kernel is the 04/04 test, right?
[Verizon Samsung Galaxy S III] keynith:
After a reboot, it downloaded nicely :)
[Verizon Samsung Galaxy S III] failsaf3:
Strange issue

So I have a strange issue. I'm currently running CarbonROM 1.5 (3/2 release) along with KT747 3.0 kernel (4/4 release). I'm currently running:

- pegasusq gov (and previously ran ktoonsez gov)

- zen gov (and row at some points)

- undervolted 25-50mv at various steps.

- 189-1512MHz

Everything runs smoothly with an occasional reboot every 2-3 days.

I figured I would move to a newer release of CarbonROM but I'm having all kinds of graphics issues- tearing, icons/dividers disappearing, graphics stretching etc. Normally I would associate this with being undervolted too low. However this is with the stock voltage table. I've even tried raising the voltages in steps of 25 and 50mv above stock. Slightly better but still issues.

This happens with Carbon 1.6 with KT747 3.4 (4/11), Carbon 4/8 nightly with KT747 3.4 (4/11) and also with Carbon 1.6.1 and KT 3.0 (4/4).

Restored back to Carbon 1.5 with KT747 3.0 (4/4) release and everything is fine.

Anyone have any similar issues or any ideas? Do newer releases of Carbon and KT just not want to play nice on my phone? :confused:
[Verizon Samsung Galaxy S III] Casper34:
Page wont load using dolphin. :confused:

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] mw86:
Worked on Chrome. Looks okay has a very them able framework. I'll stick to Task AOKP but the page should be fine on Chrome.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Will the 4/11 aosp kernel fix the crazy graphical errors some of us were getting?
[Verizon Samsung Galaxy S III] jamesino:
I'm running Carbon 4/8 and, just now, KT747 4/11, for the past 1.5 days, I ran KT4/7. I havent had any problems in terms of freezing/SODs with either combo.

The only glitch I can think of is I get those occassional flickering horizontal grey bars on my screen. This is brightness and app dependent.

But nothing like you have described.

I'm on interactive/row.
[Verizon Samsung Galaxy S III] failsaf3:
Thanks for the response. In my limited time running Carbon 1.6+ with KT kernels I didn't have any freezes or SOD. Just massive graphical glitches. I did turn of the "CRT off" animation but no help.

Carbon 1.5 (and earlier) + KT kernel combo, I never had any issues so I'm at a loss as to why the odd behavior all of a sudden.
[Verizon Samsung Galaxy S III] ktoonsez:
It should, thats why I made the release so you guys would be caught up.
[Verizon Samsung Galaxy S III] Neverendingxsin:
You're the best :) Testing it now

Edit: Still getting major graphical glitches. Strange lines in the camera and PIE gets so bad that it just freezes.
[Verizon Samsung Galaxy S III] masri1987:
Any specific ktoonservative settings ktoonz?
[Verizon Samsung Galaxy S III] savagebunny:
Well here are results for anyone wondering about this Kernel...

http://xdaforums.com/showpost.php?p=40198449&postcount=1926

@masri1987 check out this thread. It's the discussions of different setups for the phones. Some like ktoon gov and some like peg, or asswax. Just gotta try it out.

http://xdaforums.com/showthread.php?t=2144004
[Verizon Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 4/11/2013

1. Upgraded to newest Linaro compiler

2. Fixed multiplier problems in some of the schedulers

3. Updates to KTweaker for some error handling

4. Scheduler/Entropy optimizations

ENJOY!!!!!!!! :good:
[Verizon Samsung Galaxy S III] mike216:
Holy **** this thing is sick on the new liquid release
[Verizon Samsung Galaxy S III] tprophit:
Is ktoonservative governor hot plugging, or do we need to enable hot plugging for ktoonservstive?

Thank you.
[Verizon Samsung Galaxy S III] ktoonsez:
By default it hotplugs unless you disable it in the governor adjustments screen.
[Verizon Samsung Galaxy S III] tprophit:
So that would be done by changing 0 to 1?

Not that I'm going to, but if that's the case then my next question is, I don't use Bluetooth, is there any benefits to disabling BT hotplugging?
[Verizon Samsung Galaxy S III] ktoonsez:
A 1 disables hotplugging and keeps both CPU cores online. No need to mess with BT one unless you have issues with BT music play back. Turning that to a 1 disables hotplugging when paired to a BT device.
[Verizon Samsung Galaxy S III] savagebunny:
Damn, I don't have enough time to test kernels with all these releases :eek: Thanks ktoon
[Verizon Samsung Galaxy S III] tprophit:
Thanks, just learned something new. I appreciate your work, and willingness to help. It's gonna be a little while, but I will ship a nice donation to you when I can.

Thanks again.
[Verizon Samsung Galaxy S III] savagebunny:
@ktoonez. Enjoy it man. Buy yourself some alcohol for the weekend. That's how much it costs me to fill my motorcycle tank ;)

603772084S282282T
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks man, very cool :D :highfive: :good:
[Verizon Samsung Galaxy S III] Stranger_84:
Donation sent great work thank you 1CG863748E3178232
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks buddy :good: :highfive:
[Verizon Samsung Galaxy S III] NITRO_2:
I'm about to make the switch to liquid 2.2 from beans rom. Mind telling me which ktoon kernel I download? The Linux one? Sorry for asking
[Verizon Samsung Galaxy S III] Stranger_84:
His latest aosp 3.4 release!!!
[Verizon Samsung Galaxy S III] savagebunny:
Depends if the rom is based off 3.4. See Carbon 1.6.1 is based off 3.0... Luckily I found out before I flashed over 3.4
[Verizon Samsung Galaxy S III] Stranger_84:
Liquid 2.2 is 3.4 based use ktoonz latest release
[Verizon Samsung Galaxy S III] mike216:
Glad to see someone had already helped you with this question but never be sorry for asking. Don't let the few thread nazi's out there make you feel like you can't ask for help
[Verizon Samsung Galaxy S III] thornev:
To the Man ! 6S059083F05137824
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks man, awesome! :highfive: :good:
[Verizon Samsung Galaxy S III] PoLoMoTo:
There was one in /system/app I deleted then reflashed and now I can enable oc, lock frequencies and move one slider but if I try anything else it freezes and reboots :/ Maybe I'll try 4/11
[Verizon Samsung Galaxy S III] HeinousJ:
Is there a difference between the two files?

1. KT747-AOSP-JB-MR1-3.4-VZW-04-11-13

2. KT747-Kernal-AOSP-JB-MR1-VZW-04-11-2013

File #2 does not boot for me. It does not even get to the boot animation. I am running the latest AOKP with the latest cwm touch.
[Verizon Samsung Galaxy S III] juancaperez2000:
File 2 is for roms running kernel 3.0 and file 1 is for roms running kernel 3.4 so latest AOKP is running 3.4 u need flash file 1
[Verizon Samsung Galaxy S III] HeinousJ:
Thank you for the clarification. I knew that it would be something simple. That is what I get for arbitrarily flashing what ever KT drops without looking first. :p
[Verizon Samsung Galaxy S III] pettigrew95:
I read the description about lulzactive and it doesn't say anything about that governor keeping the cpu at max frequency when the screen is on. I noticed when my screen is on if I'm looking in SetCPU the frequency is stuck at 1512 mhz even if I'm not touching anything. Any input is appreciated, thanks guys!
[Verizon Samsung Galaxy S III] mike216:
It looks like a bombarded amount of appreciative good people donated and I wanted to be one of them. Have a couple drinks on me. Thanks champ. Day two is awesome with this kernel. Good battery and amazing speed. Love faux sound mod!
[Verizon Samsung Galaxy S III] MorphiousGX:
While testing

Installed 4/11 Kernel v3.4 AOSP. I noticed this SmartassH3 governor. I wanted to test it out.

Here is what I noticed so far:

It has same settings as Asswax

ISSUES

The governor seems to remains at max frequency level instead of throttling down

The governor caused KTweaker to hang when:

Trying to modify values. I would have to force kill

Trying to load saved settings if it is already selected as a governor. I would have to force kill

app tries for fix mismatched settings after a reboot

Other than that (so far) the kernel seems to be very smooth and very efficient. I like it :good:
[Verizon Samsung Galaxy S III] keynith:
Installed the 4-11 from clean install, hours later screen flashed a few times which prompted me to do a battery pull, due to the phone not responding to power key, home key, etc.

Upon booting, the phone would go black after the samsung logo. Rebooted to recovery, tried wiping cache(s) with no boot. Even reinstalled the kernal, with no avail. Haha i didn't wanna wipe everything so i tried restoring my last backup, identical build numbers and all, and it still wouldn't boot. I ended up having to wipe everything and restart from scratch so it would finally boot.

Idk what happened, but i did everything the same when i installed the 4-11 kernal again and no problems so far. Weird bug.
[Verizon Samsung Galaxy S III] mike216:
What rom?
[Verizon Samsung Galaxy S III] masri1987:
Anyone using any governors that are not ktoonservative and pegasus?
[Verizon Samsung Galaxy S III] jamesino:
I'm using interactive.
[Verizon Samsung Galaxy S III] masri1987:
I'm curious about the new governors like dancedance and smartassh3
[Verizon Samsung Galaxy S III] PoLoMoTo:
Mind me asking what version Chameleon you're using? 4/12 wont boot past the S3 screen...
[Verizon Samsung Galaxy S III] keynith:
Carbon nightly. I know those can be sketchy, but it only started the screen flash and random rebooting after 4-11 3.4 kernel was installed
[Verizon Samsung Galaxy S III] mike216:
Chances are if no one besides you are reporting this it's far more then likely the nightly? Is hard to say for sure but I would bet that something is buggy
[Verizon Samsung Galaxy S III] jamesino:
Running the 4/11 KT747 with 4/8 Carbon nightly.

I'm happy to report that the 4/11 KT747 is the first v3.4 kernel that I have used that matches the speed of the fastest v3.0 kernels in terms of smoothness and absence of lag.

I'm extremely OCD about scrolling and animation smoothness.
[Verizon Samsung Galaxy S III] tprophit:
Much of the battery life discussions center around screen on time. What about call time? For example, I'm at 47%, total of 7:19 phone on, 6:47 on battery (on charger for 32 minutes) with 1:37 in talk time, 1:32 screen on. Koontservative/row, UV -50, uc to 189, and ktoonz settings. Does this seem like decent battery life for the usage?

Thank you.
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks man. Very cool:)