yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Kyuta Syuko:
Thanks for the info. Some of the users might find it useful.
[Captivate Android Development] ddoubt:
hey kyuta, you're running stock kj3 right? are you on rfs or ext4?
[Captivate Android Development] rajendra82:
Kyota:

This kernel has served me well while on KJ3. Thanks for all the hard work. Are you planning to patch the new KK1 leak with the fixes?
[Captivate Android Development] Jsmokey:
Don't really know how much could be gained by this since IlluminatedOne reported it boots with kj3 kernels no problem. I was actually going to start porting my kernel over till I read his post about it in the kk1 thread.

Might be worth pulling the kk1 kernel apart though just to see if there are any differences between the two.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] 1tontomato:
This is the XDA and to say one thing is better than another is an irrelevant statement. There are a lot of devs that make REAL contributions. Saying one thing is better than another is just an opinion, but in my honest opinion "Fusion" and "The Collective" make my experience, with my captivate a proud one. I'm always saying things like "does your iphone do this" and they always say "WoW that's cool.......sad face.... no" you guys make it work.. Thanks everyone.
[Captivate Android Development] Kyuta Syuko:
EXT4 is what I'm using on odexed KJ3. Will see about messing around with KK1 this weekend unless something else comes out.
[Captivate Android Development] rajendra82:
It might be worth it, just to get any bugfixes that might have been implemented in the KK1 kernel.

Edit: or the KK2 kernel.
[Captivate Android Development] Soy_Filipo:
Will you be releasing a kk1 or kk2 version?
[Captivate Android Development] Kyuta Syuko:
I'm currently working on a KK2 based Samurai. Was thinking about releasing two different versions -- a KK1 and a KK2 -- but I decided that'd be fairly pointless. Currently working on adding a few tweaks and then I'll move it over to the KK2 base. Not sure how long it'll take.
[Captivate Android Development] Kyuta Syuko:
Alright got my KK2 kernel packed and uploaded, but it's untested. Currently backing up my phone to install KK2 Stock. Will update the first post in a few minutes.

*edit*

Links pulled due to it not working...
[Captivate Android Development] blutruck:
I downloaded it last night before you pulled it and installed it this morning before I read your post. It does work with lagfix disabled but hangs at ATT screen with it enabled. I booted into recovery and disabled lagfix and it boots now, but when it boots it is as if it did a factory reset. No apps, wifi info missing, bluetooth info missing. It runs smooth otherwise...
[Captivate Android Development] Kyuta Syuko:
Didn't try it with lagfix disabled. Thanks for that info.

*edit*

Ok I'm a dumbass. Forgot to comment out a line in the init.rc file. Repacking now to test it.

*edit 2*

Ok passed the AT&T Screen but bootloops... Might be a while...

Got the same thing when I disabled lagfix. I wonder why...
[Captivate Android Development] IlluminatedOne:
I am waiting for Samurai 1.3 :) So far Samurai 1.2 (lagfix disabled) is working pretty much fine with KK2 Stock deodexed.

LOL!! :p Didn't notice it before!!
[Captivate Android Development] TonyStark R.I.P.:
Yip yip yipee
[Captivate Android Development] Soy_Filipo:
Whats is LMK? Does it makes multitasking better or something?

Sent from my Galaxy Captivate, not that you care, just saying...
[Captivate Android Development] Kyuta Syuko:
LMK is Low Memory Killer. It determines which apps will be killed at what free memory threshold. Less aggressive LMK settings will allow better multi-task-ability but will probably cause you to experience more lag due to less free RAM while more aggressive LMK settings will allow more free RAM and less lag but you won't be able to multi-task as easily.

I've managed to get 1.3 working so I'm uploading and will update the first post in a few.

*edit*

Ok OP updated let me know how it works out.
[Captivate Android Development] TonyStark R.I.P.:
SGS not liking it. Problem w/ zimage
[Captivate Android Development] Kyuta Syuko:
Which file did you download? CWM flashable one?

Also from which link?

*edit*

I'll have to fix it later I'm heading out now... On the other hand the tars should work if you want to try Kernel Flasher.
[Captivate Android Development] TonyStark R.I.P.:
That's what I used bro

~~ Odin/Heimdall/Kernel Flasher tars ~~

Dropbox USED this file

Crate

Ubuntu One

~~ CWM Zips ~~

Dropbox

Crate

Ubuntu One
[Captivate Android Development] TRusselo:
title of OP still says kj3, not kk2 as it says in changelog.
[Captivate Android Development] Kyuta Syuko:
I think I know what might be wrong, but It'll have to wait till I get home.

*edit*

Ok tars have been fixed and should be working correctly now.

Fixed Thanks
[Captivate Android Development] emuneee:
Got the KK2 Samurai Kernel 1.3 working well on my own customized KK2 ROM....thanks!
[Captivate Android Development] nakedninja42:
I couldn't get the tar's to work with ODIN but it did work with SGS Kernel Flasher... :confused:
[Captivate Android Development] Kyuta Syuko:
What error was Odin giving you?
[Captivate Android Development] nakedninja42:
ODIN would get to the point of flashing the kernel and it would hang. I let sit a couple times I tried, first 10 minutes and the second time for ~ 5. I unplug from ODIN and reset it with stock kernel and flashed no problem. I tried creating a new tar with the zImage and still would hang.

Kernel Flasher flashed with no issues, not sure why ODIN would hang for so long.
[Captivate Android Development] Soy_Filipo:
Wall will happen to apps IM apps like Whatsapp, PingMe and such when the memory its low? will they be automatically closed?
[Captivate Android Development] xfernand:
I was able to flash with Kernel Flasher as well but I'm getting a list of access errors when rebooting inot Recovery.
[Captivate Android Development] Kyuta Syuko:
If the threshold that they're set to is reached yes. With my kernel that should only happen if you're playing a resource intensive game or using a resource intensive app. FYI LMK is built into the stock kernel so there is no getting rid of it.

I'm able to get into recovery just fine. What errors are you getting?
[Captivate Android Development] RDI:
I went into Recovery and flashed from 1.2 to 1.3, then after booting added zipalign folders and rebooted. I have the paid Voodoo app and it has had lagfix enabled. So far, so good.

SGH-I897 w/Modem UCKK2

Samurai Kernel 1.3

with zipalign & lagfix

Illuminance 1.1.0 2.3.5
[Captivate Android Development] xfernand:
See attached...
[Captivate Android Development] Kyuta Syuko:
That's rather strange... Have you tried redownloading it and/or reflashing it? Might have been a bad file/flash.
[Captivate Android Development] boog:
For future refrence, all of these builds that work with each other, you just typically need to swap the lib folder and repack against the new kernel. (as long as there weren't any huge changes or improvements)
[Captivate Android Development] Kyuta Syuko:
Yeah I figured that out which is how I was able to get it to work, but for some reason the tar file is messed up... the CWM file seems to work just fine though.

Going to make a new tar file and see if it'll work for everyone...
[Captivate Android Development] boog:
did you tar it in linux? I never really get to test mine, using heimdall.
[Captivate Android Development] Kyuta Syuko:
Well I tared it incorrectly with the tar command (added in a directory) then fixed it with ark. Just now tared it correctly with the tar command (like I did with the previous versions) and uploaded and changed the link in the OP. Hopefully they'll provide better results.
[Captivate Android Development] boog:
It happens to the best of us ;)

I spent the day tinkering with kernel source, managed to get talon ported over and booting before I remembered the whole i9000 kernel on a i897 rom causing bluetooth issues. And still cant get the kh2 source to build properly.
[Captivate Android Development] loudoun83:
Will the Samurai 1.3 KK2 Kernel work with a KH3 ROM? I read on xda that builds after KH series were really for the i-997, the last best one for i-897 was the KH series?
[Captivate Android Development] boog:
It should run.
[Captivate Android Development] Kyuta Syuko:
I've not had any issues yet with KK2. Not like the KJ series anyways.
[Captivate Android Development] loudoun83:
Thanks Kyuta and Boog
[Captivate Android Development] ddoubt:
so... KK2 is performing better than KJ3 then? Which issues you´ve had that you don´t have anymore?
[Captivate Android Development] TonyStark R.I.P.:
This is a very good question! I have loaded everything on kk2 that I was running on Illum rom. Whith this kernel I have the same lag. It always seems to happen directly after a sleep period. Whenever I wake it and use Widget Locker to open it lags, almost like it's still waiting for it to come out of sleep.

