Database Users

New Eris Vendor Tree

Ok, folks... Some very industrious devs have worked out a more complete vendor tree for the Eris at http://github.com/punk-kaos/vendor_htc_desirec. I've synced it into -
$AOSPsource/froyo/vendor/htc/desirec <-- this is the level that all of the files are at (i.e. everything under vendor_htc_desirec/ from the repo)
I'm a little lost as to where to go from there. I've looked at multiple vendor trees, and everyone seems to do things a little differently each time.
Can any of you point me in the right direction?
Thanks!
Kudos to Kaos, jamezelle, conap, vinylfreak89, & darchstar! You really rock.

Ok, so I copied it all under
$AOSPsource/froyo/device/htc/
Since that's where the dream, passion, etc. stuff is.
Now, I do a - 'source build/envsetup.sh' and it seems to find the desirec stuff.
including device/htc/desirec/vendorsetup.sh
including device/htc/dream/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/sapphire/vendorsetup.sh​
I'm stuck at what to do a 'lunch' on now. In the vendorsetup.sh, there's a 'cyanogen_desirec-eng'.
When I 'lunch cyanogen_desirec-eng', I get -
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/htc/desirec/froyo_desirec.mk]]: "vendor/htc/desirec/device_desirec-vendor-blobs.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?​
Getting closer!

Applause
I read you posts and see the questions you ask(that never seemed to get answered)and you will post some stuff you have learned all to help someone else who might want to get started dinking around with a pretty cool open source operating system. I applaud you for asking questions and when no one replies you answer it again yourself. You are the true definition of open source!

Im fairly new to this whole scene so excuse the "dumb" question but what exactly is a vendor tree?

You are stellar. I am going to try and port a froyo rom and then start to build something from the ground up. The questions you ask and the information you provide is invaluable. Want to put a rom project together?
Sent from my FroyoEris

good progress

paperweight said:
I read you posts and see the questions you ask(that never seemed to get answered)and you will post some stuff you have learned all to help someone else who might want to get started dinking around with a pretty cool open source operating system. I applaud you for asking questions and when no one replies you answer it again yourself. You are the true definition of open source!
Click to expand...
Click to collapse
Thank you. Many devs have helped me to learn all that I have learned. They are busy people just like most of us. Some of them probably don't pay attention to the forum that often. Some just have their own projects. Some hang out in IRC instead of looking in here. Actually, I've learned a lot in IRC, even when I just kick back and lurk. I really do want to get all of the info that I learn out here in the forum where 'noobs' are lurking. I've found that there is a certain level of detail that is available fairly easily with the search box. There's a point where it takes some real digging to figure things out. My hope is that it won't always be that way.
I tried manually taking all of the files and settings from the vendor tree and inserting them into SgtShultz. It didn't fix things. So, I'm thinking that either it really does have to be compiled in or this tree and AOSP Froyo don't quite mesh. Since there is some source code in the tree, that is most likely the issue.
I never could get the lunch command to work. That file is not there, and I'm still not sure what it should contain if I were to create it. Getting this to work would really help both of my other current projects...

MacShannon said:
Im fairly new to this whole scene so excuse the "dumb" question but what exactly is a vendor tree?
Click to expand...
Click to collapse
When you compile AOSP and/or variants from source, there is generally no device specific code - like drivers for instance. The vendor tree just sets everything up to add those proprietary files and settings into the mix, so that the resulting ROM will actually be usable. That's the idea anyway!

thanks for all the work you've been doing recently! i've followed the other thread as well... and am happy to say that i use (and appreciate) your work!

gnarlyc said:
When you compile AOSP and/or variants from source, there is generally no device specific code - like drivers for instance. The vendor tree just sets everything up to add those proprietary files and settings into the mix, so that the resulting ROM will actually be usable. That's the idea anyway!
Click to expand...
Click to collapse
I also have a "dumb" question.
If this is for the Eris, then why are the files under the "desire" name? I thought the eris was based on the hero platform or am I missing something obvious here?

