yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] gnarlyc:
It should put everything in 'out/target/product/desirec' and not 'out/target/product/generic'. Do you have a system folder in there? If so, do you have 'out/target/product/desirec/system/use/keychars/desirec-keypad.kcm.bin' ?
[Droid Eris Android Development] Sjflowerhorn:
nope lol i knew i messed something up along the way lol
[Droid Eris Android Development] gnarlyc:
That's ok. I'm not getting anything in either folder due to the error. If I compile without the vendor tree, I at least get a working ROM under 'generic'. We will get this, and then write up a step by step.
[Droid Eris Android Development] Sjflowerhorn:
i havent had any time lately with getting ready for vacation and working on dsm after dsm after dsm atfer dsm lololol did i leave any dsm's out for today, well at least biz is boomin! after the Shootout on the 14-15th then ill have plenty of time to get back to things. lol im kinda hoping you have it figured out by then but im all game to help get this worked out for us up-and-comers.
[Droid Eris Android Development] sbarne3:
I know the feeling... I REALLY want to be working on this, but my schedule just hasn't allowed it lately... these 70-80 hour work weeks are about to kill me... But the end is in site!!
[Droid Eris Android Development] swordrune10:
oh ya... forgot bout this x.x ya i got it to build finally with it recognizing my baseband.. but! its moving so slow its not even usable... how can i fix that?
[Droid Eris Android Development] bubba1114:
im having trouble extracting files with ./extract-files.sh. this is what im getting

[Tyler@Tyler desirec]$ ./extract-files.sh

error: device not found

