yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] SlimJ87D:
Maybe it takes time for power to reach the SDCard and for it to load up, I think you might have thought of it. If no one reports about Ext3, I will try it out later.

EDIT: I truly believe this is the problem now. Power tot eh SDCard gets cut. But when we have oru phones plugged in USB, then the cards are constantly on drawing power to the SDCard as the computer reads them. This is why the problem doesn't occur when the cards are being read by the PC.

We would have to run something to make the card on all the time which might either damage our cards or consume a lot of battery. I think this problem will remain on ext3 as well.
[Captivate Android Development] dalingrin:
I have the same problem and I'm not using a ext 3/4 partition.
[Captivate Android Development] _Opiate_:
I have confirmed that the speedfix2 ext4 kernel causes issues with the phones mic during phone calls. Ive re applied it 3 times just to make sure. Anybody using that kernel should make a phone call and listen to your voice in the other persons phone.
[Captivate Android Development] SlimJ87D:
Nuke, what are the CD commands we have to type to move our data back to our phones?

Do we have to do this to switch back? I'm going to give Ext3 a try a bit later but I don't want to have to reinstall all my applications again.

Have you tried the Ext3 method? Does it do the same? I just tested my friends Vibrant and my phone. His phone does sound more clear, and I think Ext4 is causing a problem.

Sure is a bit things that need to be fixed in this method.
[Captivate Android Development] _Opiate_:
im about to give ext3 a shot
[Captivate Android Development] SlimJ87D:
POST DELETED THANKS TO NUKES CONFIRMATION

Please let me know if the voice problem gets fixed and the idle lag when your phone turns on gets fixed?

