yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] -Thrive-:
mtcarey, I don't want to single out favorites. I have tried all of the kernels on this forum by boog, Kyuta Syuko, Jsmokey and yourself and they are all excellent. I can't think of a bad thing to say about any of them and we all owe this group our respect, admiration, and gratitude for your hard work and collaboration.

But I did want to point out my own personal experience on my phone running Watsa's amazingly stable Pinnacle KH3 ROM and I have found that your kernel offers the best combination of performance, battery life, and function that I have observed so far. I am impressed by your custom CWM with the important nandroid capability, and even though I haven't tried it yet, your incorporation of init.rc tweaks into your CWM is creative and valuable. One of the reasons I haven't tried it yet is because your default tweaks work so well on my phone, I haven't had a reason to experiment but I'm sure my flash addiction will take over soon and I love having this option. Keep up the awesome work!
[Captivate Android Development] droiduzr2:
What are the default tweaks?

I did not load the tweaks listed in CWM...yet
[Captivate Android Development] mtcarey:
I've fixed the .android_secure issue, and the Tibu problem is being looked at. Of course, I haven't had a problem with Tibu yet! Hopefully will have the new version out tomorrow.
[Captivate Android Development] mtcarey:
By default it uses my "syscorps.tweaks".
[Captivate Android Development] droiduzr2:
And what do those tweaks do?

Is there is thread or guide to know what these tweaks do?

thx
[Captivate Android Development] mtcarey:
I'm not aware of any specific threads relating to kernel settings, but if you search on it I'm sure you'll find lots of info. Jsmokey has done a lot of research... you might take a look at his Red Nebula thread.
[Captivate Android Development] crandy2:
Any update on when the new version will come out?
[Captivate Android Development] -Thrive-:
I suspect mtcarey is trying to sort out the TIBU restore problems. It appears TIBU restore has some dependency on CWM and the latest version of Corn has his custom CWM.

Edit: TIBU defrost also seems to be affected.
[Captivate Android Development] mtcarey:
Maybe later today if I can wrap-up a few things. The Tibu issue is still being investigated... I can't duplicate the problem! It's possible that I inadvertently fixed it in working on other things.
[Captivate Android Development] -Thrive-:
Yikes, found the cause of my TIBU problems. User error. I renamed the CWM backup folders in order to keep straight what kernel I was on at the time of nandroid backup. Had no idea that TIBU used these files for its app recovery and defrost. This may just be me but anyone experiencing TIBU issues on this kernel should make sure they didn't do the same thing. Sorry mtcarey, I messed up.
[Captivate Android Development] mtcarey:
No problem... it was good to check it out anyway, since every time I look at the CwM source I find something else to fix! New version later today....
[Captivate Android Development] getinlost:
Would that be a KK2 update?
[Captivate Android Development] mtcarey:
Yes it will be KK2.
[Captivate Android Development] Kyuta Syuko:
Any plans on releasing the source for you fixed recovery?
[Captivate Android Development] joonair:
I flashed this kernal over Illuminance 2.1 and I converted to ext4

and I noticed quite a bit of lag, and my quadrant score was at 900.

I set my CPU at 1GHZ using setCPU , but it was still laggy. What was I doing wrong? I went to recovery, then lagfix options and converted from rfs to ext4.
[Captivate Android Development] mtcarey:
Not planning to yet... it's still a work in progress.
[Captivate Android Development] mtcarey:
Did you check for any existing init.d scripts that might be messing with the mount options or the i/o scheduler?
[Captivate Android Development] joonair:
I have some files like voodoo_system conversion _ saved . tar.lzo and a voodoo folder. I am currently on samurai 1.3 for now... should I delete these files?
[Captivate Android Development] mtcarey:
They shouldn't be there anymore after you flash this kernel. The only thing that might remain are /system/etc/init.d scripts and /system/etc/sysctl.conf.
[Captivate Android Development] joonair:
so after flashing this I should look for init.d scripts and sysctl.conf. at etc and delete them? as well as the voodoo files?
[Captivate Android Development] mtcarey:
The Voodoo files should be gone... except for some on your sdcard, which shouldn't matter. The init.d scripts you can simply move to another location so they don't execute until you can ensure that none of them cause problems.
[Captivate Android Development] joonair:
Thanks :) works good now. Btw, do you recommend ext4 or ext2? I know ext4 is more stable but I heard ext2 is ALOT faster than ext4
[Captivate Android Development] mtcarey:
Ext2 is faster because it doesn't keep a transaction journal... data corruption is almost certain at some point. By default I set up Ext4 to journal /data and /dbdata, but not /cache. Best balance of safety and performance, in my opinion.
[Captivate Android Development] joonair:
Alright thanks again :) I'll report back after more usage
[Captivate Android Development] -Thrive-:
Silky smooth, voodoo sound works, like the new options under CWM tweaks menu. Great work!

