Database Info

Release Of Kernel Sources & Custom Rom Development ?

Will Xiaomi release kernel sources fully for this smartphone & therefore able to have active rom development (including Android M 6.0 roms) in the near future ?
(Kernel sources for the Xiaomi Mi3 & Mi4 were released very late and not in full and are the reason I believe that many Lollipop roms for these devices are not stable).

I think it depends on whether the device goes international. They were quick to release the sources for the Mi4i, and that is the only phone they officially sell internationally. That said, at least it uses the most common SOC of 2015.

Does it help that it has the same soc as the nexus 5x?

ermacwins said:
Does it help that it has the same soc as the nexus 5x?
Click to expand...
Click to collapse
It helps a little bit maybe, but the problem is all the other stuff inside the phone is different. You still need proper sources from Xiaomi.
M.

Do Xiaomi devices have root "built-in" ?
I'm interested in ROM development, too, but for the first months having root would be enough.

Giocarro said:
Do Xiaomi devices have root "built-in" ?
I'm interested in ROM development, too, but for the first months having root would be enough.
Click to expand...
Click to collapse
I have seen a guide on MIUI forum: "How to flash TWRP Recovery and Super Su(Root) on Xiaomi Mi4C"

Having access to kernel will also mean ir blaster will work on custom roms?

ermacwins said:
Having access to kernel will also mean ir blaster will work on custom roms?
Click to expand...
Click to collapse
Don't count on that. Many device that have kernel source and ir blasters still don't work on aosp based roms. Due to all the drivers for the hardware being closed sourced.

zelendel said:
Don't count on that. Many device that have kernel source and ir blasters still don't work on aosp based roms. Due to all the drivers for the hardware being closed sourced.
Click to expand...
Click to collapse
When we say kernel source, is that pertaining to the soc?

ermacwins said:
When we say kernel source, is that pertaining to the soc?
Click to expand...
Click to collapse
The kernel covers all aspects of the device in one form or another.

zelendel said:
The kernel covers all aspects of the device in one form or another.
Click to expand...
Click to collapse
Let's say xiaomi is taking long to release their kernel source but the source for nexus 5x soc is out, would that be enough for aosp rom?

ermacwins said:
Let's say xiaomi is taking long to release their kernel source but the source for nexus 5x soc is out, would that be enough for aosp rom?
Click to expand...
Click to collapse
No it won't. You will also need the device tree for this device. It's not how long it takes for them to release it that I would be worried about. It's if the source is complete and not broken like they are known to release. They have a habit of release broken source to force users to use miui. If you look at other devices from this OEM it takes months some times a year before they release it and when they do it is broken and devs have to take weeks to get it even remotely working. Then there are still bugs that are never fixed.

zelendel said:
No it won't. You will also need the device tree for this device. It's not how long it takes for them to release it that I would be worried about. It's if the source is complete and not broken like they are known to release. They have a habit of release broken source to force users to use miui. If you look at other devices from this OEM it takes months some times a year before they release it and when they do it is broken and devs have to take weeks to get it even remotely working. Then there are still bugs that are never fixed.
Click to expand...
Click to collapse
So having an aosp based rom as a daily driver is out of the question?

ermacwins said:
So having an aosp based rom as a daily driver is out of the question?
Click to expand...
Click to collapse
isn't the Broken OS ROM by TS Team AOSP based ?

Of interest:
[News] Mi 3/4/Note Kernel Source Code Released! Next to Be, Mi Note PRO, Mi 4c/S:
http://en.miui.com/thread-235127-1-1.html

Don't sceptical, I reconstruct Redmi 2 kernel source without any help from Xiaomi. They released Redmi 2 kernel source for KitKat when my device already run "fully open source" and almost bug free Marshmallow :laugh:

WIP* ( port) Linage OS LG Stylo 2 plus

Development is dead. Please delete..

Rmontoya83 said:
Good news I have a working Linage OS 13 build for the lg stylo 2 Plus GSM. Thought it was bug free still has some issues though . My PC took a dump I have the sources saved on my hard drive I will have a new PC on Feb 6 and will release the Rom For Free probably with in a few days from then. As I'm almost done porting a working lineage OS 14 for the device.
I will update the device tree on Github So I can get help from other devs to trouble shoot these issues better and collaborate works. I will also include a working recovery with the Rom for free . I am doing this in my free time so please be patient .
I will keep you posted ?
Any people interested in helping let me know.
Click to expand...
Click to collapse
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT

cragains said:
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT
Click to expand...
Click to collapse
You can downgrade your firmware .

Nice work let me know when the source is up at github , i may be able to help

I'm so anxious I can't wait to get my new PC! I will be compiling a lot faster. You guys are going to like this lineage OS port. Hang in there

Any screenshots?
I'm interested in this also

Pelegius22 said:
Any screenshots?
I'm interested in this also
Click to expand...
Click to collapse
Not at the moment I had the backlight on my display burn out . had to flash the stock rom back for warranty purposes and for some reason every time I try and back up via twrp the data gets corrupted.
So the only place I have a working Rom is stored on a hard drive and I get my PC back on the 6th this month so it will be up soon.

Twrp link

Rmontoya83 said:
You can downgrade your firmware .
Click to expand...
Click to collapse
No PC right now, I moved across the state, and left my PC.
Can't down grade
LG Stylo 2 PLUS
TWRP no ROOT

Got the new laptop up and running building starts tommorrow.

All souces are downloaded . I will start building the device tree tonight hopefully by end of week myself and @messi2050 will have a working lineage OS build for the ph2n. I stood up all night working on the list of proprietary files need for the build.
Now comes the hard work of adding all the required blobs to get it all functional please be patient. As we are doing this in out free time. Once the device tree is all setup it will be a lot easier to port other roms to this device such as omni aokp DU and so much more. I chose a 13 build as I'm new to this and its a lot easier to port a Rom that has many components that are stable with the version.
If you appreciate our work buy us a cup of coffee. Or hit the thanks button for the Devs working on this build .
Thanks to all the xda community.

We should work on a changelog concerning drivers for cheaper models like my tmousa k550.

(((Poll )))) custom kernel with more governors and overclock or stock kernel?

Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom kernel with more governors and overclock! Let me know if you need me to test, I have MetroPCS variant. Thank you also for your time and development for this amazing device!

Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom all the way.
I am sending this to you in hopes of curing my boredom...

Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.

we need all the help we can get
Giminji said:
Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.
Click to expand...
Click to collapse
@messi2050
has one repository done for device /device
i have the other kernel/
i am working on the blobs using @JackpotClavin utility tool to pull all the blobs needed for the build. once we have a stable tree we can work on building other roms.

Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
https://github.com/RichieRich83
@messi2050
You rock brother.

