Most of the under rated xiaomi phones like redmi 4, 4x etc. all have project treble ported for these devices. Why cant mi4i have the same? If someone can port project treble rom and twrp recovery (redwolf) that supports project treble then I would be grateful.
Thank you.
Salam.Vivek said:
Most of the under rated xiaomi phones like redmi 4, 4x etc. all have project treble ported for these devices. Why cant mi4i have the same? If someone can port project treble rom and twrp recovery (redwolf) that supports project treble then I would be grateful.
Thank you.
Click to expand...
Click to collapse
What is Project Treble?
tamojit_ray said:
What is Project Treble?
Click to expand...
Click to collapse
Traditionally the OS framework and low-level software were all part of the same code. So when the OS got updated, this low-level software technically referred to as vendor implementation—also had to get updated. That’s a lot of work. Hence lead to android fragmentation.
So in order to curb this problem to some extend Google introduces Project Treble, starting with Android 8.x (Oreo),the core hardware code is separate from the OS code, device manufacturers will be free to update their software without having to wait for the silicon maker to also update its code.
In simple term it is somewhat like installing windows OS where you just install it and the drivers are installed separately( here in project treble the vendor partition has the drivers needed for that device)
We only got like 2 devs that work on ferrari once in a blue moon. The main guy who maintain trees is currently busy with life. You should use miui or get a new phone.
Related
We know that stock Oreo for Mate 9 has treble enabled.
I have been reading about treble and it seems that it focuses on standardizing vendor/odm partitions. The same vendor partition could be used by different Android flavors, including pure AOSP or Lineage.
Moreover, in treble devices the kernel must implement loadable modules. The same kernel will be shared among devices with the same SoC. Software for particularities like storage devices or camera will be loaded from vendor/odm partitions.
I'm not an expert, but shouldn't this mean that once a device with HiSilicon Kirin 960 has a functional AOSP- based ROM a port to Mate 9 should be easy to develop? Even it is possible that ROMs from other devices directly work...
What do you think?
I have no technical knowledge on this stuff, but from what I've read you're right. And I really hope this will be true !
Treble might be the reason I stick with the Mate 9 instead of moving to the Pixel 2 XL.
"...because of the way the lower layer of Android was modularized, all Treble devices in the market will be able to boot a generic stock, AOSP Android build."
https://www.xda-developers.com/project-treble-custom-rom-development/
At very least it will make updates easier
tusko5 said:
We know that stock Oreo for Mate 9 has treble enabled.
I have been reading about treble and it seems that it focuses on standardizing vendor/odm partitions. The same vendor partition could be used by different Android flavors, including pure AOSP or Lineage.
Moreover, in treble devices the kernel must implement loadable modules. The same kernel will be shared among devices with the same SoC. Software for particularities like storage devices or camera will be loaded from vendor/odm partitions.
I'm not an expert, but shouldn't this mean that once a device with HiSilicon Kirin 960 has a functional AOSP- based ROM a port to Mate 9 should be easy to develop? Even it is possible that ROMs from other devices directly work...
What do you think?
Click to expand...
Click to collapse
I would think so, with treble enabled it would at least make major updates easier on the part of the manufacturer, if that is the case, compiling a "generic" version of the asop code easier to implement, especially when it comes to major version upgrades such as to let's say android 9, I'll have to look into it.
Guys Lenovo K10 note is very good phone with great specs as it has a Full HD+ screen and SD 710 SOC. My request to all the developers is to make this great device popular around the world like Xiaomi by making some stable custom roms for this device. HERE IS THE KERNEL SOURCE CODE FOR LENOVO K10 NOTE -
https://lenovomobilesupport.lenovo.com/nz/en/products/phones/k-series/k10-note/downloads/ds541914
All the best developers
would be great to have some development for this device
[Query] regarding when the offical TWRP will release for Lenovo K10 Note????
The device is great with a good processor,good display,good battery and a decent camera but since the phone is awesome i hereby look forward to get further amzing features of custom rom and have one more doubt about why there is no pixel experience rom for any Lenovo series mobile and there is also not any official custom rom for lenovo k6 power(karate) ........
REQUEST for all the developers to make custom roms for this amazing device
For all the above comments and others who read this,
custom development can't be done just like that, it is difficult. The developer should have this device in hand to be able to do something. Above all that they give it for free therefore we shouldn't compel or request them, someone will do it voluntarily if he/she can.
Thankfully this device is having TWRP's recovery builds and also official one. This device is project treble supported it means you can flash Generic System Image (GSI).
As of now try flashing GSIs. Download a few treble checker apps from store and look for partition structure, I think it is arm64 A-only. One more thing is that all GSIs may not work perfectly and some will not boot at all, the same time some will work perfectly all right, also there are lots of GSIs available to test.
Good Luck, Stay Safe.
Hi
I was just wondering is there any development of Lineage OS going on ? Or the source code was not released yet ? I was using that system on my another phones,
Here is review for POCO version: https://www.youtube.com/watch?v=rvKmSetMHKQ
There are some efforts for building from source and via GSI and overlay. Sourcebuilds are not booting for now. But me and some others are still on it (while I lack the spare time atm)
For now you can use GSI with some bugs as far as I know.
I had mixed success with sourcebuild - see here https://forum.xda-developers.com/t/building-lineageos-17-1-from-source.4245417/
I have an a01 core and the performance is a bit slow. Stock android is faster than android with One UI, so I wonder if there's a way to install a rom or stock android in. No matter if I need root. Sorry for not knowing about this topic
Treble gsi - majority phones launched with andorid 8 and above project treble. This allows one Rom to support many devices.
Check if your phone supports project treble with this app
Treble Check - Apps on Google Play
Check your device for Project Treble support and more
play.google.com
If supported, use this guide to install andorid 11 GSI
Download Unofficial LineageOS 18.0 GSI for Project Treble Supported Device
From this guide, you could download the unofficial LineageOS 18.0 GSI for Project Treble devices. One question that might come to your mind is what
www.getdroidtips.com
This is AOSP 11
Release AOSP 11.0 v303 · phhusson/treble_experimentations
Fix hotspot for some people Fix boot on Samsung Qualcomm Android 11 vendors (/!\ this fix is incompatible with Magisk!) Fix proximity on some Samsung devices (requires ticking extra sensors) Fix 3....
github.com
Tab E said:
Treble gsi - majority phones launched with andorid 8 and above project treble. This allows one Rom to support many devices.
Check if your phone supports project treble with this app
Treble Check - Apps on Google Play
Check your device for Project Treble support and more
play.google.com
If supported, use this guide to install andorid 11 GSI
Download Unofficial LineageOS 18.0 GSI for Project Treble Supported Device
From this guide, you could download the unofficial LineageOS 18.0 GSI for Project Treble devices. One question that might come to your mind is what
www.getdroidtips.com
This is AOSP 11
Release AOSP 11.0 v303 · phhusson/treble_experimentations
Fix hotspot for some people Fix boot on Samsung Qualcomm Android 11 vendors (/!\ this fix is incompatible with Magisk!) Fix proximity on some Samsung devices (requires ticking extra sensors) Fix 3....
github.com
Click to expand...
Click to collapse
Thanks for the support!
After reading about the fast kernel source release for the Xiaomi 12 and Xiaomi 12 Pro one could think that xiaomi did a good job at complying with the GPL v2 license and providing useful sources for developers of custom kernels. But appearances are deceiving: The provided kernel sources are incomplete and partially broken.
The most important issues are that xiaomi pushed incomplete devicetree sources which are neither provided by qualcomm anymore unfortunately and the touchscreen drivers are really out of date which leads to broken double tap to wake and under display fingerprint sensor. Additionally building the kernel isn't as trivial as it sounds anymore since many kernel modules are built outside of the kernel tree now.
During the past days i have spent some time on getting a source built kernel including modules and devicetree running on Xiaomi 12.
I have sucessfully booted the kernel and uploaded this work to github.com/xiaomi-sm8450-kernel.
Using this manifest one is able to compile the OSS kernel for Xiaomi 12 and Xiaomi 12 Pro.
I hope that this can help other developers working on the Xiaomi 12 and Xiaomi 12 Pro!
For instructions to build the kernel and more details about missing sources please refer to the manifest on github.
Note that double tap to wake and fingerprint sensor don't work as is on the stock ROM.
Also note that the OSS display-devictree for Xiaomi 12 Pro is missing the configurations for some referesh rates which were supported on MIUI. This could be dumped and included from the stock dtbo.img with some effort.
If you encounter issues with this OSS kernel feel free to ask me and i will give my best to help.
To finish this thread i want to draw further attention to the fact that this is not a one-time issue with the OSS kernels for Xiaomi devices and the situation seems to get even worse. The newer Redmi K50 gaming got kernel sources which don't include any external respositories, as in no techpack drivers and no devicetree sources at all. The new Xiaomi 12S series still has not seen any open source kernel release.
I hope this project helps to set a better starting point than the xiaomi oss release to other developers for the Xiaomi 12 and Xiaomi 12 Pro.
Thanks for thus clarification Arian. Sad story....To be continued... Quo Vadis Xiaomi?
ti think the xiaomi 12 has suffered a performance squeeze... this is not because of the heat.... i have tried thermal unlocking and overclocking the CPU GPU and updating the driver 617 the result shows the real performance is vastly different many
Can you tell me which version of clang can be used to build the kernel from the sources for lineageos 20? And which commands to use? I would like to build a kernel for Kali Nethunter, but when using any of the defconfig I get compilation errors
Can you explain how to flash built kernel..? I built the kernel and I get the kenrel image but I don't know how to flash it to the device...
Would you know if this is also the case for Mi11 Ultra tree?
The OSS for the 12S and 12S Pro has just been released recently if anyone is interested in looking at it:
GitHub - MiCode/Xiaomi_Kernel_OpenSource at mayfly-s-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
I would be interested to hear if the kernel source for the 12S family is also incomplete, like the regular Xiaomi 12 series
pj_ said:
Can you explain how to flash built kernel..? I built the kernel and I get the kenrel image but I don't know how to flash it to the device...
Click to expand...
Click to collapse
You need to pack the boot, vendor_boot, vendor_dlkm and dtbo images, the easiest way is to do that within the LineageOS tree.
KeepingKeyes said:
The OSS for the 12S and 12S Pro has just been released recently if anyone is interested in looking at it:
GitHub - MiCode/Xiaomi_Kernel_OpenSource at mayfly-s-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
I would be interested to hear if the kernel source for the 12S family is also incomplete, like the regular Xiaomi 12 series
Click to expand...
Click to collapse
Yes, unfortunately this devices source situation is even worse. On all the recent releases xiaomi did not release the audio, display and camera drivers. The released touchscreen driver does not compile either, though i fixed that by guessing and the driver works now: https://github.com/xiaomi-sm8450-ke...3b9d0f69ecd2ba01674a0dc29cfdc86782bb7c9d6c3da