So I am trying to build AOSP 5.0 for Redmi 1s. I downloaded the AOSP source. I also downloaded the device tree and vendor tree from github. Now what changes I have to make to build AOSP????
You need to edit the make files, edit .sh and vendor.
I used this answer to get my AOSP running on my G2 using CM sources. It's not very hard to manage this because CM is not quite different in these aspect, but you need to know some stuff about programming and solve the errors. Good luck.
GalaticStryder said:
You need to edit the make files, edit .sh and vendor.
I used this answer to get my AOSP running on my G2 using CM sources. It's not very hard to manage this because CM is not quite different in these aspect, but you need to know some stuff about programming and solve the errors. Good luck.
Click to expand...
Click to collapse
Can you explain...cause I can't understand that post
Related
Hello everybody.
I have a noob question about compile cyanogenmod for my new device.
Now, i have: CMW recovery, Kernel source code on local computer, full repo cm source + toolchains.
How to add my device tree, kernel source code to CM source and compile CM7 ROm?
Thanks you, cheer
Anyone here?
Did you figure it out yet? I asked the same question and am waiting for an answer, tho I'm on CM 10, HTC Vivid. If I figure it out I'll post back and try and help.
nguyenhonganh said:
Hello everybody.
I have a noob question about compile cyanogenmod for my new device.
Now, i have: CMW recovery, Kernel source code on local computer, full repo cm source + toolchains.
How to add my device tree, kernel source code to CM source and compile CM7 ROm?
Thanks you, cheer
Click to expand...
Click to collapse
I met the same problem, does anyone can help?
Do you have a device tree? Or do you have an unsupported device? If you have an existing device tree from some other ROM, etc, then you just need to edit your .repo/local_manifest/roomservice.xml to pull in the trees that you need.
If you need to create a device tree, then it gets not complicated, as each device is different. The basic process is to create the necessary directories (device/manufacturer/model, kernel/manufacturer/model (may need to be kernel/manufacturer/device_family/model, for reference to that, see CM's repo for the LG G3) and finally vendor/manufacturer/device.
After you have the directories setup, you will need to actually start building the tree. The easiest way is to copy another devices files into your devices tree, and then edit the files. The closer the device you copy in is, the less work you will need to do to the files. Refer to sites like gsmarena.com, PhoneArena.com, etc for phone specs.
That's about as far as I can take you without dealing with a specific device. If you need more info, post back here with your questions, and post your device specs, or at least the model number,and I'll see if I can help.
rassawyer said:
Do you have a device tree? Or do you have an unsupported device? If you have an existing device tree from some other ROM, etc, then you just need to edit your .repo/local_manifest/roomservice.xml to pull in the trees that you need.
If you need to create a device tree, then it gets not complicated, as each device is different. The basic process is to create the necessary directories (device/manufacturer/model, kernel/manufacturer/model (may need to be kernel/manufacturer/device_family/model, for reference to that, see CM's repo for the LG G3) and finally vendor/manufacturer/device.
After you have the directories setup, you will need to actually start building the tree. The easiest way is to copy another devices files into your devices tree, and then edit the files. The closer the device you copy in is, the less work you will need to do to the files. Refer to sites like gsmarena.com, PhoneArena.com, etc for phone specs.
That's about as far as I can take you without dealing with a specific device. If you need more info, post back here with your questions, and post your device specs, or at least the model number,and I'll see if I can help.
Click to expand...
Click to collapse
I have a mt6750 devices... And there is a device from my company manufacturer.. Its a mt6750 device, it have cm device tree.. Both device working on same rom.. I can port that device rom but it always give me bugs.. So my question is how to use it?
Hey guys!
My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel).
We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9...
So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad.
If someone could help me make this device tree work it would be awesome. Thanks!
P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Delete cm.mk
Edit vendorsetup.sh (remove "cm_").
That is all you need to do, I believe.
Like you know, sync the AOSP source, include your device folder amd build.
Sent from my Galaxy Nexus using Tapatalk 2
mDroidd said:
Delete cm.mk
Edit vendorsetup.sh (remove "cm_").
That is all you need to do, I believe.
Like you know, sync the AOSP source, include your device folder amd build.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I found this thread and this is exactly what I'm doing. Would you be interested in answering my questions in exchange for a nice donation? I haven't had much luck getting help and being a single parent of three toddlers I really need to maximize my free time to work on this.
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through.
私のEVO 3Dから送信される。
dastin1015 said:
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through.
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
Removing overlays doesnt work here. Have many issues regarding the kernel.
hey
Good luck
rohan32 said:
Hey guys!
My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel).
We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9...
So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad.
If someone could help me make this device tree work it would be awesome. Thanks!
P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Click to expand...
Click to collapse
Were you able to port aosp device tree from cm.Please tell me how ?
Hello!
I'd like to build my own rom from AOSP 8.0 official branch. I'm looking for some kind of guide but couldn't find any So, let's say I've got android source code and files from other custom rom that makes camera work. What have I to do to make my rom now? How can I build it and be sure that everything will work. Generally my target is to install android 8 on my Leeco le 2 x620 device with Mediatek chip
Any help is appreciated ^v^
LEGOL2 said:
Hello!
I'd like to build my own rom from AOSP 8.0 official branch. I'm looking for some kind of guide but couldn't find any So, let's say I've got android source code and files from other custom rom that makes camera work. What have I to do to make my rom now? How can I build it and be sure that everything will work. Generally my target is to install android 8 on my Leeco le 2 x620 device with Mediatek chip
Any help is appreciated ^v^
Click to expand...
Click to collapse
"I'd like to build my own rom from AOSP"
So you mean an aftermarket os like lineageos or carbonrom or do you mean that you take the aosp repo and compile aosp for your device? You can look in source.android.com
"source code and files from other custom rom that makes camera work"
Is that an already compiled rom? Because you won't get source code out of that
"How can I build it and be sure that everything will work"
Ya don't. Nothing can ever be 100% bugfree, it can either be from your device tree's source code, or the aosp code itself.
Generally, if there is a caf tree for your device, it's going to be 3x as hard to create an aosp tree.
It is going to be 100000x as hard to create an aosp tree that is for a newly released, new hardware requirement operating system.
Wanna know the topping of the cake? Mediatek is notorious when it comes to releasing the source (in fact, it has become a meme in the Mediatek users world) but don't let that stop you son.
You can try, but don't give up just because it won't compile the first couple of hundred times. The errors when compiling should give you a great start
Good luck.
ramiabouzahra said:
"I'd like to build my own rom from AOSP"
So you mean an aftermarket os like lineageos or carbonrom or do you mean that you take the aosp repo and compile aosp for your device? You can look in source.android.com
"source code and files from other custom rom that makes camera work"
Is that an already compiled rom? Because you won't get source code out of that
"How can I build it and be sure that everything will work"
Ya don't. Nothing can ever be 100% bugfree, it can either be from your device tree's source code, or the aosp code itself.
Generally, if there is a caf tree for your device, it's going to be 3x as hard to create an aosp tree.
It is going to be 100000x as hard to create an aosp tree that is for a newly released, new hardware requirement operating system.
Wanna know the topping of the cake? Mediatek is notorious when it comes to releasing the source (in fact, it has become a meme in the Mediatek users world) but don't let that stop you son.
You can try, but don't give up just because it won't compile the first couple of hundred times. The errors when compiling should give you a great start
Good luck.
Click to expand...
Click to collapse
Oh God, how am I meant to do this ;0 There is Lineage 14.1 project on my device. I really want to have android 8 on my phone. Thank you for all the advice.
Yes im trying the same andere without any succes so far.
Im also trying to port from a different device ROM to the stock ROM what im running now.
The chip sets are the same but the Android versions not.
It would be really Nice if some mtk ROM developer find some time in his busy life to create a ROM for our phone.
Or a guide to compile/port Android o tot oud phone.
We need build instructions in order for people to more easily make custom roms. Currently most roms here only provide a repo or two, hardly describing the build process if anything. Not sure if those repos contain all the sources/blobs you need either.
It's not that hard to build and you can always go on th cheap and hire a cloud vps for a few hours, so don't bother with local building unless you have the powerful hardware.
Anyhow, so far what I know is that some people just replace the kernel and firmware, it seems this is called repacking.
Others are building Lineage from source as per their instructions, which are not descriptive when you're porting to a new device.
We need concrete and concise information about how it's done.
Lineage wiki is pretty accurate and if someone ask here I can try to solve his doubt.
I am not the best developer but I know the basics xD
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
randxor said:
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
Click to expand...
Click to collapse
Thats thanks to codeworkx code. Basically you compile a rom for zl1 and works for zl0.
My workflow is
repo init/sync the rom
Fix libhidl and libbfquio if needed (Dont know why they fix an error creating a bigger one tho)
Take the device tree, vendor and kernel
Adapt the device tree for the rom (Like in cosmic where config is in root not in config folder, boardconfig...)
And just brunch or make or lunch depends on rom xD
Edit: Forgot u need like 200 frameworks/av commits to make zoom work https://github.com/mosimchah/frameworks_av/commits/o8.1 all the january 15th and this one http://gerrit.aicp-rom.com/#/c/54436/
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
randxor said:
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
Click to expand...
Click to collapse
Yout init the rom source you want to compile
You dont need to adapt anything codeworkx already did it for us we just compile zl1 roms with his device tree (Los one) or any of the forked ones (Like Aicp which I recommend).
Libhidl and libbfquio depends on the rom you are building. Libhidl is solved by reverting this changes https://github.com/PixelExperience/system_libhidl/commit/607e961b85eea8969503d8ff8437c014f04f0ca2 and libbfquio by taking this http://gerrit.aicp-rom.com/#/c/56488/
You dont adapt device tree to device you adapt it to the rom you are compiling see how other devs do it in their github (Every rom is different for example in cosmic you rename lineage/aicp.mk to cos.mk and change where to import things)
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
Start by picking up a rom you want to compile that has 8.1 source working and better if a msm8996 device is there (zuk z2, oneplus 3...)
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
randxor said:
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
Click to expand...
Click to collapse
Np
Not sure dont know much about android kernels
Hey there devs.
I'm looking forward to build a pure aosp rom based on oreo 8.1 for mido.
So far I've tried and successfully built los 14.1 and rr 5.8.5 from source, but I want to build aosp source so as to create a vanilla aosp rom. I've looked on the internet and asked a couple of devs here in the forum and they told me to merge caf patches. I totally understand the point of caf but then i don't know how to do it. Also I'm pretty sure that some patches (caf maybe) need to be added to source since the compilation always gives an error related to board config, when i followed the official guide at android website. (But then I don't understand what overlays i have to apply or even what they are)
Edit : i use gcloud to build.
If anyone can guide me as to how i can build aosp, it would be really helpful:fingers-crossed:
But then any help is appreciated.:good:
Thanks in advance!
i've no knowledge on building rom but im waiting for your vanilla for sure, hopefully you made it from Note 4X as base since all 8.1 rom i have tried are giving me various app are stopping after using it for sometime. i hope i can help you in some way though i have limitation in helping. thank you for your spirit!
groovepeppy said:
i've no knowledge on building rom but im waiting for your vanilla for sure, hopefully you made it from Note 4X as base since all 8.1 rom i have tried are giving me various app are stopping after using it for sometime. i hope i can help you in some way though i have limitation in helping. thank you for your spirit!
Click to expand...
Click to collapse
Don't worry man, I'll find out some way to build it. I'm Waiting for los 15.1 to get official so that the kernel source and other sources are out which i can use. But still I'm trying to learn and build.:laugh: