yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] kennethpenn:
Any chance of bringing this speed fix by mimocan to the Captivate?

Supposedly some international version Galaxy S'ers are sitting pretty with 1700's Quadrant scores because of this fix among other firmware flashes, etc.

Can we replicate this for the Captivate?

Here's a little inspiration:
[Captivate Android Development] designgears:
"I have made a custom kernel to mount an ext3 partition on the sdcard at the boot time."

Can't make a custom kernel without source... and there is no source out yet... or even a stock firmware.
[Captivate Android Development] autoxer:
Isn't the stock firmware in this? http://xdaforums.com/showthread.php?t=731989

I've compiled kernels for linux before on my own PCs, and from what I can tell, he's just added ext3/ext4 support and customized the init.rc to mount the partition at boot time. I should dig around and see what I can find.
[Captivate Android Development] sl8125:
MANG~

I will worship the ground you walk if you can get this to work on Captivate.

I bricked my phone many times trying to make this work. Apparently when mimocan's kernel installed, external sd card can not be detectect and g sense will be off 90 degrees. however, all buttons do what they are suppose to do.

Anyways, please please help with this MOD. Alot of us Captivate owners are looking for this fix.
[Captivate Android Development] rob989_69:
You will be my new hero if you get this working on the captivate.
[Captivate Android Development] _Opiate_:
You ain't kidding either! That fix is the sh@t! I've finally gotten my Captivate to run decently with LauncherPro but it's that nothing compared to what it could do with this fix. It's a shame really, we have KILLER hardware and the software implementation has seriously crippled it.
[Captivate Android Development] kennethpenn:
designgears already posted the stock firmware... no? Twenty bucks to anyone who can get my captivate up to these benchmark scores.

Koush posted up the stock kernel too.
[Captivate Android Development] Baldilocks:
I'd donate $20 as well.
[Captivate Android Development] sportedwood:
im in for 20$ for a fix, even using SetCPU to 1000mhz whenever the screen is on I still get little stutters that feel like memory read issues, buddy was just over with his froyo nexus 1 and it was amazingly fast.

20$ is cheaper than the 35$ return see :rolleyes:
[Captivate Android Development] sl8125:
I am in. I love to see happen. $$s for your time and bro.
[Captivate Android Development] sl8125:
Holy CHIT!

Ck this vid out. Its running the Mimocan Fix.

I need a FIX now. Come on man gotta do this.

http://www.youtube.com/watch?v=_b363eq0dXY&feature=related

http://www.youtube.com/watch?v=AjJdT-tlHOY
[Captivate Android Development] rob989_69:
Well..... I just drooled all over my keyboard..... Anyone out there want to take a stab??? PLEASE!!!!
[Captivate Android Development] Anthonok:
Hopefully that won't take much get running for us
[Captivate Android Development] thedon809:
I'm not a baller like some of you, but I would give 10 dollars to whoever makes this work with the captivate and maybe makes a vid on how to do it.
[Captivate Android Development] _Opiate_:
Don't worry it will come around.
[Captivate Android Development] Unhelpful:
it appears ext2/3 are already supported...

On my stock Captivate kernel /proc/filesystems shows ext2 and ext3 are already supported. Only boot scripts should need to be changed to use them. Also interesting, cramfs and romfs are supported but unused.
[Captivate Android Development] vietphunguyen:
I tried this fix with ext3 and ext4, it didn't work just a black screen. Check this reply i posted to see my steps :(
[Captivate Android Development] Kagoshema:
in that case, anyone care to try the i9000 bootscripts with our kernel?
[Captivate Android Development] sl8125:
how is this done? new to this. i'll give it a try.
[Captivate Android Development] _Opiate_:
Good luck with that. I hope it works for you. We really need this fix until Samsung can fix the "bottle neck" but that probably wont happen until froyo is ready.
[Captivate Android Development] NukaCola:
Is your card in the slot? Does it have two partitions?

The reason we are doing two partitions is because the android vold (daemon that automounts) is nothing like suns real vold and will only look at the first parition on a disk. So we make partition 1 a FAT partition that the phone (and your computer) can mount and use. Partition 2 we use for your speedup hack.
[Captivate Android Development] SlimJ87D:
Nuke, I just donated you $10 because I'm confident this will work but I can't get it to work.