i'm willing to drop my quadrant scores by 500 if it means more stability until EXT4 is fixed.
[Captivate Android Development] AJerman:
Indeed I sound bad in calls as well. Dropping back to ext3! :(
[Captivate Android Development] SlimJ87D:
Don't drop back yet, we need to confirm if it even works. Opiate will let us know.

I honestly think Ext3 might still ahve the problem. I think the SDCards are drawing a lot of power and messing up the speaker. We might even sound the same if were doing stuff with our SDCards and talking on the phone with the stock Kernels.
[Captivate Android Development] _Opiate_:
Ill let you know as soon as i get it loaded. Its a shame really. I was scoring 1850's with a class 2 sd card but i can't deal with that mic bug. Hopefully the ext 3 wont be too much slower. Guess we'll find out.
[Captivate Android Development] AJerman:
I guess it'll be a race. ;)
[Captivate Android Development] NukaCola:
No no, don't do any of that! There is no linking and whatnot going on.

If you yank the card, the phone will boot to the state it was in when you applied the new kernel. Alternatively do something like (untested):

# mount -t rfs /dev/block/mmcblk0p2 /sdcard/mnt
# busybox cp -a /data/* /sdcard/mnt
# exit
..

then I'd do adb reboot download and reflash with whatever kernel you want.
[Captivate Android Development] _Opiate_:
Im hoping its just a bug in the kernel. If its not then surely we would have read something about it in the i9000 thread by now.
[Captivate Android Development] AJerman:
The one thing that comes to mind is that you said you compiled with 2010q1 when Samsung suggested 2009q3. Maybe it all compiled right, but this could be a side effect of something it didn't like? Perhaps try compiling with the older toolchain and see what happens.
[Captivate Android Development] AJerman:
Actually, we'll find out if that's the likely problem really quick. I'm going to drop back to the stock kernel using userinit.sh to mount, Opiate I assume is dropping back to your compiled ext3 kernel that mounts in kernel. If it's the toolchain, or something else in your compile, his should still have issues while mine wont.

And why can't I edit my last post?
[Captivate Android Development] _Opiate_:
If you can get that method to work can send me a step by step? I dont really understand how that usernit deal works
[Captivate Android Development] NukaCola:
Probably, although it does seem kinda power related (well the lag is, not sure about the voice), did you check voice quality with the handset plugged in?

I'll have to compile and check a few alternate kernels.

Someone can check how the ext4_only kernel does running with /data on the original partition (not the sdcard).

But it does seem like the i9k people didn't have these issues so we should be able to figure them out.
[Captivate Android Development] NukaCola:
Yeah I already thought of that, I can't find that older toolchain atm though.

Yeah if you guys do that we'll know for sure.
[Captivate Android Development] AJerman:
Yeah, actually, I think I'm going to try one more thing in between. I'm going to use the ext4 enabled kernel with an ext3 partition and see what happens. And I guess the ext4 kernel with no SD card partition too. I'll let you guys know how they all work.
[Captivate Android Development] SlimJ87D:
Do we need to flash the stock kernel to go back?

if so, where is the stock kernel located after I remount from the SDCARD back to my phone?

EDIT: STOCK KERNEL HERE!

http://xdaforums.com/showthread.php?t=733937
[Captivate Android Development] SlimJ87D:
Compared the Vibrant and Captivate again which use to sound identical. The Vibrant remains clear even when I have the Captivate plugged into USB.

Sounds like the voice problem is in the Kernel

The SDProblem is a power problem.
[Captivate Android Development] _Opiate_:
We will know soon...im getting ready to flash the ext 3 kernel. Downloading now
[Captivate Android Development] AJerman:
Just tested the ext4 kernel with no external partition, still have voice issues. So it's not an issue with the ext4 partition necessarily, but something in the kernel is affecting the voice quality.

Here's the 2009q3 toolchain page: http://www.codesourcery.com/sgpp/lite/arm/portal/release1039
[Captivate Android Development] ranova:
yea i can confirm there is a mic\voice problem. Good thing I dont use the phone much, I'll wait for a new kernel.

Nuka, can you link the stock kernal for those who want to revert back?
[Captivate Android Development] SlimJ87D:
I linked the stock Kernel already, please read other post. Thank you.
[Captivate Android Development] _Opiate_:
Im almost ready to load the ext 3 kernel if this download would hurry. Its a little slow for some reason
[Captivate Android Development] Anthonok:
Question... When we finally get a custom rom would we need this fix? I've tryd this a few times and have failes everytime and figured i might as well wait until we get a new rom.
[Captivate Android Development] NukaCola:
Great, ill get on that right away when I get home (not long)
[Captivate Android Development] SlimJ87D:
You want me to GMAIL it to you?

I don't think so, because you have to set your kernel up with your SDCARD.

In the near future I think there might be a single click program someone will write to do it all.

They are already doing single click root programs for the vibrant and Droid X so we'll see. But the breakthrough is here with the developers and testers that are dedicated to solving problems!
[Captivate Android Development] _Opiate_:
im putting sim card in and rebooting....
[Captivate Android Development] AJerman:
Why are you guys trying to flash the stock kernel? Don't you want to use NukaCola's ext3 mounting kernel? If you go back to stock you're not using any external partition at all.

Just so you guys can have a quick laugh at my expense, I tried to flash back to the stock kernel and test call quality, and it still sounded like crap. I got worried, then realized I had gone into odin and flashed the radio on accident because I was so used to doing that yesterday! :p

So anyway, tar'd up the original kernel, uploaded it, and with no external partition, it sounds great. So I loaded up an ext3 partition with the STOCK kernel using a userinit.sh script (rather than using NukaCola's ext3 mounting kernel), and it sounds fine still.

So once someone tests with NukaCola's ext3 mounting kernel, we can determine if it's an issue with the kernels or ext4 being enabled in them.
[Captivate Android Development] _Opiate_:
Its still there

For those that are interested quadrant went from 1800 to 1500 when I switched to ext3.
[Captivate Android Development] _Opiate_:
Ext3 seems faster even though its quadrant score is a little lower
[Captivate Android Development] NukaCola:
Does the ext3 kernel have the sleep lag?
[Captivate Android Development] AJerman:
So if it's gone for me, but still there for you, there's definitely something up with the kernels. Lets let him recompile with the other toolkit and see if that helps.

That would answer my question as to why they said to use the older toolkit.
[Captivate Android Development] systoxity:
can anyone post a variation of this on the wiki, i'll edit it up after but i got plenty of guides im still porting over there.

here's the link:

http://samsungcaptivate.wikia.com/wiki/Samsung_Captivate_Wiki

dont forget to give credit, where credit is due.
[Captivate Android Development] NukaCola:
something like that yea, ;)

(Though I should add, they linked directly to the newer toolkit in the i9k sources, thats why I just did a wget on that).
[Captivate Android Development] _Opiate_:
Hopefully we you can resolve this! Your the man Im sure you can lol

