Xiaomi releases the kernel sources for the Redmi K30 4G/POCO X2
After a year and half long waiting period, POCO finally expanded its portfolio with the launch of POCO X2 in India. While not a direct successor to the POCO F1, the POCO X2 is filled with all the right ingredients necessary to make its own name. With a smooth 120Hz display, a bigger battery, improved cameras, and even cheaper starting price, the device should face no issue convincing potential buyers. However, it’s not just the low price point that makes POCO so popular among enthusiasts. The part of the appeal also comes from the company’s dev-friendly nature and willingness to support the modding community.
POCO X2/Redmi K30 4G XDA Forums
Speaking at the POCO X2 launch event yesterday, C. Manmohan, POCO General Manager, reiterated their support for the community and promised that the company will provide the kernel sources for the device from Day 1. As promised, the kernel sources and device tree for the POCO X2/Redmi K30 are now live on the company’s GitHub. It should be noted that the POCO X2 is just a rebranded version of the Redmi K30 4G and hence the same code is applicable for both devices. POCO is in the process of carving its own identity which is distinct from Xiaomi, but for now, the kernel source release comes from Xiaomi’s official GitHub repository. You can review the source code by visiting the link below.
POCO X2/Redmi K30 4G Kernel Sources
The release of the kernel code will greatly aid the development efforts and we can look forward to developers booting TWRP and bringing early port of AOSP-based ROMs in the following weeks. The POCO F1 remains one of the most popular devices on our forums and with the release of kernel sources, the POCO X2 has set itself on the same path. The device will go on sale in India starting February 11th from Flipkart for a starting price of ₹15,999 ($225).
The post Xiaomi releases the kernel sources for the Redmi K30 4G/POCO X2 appeared first on xda-developers.
from xda-developers https://ift.tt/2GXTwxI
via IFTTT
No comments: