yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Kaik541:
certainly not meaning to sound belittling, because AOSP 2.2 would be great as an alternative (especially based on pure captivate source code for support like things like the audience chip), but you guys do know CM7 is already heavy in development and fairly well along (though still buggy and lacking support for things like the audience chip).

And CM7 is much closer to AOSP than CM6.1 was, and the addition of the tmobile theme engine made it have a much cleaner look and feel. if you guys are dying for some AOSP/CM, you have the capability of building it yourself (just don't expect everything to work).
[Captivate Android Development] ferman:
Awesome. This is also a feet still and if I'm not mistaken cm7 for the captivate is based off i9000 still. Sooooo its not closer. And if we get aosp froyo wouldn't it help to make aosp gingerbread a bit easier since there is an aosp version.

I still don't know but that makes since. But idk.
[Captivate Android Development] mnjm9b:
Ok....

So just for a quick update to where I stand on this.

I finally read through all of gdanko's thread.

It started out very much like my plan.

However skipping to the end, it is all Cm talk and I9000.

So I went through it all to see where it got off track.

I can't say for sure what his thoughts were. But it seems like the lack of source had led him to the cm builds with I9000 source.

I am still hopeful for source soon.

But I am getting a lot farther than I ever thought possible from scratch.

I am currently working on setting up a github repo.

This is my first time using a repo from this end so I am leaning as I go. I will announce it once I figure it all out. So I can get some testers input.
[Captivate Android Development] designgears:
CM is no longer AOSP, they put tons of extra crap in.
[Captivate Android Development] Kaik541:
never said it was. said closer to AOSP. as in, CM7 is more like gingerbread than CM6.1 was to froyo. either way, this isn't relevant to the conversation at hand. CM7 is more or less based off of a lot of the Nexus S sources (but not everything because of hardware differences) with sprinklings of i9000 and captivate stuff.

Just like MIUI is built off of CM, CM is built off of ASOP; heavy modification but a lot of similarities at heart. AOSP is never a bad thing, it can only lead to further development and help the community as a whole. Good luck with it and I hope something comes of it.
[Captivate Android Development] a.vandelay:
cyanogenmod is most certainly aosp. it's built from the android source as published by google. sure they've added things, but they're still building it from the source. at this point any rom not based on a samsung build will be great.
[Captivate Android Development] whiteguypl:
Incorrect.

Edit: sorta
[Captivate Android Development] goob1284:
Any idea when this will be up and running?
[Captivate Android Development] askpcguy:
Interested to see this and where it goes. Subscribed.
[Captivate Android Development] Phateless:
This is just awesome! I have noticed the exact same thing about most ROMs being ported from some other device and I would love to see how pure AOSP would run on this device. :cool:
[Captivate Android Development] mnjm9b:
I have ran into a minor issue recently where I lost most of my setup for compiling.

I didn't loose anything important but I do need to re-download some of the sources that I was using to create the homemade drivers.

Specifically the Rogers, vibrant and the I9000 froyo sources from the Samsung opensource site.

However, for some reason I can't get speeds better than 3-5 Kb/s

Does Anyone have a mirror for these???
[Captivate Android Development] timur525:
Someone get this man a mirror!
[Captivate Android Development] spirit32:
come on guys! give him a mirror!
[Captivate Android Development] bay_wolf:
I'll get you a mirror tomorrow if no one else gets you one by then, headed to bed onw.
[Captivate Android Development] askpcguy:
What do you need? I'll let the download run overnight if I can.
[Captivate Android Development] MikeyMike01:
http://www.multiupload.com/INR5NEC9GP

http://www.multiupload.com/FAM67ZODKU

http://www.multiupload.com/1NVNCUCEMK
[Captivate Android Development] BL4zD:
subbed

/10chars
[Captivate Android Development] trell959:
we dont even have a samsung source to build from
[Captivate Android Development] locsplitter:
subbed,

thanks dude
[Captivate Android Development] kannonball2290:
Any word on this? Is development stopped?
[Captivate Android Development] mnjm9b:
My last post was less than a week ago. :rolleyes:

I dont have the luxury of spending every waking moment working on this.

WORK/FAMILY/LIFE/ETC...

On a more Serious Note...

the loss of my storage drive has actually went from a minor hangup to a Major issue.

I had a working froyo repo sync on my ext HD and have been using it for a long time.

luckly I had most of my work that I was doing still on my PC.

however, after loosing my drive I have not been able to get a working froyo sync.

I can successfully build a generic AOSP for eclair as well as gingerbread

I can Even build for CM7.

But so far for some reason the FROYO repo seems to be broken.

SO DOES ANYONE HAVE A WORKING REPO FOR FROYO

I have been using:

git://android.git.kernel.org/platform/manifest.git -b froyo
[Captivate Android Development] mnjm9b:
Burning up the laptop!!!!

just found a repo at:

git://github.com/android/platform_manifest.git

synced fine and looks good.

I am currently doing a test run.

if this works I should be releasing something very soon...
[Captivate Android Development] Dlev7:
Alright very excited good luck. Will for sure try this out if you can get it out soon. Any prerequisites with flashing?

Im on CM7 obviously going back to stock but any thing different?
[Captivate Android Development] KCutrer1:
That's definitely exciting news! Look forward to seeing how this turns out.
[Captivate Android Development] Coak5:
Oh joy. I really can't wait to see what kind of magic you pull out on this one. Been waiting for a long time for somthing like this to come out for our cappys. Thanks for your hard work and effort. I'm more than sure everyone here appreciates the work you're doing.

P.S. IMO Gingerbread is fantastic too but I much rather use Froyo knowing that it is way more stable and knowing that you are building it from the source makes it way more exciting than CM7 to me. I don't know about anyone else.
[Captivate Android Development] Kaik541:
... err, CM7 is built from source, so don't kind of understand that last bit. AOSP froyo based on pure captivate sources would be nice to have as an alternative though (especially for the audience chip support)
[Captivate Android Development] mnjm9b:
I appreciate all the warm response to this.

However, I can almost guaranty No one will use this as a "daily driver"

It is very plain.

No Google apps

Stock android apps

No tweaks

Not very functional

The intended use is to serve as a "base Rom" that is to be developed into more useful roms

BTW...I am currently on cm7 for my daily use.

And contrary to what is said,

Cm7 has tons of features beyond a stock AOSP

While it IS built from AOSP... it offers the kind of extra options that defines what having an android phone is all about.

I only hope that once the captivate sources are available that it will help to make cm7 as well as all other roms for us...

better.
[Captivate Android Development] buddy17:
what kinds of things have you got to work so far?
[Captivate Android Development] mnjm9b:
test build with the new repo completed without issue.:)

