Treble implications for OS updates - Google Pixel Questions & Answers

Does it mean it will be easy to compile AOSP, so that the original Pixel can get essentially stock OS updates for years, and get them quickly, eliminating an advantage of the Pixel 2? Pixel 2 is to get three years of OS updates, compared to only one more year of official OS updates for the Pixel.
Will it really make OS development much easier?

foosion said:
Does it mean it will be easy to compile AOSP, so that the original Pixel can get essentially stock OS updates for years, and get them quickly, eliminating an advantage of the Pixel 2? Pixel 2 is to get three years of OS updates, compared to only one more year of official OS updates for the Pixel.
Will it really make OS development much easier?
Click to expand...
Click to collapse
There's no reason to believe the Pixel 2 firmware will have any compatibility with pixel 1

sd_shadow said:
There's no reason to believe the Pixel 2 firmware will have any compatibility with pixel 1
Click to expand...
Click to collapse
I had thought the idea of Treble was to present a standard interface between hardware and the OS, to separate the device-specific, lower-level software written in large part by the silicon manufacturers from the OS.
"Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work." https://www.xda-developers.com/project-treble-custom-rom-development/
Doesn't that mean someone can just compile the latest AOSP build and it will run on a Treble Pixel 1? Don't the current Nexus and Pixel phones essentially run AOSP, but have to be modified to work with the specific hardware, modifications that won't be necessary with Treble?
Or is this the issue: "You won’t be able to boot up flawlessly-working generic Android 9.0 builds on your Treble device just yet, though – device trees and kernels will still require being worked on."

foosion said:
I had thought the idea of Treble was to present a standard interface between hardware and the OS, to separate the device-specific, lower-level software written in large part by the silicon manufacturers from the OS.
Click to expand...
Click to collapse
that's the general idea, but afaict, it's not there yet and not for the pixel 1
foosion said:
"Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work." https://www.xda-developers.com/project-treble-custom-rom-development/
Click to expand...
Click to collapse
I didn't read your link, but I did watch the linaro talk from a week or two ago about... The vendor test suite (VTS), is to be used to have aosp be bootable on XYZ SOC, as the idea is to keep all of the vendor blobs outside of aosp / the core of android.... in practice though, even with the pixel, it still isn't 100% like that. ROMs like LOS are still pulling vendor blobs and baking them into their build system....
foosion said:
Doesn't that mean someone can just compile the latest AOSP build and it will run on a Treble Pixel 1? Don't the current Nexus and Pixel phones essentially run AOSP, but have to be modified to work with the specific hardware, modifications that won't be necessary with Treble?
Or is this the issue: "You won’t be able to boot up flawlessly-working generic Android 9.0 builds on your Treble device just yet, though – device trees and kernels will still require being worked on."
Click to expand...
Click to collapse
who knows about android 9.0, but it doesn't work for Oreo and the pixel 1... Nexus and Pixel run aosp with a bunch of Google's tweaks from their own internal android tree + all of the google services and apps... I'm sure there is a reasonably sized set of patches / Delta between aosp and Google's own builds.... but obviously, google provides a very 'vanilla' version of android.

foosion said:
Pixel 2 is to get three years of OS updates, compared to only one more year of official OS updates for the Pixel.
Click to expand...
Click to collapse
Independent of the discussion here regarding Treble, the original Pixel is getting updates for the same duration (from release) as the Pixel 2.
Both devices will get 2 years of Android version updates, and another year of security updates.
https://support.google.com/pixelphone/answer/4457705
The original Pixel will get android version updates through October 2018, and security updates through October 2019. The Pixel 2 will get updates for one year longer simply because it was released one year later, but no additional promises have been made for the Pixel 2.

Fairly sure Pixel 2 is getting 3 years of OS updates which is probably a result of Treble. Google want to show off how easy updates are now so it wouldn't be good if they drop support after 2 years still.
As for the first gen Pixel, I don't believe our devices support Treble.
Edit: sorry, looks like first gen Pixel does support Treble. My bad.