I'm using Windows 7. I kind of need a step by step detailed guide for this. I have my donation confirmation number if you need proof.
[Captivate Android Development] Tacun:
So I thought I would post my results so far with the ext4 fix:

I want to point out that you have to flash the ext4 kernel before you can successfully execute this string:

mount -t ext4 /dev/block/mmcblk1p2 /sdcard/mnt

The only issue I have at the moment is that I'm not sure what format the 1st partition should be to be recognized by the phone.

But I really wanted to thank you and mimocan for this. This is all I've cared about as far as captivate development goes for the last week. This phone really shines with the fix. Plus when it comes to quadrant scores, the fact that this phone with a samsung 2.1 rom and this fix getting a 1600 compared to an Evo on 2.2 and cm6 getting a 1500 is impressive.

Edit: I did this on Win7 x64. I can put together a guide for those running Win7 x64 for the fix pretty quickly if you guys want.

I was getting the same error. It worked after I flashed the ext4 kernel first
[Captivate Android Development] NukaCola:
Nono, no proof needed. I trust you, and like I said its not necessary. But it is appreciated! Thanks!

I'll try to put together a better guide, I just wanted to throw something together with this and get it out there. Im sure things will seem easier in a day or so when wrinkles are ironed out.
[Captivate Android Development] SlimJ87D:
Thanks Nuke, and thank you for your hard work. i really think you should make your own topic here so you can edit the first post when needed. Get it stickied too.
[Captivate Android Development] Anthonok:
Failed again. Same thing happend. I suck at this stuff. ill wait for the better guide. I come from using iphones for the past few years and I'm used to just clicking a button and having a program do the jailbreak for me. never had to do anything involving code and stuff. oh well. But i greatly appreciate the time and effort put into this.
[Captivate Android Development] NukaCola:
Oh yeah, DUH. Sorry about that.

It should be fat32 (vfat in linux terms)

You are welcome, the phone really does shine with this fix. When we get JIT it should fly though >:)

That would be great, I'm sure a lot of guys would really appreciate that (including me).
[Captivate Android Development] MSigler:
Got mine up and running, didn't seem to copy any of my programs over from the internal SD card, so I had to reinstall stuff manually, but I don't honestly care, the phone is usable now, instead of a stuttering mess.

Expect a donation when my paycheck clears :o
[Captivate Android Development] SlimJ87D:
OH GOD! Please help us out, I'm so desperate to get my phone flying like crazy!
[Captivate Android Development] Maroon Mushroom:
That would be awesome.
[Captivate Android Development] MSigler:
Before:

After:

Edit - And this is on the slow ass class 2 card that came with my Nexus One, when I put a class 6 or better in it next week, it should fly.
[Captivate Android Development] ranova:
what drivers are you guys using. When I plug my phone in via download mode, I get a pop-up saying "USB device not recognized" (Odin3 is already open)
[Captivate Android Development] Unhelpful:
kernel configs?

Is there any chance you could share the .config for these kernels? It would be nice to have a starting point for custom kernel builds, and I'd also like to try reformatting the /data partition of the internal SD as ext3/4 to see how much of this bottleneck comes from RFS alone.
[Captivate Android Development] SlimJ87D:
Hey thanks for this guide it is going to help me out so much. But from Mimocan's forum I heard that you can't do more than 2 GB or else you will get problems down the line.

Once again, thank you for writing this up, I really need the help.
[Captivate Android Development] NukaCola:
There is nothing special about these .configs, the one thing is you need to do since Samsung didn't include any initramfs stuff with the sources is to go in and enable initramfs support in the kernel, then add a path to your initramfs directory in the field that appears (in menuconfig). Basically extract the initramfs from your running kernel there (and make your edits). Use Samsungs build_kernel script (put hte arm tool chain where the script wants it). I actually use arm-2010q1, while Samsung used arm-2009q3 to build our running kernel. Comment out the line that makes defconfig in the build script, then run it. You'll get a working zImage. The kernel you compile load the stock modules without issue.
[Captivate Android Development] ranova:
after entering:

busybox cp -a /data/*

Does this process take a long time without any verbose? Right now it is just sitting there with a blinking cursor. I remember having around 200mb in /data/data alone
[Captivate Android Development] Tacun:
Yes it will take awhile to finish.
[Captivate Android Development] KCutrer1:
Hey guys, I'm sorry if this question has already been answered, but I was just wondering does this fix work with the JM2 i9000 ROM that Reaver117 posted? I flashed that a while ago with Samset 1.6 and I wanted to see if this fix would work with that as well, or if I'd have to go back to stock in order to use the fix.
[Captivate Android Development] NukaCola:
Also make sure you actually typed: busybox cp -a /data/* . <-- note the dot.
[Captivate Android Development] NukaCola:
If that rom works with the stock kernel I see no reason it wouldn't work with either of these. So go ahead and try it ;)
[Captivate Android Development] ranova:
crap, how do i cancel whatever thats going on?
[Captivate Android Development] NukaCola:
Nothing is going on, dont worry.

CTRL + c should get you out of it.
[Captivate Android Development] Tacun:
So nuke can you look over that guide?
[Captivate Android Development] KCutrer1:
Yeah I flashed the PDA and CSC files and then went back and flashed the Captivate kernel, so yeah since it was the stock kernel I'll assume that it'll work. I'll check it out and post the results in case anybody is in a similar situation.
[Captivate Android Development] siehead:
thank you so much for all your hard work.

will there ever be a speed fix for those of us that are complete noobs? I really don't mean to sound ungrateful or overzealous but I just know so little about this process that I will feel more comfortable implementing it when it becomes as simple as rooting.

Is this a realistic expectation? Generally how long does it typically take before speed fixes and custom roms can be flashed in a process as easy as rooting? Or will those of us with little to no skill just have to wait for an official release?

Thanks in advance for not being frustrated by my question, I'm sure I'm not the only one out there who is chomping at the bit for a more simple implementation.
[Captivate Android Development] NukaCola:
I'm way to tired to get a sane guide done now, I've been on my way to bed for hours already ;)

I suspect you'll have some guides that are better than what my improved one would be along from the windows guys soon.
[Captivate Android Development] Tacun:
Interesting... For some reason it worked for me without the dot.
[Captivate Android Development] NukaCola:
I'm sure there will be a much better way soon, I'd like it to be as simple as the rooting was, or perhaps something via clockwork can be done. I don't know enough about those things to put a nice clean package together yet, so I released the dirty way first.
[Captivate Android Development] SlimJ87D:
Do you have any experience using Paragon to perform partitions?

I tried to partition it but now when I plug my phone in USB I don't see my SD card anymore. The other half I partitioned won't show up. But my phone finds it fine.

I think the EXT4 became Partition 1 some how.
[Captivate Android Development] ranova:
is there anyway to check if it copied over correctly? can you just go to /sdcard/mnt, enter "ls" and will it show files?
[Captivate Android Development] siehead:
Well yours is certainly a welcome addition to the community. Thanks for the hard work and the kind response.
[Captivate Android Development] SlimJ87D:
Do we just have to simply name it "Partition 1" and it's considered partition 1?
[Captivate Android Development] Tacun:
When you partition a disk the partitions are referenced from left to right. No matter the names of the partitions they are know to the OS (in this case) as 1p2 or 1p1. The first number being the disk number and the second being the partition number on that disk.
[Captivate Android Development] SlimJ87D:
So if I make the right one EXT4, then that will make Partition 2 my EXT4?
[Captivate Android Development] Tacun:
yes as long as there is actually a partition before it.
[Captivate Android Development] SlimJ87D:
Thanks! Well here goes nothing, I'm going to start following your guide.
[Captivate Android Development] Tacun:
When I put the SD card back in my computer I can see all the files copied over, but I haven't checked with a file explorer on the phone.
[Captivate Android Development] SlimJ87D:
How long should Odin be stuck in the "File Analysis.." part?
[Captivate Android Development] Tacun:
It should all happen very fast. Are you sure you were in download mode? You will see a yellow triangle with a digging android in it and it will say DO NOT POWER OFF TARGET
[Captivate Android Development] SlimJ87D:
Yes, I am here. But for what ever reason, Odin doesn't do crap. It just says

"File Analysis" and does nothing. My phone won't reboot either. Do i click Re-Partition?
[Captivate Android Development] Tacun:
No do not check re partition. You have to make sure that odin is open before you plug your phone in to your pc. So if you are in download mode disconnect it and re open odin then plug it in.
[Captivate Android Development] _Opiate_:
for some reason I cannot click download on 2shared. any body host?
[Captivate Android Development] SlimJ87D:
This is very Strange... But Odin just freezes and doesn't do anything at all. Is there a way for me to exit out of download mode?

look for some tiny text that says "click here"
[Captivate Android Development] Tacun:
You can only really pull the battery as far as I know. Doing that will software brick it but you can fix that by using this: http://xdaforums.com/showthread.php?t=731989
[Captivate Android Development] SlimJ87D:
omg... are you serious... am I really taht screwed...

What do you have checked in Odin exactly? My phone gets located to COM 0.

When I click Start, it just says file analysis. This is terrible news to me :(
[Captivate Android Development] Tacun:
Nothing in odin is changed from when it is opened so re partition is not checked, auto reboot is checked, and F. Reset time is checked.
[Captivate Android Development] Tacun:
So after some tinkering around with the memory and other optimization I was able to get this:

This was with the ext4 fix and this idea posted earlier in this thread.
[Captivate Android Development] SlimJ87D:
I am now stuck on the zImage part...

I don't understand why my ODIN keeps F-ing up...
[Captivate Android Development] Fortune090:
Ok, everything has been working, but when I put in mkdir /sdcard/mnt, I get mkdir failed for /sdcard/mnt, File exists...?

I've partitioned, flashed ext4 kernel, but I'm stuck here...
[Captivate Android Development] Fortune090:
Think you might be stuck where I was. If it stays at zImage for longer than 10 seconds, unplug, remove battery, and reboot Odin and load the CSC file again. Put the batter back in, plug in the phone, and you should get the phone+!+computer screen. Hold both volume buttons+power button, and wait for the screen to go black and pop up the phone+!+computer screen again, then once it goes black again, let go of just the power button, and it should go into download mode. NOW try pressing start. You should actually see a progress bar now.

It didn't work for me until I did this...
[Captivate Android Development] Tacun:
Is this a second attempt? I would mount your sd card and delete the mnt folder the unmount and try again.
[Captivate Android Development] Fortune090:
Wait, I have to unmount the sdcard from the phone before I start this?

EDIT: Ok, that didn't do anything different...

And no, this is my first attempt...
[Captivate Android Development] Tacun:
No I meant from your computer. Like when you pull down the notification bar and click usb storage.

The same thing happened to me so I opened the sd card on my pc and deleted the mnt folder on the sd card.
[Captivate Android Development] SlimJ87D:
Phone is now Bricked...
[Captivate Android Development] Tacun:
How is it bricked? They are un-brickable: http://xdaforums.com/showthread.php?t=731989
[Captivate Android Development] Fortune090:
Ok, now I got past that, and now it says mount: Operation not permitted.
[Captivate Android Development] Tacun:
You have super user access right? You will see this: # on the left of the command prompt instead of this: $
[Captivate Android Development] SlimJ87D:
Very sorry, I meant software bricked.

My friend was typing for me while I was holding Volume buttons and power buttons.

Here is a really important note.

YOU MUST RELEASE THE POWER BUTTON AND KEEP THE VOLUME BUTTONS HELD RIGHT WHEN THE SCREEN TURNS BLACK!

This will get it back to download mode. Then you can redo the kernel thing all over again.

I finally got it to work. I don't know why it was so hard but I think the driver can cause problems for different PC set ups. I will follow through the rest of your tutorial. Thank you Tacun.
[Captivate Android Development] Fortune090:
I do have super user access, but I'm seeing the $, not the #....

EDIT: Got it! Had to actually open Superuser Permissions on my phone until it recognized it was being used.
[Captivate Android Development] Tacun:
Yeah sorry I didn't make that clear its kind of a general guide.
[Captivate Android Development] SlimJ87D:
I have a similar situation. It is just telling me "PERMISSION DENIED"

I'm getting the money sign too. What did you do in Superuser exactly?
[Captivate Android Development] Tacun:
When you type "su" it will open a prompt on your phone and you have to click allow for it to give you access.
[Captivate Android Development] _Opiate_:
Hells YEAH!!! Using the ext4 kernel I managed a quadrant of 1812 with a poor little class 2, 4gig. I'm also running JM2 with samset 1.6 but damn I'm happy!
[Captivate Android Development] SlimJ87D:
Thanks Tacun for your patients... I'm very sorry for being such a noobie.

Well after I type su, it then shows a #.

Then i type in mkdir /sdcard/mnt and it says:

mkdir failed for /sdcard/mnt, read-only file system

what does this mean?

EDIT: Had to unmount... sorry...
[Captivate Android Development] Tacun:
I thought you might figure it out :)
[Captivate Android Development] Fortune090:
AMAZING!! After a few "I think I fried my internal storage" and reboots to find out otherwise, I finally got it to work!

Just scored a 1735 with Quadrant with all the startup apps still running.

Thank you Nuka SO MUCH, and Tacun for helping with my troubles. :)
[Captivate Android Development] SlimJ87D:
Hmmm... how do you know if it works or not...

my quadrant score was only 900... I don't think I did it.

Is there anyway to know if you did it all correctly?
[Captivate Android Development] Tacun:
I'm exited to see other people getting this to work, the difference is dramatic!

You will notice the difference if it works. I would go through it step by step with you but I'm still working on other stuff on my phone. You'll get there though so keep trying. I'm checking the thread every 5-10 mins so I'll try to help if I can.
[Captivate Android Development] SlimJ87D:
So do I have to reinstall the kernel? then start all over again?
[Captivate Android Development] Tacun:
It was easiest to do when I used the odin3 one-click download and flashed everything back to stock. But if you have already flashed the kernel once you shouldn't have to flash it again until the last step(if you even have to then).

Which steps do you think you are having problems with?
[Captivate Android Development] SlimJ87D:
This is my cmd.
[Captivate Android Development] Tacun:
At the end you are typing "unmount" you are supposed to type "umount" Plus when you type "busybox cp -a /data/* ." you have to wait until the # shows up again before you continue. It will take a little while. Other than that you should have it soon.
[Captivate Android Development] SlimJ87D:
Holy Crap!

I'm such an idiot... So how do I restart the whole CD thing over again? It's not letting me start from step one. Where do I start again?
[Captivate Android Development] Tacun:
open the cmd and cd to your androidsdk\tools folder

then type adb shell

then type su

then pick up at cd /
[Captivate Android Development] SlimJ87D:
I think I did it right this time?

EDIT:

nope... Still getting 900... dang...
[Captivate Android Development] Tacun:
Looks like it. Just flash the kernel again and it should be working.

EDIT: Did you flash the kernel again?
[Captivate Android Development] SlimJ87D:
Okay, I just reflashed the Kernel again.

I am going to go through the CMD commands again and see what happens.
[Captivate Android Development] Tacun:
And after your done flash the kernel again and just boot the phone and check
[Captivate Android Development] SlimJ87D:
Now Quadrant gets stuck at I/O Database writes.

I'm just not having good luck with all this.

EDIT: Too tired now... I'll give it another try tomorrow, or see what other people do. Or wait for a more detailed guide :(
[Captivate Android Development] jankyboy:
Any way to apply this fix using a Mac?
[Captivate Android Development] SlimJ87D:
Just Flashed Stock Rom, redid all the steps again.

Still getting 900. I'm going to blame it on the SD card for now. Hopefully when I get another one it will work better. But for now I'm not getting very good sores.

This could be due to a number of things, it might be how I partitioned my SD card also.
[Captivate Android Development] NukaCola:
No, windows is needed for flashing with Odin. It is reported to work in virtualbox, vmware or similar though.

I also posted a new thread with better instructions (as requested in this thread before, but I was too tired to do it last night). If somebody has instructions, links to other howtos (partitioning!) let me know and I'll edit it in there.
[Captivate Android Development] atinm:
Good job on this! Question regarding building the kernel - did you just enable CONFIG_EXT4 in the .config and build from the Captivate kernel sources? How do you manage to get a 6GB file while I get 2.7GB? Any other things I need to do besides just build the kernel and modules? How do the modules end up in the image - maybe that is what I am missing.

Thanks,

-Atin
[Captivate Android Development] NukaCola:
You are probably missing the initramfs, if you read back in this thread you'll find where iq quickly explain that
[Captivate Android Development] tiger4j:
Any help please? This is exactly what happens while trying to flash JM2. I open odin and click csc. I then put in "captivate_speedfix2.tar" Then while in download mode I plug phone in. Odin then recognizes as 0:[com8]. I then click start.

Added!!

odin v.3 engine (ID:8)...

File analysis...

Get PIT for mapping..

Firmware update start...

zImage...

This is where it stops every time. Phone is rooted and in download mode with android digging. Phone plugged in after odin starts- it recognizes as com8. I am running vista. I click run as administrator. The odin one click restore works fine-Thank God- I do not know why it will not complete. Any ideas? Hopefully?