however, it fails to boot in emulator. so I would bet its not safe to flash to device yet.

I even tried syncing 2 different branches of froyo with same errors in emulator.

there is definitely something different with this new repo.

I will look into this more maybe this weekend. (I think I saw smoke from the laptop on the last build...LOL)
[Captivate Android Development] mnjm9b:
Ok... I got my test build to build fine...

And to my surprise I just read that the froyo source just dropped.

So this "should" be easy now...

However, by the time I get a chance to run it with source there will probably be 100 new roms in the dev forum...lol

I will still do this for myself.

And if Noone posts an AOSP

version I will still post it here...

Probably not until this weekend....
[Captivate Android Development] MikeyMike01:
Don't be discouraged... AOSP is a much more worthy goal than CM.
[Captivate Android Development] mnjm9b:
I agree...

I'm not really discouraged...

I just cant work on this as much as most devs here do

so I cant provide results as fast.
[Captivate Android Development] :
Thats ok, a little progress is better than none at all. When you feel its ready or need beta testers, post it. You will find that a lot of people will appreciate your hard work. :)
[Captivate Android Development] a.vandelay:
what he means is a lot of people to jump down your throat when they can't voice dial over bluetooth in 8 languages while using GPS and giving a dog CPR.

people here are never happy, that's how it is when you've never actually developed something and expect people to be able to make it perfect from v. 1.0.

also, get a donation link!
[Captivate Android Development] di11igaf:
bingo..

post of the day award.
[Captivate Android Development] oldskooldawgz:
I am much more happy with anything devs put out I get much more critical when it is something a company puts out cough Samsung cough looking forward to ur work and keep up the work
[Captivate Android Development] iXNyNe:
This would be really cool to see plugged into something like that rom kitchen where you pick what you want on the base.

Good luck, looking forward to this!
[Captivate Android Development] bames:
good stuff

i have found it good just to ignore anything said by a person wearing a bluetooth earpiece. Did they miss out on the memo? Even worse with wearing your phone on your belt and right up there with sporting a full fledged fanny pack. Seriously people i am all for creature comforts, automation, integration, etc...but you look ridiculous.
[Captivate Android Development] mnjm9b:
B

I

N

G

O

that's all I have to say about that...
[Captivate Android Development] Coak5:
Done!?!? Already???
[Captivate Android Development] ademejia:
everybody would still love to see a aosp rom do you have a op ?
[Captivate Android Development] askpcguy:
I'd offer to beta this, if available.
[Captivate Android Development] mnjm9b:
sorry guys....I jumped the gun on my enthusiasm...

I am still having one minor hiccup on the build.

I will hopefully get this done before the weekend is up.

otherwise I will have to wait till next weekend before I can release anything.

I want to at least flash it to my phone before I post it for others to try.

and I cant take the chance of flashing during the week.

so I will try my best to get this done before tomorrow night.
[Captivate Android Development] askpcguy:
I keep seeing things in the android SDK about virtual devices, if I can get that to work, I can flash a beta "rom" to a virtual device. Will report back once I get more information.
[Captivate Android Development] rajendra82:
Since the first rule of CM is don't ask for an ETA, and since this is AOSP, not CM. What's the ETA? :)
[Captivate Android Development] mnjm9b:
I always test in an emulator first before flashing to phone.

so I will already know if its working that way.

I will only release it if I flash successfully on my device first.

I would hate to have someone BRICK their phone because of something I released.

for you.... NEVER...lol:D
[Captivate Android Development] steveo314:
No...the first rule of rom dev is you don't ask eta. Just like debian linux.
[Captivate Android Development] rajendra82:
Cannonical give Ubuntu ETA twice a year into eternity, and they are the new debian for all intents and purposes. Just saying :p
[Captivate Android Development] dayv:
But remember while ubuntu is given away, Cannonical is a commercial corporation. Both getting and expecting an eta is a different animal in a commercial environment.
[Captivate Android Development] :
Be original. http://www.slackware.com/
[Captivate Android Development] mnjm9b:
ok...

so I got the test build to build fine

and I also successfully ran it in an emulator.

however, I could not get a FULL captivate specific version to build

without errors.

I am currently building a very limited captivate specific build.

I don't expect there to be any problems with this build

(other than it's not worth flashing)

I will then continue to add in little bits at a time to narrow down

where the issue is with the FULL build.

when I get it pegged I will be able to fix it easier.

I will keep you posted but I Highly doubt a release this weekend.

baby steps...baby steps...LOL
[Captivate Android Development] mnjm9b:
switching repo again...

maybe I am paranoid but it seems like every one I have tried has

been sabotaged so only people "in the know" can work around it.

I have ran into some very strange errors that I never encountered

any other time I have built android.

I attempted to contact several "DEVs" that appear to have a working repo

to trouble shoot my errors but I haven't made it to the "IN CROWD" YET...

google only supplies me with other people having the same problem but

no solutions. and the ones that say they solved it never say how!!!

I really wish I had backed up my working build environment to a dvd...

Ugggg!!!!

this sucks.

this is taking way longer than it should...

if I don't get a working build environment soon I will have to abandon this project.

to be honest anyone with a working build environment could get this built within an hour.

I have spent weeks now trying to get back to where I was when I had a working environment.

I am really surprised no one else released this yet...
[Captivate Android Development] mnjm9b:
Maybe I will just jump to building an AOSP gingerbread

for some reason the gingerbread and eclair build environments

are building just fine...

just froyo is having problems.
[Captivate Android Development] :
Well Froyo has been around for a bit now and there are plenty of Froyo roms available now... so a Gingerbread would not only be a step forward, but it would also probably benefit a lot more people right now, not to mention that it seems to be easier for you since its building just fine.

Again, thank you for your time and effort put into this project.
[Captivate Android Development] mnjm9b:
the only problem with jumping ship to gingerbread is that

there are no sources for the captivate.

so I will end up with a franken-source to get it to work correctly for us.
[Captivate Android Development] a.vandelay:
no way to file a bug report with google?
[Captivate Android Development] js22:
I'm watching this thread with curiosity, and have a few questions for either the OP or anyone else who has time to answer. I don't want this to be a hijack, but it seems pretty related to this thread; If OP or moderators want me to repost somewhere else, I understand.

The short version of my question is :

"How does (could) open-source ROM development work ?"

Compared to the Linux/FOSS world that I'm familiar with, the Android ROM development world seems very private and secretive. Lots of fragmentation and unnecessary duplication of effort.

It seems to me (and I realize this may be naive) that for some fairly generic platform (say, Froyo on a Galaxy S device) there should be a generic repository of code/configuration/HOWTOs that ROM developers could work from and contribute back to. I realize that there are issues with chunks code that are closed-source, but (again, somewhat naively) I imagine that that's just a matter of having a set of scripts that can be configured to copy a "black box" binary file from a specific device and build it into a target ROM.

As a user of custom ROMs, and someone with a Linux background, I'd sure like to be able to peek into the latest cutting-edge ROM that I've flashed, do a little debugging or possibly feature-adding, and pass the changes back to the ROM maintainer(s). And just for fun, it would certainly be fun to be able to download the code, do a config for my device and my needs, and then compile it, just like I would for a custom kernel. (I'm not saying I really would do this, but just knowing I could is a Good Thing.) As it stands, flashing a bleeding edge ROM and encountering a bug or missing feature leaves you with the single option of waiting for a lone super-hero to address the issue.

Is this very far off the mark from what the OP has in mind ? Am I missing some fundamental hurdle that makes this sort of thing impractical/impossible ?

Anyway, as I said, I don't want to hijack (too much).

OP, as you get time, I'd be interested in seeing what steps you have taken towards getting a system working.
[Captivate Android Development] mnjm9b:
Exactly...

Or at least how it was/should be.

I am on my cell right now.

When I get a chance I will update

The OP with links etc...

In the meantime you can get started

By Googling "android aosp"
[Captivate Android Development] js22:
I've looked (briefly) at the AOSP site, but from what I see it's oriented to porting Android to new, uncharted hardware. The thing that seems to be missing is the "secret sauce" of how to configure and build the open source part of Android, combine that with the binary black boxes for a Captivate/Galaxy S/etc., and end up with a ROM that works.

It seems like the job of discovering the secret sauce is the big hurdle in the ROM development world.

I guess the other big issue is the "local" community of developers and users of ROMs for our platform may want to fix bugs and add features that the folks upstream (Google) don't want to deal with. So some place to share patches, configs, code, etc. would be a big help.
[Captivate Android Development] Kaik541:
this is kind of the goal of cyanogenmod. freel free to peruse their (very public) build system here www.github.com/CyanogenMod, and even the more detailed additions from the CMSGS Team (CyanogenMod for Samsung Galaxy S) here: www.github.com/teamhacksung

both of these have a very thoroughly documented list of things that were necessary to get it working correctly and make it work easily. it may not be "end-user readable", but if you have any interest in development, you should be able to comprehend the vast majority of it.

as for froyo stuff, there was a lot of preliminary work done at www.github.com/cmsgs but was dropped in favor of gingerbread.
[Captivate Android Development] mnjm9b:
Yes...

I use all of those and more.

In fact most of what I find that works comes from these.

Big thanks to these folks.

Contrary to what most think,

CM7 is Full of extras that differ from a pure aosp.

Although, I enjoy most all of them. :)

However its the extras that sometimes get in the way of troubleshooting.

All I am trying to do is get a pure aosp build specifically made for the 897

I never had this much trouble.

I had an easier time porting android to my winmo HTC tilt.

Although the key in that scenario is HTC!!!
[Captivate Android Development] Kaik541:
oh I'm very aware of how much is tacked on (and what some even find very unnecessary), but the way the build is put together is very similar to how google does it. theoretically, you could apply almost all of the changes from CM7 to AOSP and it would remove the majority of the bugs (again, theoretically). I hope you know that me dropping in here isn't an attempt to promote or bolster CM7's status on the forum, it's capable of doing that itself... just trying to help educate in any way I know how (the guy above wanted information about a collaborative and detailed build system for android, and CM has that so that was why I answered the way I did)
[Captivate Android Development] mnjm9b:
As I am well aware of you being aware...lol

You do a great job in the cm7 thread.

I was only bringing up that because so many people make statements like wanting a true aosp rom like "CM7".

I love CM roms...

Most of what I used on the tilt was

Either a CM rom or at least used

some of CM "fixes"

Using CM7 as a daily driver as we speak.

I love that I can build it myself.

Feels like I can trust it more if I have code. :)

