yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] :
I've got no lag with ext3 or ext4 external partitions. What are you getting in Quadrant with those? Not that Quadrant is a real life test, but it can at least give an idea if you have it all set up right. With OC+ext3 you should get around 1600-1700, with OC+ext4 you can get as high as 2100 as you can see in my signature.

Edit: Other than the wake up lag, but that's a known bug right now that we haven't been able to pinpoint. If Samsung would just give us working code we wouldn't have to worry about it.[/QUOTE]

I'm getting the same Quadrant scores as before...but now I have the wake lag after doing the lag fix. The OP for the lag fix I used had a way to test if the fix worked at the end of his post and I'm showing the data file he mentioned (and its contents) but the dalvik-cache file was empty. I'm assuming I messed up somewhere along the line. I have no issues with the phone at all, even the battery life seems ok after a few hours of really hard use. Pretty amazing work.
[Captivate Android Development] :
Put your set cpu governor on ondemand to reduce the wake up lag.
[Captivate Android Development] hansmrtn:
Thats just what I was about to say! I have a nexus one that does that, and I changed it to on demand and no wakeup lag. Took the words right out of my mouth

To make this community push forward in development, I highly suggest you pack this into a new boot.img and make it a signed flashable zip file.
[Captivate Android Development] AJerman:
The method mentioned isn't a bad idea, and we'd already planned on trying something similar too, but I know that I personally have too many projects already on this phone, haha. I can't keep up with any more.

The reason they are getting such high Quadrant scores is because that thread is telling you to use ext2. That's not a very good idea since ext2 isn't a journaled file system. I'd much rather stick with ext3 or ext4. You can read Cyanogen's post on this here: http://xdaforums.com/showthread.php?t=520582

So, the method could be worth testing, but stay away from ext2.

I'm still new at all this, so I don't even know how to do that yet, but I'll definitely do it for a final package of this. Right now it's just been testing. I need to go back and fix it so it doesn't just replace 1 GHz before I get too far along.

Thanks for the on demand tip though. I'm going to try that out myself! :)

Edit: On Demand keeps making my phone lock up. After it sleeps for a while it won't wake back up.
[Captivate Android Development] jasonyump:
So just giving some feedback after testing this out all day.

So far the kernels running great. Haven't had a problem with the wakeup lag, well it doesn't bother me. Takes about an extra second to wake. Its running on demand, and i've tried conservative, and performance. All of them worked without any adverse effects.

Although some bugs i've noticed are trying to stress test with setcpu im getting force closes. Haven't successfully been able to stress it yet.

And something else that's off is my battery reading. Not sure if its related to the kernel. So Its jumping all over the place. It was at 19% and a second later i got low battery warnings. Checked and it was at 5%. I put it in sleep for about 5 minutes, reset my phone plugged it in. It was immidiately at 50%. Now its at 30%. So i've only noticed this bug about an hour ago. Will still keep an eye on it.

Ill check it out more tonight and let you know if the bugs still there.

But other then that so far, this kernels been great.
[Captivate Android Development] AJerman:
That's weird that you're having force closes in SetCPU, because I ran it for a while with no issues. Can anyone else try stress testing in SetCPU and see if they have any problem?

Not sure what to say about the battery thing either. I haven't noticed the battery acting weird at all. Is this happening to anyone else?

I'm working on improving the overclocking code right now, in fact, a new kernel just finished compiling, so I'm going to test it out, but I should have something new for you guys to try soon. I'm about to take a break for the night though since I've been playing with this phone just about non-stop for the last couple days, so if I can't get it working tonight I'll do more tomorrow.
[Captivate Android Development] larry996:
guys,

Want to test this out, loaded the kernel and have my SD Card formated with fat32 and a 1gig ext4. Can you tell me how to load the int. scripts for ex4? Or point me to the right post?

thanks man

Larry
[Captivate Android Development] hansmrtn:
I think you should change the title to something less helpless. Since its working and all :D
[Captivate Android Development] JacenSolo2001:
zImage

Can someone give some instructions on how to flash with the new zImage file? I'm anxious to give it a try!

Thanks !
[Captivate Android Development] larry996:
Use Odin3 to flash kernel and PIT. Put Kernel in CSC, and PIT 512 in PIT space
[Captivate Android Development] cruiserbax:
My 7 cents

