Database Develop

Why the released Oneplus phones won't get Project Treble support.

Yes, we are happy to share our rationale. Recently, we received requests from users and community members, some of which signed a Change.org petition to support Project Treble on the OnePlus 5 and OnePlus 5T. Project Treble is a really exciting technology, but it is not the right fit for us now. I assure you we’re still updating our devices and will continue to deliver high-quality, stable software updates. That being said, we always welcome feedback, and I want to further shed some light on why we are not implementing Project Treble on these devices.
Project Treble requires a storage partition, by which the Android framework and vendor image are separated. However, because partitions were not required of Android N and previous versions of Android, all of our current devices do not feature a partition. According to our tests, if we were to modify the partition layout via OTA there is a risk that devices will brick during the partitioning. We feel this poses too great a risk for our community of users, which is why we have decided not to implement Project Treble on current OnePlus devices.
While Project Treble can increase the rate of Android OS updates, it mainly accelerates the Android framework updates. We were one of the first manufacturers to release an update to Android O. Our software team is committed to delivering high-quality and stable major OS upgrades, and we will continue to look for ways to improve the quality and rate at which we deliver software updates in the future. That being said, we look forward to the future of Project Treble, and how it will evolve to better support devices ahead.
Source : https://forums.oneplus.net/threads/join-our-oneplus-5t-ama-now.686679/page-41#post-17271933
? Share your opinions! ?

It could be a option to provide the tools to make the needed partition once the device is old enough. Say for the OP3. With a big warning that usage is on your own risk. Just like some vendors do when unlocking the bootloader.
I think that would make Al lot of us happy.

GeminiRx said:
It could be a option to provide the tools to make the needed partition once the device is old enough. Say for the OP3. With a big warning that usage is on your own risk. Just like some vendors do when unlocking the bootloader.
I think that would make Al lot of us happy.
Click to expand...
Click to collapse
Too much risk of bricking

Will Moto X4 get project Treble support whenever it gets Android Oreo?

Update
Moto hasn't enabled treble in Indian Moto X4 (XT1900-2)
Many OEM like Nokia, OnePlus etc are disabling Project Treble on their devices in Oreo updating stating that Treble requires re-partitioning of internal storage which if done via OTA has a high probability of bricking the phone.
https://m.gsmarena.com/current_nokia_phones_will_not_support_project_treble-news-28590.php
https://www.gsmarena.com/oneplus_ex...ject_treble_on_current_devices-news-28616.php
So will Moto X4 get Treble in Oreo Update? I'm afraid it might not get it.

Is Project Treble linked with the A/B Partitions ? If yes, we have already these partitions on our Moto X4 (non Android One Version) so I hope it will be compatible...

Taolefeng said:
Is Project Treble linked with the A/B Partitions ? If yes, we have already these partitions on our Moto X4 (non Android One Version) so I hope it will be compatible...
Click to expand...
Click to collapse
Nobody knows for sure yet. We'll have to wait and see when Oreo drops.

x4 was launched quite a bit after oreo was already officially released, and it's a mid-end phone by Motorola (they even give moto g4 oreo update, even though it's because they feel pressured due to previous mistaken promise, they still said they 'll go through with it...) .
It could definitely increase sales of the moto x4 and make it more able to compete with devices that will be released on Oreo in the next months coming. It would mean that customers will get updates as frequently as other devices released on Oreo,
Moto x4 retail version is released with A/B partitions just like Pixel 2XL. Seems like A/B partitioning is essential for Treble, which devices like 1+5 lack indeed.
So these are 5 factors which could contribute to treble being activated when Oreo comes to the x4 but treble could just as likely not be on it...
There are phones that got released way before the x4 that did pull it off, so it's possible.

