yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Wait for todays nightly or wait a sec, I'll give you a link to the 19. build for jfltexx

Edit: check your pm

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Vladivid:
Try this - https://mega.co.nz/#!dVMVURxA!X8fDHEziyB7_be7wyY-2myWgCAoR6RGm_8S20cLTCm8
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Any feedback on the GPU boost for ktoonservativeq??????
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
i will try it.. where is the option? i can found it :good:

Sorry ktoonsez, have you read here? http://xdaforums.com/showpost.php?p=48662907&postcount=6829

please can you try to fix it?

thanks
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Its in Governor adjustments (set to 450 by default). No I cant fix the ROM/app.
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Founded, i appyed it, for now seem :good: i continue to test it..

ok, thanks, i hope will fix soon...
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Great!! Thanks! Which settings do you use/prefer?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Im using my OC setting of 504.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
So in Extras max gpu = 504

And in ktoonservativeq gpu boost 504 too?

But gpu always went from the idle 320 to the max gpu value when we did something...? So why the touch boost?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Yes settings are what I have.

Mine always stayed at 128 and went to 320 when touching.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Really?? Mine is always on 320 when idle... Always been... Why is that?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Cus your phone sucks :D. Lol, I dont know why urs doesnt act like mine. I use ondemand GPU gov.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Never goes below 320. Never.. Ondemand gov on gpu too.. That sucks....

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
i wronged sorry
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
[MENTION=4325945]ktoonsez[/MENTION]

The whole thing isn't working as it should ;)

If I set max gpu at 600 and touchboost gpu to 504 it goes straight to 600...

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
+1

here the same, dont go down of 320
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Read the change log, I told you to set the touch boost to your max if you are using your max. There are NO steps in between 320 and your max, so it goes from 320 to the max, thats it, no in between steps.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Ok thanks. But still no clue why 320 is the lowest on mine. Latest cm11.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] czar22:
no Slow Motion Record - on Stock Camera

why ?

4.2.2 kernel TW
[Galaxy S 4 i9505 Original Android Development] topiratiko:
Hey guys...runnin 12/12 update...anyone notice slightly degraded performance and battery? On i337

Samsung Galaxy SIV

Graviton 1.7 Rom

Ktoonsez 12/12 Kernel
[Galaxy S 4 i9505 Original Android Development] MrJiM:
[MENTION=4325945]ktoonsez[/MENTION]

Could you share your backup file with your settings? Thanks :)

Edit: Btw.. You are om CM rom right?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Here you go, be sure to remove the ".txt" part:

View attachment Settings.txt
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Great, thanks :)

i will try it :)

But how i can download it? i cant

if click it open a web page
[Galaxy S 4 i9505 Original Android Development] bignick8t3:
Right click and select "save link as" :)
[Galaxy S 4 i9505 Original Android Development] MrJiM:
Gonna try it after I fix my phone says "out of storage" when there are loads of storage left problem. Maybe caused by newest modem. Reverted back to MKF and hoping for the best. :D

Edit: Damn it! Broke at 90% download on spotify... :(
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
You can also download "Ktoonsified" from my thread if it helps. Those are his settings.
[Galaxy S 4 i9505 Original Android Development] yod123:
Looks like wi-fi is broken for mine. Just can't turn it on... XXUEMK9 tw rom with 12/12 kt kernel. Any ideas? Looks like need flash another modem...
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Updated Post #3 Settings

My settings

General Screen

governor = ktoonservativeq

scheduler = bfq

Min Mhz = 189

Max Mhz = 1998

Voltage Screen

UV'd 50mv across the board for CPU and 75 for GPU (use menu button for hidden menu option to globally subtract)

Extras Screen

Screen OFF Profile Mhz = 486

Disable Screen Off Mhz Call = Enabled

Screen OFF Profile Sched = noop

GPU Max Mhz = 504

Screen OFF GPU Max Mhz = 200

GPU governor = simple

Internal Read Ahead = 2048

External Read Ahead = 2048

General -> Governor Adjustments Screen

sync_extra_cores=1

touch_boost_cpu = 1242

touch_boost_cpu_all_cores=1

up_threshold = 80

sampling_rate = 40000

sampling_rate_screen_off = 90000

disable_hotplugging_chrg = 1

touch_boost_gpu = 504

ALL THE REST ARE STOCK
[Galaxy S 4 i9505 Original Android Development] skeamznz:
Great thank you will try the boost later. How do you find battery life with the GPU over clocked and with screen off GPU on?
[Galaxy S 4 i9505 Original Android Development] Dijkstra88:
New Linux 3.4.75 is out :D

Send from my GT-I9505 with Tapatalk 4 Pro
[Galaxy S 4 i9505 Original Android Development] schnip:
Linux 3.12 is out dude...

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Still get 3 days on a single charge :D :good: :p
[Galaxy S 4 i9505 Original Android Development] csec:
Hey Ktoonsez, you don't use your phone much, do you?!

Maybe post one of your cycles here would shed some light on these strange numbers!?
[Galaxy S 4 i9505 Original Android Development] nplnpl:
Problem

the Kernel ktoonsez for 4.3 touchwiz 12.12.2013 have a bug .... screen luminosity ( -5 +5 ) not work ... fix problem :)
[Galaxy S 4 i9505 Original Android Development] Dijkstra88:
Dude, that kernel doesn't work with our device.
[Galaxy S 4 i9505 Original Android Development] Tylog:
19/12 Kernel works very nice KT , good Battery, good job :)
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
+1 :laugh::victory:
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
OP Updated

Change Log 12.21.2013

1. SUPER CRAZY WACK FUNKY SPEED EDITION!!!!!!!!!!!

2. cpufreq: Some general re-write to make freq changes smoother and more efficient

3. acpuclock-8960ab; Update from ML4

4. subsystem: Add extra checks to make sure subsys_domain and iommu_domain are NOT NULL

5. msm: msm_bus: More checks to insure pdata and bus driver vars are not in error and NO NULL

6. grp3d_low_vectors: Bump MBPS to 1700 for low vectors for better low speeds

7. gfx3d_fs_data: Change reset_rate 27000000 from 1800000. Remove 1800000 from clk_tbl_gfx3d. Increase log length for msm_rpm

8. dcvs: Set msm_dcvs_enabled = 0 when msm_dcvs_scm_init() fails adn be sure to return early when msm_dcvs_enabled == 0

9. perf_event_msm_krait_l2 sync with ML4

10. scm: Rewrite scm_call funcs and ML4 merges

11. Linux 3.4.75

From previous OTA's

1. ONLY USE THIS WITH CM 11 BUILT ON 12.18 OR NEWER!!!!!!!

2. Prox sensor

3. Fix for Battery issues on builds 12.18 and newer

4. ktoonservativeq: Added "touch_boost_gpu" option. Be sure if you are using the max GPU frequency that if you adjust the max, also adjust the "touch_boost_gpu" option.

5. ONLY USE THIS WITH CM 11 BUILT ON 12.18 OR NEWER!!!!!!!

6. Fix battery update for the 2nd day in a row!!!!!!!!!!!!!!!!!!!!!!!!!!

7. ONLY USE THIS WITH CM 11 BUILT ON 12.16 OR NEWER!!!!!!!

8. Upgrade camera to ML4 source from Samsung

9. Sync GPU/Display drivers from ML4

10. cpufreq: interactive: Allow 1 ms error in above_hispeed_delay

11. cpufreq: interactive: Reset floor_validate_time if busy at max for 100ms

12. cpufreq: interactive: Add a sampling_down_factor for max frequencies

13. Many msm: msm_fb updates

14. Many msm: msm_mdp updates

15. Many msm: msm_vidc updates

16. Updated healthd binary for charging routines for CM 11

17. ENJOY!!!!!!!!!!!!!!!!!!
[Galaxy S 4 i9505 Original Android Development] phil.o:
Will there also be a 4.3 jizzer kernel with gpu touch boost?! :D

°°° tapatalked °°°
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Havent had a chance to see if the jizzer can handle it yet.
[Galaxy S 4 i9505 Original Android Development] Tylog:
Hehe , point 1 it's nice:p

Thanks again for the next update, love it :)

Tapatalk SlimKat 4.4.2
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
I liked it too. :good: :D :highfive: :cool:
[Galaxy S 4 i9505 Original Android Development] rlorange:
0.1 is not enough! He he
[Galaxy S 4 i9505 Original Android Development] csorrentini:
What could possibly be causing my screen to just stay black after the initial Samsung load screen after flashing the TW 4.2.2 Ktoonsez? I am currently using WICKED V8 4.2.2 and I followed the directions (clear cache, dalvik) but same thing each time. I am using Philz recovery so I can't do the fix permissions there, could that be the cause?
[Galaxy S 4 i9505 Original Android Development] Moz007:
21.12 is f*cking smooth !!! This is your gift for christmas ! :D
[Galaxy S 4 i9505 Original Android Development] Formhault:
I thought making phone calls via headset without taking the phone out of the pocket doesn't count! :cyclops:

---------- Post added at 12:18 PM ---------- Previous post was at 12:15 PM ----------

Advertising done right lol :silly:
[Galaxy S 4 i9505 Original Android Development] rlorange:
KT latest version is killer... Just noticed that the GPU is more sensitive to under volting now for me. Instead of jar freezing I get graphical glitches but a working phone until I raise the voltage for the highest step.

---------- Post added at 12:25 AM ---------- Previous post was at 12:10 AM ----------

Actually I can't go beyond 545 anymore where as until this version I could do 627 indefinitely... So I think something needs fixing
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
I forgot a part of the change log. Part of my touch_boost code has a patch for voltage, in previous versions, in certain situations, it would either use the 320 step or the hardcoded max voltage.
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
I use screen about 2.5 to 3 hours in that 3 days. Of course it does vary since I have been home, using it alot more, but when I am traveling Im always right around that 3 hour mark and getting almost 3 days. One great thing with my settings is the sleep drainage. Last night I went to bed early at 9:30 and had 91%, then woke up 11.5 hours later and I am sitting at 87%. 4% drain for 11 hours is just amazing these days with all the added features/services of ROMs today.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Hmmmm OK but there still seems something off maybe try this:

Main GPU: 545 v 875,975,1100

Stable with 450 touch boost.

Main GPU: 600 v 875,975,1100

unstable with 450 touch boost.

So it seems like the main max GPU is using the 320 step voltage as well as the TB setting? Or is it the case that the touch boost at 450 is getting 975 instead of 1100 somehow?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Im stable all the way up to 627. The proper voltage selection is being made for sure!!!!!!!!! :good: Also, you should have read the change log and see that you need to MATCH your max boost to your max GPU freq, dont know if that will make a difference for you.

EDIT:

Also my top GPU voltage is at 1150.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Ah OK missed that detail... Indeed if I match them it's back to normal but I had to switch governors first, change my global max then switch gov again and incrementally repeat step by step to 627. Because a jump from 450 to 627 either way was too big a miss match since the GPU choice for ktservative is still active when you switch back to using.

Perhaps the GPU boost could automatically match and link to the global setting first when you set ktservative?

---------- Post added at 06:24 AM ---------- Previous post was at 06:17 AM ----------

Aha! So I found the solution. You must lower GPU boost to 320 BEFORE changing global GPU max. Then change the boost value to match. Choosing 320 will use 320 step voltages but 450 uses max step voltages so you can't increase the global max while currently using a boost higher than 320 without issues
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Cooooooool. I dont want to automatically do that due to n00bs out there. :good:
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
OP Updated

Change Log 12.22.2013

1. TW and TWGE: ktoonservativeq: Added "touch_boost_gpu" option. Be sure if you are using the max GPU frequency that if you adjust the max, also adjust the "touch_boost_gpu" option.

2. TW and TWGE: Linux 3.4.73

3. TW and TWGE: Linux 3.4.74

4. TW and TWGE: Linux 3.4.75
[Galaxy S 4 i9505 Original Android Development] rlorange:
Actually that didn't work either mate but wiping kt app data and then choosing kt governor> global GPU 627 > touch GPU 627 works. Any other way seems to mismatch and fail so there is a big noob trap here... Perhaps the voltage settings aren't changing with the step choice?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
They are 100% changing, I verified it, not sure why you are having so much troubles. And yes you absolutely have to wipe app data when I add options to KTweaker if you have troubles. That has always been the rule :p :cyclops:
[Galaxy S 4 i9505 Original Android Development] rlorange:
Yeah I wiped it before after failed settings many times... But did restore app settings backup do there was my problem?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
If you wiped app data then restored your settings you basically did nothing, restoring will just bring back all the old data. So yes that could have been your issue.
[Galaxy S 4 i9505 Original Android Development] Formhault:
So... If max GPU is 504 MHz, touch boost must also be set at 504 MHz?

Sent from hyperspace
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Only if you want the max as your boost also.
[Galaxy S 4 i9505 Original Android Development] Formhault:
I'm having a really hard time here... I did read, thoroughly even, but I feel retarded :(

1) Touch boost = frequency the GPU is scaled at when you touch the screen?!

2) Why would you need that? GPU is not needed to operate at high frequencies when you only touch the screen... But in intensive graphical games! :/

I didn't get it at all, right? :angel:

Sent from hyperspace
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
#1 is right. In my limited game experience, I touch the screen when I want things to happen in the game when no motion is going on which would cause the GPU to drop, therefor this helps alot and just makes UI more responsive when touching it. If your game is written properly then your GPU will already be maxed when alot is going on but still could drop at certain points when the screen is not in motion.

Also you can control how long it stays boosted with:

boost_hold_cycles (22 = 1 second)
[Galaxy S 4 i9505 Original Android Development] Formhault:
So... When GPU maximum frequency is set at 504 MHz and touch boost is at 504 MHz as well... If a badly coded game does not ramp up the GPU, touch boost will for sure (but only when you touch it)?

But I think most good games are optimised for this already. Badly written games like Candy Crush and Minion Rush may benefit from this greatly, I suppose...

I thought touch boost would temporarily increase the GPU frequency *above* the maximum frequency, like Intel Turbo Boost, you know. But I should have realised that this was not the case since... "touch" in the "touch boost" naming scheme... If I were to understand how this works in the first place! :silly:

Sent from hyperspace

---------- Post added at 12:33 AM ---------- Previous post was at 12:27 AM ----------

Hey ktoon... Why do you use BFQ sched? I thought FIOPS is better? Or SIO (which does not seem to be included). What about them? Or ROW?

I've heard / known about them since the Note / Note 2, that's why I am bringing it up.

Sent from hyperspace
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
BFQ is the best scheduler I have used, really makes a difference in UI for sure. ROW is very slow to me.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Restoring data in-app on some apps is not exactly equivalent to doing via TB or equivalent so cheers for clarifying that
[Galaxy S 4 i9505 Original Android Development] rlorange:
I'm still getting inconsistencies Kt. For example set global GPU to 600 followed by boost to 600 glitches. Then if I lower global to 504 followed by boost to 504 then put global back up to 600 fine. In all end results both show boost at the global of 600 even though one glitches

---------- Post added at 01:33 PM ---------- Previous post was at 01:22 PM ----------

Just reloaded defaults from app and rebooted and it's defaulted to 450 touch boost however I noticed the extras global setting is still at 600!!!

I'm dual booting so could be the culprit?
[Galaxy S 4 i9505 Original Android Development] Formhault:
Is the performance/battery drain ratio good, too? I switched to BFQ from FIOPS yesterday and did not notice anything out of this world. I am just being nitpicky right now... :silly:

Why NOOP as the screen-off scheduler? I assume it implies less speedy I/O, hence better battery life (which is what you need when you don't really look at the phone)?

What about SIO? Back in the Note 1 days, I remember SIO was the sh*t, with ROW picking up speed fast. Of course, things have probably changed a lot since then, especially with the newer Androids and such. Plus, back then, the kernel was NOT 3.4.xx... right... that's probably something, too.

Again, I'm just being overly nitpicky, lol.

---------- Post added at 09:28 AM ---------- Previous post was at 09:24 AM ----------

Does such a high GPU frequency even make sense? I remember back when I first got the S4 and found out abot KT, I tried many things and they did not seem to stick at all.

For example : ramping the GPU speed up to 627 MHz did not result in smoother experience in some games. 450 / 627 MHz... same thing.

Right now, I am sticking with 504 MHz, regardless of wether it is in effect or not (I just think it's faster so even if it isn't faster, at least it's placebo so I feel good, LOL).

Same goes for voltages. I could UV so much it would go negative 50 milivolts. That means the voltages were not sticking back then...

Right now, I am sticking with -75/-75 UV on both CPU and GPU. Just in case it PROBABLY works. Even if it doesn't, at least it's placebo so I think I feel the phone a bit less warm.

:silly: :silly: :silly:
[Galaxy S 4 i9505 Original Android Development] csec:
GPU frequency and Voltage is really working the way it should... NOT.

Old times with Tegra 3, strange things happened, but this Adreno is surely a Wonderland.

But tbh, before I flashed Ktoonsez kernel, I was regretting the upgrade to S4. I like how cool the phone is with this kernel. CPU UV works as it should here, and I am satisfied with it.

Now with CM and latest Ktoonsez kernel I understand why here awesome is a rule. :good:
[Galaxy S 4 i9505 Original Android Development] harise100:
I need to raise the minimum CPU frequency to 486 to get my phone smooth.

All lower frequencies result in micro stuttering.

Everything else is working great. :)
[Galaxy S 4 i9505 Original Android Development] djsolidsnake86:
what is latest for miuiv5?
[Galaxy S 4 i9505 Original Android Development] Formhault:
So... Do they work the way they should or not? :laugh:

Sent from hyperspace
[Galaxy S 4 i9505 Original Android Development] radiobicho:
Hi all. Whats the best Ktweaker configuration to have Overclock performance with NO LAG? Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] Misk77:
Take a look in Ktweak shop by luigubull23 forum
[Galaxy S 4 i9505 Original Android Development] csec:
I was just trying to talk like Ktoonsez. ;)

