https://www.xda-developers.com/google-mandating-linux-kernel-versions-android-oreo/amp/
According to this thread,
Currently existing devices that are upgraded to Android Oreo are only required to run kernel version 3.18 or newer.
And when I checked my moto g4 plus kernel version, it is 3.10.84 which is less than 3.18 Linux version.
So how does moto g4 plus supposed to get Oreo update when it is very time consuming and difficult for Motorola to update both Linux kernel and Oreo at the same time
Easy, the Moto G4/G4 Plus never was going to receive Android O, so this was never going to be a problem!
jack_04 said:
https://www.xda-developers.com/google-mandating-linux-kernel-versions-android-oreo/amp/
According to this thread,
Currently existing devices that are upgraded to Android Oreo are only required to run kernel version 3.18 or newer.
And when I checked my moto g4 plus kernel version, it is 3.10.84 which is less than 3.18 Linux version.
So how does moto g4 plus supposed to get Oreo update when it is very time consuming and difficult for Motorola to update both Linux kernel and Oreo at the same time
Click to expand...
Click to collapse
Either you didn't read properly or misunderstood
Kernel version requirements: Older Android devices released prior to Android O but that will be upgraded to Android O can continue to use their original base kernel version if desired.
Click to expand...
Click to collapse
For more info: https://source.android.com/devices/architecture/kernel/modular-kernels#core-kernel-requirements
Related
Moto x pure 2015 6.0 source kernel released. Would anything be able to come of this for our phone?
There is no (stock) 6.0 and never will be for our phone.
ok :v
Does any one with Oreo beta build can confirm that it supports treble project pleas?
No its not.
We have a build.prop of 8.0 and it has disabled treble.
Project Treble requires kernel version 4.4.Unfortunately the beta Oreo update has kernel version 3.18
effingbadluck said:
Project Treble requires kernel version 4.4.Unfortunately the beta Oreo update has kernel version 3.18
Click to expand...
Click to collapse
No it doesn't it requires a special vendor partion which we didn't have in previous builds
effingbadluck said:
Project Treble requires kernel version 4.4.Unfortunately the beta Oreo update has kernel version 3.18
Click to expand...
Click to collapse
I don't think this is the case - Android 8.0 requires 2017 SoCs to launch with Kernel 4.4 or newer, but older SoCs can use Kernel 3.18 or newer.
https://source.android.com/devices/architecture/kernel/modular-kernels
Kernel changes are required to enable Treble regardless of the base Kernel version.
I for one am disappointed that Treble is not present in the O Beta. So disappointed, in fact, that I will likely sell the device if this isn't present in the final build (which seems unlikely). The only reason I got an A1 was to investigate Treble development.
mwarner said:
I don't think this is the case - Android 8.0 requires 2017 SoCs to launch with Kernel 4.4 or newer, but older SoCs can use Kernel 3.18 or newer.
https://source.android.com/devices/architecture/kernel/modular-kernels
Kernel changes are required to enable Treble regardless of the base Kernel version.
I for one am disappointed that Treble is not present in the O Beta. So disappointed, in fact, that I will likely sell the device if this isn't present in the final build (which seems unlikely). The only reason I got an A1 was to investigate Treble development.
Click to expand...
Click to collapse
me too i got an A1 becouse its an android one device wich should be all stock features and should supports Treble if it dosnt i well sell it and got htc u11 life wich did support it
On the flip side even the near stock OnePlus 5 also will not support treble . Only the pixels seems will get this for now.
Having said that A1 is an ideal candidate for treble
vkk178 said:
On the flip side even the near stock OnePlus 5 also will not support treble . Only the pixels seems will get this for now.
Having said that A1 is an ideal candidate for treble
Click to expand...
Click to collapse
It's not just Pixels - Huawei is really doing a sterling job here and implementing Treble on all its Oreo Beta builds. Essential, HTC and Sony also upgrading various devices to Oreo with Treble support.
Mike
Sent from my Pixel XL using Tapatalk
LIONS1 said:
No it doesn't it requires a special vendor partion which we didn't have in previous builds
Click to expand...
Click to collapse
1st Gen pixel did not launch with treble. They got treble and kernel 4.4 with Oreo. Xiaomi is ****.
Aman301582 said:
1st Gen pixel did not launch with treble. They got treble and kernel 4.4 with Oreo. Xiaomi is ****.
Click to expand...
Click to collapse
No, Google Pixel didn't have Kernel 4.4, they implemented Project Treble on Kernel 3.18
Love4Taylor said:
No, Google Pixel didn't have Kernel 4.4, they implemented Project Treble on Kernel 3.18
Click to expand...
Click to collapse
My bad, but pixels got treble which A1 didn't.
Aman301582 said:
My bad, but pixels got treble which A1 didn't.
Click to expand...
Click to collapse
Correct me if I'm wrong but do we really need treble as this is android one device and it is close to AOSP as possible and as such I'm not really sure we really need it.
However we need the kernel sources and they are still not released.
Will project treble be available for older devices or it will only be made available for new released devices that launched with Android 8.0 Oreo?
justmoto92 said:
Will project treble be available for older devices or it will only be made available for new released devices that launched with Android 8.0 Oreo?
Click to expand...
Click to collapse
All signs point to no for this phone. Moto left it off their list of devices getting oreo. It is very unlikely to get oreo and even less likely to get treble support. The Pure/Style might get a few more security patches, but I wouldn't even count on that. It is >2 years old and had 2 major OS updates; in the android world that makes it due for abandonment.
Only for Oreo out of the box.
Project Treble is enabled only for Oreo OOB device even OnePlus5T dosent support Treble bcoz it comes with N OOB.
Treble need a specify partition on the NAND, so manufacture need to set it up in factory, so NO for Style.
All I want is a official 7.1, but...
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.
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