Device Tree, Vendor Tree & Kernel for the OnePlus 3T? - OnePlus 3 Questions & Answers

I'm trying to build a new AOSP ROM for the OnePlus 3T from source, now I can't seem to find the GitHub source for the Device Tree, Vendor Tree & Kernel.
Anyone knows where I can find them?
Any help would be appreciated!

Related

T310 Device tree, kernel, and vendor sources

I'm trying to build Cyanogen from source based on the instructions here:
http://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
It looks like there's the device and kernel sources in this CM12.1 thread
http://forum.xda-developers.com/gal.../sm-t31x-cyanogenmod-12-1-unofficial-t3094681
But what do I use for the vendor sources?

Source and device tree

Ginkgo, hello.
Why most costom roms is using one (trinket) tree? On the old days, people is know when CM/LineageOS (Los) release is meaning use the clean tree and this is always for base all costom rom. But now, is not. This is not on Ginkgo only.
I see the Los tree is clean, good for battery backup with good performance and stabillity. Why not maintainer bringup this source to another rom?

Unofficial Lineage 16.0 for Samsung Galaxy S10+ (Exynos)

Hi!
I have been looking some time for a Lineage 16.0 device tree to build Lineage 16.0 to this phone and as I forked the 17.1 repo made by whatawurst I started to change it accordingly and the reason for it is that I intend to build libhybris with Lineage 16.0 as a base since there's no hybris-17.1....... YET (It's coming though).... to it so that I may boot Sailfish OS as well.
I had to change the standard local manifest and make my own repos for obvious reasons.
Now here's the fun part.
I extracted the blobs from the phone and put them in my vendor repo and synced without a problem.
I then ran source build/envsetup.sh && lunch lineage_beyond2lte-userdebug and it worked OK.
As I started to build Lineage I got an error about a missing ril file and YES I suspect that it's missing a lot more files as well.
I have no clue why ./extract-files.sh in /android/lineage/device/samsung/beyond2lte looked for files that aren't in the stock vendor directory.
I guess it differs from Lineage version to another.
I also know that Lineage 16.0 won't boot on a Q bootloader, but I don't intend to boot Lineage after it's built.
I'd appreciate if someone here would be kind enough to help me fix any missing files so that Lineage 16.0 will build.
When I can confirm that it builds I'll start to try: https://github.com/mer-hybris/hybris-patches/tree/hybris-16.0
Here's my device tree for Lineage 16.0: https://github.com/Umeaboy/android_device_samsung_beyond2lte

Device tree?

Any chance someone has or can share a device tree for the N100?

Question Experimental device tree

I found these device tree on github, for nabu (mi pad 5), can some pros in building, fix it and adapt it for 12? or help me do it? I'm a newbie so i need a lot of help
device tree: https://github.com/sailfish-on-nabu/android_device_xiaomi_nabu
common tree: https://github.com/sailfish-on-nabu/device_xiaomi_sm8150-common
and thx to this user who started adapting it for our pad

Categories

Resources