yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] nerdcorerising:
I've been trying to build it today as well. I got the exact same error with make otapackage, (building it is fine, but making the package is what breaks)

I've managed to track down that the error is caused by there not being a "boot.img" file when the ota_from_target_files script expects one.

Now the real question, why isn't there a boot.img if the script expects one? My guess(and it's really only a guess) is that there isn't a working cm kernel for the vibrant yet, so no boot.img. There is a ramdisk from the build, but that's only half of what is necessary to make a boot.img.

I'm thinking about trying to use the boot.img from another rom or maybe stock. I have no idea if it will work, I'm a fairly experienced with programming/linux, but new to android hacking.
[Vibrant Android Development] wergeld:
I don't think this will work without the proper boot.img.

Probably all kinds of drivers missing too.

But its cool to work on =)

BTW how long did it take you to "finish" the build?

Took my dual core 2.8GHz 2GB ram pc about 45 minutes.
[Vibrant Android Development] nerdcorerising:
I have a dual core 1.6 on my laptop, took me around 1 hr 40 min.

My thoughts are either of these two options could work:

1. If we had a kernel for the vibrant we could make a boot.img using the kernel and the cyanogen ramdisk. The problem with this approach is that even if we had the kernel, the format for the boot img could be vastly different for the dream/sapphire, which is what most of the tools are written for. See here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images for what I'm talking about.

2. If we could make just an update that flashes the system and data without the boot, that could work. Then we would be keeping the kernel and ramdisk from the stock rom, which would have the correct drivers. The problem with this would be if 2.2 depends on a newer linux kernel than is provided with 2.1, or if there are options left out that cyanogen depends on. Also, I have _no_ idea how to make a custom update.zip and can't find a how to anywhere.

P.S. I'm not sure if you know this or not, but when you run make otapackage, it runs the regular make and then the ota_package script after. So you have the output files (system.img and user_data.img) in out/target/product/vibrant to mess around with. So, like I said in 2 up there, if somebody knows how to make an update.zip that flashes those two img files, then we could try out cm 6 on our stock kernel.
[Vibrant Android Development] chaoscentral:
i can tell u now that wont work, I made an update zip with the system directory that JAC posted for CM6, and it doesn't boot with the stock boot img. I'm assuming reason behind that is the init.rc is still setup for touchwiz, and probably some other things too.
[Vibrant Android Development] dcchristopher:
http://en.wikipedia.org/wiki/Android_(operating_system)#Update_history

2.0/2.1 is based on Linux kernel .29, 2.2 is based on .32

Theoretically you could get the boot.img from another Froyo ROM but you would need all the kernel extensions/drivers specific to SGS ... perhaps from one of the leaked Samsung firmwares? (JP3, etc)
[Vibrant Android Development] nerdcorerising:
Yeah, I realize that they are on different kernels -- but that doesn't necessarily make them incompatible. Most linux kernel updates are bug fixes/performance optimizations/driver updates, which wouldn't affect the compatibility. What would prevent us from running android coded for a .32 kernel on a .29 kernel is if some library or system call was implemented in the .32 that isn't in the .29 and android 2.2 depends on that library/system call. I feel like .29 to .32 is too small of a difference to really affect the compatibility of software running on it, but that's just my intuition.

What I'm beginning to suspect is that CM 6 for vibrant is just broken. I managed to jury-rig an update.zip together using the Nexus One Release Candidate's install script (it wasn't signed, but clockwork doesn't care) and install just the system and data on top of the stock kernel, and I got endless reboots without even getting past the initial Samsung screen.

So, it could be that the kernel is incompatible. It could also be that the script I used doesn't create the right symlinks for the vibrant because I stole it from another phone. Or, it could be that cm-6 is broken for the galaxy s right now and that's why the devs haven't started releasing nightlies.

My phone didn't get far enough to be able to adb shell in and get a logcat, so I can't really say what happened other than it doesn't work.
[Vibrant Android Development] chaoscentral:
im pretty sure its the kernel. I remember back when I had the HTC Hero, and 1.5 was the only firmware out, and devs were trying to get eclair working on the phone, they were really half assed ports where not much worked until a leaked 2.1 build came out then they just took the kernel from that and it worked fine.
[Vibrant Android Development] DocRambone:
I dont know if this helps... but here is the 2.2 kernel from ZSJP2 19000 leak.
[Vibrant Android Development] ttabbal:
I'm getting adb to build now.