I flashed this morning and have been testing it for 8 and counting hours now. I ran quadrant standard and scored 1154 I ran CPU benchmark and scored a 10 x average of 651ms and Linpack scored 10.233. I also ran the stress test for 2 hours 4 minutes without any issues. I am currently running through all of my installed apps to look for issues or problems, so far I have tested: Google Maps, Google Sky(using GPS/compess and all sensors), Google Goggles, c:geo, android browser/skyfire, Benchmark, CPU Benchmark, Quadrant standard, Camera(pictures/video all res.), CSDroid (clear sky clock for astronomy) Google Earth, GPS Test, Last.fm, Linpack, youtube, played videos from SD card in various formats (xvid/divx/wmv/mp4) though only in 720P, used wifi and 3g in all apps that use data and beamed/received a file via BT (did not test BT headset as I do not use one) the battery life is about the same as far as I can tell. I don't see a LOT of real world performance improvements but I do notice it some certain instances (when you use certain apps and games a lot you can tell when they feel different) I did not like the ext3/4 fixes and reverted to stock. all my testing has been done with the stock captivate jf6. the only (annoyance not issue) is the wake up lag (I do not use setcpu) it takes about 1.75seconds for it to wake and does NOT bother me. Thank you to all the contributers to this project to include testers.

This is my first post and I feel bad for not having contributed even though I have been following a lot of the winmo and android threads for years now.

-Have an AIRBORNE day!
[Captivate Android Development] rob989_69:
I just used odin and threw the kernel in the pda section, no pit. Worked like a champ.

AJerman, THANK YOU!!! Your fix has made a HUGE difference in my phone. Between this and Xor's script this thing flies and benchmarks rock.
[Captivate Android Development] cruiserbax:
PDA slot

I can confirm that as well, I put it into the PDA slot used adb to put the phone into download and flashed it like that without a pit file
[Captivate Android Development] JacenSolo2001:
I've got the little android with a shovel says "Downloading" do not turn off target.

What's next, and how do i get the zImage file into Odin?

Crap - it's been on the downloading screen for 15 minutes, am i screwed?
[Captivate Android Development] cruiserbax:
Perhaps you should read up on using Odin before messing with your captivate like this? in any case there is a check box next to the button that says "PDA" check it then hit the "PDA" button and select the .tar you downloaded of the kernel.
[Captivate Android Development] JacenSolo2001:
don't have any labels in the Odin screen just a bunch of blank boxes, nothing saying PDA
[Captivate Android Development] cruiserbax:
No Sir! I believe these devices are very hard to "brick" no data is being transfered, just pull the battery it'll be fine! when it flashes it only takes a couple of seconds then auto-reboots.
[Captivate Android Development] JacenSolo2001:
thanks for the input - Odin is still showing all blanks with no labeled boxes, is this a bad install of it maybe? (Windows 7 64bit)
[Captivate Android Development] designgears:
hahaha, no, you cant brick these phones by messing with the software.

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

go there to fix
[Captivate Android Development] JacenSolo2001:
This is what it looks like at the moment
[Captivate Android Development] cruiserbax:
Perhaps, I downloaded Odin3_v1 from the samsung-firmwares site and it looks like the attached image. also I got it to flash fist time by:

connect captivate to pc (you must have the correct drivers installed already)

open Odin3 and put the OC kernel tar into the PDA slot, make sure re-partition is NOT checked and auto-reboot IS checked. open a command prompt on your computer and make adb available or just cd into it's folder/tools folder then do "adb reboot download" without the "" then after it boots into download mode you will see a virtual com port ID highlight in yellow, now click "Start" in Odin3 and it will flash then reboot your captivate.

This is just how I did it and adb means you have to install the android sdk, I tried once to boot into download mode the alternate way but it would not work for me (I did only try once) but I have adb so I just did adb reboot download.
[Captivate Android Development] cruiserbax:
This looks like the one-click download for the stock ROM or something just go here http://www.multiupload.com/DLS7TWUVPY and download the whole program.
[Captivate Android Development] Unhelpful:
Could we get a patch for these changes? Some of us are still looking at tweaking other things and would like to build our own, and I only see links for compiled kernels.
[Captivate Android Development] XorZone:
I think we need dedicated thread or even wiki page for devs.
[Captivate Android Development] JacenSolo2001:
got a good version of Odin now, hanging on file analysis, should it take long for that?- think i'm gonna stop for the night, and try tomorrow after work...thanks for the assistance all.
[Captivate Android Development] designgears:
You have to have odin open and the usb plugged in when you enter download mode or it wont get past that.

