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?
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..
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?
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!
Why we still don't have LineageOS 19?
What is missing ?
I asked luk and he told me build quality is not enough good in his opinion (that was month ago)
A couple Asus and Pixels got it so far, according to this post.
https://www.xda-developers.com/lineageos-19-android-12/
Kernel source is here but, judging by the performance of the stock rom, it's probably not great as a stable base :
GitHub - OnePlusOSS/android_kernel_oneplus_sm8350 at oneplus/SM8350_S_12.0_9Pro
Contribute to OnePlusOSS/android_kernel_oneplus_sm8350 development by creating an account on GitHub.
github.com
OnePlus themselves seem to have been pushing 12.1 to earlier models and are probably just going to go for a better Android 13 experience for the 9/10 models.
Even Google has made a mess of Android 12 on their own Pixels.
You can always check the OnePlus github at the url above and search for the chipset which you can confirm using the GSMArena page for the phone :
OnePlus 9 Pro - Full phone specifications
www.gsmarena.com
When you do, you'll see the latest revisions pushed by OnePlus along with the Android base, SM8350_S_12.0 in the above case. If you don't see the current version then there's no kernel source pushed by OnePlus which means custom rom modders need to try using previous kernel source. That's why all the Android 12 roms have been using the Android 11 kernel and why the phone had to have OxygenOS 11 before flashing
djsubterrain said:
Kernel source is here but, judging by the performance of the stock rom, it's probably not great as a stable base :
GitHub - OnePlusOSS/android_kernel_oneplus_sm8350 at oneplus/SM8350_S_12.0_9Pro
Contribute to OnePlusOSS/android_kernel_oneplus_sm8350 development by creating an account on GitHub.
github.com
OnePlus themselves seem to have been pushing 12.1 to earlier models and are probably just going to go for a better Android 13 experience for the 9/10 models.
Even Google has made a mess of Android 12 on their own Pixels.
You can always check the OnePlus github at the url above and search for the chipset which you can confirm using the GSMArena page for the phone :
OnePlus 9 Pro - Full phone specifications
www.gsmarena.com
When you do, you'll see the latest revisions pushed by OnePlus along with the Android base, SM8350_S_12.0 in the above case. If you don't see the current version then there's no kernel source pushed by OnePlus which means custom rom modders need to try using previous kernel source. That's why all the Android 12 roms have been using the Android 11 kernel and why the phone had to have OxygenOS 11 before flashing
Click to expand...
Click to collapse
thats why custom A12 roms, still need stock A11 firmware ?
GabrielSousa said:
thats why custom A12 roms, still need stock A11 firmware ?
Click to expand...
Click to collapse
Until now yes but judging by what was said above, even the A12 kernel isn't up to scratch for custom roms.