hpgramani said:
Many OEM like Nokia, OnePlus etc are disabling Project Treble on their devices in Oreo updating stating that Treble requires re-partitioning of internal storage which if done via OTA has a high probability of bricking the phone.
https://m.gsmarena.com/current_nokia_phones_will_not_support_project_treble-news-28590.php
https://www.gsmarena.com/oneplus_ex...ject_treble_on_current_devices-news-28616.php
So will Moto X4 get Treble in Oreo Update? I'm afraid it might not get it.
Click to expand...
Click to collapse
I think motoX4 will get Treble update as having somewhat above average knowledge in smartphones, I noticed that i'm getting 44gb of space left in my 64gb variant. and moto having almost stock android without tones of blootwares. I think i should get somewhat 50-52 gb of onboard storage. And as Project Treble needs another partition may be that's where the extra space went.
Its all just my way of connecting dots and looking at the big picture. I hope i'm not wrong and u guys will agree:angel::angel:

Off topic but has anyone seen any news about the oreo update for Moto devices? I'm seeing on the tech blogs that other devices receiving betas. Helk,the HTC u life on T-Mobile is actually receiving oreo right now. I saw somewhere that Moto said promised oreo by the end of the year and no word.
Sent from my [device_name] using XDA-Developers Legacy app

aakarshmodi said:
I think motoX4 will get Treble update as having somewhat above average knowledge in smartphones, I noticed that i'm getting 44gb of space left in my 64gb variant. and moto having almost stock android without tones of blootwares. I think i should get somewhat 50-52 gb of onboard storage. And as Project Treble needs another partition may be that's where the extra space went.
Its all just my way of connecting dots and looking at the big picture. I hope i'm not wrong and u guys will agree:angel::angel:
Click to expand...
Click to collapse
our nougat has A/B partitions already, they have nothing to do with treble... that's where all the space went. z2 is not getting it, and we probably are neither..... as someone with above average knowledge, yours is pretty lacking

bombaglad said:
our nougat has A/B partitions already, they have nothing to do with treble... that's where all the space went. z2 is not getting it, and we probably are neither..... as someone with above average knowledge, yours is pretty lacking
Click to expand...
Click to collapse
We will get treble feature .... Apart from that there is no reason to give a/b partition. As it was also rumored in early 2017 for motox4. Anyways let's wait n hope for the best

aakarshmodi said:
We will get treble feature .... Apart from that there is no reason to give a/b partition. As it was also rumored in early 2017 for motox4. Anyways let's wait n hope for the best
Click to expand...
Click to collapse
That's not true at all. The reason for A/B partitions is to allow for seamless background updates, nothing to do with Treble. They were implemented on Pixel 1s before Oreo and Treble even existed.
Moto is under zero obligation to implement Treble on the X4... Unless Google really asks them to as part of the Android One program. Which is possible. I'd say it's 50/50 if we get it.

FanDroid09 said:
That's not true at all. The reason for A/B partitions is to allow for seamless background updates, nothing to do with Treble. They were implemented on Pixel 1s before Oreo and Treble even existed.
Moto is under zero obligation to implement Treble on the X4... Unless Google really asks them to as part of the Android One program. Which is possible. I'd say it's 50/50 if we get it.
Click to expand...
Click to collapse
the question is, whether google will treat a1 devices like pixels in this regard

funkymonkey_01 said:
Off topic but has anyone seen any news about the oreo update for Moto devices? I'm seeing on the tech blogs that other devices receiving betas. Helk,the HTC u life on T-Mobile is actually receiving oreo right now. I saw somewhere that Moto said promised oreo by the end of the year and no word.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The Android one edition starts recieving Oreo.
https://www.phonearena.com/news/Mot...arts-getting-Android-8.0-Oreo-update_id101000
So those who have Android one edition can check whether project treble is enabled or not

any updates regardes treble?

https://forum.xda-developers.com/showpost.php?p=74940357&postcount=17
Looks like it's not enabled.

LIONS1 said:
any updates regardes treble?
Click to expand...
Click to collapse
no treble support for mx4 even after oreo update

Sagar_1401 said:
no treble support for mx4 even after oreo update
Click to expand...
Click to collapse
same here for MI A1 thats disappointment only HTC U11 Life has it

aakarshmodi said:
We will get treble feature .... Apart from that there is no reason to give a/b partition. As it was also rumored in early 2017 for motox4. Anyways let's wait n hope for the best
Click to expand...
Click to collapse
we're not getting it, told you so

Anyone grab OTA zip yet? Would love to take a peek.
As for treble...wonder if proprietary vendor/HALs will ever pop up anywhere (assuming they were ever created). Seems that is all that is needed to implement it on an otherwise capable device.

