yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] whiteguypl:
The information needed to flash it already exists. If you dont know where it is or how to build from source you should not even attempt this.
[Captivate Android Development] TheEscapist:
We aren't allowed to release pre-built zips, as per codeworkx's request. Instructions on how to build it are on the CM forums. Captivate specific fixes are posted in here.

Basically this. This is still pretty alpha level stuff.
[Captivate Android Development] cchant:
Does this solve the issue with being able to install apps to the internal SD? This and incoming sMS are broke for me
[Captivate Android Development] techmik67:
Building latest captivate rom and fixed vold.stab and headset in kernel build..... will flash when done.....
[Captivate Android Development] TheBassman369:
What if you all were to get a Captivate build of CM7 working?
[Captivate Android Development] junktzu:
Who's repo are you using? TheEscapist's or Coolya's?
[Captivate Android Development] techmik67:
Coolya's with the fixes to vold and headset from TheEscapist.....
[Captivate Android Development] cchant:
Let us know if the vold.stab fixes internal SD app installation
[Captivate Android Development] techmik67:
latest issue..... cant restore/install appps cause internal storage total listed at 0.00mb and 0.00mb available. internal storage: /mnt/emmc is fine and has plenty of space.
[Captivate Android Development] TheEscapist:
My repo is ****ed, so i'll just post my fixes in here. I'll make a post in a bit. Once we get all the fixes, i'll try and get it into coolyas repo. We may end up having to do what we did with cm 6 though, and i'll reorient and compile those kernels for you guys after a proper release.

Internal storage is NOT fixed by the vold.fstab fix. Apparently /data isn't mounted after a reboot, which is probably why it's showing up as 0b. When I reflash it today, i'll check to see if that had something to do with it. If you want to install apps, go to cyanogenmod settings > applications > install location and change it to external.

I'm also looking for the orientation driver so that I can fix that.

Most critical for me right now is the incoming sms issue, though. Cchant and I are the only ones with it, apparently. Cchant, you wouldn't happen to be on rogers, would you?
[Captivate Android Development] cchant:
I'll look here in a bit but I thought I saw a post where they had modified a script to force to mount /data at reboot.

I'm not on Rogers I'm on AT&T. A weird thing happened last night. I left wifi on to test if wifi sleep was fixed or not. Well after a bit I saw the phone reset. I just left it because I was busy doing something else and a few minutes later I received 5 or 6 SMS I had my wife send me as I was trying to fix the SMS issue. Not sure what happened but it started working. Before that happened I was trying find if there was a way to modify the SMS message center number. I was thinking that it had to be manually set since we have to manually set APN for MMS and data to work, but I wasn't able to find where that can be edited
[Captivate Android Development] TheEscapist:
Okay, I'll look for that.

And my smsc was set fine. You can check it by putting *#*#4636#*#* into the dialer. I'll try and crash my phone, maybe I'll get lucky.:rolleyes:
[Captivate Android Development] cchant:
Here's the post to get data mounted on reboot
[Captivate Android Development] TheEscapist:
LIST OF CAPTIVATE SPECIFIC ISSUES/FIXES​

Issue: Headset logic is reversed

Status: Fixed

How to Fix: Replace /path/to/cm/kernel/samsung/2.6.35/drivers/misc/sec_jack.c with the one attached (rename to sec_jack.c). You must build a captivate kernel for the fix to work.

Issue: Internal and external sdcards are reversed.

Status: Fixed

How to Fix: Replace /etc/vold.fstab on your phone with the one attached(rename it to vold.fstab), then reboot. UNTESTED: There is a vold.fstab under device/samsung/captivate, you could probably just replace it there and not have to do it after.

Issue: Orientation sensor is broke under captivate kernels

Status: Unfixed - (kind of) being worked on

Issue: Data doesn't work out of the box

Status: Fixed

How to Fix: You have to manually add an apn for AT&T or Rogers. Just google (carrier name) APN.

If anyone finds more Captivate specific problems, post them here, I'll add them. If you guys want me to also add non-captivate issues and fixes, I can do that too.
[Captivate Android Development] cchant:
The main things that keep this from being "daily use" are the Camera being broke and internal storage not being mounted correctly. I might be able to live without the camera though :P

On CM forums it seems a few of the guys are working on the storage mount but it doesn't appear fixed at the moment.

