I seem to have stumbled across some vendor blobs for Xiaomi 9 (Cattail). I was wondering if this was usable to compile a workable kernel. if not, could anything be done with the source i am attaching?
GitHub - Vendor-Blobs/android_vendor_tree_xiaomi_cattail: Redmi 9/9 Activ (cattail) - Android 11 - Vendor Tree - V12.5.6.0.RCTINXM
Redmi 9/9 Activ (cattail) - Android 11 - Vendor Tree - V12.5.6.0.RCTINXM - GitHub - Vendor-Blobs/android_vendor_tree_xiaomi_cattail: Redmi 9/9 Activ (cattail) - Android 11 - Vendor Tree - V12.5.6.0...
github.com
Hopefully we could get something out of this
TheDuckWithAMonocle said:
I seem to have stumbled across some vendor blobs for Xiaomi 9 (Cattail). I was wondering if this was usable to compile a workable kernel. if not, could anything be done with the source i am attaching?
GitHub - Vendor-Blobs/android_vendor_tree_xiaomi_cattail: Redmi 9/9 Activ (cattail) - Android 11 - Vendor Tree - V12.5.6.0.RCTINXM
Redmi 9/9 Activ (cattail) - Android 11 - Vendor Tree - V12.5.6.0.RCTINXM - GitHub - Vendor-Blobs/android_vendor_tree_xiaomi_cattail: Redmi 9/9 Activ (cattail) - Android 11 - Vendor Tree - V12.5.6.0...
github.com
Hopefully we could get something out of this
Click to expand...
Click to collapse
Vendor blobs are part of what is needed to build custom ROMs. To build a kernel you need to find the kernel source code for your model number.
Would it be possible to use a similar but more popular device's build which has its source available, and modify it for my device?
I'm planning to do it as a hobby, so no rush
TheDuckWithAMonocle said:
Would it be possible to use a similar but more popular device's build which has its source available, and modify it for my device?
I'm planning to do it as a hobby, so no rush
Click to expand...
Click to collapse
From what i've seen in my research,there are quite a few people who are looking for 64 bit ROM's for cattail,but i suppose that this method might not be the most reliable since i've come across a lot of people reporting bricked devices cuz of it
Related
Hi there.
I wanted to know is the proprietary blobs and device/vendor tree different for each version of Android (like nouget vs Android o)?
Can a properly working proprietary blobs and device/vendor tree for Android 7 be used to port or build Android 8 based ROM once the latest version of Android comes out for full deployment?
Xiaomi has just released kernel sources for tiffany（Mi 5x ). the official github page is:
https://github.com/micode/xiaomi_kernel_opensource/tree/tiffany-n-oss
Just as on tissot N, Xiaomi have squashed all their changes and applied over wrong CAF tag.
I took the proper caf base (LA.UM.5.6.r1-06100-89xx.0) and applied Xiaomi changes over it with some cleanups here.
If any devs are interested in it: https://github.com/Flex1911/tiffany
bt4wang said:
Xiaomi has just released kernel sources for tiffany（Mi 5x ). the official github page is:
https://github.com/micode/xiaomi_kernel_opensource/tree/tiffany-n-oss
Click to expand...
Click to collapse
Good news
bt4wang said:
Xiaomi has just released kernel sources for tiffany（Mi 5x ). the official github page is:
https://github.com/micode/xiaomi_kernel_opensource/tree/tiffany-n-oss
Click to expand...
Click to collapse
hope to see LineageOS soon
I got a question
Will unofficial stuff like Lineage os or Twrp Recovery develop into Official builds? I mean Official builds are powered by individual maintainer right?
A few weeks after the new Android 9.0 Pie update, Xiaomi released kernel source code for Pocophone F1 (beryllium) publicly through GitHub.
[Please note that Poco F1 shares the same branch as Xiaomi Mi 8 (dipper), which has similar specs.]
Pocophone F1 kernel source:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/dipper-p-oss
~Aluminium X
On my phone:
Code:
beryllium:/ # uname -r
4.9.112-perf-g4aff1b2
It means the kernel is compiled from commit "4aff1b2", but this branch of git repo doesn't have such commit.
could it be that the sources used internal for releases are different from what Xiaomi actually shares public?
these kernels are clang ready
https://github.com/milouk/Sphinx-Beryllium
https://github.com/DevMashru/android_kernel_xiaomi_sdm845
https://github.com/Pierre2324/NGK_android_kernel_xiaomi_sdm845
https://github.com/LineageOS/android_kernel_xiaomi_sdm845/tree/lineage-16.0
toolchain + tutorial
https://github.com/kdrag0n/proton-clang
some patches for lineageos attached
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