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).
Related
We all know that Mi A1 is having A/B partition unlike most of the devices we see in the world of Android.
It is good to have that, we can experience seamless updates but, Is this reason making difficult for the developers to build custom roms for this device?
Do we get builds from Lineage os in future?
Do we get custom roms like aosp extended, aicp, mokee os & many others?
Do all devices get aosp extended, aicp ,mokee within one month of launch?
Yaar have some patience atleast.
Let sources be out...
Vasu Netha said:
We all know that Mi A1 is having A/B partition unlike most of the devices we see in the world of Android.
It is good to have that, we can experience seamless updates but, Is this reason making difficult for the developers to build custom roms for this device?
Do we get builds from Lineage os in future?
Do we get custom roms like aosp extended, aicp, mokee os & many others?
Click to expand...
Click to collapse
Hey, shouldn't be hard at all, the chipset is very common which means making the right commits shouldn't be too difficult, of course it all depends on xiaomi releasing the kernel source code. Once the device tree is setup,all roms are very easy to port.
I been quite a while why there are no roms for mi a1 as google will update mi a1 to 8.0 when im old and about to die "why is there no rom development wilk this device ever have any roms".
Because there's no kernel sauce! Source!
Don't quite understand .. isn't the complete firmware shared already on xiaomi site .. ?
KhaledAbdo said:
Don't quite understand .. isn't the complete firmware shared already on xiaomi site .. ?
Click to expand...
Click to collapse
Compiled firmware, not the source code, that's completely different things.
Kernel source still not shared by mi.
https://www.xda-developers.com/xiaomi-not-released-kernel-sources-mi-a1/
I read it here. But why they dare to put "Android One" and advertise as it is? They want to test our patience and people to sue them for being "misleading"?
myself379 said:
https://www.xda-developers.com/xiaomi-not-released-kernel-sources-mi-a1/
I read it here. But why they dare to put "Android One" and advertise as it is? They want to test our patience and people to sue them for being "misleading"?
Click to expand...
Click to collapse
nobody stopped them withholding miui sources and kernel sources for other device trees. They have always stood on giants shoulders.
Wait for Google's project trebel to land with Oreo so that we can have lot more custom ROMs.
It's not guaranteed that we get project Treble implemented:
https://www.xda-developers.com/oneplus-project-treble-android-oreo/
Phones and tablets that ship with Android 8.0 Oreo are required to implement Project Treble, but devices running older versions of Android — including the OnePlus 5T, which runs Android 7.1.1 Nougat — are not.
Click to expand...
Click to collapse
Anyone can help me to confirm that op5 oreo beta is based on android 8.0?
Because chinese websites say that op5 oreo beta is based on android 7.1
You can use adb to check:
adb shell strings /dev/block/bootdevice/by-name/modem | sed -n 's/.*"apps": "\([^"]*\)".*/\1/p'//
You can google search 一加手机5 8.0 7.1 底层 if you understand chinese.
i.am.newbie said:
Anyone can help me to confirm that op5 oreo beta is based on android 8.0?
Because chinese websites say that op5 oreo beta is based on android 7.1
You can use adb to check:
adb shell strings /dev/block/bootdevice/by-name/modem | sed -n 's/.*"apps": "\([^"]*\)".*/\1/p'//
Click to expand...
Click to collapse
oxygen os 5.0 is Android Oreo (Android 8.0)
Why would Oreo be based on Nougat?
i.am.newbie said:
Anyone can help me to confirm that op5 oreo beta is based on android 8.0?
Because chinese websites say that op5 oreo beta is based on android 7.1
You can use adb to check:
adb shell strings /dev/block/bootdevice/by-name/modem | sed -n 's/.*"apps": "\([^"]*\)".*/\1/p'//
Click to expand...
Click to collapse
Any dev can help me to confirm it?
The settings menu is based on 7.1 for some reason.
I don't understand why OnePlus didn't move completely to the 8.0 source
Well, these were my initial thoughts - why the f, OnePlus 5 wants to retain Nougat look & feel. Perhaps, they don't want end users to get confused with new UI and still have new platform.
But I confirm they are using Oreo base - you can check presence of new "manifest.xml" under vendor partition - which is new way forward starting with oreo to define HALs. Also, the kernel source tag 6.x is for Oreo.. everything suggests its based on Oreo but OP team wants to retain Nougat feel (quite stupid in my opinion.)
Also, devices don't start fresh when new android version drops. Instead dev team will "bring up" existing device tree to make it compatible with new blobs and new source API/requirements. Perhaps, some left over from old base we are seeing in the screenshot shared.
Cheers.
neobuddy89 said:
Well, these were my initial thoughts - why the f, OnePlus 5 wants to retain Nougat look & feel. Perhaps, they don't want end users to get confused with new UI and still have new platform.
But I confirm they are using Oreo base - you can check presence of new "manifest.xml" under vendor partition - which is new way forward starting with oreo to define HALs. Also, the kernel source tag 6.x is for Oreo.. everything suggests its based on Oreo but OP team wants to retain Nougat feel (quite stupid in my opinion.)
Cheers.
Click to expand...
Click to collapse
The OOS Betas do have the new Oreo UI. It does not have a Nougat look or feel. But it's possible some other mod that OOS uses requires that code. Maybe they need it to keep their spyware working properly.
jhs39 said:
The OOS Betas do have the new Oreo UI. It does not have a Nougat look or feel. But it's possible some other mod that OOS uses requires that code. Maybe they need it to keep their spyware working properly.
Click to expand...
Click to collapse
Maybe. But in this case, if they did so, then I would say bye to OOS and hello to Paranoid.
jhs39 said:
The OOS Betas do have the new Oreo UI. It does not have a Nougat look or feel. But it's possible some other mod that OOS uses requires that code. Maybe they need it to keep their spyware working properly.
Click to expand...
Click to collapse
Not really Oreo UI ...some improvements exists thou
RogerF81 said:
Maybe. But in this case, if they did so, then I would say bye to OOS and hello to Paranoid.
Click to expand...
Click to collapse
eh i'm also waiting for pa oreo
luxandroid said:
Not really Oreo UI ...some improvements exists thou
Click to expand...
Click to collapse
I ran Oreo on two different Google devices--the Nexus 6P and Pixel XL. OOS is definitely using the Oreo UI. I think One Plus is taking shortcuts to update to Oreo which is pretty typical for the company. Android apps are generally made to be compatible with older Android builds so the fact that OnePlus is using some Nougat HALs and APIs in their version of Oreo isn't something most users would ever even notice. But this isn't new for One Plus. The reason the ported Pixel Camera app works perfectly on many phones but not the OP5 is that One Plus used an outdated camera API in their version of Nougat.
https://www.reddit.com/r/oneplus/comments/7iydl8/oneplus_allegedly_kept_711_firmware_in_its_oreo/
Will Project Treble make porting rom easy, like a one-day job?
Could we port roms between different hardware platforms on devices have Treble support?
For example, can we flash the system.img of Honor 9 into an Essential Phone PH-1 and boot EMUI 8.0 on it, or boot Essential's system image on Honor devices?That's not possible before Treble.
The short answer: no. System images from Huawei/Honor phones reference a ton of vendor-specific stuff that isn't available on other phones.
MishaalRahman said:
The short answer: no. System images from Huawei/Honor phones reference a ton of vendor-specific stuff that isn't available on other phones.
Click to expand...
Click to collapse
In fact the EMUI camera port is partly working on a xiaomi device,even rhe camera is related to a vendor.xxx.so file that is vendor-specific .The phone even don*t support treble.So I wonder if the vendor stuffs could also be ported.
Hi.
I will turn arround the question.
Will we be able to use the same ROM file (it can be LineageOS) on 2 different devices ?
The hardware specific applications can be installed like now we do it with weather service or root service for LOS or open gapps .
Tomek0000 said:
Will we be able to use the same ROM file (it can be LineageOS) on 2 different devices ?
Click to expand...
Click to collapse
Yes, of course, it already works, check other threads
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!