chmod: cannot access `../../../vendor/htc/desirec/proprietary/akmd': No such file or directory

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

[Tyler@Tyler desirec]$

can someone please tell me what im doing wrong?
[Droid Eris Android Development] Conap:
Is your phone plugged in with usb debugging on? do you have sdk installed and are you able to run adb commands? the computer is not seeing your phone....
[Droid Eris Android Development] bubba1114:
.... wow really feel dumb. should of realized that when it said devices cannot be found. thanks
[Droid Eris Android Development] bubba1114:
lol ok one more question then i should have it.

build/core/combo/TARGET_linux-arm.mk:39: *** Unknown ARM architecture version: armv6. Stop.

does anyone know how to fix this? i seen it was posted in earlier postings but i was unable to see a fix for it?

Thanks in advance
[Droid Eris Android Development] Conap:
Look at the BoardConfig.mk or a name close to that in the vendor tree and look for a line that says TARGET_ARCH_VARIANT := armv6 and change it to say TARGET_ARCH_VARIANT := armv5te
[Droid Eris Android Development] bubba1114:
thank you so much. truely a life saver lol
[Droid Eris Android Development] Funnyface19:
U know what's funny tho desire spelt backwards is erised so the first 4 letters are eris
[Droid Eris Android Development] bubba1114:
hmmm well you can kill me now or later but got another question. lmao google didnt help me with this one.

build/core/base_rules.mk:128: *** vendor_htc_desirec/recovery: MODULE.TARGET.STATIC_LIBRARIES.librecovery_ui_desirec already defined by device/htc/desirec/recovery.

i looked under base rules and couldnt find anything that looks the same or remotely the same. lol so what would this be under? and what would i have to change?
[Droid Eris Android Development] Resun:
It means you have 2 of the same files that are attempting to compile the same thing. Just remove the one in ../device/htc/desirec/recovery.
[Droid Eris Android Development] bubba1114:
sweet thanks that worked.
[Droid Eris Android Development] gnarlyc:
So, can one of you who got this all to work start from the beginning and let the rest of us in on how you do it? I haven't looked at it in a few, but I'll gladly dig into it again.

Nothing too detailed is needed, since we get the idea. Just some pointers or an overview of steps would be wonderful.

Thanks!

Of course, feel free to ignore me too. Or tell me to search or read the whole thread or buzz off or whatever dude.
[Droid Eris Android Development] swordrune10:
i may have gotten somewhat far on my vendor tree for this, but idk how to get any farther.. nor do i really want to x.x .. idk either how to tell u how to get this stuff to work, all i can really do is give u my vendor tree.. all pretty much works, only two errors that i know of.. softlight keys not working, when wifi gets turned on the whole rom is sllooowwww.. oh! and for some reason i can only build using aosp, cyanogen doesnt seem to work, but i do believe thats not my vendor trees fault x.x
[Droid Eris Android Development] bubba1114:
when any of you were compiling the trees (meaning running the make code) did any of you have it get stuck on target Dex: framework. ive tried running 4 different times. i even changed from eng to user and it still happens to get stuck at the same point? any fix for it?
[Droid Eris Android Development] Conap:
what do you mean by stuck? does it give an error? sometimes you have to scroll up a little ways to see the error....I don't think this vendor tree was quite finished so it probably needs a few changes to build properly.
[Droid Eris Android Development] bubba1114:
its been "loading" it for the past 2 hours. like it hits target Dex: framework and then wont go past it. it doesnt throw any codes or anything just sits there
[Droid Eris Android Development] Conap:
Thats odd.....have you tried closing the terminal then go back and start the build again. Do not do a make clean and it will pick up where it left off and see if it goes past then. Honestly I've never had that happen while compiling any rom so not sure what could cause it....
[Droid Eris Android Development] bubba1114:
ive closed it and started it again. So should i do a make clean or no?

so i make clean it. and it came up with pry about 40 different errors and most of them are about java. idk if you want me to post what its saying but i wont unless you guys want to see what its saying
[Droid Eris Android Development] Conap:
make clean give's you java errors? are you sure your system is set up right to compile this? you can post the errors if you want but I can't promise I'll know what they mean...
[Droid Eris Android Development] Conap:
definitley seems java is not set up correctly...double check your paths...i use java 1.6.20 and compile froyo a couple times a day with no issues. manually delete everything in the out/target/product/desirec/ folder and try it again.
[Droid Eris Android Development] bubba1114:
I used the Java configure code to change the main Java. Is there other codes I have to run to change the any littler Java process
[Droid Eris Android Development] Conap:
I don't know about that I entered it into the bash.rc myself to set up java...i'm pretty new to linux so not super sure what you need to do there...of course if it started to compile at first something is working.
[Droid Eris Android Development] bubba1114:
Lmao yeah. I'm pretty new to Linux to but surfing the web helped me get where I'm at now
[Droid Eris Android Development] bubba1114:
hmmm well i changed the java to 1.6.0 and 1.5.0 and it still gives me all the same errors? im lost now
[Droid Eris Android Development] gnarlyc:
Did you ever have any luck?

I've started from scratch again, now that most other distractions are out of the way. This is still holding up two other projects for me, so I want to get it working.
[Droid Eris Android Development] bubba1114:
No actually I didn't. Just got done with the process of switching from Ubuntu 10.10 to Linux mint 9 and working a ton to be able to attend the Google I/O 2011. But should be getting time all weekend to jump in to it. Ill inform everyone of what has happened and if I am able to get it
[Droid Eris Android Development] gnarlyc:
Cool. Yeah, let us know.

I'm building a script as I work kinks out, but am still in the early stages. At least I've done it before (well, unsuccessfully!) and read more about it now.
[Droid Eris Android Development] gnarlyc:
Ok. I managed to stay on task for a bit. Here's the current version of my script. It does produce a out/target/product/desirec folder, but it's incomplete. Looking at the errors now.

cd $KITCHEN_ROOT/source/projects/froyo/device/htc/

rm -r desirec/

git clone http://github.com/punk-kaos/vendor_htc_desirec.git

mv vendor_htc_desirec/ desirec

cd desirec/

perl -pi -e 's/armv6/armv5te/g' BoardConfigCommon.mk

mkdir proprietary

cp $KITCHEN_ROOT/proprietary.zip proprietary/

cd proprietary

unzip proprietary.zip

cd ../

perl -pi -e 's/adb/#adb/g' extract-files.sh

perl -pi -e 's/\/vendor\/htc/\/device\/htc/g' extract-files.sh

./extract-files.sh

cd ../../../

rm -r out/target/product/desirec

source build/envsetup.sh

lunch desirec-eng

make -j4​
[Droid Eris Android Development] gnarlyc:
So, here's my script now. It gets much closer. For now the script mods extract-files.sh, etc. each time, however I've forked the tree. If it turns out that I need to make these changes every time for this to work with AOSP (non-CM6), then I'll just start using the fork instead of the main tree unless someone else comes up with a better solution. I now have an out/target/product/desirec folder with desirec specific stuff in there! It's not complete, but it errors out a lot farther into the compile process than before.

cd $KITCHEN_ROOT/source/projects/froyo/device/htc/

rm -r desirec/

git clone http://github.com/punk-kaos/vendor_htc_desirec.git

mv vendor_htc_desirec/ desirec

cd desirec/

perl -pi -e 's/armv6/armv5te/g' BoardConfigCommon.mk

mkdir proprietary

cp $KITCHEN_ROOT/proprietary.zip proprietary/

cp $KITCHEN_ROOT/vold.fstab .

cp $KITCHEN_ROOT/wlan.ko .

cp $KITCHEN_ROOT/kernel .

cp $KITCHEN_ROOT/brf6350.bin .

cd proprietary

unzip proprietary.zip

mkdir -p $KITCHEN_ROOT/source/projects/froyo/vendor/htc/desirec/proprietary

cp * $KITCHEN_ROOT/source/projects/froyo/vendor/htc/desirec/proprietary

cd ../

perl -pi -e 's/adb/#adb/g' extract-files.sh

perl -pi -e 's/\/vendor\/htc/\/device\/htc/g' extract-files.sh

perl -pi -e 's/TARGET_BOOTLOADER_LIBS := \\/#TARGET_BOOTLOADER_LIBS :=\\/g' BoardConfigCommon.mk

perl -pi -e 's/libboot_board_desirec \\/#libboot_board_desirec \\/g' BoardConfigCommon.mk

perl -pi -e 's/libboot_arch_msm7k \\/#libboot_arch_msm7k \\/g' BoardConfigCommon.mk

perl -pi -e 's/libboot_arch_armv5te/#libboot_arch_armv5te/g' BoardConfigCommon.mk

perl -pi -e 's/vendor/device/g' extract-files.sh

./extract-files.sh

perl -pi -e 's/vendor/device/g' device_desirec-vendor-blobs.mk

cd ../../../

rm -r out/target/product/desirec

source build/envsetup.sh

lunch desirec-eng

update-java-alternatives -s java-1.5.0-sun

make -j4

update-java-alternatives -s java-6-sun​

I think one of those lines is changing the name of the blobs file, and then I'm trying to mod the blobs file later... I'll have to look at that. Does any of this make sense? :)
[Droid Eris Android Development] darchstar:
here you go: http://github.com/darchstar/android_device_htc_desirec

the sed'ing in the commit is a joke, but it kinda is all you had to do besides getting the right kernel
[Droid Eris Android Development] bubba1114:
lolwell hell you got farther then i did when it was failing. i got all the way to cd ../../../ then it failed saying that doesnt exist then all the java codes were thrown after that. lol
[Droid Eris Android Development] gnarlyc:
Thanks darchstar. The joke is probably not far from the truth. In 3-4 months, I plan to make a ROM that will work on both the Hero and Eris, since they are so close. Sshhh. Don't tell anyone though. I don't want someone to take my idea and do it first.

One of the issues that I have had with Froyo AOSP and vendor trees is the difference between device/htc/desirec and vendor/htc/desirec. So, your extract-files.sh is actually going to give me the same problem. I'm still looking to use my fork instead, but all of the kinks are definitely not worked out. Thanks for putting it together though. Your list of needed proprietary files is different than the other list, so that tells me that maybe non-CM6 builds need some different files. I'll test once it's worked out.
[Droid Eris Android Development] darchstar:
br0, you haven't even tested it... test it before saying it wont work cuz thats based off my heroc device tree which is based off the supersonic device tree which is based off the official passion device tree which is in aosp froyo source code. the only thing you would need to do to get it to compile with cyanogenmod or aosp would make a androidproduct and vendorsetup so you can lunch it

also, about merging heroc and desirec, it wont happen, different kernel base for the boot.img
[Droid Eris Android Development] Conap:
This tree will work. Its pretty much what the tree i use looks like beings that I based mine off Darchstars tree(http://github.com/Conap30/android_device_htc_desirec). I am attaching the other files needed to compile cyanogen just copy them to the corresponding folders in the cyanogen source.
[Droid Eris Android Development] darchstar:
if you wouldn't mind, could you give me the output of uname -rv with the kernel in my device tree
[Droid Eris Android Development] gnarlyc:
So, I need to make an AndroidProduct.mk and VendorSetup.mk in addition to the files that are already there? Well, that might be what is needed to get things to work then. That would be great, because I've now tested with your repo and I get the same results as before due to what I mentioned in the post above.

The comment about making a 'universal' ROM for both devices was mostly a joke in response to your sed joke. However, if there is a way in the update(r)-script to detect the device and flash the appropriate boot.img, then it might work. I am aware that the kernels are different.

Thanks for jumping in here, by the way. There are several of us who really want to understand this part and get it working, so that we can start contributing 'at the next level' so to speak.
[Droid Eris Android Development] Conap:
would I have to compile the whole rom? that command needs to be run with the kernel running on the phone right? I use my own kernel....could i make your kernel a zimage to boot it?
[Droid Eris Android Development] gnarlyc:
Thanks a bunch Conap! I'll take a look at these and see if I can figure out what I'm doing wrong. I really appreciate you jumping in here and helping us 'compile from source noobs'.
[Droid Eris Android Development] darchstar:
fastboot it, idc. i just wanna know what that outputs as on someones eris
[Droid Eris Android Development] gnarlyc:
So darchstar got me thinking (and you didn't think it was possible...). I really need to follow through all of these scripts and see what they are doing and understand it.

build/envsetup.sh has this near the end -

# Execute the contents of any vendorsetup.sh files we can find.

for f in `/bin/ls vendor/*/vendorsetup.sh vendor/*/build/vendorsetup.sh device/*/*/vendorsetup.sh 2> /dev/null`

do

echo "including $f"

. $f

done​

That seems to be where it looks for vendor trees. Note that it doesn't run 'vendor/*/*/vendorsetup.sh', which to me would seem like that's why it misses 'vender/htc/desirec/vendorsetup.sh' but it does find 'device/htc/desirec/vendorsetup.sh'

So, that's great. I still don't understand how it works for everyone else and not me without munging some files first, but I'm getting there. And, I'll continue to post my progress here so that everyone can see how little I actually know and learn with me as that changes. That is why I'm here, in case you can't here the voices too. :)
[Droid Eris Android Development] Conap:
there shouldn't be a vendor/htc/desirec/vendorsetup.sh....it should pick up the vendor/cyanogen/vendorsetup.sh which has the cyanogen_desirec option.
[Droid Eris Android Development] Conap:
2.6.29.6-cyanogenmod #2 PREEMPT Fri Aug 27 18:11:07 CDT 2010

thats the output if you didn't get my pm....also soft keys don't work at all but nice to see that your kernels is so close to working on our phones....
[Droid Eris Android Development] gnarlyc:
So, it seems to me that I am syncing the vendor tree repo in a different spot than you. I'm putting it in this folder:

$KITCHEN_ROOT/source/projects/froyo/device/htc/desirec

I WAS putting it here: $KITCHEN_ROOT/source/projects/froyo/vendor/htc/desirec

I'll try putting it one folder up. That would match with what the envsetup.sh script is doing, so that might just work for me.

Thanks again!
[Droid Eris Android Development] Conap:
yes the vendor tree should go in device/htc/ it will already have tree's there for heroc and other phones so just add the desirec tree. the extractfiles.sh scipt and setupmakefiles.sh scripts will create the needed files in vendor/htc/desirec. then download the files i put up here and copy them to the vendor/cyanogen corresponding folders to how I have them in the file.
[Droid Eris Android Development] gnarlyc:
Thank again. It's really helpful to get the steps that work for you. I'm not syncing CM, so there's no heroc in there, but there are dream, etc.

So, from what you are saying, the repo should be synced to device/htc, and the the proprietary files will get copied under vendor/htc/desirec. Interesting.

I think that having stuff in several different places is confusing at first. I was just assuming that the files would either be under device/htc or vendor/htc, not that some files would be under both. (Or get created under the other one by the scripts in the first...) That was the initial confusion with this whole thing. I would get errors about files needing to be in one folder structure or the other and them not being there, hence the modding of the extract-files.sh and such. And, the vendor trees that I am pulling down to test are geared for CM, but I'm syncing Froyo AOSP.

I guess that assumed that all of the device specific files would be neatly under one folder structure. It all goes back to me not digging into what is actually going on FIRST before trying to get this to work. Onward again!
[Droid Eris Android Development] Conap:
well your assumptions would have been correct if you were doing a 2.1 build but it was changed in the 2.2 build. if you are just doing aosp you probably won't need the extra files I uploaded....
[Droid Eris Android Development] gnarlyc:
Thanks again Conap.

In an effort to really learn what I'm doing, I've started over with the dream vendor tree from Froyo AOSP and copied it. After modifying it enough, I get a partial desirec build. All of the settings need to be worked out, but I'm quite happy with the start that I have on this.

http://github.com/gnarlyc/desirec.git

(Like we need another vendor tree!)

So, now my script looks like this:

cd $KITCHEN_ROOT/source/projects/froyo/device/htc

#included for testing

rm -r desirec/

rm -r $KITCHEN_ROOT/source/projects/froyo/out/target/product/desirec

git clone git://github.com/gnarlyc/desirec.git

cd desirec/

./extract-files.sh

cd ../../../

source build/envsetup.sh

lunch full_desirec-userdebug

make -j4​

Now, that's a lot shorter than my previous script!
[Droid Eris Android Development] gnarlyc:
I now have it compiling completely without errors, but the resulting ROM will not boot. The logcat give libandroid_servers.so errors.

Here's my current script.

cd $KITCHEN_ROOT/source/projects/froyo/device/htc

#included for testing

rm -r desirec/

rm -r $KITCHEN_ROOT/source/projects/froyo/out/target/product/desirec

git clone git://github.com/gnarlyc/desirec.git

cd desirec/

mkdir -p $KITCHEN_ROOT/source/projects/froyo/vendor/htc/desirec/proprietary/

cp $KITCHEN_ROOT/prop/* $KITCHEN_ROOT/source/projects/froyo/vendor/htc/desirec/proprietary/

./extract-files.sh

cd ../../../

source build/envsetup.sh

lunch full_desirec-userdebug

make -j4​

Here are the files in my $KITCHEN_ROOT/prop/ folder. These are the same files that my extract-files.sh tries to grab.

01_qcomm_omx.cfg

akmd

AudioFilter.csv

AudioPara4.csv

AudioPreProcess.csv

brf6350.bin

copybit.msm7k.so

desirec-keypad.kcm.bin

Fw1251r1c.bin

gps.conf

libaudio.so

libaudioeq.so

libaudiopolicy.so

libaudiopolicygeneric.so

libcamera.so

libGLES_qcom.so

libGLESv2.so

libgps.so

libhgl.so

libhtc_acoustic.so

libhtc_ril.so

libmm-adspsvc.so

liboemcamera.so

libOmxCore.so

libOmxH264Dec.so

libOmxMpeg4Dec.so

libOmxVidEnc.so

libopencorehw.so

libqcomm_omx.so

libspeech.so

lights.msm7k.so

melfas-tsi-ts.kcm.bin

sensors.desirec.so

tiinit_5.3.53.bts

tiwlan.ini​

I'm going to take a break for a bit and read this thread - http://xdaforums.com/showthread.php?t=704561 in its entirety. It appears to have some good info that might be helpful.
[Droid Eris Android Development] Conap:
which vendor tree are you using? you have one you made on github and one forked that vynylfreak89 was working on?
[Droid Eris Android Development] gnarlyc:
I'm using mine (git://github.com/gnarlyc/desirec.git). It's still a work in progress, obviously. I built it from the dream tree in Froyo AOSP.
[Droid Eris Android Development] Conap:
You might want to try adding the prelink-linxux-arm-desirec.map from my vendor tree...you would have to refference the make files to use it instead of the defualt....i know there were some issues in the begginning of building Froyo like you are describing because some of the prelinks of the libs changed in froyo. I just used the prelink.map from heroc tree. Just something to look at...The thread you linked above does have a lot of good info in it and does address your issue some. If I remember correctly it has something to to with the libaudio.....
[Droid Eris Android Development] gnarlyc:
Thanks a bunch. I'll take another look after I finish reading the thread. This is going to work, and I'm going to know why! :)

I don't think we have a good, clean, basic, working Froyo AOSP ROM. It would be nice to have one as an option, even though CM6-based ROMs are really nice.