Another issue I've found is that newly installed apps don't appear in the widget picker.
[Captivate Android Development] TheEscapist:
In the 4 months I've had this phone, I've only used the camera once, and that was to take pictures of my girlfriends cat, so camera is a non-issue. Apps install fine once you change the install location to external, so again non-issue for me.

I think I'm one of those guys you were talking about. :rolleyes:

And that's probably related to the internal storage problem. Do they show up after a reboot, or not at all?

EDIT: You wouldn't happen to have a copy of that /data mounting script, would you? I need to charge my phone before I can flash it and check under mount, and I don't feel like digging through tons of scripts just to find where data is mounted after the first boot. :rolleyes:
[Captivate Android Development] cchant:
any time I reboot the phone it's as if it's the first boot. Any changes I made to settings and apps downloaded etc do not save
[Captivate Android Development] TheEscapist:
Almost certainly connected to /data not being mounted. /data is where your downloaded apps are saved, so it makes sense that it doesn't show up.

Unless of course you are manually mounting data, in which case it's a different problem that we have to track down.
[Captivate Android Development] cchant:
I haven't figured out how to mount to data. In a post by aqtrans he said he was able to get /data to mount on reboot by adding the command to mount ./data in an init.d script but I haven't quite tracked down what he did yet
[Captivate Android Development] techmik67:
+1 x 1000 on the /data mounting script.... that would REALLY help....

=)
[Captivate Android Development] cchant:
I'm trying to figure it out but it's slow going. I have a 4 month old that likes attention :P

check under out/target/product/galaxys/system/etc/init.d

05mountsd could be of use
[Captivate Android Development] TheEscapist:
Man, I love being a 16 year old with no school for a week. :D

Anyway, looks like /cache is /dev/block/mtdblock3 and /datadata is /dev/block/mtdblock6. Maybe if we wrote a script to mount those two?

Also, I bet we're totally overlooking something here, like the commands actually just mount /data or something easy. :o
[Captivate Android Development] cchant:
From aqtrans post it seems all he did was add a command to a script.
[Captivate Android Development] TheEscapist:
Yeah, I'm betting everything is set up, you just have to call a command to mount the data partition. I just don't know what it is.

