Hey guys
I've seen some Android Q GSI Images on the internet and I'm asking myself whether or not they would work with our axon (A2017G for me)?
Also, I have a general question about GSI on Axon: I've seen A GSI Roms, B GSI Roms and A/B GSI Roms.. what's the difference and more importantly, which one of those can I take for our axon? I have trebleized right now on latest LiquidRemix Pie
Thanks in advance,
Fred x
No harm in trying them out. We use x64 A only. No idea what the differences are
jojofreddy said:
Hey guys
I've seen some Android Q GSI Images on the internet and I'm asking myself whether or not they would work with our axon (A2017G for me)?
Also, I have a general question about GSI on Axon: I've seen A GSI Roms, B GSI Roms and A/B GSI Roms.. what's the difference and more importantly, which one of those can I take for our axon? I have trebleized right now on latest LiquidRemix Pie
Thanks in advance,
Fred x
Click to expand...
Click to collapse
There are only two actually: A-only and AB ROMs, this pertains to the seamless update scheme. A-only means you only have one system partition, while AB means that there are two system partitions. If your phone is AB then the ROM can download updates in the background and flash them to the unused partition, and after it's done you can reboot and the active partition will be switched to that one. you basically don't lose time updating.
When Treble for our phone was made by djkuz, it was unclear whether it would be possible to implement an A/B scheme. We wouldn't lose much storage space (maybe none at all) because our stock system partition is actually huge, so it could be shrunk considerably and duplicated (I think it's 6GB in size). Oki said he would look into it some time ago.
Just use ARM64 A-only images for the Axon
Try Q yourself and report back, there's no obvious reason why it wouldn't work. maybe it does, maybe it doesn't, the question is why you would even bother with a leaked release idk
Thank you for your in-depth answer!
I've seen that leaked GSI Rom but also read an article that some sort of DP or Beta will be officially released soon. Maybe I'll get into Rom building, maybe I'll just try and report back, but of course: being on the very bleeding edge
Cheers
I tried the only gsi rom I could find at the time of writing this. I had no luck with all the vendors we have here. Every time I reboot I get a promising android text on the screen as if its booting but soon after it goes to the fastboot menu. It did this for every vendor i used. Let me know other peoples luck with this.
That leaked GSI will never work in axon7 because it requires the device to be "system as root" .
I heard that there will be another version of the GSI but could not find it anywhere
king1990 said:
That leaked GSI will never work in axon7 because it requires the device to be "system as root" .
I heard that there will be another version of the GSI but could not find it anywhere
Click to expand...
Click to collapse
Could you briefly explain what this is?
stevecaboose said:
Could you briefly explain what this is?
Click to expand...
Click to collapse
System-as-root requires the ramdisk to be part of the system image, as in the AB images
It also loads your img file into root " { "/" folder } compared to the normal /system before.
So, if your kernel is not configured to read the ramdisk from system, then it would not be able to use a System-as-root image.
This is my understanding of it, correct me if I am wrong..
Related
Hi... I've been reading some news about Project Treble, and how it helps with the custom ROM development and software updates. But I want to ask. Is this working on phones like the Galaxy S5? Because it would be helpful considering the potential of this phone and how stable it is running on Nougat, and an Oreo update would be easier to Port.
Unfortunately, it's not. It is only compatible with phones that were initially shipped with Android 8.0.
camellirite said:
Unfortunately, it's not. It is only compatible with phones that were initially shipped with Android 8.0.
Click to expand...
Click to collapse
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Raynelfss said:
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Click to expand...
Click to collapse
After reading that article, you're right. I read a news article that said only phones shipped with 8.0 will be compatible with treble, my mistake.
Raynelfss said:
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Click to expand...
Click to collapse
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
djgigi94 said:
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
Click to expand...
Click to collapse
Ok... That's sad but ok. At least we are having Oreo anyway! Thanks for clarifying. Close thread please!
djgigi94 said:
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
Click to expand...
Click to collapse
I heard something about repartitioning, so it doesn't necessarily has to do with the Kernel, it's more like partitioning the device storage, with A/B partitions and stuff with vendor. I heard about a tool that can do that job called REPIT but I didn't do so much of a research of it.
Mi3 with snapdragon 800 on kernel v 3.10 got android p today so is there any hope for our s5s ,can it be ported to our phones like the redmi devs did
https://www.xda-developers.com/xiaomi-mi-3-xiaomi-mi-4-xiaomi-redmi-4x-android-pie-ports/
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Rhioun said:
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Click to expand...
Click to collapse
Looks nice. It would be great to try. If someone does try please post your experience here!
clockstoper said:
Mi3 with snapdragon 800 on kernel v 3.10 got android p today so is there any hope for our s5s ,can it be ported to our phones like the redmi devs did
https://www.xda-developers.com/xiaomi-mi-3-xiaomi-mi-4-xiaomi-redmi-4x-android-pie-ports/
Click to expand...
Click to collapse
Xiaomi have a terribke habbit of skipping android versions
Take the MiBox for example, from what i hear it never got an official 7.1.2 only leaked builds, they went from 6.0 to 8.0 and still face quite alot of bugs.
don't know if this is the right place for this but my old moto g 2014 with 3.4 kernel version just got android pi port its very smooth as per the reports, i have not installed it yet as i gave that phone to my mom. the phone runs on with a lowly snapdragon 400 chip and 1gb ram also its kernel version is 3.4 which is the same as our s5s so there might be a good chance android pie can be ported to our device
LINK
https://forum.xda-developers.com/moto-g-2014/development/titan-xperience-13-0-t3830834
did some further searching and found that lenovo zuk z1 also got Pie and it has SD 801 chip like our S5 so things looking quite promising tbh.....
LINK
https://forum.xda-developers.com/zuk-z1/orig-development/rom-pixel-experience-t3830494
clockstoper said:
don't know if this is the right place for this but my old moto g 2014 with 3.4 kernel version just got android pi port its very smooth as per the reports, i have not installed it yet as i gave that phone to my mom. the phone runs on with a lowly snapdragon 400 chip and 1gb ram also its kernel version is 3.4 which is the same as our s5s so there might be a good chance android pie can be ported to our device
LINK
https://forum.xda-developers.com/moto-g-2014/development/titan-xperience-13-0-t3830834
did some further searching and found that lenovo zuk z1 also got Pie and it has SD 801 chip like our S5 so things looking quite promising tbh.....
LINK
https://forum.xda-developers.com/zuk-z1/orig-development/rom-pixel-experience-t3830494
Click to expand...
Click to collapse
Anyone working on 9.0 for S5?
Official Aex devices will get 9.0 soon so yes I presume
The Galaxy S5 (klte) Kernel source on LOS has reportedly submitted comments about LineageOS 16. So we're having our pie soon.
LineageOS 16.0 teaser trailer by haggertk.
Rhioun said:
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Click to expand...
Click to collapse
I've heard from the official website of lineage os that they can turn a device into an A/B device, but I am not sure that whether the A/B device is the one that have 2 partitions, here it is (https://lineageos.org/Changelog-19/)
Frank Telescope said:
I've heard from the official website of lineage os that they can turn a device into an A/B device, but I am not sure that whether the A/B device is the one that have 2 partitions, here it is (https://lineageos.org/Changelog-19/)
Click to expand...
Click to collapse
Its not as simple as having a/b partitions , there is a kernel issue. a simple google search wich show you guys that there is a minimum kernel version required for treble which the s5 is far and i mean far behind that minimum requirement for treble.
I know this is like off-topic but there is now a project WIP going on for Samsung Galaxy S3 Neo, since it's using 3.4 kernel, we using S5 have luck to support treble. At least if someone willing to do it.
For the AB partition it might be impossible to do so.
Now with pascua28's Intelli-Kernel we're even closer to the dream. This guy has managed to do wonders with this device... The last thing that may happen is him being able to update our Kernel version. I don't know how the A/B partition things work, but from what I've heard it requires a higher Kernel version. The S5 runs 3.4 right now, but with @pascua28 work it may get a higher version soon.
Seeing as the first Android P Preview came out today, I'm wondering what (and how long) it would take to port it to Project Treble compatible devices.
Considering it is closed source, hard to say...
Though many people are on this.
phhusson said:
Considering it is closed source, hard to say...
Though many people are on this.
Click to expand...
Click to collapse
Nice to know!
When the source code is usually released? With the official release of the new Android version? In this case we should wait September 2018 for android P...
Can't we just flash GSI of already released pixel images?
espireso said:
Can't we just flash GSI of already released pixel images?
Click to expand...
Click to collapse
Released images are not GSI.
phhusson said:
Released images are not GSI.
Click to expand...
Click to collapse
I've learned it from the hard way. I extracted system.img out of newly released pixel.zip. It didn't boot ¯\_(ツ)_/¯
phhusson said:
Considering it is closed source, hard to say...
Though many people are on this.
Click to expand...
Click to collapse
does it always go open source only after all dp r released and stable is out?
zohaibahd said:
does it always go open source only after all dp r released and stable is out?
Click to expand...
Click to collapse
Yes
I too have a question. what if the manufacturer no longer updates their device to android P but the device is trebled supported on Android O. will the devs still can update the device to android P and so on?
Because on not trebled enabled devices still getting the latest OS thru custom roms and powered also by snapdragon SoC.
If we gotta wait until the source is released then what's the point of project treble compared to the usual custom rom developement process ? Correct me if I'm wrong, but isn't treble supposed to allow any device that got a vendor partition to boot any system partition regadless of the hardware used by the given device ?
If I'm not mistaken:
Treble allows for a generic system image to be used. The Android P developer previews are very likely not GSIs: they target a particular vendor configuration. (I wouldn't be surprised to find that they include an updated vendor partition to go along with them.)
A GSI doesn't target a particular device, it targets only the known services specified by a particular release of Android - an Android GSI could theoretically target any specified vendor interface, be it 8.0, 8.1, 9.0, or whatever future interface appears, or even multiple if someone wanted to put in the effort.
That doesn't get past the fact that there is no source for Android P yet, so a GSI can't really be built for it. And the vendor interface doesn't mean that any image will boot on any device - maybe one that depends on a strict subset of what's provided in the vendor interface on a particular device, but I wouldn't be able to grab a Pixel image and load it on a Galaxy S9 or Mate 10 Pro, or otherwise for any mix of devices. They all have dependencies on vendor-specific pieces in their vendor partition, at the very least; there's also /product, /oem, and /odm on the Mate 9, which is also depended upon by it's system.img. A GSI can't depend on the existence of those things, an OEM image can.
Maybe, with a fair bit of work, someone could rip apart the Pixel system image and make a GSI out of it, but P would probably be out before that made significant headway into making it a GSI.
irony_delerium said:
If I'm not mistaken:
Treble allows for a generic system image to be used. The Android P developer previews are very likely not GSIs: they target a particular vendor configuration. (I wouldn't be surprised to find that they include an updated vendor partition to go along with them.)
Click to expand...
Click to collapse
Yup, vendor partition has been updated.
And all your explanation is correct
Are GSIs for future versions of Android going to be released by Google or some other official entity? I thought this was the whole point of Project Treble :|
bemymonkey said:
Are GSIs for future versions of Android going to be released by Google or some other official entity? I thought this was the whole point of Project Treble :|
Click to expand...
Click to collapse
Google does make GSIs available to oems for testing (cts/vts) -- you can find evidence of this in the android-vts google group. I suppose they could make those publicly available, but if they are just stock aosp (with no google apps) they probably don't want to do that yet.
GSIs are a nice outcome of Treble, but that wasn't the main goal.
There is a really good podcast discussing what Treble is over at Android Developers Backstage (episode 75).
Yall need to seriously learn to chill out and enjoy what you have for a second, for real. The P preview is exactly what it is and has always been...a PREVIEW. Just like before when it was only available to nexus devices, it's the same for pixel. Plus, it's highly unstable and buggy as hell right now, and like most previews before this one, a lot of the features will be removed and more added in as time goes.
And to answer your question, ge-n, about what the difference is, it's not an instant invitation to see what Google releases as a preview. For us, our greatest advantage is if you're running a S9 per say (bloated to hell and grossified by their "Samsung experience" aka former TouchWiz) you can get a more stock version if you'd like.
It seems like there's been some movement on this...
How long will we get Stable Treble rom?
MAH35H said:
How long will we get Stable Treble rom?
Click to expand...
Click to collapse
As long as it takes you to develop one.
Will be interesting to see how the P beta program is distributed since it's a lot of treble devices that's getting it now!
Hey everyone I just wanted to ask what this trebel label means, my lack of understanding and research tells me its kinda like OTA but for a more secure way to push updates to devices? being someone who has been using my device fine, am just a bit wonderous wondering what this Trebel means for my favorite ROM, Recovery and Kernel
dalebaxter01 said:
Hey everyone I just wanted to ask what this trebel label means, my lack of understanding and research tells me its kinda like OTA but for a more secure way to push updates to devices? being someone who has been using my device fine, am just a bit wonderous wondering what this Trebel means for my favorite ROM, Recovery and Kernel
Click to expand...
Click to collapse
for the moment, forget about it
it's very green and brings more troubles than solutions or any gain in particular. We will see how things develop with time.
You can read more about treble in here
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
bornlivedie said:
for the moment, forget about it
it's very green and brings more troubles than solutions or any gain in particular. We will see how things develop with time.
You can read more about treble in here
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
Click to expand...
Click to collapse
Reading the article I'm still a bit confused by what all this would mean for the end user, I really enjoy AEX since I moved from RR and it seems like this is the "latest and greatest" type of situation, yeah okay launches are tough but when everything smoothed out what would this treble allow us all to do?
dalebaxter01 said:
Reading the article I'm still a bit confused by what all this would mean for the end user, I really enjoy AEX since I moved from RR and it seems like this is the "latest and greatest" type of situation, yeah okay launches are tough but when everything smoothed out what would this treble allow us all to do?
Click to expand...
Click to collapse
In reality, it means little to the end user. It could theoretically mean that ROMS require less development time, since all roms in theory are based on a single image.
You can kinda of see this with Google's OEM Partners. At Google I/O they listed a number of partner OEMs that were the first to use treble and for the most part they have released upgrades quicker and more reliably then there non-treble counter parts. This also can be extended to the modding community and in general means that porting roms and developing them on a new phone should be easier.
This is all part of a bigger push by Google to gain uniformity across devices. They started requiring security updates in there SLA's and now are pushing treble.
Trebles's All the benifits goes to vendor and stock rom users Rights. As we are Custom Rom users what are the benefits we getting from Treble Projects?
https://www.androidpolice.com/2018/05/13/project-treble-impact-android-custom-rom-community/
alwynjoshy said:
Trebles's All the benifits goes to vendor and stock rom users Rights. As we are Custom Rom users what are the benefits we getting from Treble Projects?
Click to expand...
Click to collapse
In the future you will be able to flash the custom treble image specific for your hardware, and then a GSI (Generic System Image) of your choice: RR, AEX, DU, Tesla, etc... that will be generic and able to be flashed in any hardware. That means that GSI development teams will be able to maintain their roms and apply the security fixes without the need to create custom rom versions for each hardware. So, finally we will have real OTA updates for custom ROMs. We all hope LineageOS 16 to have more or less this philosophy too. Well see it in September.
So, benefits for the user:
More ROMs to choose for your device (actually all of them!!!)
More frequent upgrades from custom GSI teams.
Oki said:
In the future you will be able to flash the custom treble image specific for your hardware, and then a GSI (Generic System Image) of your choice: RR, AEX, DU, Tesla, etc... that will be generic and able to be flashed in any hardware. That means that GSI development teams will be able to maintain their roms and apply the security fixes without the need to create custom rom versions for each hardware. So, finally we will have real OTA updates for custom ROMs. We all hope LineageOS 16 to have more or less this philosophy too. Well see it in September.
So, benefits for the user:
More ROMs to choose for your device (actually all of them!!!)
More frequent upgrades from custom GSI teams.
Click to expand...
Click to collapse
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
alwynjoshy said:
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
Click to expand...
Click to collapse
Once you have the Treble framework in place and have then flashed a device specific vendor image you can from that point on flash any GSI ROM. The thing to note is that so far NFound's Treble ROMs have included vendor image files in them which makes them device specific, you need to check for and remove any vendor image files from Treble ROMs created for other devices if you wish to try the ROM on a device other than what it was made for.
alwynjoshy said:
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
Click to expand...
Click to collapse
A treble rom is hardware specific, so you cant flash a treble rom designed for a different device. Only GSIs are compatible with multiple devices, and it is this way since the hardware dependant part is only in the treble rom.
Right now there are not fully treble roms available for the Axon7. The currently available roms labeled as treble are delivered and work as a usual full rom. The treble and system parts are still mixed up in those roms. It will take some time until we could enjoy a fully wotking treble rom in the Axon7.
Hello,
after testing out lots of ROM with Treble, I used some GSI and some of them worked more some less. In the Treble Development department I found a working AOSP 9 GSI. The ROM did work quite good and I would use it as a daily driver, but sadly the battery consumption was the greatest I ever had.
Maybe it is because of the ROM, but after all the vendor image should also be good. The only one we can use is from nfound and he left us...
So, what do you think? Will there every be a vendor image we can use for GSI?
yes.
Did you try this one: [AOSP 9.0] [EXPERIMENTAL] [2018-08-22] Phh-Treble ?
Cause this is the one, that gives me a SOT of about ~ 5h , which is ok for me right now ...
(altough, using AEX 5.8 SOT was 6-7h for me ...)
But it is in development ...
Mart Son said:
Hello,
after testing out lots of ROM with Treble, I used some GSI and some of them worked more some less. In the Treble Development department I found a working AOSP 9 GSI. The ROM did work quite good and I would use it as a daily driver, but sadly the battery consumption was the greatest I ever had.
Maybe it is because of the ROM, but after all the vendor image should also be good. The only one we can use is from nfound and he left us...
So, what do you think? Will there every be a vendor image we can use for GSI?
Click to expand...
Click to collapse
timmtomm8 said:
Did you try this one: [AOSP 9.0] [EXPERIMENTAL] [2018-08-22] Phh-Treble ?
Cause this is the one, that gives me a SOT of about ~ 5h , which is ok for me right now ...
(altough, using AEX 5.8 SOT was 6-7h for me ...)
But it is in development ...
Click to expand...
Click to collapse
There is another one based on this one, because this one gave me to much errors. Maybe the new GSI got better...
Did you flash some post GSI zips or did it work out of the box?
So at the moment we only have nfounds vendor image which boots up most gsi, but there are problems not solved. My great hope was that we will get a good vendor image with lineage, but it does not boot any gsi at the moment.
Nfounds vendor seems to be compatible with Oreo and pie. At the moment there is no sign for a pie only vendor image what would be great
Do all the GSIs available for the A7 get the irritating "vendor image mismatch" or "there's an internal problem with your device" on every bootup? I know it can be ignored but it's just annoying as hell. What causes this? I read that it has something to do with the boot/vendor signature/fingerprint not matching what the ROM expects to see. Is there a solution that makes these messages go away? I'm interested in trying a Treble Oreo GSI, but I need a daily driver that can be counted on, and so far I've had very little luck with getting GSIs to boot.
Which vendor image and boot image is correct for an A7 running a Treble ROM? The ones by Nfound? Or LineageOS? Or something else? It would be nice if ZTE would update our device to official Oreo and officially adopt Treble and a vendor partition. The A7 is classified by ZTE as an end of life/support device, with the Axon 9 due soon, the least they can do is bless us with this one last gift as a farewell.
I wouldnt mind running Pie, but I like using Xposed modules, so no go there. On the Oreo GSIs I've tried, exFAT MicroSD usually shows up as corrupt. This is unacceptable to me. And I must have my cache and data partitions as F2FS, for best performance. And a custom kernel.
Hi all, I'm wondering why we haven't any AOSP roms or ports from Pixel? I like one ui and all this staff but pure android seems to me be more exciting, even on our galaxies
You can use GSI roms on all Treble devices , use A/B scheme, even Android Q at your own risk , greater if you own a Exynos S10+
rangemogger said:
You can use GSI roms on all Treble devices , use A/B scheme, even Android Q at your own risk , greater if you own a Exynos S10+
Click to expand...
Click to collapse
Im okay even with Android Pie, but still we dint have even it (roms ports). Can you actually explain smth about gsi roms? As i understood we need to cimpile it with our kernel etc. ?
You can find many GSI here https://forum.xda-developers.com/project-treble/trebleenabled-device-development and If a custom recovery is required use this https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856 ...at the moment it scares me
rangemogger said:
You can find many GSI here https://forum.xda-developers.com/project-treble/trebleenabled-device-development and If a custom recovery is required use this https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856 ...at the moment it scares me
Click to expand...
Click to collapse
Yeah, i checked it(twrp) up, it's really strange and scares) on htc hero it was much easy xD and about gsi seems that it really can work, maybe someday will try, if anybody haven't do it yet
More development here https://forum.xda-developers.com/s10-plus/how-to/project-treble-s10-t3923946