yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] TheEscapist:
try just doing mount -t ext4 /dev/block/mmcblk0p2 /data, maybe one of the options is causing the problem. Additionally, try formating it, then remounting it as yaffs2, so mount -t yaffs2 /dev/block/mmcblk0p2 /data

I'll do some more work on it later tonight, I got to go to work in a few minutes.
[Captivate Android Development] cchant:
yes but it does not stay mounted once CM7 boots.
[Captivate Android Development] junktzu:
I'm sure you guys already saw this but it looks like the cappy is getting a little love...
[Captivate Android Development] slifer315:
codeworkx also said that he was only going to do that first step and that someone needs to step up and start maintaining the captivate version.

http://forum.cyanogenmod.com/topic/15169-sgh-i897-cm7-work-in-progress/
[Captivate Android Development] My20:
I AM NOT RESPONSIBLE FOR ANY DAMAGE

+++ test script +++

put /data/local/

userinit.sh

or /sd-ext or /etc/initd.d/06mount

#!/system/bin/sh

# check data

if [ -e /dev/block/mmcblk0p2 ];

busybox mount -t yaffs2 /dev/block/mmcblk0p2 /data

then

echo "data is ok";

fi;

exit

fix chmod 775 userinit.sh

reboot

+++++++

OR

in file /etc/initd.d/06mount

#!/system/bin/sh

#

# mount ext4 partition from sd card

BB="logwrapper busybox";

if [ "$SD_EXT_DIRECTORY" = "" ];

then

SD_EXT_DIRECTORY=

/emmc

/sd-ext;

fi;

# find SD Card

for MMC_NUM in `seq 0 9`;

do

MMC_TYPE=`cat /sys/block/mmcblk$MMC_NUM/device/type`

if [ "$MMC_TYPE" = "SD" ];

then

SDCARD=/dev/block/mmcblk$MMC_NUM

break

fi

done

if [ -b "$SDCARD" ];

then

# find sd-ext partition by label

PARTITIONS=`cat /proc/partitions|grep mmcblk$MMC_NUM|grep -v "mmcblk$MMC_NUM$"|awk '{print $4}'`

for PARTITION in $PARTITIONS

do

LABEL=`e2label /dev/block/$PARTITION`

if [ "$LABEL" = "sd-ext" ];

then

SD_EXT_PART=/dev/block/$PARTITION

break

fi

done

if [ -b "$SD_EXT_PART" ];

then

log -p i -t mountsd "Checking filesystems..";

# fsck the sdcard filesystem first

if [ -x `which e2fsck` ];

then

e2fsck -y $SD_EXT_PART;e2fsk_exitcode=$?

else

echo "executable e2fsck not found, assuming no filesystem errors"

e2fsk_exitcode=0

fi

# set property with exit code in case an error occurs

setprop cm.e2fsck.errors $e2fsk_exitcode;

if [ "$e2fsk_exitcode" -lt 2 ];

then

# mount and set perms

$BB mount -o noatime,barrier=1,data=ordered,noauto_da_alloc -t ext4 $SD_EXT_PART $SD_EXT_DIRECTORY;

if [ "$?" = 0 ];

then

$BB chown 1000:1000 $SD_EXT_DIRECTORY;

$BB chmod 771 $SD_EXT_DIRECTORY;

log -p i -t mountsd "$SD_EXT_DIRECTORY successfully mounted";

else

log -p e -t mountsd "Unable to mount filesystem for $SD_EXT_DIRECTORY!";

fi

else

log -p e -t mountsd "Unable to repair filesystem, disabling apps2sd";

fi

fi

fi
[Captivate Android Development] techmik67:
latest build attempt:

Notice file: external/sqlite/dist/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib/libsqlite.so.txt
make: *** No rule to make target `device/samsung/captivate/init.aries.rc', needed by `out/target/product/captivate/recovery/root/init.aries.rc'. Stop.
make: *** Waiting for unfinished jobs....
Notice file: external/sqlite/android/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib/libsqlite3_android.a.txt
Note: build/tools/signapk/SignApk.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
22 warnings
[Captivate Android Development] cchant:
Let us know your experience with this
[Captivate Android Development] My20:
give touches, I work with linux
[Captivate Android Development] cchant:
Something is wrong with the repo and it isn't downloading correctly
[Captivate Android Development] cchant:
I may try your script later. Thanks
[Captivate Android Development] techmik67:
I did the bold and now my storage page under settings says:

SDCARD

Total 14.85GB

Available 11.85GB

Internal Storage

went from 0.00b total and 0.00b available to:

Total 1.85GB

Available 1.42GB