Also, your sms is fully working now, correct? Did you back up and restore your /efs at all? I'm just grasping at straws here, trying to figure out why I'm the only one with this problem. :(
[Captivate Android Development] cchant:
it was working until I reboot my phone now it's broke again. I did back up the /efs but I thought the initial zip restores it on it's own. Not sure though
[Captivate Android Development] TheEscapist:
Weird. :l And it's supposed, but It doesn't really work, as /sdcard doesn't mount properly for us. I know I have (at least) an improper IMEI.
[Captivate Android Development] He4dShOt:
How can I install google apps?
[Captivate Android Development] TheEscapist:
Flash this.

For future reference, gapps zips are hosted on http://goo-inside.me/google-apps/

Also, is your incoming sms working?
[Captivate Android Development] He4dShOt:
i get stuck on the droid... :(
[Captivate Android Development] He4dShOt:
W/SetupWizard( 219): Not continuing because we're waiting for GLS to finish clearing the old accounts

...wtf??
[Captivate Android Development] TheEscapist:
As in bootlooping?

And that's odd, worked fine for me.
[Captivate Android Development] He4dShOt:
on the green android that you have to touch to begin the wizard...
[Captivate Android Development] cchant:
I get that too on every reboot. It has to do with the internal sd not mounting on boot
[Captivate Android Development] TheEscapist:
Once aqtrans comes back on, we can ask him for the script. I'm currently trying to get the orientation sensor working.
[Captivate Android Development] jai134:
I'm trying to build for my GT-I9000. Built nicely yesterday can't do it today. Gets this (in Swedish):

make: *** Ingen regel för att skapa målet "out/target/product/galaxys/obj/lib/libFLAC.so", som behövs till "out/target/product/galaxys/obj/SHARED_LIBRARIES/libstagefright_intermediates/LINKED/libstagefright.so". Stannar.

Resynced an hour ago. I'm using instructions from Coolyas repo. ./build_galaxys.sh

Anyone who knows if there is something new I have to do to build?
[Captivate Android Development] cchant:
I'm getting the same issue on resync and rebuild
[Captivate Android Development] TheEscapist:
It's probably an issue on their side then. Of course, it would help if we could read the error. :p
[Captivate Android Development] zerojay:
For anyone wondering, the reason why I wasn't able to get into Download/Recovery with the buttons is because I have a Captivate with a faulty bootloader. Sent it back, getting a replacement. It ended up hard bricking (no response whatsoever when you attempt to turn it on). Back in 7-10 days. :)
[Captivate Android Development] TheEscapist:
Ahh, well, better luck next time. Hopefully it will be a bit more stable by then. :p

EDIT: Anyone know how to force make to use a custom config file? in .config, there's an option to use the orientation sensors that's commented out in the captivate version, but in the galaxys version. If i add those in the captivate version, and can get make to use those instead of the default config, we'll have orientation, just reversed. Then I can orient it properly.
[Captivate Android Development] mkurzum:
The cyanogen thread states you must have jpm or higher.

By flashing the rogers modem after all my steps I got 850 back, 2g/3g work perfectly

P.s: yes I did mean pit .512 in my earlier post
[Captivate Android Development] h8rift:
I stayed with the ji6 modem (didn't go to JPM first). Everything is working fine from a modem standpoint.

I also changed the updater script and build.prop to show its still an i897 :)
[Captivate Android Development] NiXXeD:
Usually staying with a captivate modem yields fuzzy/quiet call quality and/or FCs eventually.
[Captivate Android Development] h8rift:
Well, if it does I'll move forward from there. So far so good :)
[Captivate Android Development] newter55:
Deleted...irrelevant

Guess that answers my question glitter...lol
[Captivate Android Development] kamots:
alright i just flashed to stock :Dand am getting ready to flash the jg8 modem with odin, and after that i can just follow the instructions to install cm6 correct? or, do i need to get the jpm modem as well and flash that after jg8? just curious.
[Captivate Android Development] gtg465x:
The increased CPU score is only due to a bug. Some video codecs are not working correctly so Quadrant just skips video encoding/decoding tests and thinks they were completed in 0 seconds.
[Captivate Android Development] bedwa:
I tweeted on my twitter account my quad score cause it was OVER 2600. I would screenie as well, but my home key is still being funky even after flashing the new kernel

Will get link and edit post... brb.

http://bit.ly/cDV2BD

And mine did all the tests it's done in the past. It jumped from 1700 with the kitchen sink reoriented kernel and cognition (forget which one.)
[Captivate Android Development] kangi26:
I'm first!!

I hear the sound of trout headed your way!:D
[Captivate Android Development] newter55:
Thanks....I was wondering if it was right or another issue like incorrect results from the vibrant kernel...post will be edited

sent from my captivate disguised as an i9000 running cyanogen ;)
[Captivate Android Development] biggem001:
I cannot flash this..

i keep getting the error Assert Failed: getprop

My Steps:

Flash to sock (odin)

Flashed initial kernel (on i9000) page

Flash CM (FAIL)

I've even tried flashing with this kernel as well
[Captivate Android Development] xuzer:
I believe you have to flash jpm or newer before attempting cyanogen
[Captivate Android Development] tjsooley:
is anyone working on a captivate kernel for cyanogen that can user a captivate modem?

HSUPA rocks but battery life sucks and without a bell froyo modem it can be a pain n the ass to setup, and even after it is setup correctly signal is not as good as it is with the captivate modem.
[Captivate Android Development] biggem001:
flashed to JPM - installed initial kernel - still fail.

--

got it!
[Captivate Android Development] ademejia:
did you do nandroid back up of the i9000 rom, flash the cm kernel then do a date wipe then flash the cm rom. it worked for me im using captivate. then after you boot to cyanogenmod u want to flash the kernel from here.
[Captivate Android Development] smeltn:
man so excited to see this coming along. I can't wait to use CM on my Captivate!!
[Captivate Android Development] h8rift:
I flashed from Cog, flashed the initial, flashed CM, wipe, booted, then flashed re-orient kernel.

Kept my modem and all that good stuff.

Edit: also, I had to edit build.prop and updater script from i9000 to sgh-i897 for it to stop giving me assert errors.
[Captivate Android Development] biggem001:
anyone having a problem with swype?
[Captivate Android Development] provoked:
Just a quick question because I want to flash this when I get home. I am already on jpa I think... aka doc's rom. That would work with flashing kernel and doing the clear without starting from jf6?
[Captivate Android Development] newter55:
I have run many i9000 setups and find a different experience. Battery is great on many and my signal (actual strength..not bars showing as this can vary by rom) is as good as either of the other two captivates in the house which are on cap firmware and modems

And setup is just one added step of flashing jg8 before going to i9000

sent from my captivate disguised as an i9000 running cyanogen ;)
[Captivate Android Development] jai134:
Don't know the exact words but after make:*** it says "no rule to create target" and after libFLAC.so it says "needed by". Ends with "stopping".

