yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] max_warheads:
mmcblk0 = internal, mmcblk1 = external

For the tfsr, none of them have valid partitions, but it comes to about 1GB

Disk /dev/block/tfsr0!c: 525 MB, 525336576 bytes
Disk /dev/block/tfsr1: 0 MB, 262144 bytes
Disk /dev/block/tfsr2: 0 MB, 262144 bytes
Disk /dev/block/tfsr3: 10 MB, 10485760 bytes
Disk /dev/block/tfsr4: 1 MB, 1310720 bytes
Disk /dev/block/tfsr5: 1 MB, 1310720 bytes
Disk /dev/block/tfsr6: 5 MB, 5242880 bytes
Disk /dev/block/tfsr7: 7 MB, 7864320 bytes
Disk /dev/block/tfsr8: 7 MB, 7864320 bytes
Disk /dev/block/tfsr9: 300 MB, 300417024 bytes
Disk /dev/block/tfsr10: 140 MB, 140509184 bytes
Disk /dev/block/tfsr11: 36 MB, 36700160 bytes
Disk /dev/block/tfsr12: 13 MB, 13107200 bytes

For stl: still some sort-of valid partitions, of course directly on the block device. A bunch of cant opens though. ~ 464MB I can see..

fdisk: can't open '/dev/block/stl1': Invalid argument
fdisk: can't open '/dev/block/stl2': Invalid argument
Disk /dev/block/stl3: 6 MB, 6553600 bytes (?)
fdisk: can't open '/dev/block/stl4': Invalid argument
fdisk: can't open '/dev/block/stl5': Invalid argument
Disk /dev/block/stl6: 1 MB, 1310720 bytes (unkown value for cylinders)
fdisk: can't open '/dev/block/stl7': Invalid argument
fdisk: can't open '/dev/block/stl8': Invalid argument
Disk /dev/block/stl9: 291 MB, 291504128 bytes (?)
Disk /dev/block/stl10: 134 MB, 134742016 bytes (?)
Disk /dev/block/stl11: 32 MB, 32768000 bytes (?)
fdisk: can't open '/dev/block/stl12': Invalid argument

BML: matching the tfsr, to the T, but without partition information.

Thats all I can dig up, I've attached an `ls -l /dev > devs.txt`

It's hiding in there somewhere.
[Captivate Android Development] XorZone:
Can't the analysis by done on the kernel sources?

Also, what do you think about best file system for our need?

UBIFS (can we use it with external sdhc)? YAFFS? Or JFFS2?

do we really need journal or ext2 (or ext3 w/o journal) will be enough?
[Captivate Android Development] ranova:
here's what koush has to say about the SGS:

http://twitter.com/koush/status/20321413798
[Captivate Android Development] AJerman:
Well, not the best news, but I just compiled a kernel myself and have voice call distortion as well, so it's not just something in NukaCola's compile of the kernel. Not really sure what would be causing it. :confused:
[Captivate Android Development] dalingrin:
What does the voice call distortion sound like?

I'm curious because the captivates audio uses some noise reduction algorithms.

The settings can be tweaked in *#*#197328640#*#*

I wonder if the settings are different in a compiled kernel vs stock.
[Captivate Android Development] NukaCola:
This is pretty much what I have been working on just now, didn't realize that there was a tweakable setting there, I'll have to go through them all now and compare...

The i897 sources have a KEPLER_AUDIO_A1026 config option, that will not compile, missing files. It also has a A1026_HW_Rev02 option (AUDIO_HW_Rev02) that will compile. But kernels with that driver sound the same as the ones without. The i9k sources don't have those at all.

Now it is time to compare the options in the secret menu I guess, I'll upload a kernel with that option enabled after I walk my dog for the peeps that want to test around.
[Captivate Android Development] XorZone:
Could you try audio loopback test please?

*#*#197328640#*#*

Common-factory test-audio loopback- and both pcm and packet for the handset plz.
[Captivate Android Development] NukaCola:
Here is a kernel with the A1026_HW_Rev02 driver compiled in. It should mount rfs from internal sd card or ext3 or ext4 from external card on /data depending on what you have setup. Doesn't have much testing other than that it boots and voice sounds just as bad as with our other kernels.

Is there a document showing all stock settings in that menu? There is a lot of junk in there...
[Captivate Android Development] dalingrin:
Has anyone been able to get a stock kernel config other than the one in the source?

Running diff on the captivate kernel config and the I9000 kernel shows the following lines added in the Captivate kernel.

