yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] -Thrive-:
Your symptoms are different than mine. My duplicate folders are both lowercase, have the same date, and same contents. From the little I have read about RFS corruption, your symptoms seem to be a clearer indication of it, particularly the uppercasing.
[Captivate Android Development] visionlogic:
I see. Thanks.

I read supercurios RFS corruption thread and his automated kernel fix but it's for I9000's. Any idea of how to go about fixing this RFS corruption on my Cappy?

EDIT - Nevermind. Converted to ext4 and the all CAPS folder no longer appears. Thanks.
[Captivate Android Development] -Thrive-:
mtcarey is working on it. His post is about 6 posts back (page 54). He was going to release it last night but he also wants to include EXT4 for /system so it will be a little longer.

Edit: our posts crossed. Glad that worked for you.
[Captivate Android Development] Cdub5:
So I've wiped data in tibu, uninstalled, reinstalled it, I've wiped cache and dalvik, reflashed the kernel, did a bu in cwm, tried older versions of busybox, tried restoring apps with tibu (which didn't even go, it just got stuck on the first app restore, which was another issue I had in the past) and still can't freeze apps. There are two apps that are frozen from when I was on samurai kernel, but I can't freeze any now. Hope there is a resolution, cuz this kernel is very nice.
[Captivate Android Development] mfdemicco:
I do not think this is rfs corruption. These are the only two folders we are having trouble with. It must be kernel / CWM related.
[Captivate Android Development] mtcarey:
It seems to be an issue with detecting the presence of that folder from within Recovery and not recreating it. Funny thing is, it doesn't happen to me (of course), though it did happen once early on in development. It also shouldn't be possible. I'm adding another method of checking.

I'm pretty close to getting the new version out with RFS partition repair and Ext4 for /system. Testing / debugging now.
[Captivate Android Development] Cdub5:
So I flashed red nebula kernel to see if it fixed my tibu not freezing apps issue, and it did. Not sure why after all my attempts to fix this issue on this kernel, (a couple posts above explains) I was not able to. Possible bug? Hopefully its fixable cuz I really like this kernel
[Captivate Android Development] mtcarey:
Yes, it must be a bug. It's next on my list to look at after I finish the /system ext4 option.
[Captivate Android Development] Cdub5:
Thanks,I appreciate it. Your kernel rocks
[Captivate Android Development] -Thrive-:
This may be a long shot but maybe TIBU is stuck trying to do freezes/restores using a CWM backup created while on a prior kernel. Before he resolved his problem by flashing a different kernel, I was going to suggest to Cdub3 that he go into /clockworkmod/backup and rename all folders except the last one that was created while on Corn, and then wipe TIBU data (or uninstall/reinstall) to force TIBU to use the last backup folder. Just a thought.
[Captivate Android Development] ddoubt:
hey mtcarey.... pikachu's thunderbolt will replace your tweaks, right? Have you tested it yet?
[Captivate Android Development] mtcarey:
I haven't looked at it yet, but I see a lot about it. I'll check it out. The Recovery-based tweaks get applied before anything else, so you can override them with anything in init.d. You can also turn off the Recovery "injected tweaks" by selecting "no.tweaks".
[Captivate Android Development] mtcarey:
Ok , I took a quick look, but haven't yet tested. If you're going to use these, I suggest the following settings in Recovery to avoid redundant processing:

1) Injected Tweaks: no.tweaks

2) I/O Scheduler: default

3) Scaling Governor: default

3) Block I/O Optimization: OFF

4) init.d scripts: ON

5) sysctl.conf: ON

Darky's Zipalign script that actually works

This is already included in the CwM install, but you can replace it if you want.

Patched libsqlite that disables the need to fsync. Extremely fast database writes.

This is great! I've been looking for this.

zipalign binary

Already included.

sqlite3 binary

Already included.

remount script - Included in /sdcard/bolt_scripts/

I'll have to take a close look at this to make sure it doesn't cause any problems.

sqlite_optimize script

