yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] rajendra82:
I noticed the instability as well. When I tried to run Root Explorer, a few times I'd get a dialog box saying that it could not get root permission, but then the next attempt would run. I sometimes saw no lag on wake up, and then other times, it took a long time to wake up, and when it did, it was as if having just booted up with media scanning and all that. I did not revert to stock before I tried the hack, so that may have contributed to what I observed, but for me the script hack seemed to simply spread the lag into chunks that caused parts of the system to get ahead of others. The problem was some of the parts that needed to catch up were being left behind, causing these errors. I think a lower level kernel based hack would overcome this issue.
[Captivate Android Development] _Opiate_:
So swapped back to this method as soon as I found out the kernel had been refreshed with no audio issues. For some strange reason though the phone feels a little faster using an ext-3 instead of an ext-4 even though the ext-4 scores higher and is supposed to be a better type if partition. Maybe its just in my head I don't know but it sure seems that way.
[Captivate Android Development] sl8125:
are u using samset with this fix. what firmware is compatible with this fix? i like samset's work.
[Captivate Android Development] NukaCola:
I'd expect any rom that you can run with the stock captivate kernel to work just fine with this. I run the stock I9K rom...
[Captivate Android Development] mostyle:
Something weird that's happening for me.. I did a stock reset with Odin then flash with the new Kernel. Everything appears to have flashed (kernel version is 2.6.29 @aboman testbox #22 and I have the 1-2 sec delay coming from sleep mode now) but when I try to run quadrant I hang on test 3/4 under I/o (database writes) and the test never completes. Can also verify that the a2sd fix is working because now any app that I install is not present if I boot with no external SD card and settings are reverted to older versions. I have an 8gig Kingston and I suspect from forum readings that this mat be the culprit but I wanted to hear other ideas. I'm going to grab a sandisk card so I'll edit with that result.

Thanks.
[Captivate Android Development] rob989_69:
Is there any way to confirm this fix?? Aside from quadrant scores anyway?
[Captivate Android Development] alphadog00:
I installed JM5 last night and discovered Busybox could not be found in the market - even with Airplane mode.

You could install Titanium backup and have it install Busybox.
[Captivate Android Development] NukaCola:
How do you mean confirm? Make sure you are running it? Just do something like:

$ mount | busybox grep mmc

in a terminal (adb shell). It should show /dev/block/mmcblk1p2 mounted on /data.

And your phone should 'feel' faster ;)
[Captivate Android Development] rob989_69:
Ok, tried this again. Little history first. I'm coming from stock kernel with app lag fix. I flashed AJerman's OC Kernel and am OC'd to 1.2Ghz.

After that I deleted the existing mnt folder on /sdcard (from the original attempt at this fix) and formatted to ext3. Then applied this fix. My benchmark scores are virtually identical to the ones after flashing AJerman's kernel and OCing in the first place.

Any thoughts?
[Captivate Android Development] sl8125:
After weeks of messing around, i ended up buying back a captivate. I ran JM2 and Samset 1.6 and try to update busybox and i could not find it. Where did it go? Also, airplane mode nowhere to be found. Maybe Busybox is being updated again? HUH?
[Captivate Android Development] rob989_69:
Thanks, did that and confirmed this is implemented now. Any thoughts on my previous post??
[Captivate Android Development] NukaCola:
Performance of this' and the userspace fix should be virtually identical on the same filesystems..

AJerman is working on cleaning up the OC code, when he is happy I'll put up a kernel with that applied as well.
[Captivate Android Development] AJerman:
Waiting for it to compile, hopefully everything is good now.

Edit: No... no, that was not so good, haha. That was a very broken kernel. Trying again. :p
[Captivate Android Development] rajendra82:
I ran the script hack for a while, and Quadrant database writes test 3 of 4 takes a long time once the fix is applied. I thought it had hung as well, but be patient and let it finish. It is one of the behaviors that shows that the fix is working. The long wait is usually followed by a high Quadrant score.
[Captivate Android Development] kennethpenn:
Looking forward to this plus the 1.2 GHz overclock. Now that voice is fixed, I'll chip in my promised money when you all complete the latest version.

