Related
I've done some easy searching and found what might be the actual cause of the Xperia Z3 not being announced as getting Android N with other devices from the Sony line.
Even though we have Android 7.0 previews available and it works fine with a few software bugs that need to be ironed out, the Xperia Z3 will not be getting official Android N.
And heres why:
The problem lies in Google and their Android N requirements.
You might be asking, what do you mean by requirements the device ran the previews just fine!?
Well, Google has introduced new encryption methods in Android N which have certain hardware requirements.
The Snapdragon 800/801 don't have support for some of these newer encryption methods.
Another question you might be asking is, well we don't need these encryption methods, but Google says otherwise.
Their policy is that their encryption methods must be fully running by the time the device setup is done.
So the actual reason for the Z3 not getting Android N is both technical and legal.
In the end, its actually not Sony's fault, Sony is just following the rules which Google put.
Although I don't see any problems for Qualcomm releasing the drivers needed for further development.
We will probably see unofficial Android N on our devices, but at the moment it seems like a far stretch due to Qualcomm not wanting to release drivers.
Sources:
Android Authority
It's exactly full-disk encryption and GG haves Compatibility Definition Document (CDD) for all devices need to run Android N. So easily, Snap 800/801 have feature full-disk encryption, but with this, they do pass Compatibility Test Suite (CTS) but don't meet the CDD because read/write speed. Snap 805 is newer and have module for this feature, so can make it faster.
But, if Sony open our kernel, Snap public your driver, custom rook does not need full-disk encryption at all.
That's all I found about this.
This is just one of many reasons why we can't get N. Opengl 3.1 or Vulkan is also required for certification which only SD 805 and later have. Basically all devices older than SD 805 are sol for future updates. Now Sony could release stockbased build in a zip format through dev program without gapps which wouldn't cause issues with Google
Lets try and keep it in one thread
http://forum.xda-developers.com/z3/general/xperia-z3-wont-android-n-t3446158
Thread closed.
The Sony Xperia Z2 and Z3 devices are both amongs one of Sony's best smartphones ever that they has released. By signing this petition, we will all let Sony take action and update our precious Z2 and even Z3 devices to Android Nougat!
But what about Vulkan API support???
Anything is possible, and we will prove to Google and Sony that having the minimum requirements for software to work correctly, is plain garbage, and that Vulkan API can be left out for them, because it's not like the Vulkan API is a necessity for Nougat in order to run correctly.
ANYMORE QUESTIONS WILL BE BROUGHT UP FROM THE COMMENTS ONTO THE OP AND ANSWERED HERE.
SIGN THIS PETITION NOW!: http://bit.ly/2eEwqN5
Thanks!
I Just Want A Stable 7.0 Build For Z2
Man i think this is impossible. Qualcomm completely left the development of the SD800/801 and if Sony update our devices without permission of Google, they will be in a big trouble. To me, this is impossible.
You are totally right Little Snevil. I also think that official update it's impossible because Qualcomm processor.
Enviado do meu D6503 através de Tapatalk
Well, MAYBE it is possibile to get android 7.0 on snap 801. Just look http://www.techtimes.com/articles/1...coming-soon-geekbench-benchmark-hints-yes.htm
This is sad, but change.org never has been listed by Google or Sony, like happen with z1 and marshmallow, Xperia L and kit kat, Xperia sp and kit kat. The true is Google and Sony never listen to users, only look the sales, and for those is better for him sale the new and forget the old
what i can say in that?
@Brandon Nel
Having a petition is a good idea, and I am not against it.
But there are two questions I would like to raise before proceeding to sign the petition:
1. Our Z3 and Z2 has been released for 24 and 30 months already, this already exceed the normal aftermarket support for Android devices (usually it goes among 18 to 24 months). Although you might say there has been rule breakers recently (for instance the Xperia Z that has almost 36 months of follow up upgrade), but however there are also some far below standard devices (eg Xperia C, which has no android upgrade since release). After all, Qualcomm, Sony and any other companies still have to make money for R&D and make a living, right? So I am thinking that shouldnt we live with what we are having now (AOSP 7.0)?
2. Shouldnt Qualcomm the company you should challenge against? Vulkan and OpenGS are featured in the chipset which is manufactured by QC, not Sony!
We should petition Qualcomm & Google instead of Sony.. Sony tried their best to bring Nougat through their Beta program for Z3.
But due to the lack of chipset updates from Qualcomm and the Vulkan API requirement set by Google, so many devices have been abandoned from the update even though they are fully capable to run N. This includes Z2 & Z3.
So in this case, either Qualcomm has to release update to our chipset or we have to force Google to remove mandatory Vulkan API requirement.
i need to pls make stable nougat..........................
artsfreaky said:
i need to pls make stable nougat..........................
Click to expand...
Click to collapse
Then sign the petition and prey
Sent from my Sony D6503 using XDA Labs
Paste a link to the petition on Twitter Sony and Sony News
//This is purely an opinion, might be treated as sarcasm, but it is an opinion
1. Nougat is bad for me, it is uglier and security is even worse because of getting more strict.
2. It is nearly impossible to push this through, because now you need to actually HAVE that VulkanAPI support in order to get a cert from google to use gapps(Noone will use Vulkan straight away, because of fragmentation, but well, three billion devices run java, now three billion devices will have to run Vulkan as well and if not, they'll die)
Any effort is worthwhile haha. This should be shared in the Z3 forums!
Well, Sony published AOSP for Xperias. This might mean something, maybe they will be able to somehow get that cert.
Did you see this :
Sony is not to blame for leaving the Xperia Z3 off the Android Nougat list
http://www.xperiablog.net/2016/08/3...ng-the-xperia-z3-off-the-android-nougat-list/
All devices with SD 800/801 will not updated to Android N 7.0 , Because of Qulacomm .
Alaa | Google Android said:
Did you see this :
Sony is not to blame for leaving the Xperia Z3 off the Android Nougat list
http://www.xperiablog.net/2016/08/3...ng-the-xperia-z3-off-the-android-nougat-list/
All devices with SD 800/801 will not updated to Android N 7.0 , Because of Qulacomm .
Click to expand...
Click to collapse
Not because of Qualcomm, but because of Google. They made Vulkan obligatory for getting certs. No one is going to use it from day one of Nougat anyway, because fragmentation, they want to push APIs, but Nougat isn't like 99% of Android right now. Although it might be handy when it reaches higher shares due to Vulkan's performance.
Google has made it mandatory for devices launched with Android Oreo to have Linux Kernel 4.4 and Project Treble but
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
From AOSP/Google (I can't yet put links to source as I don't have 10 posts yet)
Which includes our OnePlus 3T. As OnePlus has already said Android Oreo will be the last major update for our device (officially) we might not get Project Treble (like Nexus 5X and 6P) and Linux kernel 4.4 (a major update from our current 3.18) making it very difficult for the developer community to port future updates as Android P and above might only have Treble base unlike Android Oreo.:crying:
That would be a another bummer after there limited support announcement for 3t. For know I keep my fingers crossed for a better message on this front.
Still if images are released for AOSP you still will get development for our phone though. ?
Goku80 said:
Still if images are released for AOSP you still will get development for our phone though. ?
Click to expand...
Click to collapse
Exactly. Honestly I don't see why Project Treble matters to the average ROM user. I just want my phone to work and perform well and have a decent battery life. Besides that I don't really care. Currently I have a Nexus 6 and just replaced the battery in it but I'm perusing the forums for various devices (this was one of them) that I may be interested in. I want to see how the development community is for each one before I decide. Reason I may be considering this over the OP5 is I have heard bad things about the screen and jelly scrolling.
rjmxtech said:
Honestly I don't see why Project Treble matters to the average ROM user.
Click to expand...
Click to collapse
You don't see why?
Let me help you out:
Ars Technica said:
Custom ROMs shouldn't need to be painstakingly hand-crafted for individual devices anymore—a single build should cover multiple Treble devices from multiple manufacturers. Imagine the next time a major new version of Android is released. On Day One of the AOSP code drop, a single build (or a small handful of builds) could cover every Treble device with an unlocked bootloader, with a "download Android 9.0 here" link on XDA or some other technical website.
Click to expand...
Click to collapse
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
I totally agree this !
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Exactly! Development and porting of Custom ROMs will become easier than ever before and porting of future versions of Android will also become way lot easier (if possible at all as future versions of Android might become completely dependent on Project Treble unlike Android Oreo which is compatible with both)! And porting Project Treble is very very difficult if not impossible (unless you are the Silicon Manufacturer) !
So lets together spread the information about the importance of Project Treble and pressure OnePlus to provide Project Treble with #WeWantTreble
We shall Never Settle!
#WeWantTreble
Sent from my ONEPLUS A3003 using XDA Labs
Lets spam Carl Pei twitter with questions regarding this..
(Well not really spam, that would be rude, more like a lot of people asking him same question in shorts period of time)
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
i have red somewhere that pixel devices support treble. Same Soc, should have supported. idk.
From my experience as a Junior Android developer and reading the papers about the project treble, i could say that if there is a little group op3t developers who want this, this can be possible.
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Interesting. But I assume there would still be issues even if they tried to make a universal solution.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
DelicatePanda said:
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
Click to expand...
Click to collapse
Friggin' derp. How did I forget about the Pixel?
That being said, we'd still need to see how its implemented on the Pixel...As far as I know Treble also relies in a specific type of device partitioning which may be problematic for existing device adaptations. The Pixel phones already used the /vendor partition how it's supposed to be used so adapting Treble is almost a non-issue. I don't think our phone uses the same partition layout.
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
DelicatePanda said:
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
Click to expand...
Click to collapse
That sucks .. even for OnePlus 5?
why the heck Carl is not replying officially on it, anywhere???
Please suggest a way to make our device get the Project Treble officially.
More details on Google Project Treble,
Thanks.
This can only be accomplished by the manufacturer of the phone (Oneplus) in corporation with the SoC manufacturer (Qualcomm). But we can always say pleeease with a big nice smile in the Oneplus forum and hope for the best. ?
pitrus- said:
This can only be accomplished by the manufacturer of the phone (Oneplus) in corporation with the SoC manufacturer (Qualcomm). But we can always say pleeease with a big nice smile in the Oneplus forum and hope for the best.
Click to expand...
Click to collapse
As per the official OnePlus forums from I visited, I have read them saying "Treble is interesting, we will keep close an eye on it.."
Which is like killing me all the time...
Could someone from XDA OnePlus team reach out to OnePlus official and represent our request???
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
Dint quiet get you there mate...
you mean Treble is not a good move?
orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
Incoherent, confused, and totally off the point, what after next year there is no Android update, would that kill the phone, I still have wildfire s, it's on ginger bread, it runs youtube, Facebook and what's app, this phone will be usable till it is not broken
Sent from my ONEPLUS A3010 using Tapatalk
dante_67 said:
Incoherent, confused, and totally off the point, what after next year there is no Android update, would that kill the phone, I still have wildfire s, it's on ginger bread, it runs youtube, Facebook and what's app, this phone will be usable till it is not broken
Sent from my ONEPLUS A3010 using Tapatalk
Click to expand...
Click to collapse
I like turtles.
Is it possible for devs to port the kernel to 4.4+ once OP release sources for Oreo?
Well, given that OEM support for our device will end by mid next year, Project Treble implementation is not really worthwhile for our devices. It won't be useful to OnePlus for long (for the 3/T), and also it'll be quite expensive to be worked on.
But if OnePlus decides to pull an OPO, and grant us our wishes, we'd all be happy.
It has almost nothing to do with Oneplus, if Qualcomm update the reference msm8996 kernel to linux 4.4 then its trivial to port oneplus modifications over.
Qualcomm has practically zero motivation to do this, infact it works against their interests.
orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
x86 or ARM? Jesus, that's some pretty old CPU architecture right there. Care to elaborate as to why you want it to go further?
thes3usa said:
x86 or ARM? Jesus, that's some pretty old CPU architecture right there. Care to elaborate as to why you want it to go further?
Click to expand...
Click to collapse
I like turtles.
orange808 said:
I like turtles.
Click to expand...
Click to collapse
Makes sense. Thanks for your informative explanation xD
OnePlus 3, 3T, 5, and 5T are all missing out on Project Treble, but will be updated to Android 8.1.
I'd rather have Treble.
Sent from my ONEPLUS A3000 using Tapatalk
HampTheToker said:
OnePlus 3, 3T, 5, and 5T are all missing out on Project Treble, but will be updated to Android 8.1.
I'd rather have Treble.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
And if OnePlus had release Project Treble but not Android 8.1, you would have also complained.
Stop complain about everything you don't have, and enjoy what you have: should I remind you that Android 8.0 should have been the last update for the OnePlus 3(T)? Plus, Project Treble targets all devices launched with Android 8.x, which is not the case for actual OnePlus phones.
Not only "OnePlus" doesn't give project treble,
Stop complaint about "Project Treble"
there is a petition going to support Project Treble for OnePlus devices
feel free to sign the petition and make a difference
We (the community) would like to ask Oneplus to support Project Treble in OOS
casual_kikoo said:
And if OnePlus had release Project Treble but not Android 8.1, you would have also complained.
Stop complain about everything you don't have, and enjoy what you have: should I remind you that Android 8.0 should have been the last update for the OnePlus 3(T)? Plus, Project Treble targets all devices launched with Android 8.x, which is not the case for actual OnePlus phones.
Click to expand...
Click to collapse
Project Treble is compulsory for devices launching with Oreo, but can be enabled when a device is updated (see OG Pixel/XL and Essential Phone), so OnePlus can do it if they want to.
JoinTheRealms said:
It has almost nothing to do with Oneplus, if Qualcomm update the reference msm8996 kernel to linux 4.4 then its trivial to port oneplus modifications over.
Qualcomm has practically zero motivation to do this, infact it works against their interests.
Click to expand...
Click to collapse
Correct me if I'm wrong, just guessing here, but isn't the Google Pixel 1 getting treble? It has the same SOC, so getting the required kernel references shouldn't be a problem right?
EDIT: This is ofcourse only applicable to the 3T, so they'd have to split the OTA's from the OP3. Highly doubt that they'd do that though.
To all those who want to know more about Project Treble please use this thread to discuss about it.
What is Project Treble?
Ans. Treble is the most significant low-level change to the Android platform to date. To simplify heavily, it separates the vendor implementation from the Android framework in an effort to avoid lengthy waits for updates. . Let’s break things down a bit more:
The full update process to bring a new Android version to devices is a long and complex topic.
The “vendor” usually refers to silicon-manufacturers such as Qualcomm, but can also refer to the maker of any other proprietary hardware found in a device. The “device maker” or “OEM” usually needs to wait for the vendor to update their code so the proprietary hardware works with the Android OS framework in a newer version of Android.
However, what is happening with Project Treble is that Google is requiring that any vendor-specific code be separated from the Android OS framework and instead live in its own vendor implementation. Usually this means that there is now a separate /vendor partition on Treble-enabled smartphones that contains a bunch of HALs (Hardware Abstraction Layers).
Furthermore, vendors must implement code that lets the Android OS framework communicate with HALs in a standardized way. This is done via HIDL (HAL Interface Definition Language). With this in place, an OEM can work on an Android update without having to wait on vendors to update their HALs. Theoretically, this should speed up the entire Android update process as vendors can update their code at any time through the Play Store.
For indepth information check out this pagehttps://www.androidauthority.com/project-treble-818225/
Devices with Treble support:
- Essential PH-1
- Google Pixel
- Google Pixel XL
- HTC U11 Plus
- Huawei Honor 8 Pro
- Huawei Mate 9
- Huawei Mate 10 Pro
- Sony Xperia XZ1
- Sony Xperia XZ1 Compact
- Asus Zenfone 4 (ZE554KL)
- Honor V10
- Huawei P10/ P10 Plus
Devices which will ship with Android 8.0 Oreo will be Treble compatible by default.
Older devices will become treble compatible if the OEM creates a vendor partition via OTA update, like the Honor 8 Pro.
Custom Roms:
As of now @phhusson is working hard to make his AOSP rom boot as a fully functional rom on all the Treble supported devices, go check out the rom thread here https://forum.xda-developers.com/pr...evelopment/experimental-phh-treble-t3709659"]
Check Treble Compability
Open a terminal app on your device and simply type the following command:
getprop ro.treble.enabled
Click to expand...
Click to collapse
If it returns a boolean value true, your device supports Treble and if false it doesn’t.
[NOTE: New devices with Treble support are launching so its not possible for me to update the supported device list, so they'll not make their name on my list, but you can surely ask about your device on the discussion thread]
My understanding of Treble is, from the *big picture* anyway, that the responsibility for hardware access shifts from Google to the individual device mfgs.
The hope for us is that new versions of Android can be distributed much more rapidly, because testing of new hardware (or changes to existing hdw) won't have to wait for the new OS to be done, and that the interface to the hdw will be separate from the OS.
Another hope would be that a devices 'life span' would increase? (or at least stay current longer).
AsItLies said:
My understanding of Treble is, from the *big picture* anyway, that the responsibility for hardware access shifts from Google to the individual device mfgs.
The hope for us is that new versions of Android can be distributed much more rapidly, because testing of new hardware (or changes to existing hdw) won't have to wait for the new OS to be done, and that the interface to the hdw will be separate from the OS.
Another hope would be that a devices 'life span' would increase? (or at least stay current longer).
Click to expand...
Click to collapse
Treble means separating the vendor source from the software source, the treble devices will have a separate vendor partition, in which the vendor source will be. Now the manufacturers will only require to make the Software bug free so that the user dosent face any problems in day to day usage. From @phhussons AOSP treble rom we can get a clear picture that by separating the vendor source, the Treble based AOSP roms will run on any Treble compatible device regardless of the SOC/hardware configuration.
venom928 said:
Treble means separating the vendor source from the software source, the treble devices will have a separate vendor partition, in which the vendor source will be. <snip>
Click to expand...
Click to collapse
Ah yes that makes sense, it's not only the hardware source (vendor specific), it's also the vendors software (their mods and bloatware) that will be in the separate partition.
It really does sound as though this should speed up the time it takes for users to get updates of all kinds. It also seems pretty certain, non-Treble enabled devices will fall by the wayside. Doesn't seem there's any way around that?
AsItLies said:
Ah yes that makes sense, it's not only the hardware source (vendor specific), it's also the vendors software (their mods and bloatware) that will be in the separate partition.
It really does sound as though this should speed up the time it takes for users to get updates of all kinds. It also seems pretty certain, non-Treble enabled devices will fall by the wayside. Doesn't seem there's any way around that?
Click to expand...
Click to collapse
For non-treble devices the only way is that the OEMs must release an OTA update which will create a separate Vendor partition, but OEMs won't do(except some recent flagships) that bcz they want sales of newer devices with Treble support. As far as time is concerned, suppose it takes 2-3months for an OEM to build a fully bug free update, but it will require 3-4weeks for the OEM to build that same update
venom928 said:
For non-treble devices the only way is that the OEMs must release an OTA update which will create a separate Vendor partition
Click to expand...
Click to collapse
Yes, it seems the consensus is that mfg's won't risk bricking the phones by doing that kind of an OTA update? We'll see fairly soon what they'll do with the older devices.
It's good that google is calling the shots with this and is insisting new Oreo devices have it. It's bad though that devices just a few months old that cost mucho bucks may go without it.
AsItLies said:
Yes, it seems the consensus is that mfg's won't risk bricking the phones by doing that kind of an OTA update? We'll see fairly soon what they'll do with the older devices.
It's good that google is calling the shots with this and is insisting new Oreo devices have it. It's bad though that devices just a few months old that cost mucho bucks may go without it.
Click to expand...
Click to collapse
The honor 8 pro got Treble via OTA because it was one of the best selling device, but some OEMs will prefer not to do that so that customers will shift to newer devices. Like OnePlus could have easily added Treble to atleast 5/5T but they thought of not doing it, just depends upon the OEM
venom928 said:
The honor 8 pro got Treble via OTA because it was one of the best selling device
Click to expand...
Click to collapse
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
AsItLies said:
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
Click to expand...
Click to collapse
yep surely
Mate 9 as well
AsItLies said:
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
Click to expand...
Click to collapse
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
revjamescarver said:
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
Click to expand...
Click to collapse
Mate 9 is in the list bro, check OP
revjamescarver said:
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
Click to expand...
Click to collapse
Thanks Neighbor. Huawei is rapidly moving to the top of my list of phone mfg to buy. It doesn't look like the kirin processors have much los support, but with treble... well, it seems previous prerequisites are being turned upside down.
For sure, when one evaluates (buying) a phone, many factors are relevant. But for most (if not all) of us, how long the phone will stay up to date is probably at the top of that list.
Hope the other mfg's follow Huawei's lead here, else we'll have a lot of recently mfg phones with outdated sftwr soon.
AsItLies said:
Thanks Neighbor. Huawei is rapidly moving to the top of my list of phone mfg to buy. It doesn't look like the kirin processors have much los support, but with treble... well, it seems previous prerequisites are being turned upside down.
For sure, when one evaluates (buying) a phone, many factors are relevant. But for most (if not all) of us, how long the phone will stay up to date is probably at the top of that list.
Hope the other mfg's follow Huawei's lead here, else we'll have a lot of recently mfg phones with outdated sftwr soon.
Click to expand...
Click to collapse
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
venom928 said:
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
Click to expand...
Click to collapse
Very good point. So even with Treble, which SOC (the phone has) will still be relevant in some respects. I have a G6 and think a wide angle lens is da bomb, but could easily do without all the glass 'bling'.
Kirin SoC
venom928 said:
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
Click to expand...
Click to collapse
Nothing at all wrong with the Kirin SoC, performance is on par with the Qualcomm SoC, only real downfall is that Huawei doesn't sell the Kirin to other oems, otherwise it would be more widespread. The Kirin 970 with its built in NPU and and gigabit LTE modem is going to give the Qualcomm 835/845 a run for their money. Of course the port of the new Google camera app is not going to give you more than the basic functionality as it was written specifically for Google pixel devices (it doesn't give you all the features on older Google or snapdragon devices either), I installed the port on my mate 9 and it was acceptable for basic camera functions but no matter what you do you're never going to get a port of something written for another device to have the same features or performance as the stock app written for your device.
revjamescarver said:
Nothing at all wrong with the Kirin SoC, performance is on par with the Qualcomm SoC, only real downfall is that Huawei doesn't sell the Kirin to other oems, otherwise it would be more widespread. The Kirin 970 with its built in NPU and and gigabit LTE modem is going to give the Qualcomm 835/845 a run for their money. Of course the port of the new Google camera app is not going to give you more than the basic functionality as it was written specifically for Google pixel devices (it doesn't give you all the features on older Google or snapdragon devices either), I installed the port on my mate 9 and it was acceptable for basic camera functions but no matter what you do you're never going to get a port of something written for another device to have the same features or performance as the stock app written for your device.
Click to expand...
Click to collapse
I agree that the Kirin Processors are good, and the reason is Kirin is Huawei's home made processor so the pairing between Hardware and Software is perfectly optimisez for better performance and as far as Better Processing is concerned, after Apple Qualcomm holds the 2nd position no doubt, yeah in near future Kirin might surpass Qualcomm interms of performance no idea.
As far as the ported app is concerned I prefer stock android/custom roms over stock roms(MIUI/EMUI) and if someone ports the stock huawei camera for Los/RR running on Huawei devices itself, I'll surely go with a Kirin device but right now thats not available so after installing a custom rom I'll prefer Google camera app, if not the ported one, I'll go with the one available in Apkmirror, though this is my own preference as I'm addicted to using stock android and google apps suite, lets see how much development the Honor 7X gets, if it gets Treble support via OTA I'll go with it else the Mi A1 as of now is my 1st choice
I'm wondering, and the answer may be 'We don't know yet', but...
Many of us have used custom ROM's to avoid using an OEM's UI, bloatware, etc. Because Treble enabled phones will have a 'Vendor' partition (which will include these UI's etc), will that then mean the mfg's specific stuff can't really be (completely) removed the way an after market ROM does?
Of course, there's always ways of disabling mfg stuff, but Roms like Los just do it all in one fell swoop (much easier).
Do we know at this point how this will work with Treble?
Cheers and Happy New Year
AsItLies said:
I'm wondering, and the answer may be 'We don't know yet', but...
Many of us have used custom ROM's to avoid using an OEM's UI, bloatware, etc. Because Treble enabled phones will have a 'Vendor' partition (which will include these UI's etc), will that then mean the mfg's specific stuff can't really be (completely) removed the way an after market ROM does?
Of course, there's always ways of disabling mfg stuff, but Roms like Los just do it all in one fell swoop (much easier).
Do we know at this point how this will work with Treble?
Cheers and Happy New Year
Click to expand...
Click to collapse
The SOC source code will reside in the vendor partition, for example The Pixel XL has SD835 so the source code of the SOC will be there in itz Vendor partition. So if you are using a Treble enabled device such as the Huawei Mate 9 which has its own custom UI, if u flash a custom rom on it, the stock OS will get completely removed and the run ROM will run on it.
The Mgf's UI is a part of the system nd not of the vendor partition.
I am planning to buy Honor 7x, I found a thread on 7X forum which has Mount points and partition layout details for 7x. In the details, i can see below line, does this mean that phone supports Treble once updated to Oreo?
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
Orignal thread link
https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990
Thanks:good: in advance!!
indigo110 said:
I am planning to buy Honor 7x, I found a thread on 7X forum which has Mount points and partition layout details for 7x. In the details, i can see below line, does this mean that phone supports Treble once updated to Oreo?
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
Orignal thread link
https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990
Thanks:good: in advance!!
Click to expand...
Click to collapse
It is evident from past experiences that the Honor 7X might get Treble via OTA update as the case was with Honor 8 Pro. The Honor 7X's source code got released a few weeks ago and I got some info that the Open Kirin team will also support the 7X so I guess the Open Kirin team will also release a Treble supported rom