From my understanding Project **Treble** was supposed to separate Android's OS data from the OEM's binaries (which are more or less equivalent to the drivers one installs on Windows) into different partitions. From that point on, Android device certification would include ensuring a device could boot Google's Generic System Images and Treble support was supposed to become mandatory for devices released with Android 9.0 or later. By this logic, seven years later, everything one could reasonably get their hands on would be Treble compliant - yet custom ROMs still seem to be made bespoke to individual devices, and I do not find much mention of people installing Google's GSIs. Why? Did Treble fail in its original purpose somehow? Why is there still no equivalent to doing a clean Windows install for Android devices?

I've recently got this new device which shipped with an Android >=4.0 Jelly Bean, and I was wondering how to increase zram on it because with the current parameters, it happens that even the foreground application goes out of memory and gets killed by the system. So you know, weird. You know, because I have other devices with the same 2 gigabytes of RAM which shipped with Android Jelly Bean and still run this same very recent Android version this new device runs on which I have never experienced this issue unless than when like I enable all types of tethering and run >10 applications in the background at the same time. I've heard it like supports something new called "Treble". I've also read now that there are Android Java applications whose entire purpose is just editing the zram parameters, which seems totally wild and inappropriate to me, so I was wondering if it was possible to do it properly without having to deal with such weird stuff.