surrealjam said:
Fairly sure Pixel 2 is getting 3 years of OS updates which is probably a result of Treble. Google want to show off how easy updates are now so it wouldn't be good if they drop support after 2 years still.
Click to expand...
Click to collapse
I'd love it if Google extended the support period for their devices. And I could be wrong, but I'm basing stuff from this page:
https://store.google.com/us/product/pixel_2_specs
Under the "Safe and Secure" section, they state "Security updates for up to 3 years".
Farther down on the page, in the tech specs section, they say:
"Minimum 3 years of OS and security updates" and "Pixel’s software and security updates for three years. See website for details." And the website reference is the FAQ page that I linked to above. That page states:
"Pixel phones get Android version updates for at least 2 years from when the device first became available on the Google Store. After 2 years, we can't guarantee more updates." and "Pixel phones get security updates for at least 3 years from when the device first became available on the Google Store, or at least 18 months from when the Google Store last sold the device, whichever is longer. After that, we can't guarantee more updates."
Again, it'd be great to see these phones official support period be extended. But from what I can tell, Google is sticking to 2 years of OS updates + another 1 year of security updates. Even with Treble support.

jss2 said:
I'd love it if Google extended the support period for their devices. And I could be wrong, but I'm basing stuff from this page:
https://store.google.com/us/product/pixel_2_specs
Under the "Safe and Secure" section, they state "Security updates for up to 3 years".
Farther down on the page, in the tech specs section, they say:
"Minimum 3 years of OS and security updates" and "Pixel’s software and security updates for three years. See website for details." And the website reference is the FAQ page that I linked to above. That page states:
"Pixel phones get Android version updates for at least 2 years from when the device first became available on the Google Store. After 2 years, we can't guarantee more updates." and "Pixel phones get security updates for at least 3 years from when the device first became available on the Google Store, or at least 18 months from when the Google Store last sold the device, whichever is longer. After that, we can't guarantee more updates."
Again, it'd be great to see these phones official support period be extended. But from what I can tell, Google is sticking to 2 years of OS updates + another 1 year of security updates. Even with Treble support.
Click to expand...
Click to collapse
I take your point. I was hoping they just hadn't updated the support page as it doesn't list the Pixel 2 yet. But you may be right.... the tech specs section is badly worded and may be misleading.

Related

Project Treble and update support

I don't expect answers this very second and hope HTC veterans would kindly express their opinions. Both good and bad are needed to see if Project Treble is indeed the answer to the ever growing problems of Android OS versions and security patch fragmentation. If nothing else hoping HTC at least provides faster updates compared to older flagships
8bitbang said:
I don't expect answers this very second and hope HTC veterans would kindly express their opinions. Both good and bad are needed to see if Project Treble is indeed the answer to the ever growing problems of Android OS versions and security patch fragmentation. If nothing else hoping HTC at least provides faster updates compared to older flagships
Click to expand...
Click to collapse
Hard to tell. They gotten two updates out so far and it's been what like three months since release?
Project treble from my understanding is more focused towards separating Android and OEM drivers. So HTC should in theory be able to release Android Pie faster without waiting for Qualcomm etc to update their drivers. The only real delay being them compiling Android with Sense and testing for suitable stability.
Potentially pushing a major update out the door and then following up later on with HAL, Modem updates etc.
You'll run into some battery life and performance issues at first since the underlying hardware code isn't matched up with Android Pie.
Security patches and minor updates won't necessarily benefit from treble. Since those are just minor changes to the system that didn't require an entire system rebuild.
In the it's a matter of what HTC makes their shrinking software department focus/prioritize.
They need to fully embrace the idea behind Project Treble. Google already requires them to provide a fully working vanilla Android build. They then customize the system and Kernel once Google gives their approval. They need to just accept and use all the stock apps Google already makes and just push out HTC launcher and Camera updates. Leave the rest to Google and the component makers.
Sorry, kinda just went off on a tangent/rant.
Tachi91 said:
Hard to tell. They gotten two updates out so far and it's been what like three months since release?
Project treble from my understanding is more focused towards separating Android and OEM drivers. So HTC should in theory be able to release Android Pie faster without waiting for Qualcomm etc to update their drivers. The only real delay being them compiling Android with Sense and testing for suitable stability.
Potentially pushing a major update out the door and then following up later on with HAL, Modem updates etc.
You'll run into some battery life and performance issues at first since the underlying hardware code isn't matched up with Android Pie.
Security patches and minor updates won't necessarily benefit from treble. Since those are just minor changes to the system that didn't require an entire system rebuild.
In the it's a matter of what HTC makes their shrinking software department focus/prioritize.
They need to fully embrace the idea behind Project Treble. Google already requires them to provide a fully working vanilla Android build. They then customize the system and Kernel once Google gives their approval. They need to just accept and use all the stock apps Google already makes and just push out HTC launcher and Camera updates. Leave the rest to Google and the component makers.
Sorry, kinda just went off on a tangent/rant.
Click to expand...
Click to collapse
Your absolutly right, they should focus on launcher and app updates and leave the rest to google. Not only the launcher, also the apps are very outdated and it seems they didnt touched the phone/contact app for ages. I am using HTC since the legendary HD2 :/
I was hoping that trenble will speed up updates by a lot.

