yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mnjm9b:
Thank you for your suggestion...

I am sure it will come in handy for someone.

also an alternative to using alternatives is setting java path.

good...

thank you for the feedback.

any input at this time is good input :)

I appreciate your time and effort.

good to know about the usb tethering too.

I also think that invoking the system the way I am may be preventing

some features from working correctly.

I didn't have time to work on this over the weekend.

I plan to get a working CWM zip and see if that helps.
[Captivate Android Development] hedgehogmd:
Just a Update i built this in a VM using ubuntu 10.04 LTS with no errors at all. I'm going to test it out this weekend. :D
[Captivate Android Development] mnjm9b:
Cool...

Thank you for playing.
[Captivate Android Development] gemuse:
Built this weekend error-free on Ubuntu 10.04 LTS. Your instructions work just fine.

I One-Click'd back to stock JF6, Master Cleared, and then copied the Overstock KB1 kernel, the KB1 modem and the newly created system.img to clockworkmod/backup. I Odin'd speedmod, battery pulled, and rebooted to recovery and installed the system.img, and then install from zip'd the kernel, rebooted, and then installed the modem.

However, still no connection. Baseband version listed as unknown.

Since the AOSP build is froyo 2.2.2, will this require a different modem?

Also, all the known bugs are here; no internal/external SD, camera, or wifi.

Runs as smooth as butter after the first bootup, though! Great work so far.

PM me if there's anything I can help with. I'm only just teaching myself Java/Android, but I have a background in VB.net, C#, lua, and javascript.

~Gemuse
[Captivate Android Development] mnjm9b:
Its looking like there is an issue with

IMEI.

The cm builds have you backup the efs folder and then restore during install.

My next attempt I will try that method to see if that is the issue.

It's a simple fix but honestly I don't

Understand the underlying problem. (my HTC builds never needed to do that)

Also the int/ext sdcard issue could be a borrowed fix from cm.

To be honest most of the issues can be addressed using cm workarounds.

I just haven't the time to apply them yet.

As I want to apply just one at a time for troubleshooting purposes.

I encourage anyone that is interested in this to try adding in some of the cm fixes and see how close this can get to working.

I will be busy for the next few days but hopefully I will get a chance this weekend to test my latest changes.

Sorry I am so slow at this.
[Captivate Android Development] gemuse:
The vold.fstab fix isn't working for me for enabling internal sdcard. I didn't actually understand what I was doing when I edited it to the settings CM6.1 said made it work. I'll do some research and see if I can't get down to the bottom of this SD card mystery.

Thanks again, mnjm9b

~Gemuse
[Captivate Android Development] mnjm9b:
Ya, I got the same results.

Keep me posted with your results.

I appreciate your help.

I unfortunately had a much busier weekend than I had planned and didn't have time to flash my latest attempt. I may try sneaking a flash in tomorrow.

I have got to get me a backup phone so I can play more during the week. LOL
[Captivate Android Development] gemuse:
This is getting exponentially messy. I also can't get an IMEI fix working. The Samsung stock flash doesn't have an efs folder or any IMEI that I can find. Also, custom ROMS, stock Samsung and the AOSP build all have different formats for their vold files. (Samsung = vold.conf, custom = vold.conf and vold.fstab, AOSP = vold.fstab, me = confused)

I'm going to do a lot more research on mounting devices with Linux and get back to you.

Done with finals!

EDIT: There is an efs folder, I was just looking in /system... oops...
[Captivate Android Development] mnjm9b:
Ty...

It's Not as bad as it looks.

As soon as I get a chance to flash

I am hoping to announce some good news.

Also, for all the people downloading,

It would be nice to hear if anyone else is working on any of it.
[Captivate Android Development] gemuse:
Excellent! Waiting patiently.

Do you know what determines how Android deals with cameras?
[Captivate Android Development] AdamOutler:
It seems that everything you are missing from functionality can be found on opensource.samsung.com. The missing hardware features are the kernel files which are proprietary samsung drivers. You're supposed to copypasta them over the kernel before building.
[Captivate Android Development] gemuse:
Excellent. Thanks, Adam!
[Captivate Android Development] mnjm9b:
not sure what you are asking

but for now I am using a fake camera to get it to build.

I will add in the aosp camera at a later date.

I am sure a few of the issues come from not building my own kernel

