Database Users

Ice Cream Source Build?

Hi,
i know that the build would be slow as hell but has anyone compiled ICS for the G1? just for trying it ?
i would like to try it myself but i have no clue on how and from hat i`ve heard my computer would take ages to build it

It's done for droid eris, it can be ported to G1.
http://forum.xda-developers.com/showthread.php?t=1352170

Porting would be inefficient when it can be built from source.
Unfortunately I can't do neither
Sent from my GT-I9100 using XDA App

Ice Cream Sandwich Build Help
As soon as the source was released I was thinking about trying to build it for "old reliable" (my nickname for my old G1). I know it would be slow as mud but I still want to give it a try. Problem is I've never compiled the source of Android before so I would be going in blind. I've read the info at source.android.com so I have somewhere to start. If anyone has any other guides/tutorials on how to build Android for a device then I would be really appreciative. I'm a Computer Science major so don't be afraid to throw a little code at me either. I'll include the details of my phone below in case anyone needs it.
HTC Dream
SPL: HBOOT-1.33.2005 (DangerSPL)
Radio: 2.22.19.261
OS: CyanogenMod 6.1 (Android 2.2.1)

You can have a look at Terry' ezGingerbread thread. Here he explains what to do to compile his ezGingerbread from the sources. Principally compiling ICS is the same, but you need to exchange / modify the manifest to your needs.
Sent from my Gingerbread on Dream using XDA App

Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App

hyperspace290 said:
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
It's almost stock, but there are some projects from CM included and some he cloned from CM or from other sites and manages them by himself. Details you can see it in his manifest.xml located in the .repo directory. The manifest defines, what projects are to be included and what branch you want to use for these projects.

You will not want my manifest for ICS (at least unless I make an ICS branch myself)
The reason is you will want to use the ICS git repos and not the GB git repos (original or cloned by me)
That said if you are new to building an android rom look at the structure using ezgb some, and build ezgb, then when you understand the structure clone ICS from aosp (see info on source.android.com) and create your own manifest from that including cloned git repos you need from ezgb with any addtl modifications required.
The first thing is:
* Git is the source control for all parts of android, however many (well over 200) git repos are used in ICS
* Repo is a tool (python script with plugins pulled from its own git repo) for maintaining all of the git repos used in an android build, and creating the true tree of repos needed for the work directoy.
* Manifest is a special git repository with default.xml (and sometimes other manifest xmls) used by the repo script to find all the projects other git repositories, as well as what branch/commit to checkout to the work directory.

Thanks for the advice guys. Glad to see the little G1 is still getting some love. I think I'll start by building ezGingerbread to get the handle on the build process for Android and at least get up to 2.3.
If anyone knows what kinds of modifications are normally needed for a port like this then I would appreciate the help. Is it normally just editing some config files or would I have to dive into the code? Thanks again.
Sent from my DROID3 using XDA App

Looks like someone has beaten me to the punch. Anyone interested shout go have a look at this thread: http://forum.xda-developers.com/showthread.php?p=19648827

not exactly.
that is a port from a source-build for the hero
but very close
looks like the dev is trying to make a source build for the dream.
you could contact him so you can work together

Really get the cm9 source, pull forward the dream/sapphire device trees from cm7 (or firerats port of that) and it ought to be alright.
There seems little in the way of true cm bits at current (sure to change soon) but most of the hardware backwards compatibility patches are alredy in cm9 from the looks of it.. for all I know this is a cm9 build since aosp has no hero device tree out of box.

I was going to reply to that thread but since I'm still considered new I can't post to development threads. I guess I will PM the dev later to let him know I'm interested in helping him out.
Why would you build for another device if the dream has built into AOSP? Doesn't make a whole lot of sense to me unless they flat out took out the board file in ICS but you could easily put it back by pulling it from an earlier revision.
Sent from my DROID3 using XDA App

FXP vs CM?

Not really sure where this belongs, so Mods, please feel free to move it.
Given all the changes within CyanogenMod recently, and the formation of Cyanogen as a business, what's likely to happen to the FXP team? I know Kali has already said he won't develop CM any more.
Everyone has their own views on the politics of the situation, and this isn't really about that.
Just saying, guys, that if you happened to leave CM and develop your own AOSP-based ROM, I'm sure you'd have a lot of followers

Probably OmniRom.
http://forum.xda-developers.com/forumdisplay.php?f=2601
http://forum.xda-developers.com/showthread.php?p=46423532#post46423532
Apparently the XZ is up and running.

I'm using cm10.1.3 (stable version), with one modification (softkey decreases for 32DP, has this mod here in the forum) and I am fully satisfied.
No bug's, clean, smooth and beautiful automony battery.
I recommend.

Ooh Omnirom looks interesting,
Time to sync sources while I'm at work...
Sent from my C6603 using Tapatalk

fards said:
Ooh Omnirom looks interesting,
Time to sync sources while I'm at work...
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
patiently waiting for a yuga release..time for something fresh.

ckyy said:
patiently waiting for a yuga release..time for something fresh.
Click to expand...
Click to collapse
I think there'll be official releases out very soon, but I'll have a look at it later on when I get chance and see how it builds and runs.
No point trying to build on my machine at work, it's steamdriven!
If the build works I'll post it . Surprised @pulser_g2 hasn't posted one already

Well @fards if it runs well....it'd be nice if you could put a build up for us to have a sneak peak
Sent from my C6603 using Tapatalk

Now I've had a chance to take a look at it (not built anything I'm still looking at device trees etc) I'm a bit underwhelmed.
There's more CM and less AOSP than I'd like, lots more CM.
Going to try merging Pabx brilliant Aosp with this too see if I can get anywhere.
Don't expect anything quick, if I can motivate myself to churn through it!

No rush @fards. Not exactly an obligation to do it. Thanks again.
Sent from my C6603 using Tapatalk

tbh at the moment the entire project just appears to be a fork of CM.
far too much of it for my tastes.
I'd wish they'd started with a pure aosp base.

fards said:
tbh at the moment the entire project just appears to be a fork of CM.
far too much of it for my tastes.
I'd wish they'd started with a pure aosp base.
Click to expand...
Click to collapse
Oh dear. Back to the usual aosp rom then

@ fards
omnirom started from pure AOSP as compare to cyanogemod
---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------
@ fards
omnirom started from pure AOSP as compare to cyanogemod

xZain69 said:
@ fards
omnirom started from pure AOSP as compare to cyanogemod
---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------
@ fards
omnirom started from pure AOSP as compare to cyanogemod
Click to expand...
Click to collapse
I suggest you go take a proper look at the github, then come back and say "sorry they are using mostly cm".
The apq kernel is the cm one(didn't look at the others close enough to care). Other device trees are cm. The git structure is cm.
www.github.com/omnirom
https://github.com/omnirom/android_kernel_sony_apq8064
Code:
defconfigs: debranding
We're not a part of cyanogenmod any more. Also to avoid anyone else
having to do this, let's make the names generic to facilitate cross-
project
Change-Id: I89b6626636d568b36b9979272c6099fd074840e3
That changes the name only of the cm defconfigs. THESE are Not aosp, they are cm based.
Ergo it's a cm fork.
https://github.com/omnirom/android_device_sony_qcom-common
Code:
README.md
Copyright 2013 - The CyanogenMod Project
android_device_sony_qcom-common
Sent from my C6603 using Tapatalk

fards said:
I suggest you go take a proper look at the github, then come back and say "sorry they are using mostly cm".
The apq kernel is the cm one(didn't look at the others close enough to care). Other device trees are cm. The git structure is cm.
www.github.com/omnirom
https://github.com/omnirom/android_kernel_sony_apq8064
Code:
defconfigs: debranding
We're not a part of cyanogenmod any more. Also to avoid anyone else
having to do this, let's make the names generic to facilitate cross-
project
Change-Id: I89b6626636d568b36b9979272c6099fd074840e3
That changes the name only of the cm defconfigs. THESE are Not aosp, they are cm based.
Ergo it's a cm fork.
https://github.com/omnirom/android_device_sony_qcom-common
Code:
README.md
Copyright 2013 - The CyanogenMod Project
android_device_sony_qcom-common
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
@fards : Have a word with yourself mate ;
The git structure is the defacto standard as used by every rom who hosts on github , PA/Omni/CM.
You cannot have sub directories in your user namespace on github so you cannot represent things in the same way as you would with your own git server with a gitweb/gtiles frontend
The device trees are ported from cm for convience the rest of the project uses repo's forked from AOSP or the AOSP it's self
So instead of scanning one repo's commit messages and making a conclusion. I would suggest you read the default manifest as well to see where the sources are pulled from
https://github.com/omnirom/android/blob/android-4.3/default.xml

fards said:
I suggest you go take a proper look at the github, then come back and say "sorry they are using mostly cm".
The apq kernel is the cm one(didn't look at the others close enough to care). Other device trees are cm. The git structure is cm.
www.github.com/omnirom
https://github.com/omnirom/android_kernel_sony_apq8064
Code:
defconfigs: debranding
We're not a part of cyanogenmod any more. Also to avoid anyone else
having to do this, let's make the names generic to facilitate cross-
project
Change-Id: I89b6626636d568b36b9979272c6099fd074840e3
That changes the name only of the cm defconfigs. THESE are Not aosp, they are cm based.
Ergo it's a cm fork.
https://github.com/omnirom/android_device_sony_qcom-common
Code:
README.md
Copyright 2013 - The CyanogenMod Project
android_device_sony_qcom-common
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Andrew Dodd (Entropy512) has been one of the major Sony contributor to CyanogenMod, so were a few people that are helping us on Omni. Just because one device tree has been taken off an existing CyanogenMod repository doesn't mean we are a CM fork. It would be shooting ourselves in the foot to start device trees from the ground up again.
Besides some device trees, everything else has been up from AOSP. Therefore, we're not a CM fork.

[Q] can someone teach me how to build a ROM

My friend owns an samsung galaxy tab 4 t-230 and would love to upgrade it into a more pure android. Since i kind of got into android ROMs and there are no AOSP or CM roms for the tab 4 t-230 this would be a great chance for me to build a AOSP or CM rom. I have ubuntu 14.10 and a decent enough pc with 16 gb of ram and an i7. If anyone could help me abit of how to build a AOSP or CM rom for the device i would be verry thankfull.
----------------------Edit-----------------------
I wanted to say thank to you guys! I did quite some progress by now. If you own a t230 / nu then feel free to check out my custom kernel

CTXz said:
My friend owns an samsung galaxy tab 4 t-230 and would love to upgrade it into a more pure android. Since i kind of got into android ROMs and there are no AOSP or CM roms for the tab 4 t-230 this would be a great chance for me to build a AOSP or CM rom. I have ubuntu 14.10 and a decent enough pc with 16 gb of ram and an i7. If anyone could help me abit of how to build a AOSP or CM rom for the device i would be verry thankfull.
Click to expand...
Click to collapse
Relevant post - some starting info, and check out the CM wiki he links to. Also, and this is a very basic step, but if you've never done this before it can be informative: download a rom zip file (preferably but not necessarily a stock-based kitkat rom for this device) and open it up in either 7zip or WinRar, check out the layout and structure, and familiarize yourself with the updater-script. (Actually you can do that with a firmware tar file too). Sorry I can't give you any more useful info, not a dev, definitely not a rom designer, just a guy who knows a fair amount of android stuff.
Also don't let the tone of that post discourage you; the poster was answering a guy who was basically asking about the feasibility of building a brand new rom for the sole purpose of being able to use one particular proprietary Samsung app. Yes it is difficult, but still doable, and you say you're motivated...

Yes i did forgot to say that any links for learning are appriciated

Well.. I would ask moonbutt74 for more info regarding commands and such, probably more info than I can give but.. keep in mind your going to have to download about 20+GB of source code and all that. Also a bunch more knowledge of more things I don't remember. But it is alot
-DUHA

Well I decided to revisit this thread. Never thought I would come so far. I really want to say thanks to all of you who supported me and still support me. Everyone has a beginning and here was mine. Now I am actually there where I really wanted to be. Releasing a custom kernel and finally work on a custom ROM! Thank you XDA!

CTXz said:
Well I decided to revisit this thread. Never thought I would come so far. I really want to say thanks to all of you who supported me and still support me. I mean everyone has a beginning and here was mine. Now I am actually there where I really wanted to be. Releasing a custom kernel and finally work on a custom ROM! Thank you XDA!
Click to expand...
Click to collapse
I'm amazed on how much people learn and achieve as well as myself. I've seen people who were total newbies then later built custom recoveries, CM12, Mods, Roms etc. Anyway good luck on working your rom!
Sent from my SM-T800 using Tapatalk

DUHAsianSKILLZ said:
I'm amazed on how much people learn and achieve as well as myself. I've seen people who were total newbies then later built custom recoveries, CM12, Mods, Roms etc. Anyway good luck on working your rom!
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Also I thank you my life for introducing me to moonbutt74. He learned me everything from how to work with custom kernels to Roms. Sadly he decided to stop developing a few Werks ago but he's doing it for his own good. I still will mention @moonbutt74 on my future projects because he really is the one who changed me from confused to knowing what is actually going on. So thanks allot !

CTXz said:
Also I thank you my life for introducing me to moonbutt74. He leatned me everything from how to work with custom kernels to Roms. Sadly he decided to stop developing a few Werks ago but he's doing it for his own good. I still will mention @moonbutt74 on my future projects because je really is the one who changed me from confused to knowing what is actually going on. So thanks allot !
Click to expand...
Click to collapse
the erlkönig cant stop!

How to make angler build

I am trying to build an image for angler. Looking for make files to build the image for angler (Nexus 6P) Where can i find the vendor/make files to build the image.
How do I see the angler option when I do lunch?

Do a quick search on Github, it should have everything you need.

Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.

debby_8 said:
Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.
Click to expand...
Click to collapse
Trying to build the kernel myself, would also appreciate some info. Samsung always at least always includes some help file to specify the toolchain needed etc.

to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?

mehmehmen said:
to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?
Click to expand...
Click to collapse
Well in my case, at this point I just want to build the kernel. It's really too bad that XDA doesnt accept posts like this on their 'development' forum. On this general FAQ forum I dont think it reaches the right audience and hence no reponse from anybody yet, to this fairly simple question. I wish XDA would support developers a bit more and would allow development questions on the development forum.

I understand what you mean, although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading. I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Im currently working on the angler with a couple of guys and we have a booting fully operational OmniRom port in testing stages now, which may end up to me then posting that as a full [ROM] thread and trying to offer support on the device for that rom. The guy that built the rom himself is very good and has helped me understand a lot, with the right attitude and willingness to learn I am sure you would be welcome in the IRC channel where I personally would be happy to try and help you get your head round some things, as the next goal for me regarding the 6p in terms of our project is going to be kernel based compiling as i want to try and get a really robust kernel built now we have a seemingly stable feature full rom built and booting.
Feel free to message me if this sounds like it may be of some help
Regards
Meh

mehmehmen said:
although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading.
Click to expand...
Click to collapse
That happens on any forum.
I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
Click to expand...
Click to collapse
Sure but that would be going off topic on someone's thread.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Click to expand...
Click to collapse
Everybody has questions, regardless of their level. I was the maintainer for Cyanogenmod Note 4, so if the above would be true, I wouldnt be here I'm sure I can figure out myself how to get the Angler kernel compiling but it would save me, and others who will try the same in the future, quite a bit of trouble if someone who had done it would just post the used toolchain etc.
Anyway you used a lot of words without helping at all. That's exactly my point, when posting on a general forum you can expect these kind of replies. That's why I'd love to see a true development forum here on XDA, not just a 'developer' forum where people just support their projects. Giving support to a project, has not much to do with development.
Nah, I could have expected this. I'll figure it out myself. Thanks but no thanks.
*EDIT* I guess this will work, using toolchain 4.6 like they recommend, it's probably the latest anyway (?)
https://source.android.com/source/building-kernels.html
They dont mention Angler, but I'll try this anyway, I think it might work. And I'll let people know if it worked or not, so someone in the future who reads this thread will know how too. Although I kinda doubt a developer will search the general FAQ forum here ...

Might wanna try asking that on a kernel development thread in Dev section - kernel developers are usually friendly to people willing to rightfully use (and maybe improve) their work. They should be at least give you a vision on how go get the basic Angler kernel up and running.
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]

Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.

rustyjay said:
Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.
Click to expand...
Click to collapse
Thanks mate ! That's what I was looking for, will try that one.
---------- Post added at 03:23 AM ---------- Previous post was at 03:03 AM ----------
Ok and it's building !
Steps I took:
1) Download angler kernel here: https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-marshmallow-dr
2) Download toolchain with: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
3) add the toolchain to the path, in my case: export PATH=~/android/toolchains/aarch64-linux-android-4.9/bin:$PATH
4) go to the unpacked kernel dir
5) export ARCH=arm64
6) export SUBARCH=arm64
7) export CROSS_COMPILE=aarch64-linux-android-
8) make angler_defconfig
9) make
Thanks again @rustyjay for the toolchain info !
---------- Post added at 03:32 AM ---------- Previous post was at 03:23 AM ----------
AndyYan said:
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Click to expand...
Click to collapse
As much as I love CM (I was maintainer for the Note 4), I don't particularly see the point of running it on a Nexus device. I just want some kernel tweaks (for example that damn fuel gauge is giving me wakelocks), so I think l wont jump onto CM. But who knows ...
---------- Post added at 03:46 AM ---------- Previous post was at 03:32 AM ----------
Build completed So I guess I just insert the resulting Image.gz-dtb into the boot.img (with android image kitchen for example), right ? Will try tomorrow, but I think that should work. off to bed now ...

Yeah what it basically does when I build aosp, don't know too much about kitchen.

rustyjay said:
Yeah what it basically does when I build aosp, don't know too much about kitchen.
Click to expand...
Click to collapse
Ok I used android image kitchen to replace the Zimage, flashed it and ... it boots
Cool, so that's easy. Now for the next part: building the whole rom ! Any idea on how to do that ? Or where to even download the code ? Is there even a whole ROM to build, including the blobs etc ? I think i saw google releasing a device tree but not the whole ROM, right ? I must say I havent really googled myself this, will look into this today myself too.
*EDIT* yeah here's the device tree: https://android.googlesource.com/device/huawei/angler/ but I dont think it's the whole ROM, going to download it now ...
*EDIT2* No this definitely isnt the whole ROM,not even the device tree There's not a lot in there !?!
*EDIT3* Info here: https://source.android.com/source/running.html
*EDIT4* So as per the link above, it turns out that most drivers are blobs ! Hmm that's a bit disappointing. You buy a Nexus because supposedly it's 'open source', turns out most of it is not.... Anyway so it seems it's just a matter of compiling the sourcecode that IS there and then adding the blobs.
*EDIT5* So this section explains the whole process of setting up the environment, downloading, syncing and building: https://source.android.com/source/requirements.html looks very similar to the CM install/build process indeed !

To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.

rustyjay said:
To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.
Click to expand...
Click to collapse
Thanks for all your info, much appreciated. Currently syncing to AOSP like explained on that page I linked, will take a few hours I guess.
BTW, what are you exactly building this for ? Just some tweaks ? I saw this kernel wakelock qpnp_fg myself, I just disabled CONFIG_QPNP_FG=y in the defconfig, the wakelock is gone but like I expected, the battery gauge doesnt work anymore neither, lol. Will need to look into it for a real fix I guess.
Also I'm planning to make an option to default MTP as USB connection. It's just plain crazy Google left that out in 6.0 !

I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.

rustyjay said:
I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.
Click to expand...
Click to collapse
It's my first Nexus and am just loving it already. I mean, getting CM to run on a Samsung device is of course fun, but it's also just SO much work. I dont think I could do it all over again on another non AOSP device.
Now on nexus, just syncing directly from google and building it, what a breeze this is !

Oh yeah if your into building, nexus is really the only way to go. My first nexus was the ns in '10 and have had a nexus phone ever since

OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.

rustyjay said:
OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.
Click to expand...
Click to collapse
What are your main changes ?
Anyway I just finished building the ROM myself. It ends up with system.img, userdata.img, recover.img, ramdisk.img, ramdisk-recover.img. I'd probably just flash boot.img and system.img, right ? That userdata.img, what is that exactly anyway ? If I flash that I'll lose my user partition=installed apps, I guess ?
BTW I didnt pull any blobs so I guess it wont run anyway. I guess I first need to extract the blobs ? Does the AOSP build process include the blobs automatically ?
Thanks !

How to get device binaries to build a working ROM for oneplus 2 with AOSP code ?

I am going through the build guide on the [AOSP][1] page and found a requirement called "device binaries"
Can anyone tell me how to get binaries for op2 to build a pure AOSP working ROM ?. I am a complete noob in this field so if I require anything device specific (op2) apart from those binaries please do enlighten me.
Also is it possible to get the binaries from lineage repository ?
[1]: https://source.android.com/setup/build/building#obtaining-proprietary-binaries

paulplusx said:
I am going through the build guide on the [AOSP][1] page and found a requirement called "device binaries"
Can anyone tell me how to get binaries for op2 to build a pure AOSP working ROM ?. I am a complete noob in this field so if I require anything device specific (op2) apart from those binaries please do enlighten me.
Also is it possible to get the binaries from lineage repository ?
[1]: https://source.android.com/setup/build/building#obtaining-proprietary-binaries
Click to expand...
Click to collapse
Short answer, you can't

anupritaisno1 said:
Short answer, you can't
Click to expand...
Click to collapse
Can you please elaborate why? Also how do lineage OS devs get those binaries or any other independent aosp developers?

paulplusx said:
Can you please elaborate why? Also how do lineage OS devs get those binaries or any other independent aosp developers?
Click to expand...
Click to collapse
You can get those binaries but you can't boot aosp at all on the op2 without a few commits from lineageos. We need a lot of hacks on op2 to even get Oreo to boot
Also those commits will obviously not work just by simply picking them and you'll have to adapt them for aosp. None of our HALs are ready for being built without the kernel source (aosp doesn't support inline kernel builds)
You can get the binaries from https://github.com/TheMuppets/proprietary_vendor_oneplus

anupritaisno1 said:
You can get those binaries but you can't boot aosp at all on the op2 without a few commits from lineageos. We need a lot of hacks on op2 to even get Oreo to boot
Also those commits will obviously not work just by simply picking them and you'll have to adapt them for aosp. None of our HALs are ready for being built without the kernel source (aosp doesn't support inline kernel builds)
You can get the binaries from https://github.com/TheMuppets/proprietary_vendor_oneplus
Click to expand...
Click to collapse
Wow! a lot of information in a single comment. Is there a way I learn more about OP kernels, roms, hals so that I gain some information at least for a start. Any proper references ? or shall I start by building LOS For op2 without knowing anything and work my way through to the top. Your advice would be helpful in this. I plan to know more about ROMs and build them with customizations... major customizations. Thank you.

paulplusx said:
Wow! a lot of information in a single comment. Is there a way I learn more about OP kernels, roms, hals so that I gain some information at least for a start. Any proper references ? or shall I start by building LOS For op2 without knowing anything and work my way through to the top. Your advice would be helpful in this. I plan to know more about ROMs and build them with customizations... major customizations. Thank you.
Click to expand...
Click to collapse
I'll tell you this. All of the guides you'll ever find are utter nonsense. You have to find your own way to do it and no guide can really help you. There really is no one size fits all guide

anupritaisno1 said:
I'll tell you this. All of the guides you'll ever find are utter nonsense. You have to find your own way to do it and no guide can really help you. There really is no one size fits all guide
Click to expand...
Click to collapse
This is true from what I have seen till now. Guess I'll start building LOS directly as a start (as it is readily available for op2), tweak it little by little and keep learning bits and bytes from everywhere. Thanks