yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Here is my testing btw:

GE with your kernel : reicast smooth and fast

Cm11 with stock kernel or faux kernel : reicast smooth and fast

Cm11 with your kernel : reicast not so smooth, laggy, slow game loading

Same settings, all on ART, same apps. Freshly installed system. What could it be?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Ninolina:
Thank you very much for your replay. I do follow this tread daily and I did see that proxy sensor value make issues but even if I set it to 255 which is highest value it still doesn't work. :(
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
I dont know what you could be doing then. What is your sensor reading in "Tools" when completely clear? Does the value even do anything when you move your hand up and down from the sensor.
[Galaxy S 4 i9505 Original Android Development] Ninolina:
In Tools it says value 23 and the number is changing if I move my hand over proximity sensor. Also if I flash kernel version from 10th March Swipe2wake and DoubleTap2wake works.
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Do this:

1. Open up "/sys/devices/i2c-3/3-0020/input/input3/screen_wake_options_debug" and set it to a 1.

2. Try the double tap and sweep 2 wake with the screen off.

3. Turn screen on as quick as u can and "Generate a dmesg" from "Tools" in ktweaker and I will be able to tell what is going on.

4. Post a link to the file.
[Galaxy S 4 i9505 Original Android Development] Ninolina:
Ok, here is the link - https://app.box.com/s/j42f0rljvsv8uytde6qy

I hope I did it right. :)
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
What wake function do you think you have enabled? The log tells me you have no options set. Go into ktweaker and set them up again, even if you are clicking on the same options. Then see if it works, if it doesnt do the same logging procedure again.
[Galaxy S 4 i9505 Original Android Development] Ninolina:
Ok, here is new file - https://app.box.com/s/qsu3uzi0n67ardeirzce

I set option for both - Swipe2wake and DoubleTap2wake and to be on Always when screen Off

For previous file it was set to be DoubleTap2wake and to be on Always when screen Off

Thank you for your effort. :)
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Ok so here is problem, for what ever reason, your ROM or some add on is activating the prox sensor that is fooling my code to make it look like you are in a phone call. If you can find what is turning your proximity sensor on then they will start working. I block out all those functions when I detect that the phone is on a phone call so you dont press things while screen is off during a call.
[Galaxy S 4 i9505 Original Android Development] Ninolina:
Ok, then I know what's wrong. I have an app called ProximityScreen Off which makes possible to turn off the screen when you cover proximity sensor. I now unable it and awake works. It wasn't in a conflict in previous version? This option to turn screen off is very important to me. Any chance to make it not to conflict? Or maybe add some feature in Kernel for turn off screen without using physical buttons?

Thank you for everything!!:)
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
All the fixes yesterday were prox related so that was what happened to u. I can not make it to not conflict, that is my only trigger to know when the phone is on a call. The new version I am working on has a "double tap to sleep" option that lets you double tap the top status bar area to make screen go to sleep.
[Galaxy S 4 i9505 Original Android Development] Ninolina:
Great! :) That's sounds good! :) Thank you for your time and all! :)
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
I dont know whats going on with your phone on CM :(
[Galaxy S 4 i9505 Original Android Development] layond:
Hello, better knock on

Enviado desde mi GT-I9505 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] leoniedelt:
Just to say to KT that the Echoe V17 + 10 March kernel + Dead By April 2.2 = the best battery life I've had since 4.2.2.

Thank you KT.
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Thanks man, really appreciate it :D :good: :highfive:
[Galaxy S 4 i9505 Original Android Development] leoniedelt:
No no, thank YOU. :victory:
[Galaxy S 4 i9505 Original Android Development] Misk77:
Kt gaming profile 1 cycle

2 email, Facebook 1h intervall.

Sync gps location on

Skickat från min GT-I9505G via Tapatalk
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Strange thing it's only on cm and only with your kernel :(. Guess I'll stay on GE with your kernel..

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] PiggySmalls:
[MENTION=4830253]Danvdh[/MENTION]'s GPE ROM is so much better than CM anyway, I only wish I had tried it earlier.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Why is it better? Cm is smoother, more options and themes are great.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
Regarding ktoonsez kernel, have you tries different GPU settings, like setting the lowest frequency to higher value (on other kernels 320 MHz is default idle value, but when under load GPU uses lower frequencies too.)? Also IO schedulers can matter a lot, have you tried different ones to see which is the best for you? If you think you could have problems with OC then don't use highest values, but tune other values for better responsivenes. Have you tried playing that game you mentioned on ktoonsez with performance governors (CPU and maybe GPU too,but not with highest frequencies.)? There is even performance profile switching on CM which could make the switch before game easier.

Edit