I have a Samsung s10e g9700 flashed with Corvus OS gsi (seems based on phh's gsi), which worked basically fine for almost a month. But when I flashed a modified system.img based on Corvus OS gsi, the phone stuck on OS boot animation (endless loop). Then I flashed back to the origin Corvus OS gsi , but the phone still stuck on OS boot animation. I'm sure that I have only flashed system partition and the origin Corvus OS gsi can work. I don't know why my phone cannot boot. But I have found that adb can be used when my phone stuck on OS boot animation, so I have got some adb logcat: logcat1 logcat2 logcat3 I have not backup my userdata (there is no twrp for my device), and the data is FBE locked , so is there any ways to fix it without losing my data?

I have a Samsung Galaxy Tab 4 8.0 (SM-T330NU) supported by Project Treble. It says the GSI is system-arm32-binder64-ab-vndklite.img.xz, but what I find here on GitHub is system-**squeak**-arm32-binder64-ab-vndklite-gogapps.img.xz. Can I install that on the tablet or does it have to be that specific GSI?

Title says it all By way of background [Project Treble](https://source.android.com/devices/architecture/treble) was announced with release of Oreo to speed up OS updates by reducing OEM delay . Devices running Oreo out of the box are expected to have it , so how do I check if my device has it and I can expect faster updates?

My old phone is running Android 10. I wanted to install Android 14 beta on it. Bootloader is locked. From what I know, unlocking bootloader would reset the device. Therefore Wifi passwords are gone. This is ok as I know them. The problem is my router admin has setup something so when using randomized MAC address it doesn't connect. But fron what I Googled, it seems MAC address is hardware based so resetting phone wouldn't change it. So, my question is, does MAC address reset in unlocking bootloader or flashing GSI make me unable to access the network? If possible, please actually try because I don't want to mess up I have no experience in this area.

I tried to update my Xiaomi Mi A2 to Android Pie since yesterday the Beta was Released. At first, I tried to install the official provided one, but after facing some errors, I installed the Treble version of the Android Pie Pixel Experience ROM. It was working perfectly, but after installing Pixelify with Magisk, my WiFi stopped working, and I got the error MAC 02:00:00:00:00. After trying some things with terminal apps and root, I opted for reinstalling the modem image, which I thought that could solve the problem, but instead, the phone didn't turn on, it kept on the Android One screen. So after waiting for some hours, I decided to format the phone and lose all of my data. I formatted the system partition with fastboot erase system_a and fastboot erase system_b, but when trying to reinstall the PixelExperienceP ROM, I receive this error again and again: fastboot flash system_a PixelExperienceP-arm64-ab.img Sending sparse 'system_a' 1/5 (524284 KB) FAILED (Error reading sparse file) Finished. Total time: 24.591s After that, I am not allowed to send any command to the phone until I restart de bootloader. I have tried to install different ROMs, the stock one, other Android versions, but I get the same error on all of them. Please, any ideas on how to solve my problem? I am really worried about having broken it. Thanks in advance.

I recently got an android phone running AOSP Android 5.1 Lollipop. I want to upgrade its software to higher android version, probably 9.0 as per the phone's capacity. But for that, I need treble support in the phone. And for that, I need to create a vendor partition. Here is a tutorial I found on XDA. [Link](https://forum.xda-developers.com/t/guide-project-treble-manual-create-vendor-partition-for-pt-gsi-rom-mi3-mi4.3878995/) This guide is focused on MI3/MI4 devices and the resource ROM mentioned in it is also for MI3/MI4 devices. I think they may not work on my phone. The phone with me is of Micromax Canvas model. So please guide me through this. Thanks.

Today, I am back to challenge you all. As you would have guessed from the question title, this post is to know about enabling treble support on old phones. Of course, there are a lot of guides on the internet about this and I **"will"** explain how this post is different from them. First, we have a post about this on this very site. Link: Here, the question has not been properly answered so this is not helpful. I found the next link from the above link. Link: This is specific to redmi note 4. So, provides no help to non MIUI users. Now, we can definitely install a custom rom to enable treble but such roms are not available for all devices. So, now, let me be specific with my device. I have a device running Android 5.1 with MediaTek MT6735 processor. Now, I have searched a lot in the internet about custom roms and have installed many roms and have **"many times hard bricked my phone"**. With no options left with me and you not annoyed by reading so much, can you please give me a way I can enable treble support using a similar way found in the above XDA post? Or any other way, if you know? And please don't, just don't tell me to either buy a new phone or give up trying to enable treble support on my device. Thanks for reading.

if project treble aims to separate the platform and vendor partitions so they can be updated separately, why is the kernel source code needed when building system.img (platform) for AOSP, isn't the kernel source code provided by the vendor side? p.s is the kernel source code used to build the core system/framework files or is it only used in the boot.img/recovery.img?

This XDA blog [How A/B Partitions and Seamless Updates Affect Custom Development on XDA](https://www.xda-developers.com/how-a-b-partitions-and-seamless-updates-affect-custom-development-on-xda/) has some Q&A's, of which : > * My device supports A/B partitions, does that mean I can make use of a Project Treble Generic System Image? > > Not necessarily. Project Treble and A/B support are unrelated. The **Motorola Moto Z2 Force doesn’t support Project Treble, yet it supports the A/B partition scheme**. > > * My device supports Project Treble, does that mean I have an A/B partition scheme? > > This is not always the case. The Honor 9 Lite is a prime example as it **supports Project Treble yet does not have an A/B partition scheme**. (Emphasis added) I thought Treble and A/B devices are synonymous in the sense having one implied other. That's not the case **Why is this? What are the differences?**

Android one phones are near stock version of Android. Starting Android 8 (or 9) project treble aims to deliver new version of Android without work from the OEM. Yet phones with Android one and treble don't get update right away, see for example the Nokia roadmap to Android Q: For example, Nokia 2.2, Nokia 3.2 and Nokia 4.2 all have Android one and start with Android 9 (so they are treble ready) and have to wait until Q1 2020. Why can't they get the GSI directly from Google servers to get update as fast as it's released by Google?

I'm trying to flash a Pixel Experience GSI onto my 2017 Samsung (SM-J730G) using TWRP . In order to do so, I need to flash the GSI's system.img into my device's System partition. However, my TWRP only allowed me to flash into either the Boot or Recovery partitions. The other options I see in other phones (System, Vendor, Preload, etc.) are nowhere to be found.