gnarlyc said:
I'm a little lost as to where to go from there. I've looked at multiple vendor trees, and everyone seems to do things a little differently each time.
Can any of you point me in the right direction?
Click to expand...
Click to collapse
Have you tried the steps from this thread?
I am currently working through them, but had to stop because it's time for me to get ready for work.
I have gotten through the step where you copy the vendor files to the htc folder

sbarne3 said:
I also have a "dumb" question.
If this is for the Eris, then why are the files under the "desire" name? I thought the eris was based on the hero platform or am I missing something obvious here?
Click to expand...
Click to collapse
Great question! HTC's 'internal' name for the Eris is 'desirec' apparently. (Note that it's 'desirec' not 'desire'.) It was somewhat confusing when they came out with the Desire...

sbarne3 said:
Have you tried the steps from this thread?
I am currently working through them, but had to stop because it's time for me to get ready for work.
I have gotten through the step where you copy the vendor files to the htc folder
Click to expand...
Click to collapse
Looking at it now. Thanks!

gnarlyc said:
Ok, so I copied it all under
$AOSPsource/froyo/device/htc/
Since that's where the dream, passion, etc. stuff is.
Now, I do a - 'source build/envsetup.sh' and it seems to find the desirec stuff.
including device/htc/desirec/vendorsetup.sh
including device/htc/dream/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/sapphire/vendorsetup.sh​
I'm stuck at what to do a 'lunch' on now. In the vendorsetup.sh, there's a 'cyanogen_desirec-eng'.
When I 'lunch cyanogen_desirec-eng', I get -
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/htc/desirec/froyo_desirec.mk]]: "vendor/htc/desirec/device_desirec-vendor-blobs.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?​
Getting closer!
Click to expand...
Click to collapse
Did you run extract-files.sh? Iirc, the vendor_blob file is created when you run it.
Sent from my FroyoEris using XDA App

Resun said:
Did you run extract-files.sh? Iirc, the vendor_blob file is created when you run it.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Holy cow! I did not run it because I already have all of those files in place. It didn't occur to me to check and see if 'extract-files.sh' does something more than just pull the files.
Thank you.

Np, been working on my own, I've done the same thing about 10 times in the past week.
Sent from my Froyo Eris using XDA App

So, I commented out all of the 'adb pull' statements in the 'extract-files.sh' script, since the files are already there. Now I see that extract-files was creating the ...blobs.mk file under vendor/htc/desirec instead of device/htc/desirec. So, I changed that and ran it all again...
cd $AOSPsource/froyo
device/htc/desirec/extract-files.sh
source build/envsetup.sh
lunch cyanogen_desirec-eng
And this gives me -
build/core/product_config.mk:192: *** vendor/htc/desirec/froyo_desirec.mk: PRODUCT_NAME must be unique; "desirec" already used by device/htc/desirec/froyo_desirec.mk vendor/htc/desirec/froyo_desirec.mk . Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?​
Here I go again! Thanks for all of the help. I really want to get this working, so that it can be scripted.

gnarlyc said:
So, I commented out all of the 'adb pull' statements in the 'extract-files.sh' script, since the files are already there. Now I see that extract-files was creating the ...blobs.mk file under vendor/htc/desirec instead of device/htc/desirec. So, I changed that and ran it all again...
cd $AOSPsource/froyo
device/htc/desirec/extract-files.sh
source build/envsetup.sh
lunch cyanogen_desirec-eng
And this gives me -
build/core/product_config.mk:192: *** vendor/htc/desirec/froyo_desirec.mk: PRODUCT_NAME must be unique; "desirec" already used by device/htc/desirec/froyo_desirec.mk vendor/htc/desirec/froyo_desirec.mk . Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?​
Here I go again! Thanks for all of the help. I really want to get this working, so that it can be scripted.
Click to expand...
Click to collapse
Shouldn't have it in both, should only be in the device subfolder.

Resun said:
Shouldn't have it in both, should only be in the device subfolder.
Click to expand...
Click to collapse
Thanks again! I know better than to do a drive by like that. I spent two minutes testing, posted the results, and then left to run errands for most of the day.
I'll try again when i get home.