bombaglad said:
we're not getting it, told you so
Click to expand...
Click to collapse
Not having it enabled yet isn't necessarily a sign that it isn't coming. The question is still is it partitioned TO support it, even if not using it yet. it was the repartitioning that other vendors claimed made it nearly impossible to support older devices, so if they have prepared and partitioned it cleanly, then there is still hope. It isn't a good sign though.

ebrandsberg said:
Not having it enabled yet isn't necessarily a sign that it isn't coming. The question is still is it partitioned TO support it, even if not using it yet. it was the repartitioning that other vendors claimed made it nearly impossible to support older devices, so if they have prepared and partitioned it cleanly, then there is still hope. It isn't a good sign though.
Click to expand...
Click to collapse
yes it is, stop waking false hopes in people.. the current A/B partitioning scheme has nothing to do with treble, all would still have to be repartitioned again for treble to be implemented... if they wanted to implement it, they would've done it already.... why would they even make two separate oreo builds, one without treble and later one with it?
also, i hate how everyone talks about "enabling" and "not enabling" treble... it's not a flag in build.prop or whatever that you can just enable, which makes treble magically work! it's a huge structural change on a pretty damn deep level. so please, let's talk about implementing, rather than enabling treble

bombaglad said:
yes it is, stop waking false hopes in people.. the current A/B partitioning scheme has nothing to do with treble, all would still have to be repartitioned again for treble to be implemented... if they wanted to implement it, they would've done it already.... why would they even make two separate oreo builds, one without treble and later one with it?
also, i hate how everyone talks about "enabling" and "not enabling" treble... it's not a flag in build.prop or whatever that you can just enable, which makes treble magically work! it's a huge structural change on a pretty damn deep level. so please, let's talk about implementing, rather than enabling treble
Click to expand...
Click to collapse
It is about being able to load the proper vendor modules into the proper places. The key questions are a) are the places ready to receive the vendor modules when ready and b) when will the vendor modules be ready. You can easily have a Treble partition structure without the code to put in it. Why else would there be so many partitions vs. other phones on the X4? I'm not saying treble WILL ever be enabled, but there can be very good reasons (like lack of Qualcomm Treble modules for the hardware) why the phone hasn't had a treble enabled build yet.

Sign for Project treble for the oneplus 5t!!!! change.org.

Hello everyone,
As i am sure you're aware, Oneplus recently told the public that they weren't going to support project treble with their devices. This only concerns the oneplus 5t but maybe with a bit of luck and community support, they shall do the same for their other devices on oreo.
Let's hope this works!!
https://www.change.org/p/carl-pei-we...ail_responsive

And we have yet another thread for this ...
Sent from my OnePlus 3 using Tapatalk

It's dead. They will never give treble for actual devices. That already said that they just can't because treble need 2 data partitions and actual OnePlus devices have only one, they said an OTA update to make this is possible but there is a risk to brick the device so they cancelled treble development. Only OnePlus 6 and futures phones will include this.

Bryandu13 said:
It's dead. They will never give treble for actual devices. That already said that they just can't because treble need 2 data partitions and actual OnePlus devices have only one, they said an OTA update to make this is possible but there is a risk to brick the device so they cancelled treble development. Only OnePlus 6 and futures phones will include this.
Click to expand...
Click to collapse
They can live with about 10-15 threads asking for Treble from ppl without even understanding what is needed for it, but they don't wanna have 2395482 threads of ppl who killed their phone via OTA, seems legit for me.

Treble is nice and all, but TBH we're gonna be just fine without it. OnePlus devices are very popular in dev community and use very common internals so updating shouldn't be an issue. Just look at how far people brought the original Galaxy S, a phone that shipped with 2.1 Eclair! Treble is far more important for mid-range and low-end, less popular devices - the ones which usually get forgotten soon after launch.
Tl;dr: we'll survive. I'm sure OP3/T and 5/T will be among the first to get LineageOS 16 even without Treble.
Sent from my OnePlus 3 using Tapatalk

Oh come on they dont have a partition bro, may be there next devices will support it