Question thinking of buying

Yes I read reviews.
I owned a Oneplus One years ago and I gave up waiting for an upgrade and bought something else.
I here that OnePlus is better at upgrading today than they were four years ago. Is this true ?
Like I said I read and I know OnePlus 6 has available an Oxygen Beta (Android Pie) but it has not been officially released ? Is true if I buy a device I may need to wait several months until they Officially release Android Pie.
Now I know you will say just run the Beta it is stable but here is the make of break question I need Android Pay and Wear OS. My experience tells me if I flash a Beta required apps like Android Pay and Wear OS may stop working.
If I buy today I think the safe thing will be to wait for Oxygen OS (Android Pie) to be released. Customer ROMs or Beta OS will break for sure Android Pay.
Other than hating to wait for official releases this device looks fine.
No wireless charging sucks but I can live without it.
The Pixel camera maybe better but I read the OnePlus 6 camera is not bad
The OnePlus 6T will be out in November but ..... THERE IS ALWAYS A NEW DEVICE around the corner. Wait for the OnePlus 6T..... oh but it a few months this will be released.
This device gives better value for the dollar.
Android pay is not working in Beta, you should read the OP forum in the beta thread to see all the things being said.
The 6T rumor is that it will come with Pie installed but since it isn't out yet nobody knows if it will really be installed out from the gate.
Personally, I think Oxygen OS is a mess and from what I see on the threads for Pie, they're just patching it yet again and putting a new UI on it over starting from scratch. All they keep doing is carrying over bugs from previous versions and then trying to re-patch them again for either the new device model and/or new Android system. Considering treble is now installed on both the 5 and 6, IMO they should have started fresh and should have been working on coding an entirely new OS 2 years ago.
If I were you, I would wait until Pie is released in the fall and see how it goes and what the complaints are before buying anything.
Official Pie has been released, you can already download the firmware and flash it.
As for updates and kernel source upload speed, the OP6 gets both the fastest among all devices I had.
As for taking pics, use the gcam port for great picture quality and the oos cam for [email protected] recording.
The Official build for Android pie has been released today which is nice as it took only about 1.5 months after Google released it themselves.
Thanks I jumped on a sale, and ordered one.
I am not even sure at this point I care about the Pixel, it may have a better camera but I am sure ordering the One Plus 6 I saved hundreds of dollars.
The OP 6T is set to be released in the next couple months. Unless you're in need of a headphone jack, I'd wait to get the latest version.
floridaman said:
Android pay is not working in Beta, you should read the OP forum in the beta thread to see all the things being said.
The 6T rumor is that it will come with Pie installed but since it isn't out yet nobody knows if it will really be installed out from the gate.
Personally, I think Oxygen OS is a mess and from what I see on the threads for Pie, they're just patching it yet again and putting a new UI on it over starting from scratch. All they keep doing is carrying over bugs from previous versions and then trying to re-patch them again for either the new device model and/or new Android system. Considering treble is now installed on both the 5 and 6, IMO they should have started fresh and should have been working on coding an entirely new OS 2 years ago.
If I were you, I would wait until Pie is released in the fall and see how it goes and what the complaints are before buying anything.
Click to expand...
Click to collapse
... That's not how android works .. even less since treble... You don't simply "patch" your Android version up to date, especially when it's a major revision that is changed. Most oftenly they start from scratch with some cherry picks. And rebuild blobs whenever necessary... files come from AOSP in it's normal form, then every time android releases a new version, this has to be merged with the current existing release yes, but that means that every difference from x that y has changes into x (x being the updated file, any of em, Y Being the old, already installed one)... Bringing something on /system over from one of the earlier oos, to a newer oos, would break alot. I mean.. we can't even run ob3 custom kernels on GM pie... Because changes... Having something stick around doesn't mean it hasn't been touched, porting is another thing, and there is also maybe a chance that it's the same group of devs handling this as it was back then. It's still oneplus. Also. Oos isnt nearly as bad as you make it sound.. Oos is by far the best fork of Android I've seen launched as an OEM specific android experience, and I've seen alot of phones. Simply due to its close resemblance of the pure experience, with it's small addins for simplicity, performance, and ease of use. The UI is Google's own new material guideline. Not oneplus'. And there was 3 pie betas wherein other Companies reach up to 18-20 betas... Are we owning the same device?
efinityy said:
... That's not how android works .. even less since treble... You don't simply "patch" your Android version up to date, especially when it's a major revision that is changed. Most oftenly they start from scratch with some cherry picks. And rebuild blobs whenever necessary... files come from AOSP in it's normal form, then every time android releases a new version, this has to be merged with the current existing release yes, but that means that every difference from x that y has changes into x (x being the updated file, any of em, Y Being the old, already installed one)... Bringing something on /system over from one of the earlier oos, to a newer oos, would break alot. I mean.. we can't even run ob3 custom kernels on GM pie... Because changes... Having something stick around doesn't mean it hasn't been touched, porting is another thing, and there is also maybe a chance that it's the same group of devs handling this as it was back then. It's still oneplus. Also. Oos isnt nearly as bad as you make it sound.. Oos is by far the best fork of Android I've seen launched as an OEM specific android experience, and I've seen alot of phones. Simply due to its close resemblance of the pure experience, with it's small addins for simplicity, performance, and ease of use. The UI is Google's own new material guideline. Not oneplus'. And there was 3 pie betas wherein other Companies reach up to 18-20 betas... Are we owning the same device?
Click to expand...
Click to collapse
I didn't say they were patching Android, I said they were patching their OS. Yes, I know they are 2 different things and I know things are working differently since treble. They can fully keep taking their Oxygen OS and throwing it over the latest version of Android and patch it to make it work with the new code, which is exactly what they've been doing. Yes, they get a guideline, that doesn't mean they are stuck doing only that and making no improvements/changes. There are literally hundreds of options they can code for, but don't.
I'm sorry, but it's not only simple, it's downright beyond basic even to what Google turns on and codes for features. Spare me the dribble of "pure android" please, it's a ridiculous mantra. I've not put the beta's on my phone but have been reading the forum and I have not yet received the stable update that has been just pushed out. But I already see some of the complaints coming in and no I'm not talking about the nonsensical postings.
If you think that OP is doing a great job on their OS, then you and I clearly have different standards. I'm glad you love it so much, to each his own in that regard.
floridaman said:
I didn't say they were patching Android, I said they were patching their OS. Yes, I know they are 2 different things and I know things are working differently since treble. They can fully keep taking their Oxygen OS and throwing it over the latest version of Android and patch it to make it work with the new code, which is exactly what they've been doing. Yes, they get a guideline, that doesn't mean they are stuck doing only that and making no improvements/changes. There are literally hundreds of options they can code for, but don't.
I'm sorry, but it's not only simple, it's downright beyond basic even to what Google turns on and codes for features. Spare me the dribble of "pure android" please, it's a ridiculous mantra. I've not put the beta's on my phone but have been reading the forum and I have not yet received the stable update that has been just pushed out. But I already see some of the complaints coming in and no I'm not talking about the nonsensical postings.
If you think that OP is doing a great job on their OS, then you and I clearly have different standards. I'm glad you love it so much, to each his own in that regard.
Click to expand...
Click to collapse
To each their own indeed. And it's not a ridiculous mantra.just as countless many others, I do prefer to be able to switch over countless amounts of phone but still have the same familiar, debloated and resource friendly UI. Having to learning all the different "UX"s gets pretty dull, as soon as ie Samsung gets settled with one, they change design language. And that, for me, is a deal breaker, I don't feel like having to relearn the same basics over and over, and where I usually have to install another AOSP based ROM on ie my Xperia, HTC or Samsung. Whilst the OnePlus just has the familiarity and non-rubbish feel to it that AOSP has. But don't get me wrong, as you said, to each their own, and if it wasn't for people like you that don't want the stock feel, we wouldn't have custom kernels and/or ROMs. And I've ran all the betas except ob3 and currently run the stable... And I've yet to run into any app not loading, crashing, or features not working as intended. But I would recommend not jumping on the bandwagon as I regret doing so, until there are some more data and user reviews of the stable branch. And I'm not trusting anyone doing a forum post not being previously recognized or a proper reviewer. The stable build is solid, but it's still early to tell.

