Related
I am about to buy this phone because it is just so damn good for it's very low price tag, however one thing is bugging me about it. I came here to find that there are no Marshmallow ROMs for it yet and the main reason for me wanting to upgrade my phone in the first place is so that I will be able to run the latest Android ROM's without performance problems. I am currently on CyanogenMod 13 on my old Samsung Galaxy S3 and I like it, but it is slow. The Redmi Note 2 doesn't even have CyanogenMod support.
Is this because Xiaomi are going to release an official MIUI based on Marshmallow? I don't want to buy this phone if it means I am going to be stuck on MIUI or on an older version of Android. I am a bit perplexed because this phone sold a lot so why hasn't anyone made Marshmallow for it yet?
Do you think that development is going to pick up for this device or is this device a bad option if you want to run the latest Google Android (not MIUI)?
Certainly, the RN2 is a lot of hardware for the money, but without source code, things are limited to either repacked/tweaked roms, or roms that are built from source, but have significant hardware functionality imperfections because source is not available. It doesn't seem clear to me whether Xiaomi will release a Marshmallow-based MIUI for the RN2 or not. Some people say yes, some people say no, so until it actually happens (if it ever does), who knows. I also bought the RN2 because it was so much hardware for the price, but I am also disappointed with the lack of CM and similar. This is certainly not for a lack of people not trying, but it seems like certain parts of the hardware will never become functional with CM unless the necessary source code is released. If you don't happen to use these parts of the hardware, well, maybe it doesn't matter. Personally, I have stuck with sMIUI because all the hardware is completely working, but I sure wish a CM version with all working hardware will eventually emerge.
verbage said:
Certainly, the RN2 is a lot of hardware for the money, but without source code, things are limited to either repacked/tweaked roms, or roms that are built from source, but have significant hardware functionality imperfections because source is not available. It doesn't seem clear to me whether Xiaomi will release a Marshmallow-based MIUI for the RN2 or not. Some people say yes, some people say no, so until it actually happens (if it ever does), who knows. I also bought the RN2 because it was so much hardware for the price, but I am also disappointed with the lack of CM and similar. This is certainly not for a lack of people not trying, but it seems like certain parts of the hardware will never become functional with CM unless the necessary source code is released. If you don't happen to use these parts of the hardware, well, maybe it doesn't matter. Personally, I have stuck with sMIUI because all the hardware is completely working, but I sure wish a CM version with all working hardware will eventually emerge.
Click to expand...
Click to collapse
Thanks for the explanation. It seems really unfortunate that they haven't released the source. I guess I should either buy the more expensive Mi4 (which I believe the source is released for) or I can just wait it out and see if the source code get's released for the RN2. It seems strange to me that they wouldn't release Marshmallow-based MIUI for such a popular, fairly new phone. I think they will release it. If they release MM-MIUI then will that enable other developers to bring stock Android Marshmallow or CyanogenMod to the RN2?
M will deffo be released for RN2. Main reason we still dont have it is:
a) first "official" device with M is supposed to be mi5
b) MTK prolly didnt polish 6.0 yet
Major companies that use X10 (eg Sony & HTC) didnt realse M for their devices either, at least as far as i know, however they are planned. So yeah M will arrive eventually, which is great, but that doesnt mean custom roms will get any better. And knowing xiaomi, and their kernel release policies, this is pretty much 100%. Pretty sure they still havent released any kernel source for their older MTK powered devices.
I think I'm going to buy the Mi4 rather because its kernel is open. I want to know that I'll be able to get android roms of any new releases. It's a real shame because the Redmi Note 2 is cheaper and a more superior device, but I have read that Mediatek are scumbags when it comes to releasing kernels because they want to force you to buy a new device when your OS becomes outdated which goes against the open source licence of Linux. Oh well, I guess that's business.
rimpy said:
If they release MM-MIUI then will that enable other developers to bring stock Android Marshmallow or CyanogenMod to the RN2?
Click to expand...
Click to collapse
If they release MM-MIUI for the RN2, unless they release the source code, this will still mean that roms are cooked/repacked, or built from source, but probably imperfectly due to lack of source. Though MIUI is based on Android, I don't think there are free and open MIUI repositories where one could grab the necessary source code for the RN2.
At this point, like everyone said, it is very unlikely that Xiaomi will ever release the source code for the RN2. Without it, custom ROMs will never be proper, and it's the reason there are no MM builds yet.
However, even though MIUI is horrible and God knows that I hate it, it's quite usable. A version of the Xposed framework that works on the latest MIUI builds has been released a couple of days ago, and with it you can get most of the functionality a custom ROM provides. It's not perfect, and I'd prefer AOSP, but it is, IMO, the best this phone has to offer at the moment.
I only got mine about three months ago, and while there were many times I came to regret my purchase, every other phone in this price range and slightly above has inferior hardware. With that said, if you want a phone running AOSP or something very close to it, you'd be better off getting a Nexus or a device that is officially supported by CM.
Thanks all. I was just about to buy the RN2 but I am glad I posted here first. I've learnt a lot and I don't think I would be happy with a phone that has a closed source kernel. The Mi4 has a smaller screen, no SD slot, slower, and costs more, but its kernel source is released and it is supported by CM13. Still very good value for money so that's gonna be my next phone.
It actually isnt slower. Benchmarks only. If you run them side by side with either MIUI or CM youll see than Mi4 is actually much faster than RN2, so yeah, its a better option if you have the money
Just thought I'd make a thread about discussing the next version of Lineage OS. Lineage OS 15 is going to be out officially for our Axon 7 soon after the source code for Android 8.0 is released.
Haha how do you know that? I doubt that.
If past experience is any indication, I wouldn't expect it until about November.
Delete
OrdenKrieger said:
Haha how do you know that? I doubt that.
Click to expand...
Click to collapse
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
ethanscooter said:
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
Click to expand...
Click to collapse
Doesn't mean that there is always some1 to maintain the device.
Edit: BTW I don't think that blogspot pages like http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/ being the best source.
Mod Edit: (non-English comment removed)
请仅用英文发表。谢谢。
Qǐng jǐn yòng yīngwén fābiǎo. Xièxiè.
Please post in English only. Thank you.
ethanscooter said:
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
Click to expand...
Click to collapse
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
OEM's are now required to provide support for two full yrs
TeutonJon78 said:
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
Click to expand...
Click to collapse
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
It's not about AOSP , you can't build for non Google devices without CAF which hasn't been brought up yet.. It'll be a good month or so
kdp162 said:
OEM's are now required to provide support for two full yrs
Click to expand...
Click to collapse
No they are not, it's optional, there is no incentive for them to do so
TeutonJon78 said:
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
Click to expand...
Click to collapse
How come my Moto G 2013 still gets newest LOS then? Does that mean that Motorola still does the above things? Not questioning you, just wondering.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
You can compile AOSP for just about anything. It's getting ALL the hardware working correctly on a new release that's a problem. Sure, it might boot, but if you don't have audio or accelerated graphics, that's an issue. Once you have a working version from the vendor, then it's a lot simpler than just putting it together before that. And nothing happens if you don't have the drivers from the SoC vendors. That's why Project Treble is such a big deal, because if it works as intended, it will remove the need for those new drivers to get a new version of Android, because the HW abstraction layer will make the older drives work.
Waancho said:
How come my Moto G 2013 still gets newest LOS then? Does that mean that Motorola still does the above things? Not questioning you, just wondering.
Click to expand...
Click to collapse
It could be that Motorola is releasing the drivers/SW updates. It really depends on the underlying hardware. If there is another device with the same hardware getting updated, those drivers can be pulled over and incorporated (the A7 has pulled a lot from the OP3). Or there are open source driver versions that could be pulled in.
Our biggest issue is that the audio chip we have isn't really on any/many other devices. So getting fully working drivers for that is a more limiting factor, than a Moto G 2013, which probably doesn't have anything outside of the standard QC SoC stuff.
And in the end, it comes down to the devs keeping stuff up to date. The Galaxy S2 is still running official LOS 14.1, because there are some crazy ass devs out there still getting stuff working on it. The more popular and easy to work a phone is, the more likely it will see longer 3rd party support. Sadly, the A7 is a little limited in both fronts combined with custom HW bits. The devs have done amazing work so far.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
I disagree that LOS on 14.x works great. I tried various builds and kernels for about 6 months. I dropped back to a rooted stock since the gpu and audio support was awful. I have a much better experience than I had on LOS or RR. I could barely even use my daydream with it.
therock11 said:
I disagree that LOS on 14.x works great. I tried various builds and kernels for about 6 months. I dropped back to a rooted stock since the gpu and audio support was awful. I have a much better experience than I had on LOS or RR. I could barely even use my daydream with it.
Click to expand...
Click to collapse
For gamers and daydream users that could be true.
When it comes to usability, privacy and customizations the LOS based ROMs are the first choice.
The audio issues are just minimal when you combine Dolby Atmos mod with custom rom.
So have you guys taken a look at Ordenkriger's post on the boot up of Lineage 15 with all the progress and what not?
We are getting LOS 15 a.k.a Oreo for our device http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Cyberwolf2 said:
We are getting LOS 15 a.k.a Oreo for our device http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Click to expand...
Click to collapse
That's not an official source
bkores said:
That's not an official source
Click to expand...
Click to collapse
Ordenkrieger and Unjustified Dev think's otherwise..https://forum.xda-developers.com/axon-7/how-to/oh-lineageos-15-t3668956
So, according to these:
https://www.xda-developers.com/project-treble-android-o-exist-flagship/
https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/
any existing device can get project Treble support.
It doesn't have to ship with Oreo.
(although all devices that do ship with it will have to support Treble as a requirement)
Google's own Pixel and Pixel XL, as well as Huawei's Mate 9 were definitely not shipped with Oreo on board, but were made Treble compatible, which is great news.
Could we show ZTE this somehow and hopefully get them to add project Treble support?
This can help all of us tremendously (the devs mainly and us as users) and offload ZTE a lot of time with updates because they can be way faster with Treble, hopefully on any new Axon they release, not just on the Axon 7.
What are your thougts on this?
it would be a good thing, as it would extend the phone's life, but im not too positive that zte is going to implement it, sadly. but there still is a chance for that. as we know, axon M uses basically the same hardware, and if axon m is going to support the feature maybe the axon 7 will have it too. you never know with zte, as they do some things surprisingly well, while they do other things lame. time will tell.
hope it too that ZTE will join Treble soon
gogo ZTE!
regards ice
I believe there's someone from ZTE on XDA, maybe he would ask?
reas0n said:
I believe there's someone from ZTE on XDA, maybe he would ask?
Click to expand...
Click to collapse
Good Idea, gonna try to find him and tag him.
Hey @Sunn76 you may be interested in this mate!
hope it helps!
The good news is that Google got Qualcom to support Treble on their Snapdraggon 821 so they could update their Pixel. That takes care of the largest stumbling block. The bad news is that ZTE will likely need support from some other their other part suppliers and unlike Google, ZTE doesn't have the muscle to strong-arm them
Bump. Let's make this happen ZTE!
Doubt it will happen. Be lucky to get a stable O ROM at all IMO. The next Axon is where ZTE will put development effort.
I'd certainly be happy if they did do an O ROM supporting it though......
nfsmw_gr said:
Hey @Sunn76 you may be interested in this mate!
hope it helps!
Click to expand...
Click to collapse
Still reading in the background[emoji5]
And yes I will pass it on
Gesendet von meinem ZTE A2017U mit Tapatalk
@Sunn76 thanks! We really appreciate you passing on the message that the community would like support for project treble (and API2 ).
Thanks.
Sunn76 said:
Still reading in the background[emoji5]
And yes I will pass it on
Gesendet von meinem ZTE A2017U mit Tapatalk
Click to expand...
Click to collapse
Great, thanks man
Api2 for camera is important as well, If I'm not mistaken there is a thread for that already posted!
I want this phone to support everything too. It's a great phone. Camera 2 api and treble would bring ZTE to legendary status in my eyes.
However I am a realist too and I understand where money is to made and I can tell you now there's nothing at all in it for ZTE to give us anything extraordinary at all.
At the end of the day I paid half the money for a phone that I believe to be in some ways better than flagship models costing twice the amount and I realise that so my feet are firmly on the ground.
Be realistic with your expectations and don't be disappointed. There aren't any other phones as good as this when it comes to pure bang for buck and things like treble and camera 2 api also aren't enabled on phones far more expensive than ours.
RobboW said:
Doubt it will happen. Be lucky to get a stable O ROM at all IMO.
Click to expand...
Click to collapse
I'm curious what makes you doubt a stable O ROM will be available for the Axon. It's got a what I assumes is a stable LineageOS 14.1 at the moment.
They've recently come down a bit in price and I was thinking of picking one up to replace a Nexus 6P which suffered from the random reboot problem (using modified kernel, only little cores to get it stable).
I won't buy any phone unless I know it has decent custom ROM support.
What ZTE does with this phone will define how well the next phone sells. ZTE isn't mainstream enough to sell phones just out of carrier partnerships and advertisements. Word of mouth is a huge factor and if people aren't satisfied, they will not recommend the phone.
Another factor are Android news websites who will give free advertisements when axon 7 gets oreo and/or treble by reporting on it.
Gryphticon said:
What ZTE does with this phone will define how well the next phone sells. ZTE isn't mainstream enough to sell phones just out of carrier partnerships and advertisements. Wired of mouth parts a huge factor and if people aren't satisfied, they will not recommend the phone.
Another factor are Android news websites who will give free advertisements when axon 7 gets oreo and/or treble by reporting on it.
Click to expand...
Click to collapse
I agree.
I'm personally pretty satisfied, and I'd definitely buy a new Axon if it's build similarly to the Axon 7 and the price is right.
Zte has the capability to go big I think if they keep their head straight and not compromise on features or sell their devices as expensive as Samsung does for example.
So I'm confused about treble. So from what I'm reading, it will allow Android to be broken down in parts and integrated into separate roms? So for instance, with our phone, it will allow things like stock axon 7 audio to work with our roms? If not can I got a short understanding of what it involves?
pinkywinky said:
So I'm confused about treble. So from what I'm reading, it will allow Android to be broken down in parts and integrated into separate roms? So for instance, with our phone, it will allow things like stock axon 7 audio to work with our roms? If not can I got a short understanding of what it involves?
Click to expand...
Click to collapse
More or less it means what you said.
The drivers will be independently updated from the core system if I'm not mistaken and this will make updating and porting so much easier.
According to Udev the Axon 7 will not be getting Treble because it does not have a vendor partition
bkores said:
According to Udev the Axon 7 will not be getting Treble because it does not have a vendor partition
Click to expand...
Click to collapse
I don't think that means it can't get a vendor partition because it doesn't have one right now.
We've seen device repartitioning since the early Galaxy S i9000 days.
Nothing is impossible in my books unless proven.
IS IT right that we wont have Project treble for our V30?
Sources are saying yes, we wont have PT.
If thats so then i will move to the Pixel 2 XL...
francois amon said:
IS IT right that we wont have Project treble for our V30?
Sources are saying no.
If thats so then i will move to the Pixel 2 XL...
Click to expand...
Click to collapse
1) No, because it didn't launch with Oreo.
2) Tell me what you want Treble for? You need unlocked bootloader for it to do anything dev wise. Do you have unlocked bootloader? I see you do, so your already have ROMs coming...
Sent via open market LG US998 V30/V30+
ChazzMatt said:
1) No, because it didn't launch with Oreo.
2) Tell me what yourwant Treble for? You need unlocked bootloader for it to do anything dev wise. Do you have unlocked bootloader? I see you do, so your already have ROMs coming...
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I want treble for Update. I dont want to stick with Oreo for 2 years.
francois amon said:
I want treble for Update. I dont want to stick with Oreo for 2 years.
Click to expand...
Click to collapse
With Treble, [b<OEMs and carriers still push any updates.[/b] That doesn't change.
The only thing that changes is one stage (silicon middleman) is cut out, which THEORETICALLY will make any planned updates faster.
If LG wants to give P to V30, they'll still give P.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
With Treble, [b<OEMs and carriers still push any updates.[/b] That doesn't change.
The only thing that changes is one stage (silicon middleman) is cut out, which THEORETICALLY will make any planned updates faster.
If LG wants to give P to V30, they'll still give P.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Maybe but i think we have to wait for Android P in the secound quater of 2019..
Yes, probably.
Sent via open market LG US998 V30/V30+
I want treble for driver updates. I do a lot of emulation and the v30 kinda sucks in emulation compared to other phones that use the same chipset. Is there a way to manually update the v30s drivers? I know pixel 2xl on treble had major increases in performance from just updated drivers that make it seem on par with the newly launched snapdragon 845 chip phones. I don't want to root my phone either, I have package disabler installed in the v30, I disabled certain apps, didn't notice a huge bump in performance.
ChazzMatt said:
1) No, because it didn't launch with Oreo.
2) Tell me what you want Treble for? You need unlocked bootloader for it to do anything dev wise. Do you have unlocked bootloader? I see you do, so your already have ROMs coming...
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
1) That's not entirely correct. Only devices launching with Oreo are required to have Project Treble but any manufacturer may choose to add Project Treble to any device being updated to Oreo or newer from Nougat or older. It'll be a little difficult for manufacturers to add Project Treble to existing devices but it should lower the cost and increase the speed of update releases.
2) How about quicker and more frequent updates?
eAbyss said:
1) That's not entirely correct. Only devices launching with Oreo are required to have Project Treble but any manufacturer may choose to add Project Treble to any device being updated to Oreo or newer from Nougat or older. It'll be a little difficult for manufacturers to add Project Treble to existing devices but it should lower the cost and increase the speed of update releases.
2) How about quicker and more frequent updates?
Click to expand...
Click to collapse
1) No OEM is going to put the work into something like that unless they are forced to. V30 didn't launch with Oreo, so no LG Treble. Everyone wishing for it was delusional. OEMs and carriers don't care about faster updates -- slower updates help them sell new phones. Only Google cares about faster updates so has made Treble a requirement for all phones going forward.
2) Theoretically faster updates with Treble. Not "faster" updates, period.
We'll see. Carriers and OEMs will still be pushing the updates out when they want. In 2016, Verizon sat on Marshmallow update the Droid Turbo for almost six moths (July - December) because it was still fantastic hardware. With Marshmallow, late 2014 Droid Turbo (with 3900 mAh battery, 3GB RAM]) would compete too well with the 2016 Moto Z and Moto Z Force they were launching in 3rd quarter. No need for stupid Moto battery mods!
So, while ALL the other Quarks had Marshmallow in July, Verizon sat on theirs until almost end of December. And no they weren't "testing". All the beta tests happened before then. For GREED reaaons, Verizon didn't want the phone to have the update. Project Treble can't force carriers to release updates faster than they want to release them.
An example of why we need project Treble:
https://developer.android.com/preview/devices/
We are not on that list because LG doesn't care about his clients.
EruElUnico said:
An example of why we need project Treble:
https://developer.android.com/preview/devices/
We are not on that list because LG doesn't care about his clients.
Click to expand...
Click to collapse
Yes, all the phones there have Treble support. But do you see a Samsung phone there? The S9(+) has Treble, but isnt on that List either. Neither are any Huawei/Honor phones. There are plenty of those with treble support.
And no, you cant just simply take any of those Images and try to port it. I tried.... (currently waiting for a guide from a guy who managed to port it to the Moto Z)
PS: currently trying to figure out what makes my LOS15.1 unstable (rebased my device tree on the GSI device tree from phhusson, and just added all vendor stuff, and left out the rest), if that works, i know where to search for errors. If it doesnt, im completly out of ideas xD
I can't find any information on the kernel source release situation. Last time with Mi 12, the sources were posted immediately with the release of the phone. Is there a reason for the delay or xiaomi decided to go back to the old source release cycle.
Asko on wrong community, try to Mi community, they will maybe know
It looks like Xiaomi is not going to open source this phone's kernel. Xiaomi's open source kernel is now available on only a handful of phones
Dispossible said:
It looks like Xiaomi is not going to open source this phone's kernel. Xiaomi's open source kernel is now available on only a handful of phones
Click to expand...
Click to collapse
Is this claim official? How much can you believe in this?
user2332 said:
Is this claim official? How much can you believe in this?
Click to expand...
Click to collapse
Sure, I can give you Xiaomi official opensource kernel link. https://github.com/MiCode/Xiaomi_Kernel_OpenSource
You can see that Xiaomi has been very negative about opensource kernel in recent years.
So, the third-party ROM such as LineageOS will be very hard to make or even can't make.
Under the GPL license, Xiaomi is supposed to provide opensource kernels for all of its devices.
Samsung, OnePlus, MOTOROLA, Nokia and some others can follow the GPL.
But there is no penalty for violating the GPL.
Xiaomi Shows No Interest in Releasing Kernel Source Code of its Devices
Xiaomi is having a good time in all the smartphone markets over the world releasing numerous devices. It is popular for producing budget-friendly phones. It has a great user base in the Indian market…
www.thecustomdroid.com
but
newer platforms all use GKI, which means it's identical between devices, even if the SoC vendors are different.
Not sure that they are obliged to release source codes for vendor kernel modules, those are proprietary.
Its a shame... May be they are somethink bigger behind, probably money ...
snx413 said:
Its a shame... May be they are somethink bigger behind, probably money ...
Click to expand...
Click to collapse
Seems to be the beginning of the end for some brands like OPPO/ONE PLUS who are considering withdrawing from the international market.
NOSS8 said:
Seems to be the beginning of the end for some brands like OPPO/ONE PLUS who are considering withdrawing from the international market.
Click to expand...
Click to collapse
But Oneplus opensource is still good. Oppo opensource is still bad.