- T R E B L E Y -
Android Partition Treblerizer
A tool able to seamlessly create / remove the vendor partition from within TWRP
INTRODUCTION
The creation of a tool able to create and remove the supplier partition from TWRP, so a computer was not required. So I created this flaming TWRP ZIP which can create and remove the vendor partition from the userdata system or partitions without a computer and without deleting the files in the mother partition in the recommended configuration.
Trebley, finally, also expands on our much loved Galaxy S8, bringing with it Project Treble on the much loved device.
The tool will try to resize the mother partition without deleting it, either during the creation and removal of the supplier partition. However, this can only be done when the mother partition is ext4, only when the supplier partition is at the end of the mother partition and when the mother partition is not encrypted. The recommended configuration is the one that is obtained by selecting the first option in each option: subdividing 512 MB from the end of the system partition. A reboot is required after applying the patch to the partition table because the kernel needs to reload it before doing anything else.
REQUIREMENTS
Due to the use of a key detection binary, it is compatible only with ARM and ARM64 devices running TWRP. So far I have tested it in the Samsung Galaxy S8 but It should work in any compatible device. I made it this way so other legacy devices could transition to Treble ROMs + GSI, and Android Pie. Please let me know about other devices using this tool!!!!!
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED AND IF YOU FOLLOW MY STEPS BELOW, YOU WILL LOSE YOUR WARRANTY, KNOX WILL DISPLAY 0x1! I'M NOT RESPONSIBLE FOR ANY DAMAGED DEVICE!.
!!! Whatever you do, it is at your own risk !!!
Either for creating or removing a vendor partition, follow these steps:
1. Download the TWRP ZIP tool to your External SD card.
2. Boot to TWRP recovery, under Install, flash the ZIP file as any other ROM or MOD file to execute the tool.
3. Reboot to recovery again to ensure the changes are applied properly.
4. In some cases you will need to format the mother partition after adding or removing the vendor partition next to it.
CREATE A VENDOR PARTITION:
So far these are the available options:
Mother partition selection: system / userdata
Split position: Splitting from the end / start of the mother partition.
Vendor partition size: 512 / 915 MB
REMOVE THE VENDOR PARTITION:
Should a Vendor module already exists, Trebley offers to remove it, returning to a Non-Treble partition table. It will return the space to the mother partition, system or userdata. So, older non Treble ROMs could be flashed after the mandatory reboot.
DOWNLOAD
Trebley_APT_v1.0_ARM_20190215-signed.zip
SOURCES
All rights reserved to the project: Party and its creator(@Oki).
CAUTION
Currently, we recommend the use of Trebley, exclusively to developers, as until now there has been no development of material related to the project treble, this project lays the foundations creating the partition vendor, for the support treble.
CREDITS
@someone755 for the keycheck binary
@Zackptg5 for the V4A install script that inspired my version.
@Oki for the base script.
XDA:DevDB Information
[PARTITION][TREBLE] Project Treble for Samsung Galaxy S8 [dreamltexx][15.02.2019], Tool/Utility for the Samsung Galaxy S8
Contributors
DarioRetr
Source Code: https://forum.xda-developers.com/axon-7/development/tool-party-v0-1-vendor-partition-t3831517
Version Information
Status: Alpha
Current Stable Version: V1.0
Stable Release Date: 2019-02-26
Current Beta Version: V0.5
Beta Release Date: 2019-02-15
Created 2019-02-17
Last Updated 2019-02-17
thx the tools makes me now easyer to create and remove my treble partition since i used for the moment all time parted with console on pc. for the one that thinks that is treble. without right vendor partition is useless. i have a partition that boots gsi but with a nice glitched display
geiti94 said:
thx the tools makes me now easyer to create and remove my treble partition since i used for the moment all time parted with console on pc. for the one that thinks that is treble. without right vendor partition is useless. i have a partition that boots gsi but with a nice glitched display
Click to expand...
Click to collapse
It is certainly not Trebley's fault, as it was specified in red, that Trebley is currently recommended for use only to developers, as Trebley, lays the foundations for Project Treble by creating the Vendor partition, after which it will be up to the developers Compile from source the vendor. IMG, the TWRP custom, and the kernel, to allow the startup of Project Treble.
In addition, in layman's terms, Trebley currently creates the vendor partition, after which it will be you dev compile the sources by adjusting them to the treble standards, to allow you to use project treble on the Samsung S8.
Members are reminded that making changes to device partitions is inherently dangerous. With that in mind, exercise caution and if in doubt, DON'T.
LenAsh said:
Members are reminded that making changes to device partitions is inherently dangerous. With that in mind, exercise caution and if in doubt, DON'T.
Click to expand...
Click to collapse
Dear @LenAsh, Trebley, precisely ensures through the scripts, a greater security, as it is all automated and calculated to the milimeter, and above all reduces the risk. Clearly, currently Trebley for S8, it is in its initial state, where it introduces the vendor partition, now it's up to you have developer, compile and propagate the material needed to start project treble in our Samsung S8 device
Any hope on this zip working on s8 phones? Or porting for others?
Rehvix said:
Any hope on this zip working on s8 phones? Or porting for others?
Click to expand...
Click to collapse
This zip is made for the Samsung Galaxy S8, but also works on other devices, because the script is multi platform and arm, currently, but we recommend the use of the zip file to developers, because currently Trebley creates only the vendor partition, but Without the vendor file, and a modified TWRP for treble support, you still can't use the project treble. We need to wait for some dev, compile from source, the appropriate kernel for project treble, and a vendor appropriate to the project treble along with a custom TWRP, allowing the Samsung S8 to use the vendor partition created by Trebley, and finally use Project Treble.
so can we get aosp room sir..??
onMyConquest said:
so can we get aosp room sir..??
Click to expand...
Click to collapse
In order to run a GSI, you have to wait for the scene, wait for some Dev, compile the kernel and the vendor, and place a custom twrp, to allow the project treble to go. In practice Trebley, prepares the partition making it compatible with Project Treble. Now you have to have developer share software, clearly depends on scene to scene, to give you an example on the Samsung Galaxy S6 Edge, with the same method, now they can use the GSI, with project treble.
Plz someon try this. Im afraid to brick
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Can somebody take this down or at least force the guy to rename it ? this is clearly a script that'll only make an empty partition, this is NOT treble as stated in the thread also by reading the messages it's clear the OP doesn't know what he's talking about
If I understand, in the case of Galaxy S8, it splits the /system partition to create a /vendor partition and copy the contents from /system/vendor to the new /vendor partition, right?
However, dont the binaries and/or drivers need to be adapted for project Treble? I mean how does the (lets say) new aosp rom know what drivers use for each feature?
Josevega said:
Can somebody take this down or at least force the guy to rename it ? this is clearly a script that'll only make an empty partition, this is NOT treble as stated in the thread also by reading the messages it's clear the OP doesn't know what he's talking about
Click to expand...
Click to collapse
My dear, create the partition to make it compatible with the Project Treble, now instead of talking about things, why do not you go to work, adapting the kernel and the vendor, and send the vendor.img, and the boot.img and twrp .img, to be able to use project treble?
Also before saying, that Trebley, does not know what he is talking about, he learns to read English, why it is written clearly is round, that this script is recommended to use you have developer to ensure project treble also on S8.
If then you want to talk bad, because evidently put project treble on S8, it requires too much work as you have to move the device tree blob and so on, and for question of laziness you want to deny the possibility of having treble to users.
So we know that the developers of the scene samsung S8, does not paste them to adapt the kernel to project treble.
bamsbamx said:
If I understand, in the case of Galaxy S8, it splits the /system partition to create a /vendor partition and copy the contents from /system/vendor to the new /vendor partition, right?
However, dont the binaries and/or drivers need to be adapted for project Treble? I mean how does the (lets say) new aosp rom know what drivers use for each feature?
Click to expand...
Click to collapse
Then, Trebley, takes part of partition either from system or userdata, and then creates a new partition named vendor, and makes the device compatible with project treble, then it needs a developer, move device tree blobs, and systems the configuration , because it is not enough to move the vendor into vendor, you have to compile the kernel so that you take the drivers from the vendor, you have to do some work first at the software level.
You need someone who has Ubuntu, take the device sources from GitHub, and run the device tree, and compile the vendor.img and boot.img which includes the kernel, and then edit the twrp to make it compatible with Treble, after that you can use treble on the device.
Trebley, did not want to compile the vendor for the Samsung S8 users, for one reason, because Trebley's developers are external to the Samsung S8 scene, and compile a kernel or vendor for an S8, as you might compile for an S7 Edge or an S6, it could cause users of the S8, slowdowns, battery that you download easily, GSI where the camera does not work.
So we prefer to be your developer of the scene, to compile the vendor and boot, to ensure reliability even with the project treble. Because we do not want s8 users to consider project treble as an unstable project.
In addition, this project has also expanded on Note 8, we will see who will be faster to adapt kernels and vendors.
Update 18/02/2019
A developer of the S7 Edge scene, he decided to contribute to the project, starting to work on the sources of the device.
https://github.com/KiubeDev
Hello ,Can you make this for s7 edge?
DarioRetr said:
In addition, this project has also expanded on Note 8, we will see who will be faster to adapt kernels and vendors.
Update 18/02/2019
A developer of the S7 Edge scene, he decided to contribute to the project, starting to work on the sources of the device.
https://github.com/KiubeDev
Click to expand...
Click to collapse
In this github account all the repositories are forked from ivan meler, he is galaxy s7/edge developer i can see a universal exynos 8895 repo but there is no device specific code for dream2ltexx and only a highly experienced developer can make this then there will be no need for treble support.
Why are u not using the preload partition???? Would be much easier as its only used for apps to be installed in stock Rom for a carrier or Region...
Can I install this, and then https://forum.xda-developers.com/pr...vice-development/lineage-phh-treble-t3767690?
Will that brick?
qasim799 said:
In this github account all the repositories are forked from ivan meler, he is galaxy s7/edge developer i can see a universal exynos 8895 repo but there is no device specific code for dream2ltexx and only a highly experienced developer can make this then there will be no need for treble support.
Click to expand...
Click to collapse
Dear, that repository is another, he is just a dev, the repository where they are working and gitlab, and is only accessible to developers.
Related
Hi guys,
I'm not a Dev but I want to talk about something interesting in the Android modding scene.
A Dev called Michael Zimmermann is developing a Grub version fof Qualcomm Android Devices (OPT is based on SD810..!).
Could be interesting to see in on Oneplus TWO, right?
Info about the project here.
Code:
Let me talk about #EFIDroid( #G4A ).
You might have eared something about it, not much up to now because there's nothing released for users.
Let's start: what's it?
First of all this amazing project is developed by +Michael Zimmermann I am NOT the dev��
G4A is a port of the well-known GNU GRUB bootloader to Qualcomm (up to now) (android) devices.
Many when it was announced asked: will we be able to boot windows or <insert Linux distro here> ?
The answer is partially no. At least it's not the main goal of the project, bit grub is able to boot a linux distro,
cuz it's the same bootloader you may have on your pc. Actually G4A is used as multiboot solution for android, like multirom.
Android ROMs are not designed for multiboot and you see that (for example) on multirom: you need a kernel with kexec-hardboot, a custom recovery and huge crazy hacks on ramdisk.
Damn, this makes your device crazy... G4A is different. Totally different. Much easier. Better.
So how does it works?
One of the rules is to make the less impact on system as possible. G4A only needs a custom boot loader.
Qualcomm released LK (their bootloader that every qcom device uses) sources.
This bootloader support almost all qcom soc, even old ones such as msm7x27.
This bootloader was hacked with some additions like uboot api (that's used to load grub).
Now the problem is booting that lk. There are two ways: let's start with the easier:
Some devices allow us to boot unsigned bootloader images (that's dangerous on security side) but we use that to write our hacked lk that will boot grub and stop. Other (and most) devices don't support unsigned bootloaders.
The bootloader is flashed both on boot and recovery partitions. Then the magic show starts.
We call this 2th boot: the stock bootloader thinks it's booting a kernel (or recovery) while it's booting another bootloader, stunningly easy and stupid.
The 2th bootloader will detect from which partition is loaded and it will choose to boot straight to recovery or of it has to load grub.
Grub is placed on a folder (boot/grub) placed on NAND, usually on sdcard and protected from user by fuse and rw permissions.
When you boot android, the bootloader will load grub, this one will make you choose what to boot recovery, system, a multibooted system, recovery running "on" a multibooted system etc.
Ofc the ramdisk has to be hacked, but to keep rom intact, the hacks are done on-the-go.
How can I install it/ manage multibooted systems?
G4A will be releases with an app called 'GRUB Manager' that will install it with a few clicks,
you just need root and an unlocked bootloader.
This app will help you creating and managing systems by adding entries to grub.cfg (for who knows how grub works).
Which devices will be supported?
Almost all qcom-powered devices can run this, the port is surprisingly easy (for devs ofc), it may take you just an half hour. Currently official supported devices are: Xiaomi Mi2(s), Motorola Moto E and Xiaomi Redmi 1s.
If you're an expert dev and you've done a port for your device/ you're interested in, hangout me.
ETA?
Sorry not eta allowed, the first build will be for devs and advanced users (I remember that on some devices we write on bootloader partition, if something goes wrong, it's not so easy to recover it) when multiboot will be fully working (now about 80%).
To sum up
> EFIDroid is an opensource project that has the goal to provide the best multiboot solution for qcom devices
> There are two ways to install this: on bootloader and 2th boot
> The GRUB Manager app will install EFIDroid and it will manage multibooted systems
> It can support almost all qcom devices
> It will be released soon for devs and advanced users as a first public beta
Some links:
Follow +EFIDroid for news
Sources
Community
I would love to port this to our OPT, let me know if I can help you out some way.
WhyOrean said:
I would love to port this to our OPT, let me know if I can help you out some way.
Click to expand...
Click to collapse
Hi, really nice!
I'm not a dev but I would like to share this news, so if you are able to work on it, please port it!
Its a really cool project, thanks i wasn't aware of it.
As for porting to the OnePlus two, i wouldn't place too much hope in it ( just yet ). Its a complicated port and the code is still in a early stage. It doesn't offer anything substantially beneficial to the user over the Multirom implementation at this point.
Maxximo88 said:
Hi, really nice!
I'm not a dev but I would like to share this news, so if you are able to work on it, please port it!
Click to expand...
Click to collapse
I'm on it
WhyOrean said:
I'm on it
Click to expand...
Click to collapse
Thanks man!
I think could be a great project!
- T R E B L E Y -
Android Partition Treblerizer
A tool able to seamlessly create / remove the vendor partition from within TWRP
INTRODUCTION
The creation of a tool able to create and remove the supplier partition from TWRP, so a computer was not required. So I created this flaming TWRP ZIP which can create and remove the vendor partition from the userdata system or partitions without a computer and without deleting the files in the mother partition in the recommended configuration.
Trebley, finally, also expands on our much loved Galaxy Note 8, bringing with it Project Treble on the much loved device.
The tool will try to resize the mother partition without deleting it, either during the creation and removal of the supplier partition. However, this can only be done when the mother partition is ext4, only when the supplier partition is at the end of the mother partition and when the mother partition is not encrypted. The recommended configuration is the one that is obtained by selecting the first option in each option: subdividing 512 MB from the end of the system partition. A reboot is required after applying the patch to the partition table because the kernel needs to reload it before doing anything else.
REQUIREMENTS
Due to the use of a key detection binary, it is compatible only with ARM and ARM64 devices running TWRP. So far I have tested it in the Samsung Galaxy Note 8 but It should work in any compatible device. I made it this way so other legacy devices could transition to Treble ROMs + GSI, and Android Pie. Please let me know about other devices using this tool!!!!!
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED AND IF YOU FOLLOW MY STEPS BELOW, YOU WILL LOSE YOUR WARRANTY, KNOX WILL DISPLAY 0x1! I'M NOT RESPONSIBLE FOR ANY DAMAGED DEVICE!.
!!! Whatever you do, it is at your own risk !!!
Either for creating or removing a vendor partition, follow these steps:
1. Download the TWRP ZIP tool to your External SD card.
2. Boot to TWRP recovery, under Install, flash the ZIP file as any other ROM or MOD file to execute the tool.
3. Reboot to recovery again to ensure the changes are applied properly.
4. In some cases you will need to format the mother partition after adding or removing the vendor partition next to it.
CREATE A VENDOR PARTITION:
So far these are the available options:
Mother partition selection: system / userdata
Split position: Splitting from the end / start of the mother partition.
Vendor partition size: 512 / 915 MB
REMOVE THE VENDOR PARTITION:
Should a Vendor module already exists, Trebley offers to remove it, returning to a Non-Treble partition table. It will return the space to the mother partition, system or userdata. So, older non Treble ROMs could be flashed after the mandatory reboot.
DOWNLOAD
Trebley_APT_v1.0_ARM_20190215-signed.zip
SOURCES
All rights reserved to the project: Party and its creator(@Oki).
CAUTION
Currently, we recommend the use of Trebley, exclusively to developers, as until now there has been no development of material related to the project treble, this project lays the foundations creating the partition vendor, for the support treble.
CREDITS
@someone755 for the keycheck binary
@Zackptg5 for the V4A install script that inspired my version.
@Oki for the base script.
XDA:DevDB Information
[PARTITION][TREBLE] Project Treble for Samsung Galaxy Note 8 [SM-N950F][15.02.2019], Tool/Utility for the Samsung Galaxy Note 8 (2017 Phone)
Contributors
DarioRetr
Source Code: https://forum.xda-developers.com/axon-7/development/tool-party-v0-1-vendor-partition-t3831517
Version Information
Status: Alpha
Current Stable Version: V1.0
Stable Release Date: 2019-02-26
Current Beta Version: V0.5
Beta Release Date: 2019-02-15
Created 2019-02-17
Last Updated 2019-02-17
oh my lord - it is happening. treble for the Note8 - just think of the possibilities :victory:
thank you unbelievably much:highfive:
WOAH dude! Finally its happening
edit: tried this and any combination i try i get a Error 2 error!
Any ideas? Or should i try this with a full wipe and try and flash it?
joluke said:
WOAH dude! Finally its happening
edit: tried this and any combination i try i get a Error 2 error!
Any ideas? Or should i try this with a full wipe and try and flash it?
Click to expand...
Click to collapse
Dont flash this yet. There's no rom compatible with this. Note that this is just a script to create partition.
v0ne said:
Dont flash this yet. There's no rom compatible with this. Note that this is just a script to create partition.
Click to expand...
Click to collapse
Ups
I'll keep it for the future then ^^
Guys, this script is currently recommended for use only you have developer, make the device compatible for Project Treble, but you need some developer of the scene, compatibilizzai kernel source for project treble, and give you the vendor.img and boot.img including a custom twrp, to be able to use a GSI and then project treble.
Furthermore, the operation of the script on all versions of Note 8 is not guaranteed.
Oh my god, here it is, but I hope that it doesnt end in the first build like everything else for note 8
Thanks devs but please dont quit now
This is insanely good work. This is so cool :laugh:
Deleted
I flashed this and got an error in TWRP.
Most likely because /dev/block/bootdevice doesn't exist on Note8, but this script is searching for that.
Shadow7107 said:
I flashed this and got an error in TWRP.
Most likely because /dev/block/bootdevice doesn't exist on Note8, but this script is searching for that.
Click to expand...
Click to collapse
What model do you have of Samsung Galaxy Note 8?
For advice and support, I suggest you join the Trebley - Making the future group!
https://t.me/joinchat/I5PCthNlYmrJ4YQY8xxXSg
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. flash my twrp from link below
2. flash treble zip
3. download any system image from https://forum.xda-developers.com/project-treble/trebleenabled-device-development and flash it as system image
Known Issues
1. need fix gps on SM-T580
2. in aosp 9.0 phh image build-in camera app crashed, all other working fine
Notes
- This is treble build, based on latest lineage 16.0, latest 3.18.137 OC kernel (thanks @followmsi) (with mac fix and 4.0.10.205 wlan driver from codeaurora project) and latest device\configs.
- for /vendor partition I use /cache (it's about 209mb, it' enough for our vendor)
- for /cache partition I use /hidden (it's about 50-60mb, it' enough for cache)
Links
Treble images
SM-T585:
1. 20190401: https://drive.google.com/file/d/1BsmyMb7hI-xYZhIj1XqLNpkfNI9kjDxa/view?usp=sharing
SM-T580:
1. 20190401: https://drive.google.com/file/d/1nQciZhBq_2BnyxbHcP4JuDDA22wUfbzW/view?usp=sharing
Root
Use Magisk if need
Recovery
SM-t585:
1. my repack with add /vendor: https://drive.google.com/file/d/1kEQ-Wwee9MYrF5i69EII8p8R_lOwwf-O/view?usp=sharing
SM-T580:
1. my repack with add /vendor: https://drive.google.com/file/d/1wB665QMq6yesKaMteHQGrmdBAKvkHo0Y/view?usp=sharing
System images
A only and 64Bits
Checked firmwares: almost all pie roms from treble's thread should work. Checked aosp, pixelexperience, arrow, havoc.
Sources
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870/tree/lineage-16.0_treble
Device tree SM-T585: https://github.com/Valera1978/android_device_samsung_gtaxllte/tree/lineage-16.0_treble
Device tree SM-T580: https://github.com/Valera1978/android_device_samsung_gtaxlwifi/tree/lineage-16.0_treble
Vendor SM-T585: https://github.com/Valera1978/android_vendor_samsung_gtaxllte/tree/lineage-16.0_treble
Vendor SM-T580: https://github.com/Valera1978/android_vendor_samsung_gtaxlwifi/tree/lineage-16.0_treble
Hi just flashed the new blissrom gsi and everything seems to be good except that the headphone jack is not working. Haven't tried a different gsi yet to see if it happens on them also or if it is a problem with our tablets. By the way this on a sm-t580
twfs said:
Hi just flashed the new blissrom gsi and everything seems to be good except that the headphone jack is not working. Haven't tried a different gsi yet to see if it happens on them also or if it is a problem with our tablets. By the way this on a sm-t580
Click to expand...
Click to collapse
I just flashed Pixel dust on my sm-t580 and the headphone is ignored.
All sounds play thru the speaker just like you didn't install a headphone.
Also the sound settings are ignored, audio playing at full volume.
Even if I changed it to all soft or even off.
The same is with Viper Os.
There is also the problem that you can't install a bigger open gaps because of the partation isn't large enough.
Thanks for the first version for our tablet.
BT audio does not work in all treble firmware
So every time I boot I get a message that says:
There's an internal problem with your device. Contact your manufacturer for details.
Is this normal after flashing Pixel Experience GSI?
Also had this issue with Resurrection Remix as well
thenubknownasepic said:
So every time I boot I get a message that says:
There's an internal problem with your device. Contact your manufacturer for details.
Is this normal after flashing Pixel Experience GSI?
Also had this issue with Resurrection Remix as well
Click to expand...
Click to collapse
I'm guessing that it will happen when your custom ROM is on a different build number from the underlying official build.
Whatever it is, I think you can just ignore it - as long as both are up-to-date, you should encounter no actual errors.
The mismatch is probaly between the build fingerprint mentioned in the build.prop file in the system partition and the build.prop file in the vendor image, specifically the ro.vendor.build.fingerprint key.
RichyE said:
I just flashed Pixel dust on my sm-t580 and the headphone is ignored.
All sounds play thru the speaker just like you didn't install a headphone.
Also the sound settings are ignored, audio playing at full volume.
Even if I changed it to all soft or even off.
The same is with Viper Os.
There is also the problem that you can't install a bigger open gaps because of the partation isn't large enough.
Thanks for the first version for our tablet.
Click to expand...
Click to collapse
I dont know about the headphones, but i have the same problem with audio always at full volume rr gsi
hi how r u
is there any problem with havoc 2.9 please?
any bugs?
Thanks @Valera1978 for this Treble implementation. I am a huge fan of Treble, as it opens a wide range of ROMs to this tablet. Do you continue development on it? It seems come to a stop?
There is another Treble implementation for this Exynos, this is for Galaxy A3 2017 (A320FL). Maybe that can help.
Please could you make a version that supports AB system images?
@Valera1978
Does it support Android 10
this project supports android 10 can someone tell me please
@Chris_0147 the project is dead, you'd better to sell the device. i'll do that also. it's too old and no developer wants to develop anymore something for it. i tried any a10/a11 gsi rom, all are not supported.
I've been looking at previous comments ,OK , I understand it doesn't support 10 and 11 but has anyone tried installing Pie and then upgrading to 10 or 11.
Nope
You can try and tell us
Chris_0147 said:
You can try and tell us
Click to expand...
Click to collapse
Very helpful, I was hoping for something more constructive
Hi guys, could any of you explain to me what is the difference between GSI based and "normal" build ROMs?
I thought most custom ROMs are based on AOSP/GSI, but right now many Android 10 ROMs for one of my devices (Lenovo P2/kuntao) are popping up and most of them are getting a lot of hate for apparently being based on GSI and are not "proper" ROMs. People are not giving any specific criticism, just generally whining, like those ROMs are useless or something.
The only difference I see is for some reason the GSI ROMs need F2FS format instead of EXT4 that is standard for other ROMs for the device.
Thanks.
To my knowledge, GSIs when properly implemented for a device are as good as a Device Specific ROM or what you call a "normal" ROM.
Usually GSIs are made for a wide-audience of devices. So the usual reason is that when a bug only available in a specific device is found. It usually isn't fixed by GSI devs.
However, Device Specific GSIs are actually made for the device it's running on. So small bugs will be fixed.
Usually though problems come from a bad vendor implementation. So if your device has a bad vendor implementation. I guess that would be a cost for concern. You can create your own but you'd have to wait for developers to create it.
They may be mad about limited Magisk Support. Since Magisk currently does not support GSI ROMs. But other than that, I don't see why GSIs get so much hate.
In a Treble world, don't all ROMs technically include a GSI? Because anything living in /system and distributed by a system.img file can actually be run as a GSI on any device that is Treble compatible.
However, right now it's probably like you say, vendors (and enthusiast ROM makers) may not completely adhere to the rules set by Android/AOSP, such as putting the correct things in the system, product, vendor and odm partitions. They include nasty hacks to solve some idiosyncratic bugs for their specific device. Nothing wrong with some nasty hacks, but they should put them in the right place (in product or odm partitions). As such, in theory there should be no need for separate system images any more.
In such a world, I suspect that indeed in the near future we will only load the GSI of our choice for all devices. We will rely only on whole ROM packages when drivers (vendor partition and optionally odm) need to be updated. This is needed for example for increasing the necessary HAL version for future Android releases, possibly shipped with an updated product partition, if the device requires some specific apps or functionality. So instead of full ROMs we can then just have "device support packages" for phones that aren't already fully fit for GSIs, or need updates for future GSI architectures.
In that case we can even have OTA updates for only the GSI, published by the specific OS maker (e.g. AOSP, LineageOS, /e/, GrapheneOS, CalyxOS and many more). Specific ROM developers then need only make sure that their device support package is up to snuff. When releasing a new OS update or version, the same OTA update can then be immmediately pushed to any device that runs it. Wouldn't that be great?
Project Treble has been quite a while since Android 8.0 and it makes Android more modular and flexible. Project Treble is a project that when you update or modify Android, the "/vendor" partition gets unmodified and that partition contains all OEM-specific applications, drivers and libraries. So it separates the Android kernel and anything Android from that partition. Because of this, can you flash any device with a GSI image? And solve the issue of users that they want MediaTek chipset drivers to be open sourced? And, I think the "/vendor" partition contains all the drivers so when they're developing a custom ROM or an update, they don't have to rework the partition and don't need the driver to be open sourced. Some people say that they installed GSIs successfully on Chinese phones that are running Android 8.1.