Asus and Zenfone 6 commitment to future Android versions

I've read online that the Zenfone 6 will get Android Q and R. Can anyone point me at anything official from Asus to verify this?
fingery said:
I've read online that the Zenfone 6 will get Android Q and R. Can anyone point me at anything official from Asus to verify this?
Click to expand...
Click to collapse
Watch the announcement event on YouTube. Should be in there. However it's not uncommon for promises of updates to be broken. Just saying since you seem to be looking for some kind of official confirmation instead of all the media coverage relaying what Asus has said on the matter.
fingery said:
I've read online that the Zenfone 6 will get Android Q and R. Can anyone point me at anything official from Asus to verify this?
Click to expand...
Click to collapse
Here you go:
https://youtu.be/VBk8c1oHUcA?t=3468
Trixanity said:
However it's not uncommon for promises of updates to be broken.
Click to expand...
Click to collapse
Quoting this for emphasis. Manufacturers have been lying about updates for years.
Any manufacturers promise of long-term support needs to be taken with a tablespoon of salt. They make money selling phones.....they get squat for pushing updates to those phones....In a while they'll get bankrupt unless they sell more. Simple market dynamics 101.
Quite frankly...I believe that the version of Android that was built into the phone is usually the best. Maybe not the best version of Android per-se...but the best for the hardware. So many times I read about people who beg for a new version for their phones only to complain later that the update sucks, and is full of bugs. So I can appreciate if they push Q but as for R...welllllll, that may be just a little too much.
jaseman said:
Quite frankly...I believe that the version of Android that was built into the phone is usually the best. Maybe not the best version of Android per-se...but the best for the hardware.
Click to expand...
Click to collapse
That's very true for fat custom skins which deeply changes stock Android look and feel as well as adds new features. Like Samsung' former TouchWiz.
OT: I am using for nearly two years Xiaomi Mi A1 with Android One. It started with Android Nougat 7.1.2, then we were updated to Oreo 8.0, 8.1 and for half an year we have Pie 9. With every Android major version and with every monthly security update the phone is better and better, they steadily eliminate bugs and even add new features which were missing at start (like FM radio app, VoLTE support, etc). I am very happy with it. But despite this there are always users who are not satisfied for example because they have not done their homework about Mi A1 and they say that slim stock Android is worse for them than fat MIUI.