Sometimes, depending on the issue, one could try going in another direction, and instead of lowering timer rates (better for responsiveness.) increase them, which can increase the throughput, but one has to use other ways to make sure frequency scales fast enough (maybe again by lowering the thresholds...).
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Already tried all that stuff. Doesn't help. Guess I have to get used to it. Or wait for Android 4.5 or 5.0

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
There are almost always different combinations one could try ☺. So if you have time and will, just don't give up. I have no idea if KTweaker app has some kind of service running, to monitor things or whatever. For the case it has, maybe try freezing the app and see it that maybe helps? Also this s2w stuff can make different kind of problems, so make sure to try disabling that too.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Funny thing is I already froze the kmonitor app ;). I tried GE with ktoonsez kernel and on cm11. Both with the SAME settings. So it must be some code that's bad.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
Which ROM are you on? CM already has that feature.
[Galaxy S 4 i9505 Original Android Development] Ninolina:
I am on Omega Rom. I also use Xposed and GravityBox also have that feature but I would loved it more if it will be implemented into a Kernel. I liked even more to use proximity sensor for turning screen off but it seems that I will have to change my old habits. :(
[Galaxy S 4 i9505 Original Android Development] !crazy:
Since you said reicast works with stock CM, and faux, you could check which toolchain, and compiler options are used for these kernels, and ktoonsez.

Regarding benchmarking tests, are here also some significant differences between the kernels?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
How does that work anyway with the prox sensor? Seems like the screen would constantly be turning off if you blocked the prox. Is there a 5 second dealy to decide to turn screen off or something like that?
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
GE with ktoonsez kernel: Reicast great

CM with stock kernel, faux kernel: Reicast great

CM with ktoonsez kernel: Reicast bad.

Gesendet von meinem GT-I9505 mit Tapatalk

---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Ninolina:
Well, if you block proximity sensor the screen goes off. There are lots of settings in that app so you can choose a delay and the gesture like wave and numbers of waves and you can choose just blocking sensor so the screen goes off. It's really handy not to think about if you locked screen before putting your phone into the pocket or a purse. :)
[Galaxy S 4 i9505 Original Android Development] !crazy:
I read before what have you typed how reicast performs on different kernels, and I was actually referring to that post. Checking benchmarks, and compiler options/toolchain could help to pinpoint the issue. It could be that reicast doesn't like toolchain, or compiler flags used for ktoonsez, or it likes those of other kernels. If benchmarking results are not much worst with ktoonsez kernel, that could be an indication the problem is characteristic for reicast.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
But kt kernel GE and AOSP has the same toolchains and flags. So why is it different on GE and cm11 and why only his kernel..

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
It probably is the toolchain would be my guess since I play a few games on CM, like Asphalt 8 and one other race game that I cant remember and the thing flys. And those games would certainly be more demanding that reicast from the 1980's.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
There is also one difference I noticed between ktoonsez kernel, and other two, and that is entropy threshold. Faux and CM kernel use very low values, ktoonsez very high values. You can change/check this with Android Tuner free under expert mode, System Mgr, Entropy.

Both cases could have pros and cons in regard to oerformance, but I wouldn't expect it matters so muchm...
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
But should't they be the same on GE with ktoonsez kernel and cm with ktoonsez kernel?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
I noticed that remark of yours, it makes sense, but on the other hand it doesn't have to. Same compilers, options, but different ROMs, and kernels. There are so much small variables and differences between CM and GE that it is really hard to be smart. Some low level stuff is behind our capabilities to track the issue, sometimes. Of course it depends on how much time and will one has.
[Galaxy S 4 i9505 Original Android Development] 4info:
Best kernel ever, ever & ever!! Thank you so much for your hard work!!
[Galaxy S 4 i9505 Original Android Development] !crazy:
Sorry for switching the subject, but I have the question about your values for VFS cache pressure, and dirty, dirty background ratio. Did you just inherit these somehow, or you have a reason for choosing exactly these values?

I have just tried again to use ktoonsez kernel, and like usual, as soon as I open faux app to change above mentioned values my screen freezes, and I have to reboot holding power button. I'm stupid. I never tried changing these values by editing file, or using another app. Maybe there is some kind of conflict with his app. I will try that too.

I known I already asked something about swipe to wake, but not sure if that was this: Could you add a timeout option for s2w /t2w too, not only for wakelock?

For example, I don't care about 'while charging' or to have it always enabled. I would just like to be able to turn the screen on when it goes off when I read something, and couple of seconds of waiting are just enough. No need for app to be active all the time.
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
If you set the wakelock to screen off for x time you have exactly this. You can set it to 30 seconds then you also won't notice a difference in battery when you turn it off with the power button. Or do I miss something?

I think it would be good to be able to choose different options.

For example I would set it to always on when on charger and 5 minutes when an led notification occurred. And 30 seconds for screen off. Now I have to choose which is most important for me and have to forget about the other scenarios.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
For the "FS cache pressure, and dirty, dirty background" stuff, I would need sysfs file names.

All this stuff is dont in the kernel, the app does nothing except when you open, no services except for the OTA service if you enable it. To do what you want with the screen wake thing, you need to set the wake lock to: "Hold on screen off 30 seconds". U need a wake lock to make it wake up reliable so that is the solution, no need to make another timer option since it needs a wake lock anyway.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
But your kernel for GE has the same toolchain as your kernel for Aosp..

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
It doesnt matter, different ROMs
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
So why is stock kernel and faux the same on cm when playing reicast? They have different toolchains (I guess). Your kernel is perfect on GE.

Guess I give up. Thanks anyway buddy.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
I read someone mentioned s2w or t2w work for him also without wake lock activated. I understood from that it will continue to work also after wake lock time outs, but not that reliable.

Files are in /proc/sys/vm. Like vfs_cache_pressure, swappines (should be 0 when ZRAM is not enabled?), dirty_ratio, dirty_background_ratio.
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Whoever mentioned that, had a wake lock going from something else, like wifi or sms messages.

Those VFS settings came from years of research from some people that know waaaaaay more than me on that stuff. Those are all set in my file called:

/sbin/ext/post-init.sh
[Galaxy S 4 i9505 Original Android Development] Formhault:
[MENTION=4325945]ktoonsez[/MENTION]

Is NTFS support included in the kernel? I tried to mount a 16GB USB stick (NTFS format) and the phone doesn't see it. Well, it does, but it's like 0 bytes out of 0 bytes... so I guess we can say that it doesn't :laugh:.

I had to use Chainfire's StickMount to mount the storage (under sdcard/usbStorage/sda1). The /usbdisk partition (the SD card) in ES File Explorer is... empty (0B/0B).
[Galaxy S 4 i9505 Original Android Development] Chrisuk80:
Slim Bean 4.3, which kernel

I decided to go from TW 4.3 to slim bean 4.3, i was hoping i could still use your ktweaker and kernel but so far ive had no look so im starting to think they dont go together

first i flashed the TW 4.3 kernel with slim bean and it would boot, i actually didnt mean to do it, i meant to click on the 4.3 aosp kernel because thats the one i thought would work, anyway i finally reflashed the ROM and flashed the AOSP 4.3 but my screens all messed up, i have a clock either side, it keeps flashing green and it just f*cked up really

does your kernel work with slim bean 4.3 and if so which one??

many thanks
[Galaxy S 4 i9505 Original Android Development] CamFlawless:
This kernel is compatible with SlimBean 4.3. Download and flash the AOSP 4.3 variant from the OP.

P.S. you got a free thanks. :P
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
lol :D, do a full wipe, flash slimbean, then KT kernel aosp 4.3 and reboot
[Galaxy S 4 i9505 Original Android Development] Chrisuk80:
thanks for the reply, thats the one ive tried to flash twice now, maybe its the download that messed up because both times its seriously screwed up, if i click the buttons it comes up with the whole screen green, i have rows of icons all the same icon, its just madness

so with you saying its ok, guess ill redownload it and try again, fingers crossed

i know this is not the place but i really wanted to try the GE ROM thats kt as worked on but wasnt sure if it was for my phone or not since it said only for canadian phones and t mobile, im in the uk on tmobile although tmobile here is now called EE, so didnt want to flash and mess my phone up!!

im just like others looking for the best battery life

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

i have been, i go into recovery and click wipe/factory reset and click do as installing new rom and it wipes loads of folders

time to try again
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
thats not a full wipe. full wipe is to wipe system,data,cache,dalvik-cache! for system go under mounts&storage>format system, for dalvik-cache its under advanced
[Galaxy S 4 i9505 Original Android Development] Chrisuk80:
ok i see

i just installed the ROM z and the kernel and its still all green and messed up

KTs kernel are under 2 sections, INTL and TMO

im in the UK on tmobile, now aka EE, should i be flashing the AOSP 4.3 TMO kernel instead of the INTL version, maybe this is the issue??

if i should be flashing the INTL then ill do what you said!!
[Galaxy S 4 i9505 Original Android Development] hawkerpaul:
Dalvik cache is wiped in a factory reset, as a factory reset wipes /data

All custom ROMs will do a format or delete-recursive the system partition in its updater-script.

Doesn't hurt to do it all individually as well though of course
[Galaxy S 4 i9505 Original Android Development] Chrisuk80:
Just did what you said

i followed your instructions to the T but when i flash the kernel my screens, green, now pink, all supersized letter, i total mess!!

gutted!!

thanks for your help anyway
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
The problem is Slim Bean is waaay too old for the newer 4.3 builds. You need an older version of the 4.3 kernel, preferably one that near matches the build date of your ROM.
[Galaxy S 4 i9505 Original Android Development] Chrisuk80:
Thats what my next step is, im on page 100 trying to find an older version of the kernel, could be a deal breaker because i really like kt's kernel so cant imaging not using it, just got bored of stock TW
[Galaxy S 4 i9505 Original Android Development] LuigiBull23:
Did you check OP for the link to previous builds? Should be less of a hassle. I commend you for actually trying to search though.
[Galaxy S 4 i9505 Original Android Development] nielsscholte:
Wifi won't turn on with this kernel running Kitkat TW
[Galaxy S 4 i9505 Original Android Development] VictorLallemand:
Then you didnt even read what's below your download link ?
[Galaxy S 4 i9505 Original Android Development] alinghi100:
Hi, I have a problem with double tap to wake.. If I double tap when I screen off the phone it works.. if I wait 1 minute or more it doesn't work anymore.. How to solve? thanks
[Galaxy S 4 i9505 Original Android Development] ritch15:
It has, it only ran once on mine.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Could you add these things from faux kernel?

release 003 (5/23/2013)

* enbled kernel AIO optimization from Linux 3.8+

* enabled touch boost for intellidemand governor

* removed kernel debugging

Gesendet von meinem SGH-M919 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] stefyno:
I tried (now) to start antutu 3 times and 2 times it came out. You mean this?