Internal storage: /mnt/emmc

Total space 13.03GB

Available space 9.88GB

Great, right? except it doesnt hold on reboot... gotta do it again.... also fc's start popping up outta nowhere.... maybe i'll try the 2nd command, with yaffs....
[Captivate Android Development] cchant:
This didn't resolve the issue for me. I can navigate both internal and external cards with root explorer but can not install apps to internal sd and it loses on reboot
[Captivate Android Development] techmik67:
ok, pulled the tibu apk and dropped it in /app inside the gapps.zip and *poof* i got tibu. i then used "mount -t ext4 /dev/block/mmcblk0p2 /data" and it recognized my 1.5GB free app storage space, so i restored 200 apps with tibu (no data). most fc'ed on opening. upon reboot, they all left.... i assume if i could actually get everything to install right and then i moved them to /system/app/ instead of /data/app/..... hmmmm.....

edit: btw - i am ALWAYS in "emergency calls only" mode. I restored my imei and added apn... stilll -101 signal strength on unknown network
[Captivate Android Development] aqtrans:
Thanks for this! I modified it for ext4 (what my /data is formatted as) and tossed it into 06mount, and it's worked 3 reboots so far. My /data init.d script wasn't clicking on every reboot.

I attached the exact script I'm using, in case anyone wants to try it. :)
[Captivate Android Development] KCutrer1:
Edit: Never mind. Please Remove
[Captivate Android Development] cchant:
Did you run efsbackup.zip before you flashed the initial zip?
[Captivate Android Development] TheEscapist:
I heard tibu has issues with gingerbread, so the force closes are probably from that. And try mounting data as yaffs2.

Also, have you tried choosing network operator? Settings, wireless and network, bottom option.

Edit: actually, are you force mounting data on every reboot?
[Captivate Android Development] TheEscapist:
I fixed my sms problem, but somehow broke my wifi. *shrugs* I think I can fix it though. :D
[Captivate Android Development] cchant:
I never got my sms to work. Let me know if you get it fixed and I'll try it tomorrow when I get off work.
[Captivate Android Development] TheEscapist:
I had it working, but my wifi wasn't working, so I reflashed the kernel, which still broke wifi and my sms. Gonna **** with it some more.
[Captivate Android Development] techmik67:
Last few build attempts the kernel builds but wireless is borked ....... stoill cant build the rom....
[Captivate Android Development] TheEscapist:
Yeah, that's what I thought. Says it can't load the wifi driver. I also noticed that kernels are .5mb smaller. Makes me think that since codeworkx changed over the boardconfig, he broke wifi. Anyone want to try building an i9000 kernel and see if that fixes wifi?

And there's a fix on the cm forums.

EDIT: Codeworkx just added mainline changes, looks like the flac project is fixed. Try repo syncing and rebuilding.
[Captivate Android Development] junktzu:
Are you guys using the captivate or i9000 ROM? I just tried building the captivate version and it failed.
[Captivate Android Development] TheEscapist:
Did it fail on the flac project? If so, just sync and rebuild.

And were doing the i9000 + captivate kernel. Captivate kernel seems to have broken wifi though, if anyone wants to check with an i9000 kernel to see if it's got wifi working, that would be great.
[Captivate Android Development] cchant:
All my testing was with i9000 rom captivate kernel. No wifi issues besides what I believe to be wifi sleep death.
[Captivate Android Development] TheEscapist:
How old is your kernel? Only in the last day or so, has wifi broken for me. If it's a couple days old, could you pm me the tar?
[Captivate Android Development] cchant:
I think I built it on the 29th of january. It'll have to be tomorrow because I am at work until 7 am tomorrow
[Captivate Android Development] TheEscapist:
Yeah, only kernels built today, maybe late yesterday appear to be broken. Looks like it's a config bug, as it says the driver isn't loaded. And that's fine, I haven't done much work on it today.
[Captivate Android Development] nkrick:
If you have not seen, there is an official SGH-I987 thread on the CM forum now. No maintainers listed. It could probably SGH-I987/986 since the hardware is identical.

http://forum.cyanogenmod.com/topic/15169-sgh-i897-cm7-work-in-progress/

Also, has anyone working on this contacted gdanko? He was working on CM6.1 & AOSP for the Captivate back in Oct/Nov. He made some kernel contributions to the i9000 that allowed them to release the CM6.1 beta I believe. Without his help they were stuck on something. He got stuck on getting the Captivate working because he had no 2.2 Captivate source to work on. Now that both Rogers and Armani source code is available, his kernel skills could help you get the CM 7 for the Captivate going.
[Captivate Android Development] techmik67:
I have one of the last versions before wifi got borked tarred up from very late 1/30 or early 1/31 and it was working ok with the fixes already discussed.