Xiaomi Mi A2 Lite is the Enterprise Recommended Device

Xiaomi Mi A2 Lite meets the Android Enterprise Recommended Device requirements.
https://androidenterprisepartners.withgoogle.com/device/#!/4812862572724224
This means Xiaomi should release the update within 90 days at the latest.
Example:
Android 10 v11.0.4 comes with March security update.
March 1 - April 1 / 1 month
April 1 - May 1 / 1 month
May 1 - June 1 / 1 month
Xiaomi cant release the new security update at June 2.
So they have left 13 days for the new update.
Learn more:
https://www.android.com/intl/en_us/enterprise/recommended/
Quote removed.
They don't really care about deadlines anymore as this phone will no longer get any system updates in 2 month as the 2 year support ends.
Think so as well, no more updates for this device. Will be left with a buggy Android 10 experience.
vinylmeister said:
Think so as well, no more updates for this device. Will be left with a buggy Android 10 experience.
Click to expand...
Click to collapse
I didn't say that we not getting updates anymore ,it's just they don't care about deadlines ... We probably get 1 or 2 system updates as they fixed the buggy Android 10 on mi a3. On that phone they pulled the update like 4 times and managed to fix it on the 5th version....
We will get 3,4 update in our a.s from xiaomi. We get so many updates for oreo and pie and they fix nothing, only new problems with new updates or i say security patches. For me i dont care about new versions of android, any stable version is good, but xiaomi wont to fix anything. My wife use redmi 5 plus almost 2 year without any bug, any restart, lag,.... That phone is same like a2 lite (specification) only a2 lite is google phone and redmi 5 plus is miui. And every miui phones works like charm. So xioami dont give a f... about google phones.
It is clear that they have no interest in the "Android one" program, I dare say that they never miss an opportunity to "sabotage" it continuously with fallacious version advances and security patches that instead of solving the problems add others
That fact that this device meets the requirements for Android Enterprise means nothing for us, customers, since that service is made specifically for companies and not individuals, so don't confuse the terms Android One and Android Enterprise. Don't read whatever makes you feel comfortable and try to post it as a fact. The following statements are made not to argue with the fact that Xiaomi/Google/Qualcomm doesn't give a damn about this device and the latest updates were horrendous, it is to fix the false information posted about this device. I want to make this statement at the beginning of my argument because I am not in any way protecting Xiaomi, but I can't stand false information based on reading 3 words and not understanding them properly.
Android Enterprise is and I quote "Android Enterprise Recommended rugged devices are designed to perform in harsh working conditions and stay up to date over long deployments. ... These devices can be used by a single employee or shared between employees."
To translate that to you folks, this doesn't apply to any of you, or us. This is directed towards the enterprise businesses which can control the devices of a company, like deploying apps, collecting data and so on. Just like some companies still use handheld devices on the field running some enterprise windows mobile/ce custom version for their company, they have a special set of features over those devices which normal customers don't have. Now do you understand the difference between customer and employee? When you buy a device that you fully own, you are a customer and you fully own the device and it's capabilities, when you are an employee and the company gives you this device you don't own it, an the company reserves the right to modify the device content and behavior based on their needs. Also the enterprise version only imply ONE version upgrade from factory version and 5 years of max 90 days security updates, which is different from what was stated in the leaflet that came with the phone.
Now for customers and not enterprise/employees there is the standard Android One program. A stock android experience, forbid to major skinning/customization with 2 year OS updates (which implies 2 versions of Android from stock/out of the box since Android is launched once a year) and three years android security updates and bugfixes. I would also go a step further to note that this is a minimum time obligation, no one is forcing them not to release a 3rd or a 4th major update for the device, but that would be contrary of the saying "you won't buy something new unless the old one is obsolete". Now back to the track, so you get 2 year os updates, which is a fancy way to say that you'll get 2 android version updates and bonus you get one more year of security updates for the last version you got. You don't add up 2+3 and for sure the 3rd year is still enforced by google!
Now, I'll tell you why the information stated in OP is false. As we established, Enterprise must be updated at least once per 90 days... Good, that's correct and fair... But, the Android One program is enforced to MONTHLY updates, not 3 months updates. And my source is and I quote directly from the android security directive website "We have an established monthly update cycle for Pixel devices, as well as those under the Android One program." and to enforce the enterprise I also quote "In addition, Android Enterprise Recommended devices are updated at least every 90 days."
So, as you can see, Xiaomi is way over their heads with this specific device. This specific device was not once, but twice way behind schedule and the penalties from Google may start to show up soon, but it may be us, the end users, the customers who'll feel the full force of those penalties. Even if the .04 version fixed the bricking problem, it's still miles away from being a good and functional build, many of the basic functions to work you have to give up on other functions, and sometimes, even some 3rd party apps can mess up the inner workings of the system. This is just wrong and I totally hope to see some improvements, hell, just make one good build and abandon it for god's sake, but don't make us experience new bugs with every update... We... and also I craved the 10 update because of many reasons... but for me, this specific version of 10 that we got, it's just a broken pie with gestures and dark mode... this isn't what google promised when developing 10, and this is not what Xiaomi promised when they enrolled in the Android One program.
But hell, again, maybe OP is right, maybe the Android Enterprise program is giving them an escape window to delay the Android updates for ~3 months... but we will see... I was eagerly waiting for an update on Monday... that day passed, the next day passed... and we're on to the end of the month... when we're going to get probably another half-assed update, with the April or May security patch... and maybe a few bugfixes that would only make us wait eagerly for the next update as well.
Honestly I miss the days when devices were built with one thing in mind, customer satisfaction. When the devices were built to simply work, and when updates, as rare as they were were actually improving your device experience, not crippling it. Now they have to find problems to fix just to release a monthly update, because updates are cool aren't they? No, they are not... The full functionality of the device is cool...
I hope I made my point, and I hope I don't upset anyone with stating my opinion based on facts. I was contradicted many times on this forum, and maybe my approach on the subject was wrong, but when you judge something, you have to always be objective, and always state the facts over feelings. I know most of us are upset and angry with the state of our devices, which is understandable and well based, but yelling our frustrations without understanding how things work isn't going to cut it.