Question, tweaks menu shows you are defaulting to conservative governor for scaling. When I boot and open Tegrak, it still shows on-demand. Is Tegrak overriding your default?
[Captivate Android Development] Boldizzle:
Wow!!

I've been using Samurai for the past month and a half but Corn has definitely come a long way. This is one very smooth yet awesome battery preserving Kernel.

Thanks for all the hard work mtcarey! This is outstanding!
[Captivate Android Development] crazililazn:
Is 5.01 compatible for kj3? Or is it only for the kk2 roms?
[Captivate Android Development] mtcarey:
Compatible with any I897 Gingerbread ROM.
[Captivate Android Development] mtcarey:
Yes, Tegrak will override the CwM setting.
[Captivate Android Development] 4-2ndtwin:
mtcarey,

Just wanted to stop by and say Thanks !!

Appreciate your hard work and the time u put in !
[Captivate Android Development] pcguy23:
+1

thank you
[Captivate Android Development] Kyuta Syuko:
So what all you got left planned for your recovery? (Really wants you to release the source so he can tinker with it) :p
[Captivate Android Development] :
The Voodoo Control App won't load for some reason....
[Captivate Android Development] mtcarey:
Voodoo Control App has no effect on this. Formatting is controlled through Recovery.
[Captivate Android Development] :
I was going to use it for the sound tweaks :p
[Captivate Android Development] mtcarey:
There's no Voodoo sound in this kernel. Do you have the paid Voodoo Sound library / app?
[Captivate Android Development] :
Yeah, I have the paid version, but accidentally downloaded the free version lol.
[Captivate Android Development] mtcarey:
Scaling governor

Has anyone noticed that the default scaling governor in KK2 has changed from conservative to ondemand, or is it just my imagination?
[Captivate Android Development] 4-2ndtwin:
Default is conservative here. I just flashed ur kernel an hour or so ago and haven't changed anything.

This is what it reads... Current Scaling Governor: conservative (default is: default)
[Captivate Android Development] mtcarey:
That's because in KJ3 the Samsung default was "conservative", so I set that up as the default. It seems that Samsung has changed that in KK2, so I've come up with a better way of determining the true "default". New version later!
[Captivate Android Development] hokiemoto:
Is Voltage Control compatible with this kernel or just Tegrak?

(seems Voltage Control lets you have more control of the frequencies and number of states)
[Captivate Android Development] mtcarey:
This is not an overclocking kernel, so Voltage Control hides most options.
[Captivate Android Development] ddoubt:
hey mtcarey, you might wanna add the zipalign binary to your next CWM release as most ROMs don´t have it by default... :)
[Captivate Android Development] mtcarey:
It's there in the /sbin directory!
[Captivate Android Development] ddoubt:
uhhh :o sorry, my mistake... :o
[Captivate Android Development] popfan:
You guys are making this device look good!!! Thanks for all the hard work!
[Captivate Android Development] crandy2:
Flashed the 5.03 kernel over 4.03 kernel in Fasty KK1. Seems to be a little faster for some things. Battery life still unknown, the drain seems about the same as 4.03 so far.

TiBu restores were a problem for me with 4.03, and still are with this kernel. The only way I can restore anything is to go into TiBu preferences and change the App Processing Mode to "classic". This invokes the android installer, which restores fine. If I try to use one of the other two modes it just hangs with the "restoring" message forever.

Everything is formatted ext4 (except system of course), and was when the backup was made.

