yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] wdfowty:
That's just kernel source code, not very helpful for building ics unless there needs to be some kernel tweaking.
[Droid Incredible Android Development] twistedumbrella:
I took out the bolded step when developing for the Tbolt, and I get to the same libaudio error. I am currently testing the general idea found http://modmymobile.com/forums/403-m...elp-building-working-libaudio-so-library.html of moving the libs to the folder to build. The error you were getting, though, pretty much states "you got rid of something I needed..."
[Droid Incredible Android Development] Smokeey:
How's it going? I'm downloading the source now.
[Droid Incredible Android Development] twistedumbrella:
make: *** [out/target/product/mecha/obj/SHARED_LIBRARIES/libaudio_intermediates/AudioHardware.o] Error 1
[Droid Incredible Android Development] wdfowty:
Well, I got past the libaudio error, I guess my brain wasn't working properly, and I didn't run extract-files script after make cobber (or at least I think that's what solved it lol). Now I just found out that a new error arose, and it's because I'm on Ubuntu 11.10, so I need to use the master branch (which I thought I had). Lol. Getting close though, just have to resync...
[Droid Incredible Android Development] Smokeey:
:( good job! Im at 78% download now!
[Droid Incredible Android Development] jermaine151:
What error you getting? I had the oprofile one and got passed it and now I got an issue with gtest. I'm using 11.10 (x64) as well. :(

make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libgtest_main_host_intermediates/gtest_main.o] Error 1
[Droid Incredible Android Development] tiny4579:
That would make sense as I think even on CM7 there are closed source binaries on our phone that are not in AOSP.
[Droid Incredible Android Development] twistedumbrella:
That is IRONIC. I JUST went to try the same thing haha
[Droid Incredible Android Development] wdfowty:
make: *** [out/host/linux-x86/obj/EXECUTABLES/obbtool_intermediates/Main.o] Error 1

Apparently you can cherry-pick the changes, as there aren't many differences as compared to the 4.0.1_r1 tag.

http://groups.google.com/group/android-building/browse_thread/thread/a859d5e6ab1de2bf
[Droid Incredible Android Development] twistedumbrella:
It's always fun if Ubuntu gives errors, considering I am on Mac 10.7 with XCode 4.2 and had to mod the **** out of it to get it to work with the 10.6/3.2.6 requirements. I will not give up all the updates to build one ROM.
[Droid Incredible Android Development] jermaine151:
Thanks WD. I'll try that. I surely don't want to download the master branch now.
[Droid Incredible Android Development] wdfowty:
Only place I've found that you can browse the source online is the CM github repo, under ICS branch.
[Droid Incredible Android Development] ithrewitontheground:
Would it be helpful to you guys to do get an SVN project set up like you did with bliss? Seems like it would be easier to do that way to me, not sure though as I don't know much about actual developing.
[Droid Incredible Android Development] wdfowty:
Screw it, I'm just gonna dl master. I'd have to fetch it anyways, and I don't feel like sifting through commits atm lol. Time once again to hog all the bandwidth in the house :rolleyes:
[Droid Incredible Android Development] jermaine151:
Makes me want to install 10.04 dual boot. D@mned gcc 4.6 is screwing with me!!
[Droid Incredible Android Development] nicatronTg:
If anybody manages to get it working, you're obligated to post a flashable zip. Unfortunately my good machine is locked into windows for gaming with no room to spare.
[Droid Incredible Android Development] Smokeey:
+1 Internets

Also, I love you.

Also, Koush and Cyanogen got the Nexus S booted using the leaked Nexus S kernel!
[Droid Incredible Android Development] wdfowty:
Wait...what?
[Droid Incredible Android Development] Smokeey:
He wants you to post a flashable zip as you get it booted :|
[Droid Incredible Android Development] Pons:
Obligated? Not sure if I like the sound of that one...
[Droid Incredible Android Development] sucker4pa1n:
Make sure copybit.h exists in your source... it said "no such file or directory" and I'd guess those other errors stem from the missing header file.

Tapatalk Pro Sig. Yep, boring.
[Droid Incredible Android Development] GRZLA:
I've been reading that GCC 4.4 works better.
[Droid Incredible Android Development] twistedumbrella:
Actually, we are obligated to post the edited source code in a publicly accessible location to allow others the opportunity to compile it themselves. For what you want, you should probably try a friendly request...
[Droid Incredible Android Development] kichard:
I'm so excited for you guys to get this running on our Inc's before verizon sells us our new nexys

:)
[Droid Incredible Android Development] GRZLA:
Ignore the children who want want want. People who really want ICS on the DINC are more than willing to wait. However many of you are trying to get a build running, thanks for putting in the work for us that aren't capable.
[Droid Incredible Android Development] donnyp1:
Glad to see you guys givin it a go. With all this teamwork going around, something good will come about. Glad to see WD givin it a shot! For all you cryin for a rom, either chill out, our load up your pc and dive in. Me, im leavin it to the pros and can patiently wait. Great work and good luck to all those involved.
[Droid Incredible Android Development] petecraig612:
Or ice-creamify a stable gingerbread ROM to tide you over lol. That's what I did. Good luck guys, can't wait to see the finished product.
[Droid Incredible Android Development] twistedumbrella:
I think I may be stuck dual booting my Mac after all. I got by so long without giving in...
[Droid Incredible Android Development] nicatronTg:
@twistedumbrella Doesn't prevent posting a flashable zip too, and even if you do modifications to get it running, the license doesn't say you have to release your modifications immediately.
[Droid Incredible Android Development] twistedumbrella:
One of the biggest causes of issue on this forum is the ratio of time spent reading a post to time spent replying to it. Please double check the post you are referring to. It clearly states that there is no obligation to post it. This has nothing to do with preventing it.
[Droid Incredible Android Development] 5thAgent:
Nobody's obligated to do anything for anyone on XDA or any other forum.