However, I have been unable to restore a working kernel build tree for 2.2.2

although honestly, I have put that on the backburner for now.

for now I just pair it up with the kb1+voodoo kernel (maybe thats my problem???)

also, I usually try to avoid the samsung methodology of copy/paste over a working build tree.

although, to be honest, I did try just that when initially looking into building the kernel.....

BIG FAIL>>>
[Captivate Android Development] gemuse:
Yeah, the Samsung open source copy pasta files are incompatible with each other. The prebuilt in Samsung's platform files won't build Samsung's kernel, as js22 experienced on page 15 of this thread. I verified.

I couldn't get anything to build from the kernels, same as js22.

Team Hacksung's kernel built just fine, but that doesn't help us much.

Any updates, mnjm9b?
[Captivate Android Development] mnjm9b:
I am going to go about this from a different angle

But I WILL have to have a kernel for sure....

Was the team hacksung kernel you built for froyo?
[Captivate Android Development] gemuse:
I'm pretty sure it's Gingerbread. I tried to flash it just for grins and giggles over a froyo rom and it bootloop'd.

I'm going to play around with the kernels a little bit more today.

Anything in particular you want me to do?
[Captivate Android Development] mnjm9b:
Great...

Let me know what you get.

Also, if you are building from source,

In the config there is a place for initramfs location...

Direct it to the initramfs posted in OP.(where you download it...not the link...lol)

And if you do find a usable 2.2.2 froyo kernel source,

Let me know.

Thanks
[Captivate Android Development] gemuse:
Well, 2.2.2 kernel is based off of the 2.6.32 linux tree, but I'm not sure if that helps at all. My internet connection is heavily firewalled against P2P connections (i.e. git, repo), so if someone could mirror the 2.6.32 android kernel source, I could get back to work on this. :D