Rmontoya83 said:
Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
URL deleted I am too new.
@messi2050
You rock brother.
Click to expand...
Click to collapse
Both you and Messi are doing amazing things. When this is done, both of you are getting a cup of java (I couldn't resist Java instead of Joe or Coffee). I downloaded the jackpotcalvindonkey thing yesterday, did the make on it, but didn't get it out.
Btw, your github shows no public repos.

Well that was quick

Request Kernel Sources from Samsung

I don't know if this allowed or not, but with the official release of Oreo now rolling out it would be a good idea for people to request Sammy releases the official Kernel source for developers to crack on with AOSP. If people could do this that would be fantastic.
Instructions as follows:
1. Go to the opensource website: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=G950F (change the value to your device)
2. Click on the "inquiry" letter on the right side of the website
3. Enter your informations (Name/Email and so on), click on "inquiry type", "request for source codes"
4. Source code type: "kernel"
5. Write a message to request the
G950FXXU1CRAP Oreo source code (it's important that you mention the base)
6. Agree the terms and send it to samsung
Thanks to Mohammed in the Telegram chat for these instructions.
Let's get these sources and finally get the AOSP we deserve!

MrDanMak said:
I don't know if this allowed or not, but with the official release of Oreo now rolling out it would be a good idea for people to request Sammy releases the official Kernel source for developers to crack on with AOSP. If people could do this that would be fantastic.
Instructions as follows:
1. Go to the opensource website: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=G950F (change the value to your device)
2. Click on the "inquiry" letter on the right side of the website
3. Enter your informations (Name/Email and so on), click on "inquiry type", "request for source codes"
4. Source code type: "kernel"
5. Write a message to request the
G950FXXU1CRAP Oreo source code (it's important that you mention the base)
6. Agree the terms and send it to samsung
Thanks to Mohammed in the Telegram chat for these instructions.
Let's get these sources and finally get the AOSP we deserve!
Click to expand...
Click to collapse
You won't get aosp from these sources, nougat sources has been out for a very long time and even then there isn't a fully functional aosp Rom.

sofir786 said:
You won't get aosp from these sources, nougat sources has been out for a very long time and even then there isn't a fully functional aosp Rom.
Click to expand...
Click to collapse
FevaX is working on the development with some others. He was working on Lineage 14.1, but decided to hold out for 15.1 instead and Kernel sources.
We can only hope I suppose. I just think there's a lack of developers for our device in this regard but anything that will help FevaX and team would be great.

MrDanMak said:
FevaX is working on the development with some others. He was working on Lineage 14.1, but decided to hold out for 15.1 instead and Kernel sources.
We can only hope I suppose. I just think there's a lack of developers for our device in this regard but anything that will help FevaX and team would be great.
Click to expand...
Click to collapse
I mean I love seeing variety with roms we can flash, but like you said there just haven't been that many devs wanting to work on it. I personally won't be trying a aosp Rom if ever it comes to fruition, i would have bought a pixel phone if that was what I wanted but I know there is some sort of demand for it though so here for you guys to see a fully working release soon

[UNOFFICIAL][ROM][10.0/9.0] LineageOS 17.1/16.0 [violet][Q/PIE]

Introduction
A spinoff thread from the previously-supported-official thread by Atman.
This thread will contain my unofficial builds for violet. On the 16.0 version, the only real fix (so far...) have been the fingerprint scanner sepolicy denials. I aim to do monthly/bimonthly builds to keep up to date with security patches, as so far I haven't encountered any other issues (let me know).
On the 17.1 version, I have slowly figured out how to make it work, but it is highly experimental.
The 16.0 ROM is stable (I use it as my daily driver).
If you find any bugs, please do take screenshots, give a way for me to replicate it on my device, and send a logcat. If you're super smart, use a logcat and filter for the keyword so I don't have to do even more digging
Please don't tell me to use PE/Mokee commits.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Flash instructions
Same as usual:
Reboot to fastboot and flash recovery with fastboot (You have to use the TWRP linked below. Other versions likely won't boot.)
Reboot to recovery TWRP
Wipe to format data, wipe again to wipe system and cache (not necessary if you're updating, only if you're switching ROMs)
Flash firmware (ADB sideload) (this step is dated. The newer builds have a higher target firmware so you should try to flash without the firmware first, then flash the firmware if the ROM doesn't work.)
Flash the ROM (sideload)
Flash GApps, Magisk, etc. as necessary
Done
Downloads (16.0) (STABLE)
Firmware (Dated firwmare)
Recovery (TWRP)
11-Jun-2021 build (with 05-May-2021 security patch), and MD5 Digest
For previous builds see below
Downloads (17.1)
Here's the 17.1 ROM. Here's the md5 hash. It has the March security patch.
It currently does not boot. If you would like to try and help with development, flash the ROM, and then flash the Chinese Q firmware on top of it (this can be downloaded from xiaomifirmwareupdater). Be warned that there is a risk that the newest android keymaster may re-encrypt your device, which in the worst case may require you to format data and/or reflash recovery and/or flash a fastboot MIUI rom. So, it's a bit risky, but likely won't be an issue.
Credits, Sources, etc.
Too many to mention. Atman Shah for getting this device supported earlier last year. ThE_MarD (Marc Bougoin) for other help. Various other names I've seen - Bruno Martins, Weikai Kong, Wang Han... all of the Lineage dev team. I'm sure I'm missing many people who have been involved in the project. I am new, and very much a latecomer to all of this.
Device Tree: https://gitlab.com/mzha/android_device_xiaomi_violet
Kernel Tree: https://gitlab.com/mzha/android_kernel_xiaomi_violet
Other things see my gitlab: https://gitlab.com/mzha
A telegram group to discuss development for 16.0/17.1: t.me/lineageos_violet
Previous builds
07-Nov-2020 (incl. Oct-2020 security patch), with 07-Nov-2020 MD5 Hash
13-Jul-2020 (incl. Jul-2020 security patch), with 13-Jul-2020 MD5 Hash
11-May-2020 (incl. May-2020 security patch), with 11-May-2020 MD5 Hash

Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?

e2vinay said:
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
Click to expand...
Click to collapse
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time

hcnulma said:
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
Click to expand...
Click to collapse
That's great
by any chance will you consider adding signature spoofing support? that would be really great. it would help many users go for microG instead of gapps
I completely understand you're starter.
great work. good luck.
Thank you

e2vinay said:
will you consider adding signature spoofing support?
Click to expand...
Click to collapse
No, but there are a few alternatives:
Merge the changes from this RFC and build it
Download the spoofer from https://download.lineage.microg.org/violet/, or get the (ed)Xposed module, or other possibilities...

Will be official Lineage Os?

Can we expect los 17 soon?

himanshu fulmali said:
Can we expect los 17 soon?
Click to expand...
Click to collapse
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.

Heyyo @hcnulma good to see you got your thread up and going!
As for 17.1? You can work with your current kernel and cherry-pick the fixes that other maintainers of violet are using and same for the device tree and vendor blobs.
As an example, LeEco msm8996 devives are using kernel source code from Marshmallow just rebased on a CAF Q Tag for our kernel since we never got anything newer...
Even once Xiaomi release their kernel source code for Android 10? It would probably take quite a bit of work to shave it down to what you specifically need and then importing it on top of a fresh CAF tag for the kernel or even more work to try and inplement it into uour current kernel.
To get official builds of LOS 16.0 going again for violet you would need to show that you are capable of fixing any major bugs that arise as well.
https://wiki.lineageos.org/submitting_device.html
anywho, hope this information helps bud!

hcnulma said:
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Click to expand...
Click to collapse
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom

Thank you. If he is stable enough I will use it to build RR PIE

Zjh0094 said:
Thank you. If he is stable enough I will use it to build RR PIE
Click to expand...
Click to collapse
It's definitely stable...
prajwal2001 said:
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Click to expand...
Click to collapse
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.

Request to create group for discussion in Telegram

hcnulma said:
It's definitely stable...
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
as every ROM uses the same device tree
and you won't be making pe instead of lineage as the same device tree and kernel are used in every Q ROM except EvoX which uses crimson kernel

hcnulma said:
It's definitely stable...
Click to expand...
Click to collapse
Thanks. I will use it as my benchmark to build RR pie.
---------- Post added 15th February 2020 at 12:03 AM ---------- Previous post was 14th February 2020 at 11:57 PM ----------
hcnulma said:
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
/quick/la/msm-4.14

prajwal2001 said:
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
Click to expand...
Click to collapse
It is precisely the device tree that I'm worried about. From experience, PE has a lot of platform-specific stuff that Lineage doesn't (and the same the other way), and also from trying to figure out the fix to 16.0 I realised there's a lot of context/definition differences between the two device trees. I'd still give it a look, but I suspect it might be easier to just modify the current 16.0 device tree.
RupeshRN said:
Request to create group for discussion in Telegram
Click to expand...
Click to collapse
https://t.me/lineageos_violet.
Zjh0094 said:
/quick/la/msm-4.14
Click to expand...
Click to collapse
Yeah I already figured it was msm-4.14. Have already cloned it but am also considering cherrypicking changes that other devs have done to their kernel trees from 16.0 -> 17.1 as opposed to starting with the CAF kernel. A work in progress.

Sir I'm noob but mokee dev released android 10 and i think mokee and los are pretty same, will he not help you if you contact him?

An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.

An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.

Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Here's the 17.1 ROM. Here's the md5 hash. Needless to say, it's very experimental, not stable in the least (expect to get past boot maybe 70% of the time) - I'm getting very mixed results when experimenting myself. Nevertheless, try it out, see what you get. Install it the same way as usual. Keen to get as many eyes on this as possible

Lineage OS

Can we expect Lineage OS to be released for realme X3? I have a feeling that it is one of the phones that can really benefit from lineage OS as despite having excellent specifications it is bogged down by terrible software support by realme?

jaidosajh said:
Can we expect Lineage OS to be released for realme X3? I have a feeling that it is one of the phones that can really benefit from lineage OS as despite having excellent specifications it is bogged down by terrible software support by realme?
Click to expand...
Click to collapse
There is no way to know if or when any device will get any kind of custom ROMs. That is a matter of whether someone with the knowledge to create custom ROMs owns one of those devices or not and whether or not they choose to build a ROM for that device and that is only "if" the stock source code has been made available to the public. If the stock source code has not been made available to the public, custom ROMs cannot be built for the device because stock source code is required in the building process.
The short answer is you will just have to wait and see or take it upon yourself to try building LineageOS for your device for yourself. Trying to build it yourself might get you there faster because you might be in for a long wait if you wait for someone else to do it or may never happen at all.