Also, i have been using captivate rom and captivate kernel.....
[Captivate Android Development] TheEscapist:
Yeah, it's something to do with the new config options, I'll dig through it at some point.

And really? I was under the impression that the cap rom was broken.
[Captivate Android Development] junktzu:
I might have one made from a few days ago. Let me check...
[Captivate Android Development] techmik67:
The ones i built before the build problems, dated 1/31, for captivate, work like this:

flash the tarred captivate zImage.

Boot to cwm 3.0. install from sdcard "20110131-captivate-initial.zip" built from the release tools.

Do the fixes previously discussed (vold.fstab, and i made BOTH those files from the thread... (userinit.sh and 06mount). Still nothing holds on reboot).

Wifi worked, sound worked, fixed swapped sdcards.

Installed apk of rootexplorer.

Use root explorer to copy apk to /system/app (it holds on reboot)

**use root explorer to go to build.prop and change "ro.product.device" from captivate to galaxys (if you don't you get an error when flashing the OTHER .zip, NOT initial.zip)**

copy new apks from /data/app to /system/app

just couldnt get data to stay on reboot and when i used your code to get internal storage to appear, many fc's
[Captivate Android Development] TheEscapist:
Did you ever fix the network issue? And, does your sms work?
[Captivate Android Development] techmik67:
this was one of the last ones BEFORE wifi got borked..... but i have NEVER been able to register on att network
[Captivate Android Development] TheEscapist:
Hmm, that's odd. The worst part about all this is the fact that this just shows how unstable and unready it is, which means we still got a long wait for a real release.
[Captivate Android Development] cchant:
Maybe the newly released source will speed things up a bit
[Captivate Android Development] TheEscapist:
Only if we get a real captivate dev.
[Captivate Android Development] Rikusaki:
They know they'll get donations for doing this. This is huge.

$200 to the first dev to port CM7 over to the Captivate! :p:p
[Captivate Android Development] TheEscapist:
I would gladly donate to a port, even if it was just a reorientation of the i9000 version.
[Captivate Android Development] bfgarzilla9k:
Why on earth hasn't this bounty been started yet?! Somebody needs to get on this like, now. First to port CM7 to Captivate? Yeah. I'd donate.
[Captivate Android Development] techmik67:
just tried the fix from cm7 weblink... new error on make is:

No rule to make target `device/samsung/captivate/init.aries.rc', needed by `out/target/product/captivate/recovery/root/init.aries.rc' . Stop
[Captivate Android Development] TheEscapist:
Codeworkx already fixed the repo, so revert back, repo sync and you should be good.
[Captivate Android Development] cchant:
Has any one else tested this yet?
[Captivate Android Development] TheEscapist:
I will tonight after I get my gapps flashed. I got my wifi and my sms working using aq's build, I'll pm you the link.
[Captivate Android Development] KCutrer1:
Alright sounds good
[Captivate Android Development] techmik67:
building a new captivate kernel to try it on, tho i am still using my captivate rom from early monday that worked... repo sync-ed and still get the same error on cap rom build
[Captivate Android Development] cchant:
Thanks. Any idea what was causing sms to break?
[Captivate Android Development] techmik67:
feel free to send it this way too... =P

ok, still cant rebuild cap rom. Using the initial.zip from 1/31

flashed my tar-ed kernel from same day and applied aqtrans fix and vold.fstab fix.

wifi working but i still cant register on att network... not even letting me save apn at the moment....

aqtrans fixed 06mount works. data retained on reboot....
[Captivate Android Development] cchant:
@TheEscapist how's your battery life been?
[Captivate Android Development] TheEscapist:
Not amazing, by any means. 79% after almost three hours. Of course, my battery isn't calibrated, so i need to do that as well.
[Captivate Android Development] cchant:
I now have /data mounting fixed and incoming SMS fixed but I can't send SMS. When I try to update smsc in *#*#4636#*#* it gives me an update error.

/data mounting has stuck through several reboots so far
[Captivate Android Development] TheEscapist:
I could never update through there. Flash back to stock, there is an option in the stock mms app tochsnge smsc.
[Captivate Android Development] cchant:
Think installing stock SMS app would let me set it in cm7?
[Captivate Android Development] TheEscapist:
I tried before, it wouldn't install. Probably depends on the TW framework. Sorry man.
[Captivate Android Development] cchant:
Thanks I'm searching different ways. Flashing back to stock then flashing back to CM7 still doesn't fix outgoing SMS
[Captivate Android Development] TheEscapist:
No, because your smsc is stored on your sim card. But, the samsung mms has an option to change it that actually works. Flash to stock, go to the samsung messaging app, go to options, and there should be an option that lets you change your mesage center number.
[Captivate Android Development] cchant:
Thanks I'll try that
[Captivate Android Development] cchant:
That worked. I guess I was making everything more complicated than it had to be.
[Captivate Android Development] TheEscapist:
Awesome. :D
[Captivate Android Development] cchant:
Well after running this the past few hours I have had only one crash that I think is due to wifi sleep death.

I would love for the camera to be fixed.
[Captivate Android Development] TheEscapist:
I've had a couple of random reboots, but nothing I can't deal with. Maybe two today, I think.

And yeah, but it's good enough for me right now.
[Captivate Android Development] SweetwaterBurns:
Quick question for those that have been here for a while, but do you guys use the otapackage build option or use odin. I'm still kind of half assedly looking (damn kids distracting me) for flashing steps since I finally convinced my system to build the latest source...
[Captivate Android Development] TheEscapist:
I use odin to flash the kernel, and then flash the inital zip. The initial zip requires CWM3, so you must have the kernel flashed first. Steps:

1. tar kernel using tar -H ustar -c zImage > zImage.tar in /kernel/samsung/2.6.35/arch/arm/boot

2. Setup initial zip using either intial_captivate or initial_galaxys depending on what build script i used

3. flash kernel

4. flash initial zip
[Captivate Android Development] techmik67:
Latest error on build:

make: *** No rule to make target `device/samsung/captivate/init.aries.rc', needed by `out/target/product/captivate/recovery/root/init.aries.rc'. Stop.
make: *** Waiting for unfinished jobs....
[Captivate Android Development] uberushaximus:
Same error when building, CM7 galaxy s builds fine though.
[Captivate Android Development] KCutrer1:
Hey guys I was wondering what exactly you did to make sure /data stuck through a reboot? I dl'ed the 06mount.txt, then renamed it to 06mount and pushed to /etc/init.d which after a reboot showed internal storage existed, but every reboot I'm greeted by the android setup process.

Edit: Misread what was going on in the post. Going to try something else.
[Captivate Android Development] cchant:
Rename it to 06mount.sh then go into recovery and wipe data reboot into recovery and go to mounts and mount data there and reboot system. Try that
[Captivate Android Development] He4dShOt:
After the first flash, shall we use ota packages?
[Captivate Android Development] cchant:
after you flash initial zip reboot system and let it fully load in to CM7 then reboot in to recovery and flash SGS update zip or captivate update zip depending on what you built
[Captivate Android Development] He4dShOt:
I meant when we are already on CM7. We have to always use the initial?
[Captivate Android Development] cchant:
In cm6 once you already had it installed you could apply updates without flashing the initial zip. I assume it is the same on cm7 but not sure
[Captivate Android Development] cchant:
To those that have this installed, is your wifi slow? Mine is much slower than 3G
[Captivate Android Development] techmik67:
Fresh download and repo sync this morning.... same make error......
[Captivate Android Development] techmik67:
"Your simcard does not allow a connection to this network"

That's the error i get with my latest kernel build from today and a rom built 1/31. Data works over wifi. Sound works. File Manager shows the correct sdcard. Data holds on reboot......
[Captivate Android Development] techmik67:
My wifi is just like usual.....
[Captivate Android Development] SweetwaterBurns:
I was able to get it to build by copying all the .rc files from device/samsung/captivate/initramfs/data to device/samsung/captivate you then have to copy s3c-keypad.kl from device/samsung/crespo to device/samsung/captivate as well.
[Captivate Android Development] cchant:
CyanogenMOD forums have a test build all packed up ready to go

http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110203/
[Captivate Android Development] uberushaximus:
Haha, the same day I build a rom there's a prebuilt one out, awesome.
[Captivate Android Development] techmik67:
That worked, thanks...... build almost complete.....

The rom there looks like it is built for i9000 and i have been trying to use only captivate kernel and rom builds......
[Captivate Android Development] cchant:
In the future we may have to use i9000 roms and kernel until someone picks up development for the captivate.
[Captivate Android Development] Squeak22:
There really isn't a reason to have a captivate specific version at this point. Bluetooth, Wifi, and headphones all work fine now with i9k kernels.
[Captivate Android Development] cchant:
I agree just pointing out that there are no developers working on the captivate specifically
[Captivate Android Development] techmik67:
All the same, good fresh build an hour ago.... here's the problem.... that error above (the quote) is what i get when i try to register on att network after i restore my efs manually. This build, i used the efs backup tool, and when i try to "search available network providers", all it finds is tmobile..... apn is set correctly and so is my imei... it sees my phone #, unknown network -105 dBm signal strength.....
[Captivate Android Development] fykick:
Well one reason I'd prefer a captivate version or some help on this is because after it boots with the i9000 kernel i'm presented with the typical problems of an i9000 kernel on a captivate (autorotation is off...etc) ...and i've tried to odin a few kernels already and none of them boot with cm7 except the initial one at the link.

So are there any kernels I can odin/flash with this that will fix all this?

Thanks
[Captivate Android Development] KCutrer1:
Never was able to get data to stay through a reboot :(
[Captivate Android Development] techmik67:
It did on older rom build, not on this 1 for me either......
[Captivate Android Development] SweetwaterBurns:
I'm going to try digging in to the source and initrd files this weekend. It's been a few years since my linux-from-scratch days, but it should be like riding a bike, right? Here's to hoping they don't need me at work.
[Captivate Android Development] KCutrer1:
Good luck!
[Captivate Android Development] Squeak22:
No, there isn't yet. All I'm saying is doing a reorient kernel to fix these small issues is much easier than trying to put together an entirely new kernel for the captivate.

Once someone takes the coolya/codeworkxx kernel and ports in xcalibur's fixes, it should work great.
[Captivate Android Development] mnjm9b:
Oh yes....if you keep pushing that square peg into the round hole it will eventually go in right.... that's easier than making a round peg that just fits...(sorry for the sarcasm)
[Captivate Android Development] ademejia:
i9000 cm7

im using the i9000 cm7 that was posted today my head set logic is backwards do you guys have a modified kernel that will work will i9000 cm7 rom.
[Captivate Android Development] insaneturbo13:
not yet, ytt3r is working on it, he will prob make progress on it tomorrow,
[Captivate Android Development] junktzu:
Has anyone tested this ROM with a captivate kernel?
[Captivate Android Development] insaneturbo13:
it wont work like that. you have to use a cm7 kernel for a cm7 rom. you will have to wait for someone to reorient then one they have. or build a new one :)
[Captivate Android Development] junktzu:
Yes I understand that, I was asking if anyone compiled a captivate kernel from the CM7 source and tried it with what codeworkx and coolya released.
[Captivate Android Development] insaneturbo13:
Ytt3r is working on the kernel
[Captivate Android Development] Squeak22:
If you shave off the square parts to make it round, it fits just fine!
[Captivate Android Development] BTTNext:
Any updates?
[Captivate Android Development] h8rift:
also, FYI. a way to temporarily get around the headset logic is:

http://code.google.com/p/toggleheadset/

Have your apps to install on external. Install this .apk. Go to Applications -> Toggle Headset Widget -> Tell it to move to phone.

Add widget on desktop. Press once and it should be up and running. :D

Thanks!

-h8
[Captivate Android Development] insaneturbo13:
YOU DOUCHEBAG! where were you last night with that info! i could have used that and i wouldnt have had to taken it off so soon :(

lol :p
[Captivate Android Development] h8rift:
LOL. I'm feelin' the love here!

thats the way i got around it when i put codeworkx beta build on my captivate. :P
[Captivate Android Development] insaneturbo13:
Well. Thanks for posting it. Will help in the future anyway! Haha
[Captivate Android Development] h8rift:
Also, FYI.

Not saying there aren't other issues with the kernels you are flashing.....but the kernel has to have the CM7 initramfs in it to even THINK about booting.
[Captivate Android Development] KCutrer1:
How exactly did you use this? There is no 06mount in /etc/init.d. There is 06mountdl. Did you copy and past what was in that text file into 06mountdl?
[Captivate Android Development] aqtrans:
In my build from a few days ago there was no 06mountdl, must be a new addition...If the /data fix is still needed (from what I've seen on the Cmod forums, if you install it correctly, being sure to mount and format the required partitions, /data shouldn't be a problem), might want to try renaming my 06mount to 07mount.
[Captivate Android Development] KCutrer1:
Hmm that's weird. The build I'm running I compiled last night, along with compiling the kernel. I'm pretty sure I followed the install instructions correctly also. Well regardless it looks as though renaming it to 07mount fixed the issue, and hopefully it'll hold until a more stable release comes out and fixes the issue altogether. Thanks for helping!
[Captivate Android Development] junktzu:
I'm sorry if this is a newb question but how are you getting the 07mount file into the etc/init.d folder? Root explorer can't seem to change the permissions to R/W and adb can't see the device.
[Captivate Android Development] KCutrer1:
Strange mine was already mounted R/W. Not sure why yours won't change.