Good job NukaCola and AJerman!
[Captivate Android Development] Saftwear:
This is the best quadrant scores so far. Im loving this workaround the most.

Having tried the others in this forum.

Flashed jm2 i9000 added voice search and droid x keyboard and this thing is completely rockin

Thanks folks for your work.
[Captivate Android Development] Zilch25:
I wanted to bump this thread:

Apparently the samset mod recently implemented a kernel hack to enable EXT3/4 partitions on the external SD but they suffered from the same wakeup lag we get... Apparently mimocan was able to patch that up, perhaps he'd be willing to give some hints to us regarding what needs to be done differently?
[Captivate Android Development] NukaCola:
Oh, I hope so. I didn't realize anybody had figured that out yet.
[Captivate Android Development] Zilch25:
He JUST updated his OP... I wish he'd given a hint as to what Mimo did differently. It seems like this is something we should be able to implement hopefully without too much trouble.

So no one has to dig for it:

http://xdaforums.com/showthread.php?t=724576
[Captivate Android Development] sl8125:
Bump,

I hate to see this fix go away. All the hype on I/O fix, no go. I had better real world results then some benchmark result. so far, i could live with a little lag on wake up. however, if you guys can perfected, this is best speed fix til this date. hope mimocan give us a hand on the fix. he doesn't have a captivate, so it might be little hard for him to help us out. but i just wish he takes a look at the kernel and give us a idea whats wrong.
[Captivate Android Development] Zilch25:
Well the thing that gives me hope is that at least the Samset ROM experienced the same wakeup lag issue, and that was built on the i9000 kernel which already had the original mimocan fix. He was able to figure out what they did wrong to create the same issue we're having...

So at least in my mind there's a possibility the issue and the fix might be the same

Has anyone PM'd him to ask for some clarification of what he did for Samset?
[Captivate Android Development] NukaCola:
I'm 99.999% certain the fix is the same. I've pm'd him but received no answer :(
[Captivate Android Development] Zilch25:
Hmmm maybe the Samset ROM author (setenza01) might have some idea what Mimo did?

So impatient for this haha
[Captivate Android Development] Zilch25:
This is pretty interesting... looks like one of the I9000 guys created a kernel with YAFFS2 support.

http://xdaforums.com/showthread.php?t=750663

Anybody think this might be worth a shot? If so, think it might be a fast, safe alternative for our devices?
[Captivate Android Development] rajendra82:
I think this is something that sounds like the best option until Samsung themselves comes up with a way to improve RFS. If someone can isolate and fix the wake up lag, and can patch in the support for a proper file system where we can move data out of RFS, then we should have a good kernel base to start from. I'd love to get a speed fix free from having severe size limitations, free from getting corrupt over time, and does not prematurely wear out our SD cards or NAND ROM.
[Captivate Android Development] NukaCola:
I just updated the OP adding an OC kernel there as well.

It scales from 100 mhz to 800 mhz as stock, then skips 1Ghz and goes directly to 1.2, following the theory that if you need 1 Ghz, 1.2 is probably better. ;)
[Captivate Android Development] mostyle:
Results..

I've been stress testing it the last hour or so and am sad to to say that I started experiencing random lock ups. At first (say 30 mins) it appeared okay. I was able to run a standard quadrant and got a 1764 which is in the standard range for me. I then OC'd and reran the test and it completed with a score of 1965 which validated the OC was functioning. Shortly after that tho (say 15 mins) I tried to resume the device from standby and it would not respond. I pulled the battery and rebooted and it rebooted perfectly. As soon as it went into standby for any lengthy period same thing occurred so I began to think it might be related to the resume. Pulled the battery again and rebooted and loaded SetCPU to look at the settings and they were @ 1200/1200. As I was adjusting the max and min settings it froze again this time while actually in use.

I will do more tests later today and I know these results aren't really scientifically tested through much trial and error but I will do more and update you.

In no way am I complaining just pointing out preliminary observations.

Thanks for all of your work!
[Captivate Android Development] NukaCola:
Not taken as a complaing at all! Thanks for letting me know, I'll look into it. I ran a few tests on it without issue before posting, but that is obviously no gurantee. The not waking from standby issue is something I've only seen with the ondemand governor, but this uses conservative by default.

Did anybody else test this and have any issues?
[Captivate Android Development] _Opiate_:
I installed just the regular version of the OC kernel last night as I was testing the Userinit.sh mounted ext-3 hack. I had the same issues with locking up. With mine it was often when I locked the phone it would not wake again no matter what I did until I pulled the battery and restarted the phone.
[Captivate Android Development] NukaCola:
Ok, so there is definitely some issue. I'm guessing the problem is with the stepping since it seems to not come back from sleep. When the phone resumes from sleep it comes on at 800 mhz, then steps as necessary.
[Captivate Android Development] XorZone:
For me it happens only with setcpu configured ondemand.
[Captivate Android Development] NukaCola:
Ah.. Yeah, don't use the ondemand governor. I should disable it in the kernel.
[Captivate Android Development] sl8125:
so do we need the updated kernel or we good to go? I am ready to download. i want to see the lag that eveyone is talking about.
[Captivate Android Development] NukaCola:
This kernel should be good to go. I've run it since last night.
[Captivate Android Development] sl8125:
How about the lock issue? I thought u need to mod the kernel.

Edit: I got it. No ondemand governor. Thanks for all your work. Going to flash tonight.
[Captivate Android Development] E_man5112:
Ok, I read the first 10ish pages, and didn't see an answer. Do you need a swappable SD card to do this? Or is the internal SD partition ok?
[Captivate Android Development] mostyle:
Swappable, or more commonly referred to in these threads as an external. The custom kernels mount to partition 2 of the external card.

This also assumes that you have partitioned the external card appropriately.
[Captivate Android Development] golemaw:
Were you able to figure out the problem with the wake up delay?
[Captivate Android Development] NukaCola:
No, I hope to get some time to work on this stuff this weekend.
[Captivate Android Development] rob989_69:
Flashed this after flashing JH2, boots to Galaxy S screen, sits there for a while, then screen goes black, nothing. Did battery pull and tried again, same. HELP!!!
[Captivate Android Development] mostyle:
NukaCola,

Just to keep you updated in my tests.. I Couldn't keep a stable install with the OC Rom although I did not try conservative. I was using 'performance 800/1200' and then tried 'performance 1200/1200' to see if it was indeed a stepping issue. Still had lockups.

Currently I'm running JH2 with your non OC'd rom and all seems fine. Not one lock up in 16 hours. I noticed that the lock ups primarily seem to happen durring the initial boot up (scanning SD cards, etc or when resuming from standby.)

Last thing I want to check is if the GPS works with the real JH2 kernel..

Would the using of the older patched kernel affect GPS or does the kernel load drivers to control GPS so the actual kernel revision is irrelevant? Short form.. Are drivers integrated into the kernel or are they loaded by the kernel?

Thanks!
[Captivate Android Development] E_man5112:
Thanks

So this depends pretty heavily on the speed of the external card? Or is there some other bottleneck in there? Don't want to buy a cheap card and be disappointed, or buy an expensive card and have it be no better than the cheap one.
[Captivate Android Development] NukaCola:
I use an old crappy card with pretty good results. It seems that anything except kingston is the consensus on the way to go at this point.

@mostyle

Thank you for the data. I had a "no wake from sleep" today as well.
[Captivate Android Development] Unhelpful:
progress!

I have what appears to be a race-free method to run a user mount/init script, although it does require a custom initrd and therefore a custom kernel. I have also done some initial tests with nilfs2 on my external SD card, as well as ext4, xfs, and jfs. Nilfs2 came out pretty clearly on top, next is to try moving my /data to it. If that goes well I'll post my kernel and a tarball of the utils you can use to set up your own system. :)
[Captivate Android Development] mostyle:
Can anyone comment on this? I'm not very familiar with Linux architecture.

When I first installed JH2 I was getting locks indoors with GPS. I flashed kernel only of the ext4 enabled kernel and now I'm not getting GPS locks indoors and having difficulty outdoors (the original stock rom issues) and I'm curious of the time I was getting indoor locks was a fluke or if it could have actually been fixed in JH2.

I'm thinking the locks I got initially with JH2 was the infamous Samsung 'we like to makes you think you have a good thing only to disappoint you later' technique.

