Even device like redmi 1s running cm14 ROMs but why our device is not getting cm14 ROM .....
Yeah mate, it hurts. But we can't ask this question bcz technically it will become asking for eta questions which is violation of xda norms (I think so).
To have an official release from Cyanogenmod we need official drivers from the Vendor usually. As soon as Motorola will release a Nougat update for our phone also Cyanogen will release an official rom too I think.
We will get it. Just be patient. The devs are working hard.
Use this ROM. It's based on CM14 and we got the Nougat 7.1 Version since yesterday. Very stable.
We can't have Cm14 yet 'cause they are working directly on CM14.1 based on android 7.1.x, without release a CM14 build based on android 7.0.x
Related
When are we Redmi 3s/plus/prime users are going to get official CyanogenMod Rom. And can we expect Android Nougat update for the same.?
Chill man ? right now we are waiting for kernel release, supposedly in next month. Till then you can check three available cm roms for our Redmi 3S: CM13 by @zwliew, Xperia CM13 port and RR rom. All have small bugs but can be used as daily drivers.
As of Nougat base... I won't count on that.
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
lat94084 said:
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
Click to expand...
Click to collapse
1) We just got Oreo on Quark. I think you should learn to use that first.
2) That Quark Oreo thread you referenced was started in August 2017. When did Quark get Oreo? July 2018.
It's now August 2018, and you are asking for Pie. So, look for Quark Pie in July 2019.
3) Also, like before only @bhb27 can code the necessary kernel for any Quark Pie. It's not who "wants" it, it's WHO can actually do it. Maybe @bhb27 wants to just work on his new Oreo kernel and ROM for awhile. Maybe he wants a different phone...
4) If you read the other thread you say this is based on, discussing it didn't really help bring Oreo any faster to Quark. It still all depended on @bhb27 actually doing the work, and doing it right. See point #2.
_______
Just so I don't have to type everything over from the first thread, read this. In your mind just substitute "Pie" every time "Oreo" is mentioned, and substitute "Oreo" when "Nougat" is mentioned. SAME EXACT SITUATION A YEAR AGO:
AUGUST 24, 2017
jeffkahlo777 said:
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Click to expand...
Click to collapse
ChazzMatt said:
It will take @bhb27 coding the current Motorola Marshmallow Quark kernel to Oreo -- the same way he coded it to work for Nougat.
Our previous CM dev @Skrilax_CZ did the original work back in early 2015, first coding Quark Motorola Kitkat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.
@bhb27 started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel @Skrilax_CZ coded. You could use 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install @bhb27's custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.
(For our Quarks, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When Sunshine unlocked the Droid Turbo bootloader @Skrilax_CZ re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quarks. The kernel is the foundation.)
Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)
By this time @bhb27 had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.
When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @bhb27 did the work to let Nougat ROMs use that kernel.
Will be the same thing with Oreo. But @bhb27 still has to code it to work smoothly with Oreo.
Also, there is no more CM. We now have LOS as the "base". @bhb27 does not release official LOS ROMs, but that's where the device kernel files go that all devs pull from.
So, @bhb27 will use Marshmallow kernel in LOS Oreo tree to make a stock kernel for all ROMs. At that point he will release an Oreo ROM based on that work. (Right now he's the dev for both RR and crDroid ROMs. Last year he surprised us by releasing then-new Nougat crDroid first, whereas he had been dev for Marshmallow RR and Mokee, and RR was his favorite.)
@bhb27 will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.
After he releases his Oreo kernel work, then other Quark devs can use that stock LOS Oreo Quark kernel to release their Oreo ROMs.
The kernel will be the foundation of any Oreo ROMs and it will all depend on @bhb27.
But don't pester him. It will be ready when it's ready.
__________
TLDR: @bhb27 is the man. He'll do the Oreo-compatible stock kernel first and then the first Oreo custom ROM. Everyone else will then follow with other ROMs.
Click to expand...
Click to collapse
lat94084 said:
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752
But for Android 9 Pie, Who wants the new Android in this phone?
Click to expand...
Click to collapse
Hope @bhb27 works on Android 9 pie as well.
once more Thanks @bhb27 your knowledge and Hard work never cease to amaze me :good::victory::victory:
I think it best to focus on android Oreo.
For example in the case of lineage os, we get an unofficial version of it for a few months or a year before the official arrives for our device, but in the case of pixel experience, do we have to wait until the ROM developer makes the 9.0 port or could the developer for our device update it without waiting?
i'm not asking for ETA, just asking if the development is individual or the devs have to wait for the PE source
Our device's maintainer is the ROM developer.
As u know
Nexus 5 got official lineage os 16 rom, including lots of other phone's, my brothers lenovo's a6000 got stable pie rom,its a budget phone from 2015 with snapdragon 410 coupled with1 gb of ram,
I don't know why nexus 6ps development is always lagging behind
nexus 5 is unofficial rom not official
As far as i know, no device has the official lineage rom yet. In Lineage's official site there is a note about it, and there isn't an ETA. Develop a ROM isn't a easy thing, and developers have their own lifes and own jobs. Be patience, soon we'll have a stable rom.
This thread is based on: https://forum.xda-developers.com/moto-maxx/general/android-9-pie-t3825923 (which is based on: https://forum.xda-developers.com/moto-maxx/general/oreo-8-0-t3660752)
But for Android 10 "Queen Cake", Who wants the new Android version on this phone?
@ChazzMatt wrote last year (edited for Android 10 "Queen Cake"):
It will take @fgl27 coding the current Motorola Marshmallow Quark kernel to Android 10 -- the same way he coded it to work for Nougat, Oreo and Pie.
Our previous CM dev @Skrilax_CZ did the original work back in early 2015, first coding Quark Motorola KitKat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.
@fgl27 started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel @Skrilax_CZ coded. You could use CM 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install @fgl27's custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.
(For our Quark, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When SunShine unlocked the DROID TURBO bootloader @Skrilax_CZ re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quark. The kernel is the foundation.)
Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)
By this time @fgl27 had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.
When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @fgl27 did the work to let Nougat ROMs use that kernel.
When Oreo arrived, there was no official Oreo Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @fgl27 did the work to let Oreo ROMs use that kernel.
When Pie arrived, there was no official Pie Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @fgl27 did the work to let Pie ROMs use that kernel.
Will be the same thing with Android 10. But @fgl27 still has to code it to work smoothly with Android 10.
Also, there is no more CM. We actually have LOS as the "base". @fgl27 does not release official LOS ROMs, does release unofficial LOS ROMs, but that's where the device kernel files go that all devs pull from.
So, @fgl27 will use Marshmallow kernel in LOS Android 10 tree to make a stock kernel for all ROMs. At that point he will release an Android 10 ROM based on that work. (Right now he's the dev for both RR and LOS ROMs. This year he surprised us by releasing then-new Pie RR first, then LOS, where as he had been dev for Lollipop RR, Marshmallow RR and Mokee, Nougat RR and crDroid, Oreo RR, Pie RR and LOS, and RR was his favorite.)
@fgl27 will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.
After he releases his Android 10 kernel work, then other Quark devs can use that stock LOS Android 10 Quark kernel to release their Android 10 ROMs.
The kernel will be the foundation of any Android 10 ROMs and it will all depend on @fgl27.
But don't pester him. It will be ready when it's ready.
__________
TLDR: @fgl27 is the man. He'll do the Android 10-compatible stock kernel first and then the first Android 10 custom ROM. Everyone else will then follow with other ROMs.
Thanks for the info.
until 2030 I have this working