Devices that don't have a separate Vendor partition will not have treble enabled. No need for any Petition etc
Until OnePlus ship a device with a vendor partition there won't be treble

Support of RR remix

Somebody tried reguest support of some custom rom ? I try it right now.

najjannajS650 said:
Somebody tried reguest support of some custom rom ? I try it right now.
Click to expand...
Click to collapse
Nothing will do it, first you need a working TWRP, secondly you need a dev that would do active support. Forget about it, Moto G6 (ALI) has no developers interest in this phone model.

kemoti said:
Nothing will do it, first you need a working TWRP, secondly you need a dev that would do active support. Forget about it, Moto G6 (ALI) has no developers interest in this phone model.
Click to expand...
Click to collapse
The G6 has been out since just May, what are you talking about? Most people in the Moto G series had G5S+'s where there's a **** load of development for and decided that the G6 wasn't enough of an upgrade for them to make the change, but there will always be a potential for new Devs to come to a device. I'll take this over to Android Forums for all I care and crowd source over there, there's always been a desire from up and coming Devs to work on low end phones over there, I bet anything someone will be willing to Dev on a donate device, especially a mid range.

Causical said:
The G6 has been out since just May, what are you talking about? Most people in the Moto G series had G5S+'s where there's a **** load of development for and decided that the G6 wasn't enough of an upgrade for them to make the change, but there will always be a potential for new Devs to come to a device. I'll take this over to Android Forums for all I care and crowd source over there, there's always been a desire from up and coming Devs to work on low end phones over there, I bet anything someone will be willing to Dev on a donate device, especially a mid range.
Click to expand...
Click to collapse
Treble GSI's are the future for our phone. i already had RR booting and working with the official GSI available on the project treble forums. TWRP works, it just needs some kinks worked out before the broad public uses (have to wipe data to put files on internal memory, and some people have had success with forceencrypt/dm verity disabling)

Dadud said:
Treble GSI's are the future for our phone. i already had RR booting and working with the official GSI available on the project treble forums. TWRP works, it just needs some kinks worked out before the broad public uses (have to wipe data to put files on internal memory, and some people have had success with forceencrypt/dm verity disabling)
Click to expand...
Click to collapse
Just for sake of discussion, doesn't Treble offer less feature implementation when it comes to actual device hardware to software "connectivity" [for lack of a better word] in other words little hardware side things that could be tweaked by the user with CyanogenMod builds per say?