so ive patched up the vendor on my computer (some files were pointing to devices/htc/desirec) and when i finally got it to behave i ran into something worse..
Code:
build/core/combo/TARGET_linux-arm.mk:39: *** Unknown ARM architecture version: armv6. Stop.
i ended up changing the lunch to desirec-eng because it wouldnt resolve the product name... im not a dev but i sure have a nose for this sort of thing, and help or an armv6.mk file would be appreciated

[SOLVED]Becoming one of those ROM/Kernel developers?

Hi there. I am interesting to be one of those ROM and Kernel developers. But I do not have any knowledge and skills in these tweaking and so on. I need to acquire those basics. (i.e. learning from scratch)
My question is, where can I learn all those knowledge and skills? I can't find anything about this in XDA website. But I do believe such guide should be available within XDA.
Thanks. =)

superstick1 said:
Hi there. I am interesting to be one of those ROM and Kernel developers. But I do not have any knowledge and skills in these tweaking and so on. I need to acquire those basics. (i.e. learning from scratch)
My question is, where can I learn all those knowledge and skills? I can't find anything about this in XDA website. But I do believe such guide should be available within XDA.
Thanks. =)
Click to expand...
Click to collapse
Head over to chef central! All the getting started info is in there. If as you say your knowledge is basic, then I'd recommend starting with ROM cooking via DSIXDA's kitchen before progressing onto anything else.
Regards.

Thanks lynxboy!

[Q] [Rom Development] What should i Know ?

Hi everyone, i am graduating in T.I here in Brasil.
I know C / C++ Programming, Java (Standard and Android Programming aswell).
I was wondering,what should i need to start helping all great developers like Kyrillos,Rudolf,Apolo and their teams to develop those custom roms.
Also,how hard it is ?
Sorry if this is at the wrong forum,but i hope i can get some answers before someone closes it
Thanks in advance !

marcelloLins said:
Sorry if this is at the wrong forum,but i hope i can get some answers before someone closes it
Thanks in advance !
Click to expand...
Click to collapse
Lol.
Post in general section bro. You don t need extensive C/C++ or Java unless you developing kernel or editing, making new frameworks and apks.
Post in general section. No one will close it.

marcelloLins said:
Hi everyone, i am graduating in T.I here in Brasil.
I know C / C++ Programming, Java (Standard and Android Programming aswell).
I was wondering,what should i need to start helping all great developers like Kyrillos,Rudolf,Apolo and their teams to develop those custom roms.
Also,how hard it is ?
Sorry if this is at the wrong forum,but i hope i can get some answers before someone closes it
Thanks in advance !
Click to expand...
Click to collapse
Hey y dont u do a search man...
There's already a thread on tutorial for custom rom. Video by rudolf895. Its clearly explained.

dhirend_6d said:
Lol.
Post in general section bro. You don t need extensive C/C++ or Java unless you developing kernel or editing, making new frameworks and apks.
Post in general section. No one will close it.
Click to expand...
Click to collapse
Hm, what exactly makes those custom ROMS faster than the stock ones ?
My bet is that the little ( and lower level , like assembly , C ) tweaks that make them faster.
Am i Wrong ? I really dont know,this is my only shot to be honest
Thanks again !

actually custom roms are nothing else then stock with a litle photoshop, some added/removed apks and repacked. they dont get realy much faster than a stock rom except if they contain a custom kernel, where the full potential of customization lies. with your knowledge you should concentrate on kernel development, there is a thread here describing all needed to get your own kernel up and running, have a look at the fugumod and the g3mod kernel thread to see what goals are already accieved and find your own customizations to make the g3 better. also u could pick up on the graphics driver project posted here somewhere, iirc nobody took the plunge yet to do this, and youd be the hero for many of us if u get it runing...
kernel development:
http://forum.xda-developers.com/showthread.php?t=1186409
Graphics driver stuff:
http://forum.xda-developers.com/showthread.php?t=1104222

[Discussion] [Call for Devs] - Trying to make the Project Treble easier for everybody