This did not occur while using Boog kj3, so there is a specific lag in place.
[Captivate Android Development] Kyuta Syuko:
The issue with the AT&T Address Book is not there, my GPS seems better overall (doesn't take forever to lock if it locks at all), and that's about all I can think of/have tested so far... Phone does seem a bit more responsive though.

Well I have an idea what might cause that. Do you experience it on any other kernel like Red Nebula or Corn?
[Captivate Android Development] TonyStark R.I.P.:
Haven't used Corn yet but yes on red
[Captivate Android Development] bobgodd:
Flashed over Pinnacle and now I have no cell signal at all.

Samurai 1.2 worked great on the same phone. Anyone have any insight??
[Captivate Android Development] TonyStark R.I.P.:
well what did you do and how did you go about it? My first thought would be to flash a different modem
[Captivate Android Development] Boldizzle:
While this is sounding tempting, the fact is, Samurai 1.2 is working so well on my Phone running Pinnacle 1.2 that I'm too scared to jump to 1.3 coz I can't imagine how much better it could get and you know the old saying "If it ain't broke, don't fix it".
[Captivate Android Development] Kyuta Syuko:
Then it probably has to due with the ondemand tweak. Both Samurai and Red Nebula have it set to not scale as fast which could cause the lag on wake-up.

Like mentioned above I'd try reflashing the modem.
[Captivate Android Development] xfernand:
Resolved the issue...

Remove

"enable-zipalign-system"

"enable-zipalign-data"

Problem gone...
[Captivate Android Development] ddoubt:
so is there a way to change that so it will fix the lag wake-up? what will be the effects of this change?

also, Id like to know the tweaks you applied on this new 1.3... they are all in the kernel, not init.d scripts right?
[Captivate Android Development] Kyuta Syuko:
Well the kernel itself isn't going to resolve those issues. They're more ROM related. I did add a few more tweaks and did the read ahead a bit better in 1.3.

Yes they're in the kernel. Could write an init.d script that would overwrite the kernel setting. All it dose is wait till the CPU is being heavily used. I think I have mine set to 75 or 85 while Red Nebula has it set to 95, but I'm not 100% sure on that nor am I at home to check.
[Captivate Android Development] Kyuta Syuko:
I thought the factory was lower then that. Or rather I thought the factory setting was set pretty low. Yeah I don't think I've touched it since setting it so if it was 65 in an older version it's probably 65 in 1.3. I wanted to say 65 but wasn't really sure about it and I was sure yours was 10 or 20 higher then mine.
[Captivate Android Development] Jsmokey:
Androids could be lower but I doubt it because the default in the linux kernel is 95 and google really didn't change squat as far as any of the governor, kernel scheduler, i/o scheduler, honestly almost any setting I've crossed checked against default linux settings which is a lot of the reason tweaking them is such a big help on android and linux. Most of these have been default, set in stone it would seem, settings for linux for I'd say close to 10 years with virtually no changes. If you run linux btw I'd recommend try to "echo" some of these settings to change them and I'd almost guarantee you see a big performance difference if not all will be back to normal after a quick reboot.

If you are interested I can supply you with some very good linux kernel tweaking links. I've actually really started playing around on my old pentium4 machine a lot again since doing it since I don't really have a lot of the stutters and lag anymore after building a new kernel and trying it out on it.

I mean its overclocked to 3.4ghz and has 4gb's of ram and a 1gb ati graphics card (used to be top of the line but barely low end by today's standard) but it used to really lag down under everyday use for me graphics editing, messing around with aosp/cm7 building, plus I use a lot of screenlets and system monitors and can go for days without a reboot without ever really getting any lag. On my newer machine, amd quad core black edition running 3.9ghz, 8gb's ram, sapphire radeon hd6950, its like night and day because the kernel was pretty much almost a bottleneck on the overall performance of the machine.

Anyways I wont waste anymore of your threads space, sorry for the small book I left earlier btw.
[Captivate Android Development] Kyuta Syuko:
Well like I said in my post I wasn't 100% sure of the settings so I'm glad you corrected me, and I'm always interested in learning so if you could PM me the links that would be great! =D