Installed Ubuntu 10.04 32-bit

installed the dependencies from the wiki page

sudo aptitude install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev

Here I found out that the Sun Java JDK isn't available without manual intervention. OpenJDK worked, but I want to make sure I don't get some weird compatibility issue. The Ubuntu release notes tell you how to get it..

sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo aptitude install sun-java6-jdk

Setup the enviornment.

export CCOMPILER=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

source build/envsetup.sh

And now "make adb" works. I'll report back when the build runs weather it works or not.

Note for everyone here, I don't expect the build to be installable or work on hardware right now. I don't recommend flashing it. I just want to be able to build it and perhaps be able to help work on it. If nothing else, it's interesting to know how to do it. I expect we will need a kernel with proper drivers and a modified ramdisk. Changing some stuff in the init.rc from JACs kernel might make the system bootable. Wes also has a ramdisk project in his repo, but I haven't gotten far enough to try to build that.

cd vendor/cyanogen/
./get-rommanager

curl: (6) Couldn't resolve host 'koush.tandtgaming.com'

Well... that sucks. :) I'll have to pull it from my phone or something. I didn't feel like getting my cable out, so I just did a "touch" on the file. The resulting ROM won't work, but I don't expect it to anyway. :) I just want to make sure I can build. I'll worry about the kernel/ramdisk/recovery later.

And get-google-files fails with a 404 on "http://www.kanged.net/mirror/gapps/gapps-passion-FRF91-signed.zip".

Editing the script and changing FILENAME= at the beginning to "gapps-hdpi-20100817-signed.zip" has that working at least.

Build is now running. So now I wait... and wait...
[Vibrant Android Development] zaduma:
This is exciting. I wish I knew more about linux and android OS to help right now.
[Vibrant Android Development] egzthunder1:
Hey guys,

I cleaned up the thread a bit (due to that post in the first page)...
[Vibrant Android Development] bchalk:
Thanks for this thread, all good info. Hopefully some more revelations will come with an ota 2.2 next month...
[Vibrant Android Development] ttabbal:
OK. I had some machine issues, but I can now build. The CM Wiki has been updated, they have categories for the various phone builds. The vibrant one doesn't have any data yet, but I followed the dream-sapphire one and replaced the phone specific parts with Vibrant versions. Other than that, the steps they give work.

"make otapackage" fails in the packaging stage. That's not surprising, as it's still being worked on. "make" worked fine though. I did use "make -j2" to make it use 2 threads as it's a dual CPU.

The root filesystem needs to be updated with a new init.rc for one, it's expecting MTD partitions and such. Not a big deal. I need to grab the JAC kernel source and see how he's doing the bootup for Eclair. The stuff that gets built looks to be designed for HTC devices, complete with the flash-image type tools being built. :)
[Vibrant Android Development] dcchristopher:
Great work ttabbal ... I plan to join you guys in this endeavor the weekend of the 11th. I will get a vmware instance of Ubuntu running on my wintel box and see if that will be enough for a development "box". My biggest concern is the ability to run this damn thing. People much more knowledgeable than me are vehemently recommending against flashing this on our phones. Well, how the heck does one work on it? (not that I would rather risk bricking my phone) I had an idea and looked into using the Android SDK's AVDs to host the system image. Apparently, it shouldn't be that hard to accomplish.
[Vibrant Android Development] ttabbal:
You don't want to flash anything yet as the boot stuff isn't ready yet. Building is a small part of the job. It needs to be packaged with a matching kernel and initrd. And there could still be bugs in the setup. Vmware should be ok, I used a xen vm.
[Vibrant Android Development] moyofalaye:
bump.

Just wanted to add my 2 cents,

I think the biggest hinderance to cyanogen on virbarnt is getting a working 2.2 kernel. But Ugene has gotten a hold of one (pending gps part)

And cyanogen has noted that if a rom is missing a hardware function then its not a rom ( something like that, not exact quote)

I guess thats why they stalled the dev .

and let me copy and paste the biggest problem thats holding development

quote

skraw, on 19 October 2010 - 11:03 PM, said:

I remember well the reactions I got when I called CM6 for SGS vaporware. Looks like cyanogen is just heading for the same conclusion.

CM is no small project. But they are all behaving like its programming "hello world". If you want to make this whole thing truely successful you have to start at its biggest problem: communication. Your web2.0 communication channels are just big bs. The information is not stored but gone right after you told it. Do you think a linux kernel could be programmed by twittering or such forum sh*t ?

_Learn_:

1) you need a mailing list. Only then your information is not lost for the interested world like it is now.

2) Talk to the world, and not amongst the same 5-10 people.

3) Make a wiki where you explain the basics of the project and how a complete newcomer can take the sources and make a flashable image out if it with gnu compilers and tools. Only then more people are really enabled to contribute. Therefore take diffs as patches, because everybody can create them.

4) Understand that there are a lot of people able to code _parts_ - small or big - of a project. As long as you don't open the whole thing up to the world _completely_ you cannot incorporate their knowledge.

Your problem is management, not coding.

/quote
[Vibrant Android Development] krylon360:
I have RC0 already built if you want it. I can't get it to flash completely though. You are more than welcome to pick it apart and go from there if you'd like. Just let me know and I'll host it up on dropbox for you.
[Vibrant Android Development] jad011:
can you send it to me ? do you know why its not finishing ?
[Vibrant Android Development] anomalous3:
I'm not saying Wes Garner isn't a brilliant and talented dev, because as far as I can tell, he is. And I'm not saying that I could do the porting myself, because I couldn't with the knowledge I have at the moment. But I'll leave you with this:

There's a reason a real OpenEclair 2.0 never got released, but got absorbed into the CM project.

I hate to say it, but someone that has as much of a life as Wes probably shouldn't have taken on such a large responsibility as managing the codebase for a device like ours. I've been checking up on his github regularly. A little work here, a little work there. But everyone else on the CM project, and plenty of devs with very little time on their hands in this forum have been putting in what seems like a lot more work. We need someone else to take over CM6 for Vibrant.
[Vibrant Android Development] jad011:
agreed, thedudesandroid has been working on it, but i havent seen change on his github page lately, probably closed stuff
[Vibrant Android Development] SE7EN-:
I couldn't agree more!
[Vibrant Android Development] cwalker29:
i second that!!!
[Vibrant Android Development] miglop:
I want a Cyanogen ROM already!
[Vibrant Android Development] PSP_Hacker:
lol everyone does :D

Aside from the TONS of enhancements from CyanogenMod, when we have it on the Vibrant and other Galaxy S variants, we'll get Gingerbread and other future releases of Android much quicker.
[Vibrant Android Development] eortizr:
We will see CM6 on a vibrant with Gingerbread has already been eaten
[Vibrant Android Development] richan90:
From wesgarner's twitter a few days ago:

"Yea brick is a great ROM officially support by CM RT @scottkellum @wesgarner So CM6 on Vibrant seems stable enough, time for a test release"

Is that a sign that it works?
[Vibrant Android Development] boimarc89:
no that means he brickd it....he has to get another 1
[Vibrant Android Development] speedysilwady:
i think hes sarcastically referring to his bricked vibrant?
[Vibrant Android Development] richan90:
Right.. totally misread that lol
[Vibrant Android Development] ryan562:
yeah looks like he may have bricked it. it looked like he was getting close to a beta for cm6 before the brick happened and according to his further tweets, odin did not work.
[Vibrant Android Development] TheDudeOfLife:
wait...wut?

;)

"nothing works" but more will soon...
[Vibrant Android Development] roguespy0:
Awesome dude, just saw your pics on twitter,cm6 is booted on the vibrant, keep up the good work.
[Vibrant Android Development] jad011:
you are the greetest
[Vibrant Android Development] moyofalaye:
Thank You for taken your time. Please could you help us help you,

What are the issues your having with getting it working ?
[Vibrant Android Development] TheSneakerWhore:
The Dude himself...good to finally e-meet you.

Thank you a million times over for picking up CM for the Vibrant.
[Vibrant Android Development] PSP_Hacker:
LOOOOOOK AT THIS **** !!!!

http://twitpic.com/30ewun

HOOOOOOOOOOOLY ****

THANKS FOR ALL YOUR WORK!

Let's get a public test release when it's brick-free and at least most of the radios are working! I don't care if GPS doesn't work!
[Vibrant Android Development] skater4690:
lol you should look at the other pics for the android tips widget it says avoid wesgarner at all costs. lmao!!!
[Vibrant Android Development] PSP_Hacker:
LOL! I guess we can #blamewes for the slow progress of CM on the Vibrant. CM6.1 would've been completely ported to our phones by now if TheDudesAndroid took it from the beginning (along with Scepterr)! :D

I think the help widget also defines Kingklick as a kang :D
[Vibrant Android Development] ryan562:
x100 can't wait!
[Vibrant Android Development] Jamison904:
This is awesome! First JAC and Eugene support the Vibrant and now the Dude! Kind of feels like a G1 family reunion. Great to see you Dude and glad you are taking on CM for the Vibrant.
[Vibrant Android Development] xalucardx:
Does CM6 will get rid of the rfs file system?
[Vibrant Android Development] crazy25000:
I've never used CM6 rom before. Summary anyone? :p
[Vibrant Android Development] gthmcty1:
Pure goodness .......but the search button and www.cyanogen.com will also help explain more in detail.
[Vibrant Android Development] crazy25000:
I went to the website, but how is this any different than what eugene is doing?
[Vibrant Android Development] Master™:
He gave you the wrong site.. http://www.cyanogenmod.com/

Unless that other site just doesn't show up for me :confused:
[Vibrant Android Development] crazy25000:
Haha I figured, so I searched online and got the right one :p

Thanks!
[Vibrant Android Development] Emrys_90:
It's similar to his AOSP rom, but there are still some things that are not AOSP. Plus CyanogenMod has a customizable UI right in the settings, you don't have to mess with any framework apk's to change colors. And their roms always stay updated, you'll continue to be on the newest Android version. Cyanogen is considered one of the best roms and developers for Android.
[Vibrant Android Development] CamachoInc:
I love CyanogenMod when I had my G1 and I would love to finally have it on my Vibrant. But I'm losing hope.
[Vibrant Android Development] gthmcty1:
Thanks for the correction Master, I guess I had "premature sendulation"

LMAO
[Vibrant Android Development] PSP_Hacker:
LOLOL xD
[Vibrant Android Development] jfleegle:
Looks like cyanogemod.com is down.
[Vibrant Android Development] Master™:
You forgot an "N" there..

It is http://www.cyanogenmod.com
[Vibrant Android Development] numberoneoppa:
Down none-the-less. :P
[Vibrant Android Development] crazy25000:
Ahh ok...the vibrant is my first android phone and I've gotten rid of my iphone so I've flashed almost every vibrant rom just to learn and its been pretty amazing. I've read a lot of comments about CM, but I've never had a chance to try it. thanks for the replies!
[Vibrant Android Development] jfleegle:
Yea, looks like I typo-ed my post, but the cyanogenmod is still giving the message "Error establishing a database connection".
[Vibrant Android Development] Master™:
Really? Works for me...
[Vibrant Android Development] numberoneoppa:
It was down. It's back up now. :)
[Vibrant Android Development] :
I'd let The Dude 'mount' my vibrant anyday! lol

anyways...

thought this might be of interest. sztupy over on the cyanogenmod forums posted this:

we've been using the pre-init hack for a long time to get some extra stuff working, and pre-init you have initialize the devices yourselves. For the stl devices you'll need to load up the fsr and rfs modules as they will initialize the wear-leveling control on the stl devices. After that, and mknod-ing the stl devices mounting should work (it does for us, and we're not relying on samsung's init), but for rfs mounting you'll have to manually adjust the mount parameters, or else it will mount as vfat or j4fs (neither of them is desired)

Here is also a CWM that is a bit more compatible with the SGS: http://github.com/sz...otable_recovery
[Vibrant Android Development] Master™:
Link is broken..
[Vibrant Android Development] crazy25000:
Lolol made me laugh soo hard!
[Vibrant Android Development] BinaryFabric:
CyanogenMod 6.0.1 RC was releasted, but the site is being hit so hard that I cant access it.

Did the Vibrant make the cut???
[Vibrant Android Development] MTC44:
No.

10 Char
[Vibrant Android Development] TRF-Inferno:
No, Cyanogen already tweeted that it did not make it. We need to give time for TheDudesAndroid to make it actually usable.
[Vibrant Android Development] jroid:
This is cm 6.1 RC1. Maybe cm for vibrant might be usable when cm 6.1 release version is ready but maybe a release would be at cm 6.2? cm6 will still be worked on even after gingerbread is announced until the source for gingerbread is released, which is when cm7 will commence. Atleast the dude has figured out how to get cm to boot, so when cm7 comes around, we'll have it on the vibrant too :)
[Vibrant Android Development] cwalker29:
Man to be honest cm6.1 for the vibrant is being left behind on someone dirty shoes. If eugene can come out with a good and stable 2.2 froyo rom. What the hell is the problem with a team of top dev's getting the job done? Truth be told its just not on the 1st to do list.. Nor the second nor the third. I'm tried of wait and i enjoy eugene rom so on that note y'all can take until next year to bring it out i don't give a ****!!!! Anymore.
[Vibrant Android Development] CamachoInc:
Its not coming to Vibrant till 2012. I gave up hope for CyanogenMod. I don't even think they care about us since they use HTC phones. All I see is bull**** excuses. If these other ROM developers can make 2.1 & 2.2 ROMs for us why the Hell is taking so LONG for CyanogenMod Team to make it.
[Vibrant Android Development] wpbcubsfan:
I'm sorry but you obviously have no clue what goes into developing for CM. First off, they build from SOURCE, they don't hack together leaked versions of other ROMs that are only partially functional (like non working GPS). I appreciate Eugene's work but it's a completely different type of development. Also, CM doesn't release anything until everything is fully functional and without the GPS drivers we're still probably SOL.

Also, I'm extremely tired of people feeling someone from Team Douche owes us anything. They develop in their free time at their leisure so when it's done, it's done.
[Vibrant Android Development] djf8:
How many times does it have to be explained.....Cyonogen Mod is built from AOSP and not modified from the TouchWiz releases that eugene and others are building/cooking off of. Not to say what eugene, sombionix, or master are doing is easy but it is completely different from what CM is going for.

*edit Ah beat me to it.
[Vibrant Android Development] jroid:
the dude is constantly working on cm. He finally got it to boot, which means he got a kernel to finally build for it which was the main problem. Now he has to get it functional and working but it is booted. Ppl loose focus on how hard it is to work on a device with NO source code and a completely different filesystem than they're use to developing for.
[Vibrant Android Development] PSP_Hacker:
There is source code for the kernel, but only the kernel, not anything else in the system. And the latest released kernel source for the Vibrant is Linux kernel version 2.6.29, the one used in Eclair (but Froyo needs 2.6.32).

The 2.6.32 kernel source was already released for the international Galaxy S (GT-I9000) though, so the CM devs (wes, scepterr, whoever) were probably busy porting it to work on the Vibrant.

TheDudesAndroid said it himself on twitter, that HTC > Samsung because they actually know how to release kernel source.

The filesystem was probably not a problem for CM development on the Vibrant since it was already fixed with the lag fixes. This is similar to how T-Mobile G1 users were applying apps2sd mods to make the system store apps/data on the sdcard's ext filesystem (along side the usual fat32); it wasn't hard to make or do because it was just a location change, and Linux is open sourced and extensively documented and easy to bend. Same should be on the Vibrant.

I wish the CM team was more open with their development. Maybe if we could get the entire progress of the CM vibrant port through github, some of the good devs on xda (like bionix, eugene373, etc) would've fixed things in CM Vibrant like the radio, JIT, audio, etc. and we would have release candidate 1 by now with every main thing working except with maybe a few bugs due to Samsung's weirdness (which get fixed later on :D)
[Vibrant Android Development] CamachoInc:
Yeah I'm sure it take time BUT I've read some of people's comments on here and other forums and I can't remember the Developers name that was in charge of working on CM for Vibrant and I read that he's been bullshitting and now the job is passed on to someone else. In my opinion, that's lack of RESPECT for those who donated money for the CM Vibrant. I'm also tired of people sticking up for this bull. The guys working on CM are very smart and educated and there's no excuse for this **** so stop kissing there ass.