Already included.
[Captivate Android Development] ddoubt:
Hmm.. I´m gonna do some tests here... I´ll let you know how it goes on Serenity with your kernel...
[Captivate Android Development] mfdemicco:
If you can include the Thunderbolt tweaks as an "injected tweak," that would be awesome.
[Captivate Android Development] Kyuta Syuko:
From my understanding YOU should be able to add any tweaks you want to the "injected tweak" by sticking them in a specific folder that I can't recall atm but should be in the first post on how to do it (but as of this post isn't).
[Captivate Android Development] mtcarey:
Once I get outstanding issues settled I plan on creating a "how-to" guide. You can create your own "injected tweaks" by creating a file with a ".tweaks" extension in the /system/etc/cwm5sc/tweaks folder. The format / syntax must be compatible with init.rc however, so init.d scripts would need to be translated. No shell commands in init.rc!
[Captivate Android Development] Kyuta Syuko:
Just out of curiosity would they be able to make a service like the ones near the end of the init.rc that calls a shell script (or init.d script if you prefer them called that)?
[Captivate Android Development] mtcarey:
I thought about adding that, but was concerned that a bad shell script run as a service in init.rc might prevent the phone from booting. Better to leave those to init.d, I think.
[Captivate Android Development] Kyuta Syuko:
Wouldn't a bad shell script in init.d keep the phone from booting anyways? Or at least throw it into a bootloop? Wouldn't running it as a service via "Injected Tweaks" make it easier to "fix" since we could just boot up into recovery and turn it off?
[Captivate Android Development] golfslicer:
Installed Serenety 5.3, restored with titanium backup, installed this kernel, then later installed some new apks from the market. The Apps installed to externel sd. I tried to move them to internal memory, via Gemni App manager. The program ran through and appeared to work, but didn't. Removed external SD card and apps gone, so I reinstalled to phone without external sd in and they installed correctly. Then put external sd back in. Is this a known problem. I'm guessing that titanium restore won't work either via batch?
[Captivate Android Development] popfan:
I got that weird error again. .android_secure image not found. Cannot restore /sdcard/.android_secure. Something went wrong while doing the reformatting. sorry.

Is it that file is missing or just not being created?
[Captivate Android Development] ddoubt:
hey mtcarey, is there a way to install you kernel with no_tweaks by default?I'd like to include it on serenity RC5.4 but I want to use pikachu01's thunderbolt...
[Captivate Android Development] mtcarey:
You can turn off init.d scripts from Recovery, too. An example of a "bad" shell script that would kill boot in init.rc but not in init.d is one that tries to remount the partitions in some incompatible way (lots of those around).
[Captivate Android Development] mtcarey:
Fixed in new version, which should be posted later today. The problem is (was) that nandroid backs up ".android_secure", but doesn't restore it if it's empty. I changed the code to ignore any errors from that.
[Captivate Android Development] mtcarey:
Yup, it's that way in new version to come.

-----------

Defaults:

adb root and debug = ON

block i/o optimization = OFF

init.d scripts = ON

power on sound = ON

power off sound = ON

sysctl.conf = ON

injected_tweaks=no.tweaks

scaling_governor=default

io_scheduler=default

P.S. Recovery expects "su", "sqlite3", and "busybox" to all be in /system/xbin. I think your ROM puts them in /system/bin, so you might want to change that.
[Captivate Android Development] mtcarey:
The new version I will post a little later today will (hopefully) resolve Tibu problems. I've tested it every which way and it works fine.
[Captivate Android Development] Kyuta Syuko:
Oh right totally forgot about the ability to turn init.d on and off... I really can't wait till you release the source =3 No hurry though I'd rather have a good, well coded product then a quick, sloppy, patchy one.

I lack the patients to go through all the recovery code and figure it all out myself. Especially since two guys who have say the code is really messed up. Besides I'm a C++ guy though from my understanding and what C code I have looked at the differences between C++ and C are like the differences between Mexican Spanish, Latino Spanish, and Spain Spanish.
[Captivate Android Development] droiduzr2:
It just makes one wonder if you "hacks" can do all of this for fun that you are so persistent and constantly evolving...imagine if we tapped your minds to solve medical problems.:cool:
[Captivate Android Development] mtcarey:
My mind is pretty well "tapped-out" after staring at this CwM code for hours. :eek:

New version 5.05 just posted!
[Captivate Android Development] visionlogic:
Thanks for all your hard work mtcarey! Just installed 5.05, converted system to ext4, will test out today.
[Captivate Android Development] Kyuta Syuko:
If they could convert diseases into poorly written C code then mtcarey could rewrite a cure for them. Even AIDS :eek:
[Captivate Android Development] ddoubt:
kk4 is out, do you think corn 5.05 would work with this leak?