I have wiped caches, and dalvik (many times). Wiping Dalvik sometimes allows one or two restores with App Processing Mode set to Auto, but then it will hang on another (doesn't seem to matter which app).

Glad to have a workaround, but it is still puzzling.
[Captivate Android Development] Kyuta Syuko:
Have you tried setting the "Restore Backups location..." to "Original Location"?
[Captivate Android Development] -Thrive-:
This happened to me when I changed kernels. Try wiping data for Voodoo Control Plus using TIBU. This forces the app to go back through the setup with the new kernel and worked for me. Be sure to also check the box that says "save on boot". The only problem I have with the Voodoo Control app is that the Headphone amplifier setting always returns to - 10 dB after a reboot. Volume limit and Bass boost hold their settings correctly. Anyone else seeing this? Maybe this is a safety feature.
[Captivate Android Development] crandy2:
Yes. That didn't help.
[Captivate Android Development] mtcarey:
I've never been able to replicate the problem. Can you tell me what ROM you're using, and the Tibu settings for "Compression", "Force system Busybox", "Enable encryption" and "Force system SQLite"?
[Captivate Android Development] crandy2:
Rom is Fasty KK1

Compression is gzip

Force system busybox is not checked

Enable encryption is not checked

Force system sql lite is not checked
[Captivate Android Development] mtcarey:
Ok, I'll keep looking.
[Captivate Android Development] popfan:
I am have the same problem on Samurai too. I am using Illuminance 2.1.1, so with the same settings as the guy above. So I think this a KK2 problem not just custom kernal problem. I have the problem in RFS and EXT4.
[Captivate Android Development] 4-2ndtwin:
Restoring through Titanium Backup

Just a friendly fyi...

After I have installed a Dev Rom and set up my Wifi, signed into the Market and reinstalled the Titanium Backup App and TB Pro Key, I have to Reboot immediately afterwards and then I am able to Restore Missing Apps with Data without any problems. If I do not reboot, that is when I have had problems with the restore process. And I have experienced the same problem as crandy2,

because

of not rebooting after reinstalling the TB app and Pro key.
[Captivate Android Development] scotths:
I am using fasty KK1 version. I didn't experience this problem using the default kernel provided with this rom (I believe the most recent KJ3 version of the corn kernel).

I just updated to the latest version of this kernel. I am experiencing the following problem: when attempting to run adb I get this error:

- exec '/bin/sh' failed: No such file or directory (2) -

Using the terminal on the phone I note that the /bin directory is empty; is this expected? Is there a sim link missing or some other way that adb should be able to find the correct shell?

Any help would be appreciated!
[Captivate Android Development] mtcarey:
I'll take a look. Quick fix... find a "sh" simlink in either /system/xbin or /system/bin and copy it to /bin. Alternative is to open terminal and type "ln -s /system/xbin/busybox /bin sh".
[Captivate Android Development] Kyuta Syuko:
First you sould check /system/xbin, system/bin, or /sbin (can't remember where he put it) for su and make sure you have Superuser installed (Superuser.apk in either /system/app or /data/app). Then you should download Stericson's Busybox Installer and make sure you have Busybox installed (it should be installed by default if I'm not mistaken). If you do reinstall it anyways (should wipe out all instances of busybox except the one being installed) and see if that doesn't fix your problem.
[Captivate Android Development] mtcarey:
His problem is that it's looking for "sh" in /bin. Busybox installs in /system/xbin.
[Captivate Android Development] Kyuta Syuko:
Yeah but it symlinks in /bin or has for me everytime I've installed it.
[Captivate Android Development] mtcarey:
Because you compressed your initrmfs, you put everything in /bin ahead of time. Busybox installer didn't do it. :)
[Captivate Android Development] Kyuta Syuko:
I remember it doing it before I started messing around with kernels, but it could have been the kernel I was using... Didn't know anything about kernel packing and what not at the time so that just totally slipped my mind...
[Captivate Android Development] mtcarey:
You should have two copies of Busybox with your kernel... the abbreviated one you put in /bin ahead of time (600kb) , and the full "market" version that resides in /system/xbin (1.9mb). When I used Voodoo and initrams compressing to make it all fit, I would erase everything in /bin after install since it normally should be empty. If you look at the stock init.rc, the /bin folder isn't even on the path.

P.S. I just found a bug in init.herring.rc (the Samsung version!):

service pvrsrvinit /system/vendor/bin/pvrsrvinit

* should be *

service pvrsrvinit /system/bin/pvrsrvinit

I'm not sure when init.herring.rc gets used. Any ideas?
[Captivate Android Development] scotths:
Thanks! Creating the symlink seems to have solved the problem. Should it be added to an init script?
[Captivate Android Development] Kyuta Syuko:
I haven't figured it out either myself =| Maybe it's something that doesn't get used but Android won't start w/o?
[Captivate Android Development] mtcarey:
I'll fix it in a new version tonight. Glad it worked! In the meantime, you'll lose it when you reboot so you might want to create your own init.d script.
[Captivate Android Development] mtcarey:
I know that init.goldfish.rc is used by the emulator... since the Captivate cpu is nicknamed "herring" I suppose init.herring.rc may provide some additional cpu-specific settings.
[Captivate Android Development] Kyuta Syuko:
Could be a possibility. Maybe I'll see what I can dig up later about it.
[Captivate Android Development] mfdemicco:
Flashed the 5.03 kernel. The tweaks can't be selected from the recovery menu.
[Captivate Android Development] xfernand:
Huge performance gain. Thanks.
[Captivate Android Development] mtcarey:
Which tweaks? Look carefully... for the "injected tweaks" it prints their contents first, then you have to go back to confirm select.
[Captivate Android Development] mfdemicco:
If I select "injected tweaks" some text appears and disappears very fast at the bottom. There's nothing to subsequently select and there is some error message in the text about directories/files not existing.
[Captivate Android Development] mtcarey:
That's bizarre... try reflashing the kernel. Maybe something got screwed-up.
[Captivate Android Development] mfdemicco:
Further information: I was able to read the text it said:

current tweak profile:

couldn't open directory

couldn't open directory

no files found

Also, in Reformatting/Lagfix Options is an error message:

E: could not open lagfix.conf!

I am using the KH3 (Pinnacle) ROM.
[Captivate Android Development] mtcarey:
Check to see if you have a folder called /system/etc/cwm5sc. If so, delete it and reboot to re-create it.
[Captivate Android Development] mfdemicco:
Thanks, that worked. There were two cwm5sc directories in there too. I deleted them both.
[Captivate Android Development] mtcarey:
Two? One was a "phantom". I'm not sure how that happens, but I've seen it a couple of times. That's why CwM was confused.
[Captivate Android Development] mtcarey:
Yikes! Turns out that the version of adbd that's floating around (134kb) is hard-coded for Voodoo, and looks for the shell in /bin. I replaced it with the version from the GB source (115kb) and everything's good. No need for a "sh" link in /bin. Will release new version in a bit.
[Captivate Android Development] mfdemicco:
Actually, there are still two of them?! I deleted them again, and still two get created.

A question: if I convert to ext4 from rfs, does the data in the partitions get saved back?
[Captivate Android Development] mtcarey:
Yes, just select the default option "with backup and restore". As far as there still being two folders created, it sounds like maybe your rfs filesystem table is corrupted. Try deleting just the "bogus" folder... if you have root explorer or estrongs highlight the folder and view properties. The "bad" folder should show some sort of error.
[Captivate Android Development] mfdemicco:
They are both good folders and are identical to each other. I tried deleting only one, and it got recreated so there is still two.

Also, I see some of JSmokey's and other tweaks in my init.d folder (probably left when I flashed other kernels in the past). What should I delete in my init.d folder? I don't want conflicting tweaks.
[Captivate Android Development] mtcarey:
I'll be releasing a new version in about 30 mins. which has some added checks for the "double folder" quirk. Hopefully that will fix your problem. As for the tweaks, init.d scripts run after the Recovery-based tweaks are applied, so they will override. I have some of Jsmokey's tweaks listed under "injected tweaks", so you might not want / need his init.d script. As for other scripts, ???. You probably should move / remove any that mess with the i/o scheduler or cpu governor.
[Captivate Android Development] :
Do you recommend a specific set of scripts? I'm using maladroit's and they are fine, but I'm just wondering what you use/prefer?
[Captivate Android Development] mtcarey:
I use my own "syscorps.tweaks" that I've used for awhile, but I really haven't had a chance to compare them against the others. You can also roll your own: create a file in the /system/etc/cwm5sc/tweaks folder with a ".tweaks" extension, and it will show up as an option in Recovery.
[Captivate Android Development] :
Sweet! Thanks a lot. I love the kernel, super smooth.
[Captivate Android Development] -Thrive-:
FYI, just flashed 5.04 and still have the duplicate cwm5sc folder. Deleted both folders using RootExplorer prior to the flash. Have had duplicate folders with all Corn 5.x versions. Doesn't seem to be hurting anything though. My config is in my sig. Currently injecting JSmokey's tweaks and running very well as it did with your syscorp tweaks. Not doing anything else in init.d at this time other than the scripts you included with the kernel. Interesting that I installed Corn 5.03 on my wife's phone yesterday and no duplicate. Exact same phone except hers is running Pinnacle 1.2 and no overclock.
[Captivate Android Development] mfdemicco:
I still have the duplicate cwm5sc folders with 5.04 as well. I deleted both folders like you did right before the flash to 5.04.
[Captivate Android Development] mtcarey:
Really strange. Can you guys try an experiment? Delete both folders, then re-create an empty "cwm5sc" folder in /system/etc/ manually. Re-boot, and see if there are still two.
[Captivate Android Development] -Thrive-:
Tried it. Still created duplicate folders after reboot.
[Captivate Android Development] mtcarey:
Ok, I'm going to add a new "rfs repair" function to Recovery tonight. In the meantime, I just updated the 5.04 images with a few more safety features if you want to re-download and re-flash. I know I should increment the version number, but I need to leave soon and don't have time! New version tonight!
[Captivate Android Development] crandy2:
Yeah I have duplicate folders as well.
[Captivate Android Development] mfdemicco:
I have another issue. I don't think init.d scripts are working. I have a script, which worked fine under version 4.x, but doesn't work under 5.x. It can be run manually, however. It's the script posted here: http://xdaforums.com/showpost.php?p=19005820

One other variable, I converted from rfs to ext4, if that makes any difference.

Edit: I got the script to work by changing some settings via Script Manager. Not sure why it wouldn't run by default, though.

---------- Post added at 01:51 PM ---------- Previous post was at 01:14 PM ----------

It's weird. I create one cwm5sc folder, but 2 get created. I delete one, both get deleted. I renamed one and deleted it, then the other remained. However, after a reboot, there were two cwm5sc folders.
[Captivate Android Development] -Thrive-:
Are you going to use supercurio's fix?
[Captivate Android Development] crandy2:
Release 5.04 seems to have fixed my TiBu problem, I restored everything I possibly could with the App Processing Mode set to Auto, direct and it worked fine !
[Captivate Android Development] mtcarey:
Great! Not sure how that got fixed, but I'll take it.
[Captivate Android Development] mtcarey:
I was looking at supercurio's rfs repair this morning. But I think I'm just going to adapt the current backup - format - restore functionality in CwM. As long as I'm doing that, I thought I might as well extend the ext4 option to the /system partition. One thing leads to another....
[Captivate Android Development] mtcarey:
Did you check to make sure init.d scripts are enabled through the "Tweaks / System Toggles" menu? Also, if you have the "double folder" issue, then that would probably prevent init.d scripts running if the config file in that folder is unreadable... can't read the switch!
[Captivate Android Development] mfdemicco:
Ah so, it was toggled off by default (I would think most would like to have it on). Both folders seem to mirrors of each other.
[Captivate Android Development] Cdub5:
So I just flashed this and seems nice so far. One issue is that all of a sudden when I try to freeze an app using tibu, tibu says its frozen, but its not. I'm running illuminance ROM, and I froze some apps when I just flashed ROM with samurai kernel, and it worked fine. I've had this issue before when I flashed fasty kj3. Apparently the newest version of busybox was causing the prob, so thru busybox installer I downgraded to an earlier version and that fixed it. Tried the same here, and its a no go. Any suggestions?
[Captivate Android Development] -Thrive-:
I had the same problem and fixed it but can't recall for sure which action did it. I suggest trying:

1) use TIBU to backup and restore the app that won't freeze and try to freeze again. If that doesn't work try 2).

2) go into recovery and do a new CWM backup, reboot and try to freeze the app with TIBU (I think this is what fixed it for me).

3) Never hurts to wipe data for TIBU
[Captivate Android Development] visionlogic:
After reading the posts about the duplicate cwm5sc folders, I checked my phone with root explorer and indeed I found 2 folders, one named cwm5sc (all lowercase) and one CWM5SC (all uppercase). The cwm5sc has today's date, the CWM5SC is dated Nov 9. The folders contain different content.

Now here's the weird part - if I exit root explorer then reopen root explorer the CWM5SC folder is not there, only the cwm5sc folder appears. If I reboot and then again check with root explorer the CWM5SC is back again with the same Nov 9 date. Exit root explorer and then open it to check again and CWM5SC is once again gone.

I don't seem to be suffering any ill effects from this, I'm just posting it hoping that it may yield some clue to those much more knowledgeable than me.