With that said Jsmokey mentioned the lag issue being related to the sdcard tweaks on his thread.
[Captivate Android Development] ddoubt:
Hmm... with both your kernel and Kyuta's before adrenaline shot I was having more lag and not so good multitask (which didnt changed much now anyway)... also something I noticed was gallery3d pics loading time... on adrenaline it is really fast (on v1 aggressive its really slow)! Also I have more free ram now with adrenaline... around 80m at least... so less lag... what tweaks could have cause these differences?
[Captivate Android Development] Kyuta Syuko:
Only time my Gallery3D seems to lag is right after wake-up, but I also don't have that many pictures on my phone, but the speed of this is generally affected by the read ahead tweaks [edit]and mount options as stated by Jsmokey[/edit]. I think the USAS uses the same setting as Red Nebula but I'm not 100% sure while my kernel uses half of what Red Nebula is set to.

Multi-task-ability is inversely related to phone lag/free RAM which as most know is handled by the LMK. More aggressive LMK settings = more free RAM and less lag at the cost of multi-task-ability while less aggressive LMK settings = less free RAM and more lag but better multi-task-ability.

The LMK settings on my kernel kill the empty apps (apps that you exited awhile ago) at 80M of RAM free and the hidden apps (apps you exited or switched from not too long ago) at 60M of RAM free to try and keep the lag to a minimum while the script I added to the OP at a few people's request kill the hidden apps at 40M of RAM free to try and provide better multi-task-ability.

Not sure what the USAS settings are as I haven't looked at it in a while.
[Captivate Android Development] Jsmokey:
As far as lag from the buffers thats a boot up only issue after that they are a non issue it just takes the system a minute to fill them at first and I just thought I'd throw the up threshold out there, I'm far from knowing everything about the kernel and how it works but I do have a good few years working with the linux kernel. Soon as I can though I'd be glad to pm the links to ya.

Like I said most of his are tweaks aimed more towards a pc you will see some benefits of less lag from time to time but with granularity and latency so high its going to lag, maybe not on the outside but when it really matters cause mundane things will lay around in the cpu while something new is trying to open. Basically the granularities are how much time the processor alots to each open application at a time making it higher allows each individual app more time to finish its work but would be bad for switching between open ones especially on a phone where everything opens in its own interface instead of a unified desktop environment and when we're talking about processors with such low nm these days its more efficient to allow the processor to go shorter periods for each cycle instead of a couple long cycles.

Also adrenaline scans for usage to hit over 75% every 20ms which would give the impression of less lag but has the side effect of lowering battery life some, not much really but it does effect it some.

The reason for gallery loading faster is the mount options adrenaline uses its simply better than default and will help with loading time in certain applications and accessing files like I said in my thread though my gallery loads almost instantly with over a 1000 images.

Actually you wont see really any lag in android at least with how much ram the cappy has till 60mb and even then its almost unnoticeable till about 45-50mb. I really don't understand how you stay at 80mb free with adrenaline since swappiness is at 0 meaning you use swap 0% of the time which might improve performance till you start running out of ram then it can't move anything out to swap and has no choice but to start killing apps to free more memory up which is probably happening fairly often.

On top of all that using a locker app is going to cause some lag when unlocking, its it's own app it has to send a signal to block the default one, then access the necessary files to load it and then use up some amount of cpu to load and while each might not be a big deal on its own its but it adds up. And with swappiness set to 0 its probably getting killed even while the phone is asleep quite often. To each his own though. I've ran mine, kyuta's and mt's kernel without any lag issues other than the occasional hiccup when going a little overboard multi-tasking but that's just me.
[Captivate Android Development] Jsmokey:
Yep USAS does use the same read ahead buffers as mine. Only difference would really come from the mount options which while not make a huge difference but some. I've actually considered adding them in for a while now.

Mine kills empty apps at 60 and right around 48 kills hidden which can result in some lag but I found out a lot of times it still won't drop that low for me except with very power hungry games or apps. Its the best in between balance I could find for the aggressive version, the standard one waits much longer for multi tasking use.
[Captivate Android Development] Kyuta Syuko:
I set the Empty apps high because I figure most people wouldn't care if those got killed since they're "old news".
[Captivate Android Development] Jsmokey:
Yeah pretty much, I've considered setting them higher but just haven't had time to test them at a higher setting.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mikel.canovas:
Will this work on kk1?
[Captivate Android Development] Kyuta Syuko:
It should work as far back as the KH releases I think. I'm pretty sure some people have confirmed it working on KJ3 so KK1 should be no problem.
[Captivate Android Development] :
This is probably a stupid question but can you make nandroid backups with the cwm that is in this kernel? I'm running this on the Stocky Kk2 rom.
[Captivate Android Development] Kyuta Syuko:
According to boog (who made and tested the recovery) you can make nandroid backups but you can only restore them while using ext4 and only once per conversion. Meaning you'll have to convert to rfs then back to ext4 to restore the backup. Once mtarey releases his modified source where he fixed nandroid and added lots of extras I'm going to see if I can't take his source and make my own recovery to fit my needs (or have boog do it since he knows what's what)
[Captivate Android Development] :
Alright, I'm not going to mess with it. I'm going to stay on this rom and kernel for awhile anyway. This kk2 rom and your kernel are flawless. Thanks
[Captivate Android Development] loudoun83:
@kyuta,