Inviato dal mio GT-I9505 con Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] noname55804:
Is that Kernel also for ME2?

Gesendet von meinem Galaxy S IV mit Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] kenzolo:
in your setting I read

General -> Governor Adjustments Screen

boost_cpu = 1242

you mean "touch_boost_cpu" = 1242 ?
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Did 1 and 2 for you, 3 is kernel specific, we both have different stuff disabled and I have a loooooooot disabled thats for sure.
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Yes, I renamed it 2 days ago in the kernel code, forgot to rename in Post #3
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
OP Updated

Change Log 5.27.2013

1. Remove a WHOLE ASS LOAD of dmesg spamming

2. Fix some KThermal issues

3. Building with Linaro now

4. Add Faux sound

5. Added battery level Mhz control, 2 steps, Low and High

6. Raise BUS and L2 cache for OC steps for moooooooore speed

7. GPU OC to 500 Mhz

8. AIO tweaks from faux

9. New KTweaker 3.6

10. KTweaker: "Extras" now has 2 options at the bottom to Generate a dmesg or logcat to you sdcard so you guys can post debug stuff easier (always puts files in "/sdcard/KTweaker/Logs/" folder)

11. KTweaker: Everything in "Extras" is active now except - "Disable Screen Off Mhz Call", "Swipe 2 Wake" and "Trinity Colors". (getting close now :D)
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Omg are you a machine?? Awesome! THANK YOU!

