yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] TheEscapist:
According to Codeworkx, there's an install script, which makes sense considering that it was marked as fixed on the google code page. Maybe we can use that.

Also, think he'll let us test with a Captivate? I'm actually really surprised they haven't released a beta. The rom itself seems stable, more stable than CM6.1B3 was. The actual install is more unstable than the rom right now.
[Captivate Android Development] cchant:
I haven't figured out the install script yet. I've been taking another path but it isn't working. He mentioned on another forum that those interested in testing to PM him or meet him in IRC. I asked him about testing for Captivate and he said they are not working on the Captivate specifically just i9000. I replied that I would still like to test i9000 ROM and kernel on the captivate but he never replied, so I don't know :P
[Captivate Android Development] aqtrans:
Hey guys, just compiled this myself and thought I'd share some things I discovered...

Firstly, there are some scripts in /releasetools to build OTA (Clockwork-mod flashable) packages. I ran efsbackup_galaxy.sh, initial_galaxys.sh, then ota_galaxys.sh, then copied and flashed the resulting zips in order, rebooting after flashing the initial zip.

I compiled the kernel using the Captivate config, but for some reason still had to apply the headphone logic fix to sec_jack.c.

On a sidenote: I compiled this on an x86 OS, not 64-bit like I thought was required.
[Captivate Android Development] cchant:
What did you do to fix the head phone logic?
[Captivate Android Development] KCutrer1:
Haha I know what you mean. I'm in a similar situation (18 year old on minimum income lol)
[Captivate Android Development] aqtrans:
I followed this:

https://github.com/xcaliburinhand/l...mmit/b2ca7bca0dcae9558464c2f7443ee81cece72da2

Except just commented out the IF statements.
[Captivate Android Development] TheEscapist:
I brick this phone, I'm out a phone for two weeks - a month. That, and my parents will kill me (despite me paying for both the phone and contract:rolleyes:).

Compiling it now. Thanks for finding/ pointing this out to us.:)

Edit: Seems to have broken a bunch of stuff. Wifi, for one. And, it didn't remove the headset icon from the notification bar. I'm betting it's something on my end though, so I'm going to do a rebuild and full reflash.
[Captivate Android Development] cchant:
Let me know how it goes. Wife is already pissed about being up so late and I work all day tomorrow
[Captivate Android Development] TheEscapist:
Can't get it to boot past the "kanged" screen. Going to odin back to stock, and try one more time.

Edit: No luck. Wifi breaks, and I still have that damned headset icon. To that guy who posted the fix, did it actually work for you?

Also, odining back to JI2 isn't working for me, probably PIT issues. Trying JF6 one click.
[Captivate Android Development] aqtrans:
Yeah adding that one line, excluding the IF statements, (or you could probably change the I897 variable to CONFIG_GALAXYS_CAPTIVATE or whatever they changed that to) to sec_jack.c worked for me. I just now reflashed it all after some crazy EFS problems, and have data, and correct headphone jack logic.
[Captivate Android Development] TheEscapist:
Ohhh, that's my problem. I added the if statements. I'll try again tomorrow. Does your incoming sms work?
[Captivate Android Development] ademejia:
is this for real i9000 cm7 ?

http://v.youku.com/v_show/id_XMjM5MTA3NzI4.html
[Captivate Android Development] votum:
My advice is wait lol.

I bricked mine with 6.1 somehow. It was bricked to the point of not even turning on though, would go into download mode maybe every 20 battery removals. I probably could have eventually got it flashed back to stock but I didn't feel like bothering with it.

Also, so CM7 is still in the works? Last I had heard was 6.1 was being skipped as they had the Nexus S source to work off for 7, but never saw a thread here about it, and haven't checked CM's site as they never update (which is fine, there's plenty here to keep me busy) Anybody have a link to the progress site, googlecode or something?
[Captivate Android Development] aqtrans:
Heh, so it seems like my data partition is being wiped on every reboot... >.<
[Captivate Android Development] cchant:
From codeworkx:

I've set up captivate now on coolya's git.

Now you should be able to build for captivate.

Follow the readme: https://github.com/coolya/android/blob/master/README
[Captivate Android Development] TheEscapist:
So, any one tried the captivate version of the rom?

What I'll probably do this morning before work is start digging through xcals commits and adding source to the captivate kernel, cause it's probably just a fork of the i9000 kernel.

Also, just wondering if it's just me, but did anyone get incoming sms working? I flashed back to stock, and got 5 messages in a row. :rollseyes:
[Captivate Android Development] cchant:
as of right now the repo is screwed up. I get an error when I try to resync. I mentioned it to codewordx so maybe he'll see it and fix it sometime today
[Captivate Android Development] TheEscapist:
the entire repo? That should get fixed soon if they plan on doing any work.

In the meantime (once I get out of bed -.-), i'll start digging through xcals commits. then we can just push through to the repo.
[Captivate Android Development] cchant:
This is the error

error.GitError: coolya/gingerbread_captivate_initramfs rev-list ('^5df584248032cf74d89b3a05ec5e539423e7c98b', 'HEAD', '--'): fatal: bad object 5df584248032cf74d89b3a05ec5e539423e7c98b

They must have hit a wrong button when submitting the commit :P

I imagine that if we're building the captivate build and things are setup correctly from their git that we shouldn't need any reorientation fix or headset logic. We'll see. I'm off to work for the next 24 hours but of course I'll be checking in
[Captivate Android Development] TheEscapist:
Working fine for me, that part of the project synced fine. I'm betting what they did was just forked the i9000 source, and didn't put in any Captivate specifics. Like I said, I'll start looking through.

Edit: Spoke to soon. Crashed right at the very end. :rolleyes:
[Captivate Android Development] zerojay:
I'm giving it a shot too. Middle of compiling right now.
[Captivate Android Development] TheEscapist:
Did your repo sync work? Or did you do that earlier?
[Captivate Android Development] zerojay:
I was able to sync the repo just fine. Got this error while compiling:

target StaticLib: libgtest_main (out/target/product/captivate/obj/STATIC_LIBRARIES/libgtest_main_intermediates/libgtest_main.a)

target thumb C++: libandroid_runtime <= frameworks/base/core/jni/android_database_SQLiteDatabase.cpp

frameworks/base/core/jni/android_database_SQLiteDatabase.cpp: In function 'void android::dbopen(JNIEnv*, _jobject*, _jstring*, jint)':

frameworks/base/core/jni/android_database_SQLiteDatabase.cpp:137: error: 'sqlite3_wal_autocheckpoint' was not declared in this scope

make: *** [out/target/product/captivate/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/android_database_SQLiteDatabase.o] Error 1

make: *** Waiting for unfinished jobs....
[Captivate Android Development] TheEscapist:
I still can't get it to sync the new captivate initramfs.

Looks like you're compiling the captivate rom, try doing the build_galaxys.sh. That one works fine for me. You can then just build the captivate rom, which is basically an i9000 kernel with proper button mapping.
[Captivate Android Development] zerojay:
Doing that. You meant build the Galaxy S rom and a Captivate kernel, right?
[Captivate Android Development] cchant:
According to codeworkx Try deleting device/samsung/captivate on your local machine and resync
[Captivate Android Development] zerojay:
I tried doing that. I get the same error I got previously when compiling both Galaxy S and Captivate. :/

Nevermind. Resynced again and I think I've gotten past it.
[Captivate Android Development] TheEscapist:
Yes.

Yeah, saw that.
[Captivate Android Development] TheEscapist:
Yeah, latest commit from codeworkx changed the sqllite library (which the make was failing on) to the cyanogenmod one, so I bet that had something to do with it.

Edit: Don't you love when the minute you start compiling, there is 10 new commits right after? Ah well. Gonna just work with what I've got and see if I can work the reorient fixes into the kernel.
[Captivate Android Development] zerojay:
Captivate ROM compiled. Moving on to Captivate kernel.

Anyone working on this, keep us all in the loop with your fixes/changes/whatever.

Kernel done... now to get this actually on my phone to try it out.

And I have no idea what to do to make this work.. anyone that's done this before have an idea?

I had to enter into the releasetools directory, make a copy of initial_galaxys.sh as initial_captivate.sh, edited the copy and changed product from galaxys to captivate. Saved it, ran initial_captivate.sh and it produced a cyanogenmod7-captivate.zip file.

Looks like the zip file has everything including the kernel. About to flash.. wish me luck!
[Captivate Android Development] cchant:
Keep us updated. I'm at work until tomorrow so won't be able to test til then
[Captivate Android Development] TheEscapist:
go /path/to/cm/kernel/samsung/2.6.35/arch/arm/boot and run tar -H ustar -c zImage > zImage.tar

then go to /path/to/cm/releasetools and open up initial_galaxys.sh At the top there should be product = galaxys or something similar, change it to captivate, and rename it to initial_captivate,sh. Run it. Copy the zip it spits out to your sdcard

Then flash the zImage.tar using odin, boot to recovery, and flash the initial-cyanogenmod7-whatever.zip.

I'm working on the captivate kernel, my git is at https://github.com/TheEscapistxda. If update your .repo to use my repo instead of coolyas for the kernel + releasetools, I'll be putting captivate specific stuff in it. Just got the headset logic fixed, so I'll push that.
[Captivate Android Development] zerojay:
I did everything except tarring up the kernel image. I noticed that the kernel appears to be a part of the zip file that the initial_captivate and ota_captivate scripts pushed out. Is the tarring still needed?
[Captivate Android Development] TheEscapist:
I don't know, to be honest. I do anyway, cause I'm coming from stock froyo, and need the CWM to flash it.

Also, anyone know how to push the local changes to my repo? I can't figure it out for the life of me. :rolleyes:
[Captivate Android Development] cchant:
You need to tar the kernel and flash it first with ODIN because CM7 needs clockworkmod 3.0 to flash it. CWM 3 is built in to the kernel.
[Captivate Android Development] zerojay:
do i need a PIT file for flashing the kernel with odin?
[Captivate Android Development] cchant:
Just flash the kernel. I didn't use a PIT File when I flashed mine
[Captivate Android Development] aqtrans:
This might be fixed in a later commit (maybe that boot.img one?), but my data partition wasn't being mounted on every boot, so I had to add the command to mount /data in an init.d script. Couldn't get my TiBu app-data to restore either :(
[Captivate Android Development] zerojay:
Ok, I flashed the kernel... not able to get into recovery to flash the ROM though.. phone boots up showing the Galaxy S I9000 Samsung screen with a large red KANGED over it.
[Captivate Android Development] TheEscapist:
you're holding down the key combo until you see that boot screen, right?
[Captivate Android Development] zerojay:
Yep, nothing comes up. Just freezes at KANGED.
[Captivate Android Development] :
Are you using the captivate key combo or the I9000 key combo? If I remember correctly, the I9000 combo is just voldown+power. I know its different. I'd look it up but bad service on mobile. Hope that helps.
[Captivate Android Development] cchant:
I think I read elsewhere that restoring with TiBu is screwed up on cm. Can't remember why
[Captivate Android Development] TheEscapist:
Odin back to stock, re sync, rebuild, and reflash. maybe you just had a bad build. Make sure you clean before rebuilding.
[Captivate Android Development] KCutrer1:
Hey guys maybe one of you could help me out. I decided to try and build CM7 from source, according to Coolya's readme, but while setting everything up it fails at this step:

repo init -u git://github.com/coolya/android.git

Typing this in results in this error:

Traceback (most recent call last):

File "/home/kyle/bin/repo", line 603, in <module>

main(sys.argv[1:])

File "/home/kyle/bin/repo", line 570, in main

_Init(args)

File "/home/kyle/bin/repo", line 184, in _Init

_CheckGitVersion()

File "/home/kyle/bin/repo", line 213, in _CheckGitVersion

proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)

File "/usr/lib/python2.6/subprocess.py", line 623, in __init__

errread, errwrite)

File "/usr/lib/python2.6/subprocess.py", line 1141, in _execute_child

raise child_exception

OSError: [Errno 2] No such file or directory

I'm sorry if this seems elementary to anybody, but I don't use Linux frequently (stick to Windows and OSX)
[Captivate Android Development] TheEscapist:
Is git installed?
[Captivate Android Development] TheEscapist:
Oh, and just wondering, has anyone been able to receive sms on CM? I can't seem to figure out why I can't receive them.
[Captivate Android Development] cchant:
I wasn't able to on the build I flashed yesterday. Hopefully tomorrow I'll have some time to play with it
[Captivate Android Development] TheEscapist:
Did you use the captivate build or the i9000 build?
[Captivate Android Development] aqtrans:
Sending and receiving texts are working fine for me. I'm using the Captivate Kernel (i9000 initramfs) with i9000 ROM.
[Captivate Android Development] ademejia:
how did you guys get cm7?
[Captivate Android Development] TheEscapist:
It's probably broken in the captivate rom, then. I'll try i9000 rom + captivate kernel w/headset fix tomorrow.

Build it from source. Instructions are on the Cm forums, use coolya's repo instead of codeworkx's though.
[Captivate Android Development] jfanaian:
Hi everyone,

I'm working on building CM7 and had an issue that I wanted to ask about. I'm using coolya's branch and was able to build the rom and kernel, flashed the kernel into my phone, and can boot into CWM 3.0.

The problem is, that when I install the zip generated using the initial_*.sh script, then reboot, it just boots back into CWM 3.0. I've tried building using the captivate and galaxys scripts, but I seem to have the same issue with both. Has anyone run into this? Any tips that could help out?

Thanks so much.
[Captivate Android Development] aqtrans:
Have you tried using the ota_*.sh scripts? I didn't really investigate the differences but I had to flash the initial zip, then the ota zip.
[Captivate Android Development] jfanaian:
Thanks for the input. I tried to install the update zip after the initial zip but it still just reboots to CWM again :(.

To explain a bit, I'm mounting to USB using the CWM option under the mount menu, then copying the cm7-galaxys-initial-YYYYMMDD.zip and cm7-galaxys-update-YYYYMMDD.zip to the root of the mounted directory. Then in CWM I'm going to install zip from sdcard and choosing the initial, then rebooting, then doing the same with the update zip.

Thanks!
[Captivate Android Development] aqtrans:
Strangely I just experienced the same CWM reboot problem when trying to install a new build. What I did to resolve it was use Heimdall (or Odin) to flash back to JI6, before it even booted though I yanked the battery, threw it into Download Mode, and flashed the CM7 kernel. Might have been overkill, but it's running smoothly now.
[Captivate Android Development] TheEscapist:
and the latest build has sms working for you? I tried with the i9000 kernel, still no luck. About to try Captivate with i9000 initramfs. if not, could you pm me your kernel or exact instructions?
[Captivate Android Development] cchant:
You guys having issues with wifi sleep or random reboots? I'm recompiling the i9000 build right now and was wondering where we stand. I'll be using it with the captivate kernel
[Captivate Android Development] TheEscapist:
Wifi sleep works fine, I was watching the logcat and saw it go to sleep a few times, and I haven't had any random reboots. I just can't get incoming sms to work.
[Captivate Android Development] vvaffles:
so can any 1 who is running this tell me what the bugs are? FWIW it seems that SMS doesnt work right and random reboots or wifi sleep? also what is the source that you guys are compiling from: i9000 or i897?
[Captivate Android Development] techmik67:
I followed the instructions from coolya's github. I had/have ramdisk.img, system.img, userdata.img and i can make boot.img. I used the release tools scripts to create 3 zip files..... cm7-captivate-initial-20110130.zip.......... cm7-captivate-update-unsigned.zip....... cm7-captivate-update-20110130.zip.

when i try to install the initial zip i get :

Flashing radio image...

assert failed: write_raw_image("/tmp/modem.bin".

"radio")

E:Error in /mnt/sdcard/cm7-captivate-initial-20110130.zip

(status 7)

Installation aborted.
[Captivate Android Development] He4dShOt:
i'm in this situation too :(
[Captivate Android Development] aqtrans:
Are you flashing from CWM 3.0? The write_raw_image command only exists on 3.x. Probably be best to Odin/Heimdall the initial kernel, then boot into recovery, and install it.
[Captivate Android Development] He4dShOt:
where can i found the initial kernel?
[Captivate Android Development] aqtrans:
If you ran the initial_*.sh, the zImage should be in there. The kernel may very well be the same for the initial and update zips though.
[Captivate Android Development] techmik67:
Will try that, thx
[Captivate Android Development] TheEscapist:
EDIT: Totally misread aq's post, so my post is unneeded.

Also, If any of you guys get it up and running, tell me if you have working incoming sms, and if you had to change any settings to get it.
[Captivate Android Development] jfanaian:
I tried this but still got the same issue. The only difference is that I'm using JH7 and not JI6, what phone is JI6 for? Couldn't find it under Captivate in samfirmware.com.
[Captivate Android Development] mnjm9b:
JI6 I think is the leaked froyo for captivate.
[Captivate Android Development] jfanaian:
Do you know where I could find it? Thanks!
[Captivate Android Development] mnjm9b:
I wish... seems to be an insider thing.

Cognition 2.3b8 I think is the only rom I found using it.
[Captivate Android Development] He4dShOt:
I think something was wrong the first time. I did try with the zImage but i got stuck on the loop with KANGED...now after recompile i'm on CWM 3
[Captivate Android Development] TheEscapist:
I actually misspelled it, I was going from JL1, stock Rogers. :rolleyes:

I don't think it matters though.

Just going to post my steps so that just in case I'm doing something somewhat different.

1. build_galaxys.sh in full rom

2 build_captivate.sh in kernel/samsung/2.6.35

3 tar the kernel at arch/arm/boot using tar - H ustar -c zImage > zImage.tar

4 run initial_galaxys.sh in releasetools

5 flash kernel using odin

6 reboot into recovery, flash initial zip
[Captivate Android Development] techmik67:
I built captivate full rom and captivate kernel..... gonna build galaxys also.....

BTW - it worked to tar and flash zImage, then reboot into recovery and flash initial.zip
[Captivate Android Development] mnjm9b:
Why start your own repo???

Can't you ask coolya to let you push your changes to his?
[Captivate Android Development] cchant:
I thought it was flash kernel flash efsbackup flash initial zip then flash ota?

Edit : sorry you're correct I misread.
[Captivate Android Development] jfanaian:
You have to fork a repo to commit changes and then request a pull. He should get his changes in coolya's repo, though, as his is out of date (or was last I checked).
[Captivate Android Development] aqtrans:
Here's what I use to flash JI6 with Heimdall.
[Captivate Android Development] TheEscapist:
Captivate rom is pretty broken, just use i9000 + a reoriented captivate kernel.

codeworkx told me too. All the changes are really small though, so I'm probably just going to send the changes to him and let him put them in.

Yeah, I couldn't get the repo to work properly for me anyway. Besides, with the headset fix posted earlier, all we really have is the orientation changes and flipping the sdcards ( which I've done), as they were reversed for me. All of them are really small, so I'm just going to send them to codeworkx and get him to put them in the main repo. Right now, I'm more concerned with getting incoming sms working though, then I can use this as a daily driver, and **** around with it alot more.
[Captivate Android Development] techmik67:
Building the rom for galaxys as we speak......
[Captivate Android Development] jfanaian:
Do you mean to flash initial zip with Odin/Heimdall or to use CWM's "install zip from sdcard"?
[Captivate Android Development] TheEscapist:
It's a update.zip, that must be installed from CWM 3, which is why we flash the kernel first. That kernel is (afailk) the only one with CWM 3.
[Captivate Android Development] aqtrans:
Just fyi, the Captivate ROM+kernel should work now. I used build_captivate.sh for the kernel and ROM, both built fine and seem to be running fine.
[Captivate Android Development] jfanaian:
That makes sense.. thanks! I just wanted to make sure I wasn't doing it the wrong way. I'm using CWM 3 to load the update.zip generated using initial_galaxys.sh. I'll keep experimenting until I find a solution :)
[Captivate Android Development] TheEscapist:
Sdcards working? I heard it was broken in cappy rom. Also, orientation sensor is broken in captivate kernel, but works in i9000 kernel.