If memory is being efficiently managed in your kernel, do we need a market program called "autokiller memory optimizer"?
[Captivate Android Development] Kyuta Syuko:
Most Android Gurus consider any auto task killer app taboo with the exception of Watchdog since it doesn't look at memory use, but to answer your question. No you shouldn't need it.
[Captivate Android Development] loudoun83:
Thanks for the info:)
[Captivate Android Development] Kyuta Syuko:
Just wanted to give a quick update. While I have a KK4 based version cooking in the oven the KK2 based version seems to work fine with KK4.

*edit*

I just want to clarify that the porting isn't what's cooking. The porting is done I'm adding in some other things and editing a few other things.
[Captivate Android Development] Kyuta Syuko:
Was trying to hack the cache but it's gotten late now so I'm just pushing out what I got. Will try again after work tomorrow for the hacked cache. 1.4 is up in the OP.
[Captivate Android Development] Kyuta Syuko:
If anyone downloaded 1.4 prior to this post there was a typo in the modified sqlite script which I just fixed and uploaded the fixed versions with no version change.
[Captivate Android Development] ddoubt:
what would be the hack on cache?
[Captivate Android Development] Kyuta Syuko:
Trying to make it bigger (like the link in the link in my sig) without the use of a file, but I might just have to go the file route...
[Captivate Android Development] ddoubt:
That hack will be nice! I´ve been wanting to include it on Serenity for some time but I couldnt get the init.d to work either...
[Captivate Android Development] hokiemoto:
Maybe a noobie kinda question, but why are there two voodoo folders created?

/voodoo

/sdcard/Voodoo

Pretty sure it's not carryover because I started clean.

Also, is wiping battery stats necessary after a kernel-only flash, or only with a full rom?

thanks
[Captivate Android Development] mbc663:
Wow, awesome work!!!!!
[Captivate Android Development] TRusselo:
works fine on Kh2...

now how about custom shutdown animation? lol
[Captivate Android Development] kitkitfok:
Will you port any sharpness fix?
[Captivate Android Development] Yuna:
Hope this will work on KH3 rom...
[Captivate Android Development] Yuna:
I am still alive xD
[Captivate Android Development] Kyuta Syuko:
Is that kernel based? I know nothing about the GB custom shutdown animation...

What do you have in mind?
[Captivate Android Development] Yuna:
He presumably means voodoo color.
[Captivate Android Development] kitkitfok:
Yes, Voodoo color or Speedmod or Galaxian sharpness fix are welcome.

I have flash stock rom before, Samsung stock sharpness is too horrible.......

http://project-voodoo.org/color

sharpness fix + voodoo sound + i897 kernel base noise cancellation = perfect
[Captivate Android Development] Yuna:
Might we can have this fix by just loading some .ko modules?
[Captivate Android Development] Kyuta Syuko:
I read somewhere that proper implementation of Voodoo Color requires source. I'll do some research into it though.
[Captivate Android Development] topiratiko:
Kyuta Syuko thanks for the shout out in op!!! I used all my thanks yesterday on existz but your next! lol think im gonna try this soon
[Captivate Android Development] bames:
wow these are dropping fast....seems like a new build almost every other day lately.

at least samsung finally got on the ball with posting the base firmwares
[Captivate Android Development] Kyuta Syuko:
It has been about every other day... I expect another leak tomorrow :p

Just want some verification that custom boot animations are working properly.
[Captivate Android Development] emuneee:
Working quite nicely on my KJ1 ROM.
[Captivate Android Development] bearnakedbrew:
Works good on KJ3, flashed .tar with sgs kernel flasher.