If we can isolate that it is something new in JH2 it may be possible to pull the drivers from JH2 into the original to keep tethered sharing and what not.

Thanks again.
[Captivate Android Development] NukaCola:
I was planning on getting an init.d enabled kernel together this weekend to give peeps more flexibility in what they want to do/test.

I'm very interested in Nilfs2 data, if that works well it could very well be the way to go! Good work :)
[Captivate Android Development] Unhelpful:
Nilfs2 is about 33% faster than ext4 in a simple copy/sync/delete/sync benchmark, the exact numbers are in the yaffs thread. Quadrant scores around 1300 vs around 900 stock, and the phone seems generally more responsive. From boot to first display of the lock screen seems a bit slower, but getting from there to the phone being usable seems faster... wish I had a stopwatch.

The method I used for user init was to move the dbata mount up to be right after /data mounts, then start /user_init.sh as a service, and move the rest of the filesystem setup into the on boot section. The boot action is stalled by starting it "write sync_fifo sync", the target being a fifo that user_init.sh reads from after the real user init, which it calls, has returned. Ugly but works reliably. Android init has an exec statement, but it's been implemented for some time.
[Captivate Android Development] atinm:
The command is "busybox cp -a /data/* ." (without the quotes). The commands means "copy everything under /data to 'here' " - the dot means 'here'.
[Captivate Android Development] Anthonok:
now when i trype mount -t ext3 /dev/block/mmcblk1p2 /sdcard/mnt i get

mount: device or resource busy
[Captivate Android Development] AJerman:
I'm not sure why Quadrant is taking so long to complete for you guys. Mine took 56 seconds to complete the entire test with a score of 1769.
[Captivate Android Development] Anthonok:
I'm Just screwing this all up haha. now after the /data/* . it starts listing all the info on the phone and says "cannot preserve ownership of" before the file names
[Captivate Android Development] Postal76:
Good catch -- I was actually running the ext4_only kernel (although I didn't mean to).

I restarted the whole process, first by reformatting my sd card and flashing back to the stock ROM. I tried flashing the speedup2 kernel first, but my phone wouldn't even boot up all the way (I guess that makes sense if it's looking on my sd card for files that aren't there yet).

I then flashed the ext4_only kernel first, copied the data files to my sd card, then flashed the speedup2 kernel. Now I can boot into Android, but I can't change any settings (can't setup my google account, can't enable wifi, etc).

What am I doing wrong?
[Captivate Android Development] McCarron:
Great work. I'm getting around 1700 or so on Quadrant after this mod.

But is anyone else having issues with downloading apps from the Marketplace after this mod? It tells me there is no space to download apps anymore. It works great with already installed apps, but new apps come down. mimocan had a fix for this issue with his mod, but it doesn't apply to this one directly.
[Captivate Android Development] Anthonok:
I give up. ill try it again later. In the mean time should i reflash the stock kernal or will it be fine?
[Captivate Android Development] SlimJ87D:
I have a theory. I noticed everyone that has the problem over at Mimocan's forum has a KINGSTON CARD!

I have the problem and I have a Kingston card. I don't think this is a coincidence. I think it just might be hard for Quadrant to work with Kingston cards.
[Captivate Android Development] McCarron:
Ahh it's all my fault, I didn't see this note:

Time to redo the partitions!
[Captivate Android Development] AJerman:
Hmm... maybe. I'm using a Lexar card.
[Captivate Android Development] NukaCola:
I'm not sure that the speedup mod actually causes this problem, the fix they modaco guys were using is to move /system/media to /disk. To try a version of that fix you can do:

# busybox mv /system/media /data/media.sys
# busybox ln -s /data/media.sys /system/media

That gives you more space on the /system partition than you had before.
[Captivate Android Development] Fortune090:
One thing I did notice with this with my phone though, is that it takes about 3 seconds once I press the side button to come to the lock screen from it being off... Any idea how to fix that?
[Captivate Android Development] vietphunguyen:
Will it work if i partition using GPart using the Captivate as a cardreader?
[Captivate Android Development] NukaCola:
I noticed that too a little while ago. No idea what causes that, and I don't remember it from when I was doing the "hot fixes" or from last night.

Edit:

Seems to be an issue only every 3-4 presses.
[Captivate Android Development] Fortune090:
I didn't notice it originally either. Just after I had everything set again after I applied the fix.

For me, it's a problem whenever I try to unlock it after it'd been idling. If I'm continuing to press it, it works fine, but the initial one still hangs for a bit.
[Captivate Android Development] AJerman:
I don't know a definitive answer on this, but I'd suggest not doing this.

Is there even any way to see the external sd card as a single external sd card through the Captivate? It just mounts the card to a folder inside it's internal storage. When you mount you see that internal + external mounted to /sdcard/sd.

Don't think you can do it.
[Captivate Android Development] magicdanw:
Very interesting! I'd like to try this out, but I'm a bit confused on one point. You post both a kernel that supports ext4 and one that also mounts the data folder from the external SD card. Do the instructions want one to first flash the regular kernel with ext4, then run the commands to copy data to the SD card, and then flash the speed fix one? Or is it only necessary to flash the speed fix one, before copying the data?
[Captivate Android Development] Anthonok:
Mine does this now as well and I havent even been able to get the fix to work. i somehow manage to screw something up along the way everytime. So now i have a still slowish phone AND it takes a few seconds to get to the lock screen. This ended up as a Lose Lose situation for me

Edit:I reflashed the stock kernal and it no longer does this
[Captivate Android Development] McCarron:
I fixed it by resizing the ext4 partition to 2GB exactly in GParted, as I missed that line in the instructions, and now it works just fine. If I run out of space, then I'll do that fix as well.

I also just donated to your beer fund NukaCola, thanks for the great work. I'd say spend it on Nuka Cola if it actually existed.
[Captivate Android Development] madjsp:
No. I tried doing this in G Parted and my sd card was corrupt. I had to re-format it.
[Captivate Android Development] NukaCola:
Yeah... It also seems to not be an issue if the phone is plugged in.
[Captivate Android Development] VtHondaGuy08:
If only I wasn't such a NOOB I would do this :(
[Captivate Android Development] AJerman:
No, I apologize as I think the confusion stems from my request for a kernel that is ONLY ext4 enabled, and doesn't mount any extra partitions. The stock kernel doesn't support ext4, there's another method to mount partitions, but I needed a kernel that supported ext4. If you want to follow the directions in this post, all you need is the speed fix ext4 (or ext3 if you want to use that) kernel, not the stock kernel with ext4 enabled.
[Captivate Android Development] _Opiate_:
Something weird just happened to me. After applying the fix when I call people i sound VERY distorted. Its like it messed up the mic volume some how. But when I restored it went away. I'm going apply it again. I re-downloaded the kernel as I believe it was probably something with the kernel that caused this.

Its the ext4 kernel by the way. Probably just a freak thing but maybe you guys should check your phones. The kernel might need to be updated as there might be a bug somewhere in it causing this. I am about to find out for sure though because I'm re-applying the fix.
[Captivate Android Development] AJerman:
Actually, I had noticed this too, but I wasn't sure if it was something caused by this fix or perhaps the modified version of the fix that I'm doing, or even any of the other many things I did yesterday.

I'm not sure what might cause this, kinda weird. I don't think it did it with ext3, just ext4, so maybe there's a delayed start for some reason on ext4. Almost like a hard drive spin down, except, obviously without a hard drive. I don't know enough about the ext4 file system itself, but I'm going to see what I can find out.
[Captivate Android Development] vietphunguyen:
If i use ext4 and use captivate speedup2 kernel. do I have to enter in the command lines provided? or does it do it for me?
[Captivate Android Development] SlimJ87D:
I am having this same exact problem. Is there anyway it can be fixed Nuke? I thought it was live wallpapers but it is not.

For me the problem is pretty consistent. I think Ext4 is quite unstable. We might have to do Ext3 until a solution is found. Does anyone have this problem with Ext3?

It feels like the price we have to pay is to have a 3 second lag on our phone when we turn it on :(.
[Captivate Android Development] NukaCola:
I'm not sure what is causing it, has anybody checked if the lag is happening with ext3 as well?

It is interesting that it doesn't happen when the power is plugged in, or if you do it several times in succession...