I haven't a clue what KEPLER is. Perhaps we should try enabling a different revision?

I believe S5PC110 is the SOC, so I'm thinking these added configs are for different hardware revisions (T959 is the vibrant)

Perhaps we should try VER_B2 or B3?

> # CONFIG_BLK_DEV_INITRD is not set
246a245,254
> CONFIG_S5PC110_KEPLER_BOARD=y
> # CONFIG_S5PC110_T959_BOARD is not set
> # CONFIG_S5PC110_FLEMING_BOARD is not set
> CONFIG_KEPLER_VER_B0=y
> # CONFIG_KEPLER_VER_B2 is not set
> # CONFIG_KEPLER_VER_B3 is not set
> # CONFIG_BEHOLD3_VER_B0 is not set
> # CONFIG_T959_VER_B0 is not set
> # CONFIG_T959_VER_B5 is not set
> # CONFIG_FLEMING_VER_B0 is not set
862a871
> # CONFIG_CONFIG_KEPLER_TSP_VER3_5 is not set
1150a1160
> # CONFIG_VIDEO_ISX005 is not set
1256a1267
> # CONFIG_AUDIO_HW_Rev02 is not set

Edit: I tried the vibrant kernel(which has the same config as captivate) and I get the same distortion.

Loopback test with the vibrant kernel produces same distortion and feedback once the microphone picks up something of volume. Which again makes me think the problem has to do

with the noise canceling algorithms or lack there of.
[Captivate Android Development] XorZone:
Could you point me to the intro for cross compiling plz?

I've done some linux dev and compiled kernel ofcourse, but never done cross. I'll play with conf.

Is it possible to flash directly zImage?
[Captivate Android Development] NukaCola:
Yeah, the A1020 seems to be a 'voice processor' chip. So I think we need to figure out that driver. It could be that we are just not getting the default settings right even with the driver present.
[Captivate Android Development] NukaCola:
Just grab the arm toolchain specified i the i897 sources README and put it where the build_kernel.sh script can find it. Make sure you comment out the line that does make defconfig from the build_kernel.sh script (there is also a .config option to use the crosscompiler, don't disable that).
[Captivate Android Development] dalingrin:
What did you do for the initramfs?

It seems to me that it has to be the A1026. I also get a compile error if I enable it.

BTW, I believe Kepler refers to audio that is built into the SOC.
[Captivate Android Development] AJerman:
Just grab a stock zImage and follow the instructions here: http://xdaforums.com/showpost.php?p=7431131&postcount=268

Check the rest of that thread for more info if you need it.
[Captivate Android Development] SlimJ87D:
Has Development for this fix ended?
[Captivate Android Development] NukaCola:
Not on my part. I'm guessing nobody has made any breakthrough worth reporting on :(

I'm hoping to have more time to spend on it this weekend.
[Captivate Android Development] tbrouwer:
How about the lag issue with waking the phone up? Seems like everybody has a problem of having to wait 2-3 seconds for the screen to come on.
[Captivate Android Development] SlimJ87D:
Ummm... we have discussed this multiple times. It is one of the problems being addressed.
[Captivate Android Development] rajendra82:
People in this thread have flashed in the Vibrant ROM on their Captivate, and are seeing the high quadrant scores. They do report crashes related to the GPS. Since the Vibrant and Captivate are much more similar in terms of button layout and hardware capabilities than the Galaxy S i9000 and the Captivate, this is probably not surprising. May be someone can look at the Vibrant kernel source code for guidance as to how to fix our sound chip issues.

http://xdaforums.com/showthread.php?t=746466
[Captivate Android Development] dalingrin:
I've flashed the vibrant kernel and it had the same microphone issues as the i9000 kernel and the captivate source.

All the kernels I have flashed are built from source.
[Captivate Android Development] Fortune090:
Did you make sure to flash the stock Odin rom first?

Sent from my Captivate
[Captivate Android Development] XorZone:
Ok. I finally received my microsd.

This thing is interesting. Thanks rajendra82!

With the stock kernel (I think it is stock because I reflashed it from I897UCJF6.tar, version 2.6.29 jetaek.lee@sep-11 #2) I following the links found the thread I've read like week ago.

http://xdaforums.com/showthread.php?t=739647 But this time I have sd card and do not want to try buggy vibrant kernel.

Steps I've done:

-1. Partitioned my 8gb card as 6.5fat+1.5 ext3

1. Backed up /system/bin/playlogos1

2. Renamed /system/bin/playlogos1 into /system/bin/playlogosnow

3. Pushed playlogos1 from advanced zip (enableuserinit.zip)

4. Corrected permissions for playlogos1

5. Pushed userinit.sh (it is userinit from vibranta2sd.zip) into /data/local

6. Corrected permissions for /data/local/userinit.sh

7. Rebooted

Now with kernel mentioned above I have 1350-1450 Quandrant score.

P.S. Plz let me know if the kernel version I mention is the stock.

P.S.S I do not have sound problems, but unlock is like 1 sec delay.
[Captivate Android Development] Fortune090:
Yes that is stock...

I think a 1 sec unlock delay is normal... I'm trying this now. Just flashed back to stock from the VibrantUpdate speed fix. Was tired of trying to get the GPS to work again with no success... Nothing else was wrong with it though. Which is somewhat relieving, but still. Still had a problem.

EDIT: Could you post a more elaborate tutorial? I did this and had no success... Score was still ~900.
[Captivate Android Development] _Opiate_:
Yes i would like to see a more elaborate tutorial on this method as well.
[Captivate Android Development] dalingrin:
If your reply was to me, then no I did not flash to a stock rom before flashing the kernel.

I was running JM2 I9000 rom with the stock captivate kernel and then flashed the vibrant kernel.
[Captivate Android Development] sl8125:
I tried the vibrant kernel but it didn't work for me. I know i didn't do it right. there no clear instructions how it was done, so i left it alone. However, it worked for me one time got a quadron score of 1500 and the phone was so fast. no lagg and supersonic speed. But my phone lost signals. no voice/no data so i went back. If you can do a write up on how its done, we all would appreciated.
[Captivate Android Development] XorZone:
Ok, let's try (I had strange mix in my captivate. But I reflashed with odin3 and after nandroid data restore reflashed stock kernel back just in case as email in version made me nervous). I'll try to backup. Revert to complete stock, backup my internal storage do a master clear and reapply this latter.

1. Preparation:

a) Download vibranta2sd.zip from http://xdaforums.com/showthread.php?t=739647

b) Part your sd card as fat32 and ext3. I have 6.5G fat32 and 1.5G ext3

