I was planning to build CM for a new device.
I saw some threads on xda related on creating device tree for a new device.
I made the prototype version of device tree and kept it aside for working later.
When I searched for making vendor tree, I cannot find any useful thread.
So how do one actually create a vendor tree?
If there is any thread related to that, link me up.
Some links here to help. - http://forum.xda-developers.com/showthread.php?t=2073370
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?
Hello,
I'm trying to build a device tree for the Samsung Galaxy Tab A 9.7 (gt510wifi), by following CyanogenMod's porting guide here. I've managed to get a basic device tree going inside CM12.1's source tree, but I'm stuck at the part where I need to create the extract-files.shand the setup-makefiles.sh. The guide says to use other device trees as a reference for creating these scripts, but from what I can tell, each script is vastly different due to device discrepancies, and I'm unsure what to do at this point. I've searched everywhere online, but there doesn't seem to be any documentation whatsoever on how to create these files.
I'm no stranger to porting ROMs, as I've built SlimLP for my other devices, but I always had a pre-built tree created by another developer that I simply renamed files in to get it to work with SlimLP's sources.
Any help is greatly appreciated
Hello,
I'm a beginner with building ROMs, yet I found an interest in build an AOSP for a phone(mi4c). I found the kernel sources released by the vendor, but I am trying to figure out the next steps: creating a device tree and getting the vendor blobs.
As I could check the kernel if for 5.1(managed to build it), and I would like to try to make that - AOSP 5.1.
Is there any way to extract the device tree from kernel(I found some device tree on git, yet I would like to know if there is another way to create it)?
for vendor blobs and which are required I found some information here on xda, but haven't tested so far.
Thanks!
I've seen one tutorial on developing custom rom from source. To do that device specific files like kernel, device tree and vendor blobs are needed. I have following problems regarding those files.
* Kernel - I have zip file of kernel downloaded from my device manufacturer site. How can i make use of that to build a rom?
* device tree - I'm not able to find a device tree for my device anywhere (github or anywhere), how can I build device tree using (kernel/stockrom...)
I'm totally new for this so I don't know if it is even possible or not. Or Is there any other way to create device tree.
* vendor blobs - I've same problem for vendor blobs as in device tree.
~ so from where and how I can extract or create device tree and vendor?
~ and make things ready to develop a custom rom
My device is HTC one (m8 eye)
code name : melsuhl
I have not found any tutorial to build vendor tree but there is an outstanding tutorial on building device tree..
Check this out : https://youtu.be/Uw_caMHZRC4
hello @HarshOne i am looking for the same things as you. Trying to build a lineageOS ROM for my cph2025 OPPO Find X2 Pro. Did you find a way to find those trees?
As we all know, official Android upgrades for the Nokia 6.1 Plus have ended with the Android 10 update and we will only be getting security patches going forth. However, some of us have the drive and desire to try out newer releases of Android, but we can't exactly shell out more money for a new device that will receive those updates.
Some of you might be aware that to make Android 11 (and beyond) ROMs a reality, any device needs a Device Tree and a Vendor Tree, and currently, there are no full trees for our device.
That's where I come in - again some of you might already be aware, but I have been working on full device and vendor trees for this device, with proper commit histories (flashbacks) so as to maintain order in the community. The trees are WIP, but the progress can be followed in the links below.
Device Tree
Vendor Tree
My current roadmap is as follows (I will update this list as and when I finish those things)
1. Finish the Device Tree by adding "configs," "rootdir," "ramdisk," and "symlinks"
2. Work on the Vendor Tree and pull missing blobs from the device
3. Build and test LineageOS with my trees - 31st build tested, device boots, sensors RIP
4. Maybe build other ROMs till android 11 arrives
Hoping to extend the life of this device,
Sid
Stonks
He attac,
He protec,
But most importantly
He got our bac
cocacola pepsi,
sid bhaiya sexy!
Cheers bro, I'm all for this!
Bumping the thread since I'm halfway done.
Also noticed another dev is close to releasing "source built vendor."
Dear dev, I challenge you to make your trees public.
Sid127 said:
Bumping the thread since I'm halfway done.
Also noticed another dev is close to releasing "source built vendor."
Dear dev, I challenge you to make your trees public.
Click to expand...
Click to collapse
Do it I am with you Coca Cola Pepsy developer :silly:
Moderator Information
Hello OP, I have moved this thread from Development to General as there is no ROM available yet. Please report this thread or contact me again if you have a ROM and kernel source links available, I can move this into Development section then.
Thanks.
Regarding the recent sparks of controversy and mods being involved and a certain someone posting this on their public channel -
Forgot to say few kids started doing criticism again better my answer do by your own or learn from scratch
Click to expand...
Click to collapse
I have only one response to the
message - I HAVE done it by myself and I HAVE learned from scratch, and my trees (which can be viewed by anyone) are evidence of the same. My GitHub history can be followed to see exactly HOW I learned too - my modifying Motorola (Chef) trees.
Also, one question for everyone - considering we had vendorless builds for our device since Android Pie, am I the only one who finds it suspicious that said dev built vendor sources only around the same time I did? I just would like to take a look at said Dev's work and verify.
Cheers,
Sid
Bumping thread since I finally made progress
After 31 excruciating builds, I'm abandoning my trees. My vendor repo got taken down in a DMCA notice for a proprietary library, and I just don't have the motivation to continue on my Device Tree after being seemingly stuck on a device which boots but nothing works. My tree is still gonna be up on my GitHub for anyone to refer to. As for ROMs, the Official LOS trees work great and that's what I'll be using for builds. Though I didn't finish what I started, I learned a lot and am thankful for the journey.
Cheers,
Sid
Edit: vendor repo is up again and I have removed the disputed lib
I wish you had maintained it as you've already done most of the work. What is the end node of device trees which marks its completion?
Volski_ said:
I wish you had maintained it as you've already done most of the work. What is the end node of device trees which marks its completion?
Click to expand...
Click to collapse
I will try and maintain it, but they've been abandoned for the time being... with Android R on the horizon, it didn't make much sense to spend countless hours trying to fix Android 10 trees. Device trees can be called complete when ROMs built using them are stable enough for daily use with every function working as intended.