I only was attempting to do a froyo build because I "had" a working repo that I built froyo on for the HTC tilt. (Many times)

I am getting closer now. Seems most of my issues are because of spelling errors and mislocation of files or file/folder structure from the different repositories I have tried. Even the ones you mention.

So for now I go file by file doing error checking.

Seems to be a bit much for an already outdated build version...lol

If my next run doesn't yield some results I may jump ship and help with the CM7 build.

I have already done some work on getting the audience chip working.

I will up that info when I have time.
[Captivate Android Development] TRusselo:
It bugs the sh!t out of me when people say that!
[Captivate Android Development] askpcguy:
Really? I got an update mail to this subscribed thread and this was the update?
[Captivate Android Development] MikeyMike01:
And now someone gets notified of your post. And my post. And so on.

The cycle of disappointment churns onward.

Sent from my Captivate
[Captivate Android Development] askpcguy:
In an effort to make an on-topic post, the best place to start development on a Captivate Android ROM is here http://opensource.samsung.com/

Specifically Mobile > Mobile Phone > SGH-I897 USA KB1 SGH-I897_OpenSource_froyo.tar.gz

That package contains all you need to build the "stock" Samsung Froyo rom.

What's done beyond that point I can only guess, usually ROMS are themed. New images are injected into sources so when flashed, the rom has a new look.

Aside from that, most of Captivate ROM development comes from building from other device sources, making changes or hacks if you will to make things work on the Captivate.

Then from that point, you're able to build a Captivate ROM without any trouble, you can start looking at other versions of Android and make an effort to create necessary files to get that Android version onto the Captivate.

Here's a post on i9000 roms on the Captivate http://xdaforums.com/showthread.php?t=734871

And another generic how to for building ROMS. http://xdaforums.com/showthread.php?t=928955
[Captivate Android Development] Kaik541:
slightly misinformed. the above zip only contains the source for the froyo KERNEL which is unrelated to the ROM building process. the kernel is only what runs the ROM, and will therefore not require any hacking together of PNG's and such.

both reaver117's and MikeyMike's post are irrelevant to the discussion at hand.