you should take this over to the stock rom thread, read in there, this has been discussed many many times in that thread.
[Captivate Android Development] JacenSolo2001:
crap - stuck on file analysis, with digging droid, read the other thread on odin, i just want back to normal phone use....help???

Is there anyway to get to recovery mode from here just to reset the phone? Mild state of panic at the moment
[Captivate Android Development] :
Next time do a little research, read about it, learn few things adb commands, read a little about flashing devices etc, don't just jump into it knowing jack st about it, next time wait for a simpler way of flashing a kernel, like for example by an update.zip thru a custom recovery.
[Captivate Android Development] JacenSolo2001:
thanks - that helps alot - not....guess i'm off to the store tomorrow to see about getting a replacement
[Captivate Android Development] designgears:
please please go read, everything in the in the stock rom thread, stop causing drama, your posts have been reported for removal so we can get back on topic.

You don't need to replace your phone, the software is broken, but you cannot brick these phones, you can always go back.
[Captivate Android Development] JacenSolo2001:
thanks to those that tried to help me out, I've re-read the thread I was referred to and are still in the same situation.
[Captivate Android Development] kennethpenn:
Flashed the kernel. Works flawlessly. Looking forward to coordination between AJerman and NukaCola for an ext4+1.2 GHz fix.

You should post a new thread now. The thread title and contents are a little confusing to find the actual thing.
[Captivate Android Development] systoxity:
excellent work guys. thanks a million! :)
[Captivate Android Development] kennethpenn:
Consisten 1138-like Quadrant scores with the NAND app lag fix. Looking forward to that 2100 w/ ext4!
[Captivate Android Development] sickwitit:
1139 Quadrant scores with the NAND app lag fix. Can't figure out how to partition for the ext4.
[Captivate Android Development] :
It took me awhile to figure out a way too. I downloaded a copy of Ubuntu onto a usb drive and booted my PC from it then went into System>Admin>and disk options or w/e it was lol, but its not too hard and it gives you the option of ext3 or ext4.
[Captivate Android Development] sickwitit:
Thanks big99gt, I'll give that a try.
[Captivate Android Development] max_warheads:
Have you guys seen the virtrual ext2 fix?

I'm pushing 2200+ scores. 1900+ with gmail and fb SNS in the background at the same time as running quadrant. Stock rom, stock kernel.

http://xdaforums.com/showthread.php?t=749530
[Captivate Android Development] USHERROB:
the problem w/ that (as far as iv researched) is that ext2 has no journaling, which Cyan said is not good to use at all. correct me if im wrong/ if this does somethin different
[Captivate Android Development] Unhelpful:
It looked like a bad idea to me, too. People need to get past the idea that speed is everything. Ext3/4 are slower because they write extra data to guarantee that they can recover gracefully from crashes and power failures. Assuming that you have a choice about shutting down properly every time is not smart, and will lose you data, especially if you can't use fsck to fix your non-voting phone and are forced to wipe /data.

Sent from my Samsung Captivate
[Captivate Android Development] max_warheads:
Ext2 has no journaling, correct.

but then you shouldn't be yanking the battery out of a running phone any more than you should out of a running laptop.
[Captivate Android Development] ashwincr:
can anyone check if this kernel has bluetooth issues like the stock captivate kernel? A lot of people including me who are running the stock captivate kernel on a galaxy i9000 rom have seen highly staticky (unusable) call quality on bluetooth. basically the calling party just hears static. No problems with streaming music or hearing the other party on bluetooth, static is only on the other end of a call.
[Captivate Android Development] AJerman:
Wow, that was like 5 pages overnight. Sorry guys, I had to take the night off, I was getting a headache from reading code so much.