As many might know, thanks to Project Treble the work needed to port ROMs has been greatly reduced.
Right now everything is still a bit messy around treble, with people searching in every possible forum (even on ones for other devices) for an image, discussing things not in relation with the topic's original device and just making thing cluttered and hard to find.
We also can see that the great thread put forward by phhusson begins to get the same treatment with people from many devices in the same thread asking device-specific questions (and even questions about devices without Treble-support) when phhusson's initial idea seems to have been to build a base image which could be used / modified for each device. Essentially giving a golden base which only needs small, device-specific, modifications.
Coming back to the title. I want to propose device-specific Treble - Threads. Permitting to let GSI (Generic System Image) threads clutter-free and development oriented, while these type of threads can be used to discuss problems related to specific devices. From what can be seen right now (through the eyes of a non-dev) most of the time only small modifications are needed, which could be managed with a custom kernel or a custom zip containing all fixes.
Hoping to find a way, together, to get Treble even better for us and making work easier for developers.
Feel free to discuss

I agree. Device-specific forums would help with reporting bugs, and finding GSIs for certain devices.

Agreed!

I totally agree, people should acknowledge this and start making a move

Treble development, imho, doesn't need to be branched out for all the specific devices. That's just not it's forte, it's mandate is to be generic, not specific.

Considering some issues may be affecting multiple devices, how about having a distinct support thread, separate from the main development thread, for every GSI?
I feel a threads for every device may be unmanageable, and actually counterproductive once such threads grow.

I've started a Treble Megathread for the Huawei P10 but it's not gaining much traction.
Treble is all well and good but if nobody is actually using it (Phh's RR v3 has only had ~1800 total downloads) then there's going to be very slow progress!

Making treble-enabled devices should just go in the respective device's development subforum that (probably) already exists....
---------- Post added at 06:03 AM ---------- Previous post was at 06:02 AM ----------
Silently said:
I've started a Treble Megathread for the Huawei P10 but it's not gaining much traction.
Treble is all well and good but if nobody is actually using it (Phh's RR v3 has only had ~1800 total downloads) then there's going to be very slow progress!
Click to expand...
Click to collapse
It's still early days yet. It will gain traction for sure.

I'm a rookie... Inwant to compile a custom rom from source and make it a treble rom that everyone can use. Can anyone suggest me tutorials or stuff like that. I've never compiled before. Any help would be appreciated.

Rifat Rezwan said:
I'm a rookie... Inwant to compile a custom rom from source and make it a treble rom that everyone can use. Can anyone suggest me tutorials or stuff like that. I've never compiled before. Any help would be appreciated.
Click to expand...
Click to collapse
If you cant search a bit in the xda forum or search in the internet... Then I think you wont be able to compile your own rom and fix all the bugs.

CosmicDan said:
Making treble-enabled devices should just go in the respective device's development subforum that (probably) already exists....
---------- Post added at 06:03 AM ---------- Previous post was at 06:02 AM ----------
It's still early days yet. It will gain traction for sure.
Click to expand...
Click to collapse
the problem is not that nobody used it, the problem is that we do not know how to install As well as I have had failures when trying

albertovazquez said:
the problem is not that nobody used it, the problem is that we do not know how to install As well as I have had failures when trying
Click to expand...
Click to collapse
So those people that have used it should write a guide on that devices' subforum. There's no need to clutter up the Treble subforum with device-specific things.

albertovazquez said:
the problem is not that nobody used it, the problem is that we do not know how to install As well as I have had failures when trying
Click to expand...
Click to collapse
It's easy:
Factory reset
Boot fastboot mode
In adb type
fastboot flash system *systemimgname*.img
The.n type fastboot reboot and wait

matze19999 said:
If you cant search a bit in the xda forum or search in the internet... Then I think you wont be able to compile your own rom and fix all the bugs.
Click to expand...
Click to collapse
Your tip was so helpful! thank a lot!

It's hard work to make a good rom. It takes much time and you have to know much about Linux / how a kernel works / what libraries do and such things. It isn't something you learn in some days.

Agree! But there is bugs that still didnt fixed by phhusson in aosp. Such as lag when opening app from recents tab (Huawei). Btw its fixed by in Pixel Experience and in Havoc OS but not in the original one ( base rom ) . Treble need some work to be perfect. Remember to old Cyanyogen mod? That one is epic!

matze19999 said:
It's hard work to make a good rom. It takes much time and you have to know much about Linux / how a kernel works / what libraries do and such things. It isn't something you learn in some days.
Click to expand...
Click to collapse
Its not hard. Nobody is willing to show the way. Thats the thing. Nothing is hard.

Rifat Rezwan said:
Its not hard. Nobody is willing to show the way. Thats the thing. Nothing is hard.
Click to expand...
Click to collapse
nothing is hard? wtf are you talking about..

matze19999 said:
nothing is hard? wtf are you talking about..
Click to expand...
Click to collapse
We have a clown over here.

Rifat Rezwan said:
We have a clown over here.
Click to expand...
Click to collapse
Please stop writing such bull****.
When you really think building a rom from source, show what you can. You think it's really sooo easy to fix all the bugs? To get the hardware working?
Developers here on xda need weeks to release a stable build of a rom and you call it easy?
I think you're the clown bro.

Any possible way to install TWRP on OOS 11 (OP8P)?

Title says it all, I was trying to install TWRP on OOS 11 but it bricked my device , I tried the same way on OOS 10 and it worked perfectly , any idea if it's possible to install TWRP while having OOS 11 (for OP8P)?

TWRP is not available for A11.

No it isn't, check their thread for updates.
You have another thread in Q+A, please get this one closed.

Is there any way to flash OOS 11 ROM from TWRP? I don't know if the ROM would still fail using this method. Anyone want to chime in?

android86.ad said:
Is there any way to flash OOS 11 ROM from TWRP? I don't know if the ROM would still fail using this method. Anyone want to chime in?
Click to expand...
Click to collapse
There's a thread dedicated to TWRP, all your answers are there.
In short the answer is - not yet.

[Thread Cleaned]
Good day everyone!
Advertising recovery distributions that come without source code should not be done on XDA. As these "off the grid" TWRP iterations are closed, we cannot verify if they can be trusted. We strongly advise to stick with proper distributions on our platform in the interest of your own safety/privacy. Doing research before buying a device can prevent a lot of frustration.
And there's no need to attack each other over something like this. I'm sure we all have more pressing matters to worry about right now. Which in hindsight may also be a catalyst for reacting a bit harsher than usual. Understandable. But let's try to get along anyway ^_^
Stay safe!
Timmy
Forum Moderator

Timmmmaaahh! said:
[Thread Cleaned]
Good day everyone!
Advertising recovery distributions that come without source code should not be done on XDA. As these "off the grid" TWRP iterations are closed, we cannot verify if they can be trusted. We strongly advise to stick with proper distributions on our platform in the interest of your own safety/privacy. Doing research before buying a device can prevent a lot of frustration.
And there's no need to attack each other over something like this. I'm sure we all have more pressing matters to worry about right now. Which in hindsight may also be a catalyst for reacting a bit harsher than usual. Understandable. But let's try to get along anyway ^_^
Stay safe!
Timmy
Forum Moderator
Click to expand...
Click to collapse
Censorship here now? Wow

Navyvet63 said:
Censorship here now? Wow
Click to expand...
Click to collapse
Always has been here. Nothing new. Post's get deleted all the time for language, slander, off topic, sharing software that is closed source and warez. Not sure why you are surprised.

Navyvet63 said:
Censorship here now? Wow
Click to expand...
Click to collapse
No. GPLv3 compliance. We love not being sued

Navyvet63 said:
Censorship here now? Wow
Click to expand...
Click to collapse
Really???
FYI, if it's "developed" by someone on XDA developers, then it's fine (for the most part)
But if it's software that is not developed and freely shared here, like warez eg: apks for apps you haven't paid for or can only be obtained from a said location.
Or like in this case a developers work who is not from XDA and we do not have permission to share then no, you can't share it here or indeed anywhere legally unless you have permission to.
In regards to the TWRP in question I believe they've been approached to collaborate and have plainly said no, so it can't be shared here..
XDA have a responsibility to adhere to these decisions..
I get it's frustrating and we all know what goes on behind the curtain, no one here's thick, but just play the game.
More to the point, I thought the guys were making headway on our TWRP anyway..
Couple that with the fact that you can do pretty much anything without TWRP and it's a non starter really arguing about it anyway