2. Unpack it

3. adb pull /system/bin/playlogos1 playlogos1.bak

4. adb shell

5. su

6. cd /system/bin

7. mv playlogos1 playlogosnow

8. adb push playlogos1 /system/bin/

9. adb push userinit /data/local/

10. adb shell + su

11. chmod 755 /system/bin/playlogos1

12. chmod 755 /data/local/userinit

13. verify change cat /system/bin/playlogos1 (should be script)

Not sure if you need to remount / rw. I didn't.

14. Reboot.

Check if /sd-ext exist

If yes ls it and you should have data and dalvik-cache there.

NOTE: they have different names for userinit in vibranta2sd.zip and enableuserinit.zip

Make sure you have same name of file and in script, e.g. 'userinit' and your playlogos1 script loosk like:

#!/system/bin/sh
sh /data/local/userinit
playlogosnow
[Captivate Android Development] Fortune090:
-1. Download the update from this thread: http://xdaforums.com/showthread.php?t=743506

1a. Flash stock Odin3 rom. (For the Captivate).

1b. Root

2. Download ROM Manager from Market.

3. Install the Captivate Clockwork for Captivate in ROM Manager.

4. Transfer the VibrantDeodexed.zip to /sdcard/ root.

MAKE SURE YOUR ext3 PARTITIONED SDCARD IS INSERTED

5. Reboot to Recovery (in ROM Manager)

6. Install zip from sdcard>choose zip>VibrantDeodexed.zip

7. After it finishes, reboot and be patient. The initial startup takes some time...
[Captivate Android Development] rob989_69:
I'm curious, on the post in the General section regarding loading the Vibrant kernels it says GPS doesn't work. is that the case here?/
[Captivate Android Development] XorZone:
In vibrant variant yes.

with stock kernel it works fine for me.

I'm backing up internal storage onto external sd in order to do clean test and see how it works with stock kernel.

I do not want to have buggy things if it can be achieved by simply adding userinit script.
[Captivate Android Development] rob989_69:
Sorry, I'm trying to keep up here. The post by fortune points to the vibrant kernel that has GPS Issues correct?

Do you have a seperate fix I somehow missed??
[Captivate Android Development] Fortune090:
Ok, XorZone, I did everything you posted step by step and didn't get anything... Quadrant score was 861. Script was working right too.
[Captivate Android Development] Fortune090:
That is correct. He wanted a clear tutorial. Still has some GPS issues (just simply doesn't work. Doesn't activate or anything.)