I appreciate the feedback so far, and it sounds like things seem to be working fine for everyone. I know this is hidden away a little with the title and all, but I still consider this in the process of being ported. I will make another topic on this, probably today, to have a consolidated post of everything. Right now justanothercrowd and I are working to get a new compile that doesn't lose the 1 GHz step, and I think he even added a little something extra, so sit tight and we'll have a more "final" version soon. This was just a test to make sure speeds and voltages were good and didn't break anything, and it looks like it's been pretty good so far.

Again, I really urge any of you reading this and thinking about doing this to be sure you know what you're doing. You won't find many instructions in threads like this because these kind of mods are the kind of things you should only do if you already know what you're doing. This phone really is nearly unbrickable, but flashing firmware isn't something to mess around with without knowing what you're doing. By all means, we would love to have more of you learn and join us, but read everything about odin and how to flash first for your sake.

As for Bluetooth, I don't know. I don't use bluetooth so I can't test it. If you're having problems with the Captivate kernel on an I9000 ROM then there are probably a lot of things that could be causing an issue and it probably needs it's own topic to discuss that. Nothing is changed in bluetooth in this kernel, so I'd expect it would work the same, but I don't use the I9000 ROM or bluetooth, sorry.

Doesn't matter, Android doesn't unmount partitions on shutdown anyway, so you might as well yank it every time. This is why you shouldn't use ext2. The difference wouldn't even be noticeable, so I'm not even entertaining the idea of ext2 for the sake of 100-200 more points on Quadrant. I assure you that you will NEVER notice the difference between 2100 and 2200 Quadrant scores.
[Captivate Android Development] rob989_69:
I can tell you that bluetooth is fine on my phone with this kernel. And I also agree that you won't notice a difference in scores in quadrant. Honestly, I don't notice a difference between JUST this kernel and this kernel + Nuka's lag fix. Score's go WAY up but phone isn't really any faster. Scores jumped from 1100+ with this, to close to or just over 2000 with Nuka's and Xor's fixes and up to 2500+ with the ext2 fix. But the phone was no faster.
[Captivate Android Development] wingman_214:
is any body having issues with the phone not waking up from sleep? it randomly happens when phone is asleep it doesn't matter how many programs are open. i have noticed that the wake up lag is non existent when plugged into ac power.
[Captivate Android Development] sl8125:
Is this kernel stable condition? I saw on page two the link to the kernel? Is this the correct link? What is the status so far?
[Captivate Android Development] joedon3:
I had no problems with the wake lag or wake from sleep, UNTIL I installed SetCPU. Then it would freeze every time the screen turned off. I have removed SetCPU and it seems ok now, although, there is a little lag.

I did notice that when I rebooted the device and looked at my SetCPU settings, min and max were set at 19.2Mhz every time.
[Captivate Android Development] solufein:
yah, that's the only one posted in this thread. dunno if another has poped up. got it running on my wife and I's phone. mainly for the call quality fix for her, and the oc for me, lol.

so far so good. get the wake up lag now though. never had it before =/
[Captivate Android Development] Unhelpful:
There is little reason to use SetCPU unless you are going to set up overheat/low power profiles. Stock kernels boot with conservative CPU governor enabled, which should be plenty for powersaving. I've noticed lockup-while-sleeping twice, resolved both times only when SetCPU was uninstalled.

EDIT: Except obviously you can use it to stress-test your overclocked kernel. Obviously forgot which thread I was on there.
[Captivate Android Development] AJerman:
The only time I've seen a lockup was when I put the governor settting on ondemand. I don't know why that would have caused the lock up, but it did it a couple of times. Other than that I've been running with 1.2 GHz as my max for a while.

The reason for the delay is that none of the other devs and I have been able to get speeds ADDED rather than replaced. This is important to me because you can use SetCPU to set a max speed of 1 GHz to turn off OC, and turn it up when you want. Right now you have to lose a speed to add a speed. I thought it was fixed, but it turns out it's still doing the same thing to us. So right now, the kernel in this thread that replaces 1 GHz with 1.2 GHz is the best kernel to use. Nothing better has been released yet. I'm starting to wonder if there's a hardware limitation of some sort, but hoping not.

