Related
Will Mi A1 get project treble with oreo update?
what is that?
I hope YES...
mahla13 said:
what is that?
Click to expand...
Click to collapse
The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond (the new architecture is already running on the Developer Preview for Pixel phones).Project Treble separates the vendor implementation (device-specific, lower-level software written by silicon manufacturers) from the Android OS framework via a new vendor interface.
In Android 7.x and earlier, no formal vendor interface exists so device makers must update large portions of the Android code to move a device to a newer version of Android.
But as far as I know project treble is only useful if they are using a custom UI like MIUI, Flyme or Touchwiz. Isn't it treble superfluous without a custom UI?
Localhorst86 said:
But as far as I know project treble is only useful if they are using a custom UI like MIUI, Flyme or Touchwiz. Isn't it treble superfluous without a custom UI?
Click to expand...
Click to collapse
There are some little things, like Xiaomi's camera app. With treble Google could update the OS directly, and Xiaomi could update camera separately.
Am I right? It's more a question than an affirmation
Mendibil said:
There are some little things, like Xiaomi's camera app. With treble Google could update the OS directly, and Xiaomi could update camera separately.
Am I right? It's more a question than an affirmation
Click to expand...
Click to collapse
I don't know. But I imagine Xiaomi could simply realease and update the camera app through the play store. Blackberry does this with it's core apps which can only be installed on blackberry devices.
Localhorst86 said:
I don't know. But I imagine Xiaomi could simply realease and update the camera app through the play store. Blackberry does this with it's core apps which can only be installed on blackberry devices.
Click to expand...
Click to collapse
True. Motorola used to do the same (I don't know if actually does). Maybe Treble it's not that important for us, Android One users.
While Treble is focused on official Android OEMs, Project Treble should also be revolutionary for aftermarket Android ROM projects
https://www.xda-developers.com/why-current-oneplus-nokia-phones-wont-be-project-treble-certified/
We have /system/vendor....
But on the other hand, we have dual partitions, so maybe they dare to repartition. The beta will be out soon, so we will see.
More details about project treble https://arstechnica.com/gadgets/2017/09/android-8-0-oreo-thoroughly-reviewed/2/#h1
so, any update about this as Beta is released in Mi a1. Did anyone find anything?
I can't find the link anymore, but I've had people test it on Oreo firmware and it was confirmed not to have Treble.
Unfortunately we will not
Until we don't get 4.4.x kernel, we won't get project Trebel. I've never seen a SD625 phone running the 4.4.x kernel so we should blame Qualcomm instead of Xiaomi (tested on a Moto G5 Plus).
Seeing as the first Android P Preview came out today, I'm wondering what (and how long) it would take to port it to Project Treble compatible devices.
Considering it is closed source, hard to say...
Though many people are on this.
phhusson said:
Considering it is closed source, hard to say...
Though many people are on this.
Click to expand...
Click to collapse
Nice to know!
When the source code is usually released? With the official release of the new Android version? In this case we should wait September 2018 for android P...
Can't we just flash GSI of already released pixel images?
espireso said:
Can't we just flash GSI of already released pixel images?
Click to expand...
Click to collapse
Released images are not GSI.
phhusson said:
Released images are not GSI.
Click to expand...
Click to collapse
I've learned it from the hard way. I extracted system.img out of newly released pixel.zip. It didn't boot ¯\_(ツ)_/¯
phhusson said:
Considering it is closed source, hard to say...
Though many people are on this.
Click to expand...
Click to collapse
does it always go open source only after all dp r released and stable is out?
zohaibahd said:
does it always go open source only after all dp r released and stable is out?
Click to expand...
Click to collapse
Yes
I too have a question. what if the manufacturer no longer updates their device to android P but the device is trebled supported on Android O. will the devs still can update the device to android P and so on?
Because on not trebled enabled devices still getting the latest OS thru custom roms and powered also by snapdragon SoC.
If we gotta wait until the source is released then what's the point of project treble compared to the usual custom rom developement process ? Correct me if I'm wrong, but isn't treble supposed to allow any device that got a vendor partition to boot any system partition regadless of the hardware used by the given device ?
If I'm not mistaken:
Treble allows for a generic system image to be used. The Android P developer previews are very likely not GSIs: they target a particular vendor configuration. (I wouldn't be surprised to find that they include an updated vendor partition to go along with them.)
A GSI doesn't target a particular device, it targets only the known services specified by a particular release of Android - an Android GSI could theoretically target any specified vendor interface, be it 8.0, 8.1, 9.0, or whatever future interface appears, or even multiple if someone wanted to put in the effort.
That doesn't get past the fact that there is no source for Android P yet, so a GSI can't really be built for it. And the vendor interface doesn't mean that any image will boot on any device - maybe one that depends on a strict subset of what's provided in the vendor interface on a particular device, but I wouldn't be able to grab a Pixel image and load it on a Galaxy S9 or Mate 10 Pro, or otherwise for any mix of devices. They all have dependencies on vendor-specific pieces in their vendor partition, at the very least; there's also /product, /oem, and /odm on the Mate 9, which is also depended upon by it's system.img. A GSI can't depend on the existence of those things, an OEM image can.
Maybe, with a fair bit of work, someone could rip apart the Pixel system image and make a GSI out of it, but P would probably be out before that made significant headway into making it a GSI.
irony_delerium said:
If I'm not mistaken:
Treble allows for a generic system image to be used. The Android P developer previews are very likely not GSIs: they target a particular vendor configuration. (I wouldn't be surprised to find that they include an updated vendor partition to go along with them.)
Click to expand...
Click to collapse
Yup, vendor partition has been updated.
And all your explanation is correct
Are GSIs for future versions of Android going to be released by Google or some other official entity? I thought this was the whole point of Project Treble :|
bemymonkey said:
Are GSIs for future versions of Android going to be released by Google or some other official entity? I thought this was the whole point of Project Treble :|
Click to expand...
Click to collapse
Google does make GSIs available to oems for testing (cts/vts) -- you can find evidence of this in the android-vts google group. I suppose they could make those publicly available, but if they are just stock aosp (with no google apps) they probably don't want to do that yet.
GSIs are a nice outcome of Treble, but that wasn't the main goal.
There is a really good podcast discussing what Treble is over at Android Developers Backstage (episode 75).
Yall need to seriously learn to chill out and enjoy what you have for a second, for real. The P preview is exactly what it is and has always been...a PREVIEW. Just like before when it was only available to nexus devices, it's the same for pixel. Plus, it's highly unstable and buggy as hell right now, and like most previews before this one, a lot of the features will be removed and more added in as time goes.
And to answer your question, ge-n, about what the difference is, it's not an instant invitation to see what Google releases as a preview. For us, our greatest advantage is if you're running a S9 per say (bloated to hell and grossified by their "Samsung experience" aka former TouchWiz) you can get a more stock version if you'd like.
It seems like there's been some movement on this...
How long will we get Stable Treble rom?
MAH35H said:
How long will we get Stable Treble rom?
Click to expand...
Click to collapse
As long as it takes you to develop one.
Will be interesting to see how the P beta program is distributed since it's a lot of treble devices that's getting it now!
So, from searching this forum it seems like people think the V20 doesn't support Treble. I've seen articles that state with Oreo it will. I am running the unofficial Los 15.1 build and downloaded the app that checks for Treble compatibility and it states my phone is treble ready though I don't have the A/B setup. Now looking at treble project builds there are many that state they are a only as well as a/b.
So, is the rooted v20 treble ready with Oreo firmware?
Also, when I do this cmd in terminal - getprop ro.treble.enabled, it returns true.
Is it possible, yes, will they do it, probably not.
You can set the boot LUN now, without Oreo, and force the phone to boot from the *bak partitions (xblbax, abootbak, lafbak, recoverybak, etc)
Notice there is one important partition missing .. bootbak. We don't have it. That would require the phone to be repartitioned, and I just don't see LG risking that.
It is hard enough to repartition a UFS NAND via a firehose, it would be insane to try it via an OTA update.
-- Brian
Thanks Brian. Guessing these treble check apps should have a big warning plastered on them for the less savvy in the android intricacies such as myself. Glad I posted before going ham on trying to install Treble roms
Actually we have xbl2 and xbl2bak that could be repurposed. They aren't actually used as part of the boot process (they are identical copies of xbl and xblbak).
However, that still leaves system. In order to have a systembak, they would have to shrink userdata which is currently 52.2G, so plenty of room, but that is VERY risky.
Again, though, this is very doable. Heck, even if they don't do it, the AOSP builds for the V20 could support it with the tweaks stated above.
-- Brian
runningnak3d said:
Actually we have xbl2 and xbl2bak that could be repurposed. They aren't actually used as part of the boot process (they are identical copies of xbl and xblbak).
However, that still leaves system. In order to have a systembak, they would have to shrink userdata which is currently 52.2G, so plenty of room, but that is VERY risky.
Again, though, this is very doable. Heck, even if they don't do it, the AOSP builds for the V20 could support it with the tweaks stated above.
-- Brian
Click to expand...
Click to collapse
So, does the V30 have all these partitions set up? It's my understanding that the V30 is definitely going to be treble supported so I'm curious if it already has these partitions in place or needs modifying (in which case I imagine some crafty bastard will be able to replicate the process).
Or along those lines, several of the supported current phones I don't believe shipped with Oreo so they had to undergo the reformatting process, I wonder if there's anything to glean from them. I'll have to see if I can wrap my head around this whole deal.
Also, is this what we are lacking? https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Wow, I should really drink at least 3 cups of coffee before posting.
What I was referring to was A/B system updates which I swore had a code name, but damn if I can find it now.
Anyway, yes, even Project Treble will still require repartitioning since we don't have a vendor partition (vendor is on system). Much easier to implement than A/B system updates, but I still don't think LG will do it.
We will just have to wait and see...
EDIT: good read on A/B system updates: https://source.android.com/devices/tech/ota/ab/ab_implement
-- Brian
LG may not add /vendor partition, but if you put the pieces together from some of the posts around the dev section theres work being done to add one in Lineage, though it hasnt been done yet.
runningnak3d said:
Anyway, yes, even Project Treble will still require repartitioning since we don't have a vendor partition (vendor is on system).
Click to expand...
Click to collapse
Just FWIW, Treble doesn't necessarily require repartitioning.
PhantomGamers said:
Just FWIW, Treble doesn't necessarily require repartitioning.
Click to expand...
Click to collapse
i've been following project treble for sometimes and there are lot of misunderstanding
1. having custom oreo roms doesnt mean you had treble support. it is true most treble phone coming with oreo by default
2. even if your phone has official oreo rom doesnt mean it support treble project ( like samsung S8 or note 8)
3. there are some devices with unnoficial treble support like oneplus devices but it still in development and as brian said we need repartition and needs lot of work. and your link above still on experiment.
i didnt say its impossible, but its far away for our devices not to mention we still need to dealing with ARB and lafs. just hope more devs joining on LG development and not rush them ( i saw lot of people doing that on brian's thread) . remember they did it for free while risking their devices on the process.
Loopback mounting is by far the safest method. You mess that up, and you phone just doesn't load the OS. You try and shrink a partition, and you mess up, and you could be toast. It isn't just shrinking, you also have to add a new entry to the GPT .. that is dangerous.
Also, if you do succeed, you will never be able to flash a stock ROM unless you put things back. For one thing stock system would no longer fit
-- Brian
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
Has someone tried this? Sorta feels like he just took that article and just keeps adding phone models to it without trying it.
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
stcr1 said:
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
Click to expand...
Click to collapse
you can't just grab random drivers (that's what these HALs are) and hope they fit your device. x86cpu got close to a working treble implementation, but LG's camera drivers wern't compatible and has since put off that project and is working more on lineage 16 (pie). IF LG ever does release a stock version of pie, perhaps a newer version of the camera driver might be compatible, but perhaps not.
Phoenix591 said:
you can't just grab random drivers (that's what these HALs are) and hope they fit your device. x86cpu got close to a working treble implementation, but LG's camera drivers wern't compatible and has since put off that project and is working more on lineage 16 (pie). IF LG ever does release a stock version of pie, perhaps a newer version of the camera driver might be compatible, but perhaps not.
Click to expand...
Click to collapse
OK. Got it. So it seems that LG is going to give the V20 a Pie update. There are announcements to that affect. Assuming LG follows through, the Pie update may or may not be Treble compatible. With Oreo, device OEMs were required (??) to be Treble compatible on new Oreo devices, but could provide non-Treble Oreo updates to existing devices. That's what I gathered. So with Pie, what you are saying is that it will be the same: OEMs are not necessarily going to package Treble support in Pie updates to existing devices. But if LG does provide a Pie update, AND if the update is Treble compatible, then things will be easy-peasy for ROM developers to port their wares to it because drivers -- like the troublesome camera driver -- will be abstracted and basically have the same abstraction across all Android devices. Is that right?
stcr1 said:
OK. Got it. So it seems that LG is going to give the V20 a Pie update. There are announcements to that affect. Assuming LG follows through, the Pie update may or may not be Treble compatible. With Oreo, device OEMs were required (??) to be Treble compatible on new Oreo devices, but could provide non-Treble Oreo updates to existing devices. That's what I gathered. So with Pie, what you are saying is that it will be the same: OEMs are not necessarily going to package Treble support in Pie updates to existing devices. But if LG does provide a Pie update, AND if the update is Treble compatible, then things will be easy-peasy for ROM developers to port their wares to it because drivers -- like the troublesome camera driver -- will be abstracted and basically have the same abstraction across all Android devices. Is that right?
Click to expand...
Click to collapse
LG released oreo without treble support, LG releasing a pie update for the V20 is doubtful at best and if they do it more than likely it won't have treble support either
Sent from my LG-H910 using XDA Labs
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
warwagon19792 said:
Has someone tried this? Sorta feels like he just took that article and just keeps adding phone models to it without trying it.
Click to expand...
Click to collapse
stcr1 said:
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
Click to expand...
Click to collapse
I did know of someone who tried this. And it seemed to work but it never passed from the booting animation screen. He tried to go back and the phone was rendered useless. (and he was a developer). SOOOOO no.... I don't recommend attempting this.
I got a new OP5 (had a OP3). I unlocked the bootloader, installed TWRP, and was looking to root and load LOS 15.1.
I did that, sort of, but then got spooked because every zip I flashed, I got this error:
failed to mount partition '/vendor' (invalid argument)
I flashed back to stock and all seemed well, though I also got stock recovery. When I installed TWRP again and then a custom kernel, I got the same error. Then I couldn't boot with the custom kernel and now I'm headed back to stock.
When I go in to Mount in TWRP, it won't let me select vendor to be mounted.
What's causing that and how do I fix it?
TWRP is just complaining about the missing 'vendor' partition, that only exists in Project Treble ROMs. Therefore, there's nothing to fix. Ignore the error.
https://forum.xda-developers.com/showpost.php?p=76621704&postcount=285
That one has been modified to remove the warning.
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Elleby said:
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Click to expand...
Click to collapse
That's true, but till then, this lone programmer (me ) will patch any updated TWRP that is released so that the the error isn't displayed if you aren't on a treble-compatible ROM.
Thanks all. That makes sense, and also explains why I didn't see it previously with TWRP for OP3.
Elleby said:
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Click to expand...
Click to collapse
Source of this, please?
Astur_Torque said:
Source of this, please?
Click to expand...
Click to collapse
Check out this article, point 3 under "Will my device benefit from Project Treble".
Official statement on Oneplus forum. That part in particular:
Over 135,000 of our users signed up to review the OnePlus 6 early via The Lab. With the OnePlus 6 device in their hands, they'll be among the first in our community to be able to download the Android P Build. (OnePlus 5/5T friends, we'll have something nice lined up for you later this year.)
Click to expand...
Click to collapse
For me that means that they will release Android P on Oneplus5/5T after the initial release for Oneplus 6.
And Project Treble mandatory, link on discussion on reddit. That part in particular:
Devices launching with Android O will come Treble-enabled out of the box.
Click to expand...
Click to collapse
shadowstep said:
Check out this article, point 3 under "Will my device benefit from Project Treble".
Click to expand...
Click to collapse
But there does not mention anything about that is compulsory Treble on Android P (on preoreo phones), just it says its compulsory on Oreo recent-released devices
Astur_Torque said:
But there does not mention anything about that is compulsory Treble on Android P (on preoreo phones), just it says its compulsory on Oreo recent-released devices
Click to expand...
Click to collapse
It's true for Android Oreo and above. Treble is the reason why there are Android P Betas available for non-Google devices. Also, here's an excerpt from this article: "Going forward, updates to phones will become far more common, as all devices that launch with Android Oreo or newer are required to implement Treble."
shadowstep said:
It's true for Android Oreo and above. Treble is the reason why there are Android P Betas available for non-Google devices. Also, here's an excerpt from this article: "Going forward, updates to phones will become far more common, as all devices that launch with Android Oreo or newer are required to implement Treble."
Click to expand...
Click to collapse
Yes I agree with you with that... However... "All devices launched with oreo"... One plus 5 is not one of those... Just 6 and incoming..
Enviado desde mi Oneplus 5 mediante Tapatalk
Astur_Torque said:
Yes I agree with you with that... However... "All devices launched with oreo"... One plus 5 is not one of those... Just 6 and incoming..
Click to expand...
Click to collapse
You're spot on. I never said that OP5/5T will definitely get Treble. Also, I'm not the OP, if you haven't realized that yet. OnePlus got away with having to mandatorily provide Treble to the OP5/5T by launching the device with Nougat (but making it upgradeable to Oreo) -- meaning that these devices don't come under the category of devices that launch with Android Oreo, thereby putting OnePlus under no compulsion to provide Treble to these devices. However, there are rumours that have been floating around that even though there is no compulsion, OnePlus is considering providing Treble to these devices.
Hey guys i was reading something about project treble and it seems we are compatible because we are running android 8.0, what do you think about it?!
I would like to be part of it, i love stock android and it is a great project
Just running Oreo doesn't qualify a device as Treble compatible. Nonetheless, @x86cpu has got the phone repartitioned and a GSI (generic system image) booted with issues. Specifically, it seems the camera will likely never work and he didn't want to pursue Treble for the time being. See this post and the ones before it for where the V20 stands for now.
Sad fact but i hope we get something at least on the next year, thanks bro!