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?
Related
Hey guys.
who is the developer of mokee 51.1(nightly)?
is it @jsevi83 @Kra1o5 or somebody else.(whoever it is thanks a lot and keep the good work)
I was wondering if they were the devs,can i flash thebeast and xcelerate kernel?as they were build on there source.
let me know if i am wrong...thx
Mokee being developed by Mokee Dev Team using armani-dev kernel source & device tree, so you can use custom kernel for CM12/12.1 that support anykernel (xcelerate & beast kernel)
No 51.1 is developed by syhost not the cm devs,if it was cm devs they will release 5.1.1 of cm before mokke..
i flashed the custom kernel successfully on 5.1.1(nightly). but before that i tried on 5.0.2(release)...it failed.
BATVIC said:
No 51.1 is developed by syhost not the cm devs,if it was cm devs they will release 5.1.1 of cm before mokke..
Click to expand...
Click to collapse
dels07 said:
Mokee being developed by Mokee Dev Team using armani-dev kernel source & device tree, so you​can use custom kernel for CM12/12.1 that support anykernel (xcelerate & beast kernel)
Click to expand...
Click to collapse
The mokee dev team can still use armani-dev kernel source & device tree to build 5.1.1 without cm devs releasing 5.1.1...
Syhost never released his kernel source - therefore mokee (open source project) can't use his work.
@Luk_Optimus,
Yes now only I'm noticed that.
Xcelerate kernel is working nice in this.
It proves that it is based on the cm only..
Hereby,
WIP....
WIP := work in progress...
Q/A
1. On which sources is this Based On?
1A. This is Based on Motorola Moto G4 Plus.
3. What about kernel sources?
3A. Kernel sources must be released by Google not by me so please wait.
Device Tree: https://github.com/HostZero/android_device_google_shamrock/tree/cm-13.0
Vendor Blobs: https://github.com/HostZero/proprietary_vendor_google/tree/cm-13.0
TWRP Tree: https://github.com/HostZero/twrp_device_google_shamrock/tree/android-6.0
DONT THIK TO COMPILE TWRP. ITS ALREADY OFFICIAL
XDA THREAD:http://forum.xda-developers.com/gm-5-plus/development/twrp-twrp-root-android-one-gen-t3404338
DOWNLOAD OFFICIAL: https://twrp.me/devices/googleandroidonethirdedition.html
Repeating its still WIP.
Team Is On Their Way....
Credits: @RealSchule
@Equal1zer
@HostZero is hard working
Good work bro.
Sources Frameworks are patched.
This will fix force closing of apps.
Full Bobs and Device Are Pushed... Errors with kernel. Need to Deal soon you will have #Alpha Builds In EXT4.
any process ? @HostZero
ralp88 said:
any process ? @HostZero
Click to expand...
Click to collapse
We need kernel source for that.
vendor blobs for lg stylo 2 plus ph2n? could use some help.
Rmontoya83 said:
vendor blobs for lg stylo 2 plus ph2n? could use some help.
Click to expand...
Click to collapse
http://opensource.lge.com/osSch/list?types=ALL&search=ms550
Hi!
I'm just wondering why I seem to have such trouble compiling ROMs based on AOSP-CAF e.g Dirty Unicorns... I always get some kind of error when it comes to building AOSP/AOSP-CAF based ROMs... What's the difference between compiling a Lineage OS based ROM and AOSP-CAF? Can't I use the same device/kernel and vendor tree? I've compiled Viper-OS and ColtOS without any problems... .
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!
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?