nicatronTg, please understand that developing a ROM takes plenty of work, and it's usually best if (even if a ROM is booting) the ROM is somewhat stable before releasing it to the masses. How about you compile the ROM and post a flashable zip. :P
[Droid Incredible Android Development] twistedumbrella:
It's true. It is not exactly just a Mortal Kombat button-mashing process to get a victory. If you want a peak inside what goes on behind the scenes, take a look here http://xdaforums.com/showthread.php?t=1343361
[Droid Incredible Android Development] wdfowty:
Wow, how did I miss that? I guess I was right to go to sleep then lol. You are correct, the copybit.h doesn't exist for some reason.
[Droid Incredible Android Development] da_knowledge:
I'm stuck there as well now. I can't find copybit.h anywhere.
[Droid Incredible Android Development] wdfowty:
Yeah, it's pretty strange...Could it be possible it's created when you build? I can't find it in the repos either. https://github.com/CyanogenMod/android_hardware_libhardware/tree/ics

After a little digging, I found this:

https://raw.github.com/android/platform_hardware_libhardware/master/include/hardware/copybit.h

No idea how compatible it is, but it's a start.
[Droid Incredible Android Development] twistedumbrella:
Mine had a copybit module that needed the optional tag, but it filled in the blanks after I did that.
[Droid Incredible Android Development] da_knowledge:
I think twistedumbrella is on the right track. From what I've been reading on the net, copybit shouldn't be necessary which is probably why we don't have the copybit.h file anywhere.
[Droid Incredible Android Development] Unholyfire:
Looks like you guys are kicking @$$. I so wish I had this week off instead of next week :-( Have we got a list of known source requirements running yet? I'd like to catch up tonight without having to re-read this entire thread. Anyone wanna start a new thread for that? Or get us all in an irc channel? I'm still stuck at work so I'm no boing boing right now :-P
[Droid Incredible Android Development] da_knowledge:
I'm new to all of this, but I always wanted to get my hands dirty. I figure the release of a new version is as good a time as any to dive in. I'm not exactly sure what you need for source requirements, so hopefully some one else can chime in.
[Droid Incredible Android Development] twistedumbrella:
Everything HTC specific from any existing device source repo, along with everything device specific. Basically the vendor repos and dependencies.
[Droid Incredible Android Development] wdfowty:
Found some nice little fixes for building on Oneiric Ocelot (11.10): http://groups.google.com/group/android-building/browse_thread/thread/207abb98ed72304
[Droid Incredible Android Development] GRZLA:
Out of curiosity, what exactly needs to be done to make this a bootable ROM? I've never built anything from source and I am sure most people who have DINC's haven't either. Just wanted to get an idea of what you guys are actually doing.
[Droid Incredible Android Development] Smokeey:
Plugging in kernel's/drivers/egls etc...but thats not as easy as it sounds, errors occur
[Droid Incredible Android Development] wdfowty:
Well, my main concern is getting the rom to compile completely/correctly. After that, you attempt to boot it, run a logcat/dmesg, and fix the source accordingly. I'm not an expert at this though. Like da_knowledge, I thought it was a pretty good opportunity to get my hands dirty in the world of AOSP....Should probably just stick to porting lol.
[Droid Incredible Android Development] Unholyfire:
IMO, it's mostly the same as porting. Just 10,000 more steps lol
[Droid Incredible Android Development] jermaine151:
Thanks WD! This pointed me in the right direction. I think my emulator build is finally going to finish compiling. Then I'll know my environment is sane and can start trying to add in the Inc parts. Just like you I'm no expert at compiling AOSP from source but I'm learning tons!
[Droid Incredible Android Development] wdfowty:
Awesome! Thanks bro.
[Droid Incredible Android Development] twistedumbrella:
Added all the details to the previous post. Hope it helps you guys out.
[Droid Incredible Android Development] jermaine151:
Thanks Twisted! I finally got was I was looking for:

Combining NOTICE files: out/target/product/generic/obj/NOTICE.html
Installed file list: out/target/product/generic/installed-files.txt
Target system fs image: out/target/product/generic/obj/PACKAGING/systemimage_intermediates/system.img
Install system fs image: out/target/product/generic/system.img

This bad boy is a beast to compile. Used up about 7GB of RAM in the process. Wow.
[Droid Incredible Android Development] wdfowty:
Got a new error now:

external/bluetooth/bluez/audio/liba2dp.c:46:17: error: sbc.h: No such file or directory

Should I do the same thing as the copybit error, and make it optional? Pretty sure we need it tho.
[Droid Incredible Android Development] twistedumbrella:
I am at the same spot. Trying to find a fix.
[Droid Incredible Android Development] wdfowty:
Emulator or inc imgs? Might want to specify before people go crazy :p

Ah, good to see it's not just me lol.
[Droid Incredible Android Development] jermaine151:
Oops. Yes, emulator only. That took a lot to just get that built (LOL). It runs great for an emulator image. Now at least I don't have to troubleshoot whether I have all of the things I need to build Android on this laptop. Now it's time to troubleshoot building it with the Inc specific parts.
[Droid Incredible Android Development] wdfowty:
Ahh that's probably a smart way to go about it.
[Droid Incredible Android Development] lioryte:
lol I wish I could help u guys but my poor ol' beat up notebook ain't got enough juice to work this. It just freezes up on me every single time :(

As for the BT error, try to use CM7 bin for now or take BT out...
[Droid Incredible Android Development] tiny4579:
So I'm trying to build ICS. Can someone zip up their device and vendor folders for me? I removed gingerbread as I had tried to sync CM's GB and ICS repo's in the same folder and I thought that was causing the following error but it did not:

Syncing work tree: 96% (213/221) error: revision refs/heads/ics in CyanogenMod/android_prebuilt not found

I tried

repo init -u git://github.com/CyanogenMod/android_prebuilt -b gingerbread
repo init -u git://github.com/CyanogenMod/android_device_htc_inc -b gingerbread

to grab the GB versions

but I get

fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found
[Droid Incredible Android Development] twistedumbrella:
You can also download the necessary folders from the CM github site. That saved me about 5 hours of downloading that happened later (just as a cya copy for missed files) which has yet to be needed.
[Droid Incredible Android Development] Smokeey:
I'm loving the progress you guys are making!!!

Keep it going!!! :D
[Droid Incredible Android Development] tiny4579:
Thanks, I got the missing files but I broke my repo with trying to init a partial repo in the same folder.

If I delete the .repo folder and re-init would it re-download if I keep the working copy or would it sync just the same? Do you know how to purge what I broke in there so I can sync the repo?

I'm not too new to git but repo I haven't done much with other than repo init and repo sync.
[Droid Incredible Android Development] twistedumbrella:
Deleting that folder is the equivalent of saying to the repo that the files do not exist. It will remove the existing files.

Do "repo status" and see what it says was altered to get a better grip on what to delete

After that you should be able to pick up where you left off with a repo sync. We are in the same boat with experience, I just got a little over-zealous reading how to add files for if they add support.
[Droid Incredible Android Development] tiny4579:
Yeah, I did that crap twice.

:(

I guess I was hoping it'd use the local copy when I synced again.

I didn't see this message till 30 freaking seconds after I deleted it.

Annoyed, third time syncing. At least it's under an hour.

And where did you get the prebuilt folder, the one for CM throws invalid LOCAL_SDK_VERSION and LOCAL_NDK_VERSION?

I know, I could just use the master mentioned but then if CM makes progress it's trickier.

I'm actually quite pissed because I was ok downloading once or twice but not 3. I wanted to be building by now :(

I could have just cleared .repo/projects/android_device_htc_inc.git i think as well as .repo/projects/android_prebuilt.git
[Droid Incredible Android Development] twistedumbrella:
I synced with AOSP for all the prebuilt stuff. Are you getting the entire source from their mirror?
[Droid Incredible Android Development] tiny4579:
Yeah, CM should have forked AOSP 4.0 so it should work. But I think I know how to get prebulit. The same way

github.com/android/platform_prebuilt then drop it in.

---------- Post added at 11:46 PM ---------- Previous post was at 11:10 PM ----------

Nah, that's no good. That's r4 of NDK and r10 of sdk. I guess that's the problem with mirrors. I'll have to pull them from the master location then.

Nevermind, I think it's good. Issue was that I had an old repo tool I think. I thought I updated it but it wasn't new enough evidently. It synced ICS fine.

---------- Post added 17th November 2011 at 12:19 AM ---------- Previous post was 16th November 2011 at 11:46 PM ----------

I won't be able to test tonight. I really need sleep, I need to wake up by 6 am.

But try in that file change the line

#include "sbc.h"

to

#include "../sbc/sbc.h"
[Droid Incredible Android Development] twistedumbrella:
For those errors, I copied in a CM7 libaudio.so, audio.so, and liba2dp.so as per synergye and ignored the errors.
[Droid Incredible Android Development] Smokeey:
ICS Keyboard works great on CM7. New auto correction and prediction works flawlessly.
[Droid Incredible Android Development] linuxmotion:
To any dev working on porting aosp to the Inc i am coming full force now. I was sick the last couple of days.. how unlucky is that. Ics drops and i get sick :-( but I'm all good now :-) time to get some **** rolling for all of us. I would like to lend my hand at anything you need.

This is where I'm at. I'm using the GB device tree from OMFGB. Removed the overlays from both device and vendor trees. Added the copybit header. Now I'm fixing the libaudio-qsd8k errors. Specifically with the audiohardware.h file. It appears to be cyclical header inclusions some where from Googling but i may be wrong.

the process of compiling a program(an OS is program.) to another system that it was not originally designed for is called porting. This is porting
[Droid Incredible Android Development] sucker4pa1n:
Woot! I'm glad my lack of programming these past few years hasn't neutered my error troubleshooting. Y'all are making me want to setup my Sabayon box (Phenom 1090T, 8GB RAM, no SSD though) and start toying with this as well... PS - Sabayon is a really fun distro to play with if you're a Gentoo fan. :-p

Tapatalk Pro Sig. Yep, boring.
[Droid Incredible Android Development] sucker4pa1n:
(Can't delete on my phone... stupid accidental repost)
[Droid Incredible Android Development] jermaine151:
Glad you're feeling better. I got stuck at about the same spot you were at, before calling it a night:

make: *** [out/target/product/inc/obj/SHARED_LIBRARIES/libaudio_intermediates/AudioHardware.o] Error 1

I guess I'll try Twisted's suggestion about grabbing the CM7 .so files. Hopefully I get time at work to play with it more.
[Droid Incredible Android Development] da_knowledge:
Good to hear that you are feeling better, and thanks for your contribution as a dev. You say you added the copybit header. Did you supply your own or are you using one from somewhere else?
[Droid Incredible Android Development] twistedumbrella:
That's great. Hopefully you won't mind explaining how to fix the audiohardware to the crowd of us who are stuck on it. It has been a real pain getting through it.
[Droid Incredible Android Development] jermaine151:
I seem to have gotten past this error by deleting libaudio-qsd8k from hardware/msm7k/.
[Droid Incredible Android Development] tiny4579:
Better way to skip it. Rename the Android.mk from the folder. I did that to skip the copybit error. That way you can revert easier if needed. I hope copybit is not important.

grr suspense is killing me. I started a build around 6:30 am and I can't even check the status until 6:30 tonight.i'm sure it failed though. And I have a social life tonight.do I can't work on it then. I should have just played skyrim last night lol.
[Droid Incredible Android Development] jermaine151:
It's in my trash so I can restore it. :) I doubt I'll need it if CM7's libaudio.so works with this. Copybit is only used with SurfaceFlinger when OpenGL can't be used. I compiled copybit fine by using the copybit.h file that wdfowty linked to in this thread.

EDIT: LOL @ Tiny! I know how you feel. I have to go to dinner with the lady tonight and I'd rather work on this. It is cranking right along at the moment. I have my home laptop next to me at work, building it. :D

EDIT2: Time to figure out this one:

make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libgralloc_qsd8k_host_intermediates/gpu.o] Error 1
[Droid Incredible Android Development] sruel3216:
Is there a way we can install this to use?
[Droid Incredible Android Development] nicatronTg:
There's a thread in the apps section about the keyboard and the new music app. Works like a charm, really good error correction.
[Droid Incredible Android Development] da_knowledge:
jermaine151, try adding

#include <string.h>

to /system/core/include/system/window.h

That worked for me.
[Droid Incredible Android Development] twistedumbrella:
I didn't think to in that high up the "food chain" lol
[Droid Incredible Android Development] jermaine151:
Baby steps:

in function out_set_format:external/bluetooth/bluez/audio/android_audio_hw.c:135: error: undefined reference to '__android_log_print'

I tried adding LOCAL_LDLIBS := -llog to Android.mk but it still bombs. Time for more research. :confused:
[Droid Incredible Android Development] da_knowledge:
Try LOCAL_LDLIBS := -L$(SYSROOT)/usr/lib -llog as mentioned here.
[Droid Incredible Android Development] jermaine151:
I tried that too. I ended up just commenting out the LOGE lines (Good luck to me troubleshooting. LOL).
[Droid Incredible Android Development] Unholyfire:
Got something to boot... but since I'm new to all this android source building, I'm not sure really what I've accomplished LOL.

- I did a full_maguro-eng build (I'll refer to this as FME). And it completed with no errors.

- I grabbed Joelz sdk build from 3 weeks ago (I'll refer to this as JSDK).

- I merged these into a zip:

+ META-INF (JSDK)

~ boot.img (JSDK)

+ SYSTEM [Folder] (FME {build *out* path})

~ Build.Prop (JSDK) {Replaced FME in SYSTEM folder with JSDK version}

Zipped, Placed on SD, Flashed with CWM, rebooted...

So, my phone boots, greets me with a message "Unfortunately, Launcher has stopped".

But I otherwise have all the functionality that the JSDK has, just with the FME SYSTEM :) That includes no touchscreen, just the pointer via trackball.

If this helps anyone's brain move into a state that is beyond mine, in a path to get a more pure AOSP for our INC, then YAY! Or, if I just wasted a bunch of my own time... Oh well, it was fun LOL

Comments?

Where do I go from here?

Or should I just abandon what I just did and get back to the pure INC build, instead of the FME merge I have now.

EDIT: Fancy finger-work, got it to unlock (after it locked/timed out), got the notification bar to draw down (that was next to impossible), clicked on the settings button with the cursor, got "Unfortunately, Settings has stopped".

LOL, even if my concoction is a complete fail, I'm fricken stoked that my idea does ANYTHING lol.
[Droid Incredible Android Development] GRZLA:
I'd say upload it and send it in PM to these other DEV's so they can see if they can do anything with it.
[Droid Incredible Android Development] bypass23:
All hardware lib/drivers/etc in your /system are maguro specific and not compatible and won't work with any HTC device.

You would have to point out all those lib/drivers/files that are maguro specific and backport them from a gingerbread build... it's the only solution to get any further imo

FYI there was already some Galaxy Nexus leaked images floating around before aosp 4 has been released, you could have basicly done the same with those.
[Droid Incredible Android Development] Unholyfire:
So essentially I've just created another unusable sdk Frankenstein. Ok. Like I said, I had no idea how usable this would be at this point, but I learned a crapton in getting this far. I appreciate the constructive criticism :) I'll back peddle to the build process the rest of you are currently on, and see if I can be of help from there.

Again, thank you. I'm a complete noob to Android source builds, but not new to developing. All of you putting your time into this AOSP build, I love you all! (In a way that only Dev's can understand HAH!)
[Droid Incredible Android Development] jermaine151:
Drumroll!! My build is finishing up and is at the final stage of building the classes.dex and apk files!!! Hopefully I get a chance to test booting it tonight.
[Droid Incredible Android Development] DiGi91:
oh time to cross my fingers!! :cool:

- DiGi
[Droid Incredible Android Development] jermaine151:
It'll take me a bit to flash it since I get off work in 30 minutes and need to put the ramdisk with the CM7 kernel, etc to see if it will boot. I'm stoked that it looks like it will finish though. I'll keep you posted.
[Droid Incredible Android Development] da_knowledge:
Congrats! Mine is done. Just trying to figure out how to zip it up to flash it.