have anyone tested yet?
[Captivate Android Development] -Thrive-:
Good morning and Thanks!!! Installed 5.05, love your implementation of RFS partition repair. Ran repair on /system and guess what. No more duplicate cwm5sc folder. Yay!!! Awesome job!!!
[Captivate Android Development] crandy2:
Flashed 5.05 this morning on Fasty KK1. Seems to work great so far. Gallery came right up (had been a problem with 5.04, and TiBu restored 5 apps flawlessly.

Thanks mtcarey !

One question. You added ext4 for system in this release. With previous releases you said you didn't think it would make much difference whether system was ext4 or rfs. Did something change your mind?
[Captivate Android Development] Kyuta Syuko:
I haven't tried it yet but with the way things have been there's a good chance it will.
[Captivate Android Development] msprag13:
I was able to use the kh3 to access cwm and reflash Pinnacle 1.3 on one bad flash and the kernel itself was good enough on the second beta.

So you can't even use the volume+/- keys for cwm?

never mind you fixed it with pinnacle
[Captivate Android Development] Geezer000:
I could get into CWM no problem but no matter what I did (running fusion) it bootlooped or stuck on the ATT screen. Once I reflashed pinnacle instead it booted right up.

There's something iffy with the kernel and Fusion.
[Captivate Android Development] mtcarey:
I just looked in Fusion... there is an init.d script in there called "00remount" that remounts the system partition. It doesn't look ext4 friendly. I'm not sure that's the problem, but it's a strong possibility. It should be removed before flashing over Fusion.
[Captivate Android Development] hoopas:
VOODOO!!!! Thank you! Has anybody got BLN working?
[Captivate Android Development] Kyuta Syuko:
Can you get BLN working w/o Sources?
[Captivate Android Development] mtcarey:
I included the binary for it, but to be honest, I don't really know what it's supposed to do! Is it supposed to flash when you get a message?
[Captivate Android Development] hoopas:
The softkeys stay lit after you get a notification & the screen turns off. Handy feature for at least me.
[Captivate Android Development] Roof King:
Working great on Pinnacle 1.3

Very smooth and fast!

Sent from an underground bunker in Texas
[Captivate Android Development] Yuna:
Oh crap - KJ1...

Can we move our stuff there? xD
[Captivate Android Development] laihafloyd:
Installed over pinnacle 1.3, great job!!

BLN Control said the kernel does not support BLN. but it does say that the latest BLN liblights exist.
[Captivate Android Development] mtcarey:
Ok, I'll look into getting that to work.
[Captivate Android Development] mtcarey:
Sorry... I got ahead of myself. I've ported Voodoo to J1 and started to update my post, but then decided to test it some more before releasing it.
[Captivate Android Development] LOSTLOGIC89:
I will also include your kj1 with voodoo lagfix in my new Fasty ^__^

Keep up the good work

+ thanks
[Captivate Android Development] mbc663:
Ive lost root after the conversion/flashing.
[Captivate Android Development] saobang3886:
Working greate on Pinnacle 1.1.1 to ^^!
[Captivate Android Development] Ikonomi:
KThanks for posting this! It's been a while since I've had ext4 on my phone.

Unfortunately, I'm having a problem after flashing the kernel on Pinnacle 1.3. After the file system conversion, the phone gets stuck on the Boog kernel boot animation indefinitely. The screen is actually interactable behind the animation, but it just keeps looping. This happens with and without lagfix enabled. I flashed back to Boog's KJ1 v3 and the phone is functioning normally again.

Maybe removing the custom animation will help. We'll see.

Edit: Moving the bootanimation.zip file did indeed fix the problem. Currently running voodoo lagfix!
[Captivate Android Development] mbc663:
nobody knows how to get root back? it flies on ext4 but i need root
[Captivate Android Development] Yuna:
Some people reporting that CWM packages are not saving changes to files.

Can anyone confirm?
[Captivate Android Development] msprag13:
Did you try chainsdd method
[Captivate Android Development] mbc663:
yes, the cwm says it flashes but the SU version doesnt change. makes me wonder about the guy a couple posts up saying cwm isnt sticking on files. although modems change when i flash them
[Captivate Android Development] popfan:
I am wondering if mtcarey's fix for TiBu would fix the Captivate ICS kernel problem for the same thing.
[Captivate Android Development] mtcarey:
Pretty sure it will.. just now flashing kk4 to make a new version! I'll also test the kk2 5.05 version on it.
[Captivate Android Development] mtcarey:
I added the ext4 option for /system as a byproduct of creating the partition repair function... I'm still not sure it makes much difference on /system but it's nice to have for it's "self-healing" properties, as opposed to RFS!
[Captivate Android Development] mtcarey:
I haven't had time to poke through all the ICS threads, but if someone can point me to a working kernel I can probably adapt it.
[Captivate Android Development] popfan:
https://code.google.com/p/ice-cream-sandwich-sgs/downloads/list

PS I was able to do a Full TiBu restore with data thanks to your new update.
[Captivate Android Development] mtcarey:
Great! Thanks for the link.
[Captivate Android Development] hokiemoto:
I tried Corn 5.05 (ext4 across the board, syscorps tweaks) on Illuminance 2.1.1 (KK2), and VooDoo Control Plus (paid) gave me the unsupported kernel message.

Any reason? did I miss something? thanks

Love all the options in CwM by the way!
[Captivate Android Development] -Thrive-:
Clear data for Voodoo Control Plus and restart the app. It will prompt you through setup again and probably will resolve this.
[Captivate Android Development] joonair:
I flashed 5.05 then converted everything (including system) to ext4

and I am only hitting 1.3k on quadrat :confused: I know it's not accurate, but I was hitting 2.3k with 4.0x.

now I converted system to rfs ( everything else ext4) and its stuck at AT&T logo.

what to do? :(
[Captivate Android Development] hokiemoto:
I noticed a big dip in quandrant score as well (I realize it's not a great indicator) 1500 with Tegrak OC to 1.2ghz
[Captivate Android Development] astroZ0MB1E:
I noticed that on my phone, init.d scripts were disabled by default. Is this normal? I enabled them, should I enable anything else in order to benefit even more from this awesome kernel.

As for the scaling governor, it is set to conservative, but it says default is default. I did not change this, it defaulted to conservative, whats the difference?
[Captivate Android Development] loudoun83:
BLN Support?

@mtcarey,

Are you planning BLN support for your kernel? Thanks for your awesome work!:)
[Captivate Android Development] mfdemicco:
There is a problem in 5.05. I converted my partitions to ext4, and now have a bazillion nested /etc folders/symlinks.
[Captivate Android Development] mtcarey:
Actually, that's the case with all the kernels. It doesn't hurt anything.
[Captivate Android Development] mtcarey:
If you installed a previous version, the default for init.d was "Off". I changed that to "On" in 5.05, but it will pick up your previous setting if you have one.

As for the "default is default" message, that just means that I set the default to be "default"... whatever Samsung compiled into the particular kernel as the default. I've been meaning to dynamically fetch whatever that is and say "default is xxxx", but haven't gotten around to it. Samsung seems to switch between conservative and ondemand every time they release a new version.
[Captivate Android Development] mtcarey:
I noticed a drop from KJ2 to KJ3. It's the actual kernel (Samsung), not my wrapper around it. These are, after all, not official releases from Sammy.
[Captivate Android Development] mtcarey:
Can't do BLN without the actual kernel source, which has not been released.
[Captivate Android Development] joonair:
I think it has something to do with the update :confused:

I am currently using v.4.03 and I am hitting 2.3k in quadrant.

I tried 5.05 earlier this morning and got 1.3k with ext4
[Captivate Android Development] Cdub5:
So freezing apps with tibu is still a no go for me. :(
[Captivate Android Development] hokiemoto:
I just tested Samurai 1.3 (KK2) and the scores went back up to 2300+

Both were on KK4 stock rom...just sayin. Linpack was 21+ regardless though - weird
[Captivate Android Development] prbassplayer:
Its the read/writes thats killing our quadrant scores. I notice them a ton slower on Corn than Samurai. Thats on Ext4. Im going to test ext2 and check back in.

---------- Post added at 12:30 AM ---------- Previous post was at 12:11 AM ----------

After switching to ext2 my quadrant went from 1600-1800 to 2500-2900. So Either its journaling or something else on how it read/writes.
[Captivate Android Development] mfdemicco:
On kernel 5.0.x, I saw no difference in Quadrant scores when I converted from rfs to ext4. My score is 1443, overclocked to 1.2GHz. Is the Voodoo lagfix better? Do these Quadrant scores mean anything?
[Captivate Android Development] prbassplayer:
Sorta? It isn't hard proof of anything. Specially when not all phones score the same. But in this case comparing with older corn where I used to get 2500-2900 on voodoo now I get 1500-1800. I noticed the difference was in the read/write part of the test. In real use that meas you should experience less lag on the loads and saves of data. But is it noticeable? Depends on the user. I was fine on ext4 I was checking why the difference on quadrant score.
[Captivate Android Development] mtcarey:
I'm checking my ext4 mount options to see if I changed anything in the past that might cause this. That's about the only place this could be... the ext4 format options are identical to Voodoo.
[Captivate Android Development] prbassplayer:
Na man not that your kernel is by any means noticeably slower. I was just messing with it to check why the lower quadrants. Im getting closer to what I used to get with older versions of your kernel with ext 2. Quick question apart from the negative of not having journaling (might loose data) is there any other negatives to ext 2?
[Captivate Android Development] mtcarey:
I removed the journal from /dbdata and got an 800 point increase in Quadrant! I must of had it off in the earlier version. I'm going to turn it off by default in the next version, and make journaling user-configurable. As for ext2 vs. ext4 (without journal), I'm really not sure. I'm not a filesystem expert, by any means. :D
[Captivate Android Development] -Thrive-:
User configurable EXT4 journaling. Love it!!
[Captivate Android Development] prbassplayer:
+1 Love to see that as well.
[Captivate Android Development] Kyuta Syuko:
From what I've gathered from other people and what I've read ext2 is pretty much ext4 w/o journaling, but don't quote me on that...
[Captivate Android Development] Jsmokey:
That and a few other minor changes like the scheduler handles ext2 a little different which has a small negative impact on performance, at least in the pc world never really messed with ext2 on a phone so it may be the exact opposite and boost performance.
[Captivate Android Development] RTBee:
I'm quoting you on that! I've told my wife, my kids and the neighbors :D:D
[Captivate Android Development] Kyuta Syuko:
lol That's the kind of smart arse remark I tend to make when someone says "Don't Quote Me"
[Captivate Android Development] RTBee:
Sorry, couldn't help it. It was just so, out there... :D
[Captivate Android Development] -Thrive-:
From what I have read on the forums, there seems to be a big disagreement about whether it is advisable to turn EXT4 journaling off. Just about everyone agrees that there is a performance improvement. Personally I went from RFS to EXT2 on everything but /system and my Quadrant scores nearly doubled. From there I went to EXT4 with journaling and the scores fell to near RFS levels, maybe 50-100 points higher. The group against turning off journaling is concerned about data integrity from corrupted filesystems. But most of the concern doesn't seem to come from first hand experience, just fear about what might happen and really, I'm not exactly keeping mission critical data on my phone. I'm thinking with Nandroid and TIBU backup, I can recover from corruption. I will not turn off journaling for /system and unless someone tells me that bootloaders may get corrupted, I figure I'll just do a Nandroid recovery or reflash the ROM or kernel as long as I can get into recovery. Like all flashing, the risk is born by the user. Any real life war stories out there that could change my mind?
[Captivate Android Development] Kyuta Syuko:
I'm with the data integrity group myself. Better safe then sorry I say, but like you said I don't really store any "mission critical" data on my phone so suffering from data corruption wouldn't be devastating...
[Captivate Android Development] mtcarey:
I've been thinking... the rap against libsqlite (resulting in modified versions like pikachu01's Thunderbolt) is that is calls fsync after every write operation to flush the write buffer. Seems to me that is an argument in favor of going without a journal on /dbdata. What's to corrupt? Of course, using "no fsync" versions changes that argument. Right now I only have a journal on /data, and the phone is friggin fast!
[Captivate Android Development] mtcarey:
New version 5.06 is posted

You can now remove the journal from any ext4 partition through new function in Recovery. If you are already on ext4 and change the setting, you need to run "partition repair" to make it stick. I'd like to use tune2fs to accomplish it much faster, but that is for the next version!
[Captivate Android Development] -Thrive-:
You're going to get a lot of people in trouble posting an update on Thanksgiving. :-)

Working great so far.
[Captivate Android Development] RTBee:
I'm in the doghouse flashing now. ;-)
[Captivate Android Development] mtcarey:
Good opportunity to shame your iPhone-fondling family members! :p
[Captivate Android Development] marcopolo1:
you need to run all the repair/rebuilt (system, data, dbdata and cache?)
[Captivate Android Development] mtcarey:
Run it on whatever EXT4 partition you change the journal setting on.
[Captivate Android Development] crandy2:
I'm out in the rain flashing. Even the dog won't let me in.
[Captivate Android Development] prbassplayer:
Im getting a error in partition /system. Says it fails doing that.... Then I get bootloops unless I flash a Voodoo rom (auto formats everything). Im going to start from scratch see if it fixes it. Any info would be appreciated