Since kenzo already has AOSP & NOS oreo build available, i just wanted to know if the builds are project treble enabled or not. If not, why not?
no it wont have treble. OEM and qualcomnn must provide drivers etc from a very low level so that it works well. kenzo only had marshmellow, so definetely no. if the device came with android O then it will have.
It's a lot of work which cannot be done by a single person or a team. Even Google has to team up with the silicon vendors and oem to try bring it to current flagships. Lineage Gerrit has some treble related commits, who knows, anything can happen. But it's mostly unlikely.
Related
Hello!
I have been following annual Google I/O 2017 and heard about all the benefits of Google's Project Treble.
I cannot help but wonder how are developers (for example here at XDA) able to create custom roms or unofficial Android updates. Why Google can't make official Android Nougat update for Nexus 7 2013, but you here at XDA can. What is different between your work and Google's when it comes to these things, as far as neither has access to hardware manufacturer's code support.
I have to say I am not a professional software developer, so I understand if this topic is beyond my comprehension.
Thank you!
"Why Google can't make official Android Nougat update for Nexus 7 2013"
Planned obsolescence.
"neither has access to hardware manufacturer's code support"
Google is obliged to release kernel source code because Linux(the kernel powering Android) is released under the GPL. The kernel is responsible for letting Android "talk" to the hardware. Developers at XDA can then modify the open-source kernel to "fit" newer versions of Android.
I'd like to chime in on this.
Let's use the Nexus 7 2013 as an example. The difference between what an official build of Nougat from Google would be and what a build of Nougat from XDA is that the Google released one will have updated devices drivers that are made specifically for Nougat, while the XDA released one simply uses the older device drivers and hope they work. In some cases they work flawlessly (mostly on Nexus devices), however other times there are things that don't work so they either need to be disabled or worked around. So essentially a Google released OS has everything updated and tested to work with the new OS, while XDA releases are more 'hacked' together to work (simply because the device drivers aren't Open Source). Google may not have access to the hardware drivers, but they still get them updated.
Now let's touch on Project Treble (and why I am so excited about it). Instead of each and every device driver needing to be upgraded and tested for each new OS version, the OS version will specify which version of the drivers (HAL's) will work with the OS. This means there will be a separate space where all the device drivers will reside, and the OS will simply load those when booting (no more proprietary binary blobs to include in the ROM! hopefully...).
This means on any Project Treble compatible device (all phones that ship with Oreo, and some that update to Oreo) with an unlocked bootloader, a user can simply compile AOSP and flash it directly to the device with no modifications and have the device work. I believe this is actually a requirement to pass Google's certification process for new devices with Oreo. That means, say, with the LG v30 if the bootloader is unlocked, there can be an AOSP ROM on day one of its release.
So instead of Android being strictly a per device compile, it is just a general compile (sans device specific features). However, this doesn't remove the old driver issue. If the drivers in their respective partition no longer are updated by the manufacturer, the later AOSP code will need to be modified to work around these (and accept them). This is still easier in my opinion than the binary blobs.
As for official updates, Project Treble allows device hardware manufacturers to work on updating the device drivers while the OS Dev (Samsung, etc) works on updating their OS. So it is a parallel development instead of a serial one (hardware AND os instead of hardware THEN os).
A question.
Do the Nexus 5X devices have the Treble system or project incorporated with Oreo?
I do not understand the other manufacturers that cheaper excuses are giving, it is true that they are not obliged but I think it would be good practice, maybe they think as before that you will not buy them a phone.
Does someone make a Change.org or similar campaign to ask all Android manufacturers to make a minimum effort?
Is there a reason why every custom ROM seems to go treble? There's no real proven benefit when having unofficial treble. As one of the LineageOS devs said on their subreddit:
You don't get treble. You have it or you don't. All those "ported treble" are plain fake and they don't have the same capabilities of the "real" treble (the one that you have on your device out of the box or from your manufacturer as a stock ROM update).
This because treble requires appropriate changes to the proprietary files (those stored on the vendor partition) that a device without "stock/real" treble won't have
Click to expand...
Click to collapse
There's only one partition instead of both. The one for seamless updates is missing (I think).
As for treble ROMs, they are pretty much a gimmick unless devs actually make use of them. But I have seen reddit comments about people trying out generic system images via treble TWRP: https://www.reddit.com/r/Xiaomi/comments/8ac2gc/project_treble_is_amazing_and_because_of_this_my/
You can try it for yourself: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
What this could mean is, in 2 years if dev support drops for the Note 4, you may still be able to get the most recent version of AOSP or some other ROM as a generic system image. No need to wait around for devs to create ROMs or compile one yourself.
to all cracks out there in this wonderful xda-universe. does anybody know if the update to Oreo brought also Treble-support?
kurvenmeister said:
to all cracks out there in this wonderful xda-universe. does anybody know if the update to Oreo brought also Treble-support?
Click to expand...
Click to collapse
No. Only devices originally released with oreo, support treble.
@matrixx1
i am asking because some other oems implemented a special vendor partition to their devices. maybe the tab s3 has a unused vendor partition like the oneplus5t. one of the devs of omnirom made the 5t unofficially treble enabled.
Doubt it as it was released with Nougat. Look at the S8/S8+, no treble. S9/S9+ released with Oreo and treble. Maybe the S4 will have treble.
Do you think that repeatedly asking for devs to port Project Treble for Kenzo will help in any way? Do you think that no dev is interested to do this? Chances are, we will not have treble unless Mi Max gets official Oreo support so the devs can port the blobs and start working on treble. Until then, any thread opened just to cry for treble is pointless. If you really can't wait until then, buy a mido or whyred.
Thank you.
That's not true.
New Kenzo sources are Treble-ready, a couple of people are working on making /vendor as independent partition (To be precise: only gralloc and hwcomposer have problems), with a few hours of work will be ready, but the reality is different: Kenzo is dead, It's not worth spending time on it.
forget it
even Xiaomi it self cant even upgrade our MIUI to nougat or oreo.
which the hardware it self is competent
I usually run LOS without GAPPS to have as little Google in my life as possible. LOS because it has active development, seems like a professional operation, gets security updates every months and supports many devices, and it seems the majority of other ROMS are based on LOS.
But there are so many other ROMs available for F1 so I'm wondering if there are any other serious ROMs for F1 that aren''t based on LOS that have been degoogled, are good for privacy, and have stable support.
Maybe in future some dev might port Sailfish OS. That's the most privacy friendly mobile OS.
For now Lineage 16.0 without Gapps is number one.
ubuntu touch is grt ...linux based community support
/e/, but I don't know whether Poco is supported. See the e.foundation website for further details.
guhvanoh said:
/e/, but I don't know whether Poco is supported. See the e.foundation website for further details.
Click to expand...
Click to collapse
supported oreo
i m afraid to flash that coz mi anti-rollback feature
I'm almost sure the anti rollback feature is disabled on our beloved poco but you can still check on with fastboot according to a reddit thread I cannot link for some reason.
SerpentSpirale said:
I'm almost sure the anti rollback feature is disabled on our beloved poco but you can still check on with fastboot according to a reddit thread I cannot link for some reason.
Click to expand...
Click to collapse
ya! i checked it.score 1,means no anti- rollback
type fastboot getvar anti
if it show no 1-3 then no anti rollback enable
above 3 means rollback enable for pie
above 4 means rollback enable for Q beta