And is there a place for the intramfs in the config menu, or will the .config have to me edited manually? (I'm not currently on my cooking machine lol)

Thanks again, mnjm9b.
[Captivate Android Development] mnjm9b:
That's what my problem was when I was working on the kernel.

I had a working one but lost it from hd failure. Haven't found a good one to replace it.

I suspect when I was trying that there were changes going on that broke something. But I haven't had a chance to try again.

And yes there is a line in the config menu. If you can't find it use one of the others like xconfig etc...
[Captivate Android Development] gemuse:
So the 2.6.32 kernel tree is missing/broken?

That could be messy.
[Captivate Android Development] mnjm9b:
It was broke when I tried... but that was a while ago...

It may be fine now.

That happens sometimes when stuff is being updated. It usually gets fixed but I never went back to try. Got busy working on the Rom...

If I can remember, I will post the urls to the kernel trees I tried before. And if I get a chance I will try and check them.
[Captivate Android Development] gemuse:
Thanks mnjm9b. I'll get back to cooking ASAP. :D
[Captivate Android Development] bravomail:
could you post compiled Neon Arm7-a optimized *.so files?

could you post compiled Neon Arm7-a optimized *.so files?

The ones from /system/lib/ folder?

Since you already progressed so far...
[Captivate Android Development] mnjm9b:
Sorry...

I just had a catastrophic hd failure. I lost all my work.(again!!!!)

Good thing its all on github now.

Although I haven't done any neon stuff so I wouldn't have it to give anyway.

(i don't think so anyway....can't verify without the hd...)
[Captivate Android Development] v1nsai:
Looks real interesting, fun way to get exactly what we want from our phones and really see what's going on in there. I'll have more time to play with this soon..... hopefully :-(
[Captivate Android Development] gemuse:
Ouch. Best of luck! Right now I don't have much besides a bunch of folders with different branches, and combinations of AOSP + samsung open source, none of which build.

On the android kernel tree there's a different branch for samsung hardware. Is that the branch we want, or do we want android common?
[Captivate Android Development] bravomail:
cata disk failure

It's a disaster.

In that ARM compiler comparison blog the guy mentioned some pro $$$ compiler which routinely gives the code twice as fast (ARM RVCT). We can try torrent searching it or may be some guy will share it for the benefit of the community.

Quick search brought me:

http://www.symlab.org/wiki/index.php/Talk:Installing_ARM_RVCT_4.0

Here is trial version

http://arm.com/products/tools/software-tools/rvds/index.php

Here direct download link from ARM site - trial I guess

http://arm.com/products/tools/software-tools/rvds/updates-patches/arm-compiler-41-patch.php

Search engine

http://www.filecrop.com
[Captivate Android Development] mnjm9b:
No idea...

I think I tried every source available. The one I lost with my first hd failure was the only one that worked right.

However, I have no idea where I got it.
[Captivate Android Development] mnjm9b:
Huh....

Not sure what your talking about.
[Captivate Android Development] designgears:
Might I recommend you some hard drives?

http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DEPA=0&Order=BESTMATCH&Description=re4

RE4's are designed to handle 24/7 access. Very reliable. Bit more expensive then your standard consumer drives.
[Captivate Android Development] mnjm9b:
Thanks for the suggestion.

Those look great...

Although, I don't think they come in 2.5" (laptop)

I already got the replacement.

http://www.newegg.com/Product/Product.aspx?Item=N82E16822136692

However, I am now shopping for a NAS RAID unit.
[Captivate Android Development] bravomail:
It's ARM compiler

ARM RealView Toolbox.

RealView yields good search results.

But after reading this I think CofeSourcery or gcc (Yagarto) will do as well. Difference is within 10%.
[Captivate Android Development] gemuse:
Just got back from field training.

And the hunt for a legit 2.2.2 kernel tree continues...
[Captivate Android Development] E_man5112:
Is CM7 a daily driver yet?
[Captivate Android Development] rasroygbiv:
+1 for that. I will help test it.
[Captivate Android Development] Smallsmx3:
If your running an aosp build why aren't u sharing it with us.....your making it sound so easy then why aren't the cm guys able to get cm7 completely up and running?
[Captivate Android Development] newter55:
I doubt it is even close to true aosp or it is not that functional otherwise I am sure it would be posted.
[Captivate Android Development] mnjm9b:
If you actually read the OP I never even once implied that this was ready.

Nor did I ever say this was easy.

and Yes it is very much true AOSP.

which is exactly why it is taking so long. (extremely hard without source)

on a side note I have been recently banned from the site (another reason for my absence)

for disagreeing with a senior mod. (nice abuse of power)

this is the last straw for me I have been fed up with the direction of XDA lately and I will be taking a long break from posting anything here.

I will be posting my work elsewhere and if you are smart enough you will find me.

feel free to bash me some more now....thats what this site is good at anyway.
[Captivate Android Development] vvaffles:
i think smallsmx3 and newter55 was talking to ytt3r about his comment before about the nexus s
[Captivate Android Development] krips2003:
Hmmm.... so you were banned just because a senior mod had disagreement with you. If its true the its quite in bad taste.

I humbly request to all mods to not follow Steve Jobs mantra 'My way or highway'.

Anyway all the best for whatever you are doing to make this cappy less crappy. ;-)
[Captivate Android Development] Smallsmx3:
I definatley wasn't bashing you and I apologize if that's how you took it.... I just thought I read that u were running this as a daily driver....I think its a great idea to get aosp froyo going.....no one wanted to do it for eclair because froyo was around the corner. Here we are still waiting and no aosp for the cappy....I've never bashed anyone on this site because I respect all the work put in d the development of things....I
[Captivate Android Development] newter55:
Sorry if you took my comments out of context. It was directed at yttr who commented that he was already running an aosp build.
[Captivate Android Development] Smallsmx3:
Same here
[Captivate Android Development] MZeora:
I would also be willing to help in any tests.

Sent via XDA from liberated Captivate
[Captivate Android Development] steveo314:
By aosp do you mean like what is on the droid 2 or what is on the infuse 4g?
[Captivate Android Development] mnjm9b:
Yes I am reinventing the wheel so to speak. but why would it be rewarding to simply build someonelses work (CM)

CM is basically AOSP with CM parts injected.

I see how CM builds for samsung seem to be having some hangups

so My thinking is that if you start from scratch (AOSP) then it would be easier to fix.

then after all the bugs are fixed it would be easy to inject any addons

such as CM or any other mods.

and then if it breaks while adding in the addons it will be a simple diagnose to fix.

BTW... In case anyone was wondering, I finished my temper tantrum and will continue to release info here as well as my other site.
[Captivate Android Development] mnjm9b:
I don't know what the Droid 2 or the infuse has...but by AOSP i mean AOSP.
[Captivate Android Development] Smallsmx3:
Glad to see your back.....I would have felt awful if I ran someone off the site....if u need testers count me in.....
[Captivate Android Development] mnjm9b:
I was more pissed at being banned than anything else, but I will let that go...

there are far more GOOD people here than BAD.
[Captivate Android Development] Smallsmx3:
I agree....sounds like u got banned very unfairly and there's nothing u can do about it....oh well
[Captivate Android Development] nakedninja42:
glad you decided to stay, I've been waiting for a "real" froyo release for this phone while I still read the threads hoping for a release in the future for CM
[Captivate Android Development] newter55:
+1 on being happy to see your return. I really felt bad that our little hijack of your thread was completely misunderstood by you.

I would be glad to test anything you need as well. Even though I did grab an inspire I am not sure I want to sell the captivate so it's available for brick testing anytime... at least until the warranty runs out ;)
[Captivate Android Development] steveo314:
When I think android froyo aosp I think no bloatware and a white status bar with black clock and the green battery icon from left to right which is what the droid phones run. And its easier to update with the google sources.

The infuse froyo aosp looks like how our cappys did when we took them out of the box with the samsung bloatware and the black bar with the blue battery icon.

If you get this "pure" google froyo to run on the cappy count me in.
[Captivate Android Development] steveo314:
This what aosp looks like:

http://www.motorolaphones.net/wp-content/uploads/2010/08/Moto-Droid-2.jpg
[Captivate Android Development] mnjm9b:
There is only one AOSP...

And yes that's what it looks like.
[Captivate Android Development] Kaik541:
ok, you're simply confused by terminology. AOSP = Android Open Source Project... which is "android as google designed it." with 2.2 that's a white status bar with black text, with 2.3 that's a black bar with green icons.

the ORIGINAL MOTOROLA DROID ran AOSP (2.0 at launch), as does the Nexus S (2.3), Nexus One (2.1), G1 (1.5), G2 (2.2 sort of), and mytouch 3G (1.6). the droid x, droid 2, mytouch 3g slide, etc. do NOT run AOSP. All the upcoming tablets run AOSP 3.0 honeycomb from the looks of things (besides the Flyer and Dell Streak 7).

The Captivate (or any Galaxy S phone) has never run AOSP out of the box. The experience you are describing is the STOCK build, not AOSP. The Infuse 4G/Captivate run a CUSTOM version/framework of android that is not AOSP... in fact, this specific breed is known as "TouchWiz", HTC usually puts "Sense" on theirs, Motorola has "MotoBlur", of which there are two versions... need I go on?

Basically AOSP and "stock" are two different terms that it's important to differentiate between.
[Captivate Android Development] steveo314:
I know that what's on the droid is aosp. I've seen instances in the android "hacker" community where the galaxy s firmware is referred to as aosp even though it is not even close.

Id much rather be running pure google on the cappy. Don't none touchwiz, sense, and motoblur phones get updates faster????
[Captivate Android Development] 10ee:
Good luck mnjm9b,

If you need any testing I have a nice new 10.11 SGH-i896 at the ready. And best part is I have a backup so if it blows up? Oh well....

Looking forward to this.
[Captivate Android Development] amtrakcn:
...Isn't Nexus S equipted with different Wifi, Baseband and GPS chips than Captivate?
[Captivate Android Development] cevy:
maybe you can check with the guys who worked on this: http://xdaforums.com/showthread.php?t=815420

They started working on pure AOSP, then no news and apparently they switched to CM...

maybe you guys can share some knowledge ?

just throwing my 2 cents
[Captivate Android Development] mnjm9b:
Wow...cant believe I missed that.

I know I searched for "captivate aosp" before I posted this.

Although if I remember correctly I may have been using the xda app to search.:eek:

either way, thanks for pointing that out.

I will have to read through it to see where/why they got off track.

I don't have time right now but maybe this evening or sometime tomorrow.
[Captivate Android Development] DOAlaboratories:
gdanko was working on an AOSP for a while, look up his thread for places to start
[Captivate Android Development] mnjm9b:
I don't need to know where to start.... I'm almost done... lol
[Captivate Android Development] jhernand1102:
Almost done with a fully working AOSP ? Can't wait to test it out...
[Captivate Android Development] mnjm9b:
Well, almost done in the sense of the big picture.... from scratch to finish...

However, It's always the last few bits that takes the longest...

I make no promises as to how soon. But it looks good.
[Captivate Android Development] ronii1123:
Take your time, and also do you plan on trying Gingerbread sometime after this? Just curious
[Captivate Android Development] Smallsmx3:
Almost done....that sounds pretty awesome.....is everything working or are u having trouble getting things working?
[Captivate Android Development] mnjm9b:
To be honest, my biggest problem is finding time to work on it.

If only I could compile on my phone... lol
[Captivate Android Development] Smallsmx3:
Well you will make alot of people happy on here when you finish.....including myself
[Captivate Android Development] TDQuiksilver:
Can't wait! :D
[Captivate Android Development] mnjm9b:
just so you all don't think I dropped the ball on this one...

I am kinda halting anymore work for a few days to see how this whole

releasing of source code thing pans out...

it sure would make life easier if we had it.

although, once the code is released I am sure many other people will be building it

so my work wont be so special after all.

I will however finish this with or without code... so stay tuned if your still interested.
[Captivate Android Development] ferman:
The source code for froyo will only be released when samsung/att release an update for us which has not yet been officially announced so i doubt in a few days it will be released. It usually takes a few weeks for source to release after the phones get it. :)
[Captivate Android Development] crecsky:
Isn't there source code out already for the SGH-I896? Basically the same phone in canada, just without the audience chip, which isn't programmed in anyways?
[Captivate Android Development] kannonball2290:
The source code for the vibrant was just released and since it is possible to run a vibrant rom on our captivates without havering to change anything really and it having the audience chip it is the preferred code
[Captivate Android Development] ru-dmitry:
Vibrant does not have Audience chip.
[Captivate Android Development] mnjm9b:
I have all of the source code for these and other devices,