Also, it sounds like mimocan has fixed the wake up lag issue, so hopefully I can get that implemented as well. Once those two things are fixed or deemed not possible, I'll make a new topic for everyone.
[Captivate Android Development] sl8125:
Will this fix the lag issue on the mimocan variant fix too? With OC and the mimocan variant fix. I will be set til froyo comes.
[Captivate Android Development] Zilch25:
It should, Mimo helped the creator of the Samset ROM for the i9000 with the exact same issue yesterday. However we don't know exactly what was done, but the symptoms were identical, so logically if we can get him to spill the beans on what he did for that we should be able to pinpoint what's going wrong with our kernel issues.
[Captivate Android Development] mostyle:
Fix

I know this isn't a technical observation but it appears as if the kernel is dropping voltage (in affect causing a standby) to the external SD. Again, I cannot code so I'll gracefully STFU.. That being said...

With Ajermann's kernel am I correct that it supports ext4 but lacks auto mount so any usage would require a hybrid joining of this kernel with the userinit.sh fix referenced elsewhere?

I appreciate all you guys' help with the compiling!

Thanks!
[Captivate Android Development] AJerman:
Yeah, the wake up lag has nothing to do with any mod we've done, it's just present in EVERY kernel we compile. Something in the source Samsung gave us wasn't right and is causing the issue. Once we find out what the problem is all of our kernels will have that fixed.
[Captivate Android Development] Zilch25:
It's strange though that the guy who did Samset encountered this issue with the i9000 kernel (which as far as we know *IS* complete). Perhaps there's just some step in there that we've missed that's unique to Samsung kernels? Then again the Vibrant guys don't have this problem...

I don't know how you guys haven't torn your hair out by now... my head is ready to explode.
[Captivate Android Development] LGSilva:
Maybe this will help on making a boot.img: http://code.google.com/p/seek-for-android/source/browse/wiki/HowToBuildKernelGalaxy.wiki?r=48#
[Captivate Android Development] mostyle:
I read that to get the audio issue resolved they pulled code from the vibrant sources.. Is this something that might work with the lag as well, or is the vibrant suffering the same flaw?
[Captivate Android Development] Zilch25:
From what I can tell the vibrant isn't... and it would be a simple matter of pulling stuff from the Vibrant to the Captivate- but unfortunately we don't have any idea what needs to be pulled, kernels are pretty complicated little balls of instruction
[Captivate Android Development] wingman_214:
I can confirm that the phone only hangs when setcpu is set to on demand. When its set to conservative or performance there is no locking.

Is there any way to making the phone think that its in ac power when in standby?
[Captivate Android Development] rajendra82:
Since our only remaining big issue is wake up lag on kernels built from the Samsung released source code, I wonder if anyone has a set of experiments to better isolate the cause:

Has someone tried to flash on their Captivate all of these and then compared wake up lag:

1. A kernel built from the Samsung source with no modifications

2. A kernel built from the Samsung source with the 1.2 GHz overclock modifications

3. A precompiled kernel pulled from the stock Captivate ROM

4. A precompiled kernel pulled from the stock Vibrant ROM and a source compiled version of the same

5. A precompiled kernel pulled from the stock i900 ROM and a source compiled version of the same

If there is more lag under some of these conditions than the others, then has someone sent the same lagging kernel to someone with a Vibrant or i9000 and asked them to see if their phones also lag with the kernel flashed on.

When the experiment is completed with all of these conditions, the reason for the lag can be better isolated.
[Captivate Android Development] TimF:
Is there a utility that can compare the of the Vibrant and the Captivate source trees in order to find out what the differences are. If there is, this might narrow the scope of where the missing files/instructions are.

Just a thought.
[Captivate Android Development] iGuitar93:
Maybe but I don't think so. You might have to just go through the code by reading it. I could be wrong though
[Captivate Android Development] TimF:
There has to be something! If puny little Windows has the powerful Windiff; the mighty Linux must have something that is super awesome! ;)
[Captivate Android Development] Zilch25:
Well after scouring the vibrant EXT3/4 thread they're claiming to get wake lag *SOMETIMES* O_o, which I guess is still better than us getting it ALL the time.
[Captivate Android Development] iGuitar93:
Oh you want an app to run on linux?

EDIT: I found a linux application called Meld. It seems similar. I also found some programs called xxdiff and kdiff3. I don't know how good they are though.