Causical said:
Just for sake of discussion, doesn't Treble offer less feature implementation when it comes to actual device hardware to software "connectivity" [for lack of a better word] in other words little hardware side things that could be tweaked by the user with CyanogenMod builds per say?
Click to expand...
Click to collapse
im not exactly sure what you mean by that but i assume any hardware issues (i've really only noticed some bugginess with bluetooth audio) can be fixed with a custom system image based on an official GSI.

Dadud said:
im not exactly sure what you mean by that but i assume any hardware issues (i've really only noticed some bugginess with bluetooth audio) can be fixed with a custom system image based on an official GSI.
Click to expand...
Click to collapse
Yeah, right...I meant like more system side like deeply modified frameworks and stuff and things that have been modded in the system like tweaks to things like active or "live display" or whatever. Other things like how notification LED functions and tweaks to the make camera actions snappier...I know there's more...I guess a better way to describe it is things that Xposed would do, but built into a ROM. Treble isn't enabling those things is it? Since it's just a software update that's entirely parallel to a phones hardware?

Thanks, that is what I want to hear ?

Good to know some of you were able to boot GSI's already. I maintain RR for another Moto device. Once I get the bootloader unlocked, I'll work towards getting us up and running with RR

Active developers for the Razer Phone 2?

Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.

Hello jcole20
That would be awesome if some devs started doing something with the RP2! If I had the knowledge, I would!! I've had the RP2 since June of this year. I had some issues with it at first but they have been worked out. I really like the phone and it would be cool to see some devs show the RP2 some love lol. Hopefully you can get something started! Take care!
Dennis

jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
I am sure people would love to see some device specific development. I have read that since the release of project treble most people just flash the system image from other roms. I specifically would love to see a stockish rom so I don't loose chroma but still get updated security patches.

I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.

Krazy_Calvin said:
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Click to expand...
Click to collapse
Most functionalities work on Pie GSIs out-of-box (you need to manually install ims.apk in order to receive SMS while on LTE, see relevant threads here, or look for it on some GSI threads such as Havoc 2.9). exFAT also works on supported GSI (with arter97's kernel), while it's not supported on stock. The only problems I have so far are bluetooth-related, and also the inability to set SELinux to permissive (not sure which might be the real cause as arter97 stated the SELinux could be permissive).
Bluetooth media audio doesn't work at all on GSI, partly due to the crippling overlays (which prevents aptX from working, and probably some other limitations). Phone calls work with a bluetooth headset, but for some reasons I couldn't properly route phone calls to my Huawei Watch 2 (which means I always have to take the call from my phone directly).
Given the mostly positive result with numerous GSIs (and that some users are happy with stock ROM, or stock-based ROM modifications), active ROM developments for the device itself doesn't seem to be at a high priority (as some might be able to contribute patches for this device to their favorite GSI instead)...

I'm currently working on my own build of LOS. I haven't seen to much active development either I'm new to rom building but looks like we could use all the help we can get!

I think the only active dev we have for this phone is Arter97's kernel and people tinkering with GSIs to get them working as they should. I wish there was more being done with the stock ROM because I like a lot of it's features, but am having a hard time dealing with it's overall instability. I'd be happy to help develop or test in whatever way I can, though.

jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
Yeah, it’s definitely just total lack of interest from other devs. We even have a guy with a prototype Razer Phone 2 with an intact DRM partition and unlocked bootloader (Allowing Netflix HD and Vudu HDX) but we couldn’t even pay anyone to try to port it.
I think if we had a fully working AOSP tree that it would possibly bring other devs into the scene. Who knows though, it has never been a popular device despite how great it is.

LSS4181 said:
Most functionalities work on Pie GSIs out-of-box.
Click to expand...
Click to collapse
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?

EMJI79 said:
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
Click to expand...
Click to collapse
A stock Android 10 (which means a stock vendor image for Android 10) is not necessarily required to have a usable Android 10 ROM (though it may speed up the development to some extent, if it does have one), but for GSI, having a stock Android 10 vendor image can be better (currently it's a hit-or-miss on existing Android 10 GSIs).
Another device that I have, Google Pixel C, never had stock Android 9 (so never had stock vendor images for Android 9, only for up to Android 8.1), but custom Android 9 ROMs are already available (thanks to followmsi's efforts) and are working well. For Android 9 ROMs, the build system builds new vendor images along with system image.
It's just whether we're going to see our device's trees being made possible, so we can start from there to develop our own custom ROMs. The existing materials might be a good starting point in making trees.
- Working with proprietary blobs (from Lineage)
- arter97's kernel (can be useful for making a kernel tree, though one can also consider using stock kernel source as a base)
- Razer factory images and kernel sources (for studying stock ROM/kernel details, and extracting necessary system and vendor blobs)

If you can port LineageOS to this device, great!

I don't understand why people aren't flocking to this device. I came from the LG G6 that probably will be stuck on Oreo forever that is way more popular. The RP2 is cheap, has killer specs + a micro SD card slot + a newer version of Android. Should be a developers dream, you would think. *shrug*

Not sure if anyone's active on this device at present. With RP2's 9.0 MR2 available on the official factory images page the latest proprietary blobs (as well as stock kernel source) are now publicly accessible.
Actually arter97 once mentioned that his RP2 kernel is almost inline with his OP6 kernel (which is also sdm845 and shares some similarities), so it's possible that OP6 (enchilada) trees may be a good starting point, but I'm not sure if any configurations are needed to keep 120Hz working as high refresh rate is relatively uncommon.
My time is very limited so I won't be able to dedicate too much time to experiment on this. At present most functionalities work fine with GSI (including Bluetooth, although tricky and aptX still not working).

IDK how relevant this is anymore but as a new razor phone 2 user to be soon I have been keeping up and it seems that @f(x)THaxxorX could be a possible candidate of what you're looking for I've been keeping up with development on the phone seems like he is doing pretty well even if we get patched gsi which properly work is better than nothing.