and yes ext3 has the "sleep lag" though it doesnt really bother me that much
[Captivate Android Development] amwbt:
Okay, what am I doing wrong? I did the captivate speedup2 kernel with ext4 only. I followed the directions to the T and it tells me to flash the kernel first then copy the data to the sd card. However, when I boot it none of the processes will run and I cannot connect to it through the sdk tools (adb shell) so I can copy the data, am I missing something?. What am i doing wrong?

It will say no device found.....when I run adb shell from the sdk.
[Captivate Android Development] gotfolk:
a very quick question...

(yes i know larger is better)

is a 2gb SD card large enough for me to run the hack once you guys have it nailed down, or should i just wait till this week to pick up a larger card?

also if you guys tell me the 2gb is enough, after i format a larger card when i get it, can i copy and paste the info from the 2gb onto a larger card and have it still work?
[Captivate Android Development] _Opiate_:
Do not boot it with the sd card in. Wait till its booted and pluged in in debug mode and then insert the sd card when your ready to adb shell
[Captivate Android Development] amwbt:
Ah, thanks, greatly appreciated!
[Captivate Android Development] _Opiate_:
If it was me though Id wait for a patched kernel. Unless you never use your phone for calls lol.
[Captivate Android Development] bobbylx:
The same thing happened to me. I got tired of trying to figure it out and used the Odin flash to original method.

Now, I have a question! After all the force closes, I booted into Clockwork recovery and did a wipe then reboot. After that my phone seemed to run just like normal but I noticed that everytime I set a Lock Pattern for the lock screen it would not save. Pretty much whenever I tell it to use the connect the dots lock screen, it will never save it.

So I used the Odin flash to stock method and everything looked good except I still cannot make the connect the dots lock screen work. Has anyone seen this happen? Could I still have the modded kernel or something. I noticed after the Odin flash that all the data was still on my internal SD, I thought it erased everything?

Thanks
[Captivate Android Development] amwbt:
Well, actually, I hardly ever do, and I just got mine running and it will do for the calls I make, they are very short. Other than that, this thing flies!!!!!
[Captivate Android Development] _Opiate_:
The data is going to stay on your card until you manually delete it.
[Captivate Android Development] NukaCola:
I have a new kernel waiting to be flashed, but now I can't get the windows drivers to play nice anymore (I managed to do adb reboot download), now usb errors from windows constantly.

Sigh.
[Captivate Android Development] _Opiate_:
And i have to add that the XDA app sucks for galaxy s phones. Everytime i post i get a force close lol.
[Captivate Android Development] NukaCola:
Yeah, same here, never fails.
[Captivate Android Development] _Opiate_:
D@mn youre fast! Good luck i hope it works!!
[Captivate Android Development] clubtech:
I can confirm that touchdown lags like hell with this fix and besides the quadrant score I did not notice any noticeable difference.

Moving touchdown to /dbdata solved the lag for me for this app.
[Captivate Android Development] _Opiate_:
If you're using then ext4 then try using an ext3. The quadrant is little lower but the phone feels faster to me. Also did you install touchdown before or after doing the fix?
[Captivate Android Development] ranova:
yea, other than synthetic benchmarks (quadrant), I REALLY think everything else is a placebo effect during real world usage. I too didn't really notice a change from stock with the ext4 hack.

Facebook (loading news feed and pictures, scrolling, etc), twitter (reloading tweets), dolphin (new tab, volume button scrolling, etc), and touchdown (whole interface) all lagged for me using the ext4 hack, but since moving them back to /dbdata/data on the NAND, they are snappy again.

I can confirm that I did it correctly because a) I have the voice\mic problem, b) I've changed my home launcher since moving it to SD and Ive pulled the sd and booted regularly into the old home launcher
[Captivate Android Development] kennethpenn:
I need a little bit of help. I went through the process... had one or two hiccups but made it thru. Didn't work. Quadrant benchmarks are the same as always.

If I want to restart everything and go back through the process, what do I have to do? Is it safe to just straight up wipe my SD card and start from the beginning? Do I need to flash back to STOCK now that I'm flashed on the ext4 kernel?
[Captivate Android Development] NukaCola:
The kernel compiled with the 2009q3 abi also exhibits the lag-when-not-plugged in issue. Voice is still horrible as well.

I'm not sure what the issue is and I'm really frustrated with having to deal with these windows driver issues (I have to fiddle for about an hour for every flash, its just an insane time waster).
[Captivate Android Development] NukaCola:
Thant is just weird, I felt that the phone is definitely faster (switching between apps, no freezing/lagging in apps etc.)
[Captivate Android Development] SlimJ87D:
Nuka, is this necessary to reboot the phone back ot normal?

# mount -t rfs /dev/block/mmcblk0p2 /sdcard/mnt

# busybox cp -a /data/* /sdcard/mnt

# exit

And also it didn't work... it says there is no such file in the directory.

But if I just flash over the stock Kernel again, will my applications and everything move back safely to my phone? I don't want to have to reset everything up again.

I am trying to get the phone back to stock again without my applications getting messed up.
[Captivate Android Development] NukaCola:
The easiest thing to do in your case may be to use tibackup to backup all your stuff and then restore it after you flash the stock kernel.
[Captivate Android Development] Tacun:
It seems that even using my bluetooth headset I am having the same recording quality issues.
[Captivate Android Development] kennethpenn:
I tried doing it... but something failed. Still same old benchmarks.

If I want to restart everything and go back through the process, what do I have to do? Is it safe to just straight up wipe my SD card and start from the beginning? Do I need to flash back to STOCK now that I'm flashed on the ext4 kernel?

Edit: nvm for now. The bugs are just too great for me. Once they're patched up I'll go ahead and retry. I'm using Clockwork to restore my backup. Does that bring me back to my stock kernel??
[Captivate Android Development] nmoline:
I am not sure what I am doing wrong, when i input # mkdir /sdcard/mnt I get the following error message "mkdir failed for /sdcard/mnt, File exists"

What am I doing wrong and how can I fix it. Thanks!
[Captivate Android Development] SlimJ87D:
It is telling you that that folder already exist don't worry.

just don't do that step anymore because you have made that folder already.
[Captivate Android Development] autoxer:
A 2gb card will work fine. I'm using a crappy old one and getting 1650-1750 in quadrant.

You should also be fine moving your data to the new card, as long as you can mount and access the ext 3/4 filesystem.
[Captivate Android Development] AJerman:
I dunno man, I think I gotta call you crazy, haha. I notice a HUGE difference from stock to either ext3 or ext4 (so I'm good on ext3 even for now until we can figure out the issue with ext4). Startup times were noticeably faster as well. Not sure what to say if you don't see much difference. The only app I use in common with the ones you listed is Facebook, and I have no lag at all in Facebook, aside of course waiting for the new posts and pictures to load, but that's data network delay, not lag in the app.
[Captivate Android Development] gotfolk:
thank you!

The 2gb SD card i have in the phone currently is a class 6.. (i ran the SD card speed test app from the phone) a friend gave it to me on friday and nothing on the package told me what class it was, so i was happy to see that.

as i am writing this i got to thinking, i really hope this speed test app is actually testing the external card and not the internal card.. it does not tell me if its testing internal or external and what the size of the card is.
[Captivate Android Development] SlimJ87D:
So you don't have that slight lag every time you turn on your phone? What kind of SD card are you using? The majority of us are having a 3 second delay to get our phones out of sleep.
[Captivate Android Development] Fortune090:
Alright, well I flashed back to stock. My phone seemed to have a horrible problem with phone calls like mentioned, but I really couldn't understand myself at all when I called myself. Noticed it was a serious problem when I got a call and they couldn't understand anything I was saying.

Just gonna wait for the kernel to be patched, then I'll go back to the speed fix. Pretty simple process, so it's not gonna be too much of a hassle. I have faith in you Nuka! ;)
[Captivate Android Development] AJerman:
I do have a very slight lag turning on the phone with ext4, and I did have more lag with ext4. The lag while using ext4 was a bit annoying, but the lag with ext3 is definitely tolerable. Aside from that everything seems to run great, definitely better than stock. I'm using an 8 GB class 6 Lexar card that I picked up at my local Target. I benchmarked it at about 11 MBps write speed and 17 MBps read speed.
[Captivate Android Development] AJerman:
Sorry, I meant slight lag turning on the phone with ext3. Why the hell can I not edit my posts anymore?! :mad:
[Captivate Android Development] nmoline:
My next issue comes when I try to unmount /sdcard/mnt It says there is no mount, when I proceed to exit and flash the kernel with Odin it stays on "file analysis" and moves no further. Any help?
[Captivate Android Development] amerikian:
OMFG !!!

:eek::eek::eek::eek::eek:

Thank you so much. I've been trying to use the Mimocan patch for the Captivate and it kept failing........NOW I'm FLYING! Here's my set up:

Captivate I897

Rooted + XWJM2 I9000 Galaxy S 2.1 Eclair + Flashed with Captivate Kernel

EXT4 FIX (ext4 -> 1GB on 8GB class 6)

HSPDA Connected = 1555 DOWN 373 UP

AT&T - Good Voice Calls

All set until Froyo in September!:eek:

Thank you OP!

:eek::eek:
[Captivate Android Development] SlimJ87D:
you must do the following.

Close Odin

Hold the power button on your phone and the Volume Up and Down keys.

The phone will go to a weird screen with a PC and phone.

Now turn on ODIN and Reconnect the USB to the PC in this state.

BUT KEEP HOLDING THE POWER AND VOLUME KEYS.. Your phone will constantly restart. You must let go of the power button only at one of the times the screen is black and then it will relaunch download mode.

Now Odin should recognize the phone again.

But please be advised that there are problems that we are all having, voice calls and a 3 second delay for your phone to get to the lock screen.

I highly advise for you to wait for the final version of this method. As of right now it's more of a beta phase. Like for example the phone is a bit more speedy, but is it worth voice calls being messed up or 3 second delay for your phone to turn on?
[Captivate Android Development] kennethpenn:
To flash back to stock kernel... I just download the Koush http://koush.tandtgaming.com//test/kernel-captivate-stock.tar.md5 thing and put that in CSC in Odin during download mode and "start"??
[Captivate Android Development] mimocan:
is my work still needed for captivate or are you guys all setup? :)
[Captivate Android Development] SlimJ87D:
Yes, that is what I did. But you have to use titanium back up to save yourself some hassle.
[Captivate Android Development] nmoline:
Odin appears to be working but this time it is stuck on "zimage" Should I just wait for it to finish or is it finished?
[Captivate Android Development] Anthonok:
Im sure we can always use more help haha. Thank you for coming up with the initial fix that this Was based off of
[Captivate Android Development] SlimJ87D:
Hi Mimocan!

Well there are 2 very big problems with our Kernels.

1. When turning out phones on to get to the unlock screen, it takes 3 seconds for the phone to turn on.

2. Voice calls sound funny and sometimes can't be heard at all. Some have reported Bluetooth errors.

These are the only two major problems that we can't figure out. It would be great if you could step in and give Nuka some advice :)
[Captivate Android Development] nmoline:
Just cancelled it and got the phone computer screen, got back into the download mode and restarted odin it flashed fine. Once my phone completely reboots I am running Quadrant Standard to see if this worked...
[Captivate Android Development] magicdanw:
So are you using the Modaco kernel with the ext4 fix now, instead of the Captivate kernel? Cause the Modaco ext4 fix is a new kernel, and not a Captivate one, but maybe that works? Anyway, details are always nice :)
[Captivate Android Development] ranova:
FYI, i need more confirmation from other people, but GPS does NOT work for me. Im using the ext4 speedhack. Drove for a good 15 minutes and it did not have a lock. Before I would get a lock within 4 minutes. I tried rebooting without avail

Can someone with any of the speedhack kernels test GPS by driving around with google nav on?
[Captivate Android Development] Postal76:
If I flash the stock ROM using the Odin guide posted on this forum, will that also restore my kernel to the original one?
[Captivate Android Development] nmoline:
WEll I must have done something wrong. Quadrant stuck at 862. I wonder what I did wrong? Flashed fine and everything.
[Captivate Android Development] anilkuj:
yes pls work your magic on captivate too :)
[Captivate Android Development] AJerman:
I've offered my help as well, but being that I'm new to Android, I need a little help in the source. If I can be pointed in the right direction on how to enable ext4 in the kernel, I'll compile a kernel as well and see if I get any different results.

I have faith that we'll figure it out somehow!
[Captivate Android Development] nmoline:
A simple reboot and I am at 1458!!! Whoo Hoo!!! Now let's see how this thing runs!
[Captivate Android Development] tiger4j:
If there's anyone new doing this fix that is debating between sd cards for your ext4 partition, just know that you do not need an expensive high class card to get peak results. I purchased the cheapest sandisk 4 Gb card I could find from Walmart (about $14), used gparted on Ubuntu to partition 1Gig as ext4 2 primary, and used MinFreeManager set to aggresive. This renders Quadrant scores between 1700 and 1850.