Totally not working the way that makes sense.
[Galaxy S 4 i9505 Original Android Development] Formhault:
Makes no sense... lol.

I was able to undervolt as much as -100 mV on both CPU and GPU. The phone froze two times throughout ~14 hours. -75 mV (on both) works fine, though.

If I UV for like -500 mV, will it work? :silly: Or it will crash (LIKE IT IS SUPPOSED TO LOL)
[Galaxy S 4 i9505 Original Android Development] boulder96:
I find that undervolting the CPU by 75mV makes the phone less responsive and more laggy as just opposed to undervolting 50mV. Do you experience this too?
[Galaxy S 4 i9505 Original Android Development] Formhault:
I don't think so. This has never been the case, in all Android phones I owned & undervolted. UV would either yield the same (noticeable by human eye, not 4x rant) performance, either make the phone crash 10 stories. :silly:

Oh, except for the Note 2. Too much undervolting (if -50 mV is too much for you...) would make one specific game glitch ALL OVER. Yes, Minion Rush, I'm looking at you. It was probably badly coded or... oh well, it still is badly coded anyway :)
[Galaxy S 4 i9505 Original Android Development] eden66:
Waiting for AOSP 4.4.2 kernel :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] boulder96:
Huh? AOSP 4.4.2 kernel has been out long ago... Latest one was 12.21.2013

In the OP even though it says 4.4 it's for 4.4.2
[Galaxy S 4 i9505 Original Android Development] csec:
-50mv for CPU is my limit, - 75 causes random reboots.

For GPU I don't really know. But I put it on -100 in the early days that kt added GPU UV, but the phone became laggy after some hours of using it. So now I don't use it much, sometimes -50 when using kt settings.
[Galaxy S 4 i9505 Original Android Development] Formhault:
I think / hope / hope / hope / hope you mean AOSP 4.3 kernel :D :fingers-crossed:

---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------

Attempting to record a video with the camera results in freeze followed by reboot (just after the screen goes wacko for half a second). Happens randomly, 1 out of 5, 10, 15, I don't know...

Happens with -100mV, -75mV, no UV... I think it's ROM/kernel related.

-----

Well... undervolt does make my phone run A BIT colder (like 1 Celsius degree I think, haha), so... :D
[Galaxy S 4 i9505 Original Android Development] jgchaval:
I did some search before posting this, but nothing useful came back, so I ask again to see if this is happening to more people, or if there's a fix. Maybe [MENTION=4325945]ktoonsez[/MENTION] can shed some light :)

Every time I open KTweaker, I get similar messages like this: "Your saved Scheduler for Screen OFF does not match current, Apply Scheduler?", same goes for CPU Governor, I/O Scheduler and many others...

I'm using Omega ROM v18 with latest KT Kernel for 4.3 (date 12.22.2013). Do I need to set options on boot in order to get settings applied everytime? Even after using the phone for some time, I get the same message when I open KTweaker, so why aren't those settings sticking?
[Galaxy S 4 i9505 Original Android Development] boulder96:
Maybe you can try backing up your settings, then clear data of KTweaker, then restore and see if the settings stick?
[Galaxy S 4 i9505 Original Android Development] reckoner_85:
Why are screen mode settings messed up after installing this kernel? Dynamic mode doesn't activate and Standard appears to be dynamic? any one noticed this?