Was that what you meant or did I missunderstand you?
[Captivate Android Development] aqtrans:
Oh sorry guys, here's the command I used to mount /data:

I put that in a file called 21whatever in /system/etc/init.d.
[Captivate Android Development] cchant:
20userinit ?
[Captivate Android Development] TheEscapist:
userinit looks like it just runs user scripts. I think he means he made a whole separate script.

Also, anyone know where aries_captivate_defconfig is so I can modify it to use the orientation sensor?
[Captivate Android Development] cchant:
05mountsd is the only thing in that directory that appears to have anything to do with mounting of SD cards. I'm looking at it now to see where I should plug it in

:crossfingers:

aries_captivate_defconfig in your system /android/system/kernel/samsung/2.6.35/arch/arm/configs

On the phone I'm not sure. I went back to stock so I could try to fix the SD mount issue. I need SMS so I'm flashing back and forth a bit
[Captivate Android Development] TheEscapist:
I just made my own script named 21mountdata, didn't work. There's a userinit script that must run self made scripts, look to see where that looks.
[Captivate Android Development] cchant:
I'm wondering if I was to plug in his code into that userinit script if that would do it. I'm going to try it.
[Captivate Android Development] KCutrer1:
Would one of you guys mind uploading the initial kernel (flashable through Odin)? I was able to compile the system.img etc. but for some reason compiling the kernel causes an error.
[Captivate Android Development] cchant:
you need to run the scripts in release tools
[Captivate Android Development] aqtrans:
Weird, did you try executing that script from a terminal to see if the script is working correctly? I had to format my /data from recovery once to get it to mount at all, even with the script.
[Captivate Android Development] cchant:
Oh so you created your own script?
[Captivate Android Development] KCutrer1:
Really? For the initial kernel?
[Captivate Android Development] TheEscapist:
Yeah, just made me bootloop though. Once I formated data in recovery, it ket me mount it there, which is an improvement. I just think I have to edit my script a little.

Also, new captivate kernels should have orientation now, just reversed (like the i9000 kernel). I'm going to try and reorient it at some point. I'll post fixes here.
[Captivate Android Development] TheEscapist:
How are you doing it?
[Captivate Android Development] KCutrer1:
According to Coolya's README. I was able to build the system.img, boot.img, ramdisk.img etc, but the next step is "PREPARE:

cd ~/android/system/kernel/samsung/2.6.35

./build_galaxys.sh clean

BUILD FOR GALAXYS:

./build_galaxys.sh

Note: Initramfs will be taken from device/samsung/galaxys/initramfs

BUILD FOR CAPTIVATE:

./build_captivate.sh

Note: Initramfs will be taken from device/samsung/captivate/initramfs"

But it fails while doing this
[Captivate Android Development] TheEscapist:
do ./build_captivate.sh clean instead.

Also, what errors are you getting?
[Captivate Android Development] cchant:
I just made my own script as well. Empty with only aq's code in there. I didn't get stuck in bootloop but I could only mount the sdcard in recovery not in CM7
[Captivate Android Development] KCutrer1:
This is the error I recieve while running "./build_captivate.sh":

/bin/sh: ../../../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: not found

make[1]: *** [kernel/bounds.s] Error 127

make: *** [prepare0] Error 2
[Captivate Android Development] TheEscapist:
Do you have gcc installed?

After formatting /data in recovery, I could mount it there, and in cm7 using mount -t ext4 /dev/block/mmcblk0p2 /data. I just can't get it to run as a start up script. I'll keep looking at it.
[Captivate Android Development] KCutrer1:
Yeah I just ran "sudo apt-get install gcc" and it reported back saying I already have the newest gcc installed.
[Captivate Android Development] TheEscapist:
And you have everything else needed installed?

Also, I can confirm that the rotation sensor is working in the latest Captivate kernel, it's reversed.
[Captivate Android Development] KCutrer1:
As far as I know yeah. In the readme the first step is preparation and it looks like that is supposed to install all the necessary things.
[Captivate Android Development] junktzu:
Hey I just wanted to thank you guys for work on this! Anyways I'm going to implement the fixes you guys workout today and rebuild the ROM/Kernel tonight when I get home from work. One question though; is it normal for a ROM build to take a couple hours? I'm building mine with an Ubuntu installation running inside of VirtualBox but I wouldn't be opposed to creating a dual boot system if it sped up the building process.
[Captivate Android Development] TheEscapist:
Yeah, then I don't know. Looks like there is somthing wrong with your gcc.