EDIT: Got a copy of the MMS from somewhere else, won't install.
[Captivate Android Development] aqtrans:
SD cards are working, but swapped. You're right though, orientation sensor is broken, that's just the first thing I turn off after installing any ROM :p
[Captivate Android Development] TheEscapist:
Yeah, just pull vold.fstab and swap the labels, mount points and partitions. ie sdcard /mnt/sdcard auto becomes emmc /mnt/emmc 1.

And yeah, it works under i9000 kernel, but it's reversed(like it should be with a non-reoriented kernel). If i could just hunt down that damn driver, find the galaxys specific code that's making it work, then I could add the reorient code from xcal. I just cannot find it for the life of me.
[Captivate Android Development] mnjm9b:
Thanks for that... what I was referring to was source code though...

Along those lines, can a kernel be modified without source?
[Captivate Android Development] TheEscapist:
Not really. Remember, AT&T froyo hasn't been released, so sources haven't been released.
[Captivate Android Development] jfanaian:
Question, after flashing the kernel is it supposed to boot into recovery mode by itself? By that, I mean, without pressing the keybinding to boot into recovery.

I'm just confused as to why it CWM boots even after installing the cm7 zip, and can't really think of anything else to try.
[Captivate Android Development] mnjm9b:
thats what I thought but in that thread supercurio posted this "Kernel alone link added - begging to be modded"

so how do you mod a kernel without the sources?
[Captivate Android Development] TheEscapist:
I dunno, I always do a battery pull and manually boot into recovery. When you flash the initial zip, you're flashing from CWM 3 (orange recovery), right?

I dunno. Supercurio put Voodoo into the JJ4 kernel, but I don't know how.
[Captivate Android Development] mnjm9b:
Is the cwm3 available separately anywhere? And is it only compatible with CM7?
[Captivate Android Development] TheEscapist:
Not as far as I know, and no, CM7 is only compatible with CWM 3 though.

Why, is your kernel not working?
[Captivate Android Development] jfanaian:
Yeah, using CWM 3.0 the orange one :)
[Captivate Android Development] TheEscapist:
Then I'd try re syncing and re building. Maybe you just had a bad build.
[Captivate Android Development] ademejia:
Is anyone going to post how to install cm7 on captivate? I dunno how to build from source.