I applied the userinit change, and it's not buggy at all. Seems like nothing has changed... Not sure if I'm missing anything here... haha
[Captivate Android Development] XorZone:
Just wait a bit. I'll check clear stock rom with empty internal storage with steps:

Odin3 Master Clear, Odin3 stock firmware, root, this fix.

Will see if I have strange brew right now, or it works on stock.

Will keep ya guys posted.
[Captivate Android Development] XorZone:
Ok, I got it.

Works with stock rom and kernel.

Fortune090, I have few ideas why you can have problems.

I'll create new thread for the step by step instructions.
[Captivate Android Development] XorZone:
Ok, Done guide, please let me know how it works in that thread http://xdaforums.com/showthread.php?p=7542083
[Captivate Android Development] amerikian:
Guys,

Thanks for the work on this! I've been following this thread closely for a fix to "the fix". Any way for this to work with non-stock ROMs? Or does it have to be the stock ROM? If i flashed to stock via Odin3 and then installed JP5 with SamSet 1.9a, for example, would this still work?
[Captivate Android Development] amerikian:
XorZone - any reason why you didn't post these steps on the new Thread? These seem much easier.
[Captivate Android Development] XorZone:
I can not see the reason why not.

If you are using kernel w/o auto mount at startup.

BTW. I posted new thread.
[Captivate Android Development] XorZone:
As usual I wanted to verify it works on stock (my version was strange brew of different parts and affected with experiments)
[Captivate Android Development] AJerman:
Xor, thanks for posting that guide. I've been using the userinit version of this mod since the start because of the kernel issues, but it's nice to see someone write up a guide.

Back to the custom kernel though, has anyone made any headway on the audio issue? I've compiled a custom kernel that overclocks the processor to 1.2 GHz, but it, of course, has the audio issues that come with every custom compiled kernel so far. I've been given suggestions that it could be something missing from the .config files, but I'm not sure what, and I don't know how we could get a .config that matches the one Samsung is using to compile the kernel. As far as I can tell though, we're using EVERYTHING bone stock, and it's still giving us this audio issue. This is our biggest hurdle right now before being able to do much with custom kernels. :confused:
[Captivate Android Development] XorZone:
Thanks.

I think we should write to the samsung support and blame that source they posted have showstopper!
[Captivate Android Development] AJerman:
Actually, that's a good idea. I think I'll email them right now and see if we can get to the bottom of this. I don't know how good they are at responding, but we'll find out!
[Captivate Android Development] XorZone:
Even at&t block some of our advanced experienced, but samsung as well as htc benefits a lot from this work.

And sharing opensource is the commitment.

Let me know how it goes. I'll ping'em as well, but not today.
[Captivate Android Development] ace518:
try samset 1.9b it tried 1.9a and it gave me force close on android.phone... 1.9b seems so far to be stable
[Captivate Android Development] _Opiate_:
Using an i9000 kernel is not a good idea.
[Captivate Android Development] AJerman:
Haha, no, it's not, but hopefully that won't even be an issue for long. I figured out the audio issue, so now we just need to fix the delayed wake up. I already emailed Samsung, so we'll see if they email me back. If so I'll just let them know what I found that was missing and hopefully they can update the source package with what's missing.
[Captivate Android Development] MSigler:
Vibrant ROM is great, but like everyone said, no GPS, trying to fix it now.
[Captivate Android Development] AllTheWay:
Quadrant Score of 1526 and second time around got a score of 1623 with the default AT&T ROM and ext3. I don't know about all the Quadrant scores and such but I do know that my device performs a lot faster and Dolphin browser is screaming right now. LauncherPro is also a lot smoother...apps do seem to open and close a lot faster.

Thanks for the fix very easy guide to follow once I figured out how to partition my SD card.

If anybody has trouble with formatting and partitioning cards I found a really easy to use guide with Ubuntu. Has illustrations and the whole nine yards.

http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=535914

The only downside that when I push the power button for the backlight to come on it takes about 3 to 4 seconds for the device to finally come on.
[Captivate Android Development] vendetta007:
You solved the audio issue? What was the problem?
[Captivate Android Development] NukaCola:
Yeah he figured it out, we were m missing files that could be lifted from the vibrant kernel.

The op here is updated with a fixed ext hack kernel
[Captivate Android Development] alphadog00:
That "turn on" lag is a deal breaker for me. I don't think i would want to wait that long every time. I suspect (as I posted in the other thread) that the OS is set to suspend power to the SD card when in standby - i wonder if having music playing off the fat32 partition would result in faster wake time - since the sd card would still have power.
[Captivate Android Development] Nausicaa647:
I find if I leave Nimbuzz running then the screen lock lag disappears.
[Captivate Android Development] NukaCola:
The lag is probably a power saving thing but since it is present even with default /data it is not a sd card power issue.
[Captivate Android Development] alphadog00:
I do not have any lag with turning on the phone with the stock os, so simething in the fix must cause it.
[Captivate Android Development] TimF:
I might have missed it but I have yet to see an explanation why the NAND and internal SD could not be re-partitioned instead of using the External SD card.

I personally don't like the Idea of having to rely on the app data stored on a removable disk. Also, if the turn-on delay is being caused by the sd card being powered down while in sleep mode, an NAND solution would prevent the delay.
[Captivate Android Development] _Opiate_:
So the new kernel post in the OP that mounts both ext3 and ext4 doest have the audio issue?!
[Captivate Android Development] _Opiate_:
Im not so sure about that because using the userinit.sh script to mount an ext-3 partition doesn't produce the wake lag.
[Captivate Android Development] AJerman:
It doesn't have anything to do with the SD card, it's just with our custom kernels. Just like the audio issues we had, didn't have to do with using an SD card, Samsung just gave us faulty source code. Same thing with the power on issue, and here's how I can prove it. I've been using the userinit method to mount an ext3 partition using the stock kernel for quite a while with no lag at all. As soon as I put a custom kernel that I compiled onto it, I had the wake up lag with no changes to my ext3 data partition setup.

So that's the next thing on our list. If we can fix the lag we'll be perfect.

Yeah, he updated the kernels on the front page. No audio issue now.
[Captivate Android Development] _Opiate_:
That's GREAT news. I don't know how i missed it. Now I can go back to JM2 with samset! I had to run stock OS using the userinit.sh script to mount a partition because for some reason using JM2 with or without samset would cause BusyBox to not show up in the market. Don't know why but it was seriously annoying. Now I can get rid of all this bloat ware again!
[Captivate Android Development] sl8125:
Let me get this straight. You have the userinit fix that uses the ext3 on sd card and also the variant mimocan fix on ext3 too. you can have both fix together? sorry got lost somewhers.

But my real question is can you have mimocan fix and userinit fix together running at same time. Just a thought.
[Captivate Android Development] Fortune090:
No. What he's saying is that he built his own custom stock kernel (no sort of fixes) and it had the wake up lag. It's just the firmware we were given by Samsung. Just a little faulty for building custom kernels. I know a few people that are contacting Samsung about it...

It would still have the wake up lag because of the fact it uses a custom kernel. The userinit fix doesn't have any problems because it still functions on a complete stock rom.
[Captivate Android Development] AJerman:
Yeah, what he said. And no, you can't have them running together because they are two methods of doing the same thing. But one method can be done on an entirely stock kernel, the other uses a modification in the kernel to do the same thing. The point was, the wake up delay wasn't there when I was using an ext3 partition on the stock kernel, so it's not an issue with using an external partition on an SD card, it's an issue with the fact that we're using custom kernels at all. Some problem in the source or config. We're still trying to figure out what.
[Captivate Android Development] NukaCola:
Exactly. However it is not connected to the 'external sd card /data partition hack', eg the 'mimocan fix'. It is an unrelated issue with our kernels at the moment.
[Captivate Android Development] sl8125:
How is this fix different to the Mimocan fix? Just my curiosity.
[Captivate Android Development] Fortune090:
Mimocan's fix replaces the stock kernel with a custom built kernel that mounts /data/ to ext3 or 4.

XorZone's fix runs a script on startup that does what Mimocan's fix does, using a complete stock kernel.
[Captivate Android Development] NukaCola:
The only issue with that is that the mount happens a little too late during the boot and can cause race issues with stock android services.

Some people seem to be running it fine, I had terrible stability problems and no gps at all with a videoplayer=>userinit script.
[Captivate Android Development] _Opiate_:
The only thing I dislike about XorZone's fix is I have to run Stock OS. You have to update BusyBox for it to work and for some strange reason when running the JM2 i9000 ROM with or without the SamSet update.zip busybox does not show up in the market.

I tried installing a backup I had of busybox so I could run what I wanted but no luck so Im fixing to go back to this kernel mounting fix now that the audio issue is fixed. I can live with the wakeup lag for a little while. I mean hell even in the stock OS with no mods the screen lags for about a second and a half when you hit the wake button so its not that big of a difference.