Just finished long Chat with Huawei Rep, as to when I might expect OREO OTA update for my MHA-L29 USA model. Basically he said he had no idea since the update push has to come from Google and not Huawei, and insisted that Huawei has no control over the timing.
I expect carrier delays, but on an unlocked phone, is he right?
100% BS. Huawei does control the updates, They just don't know squat. This is my first time not having a carrier device and waiting on the update might suck. They might be waiting for the Mate 10 to drop, but who knows.
Thanks. That’s what I thought.
LOL, NO, but AFTER the Oreo update, once the phone has 8 along with project treble enable, THEN it will be up to google to
release patches and major updates, and Huawei to update the UI & apps they preinstall. It's suppose to separate the OS, from everything else, allowing the fragmentation problem to be eliminated, or, greatly reduced.
read this:
1.) https://www.androidauthority.com/project-treble-818225/
2.) https://www.xda-developers.com/why-current-oneplus-nokia-phones-wont-be-project-treble-certified/
as i know, the mate 9 isn’t directly supported from Google project treble. Yes, i know mate 9 has project treble "vendor" partition, but as i know, the updates for it are also fired by HUAWEI.
As i know too, the phone needs two vendor partitions for real supporting "treble". This is available only on new phones, which they come with OREO and which are not updated from Nougat. (see Google manufacture conditions for OREO - less specifications for update conditions!!!)
because:
Vendor "A" (life) is the partition which runs if android is starting,
Vendor "B" (update) is the partition to download the Google updated vendor partition to!
After reboot, vendor "B" is checked and than activated to be sure, that there is no problem.
So, updates can be downloaded AND installed during the phone and android is running from partition "A".
Mate 9 has only 1x vendor partition, so we have to use the Huawei update installer routine for upgrading it!
This is the reason, the treble updates for mate 9 are fired from Huawei and NOT from Google!
you can use following app to check your partitions and treble usability
->https://play.google.com/store/apps/details?id=com.kevintresuelo.treble&hl=us
See 2 of my signature Hit me, if i’m going wrong!
Edit: add a link and updated the txt.
Thanks ice tea for detailed explanation.
cash2387 said:
100% BS. Huawei does control the updates, They just don't know squat. This is my first time not having a carrier device and waiting on the update might suck. They might be waiting for the Mate 10 to drop, but who knows.
Click to expand...
Click to collapse
Man thats cruel updates shouldnt be based on their marketing stuffs but it should be on their after sales service
Fed up
So my 636 is more approaching 3 months out of date for security updates.
This is not good enough.
FF shows 2 updates on the last month, once at least a month ago, that are not authorised for my phone.
Why are these even published if I can't load them.
3 MONTHS OUT OF DATE HUAWEI.
I AM TOTALLY OVER THIS LACK OF SERVICE
Mate 9 update using VPN
I am from Oman ,I recived my mate 9 oreo update last week when i use windsctibe VPN and try to check for update,pop cane as update available , when I connect vpn I got a us ip address ,once after download stated I disconnect VPN and download completed using normal internet
A/B partitions
Icetea said:
read this:
1.) https://www.androidauthority.com/project-treble-818225/
2.) https://www.xda-developers.com/why-current-oneplus-nokia-phones-wont-be-project-treble-certified/
as i know, the mate 9 isn’t directly supported from Google project treble. Yes, i know mate 9 has project treble "vendor" partition, but as i know, the updates for it are also fired by HUAWEI.
As i know too, the phone needs two vendor partitions for real supporting "treble". This is available only on new phones, which they come with OREO and which are not updated from Nougat. (see Google manufacture conditions for OREO - less specifications for update conditions!!!)
because:
Vendor "A" (life) is the partition which runs if android is starting,
Vendor "B" (update) is the partition to download the Google updated vendor partition to!
After reboot, vendor "B" is checked and than activated to be sure, that there is no problem.
So, updates can be downloaded AND installed during the phone and android is running from partition "A".
Mate 9 has only 1x vendor partition, so we have to use the Huawei update installer routine for upgrading it!
This is the reason, the treble updates for mate 9 are fired from Huawei and NOT from Google!
you can use following app to check your partitions and treble usability
->https://play.google.com/store/apps/details?id=com.kevintresuelo.treble&hl=us
See 2 of my signature Hit me, if i’m going wrong!
Edit: add a link and updated the txt.
Click to expand...
Click to collapse
Wrong, A/B partitions are used for "seamless" upgrades, that has absolutely nothing to do with project treble from Google. The mate 9 under Oreo is "fully" treble complaint. The vendor partition is always going to be upgraded from the vendor as this is where most of the closed source drivers and binaries live the Android system itself is just separate now from all that because of project treble, but don't expect that Google will be providing updates to any phones other than their own due to all the bloatware and ui stuff.
@revjamescarver
as i wrote, "as i know"!
And how (or where) do you get your informations???
Information
Icetea said:
@revjamescarver
as i wrote, "as i know"!
And how (or where) do you get your informations???
Click to expand...
Click to collapse
As far as treble requirements, straight from Google. Google does not "require" vendors to implement the a/b partitioning scheme, regarding the a/b partitioning scheme, straight from the vendors that implement it. There is tons of documentation on this and I'm not going to waste my time explaining it to you, go read it all yourself
it looks like i had found my next candidate for my personal ignore list now.
btw: answers like yours are not very helpful to prevent spreading wrong facts!
and again: i have written "as i know" and not "you should know".
anyway, i will spend my time now also to more rewarding themes.
...waste time?
Unhelpful.
Related
Wileyfox has just posted the following statement on their Facebook page:
Wileyfox said:
In light of the recent news from Cyanogen, every Wileyfox user's experience will remain unchanged - hooray!
This was expected and we are confident with the smooth transition planned in an upcoming over-the-air update for the entire Wileyfox product range that will migrate away from Cyanogen’s refocus strategy, and on to a purer Android experience – enhanced.
We strongly recommend that all current and future users accept the upcoming update request to ensure they are on-board for the future. This will include the ability to maintain the same experience as before and the added ability to partake in updates and upgrades to the software in the future.
We will continue to push this update to your device, and for new users we again recommend they download and install this update upon purchase.
We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect. Once this transition is implemented and users accept this upcoming update, our first order of business is to focus on delivering Android Nougat 7.0 across the portfolio beginning as early as February, and the entire portfolio by end of Q1 2017.
We value our customers above anything else, and therefore will now take full direct control on all such upgrades to ensure all devices, not just the flagship’s, will get these regular updates.
What this means is we at Wileyfox are still committed to continuous security and Android updates for the entire user base (old, current, and new), a bloatware free OS, deeply integrated value added services, and a promise to maintain a no bull**** attitude to the Wileyfox user experience.
We hope you had an amazing Wileyfoxmas. We look forward to 2017 and beyond, in a Wileyfox world of no bull****!
Instructions to download and install your latest update:
1. Receive notification about available update (see image attached).
2. Press download to update.
3. A notification will pop up stating update is ready to install. Select install.
Click to expand...
Click to collapse
(There was no image attached)
Source: https://www.facebook.com/officialwi...828.1481273535517300/1708271872817464/?type=3
Has anyone else received the OTA update mentioned? I still haven't got the notification.
person123321 said:
Has anyone else received the OTA update mentioned? I still haven't got the notification.
Click to expand...
Click to collapse
Yes, but I can not install it, because I rooted my device...
https://forum.xda-developers.com/showpost.php?p=70330176&postcount=6
Has anyone captured the OTA link?
person123321 said:
Has anyone captured the OTA link?
Click to expand...
Click to collapse
Anyone?
it's still not on https://cyngn.com/support
NotATechnician said:
Anyone?
it's still not on https://cyngn.com/support
Click to expand...
Click to collapse
It won't be because it isn't Cyanogen OS anymore.
person123321 said:
It won't be because it isn't Cyanogen OS anymore.
Click to expand...
Click to collapse
Can you confirm it? If possible, attach a picture of Settings > About device screen, that'd be very helpful. My Swift 2+ arrives Jan 6th, until them I'm going blind on OS related things
linuxct said:
Can you confirm it? If possible, attach a picture of Settings > About device screen, that'd be very helpful. My Swift 2+ arrives Jan 6th, until them I'm going blind on OS related things
Click to expand...
Click to collapse
I can't confirm with a screenshot because although I have my phone I am still waiting for the update notification. I know that the new software will not be Cyanogen OS because in their official statement Wileyfox say:
"This was expected and we are confident with the smooth transition planned in an upcoming over-the-air update for the entire Wileyfox product range that will migrate away from Cyanogen’s refocus strategy, and on to a purer Android experience – enhanced."
person123321 said:
It won't be because it isn't Cyanogen OS anymore.
Click to expand...
Click to collapse
Okay. But there's still nothing about this move on the wileyfox website, https://www.wileyfox.com/support or https://www.wileyfox.com/faqs
I have a rooted swift trying to push an OTA update - so either I need the latest update they are pushing as a zip (safest) or jump to cyanogenmod nightlies (which I'd prefer not to do) since TB currently can't "write" to the SD..
Does anyone have the latest OTA as a zip?
yep
NotATechnician said:
Does anyone have the latest OTA as a zip?
Click to expand...
Click to collapse
I think it's what you looking for. Found in the directory Android/data/com.cyngn.fota/cache/
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
h t t p : / / d l . f r e e . f r / q i f 6 f S k e 8
cm-marmite-a1478a0ee9-to-7aa1c7975e-signed.zip
bahjesaispas said:
I think it's what you looking for. Found in the directory Android/data/com.cyngn.fota/cache/
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
h t t p : / / d l . f r e e . f r / q i f 6 f S k e 8
cm-marmite-a1478a0ee9-to-7aa1c7975e-signed.zip
Click to expand...
Click to collapse
Thanks!!
Will try this.
Hi,
Can we expect to have firmware source code for this device?
Thank you
I wrote a mail to Wileyfox Support to get some information about working together with the community, this is the response:
Hello XXX,
Thank you for your response.
We do not supply drivers for our handsets, these can be obtained by doing a simple search on most search engines online.
Kind Regards
XXX
Click to expand...
Click to collapse
And yes, there are some pieces of source code available (don't blame me if I'm wrong, don't got enough time to take a deeper look):
i.e. https://android.googlesource.com/ke..._r0.3/arch/arm/boot/dts/qcom/msm8937-mtp.dtsi
NotATechnician said:
Thanks!!
Will try this.
Click to expand...
Click to collapse
Actually, this is for Marmite and I need for crackling..
Anyone can help?
On FB i get a message from Wileyfox NL, that the update to 7.1.1. is coming for the Swift-2 serie in 2 weeks. After that the Swift-1 and the Storm in 4 or 5 weeks en at last the Spark in the end of april.
*Wileyfox news message* Just received from London about the developments of our upgrade to Android 7.1.1 Nougat. As it looks now, we will first upgrade the entire Swift 2 series within two weeks. Within 4-5 weeks following the upgrades for the Swift and the Storm. Spark & X + will receive the upgrade by the end of April.
All upgrades will be offered through the WiFi network. Make sure the battery is charged at least 50%, otherwise will be unable to start the upgrade. Important dates remain neatly on the devices, though we recommend to always have a backup of your important data.
All Wiley Features of Cyanogen OS will continue to exist in this upgrade.
If there are any questions please let us know. Good day!
Regards,
Wileyfox Netherlands
I'm especially awaiting the improved Doze.
How long do i have tot wait tot get the new update?
VincentS84 said:
How long do i have tot wait tot get the new update?
Click to expand...
Click to collapse
Damn, forgot my crystal ball
VincentS84 said:
How long do i have tot wait tot get the new update?
Click to expand...
Click to collapse
Well it was meant to come out today but wileyfox said on Facebook that it's been delayed so you could be waiting a while :/
In the last 2 days my Swift 2 rebooted by itself 3 times.
Then this morning I had the message to upgrade to 7.1.1.
I accepted, but I had not enough storage available (1.4GB the download...).
I made a bit of cleanup, during which it rebooted again, and now I don't have the option to upgrade: if I check, it says I'm upgraded (version us still 6.0.1)
Anyone has similar experience?
How can I perform the upgrade?
Thanks:
In this Article by Mishaal Rahman , we can understand why OnePlus and Nokia doesn't have treble support to their devices.
I open this thread to discuss about your opinions about how danger can be to create vendor partition outside system partition.
Tell us your opinion and how we can do it safely!
/vendor
FSadino said:
In this Article by Mishaal Rahman , we can understand why OnePlus and Nokia doesn't have treble support to their devices.
I open this thread to discuss about your opinions about how danger can be to create vendor partition outside system partition.
Tell us your opinion and how we can do it safely!
Click to expand...
Click to collapse
That partition is not accessible by the user or anyone else unless the phone is rooted, and it's no more dangerous than having the drivers and libraries in the system partition, OnePlus, as nothing more than a rebranded oppo, as well as Nokia, just don't want to put in the effort, Google has made it perfectly clear that treble is not optional, it is mandatory for devices shipping with Oreo and later, Nokia and OnePlus can do what they want with existing phones, but even they have no real choice that to support treble, unless of course that want to be stuck on phones shipping with nougat and maybe upgrading to Oreo, both of them will see the Android world passing them by and their implementations of Android will become more and more fragmented. Each to their own I suppose
Repartitioning a phone carries a certain risk, especially if it is done via OTA Update, but there are ways to do it and make it relatively safe...if you are willing to put in the work. I think that's the main point.
To me, it's much more interesting to see right now, how OEMs actually use Treble. They no longer have the excuses they used to, so someone like Sony should now be able to provide the Update to Android 8.1 within Days instead of Months...but will they actually do it?
The reasoning behind OnePlus deliberately not using Oreo on the 5T and not preplanning the extra partition...well, that tells it's own story. Not really that unexpected. Nokia though...I would have expected more from them, since they started with big promises about Stock Android and fast Updates, but so far very little has materialised...
I really think people are blowing this up far more then it needs to be. In the Google article it stated that even after the treble code is sent, the oems will still have to make their changes. So as far as I can see this will only matter to oems.
I expect to see many devices with day one 8.0 updates for a while.
Well, like I said, this will be the benchmark for Updates in the future. Since a new OS version can now boot on a phone without any big changes to the UI, Drivers or Apps, it SHOULD be far quicker. How much quicker will be interesting to see. Custom ROMs already show how fast the process can be...so... interesting times!
CommanderROR said:
Well, like I said, this will be the benchmark for Updates in the future. Since a new OS version can now boot on a phone without any big changes to the UI, Drivers or Apps, it SHOULD be far quicker. How much quicker will be interesting to see. Custom ROMs already show how fast the process can be...so... interesting times!
Click to expand...
Click to collapse
Yeah if you don't want any of the main features from the oem. Like Samsung cameras on aosp. Things like that.
As for faster updates. I doubt it. As now the oems will, have to do twice the work. Instead of adding their code to the stock frameworks. Now they will have to make completely new framework files to over write the default. Downloads will be a lot bigger now as well.
Hmm... that's not the way I understand Treble!
From what I've read, the OEM can basically exchange the OS Version without really touching much of their OEM UI...
The fact that Custom Roms are limited is mostly due to the fact, that devs don't have access to the OEM Sources, so they can only compile AOSP versions of Android...
CommanderROR said:
Hmm... that's not the way I understand Treble!
From what I've read, the OEM can basically exchange the OS Version without really touching much of their OEM UI...
The fact that Custom Roms are limited is mostly due to the fact, that devs don't have access to the OEM Sources, so they can only compile AOSP versions of Android...
Click to expand...
Click to collapse
And see that is why XDA articles are crap. The way OEMS roms have worked for years is that they replace and/or recode all of googles files. Now they will have to make even more. To over write them.
That is what you will get. Either AOSP or OEM. The aosp will not have access to the OEM code. Nor will OEM push their code to aosp for google to make things work right. This comes from the fact that OEMS dont write the drivers and code for alot of the hardware. They get that from others.
Just checked, my us997 LG G6 has a symlink for 'vendor', it points to 'system/vendor'... so no separate partition on the G6 either... I was hoping! alas.
Not unexpected...the G6 launched way before Treble was announced and hasn't been Updated to Oreo yet...
They should build a tool and require a wired connection to a pc to repartition and fallback just in case.
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Clever. Sell that idea to Oneplus and Nokia please...?
CommanderROR said:
Clever. Sell that idea to Oneplus and Nokia please...
Click to expand...
Click to collapse
I might be a good coder, but definitely not a good seller
phhusson said:
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Click to expand...
Click to collapse
Did you already tried this? I mean, I'm not developer and I can't understand the pros/cons about your patch but is extremely interesting!
@franciscofranco @eng.stk @Sultanxda @flar2 can you guys share your opinion about this? Thanks in advance
FSadino said:
Did you already tried this? I mean, I'm not developer and I can't understand the pros/cons about your patch but is extremely interesting!
Click to expand...
Click to collapse
Yup, actually my main testing device for my Treble ROM is a device using this.
Pros:
- doesn't need to repartition
- Easy to integrate
Cons are only for community rom devs:
- /system and /vendor are in read-only, even if dm-verity is disabled, the only way
- some TWRP change is required
- fastboot flashing will require to launch a s cript to merge system.img and vendor.img and flash both at the same time
Frankly, I'd guess OEMs had better to repartition. If you don't move partitions, only split system into system/vendor, and write the script with error-checking in mind, I really can't see how you would brick your device.
But this patch makes it possible to answer to OEMs saying they can't because of missing vendor partition
It will be interesting to see what happens, if a Device with strong XDA Community support like the OnePlus lineup can be "Trebleized" by the community and then supported more easily without help from the OEM that made it.
Following up here, very curious about where this is going.
Not a developer, but willing to test, my device is OP3T.
In light of a dev getting Treble support on the Redmi Note 4X, is it possible to get it on our devices too? I'm willing to test.
phhusson said:
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Click to expand...
Click to collapse
Does the Zenfone 4 use your patch actually? (didn't checked if sources are available yet)
I read a while back that first devices (or just one device?) is now project treble ready without vendor partition, not knowing you might have anything to do with it...
For reference:
https://www.androidpolice.com/2017/11/26/phones-updated-support-project-treble-continuously-updated/
Sent from my OnePlus 3T using XDA Labs
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!
So, from searching this forum it seems like people think the V20 doesn't support Treble. I've seen articles that state with Oreo it will. I am running the unofficial Los 15.1 build and downloaded the app that checks for Treble compatibility and it states my phone is treble ready though I don't have the A/B setup. Now looking at treble project builds there are many that state they are a only as well as a/b.
So, is the rooted v20 treble ready with Oreo firmware?
Also, when I do this cmd in terminal - getprop ro.treble.enabled, it returns true.
Is it possible, yes, will they do it, probably not.
You can set the boot LUN now, without Oreo, and force the phone to boot from the *bak partitions (xblbax, abootbak, lafbak, recoverybak, etc)
Notice there is one important partition missing .. bootbak. We don't have it. That would require the phone to be repartitioned, and I just don't see LG risking that.
It is hard enough to repartition a UFS NAND via a firehose, it would be insane to try it via an OTA update.
-- Brian
Thanks Brian. Guessing these treble check apps should have a big warning plastered on them for the less savvy in the android intricacies such as myself. Glad I posted before going ham on trying to install Treble roms
Actually we have xbl2 and xbl2bak that could be repurposed. They aren't actually used as part of the boot process (they are identical copies of xbl and xblbak).
However, that still leaves system. In order to have a systembak, they would have to shrink userdata which is currently 52.2G, so plenty of room, but that is VERY risky.
Again, though, this is very doable. Heck, even if they don't do it, the AOSP builds for the V20 could support it with the tweaks stated above.
-- Brian
runningnak3d said:
Actually we have xbl2 and xbl2bak that could be repurposed. They aren't actually used as part of the boot process (they are identical copies of xbl and xblbak).
However, that still leaves system. In order to have a systembak, they would have to shrink userdata which is currently 52.2G, so plenty of room, but that is VERY risky.
Again, though, this is very doable. Heck, even if they don't do it, the AOSP builds for the V20 could support it with the tweaks stated above.
-- Brian
Click to expand...
Click to collapse
So, does the V30 have all these partitions set up? It's my understanding that the V30 is definitely going to be treble supported so I'm curious if it already has these partitions in place or needs modifying (in which case I imagine some crafty bastard will be able to replicate the process).
Or along those lines, several of the supported current phones I don't believe shipped with Oreo so they had to undergo the reformatting process, I wonder if there's anything to glean from them. I'll have to see if I can wrap my head around this whole deal.
Also, is this what we are lacking? https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Wow, I should really drink at least 3 cups of coffee before posting.
What I was referring to was A/B system updates which I swore had a code name, but damn if I can find it now.
Anyway, yes, even Project Treble will still require repartitioning since we don't have a vendor partition (vendor is on system). Much easier to implement than A/B system updates, but I still don't think LG will do it.
We will just have to wait and see...
EDIT: good read on A/B system updates: https://source.android.com/devices/tech/ota/ab/ab_implement
-- Brian
LG may not add /vendor partition, but if you put the pieces together from some of the posts around the dev section theres work being done to add one in Lineage, though it hasnt been done yet.
runningnak3d said:
Anyway, yes, even Project Treble will still require repartitioning since we don't have a vendor partition (vendor is on system).
Click to expand...
Click to collapse
Just FWIW, Treble doesn't necessarily require repartitioning.
PhantomGamers said:
Just FWIW, Treble doesn't necessarily require repartitioning.
Click to expand...
Click to collapse
i've been following project treble for sometimes and there are lot of misunderstanding
1. having custom oreo roms doesnt mean you had treble support. it is true most treble phone coming with oreo by default
2. even if your phone has official oreo rom doesnt mean it support treble project ( like samsung S8 or note 8)
3. there are some devices with unnoficial treble support like oneplus devices but it still in development and as brian said we need repartition and needs lot of work. and your link above still on experiment.
i didnt say its impossible, but its far away for our devices not to mention we still need to dealing with ARB and lafs. just hope more devs joining on LG development and not rush them ( i saw lot of people doing that on brian's thread) . remember they did it for free while risking their devices on the process.
Loopback mounting is by far the safest method. You mess that up, and you phone just doesn't load the OS. You try and shrink a partition, and you mess up, and you could be toast. It isn't just shrinking, you also have to add a new entry to the GPT .. that is dangerous.
Also, if you do succeed, you will never be able to flash a stock ROM unless you put things back. For one thing stock system would no longer fit
-- Brian
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
Has someone tried this? Sorta feels like he just took that article and just keeps adding phone models to it without trying it.
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
stcr1 said:
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
Click to expand...
Click to collapse
you can't just grab random drivers (that's what these HALs are) and hope they fit your device. x86cpu got close to a working treble implementation, but LG's camera drivers wern't compatible and has since put off that project and is working more on lineage 16 (pie). IF LG ever does release a stock version of pie, perhaps a newer version of the camera driver might be compatible, but perhaps not.
Phoenix591 said:
you can't just grab random drivers (that's what these HALs are) and hope they fit your device. x86cpu got close to a working treble implementation, but LG's camera drivers wern't compatible and has since put off that project and is working more on lineage 16 (pie). IF LG ever does release a stock version of pie, perhaps a newer version of the camera driver might be compatible, but perhaps not.
Click to expand...
Click to collapse
OK. Got it. So it seems that LG is going to give the V20 a Pie update. There are announcements to that affect. Assuming LG follows through, the Pie update may or may not be Treble compatible. With Oreo, device OEMs were required (??) to be Treble compatible on new Oreo devices, but could provide non-Treble Oreo updates to existing devices. That's what I gathered. So with Pie, what you are saying is that it will be the same: OEMs are not necessarily going to package Treble support in Pie updates to existing devices. But if LG does provide a Pie update, AND if the update is Treble compatible, then things will be easy-peasy for ROM developers to port their wares to it because drivers -- like the troublesome camera driver -- will be abstracted and basically have the same abstraction across all Android devices. Is that right?
stcr1 said:
OK. Got it. So it seems that LG is going to give the V20 a Pie update. There are announcements to that affect. Assuming LG follows through, the Pie update may or may not be Treble compatible. With Oreo, device OEMs were required (??) to be Treble compatible on new Oreo devices, but could provide non-Treble Oreo updates to existing devices. That's what I gathered. So with Pie, what you are saying is that it will be the same: OEMs are not necessarily going to package Treble support in Pie updates to existing devices. But if LG does provide a Pie update, AND if the update is Treble compatible, then things will be easy-peasy for ROM developers to port their wares to it because drivers -- like the troublesome camera driver -- will be abstracted and basically have the same abstraction across all Android devices. Is that right?
Click to expand...
Click to collapse
LG released oreo without treble support, LG releasing a pie update for the V20 is doubtful at best and if they do it more than likely it won't have treble support either
Sent from my LG-H910 using XDA Labs
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
warwagon19792 said:
Has someone tried this? Sorta feels like he just took that article and just keeps adding phone models to it without trying it.
Click to expand...
Click to collapse
stcr1 said:
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
Click to expand...
Click to collapse
I did know of someone who tried this. And it seemed to work but it never passed from the booting animation screen. He tried to go back and the phone was rendered useless. (and he was a developer). SOOOOO no.... I don't recommend attempting this.
I got a new OP5 (had a OP3). I unlocked the bootloader, installed TWRP, and was looking to root and load LOS 15.1.
I did that, sort of, but then got spooked because every zip I flashed, I got this error:
failed to mount partition '/vendor' (invalid argument)
I flashed back to stock and all seemed well, though I also got stock recovery. When I installed TWRP again and then a custom kernel, I got the same error. Then I couldn't boot with the custom kernel and now I'm headed back to stock.
When I go in to Mount in TWRP, it won't let me select vendor to be mounted.
What's causing that and how do I fix it?
TWRP is just complaining about the missing 'vendor' partition, that only exists in Project Treble ROMs. Therefore, there's nothing to fix. Ignore the error.
https://forum.xda-developers.com/showpost.php?p=76621704&postcount=285
That one has been modified to remove the warning.
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Elleby said:
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Click to expand...
Click to collapse
That's true, but till then, this lone programmer (me ) will patch any updated TWRP that is released so that the the error isn't displayed if you aren't on a treble-compatible ROM.
Thanks all. That makes sense, and also explains why I didn't see it previously with TWRP for OP3.
Elleby said:
As already wroted, it's just a "cosmetic" bug. Imho it's not a good thing to fix it: every time TRWP release a new patch of their software, you have to wait a lone programmer that modifies the new patch in order to remove this message error.
Consider also this: with next release of Android, named P for now, that is already available as beta for Oneplus 6, the project Treble will be mandatory and not optional as for Android Oreo. There are already some rumors that Oneplus 5/5T will receive update to Android P, and the problem with vendor partition will be gone forever.
Click to expand...
Click to collapse
Source of this, please?
Astur_Torque said:
Source of this, please?
Click to expand...
Click to collapse
Check out this article, point 3 under "Will my device benefit from Project Treble".
Official statement on Oneplus forum. That part in particular:
Over 135,000 of our users signed up to review the OnePlus 6 early via The Lab. With the OnePlus 6 device in their hands, they'll be among the first in our community to be able to download the Android P Build. (OnePlus 5/5T friends, we'll have something nice lined up for you later this year.)
Click to expand...
Click to collapse
For me that means that they will release Android P on Oneplus5/5T after the initial release for Oneplus 6.
And Project Treble mandatory, link on discussion on reddit. That part in particular:
Devices launching with Android O will come Treble-enabled out of the box.
Click to expand...
Click to collapse
shadowstep said:
Check out this article, point 3 under "Will my device benefit from Project Treble".
Click to expand...
Click to collapse
But there does not mention anything about that is compulsory Treble on Android P (on preoreo phones), just it says its compulsory on Oreo recent-released devices
Astur_Torque said:
But there does not mention anything about that is compulsory Treble on Android P (on preoreo phones), just it says its compulsory on Oreo recent-released devices
Click to expand...
Click to collapse
It's true for Android Oreo and above. Treble is the reason why there are Android P Betas available for non-Google devices. Also, here's an excerpt from this article: "Going forward, updates to phones will become far more common, as all devices that launch with Android Oreo or newer are required to implement Treble."
shadowstep said:
It's true for Android Oreo and above. Treble is the reason why there are Android P Betas available for non-Google devices. Also, here's an excerpt from this article: "Going forward, updates to phones will become far more common, as all devices that launch with Android Oreo or newer are required to implement Treble."
Click to expand...
Click to collapse
Yes I agree with you with that... However... "All devices launched with oreo"... One plus 5 is not one of those... Just 6 and incoming..
Enviado desde mi Oneplus 5 mediante Tapatalk
Astur_Torque said:
Yes I agree with you with that... However... "All devices launched with oreo"... One plus 5 is not one of those... Just 6 and incoming..
Click to expand...
Click to collapse
You're spot on. I never said that OP5/5T will definitely get Treble. Also, I'm not the OP, if you haven't realized that yet. OnePlus got away with having to mandatorily provide Treble to the OP5/5T by launching the device with Nougat (but making it upgradeable to Oreo) -- meaning that these devices don't come under the category of devices that launch with Android Oreo, thereby putting OnePlus under no compulsion to provide Treble to these devices. However, there are rumours that have been floating around that even though there is no compulsion, OnePlus is considering providing Treble to these devices.