Which devices will get the longest and most stable LineageOS support?

I recently saw that the OnePlus One is one of the first devices to get a LineageOS 18.1 build. Which I found kind of surprising because it is such an old device.
I guess it could be because the stock ROM of the OnePlus One (outside of Asia) was CyanogenOS which is a proprietary fork of CyanogenMOD which is the predecessor of LineageOS. (Correct me if I'm wrong.)
But it still seems weird that newer OnePlus phones like the OnePlus 7 don't have official LineageOS 18.1 builds as of now...
I'm curious what drives the developers to support certain devices over others and if there is a way for me to be able to predict which device is going to be supported for a long time and maybe even more importantly which device is going to be the most stable.
As an example, I very much regret my purchase of the Nvidia Shield Tablet, as they stopped supporting it with 15.1 and even that version always had massive problems (UI lags 90% of the time).
As a positive example, my Oneplus 5T has always been very stable (for the most part; Bluetooth is pretty buggy) and is one of the first devices to have gotten a LineageOS 18.1 build.
(I personally don't care about unofficial builds btw because I need regular OTA security patches from a reliable and very trusted source.)
Some time ago I read an article about some sort of feature regarding the HAL (Hardware Abstraction Layer) that might make it much easier for ROMs like LineageOS to add support for them. I think it was called "treble". Maybe I should look for devices supporting that? I really don't know...
At the moment I'm looking for a new Tablet to buy. Maybe this time I can get my hands on a device that will last me longer and won't have any severe issues.
No one?
ferivon said:
No one?
Click to expand...
Click to collapse
GSI roms are a thing, make sure your device has an unlockable bootloader and atleast android 9.
Well, having an unlockable bootloader is kind of obvious, isn't it? I mean if it wasn't unlockable, it wouldn't be listed on https://download.lineageos.org/
Not sure what GSI is, but I'm not looking for an alternative ROM to LineageOS.

Categories

Resources