Hey, say thanks to the devs, not us. ;) Full rom can take up to an hour for me, so yeah a few hours in a vm isn't unrealistic. Kernel usually only takes a few minutes though.
[Captivate Android Development] cchant:
It takes just over an hour for me to build the ROM on a dual boot of Ubuntu. Kernel is minutes
[Captivate Android Development] junktzu:
Of course the dev's get thanks too but I was getting the feeling that CM7 for the cap was DOA until i found this thread ;)

Anyways from what you're saying it would make sense to setup a dual boot with Ubuntu. Two hours+ is a long time to wait!
[Captivate Android Development] TheEscapist:
repo sync and build over night.

Besides, once you build it once, you only need to rebuild it whenever something changes. Kernel changes a lot more, but that compiles in like, 5 minutes, max.
[Captivate Android Development] cchant:
any more luck getting internal SD mounted correctly? I've tried creating my own script and modifying 05sdmounts in etc/init.d but no luck
[Captivate Android Development] TheEscapist:
You mean /data, or the actual internal storage?

I've been all over the place in terms of things that I've been trying to fix. I think we can fix the /data mounting easily, we just have to get the right script. Internal storage I haven't looked at too closely. And I have an idea on how to fix the orientation.

Just this damn sms issue. :mad:
[Captivate Android Development] cchant:
I mean /data. I need /data to work so rebooting doesn't wipe out apps etc that I've installed.

I'm not sure on SMS either. Mine has only worked that one time and I didn't do anything it just started working then quit when I rebooted

EDIT:

Have you taken a look at init.rc? After some research it sounds like init.rc runs scripts at boot or early init process.
[Captivate Android Development] TheEscapist:
Okay. init.rc (last i checked) is a file that sets configuration options at boot. I really think that we just need to put a mount script in /etc/init.d. We just need to get the script working. I'll concentrate on that first.

And yeah. It seems like we are the only ones with the issue. Are you coming from stock when you flash it?
[Captivate Android Development] cchant:
Yes I am coming from stock JH7.

I was taking a look at 20userinit again in system/etc/init.d in the comments it says "call a userinit.sh script if it's present on the sdcard"

I'm thinking we create a script name userinit.sh and put in the code aqtrans gave us and it should run that script on boot. I'm going to try that shortly
[Captivate Android Development] TheEscapist:
Got to make sure sdcard if properly mounted first.

And is your imei correct? Could that possibly have any effect on sms?
[Captivate Android Development] cchant:
My IMEI is correct so don't think that has any effect on sms.

Still lost on the /data mount at this point. I'll keep trying.

In 20userinit it seems like it points to /system/bin for userinit.sh so I created a script and put the code to mount the sd card aqtrans gave us in there. the phone boots and I can mount /data in recovery but not in CM7. It shows in the storage section that the internal and external sd cards are there. Internal storage is still at 0.0gb. I tried to install apps and it wouldn't let me install to internal. Rebooting wipes all apps and changes done on external.
[Captivate Android Development] TheEscapist:
Damn. I'm totally grasping at straws at this point.

Make sure you can mount /data in cm using the terminal/sdb shell. Try something simple, like mount -t ext4 /dev/block/mmcblk0p2(typing this off memory, so it might be off) /data. If it mounts, then it's an issue with your script.
[Captivate Android Development] cchant:
I've tried that in terminal and when I check storage it gives me internal storage with 1.8GB

but once I try to install any apps or do anything really it goes into boot loop.
[Captivate Android Development] TheEscapist:
Wait, wait, You can get internal storage to report something other than 0b?

And hmm. Maybe try mounting as yaffs2.
[Captivate Android Development] cchant:
I run this command from the terminal emulator within CM7

mount -t ext4 -o rw,remount,nosuid,nodev,noatime,nodiratime,noauto_ da_alloc /dev/block/mmcblk0p2 /data

and it gives me internal storage but crashes and goes in to boot loop. I may try some more later. Got to take a break :P
[Captivate Android Development] aqtrans:
Have you tried formatting /data and trying to mount within CWM3, using the CWM menu, not via ADB?