I am studying them and cherry picking what I find relevant to add to

what I already have.

But if you want a rom/kernel that is built completely with the code from these other devices, it will have problems.

and there are already other roms out there that are based off of wrong sources.

I am attempting to build this as pure as possible.

(yes I ran it with those as sources, and it does work...but Its not what I am working on)

and I will be only waiting a few more days before resuming work on this...

I have heard reliable chatter about source being released very soon.

But we have all seen this idle chatter before.

I can only work with what I have so I will give it a bit but thats all.
[Captivate Android Development] Djazin:
The Draft

Looking forward to test what ever you have cooking with this project even if its raw and bloody, in need of something based off this. pm me when you need a cappy cadaver to throw this rom at.
[Captivate Android Development] Smallsmx3:
I agree....I doubt well get official froyo and the source for it so close together...im really lookin forward to this becoming available though...take your time. Make sure its right.. it would be nice to have more captivate specific roms. I9000 roms blow anything we have available right now but I still feel like my phone doesn't work right
[Captivate Android Development] Thegodfather156:
Good luck
[Captivate Android Development] ferman:
Alright update is tomorrow is Samsung does what they did for the epic we'll see source in a few days! :D
[Captivate Android Development] illdroid:
actually captivate aosp, is the single most important project.

the knowledge gained from the success of such project, will unleash us from at&t\samsung handcuffs and will give us the ability to create a captivate android version out of any future android version (gingerbread etc...)
[Captivate Android Development] tjsooley:
Is this build Fully AOSP?
[Captivate Android Development] jhernand1102:
There is no build released yet but it will be AOSP when and if it is released.
[Captivate Android Development] mnjm9b:
Saw that....

Keeping my fingers crossed.
[Captivate Android Development] MikeyMike01:
Absolutely.

Sent from my Captivate.
[Captivate Android Development] bay_wolf:
Agreed! 10char
[Captivate Android Development] nkrick:
I think gdanko got busy with a new baby... that and he was waiting on 2.2 source from Samsung for a couple of drivers (that may have been released in the Nexus S and/or i896 sources since).

I have been hoping for a pure AOSP build for the Captivate since I bought it back in August. I came from running xdandroid on my Fuze, which was mostly AOSP with a few extra's added in. A pure AOSP build is the corner stone for future development of nearly any other Android build, including Android versions 2 years from now that will never be released for our phones. CM is great, but CM can be injected on a pure Captivate kernel + AOSP sources.