Gesendet von meinem SGH-M919 mit Tapatalk 2

---------- Post added at 12:53 AM ---------- Previous post was at 12:39 AM ----------

New version works good! A few more stutters than version 26.5. here and there..

Gesendet von meinem SGH-M919 mit Tapatalk 2

---------- Post added at 01:22 AM ---------- Previous post was at 12:53 AM ----------

Back to Version 26.5. for me. Version 27.5. has some random stutters and lags... Same settings as before..

Gesendet von meinem SGH-M919 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] Lazy79:
Thanks for new version. Works good here. Will keep it. Trying faux sound tomorrow. Thanks! :)

Update:

Westwood. Thanks! All seems to work good in new version.
[Galaxy S 4 i9505 Original Android Development] btemtd:
Officially the most powerful kernel on earth... Highest Scores I have ever gotten... and To make sure it was not a fluke I did it again afterwards....

Airplane Mode , didnt want to receive a message or call during the test. And cleared memory just before the test.

Congrats dude
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Which settings do you use?

Gesendet von meinem SGH-M919 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] Lazy79:
in ktweaker? max cpu 1998 / min 378. scheduler deadline. voltages as given. screen off no more than 486Mhz and row as scheduler. and some init.d tweaks but I am lazy, thus pimp my rom app, which works - only never never install the audio etc in the extras tab.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Which governor? Ktoonzdemand seems to eat battery (goes to often over 1.1 ghz)

Gesendet von meinem SGH-M919 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] Lazy79:
hm.. its better with Ktoonzdemand than it was previously with another kernel.. I think all the kernels have not yet reached their limits :)
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Will test for 2 days... Lets see..

Gesendet von meinem SGH-M919 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] nitrogen618:
Just wanted you guys to confirm.. Or if it's just me.

On the new released version 5/27..

AnTuTu runs at 2.0ghz, but not on 2.1Ghz.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Doesn't matter.. 2.0 ghz phone lol. What more do you want??

Gesendet von meinem SGH-M919 mit Tapatalk 2