Related
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.
I have a spare Razer Phone I want to donate to a developer in order to boost development for this device, since Razer released Treble for it the device got my attention, but it could use a bit more development.
Current status:
Official TWRP available
Treble available
Kernel source available
Oreo developer preview available
No custom ROMs ATM, Treble ROMs have broken critical features such as in call audio and possibly more.
I'm shipping the device for FREE to anyone who:
Is a recognised developer here on XDA
Guarantees they will use the device for development (at least try) and not just sell it on eBay
Is located in the EU, because customs, exceptions possible for really great developers.
How to apply:
Leave a post in this thread with a few short words about your previous work at XDA and what would you like to do with the device, like Kernel development, ROM porting or else.
Is this serious or some kind of sad joke?
If you have doubts in me I can just say that I already shipped a device to Phh in December to help boost Treble development, and tomorrow I'm shipping a Nexus 6 to @Elektroschmock to help the Nexus 6 development stay alive as Elektro broke their N6 recently.
In case multiple devs apply for the free device I reserve the right to pick one of my personal preference, unfortunately I have only 1 spare phone for 1 dev.
@phhusson @MishaalRahman interested or know anyone who is?
To clarify, in case it was not clear, the device goes completely free to a developer, I also pay shipping inside the EU.
If customs charges occur outside the EU I would not cover those.
Shipping with tracking.
To the forum mods:
I didn't really know where to put this, I thought not many devs would see it in the Razer forums, as those are usually only frequented by people who already have a device, feel free to move the thread if you think of a better forum where it belongs.
Well not an RD here but hey tought i might try haha, so here it goes
Im part of LOS team (Currently maintaining hero family of devices (s7 and s7 edge exynos) ) Im doing a bringup of them for oreo Fixed almost all of the bugs expect for GPS after that things can go official for them so ill have to find something to play with anyway, I have experience with AOSP build system so i could at least try to get builds for Razer Phone before any mainstream roms are ready for compiling. I would also probably try to get some fun stuff to work on phone like Kali Linux NetHunter and well i would like to play with treble supported device and razer phone looks as a nice candidate as i could get some rest from exynos
Ivan_Meler said:
Well not an RD here but hey tought i might try haha, so here it goes
Im part of LOS team (Currently maintaining hero family of devices (s7 and s7 edge exynos) ) Im doing a bringup of them for oreo Fixed almost all of the bugs expect for GPS after that things can go official for them so ill have to find something to play with anyway, I have experience with AOSP build system so i could at least try to get builds for Razer Phone before any mainstream roms are ready for compiling. I would also probably try to get some fun stuff to work on phone like Kali Linux NetHunter and well i would like to play with treble supported device and razer phone looks as a nice candidate as i could get some rest from exynos
Click to expand...
Click to collapse
Well not an RD here but hey tought i might try
Your application is welcome and noted, the RD thing was just a guideline to attract more senior devs, or how to say it.
let's give a couple of days for more devs to get the chance to express their interest and we take it from there
Hi, Diazz72 here .
Well where to start...i've joined xda about 6 years ago, stared my first project on old S4 about 4-5 years ago and continued till i've switched to G5...since it i've contributed to S7 and 6P till i switched to iPhone and soon after to S8...Well let me tell ya S8 is nightmare.
So how can i contribute if chosen...well i can bring at least two rom's to this beautiful device ( maybe R.R. and COS...Will see what crowd demands ).
If you need any more info send me a PM.
Regards, Diazz72.
Well in a nutshell, I'm the lead developer for Invictrix and previously DesolationROM. I was the first person to bring nougat to the note 4, my Werewolf kernel for the LG V20, the Nexus 5, the Nexus 7 2013, the Samsung Galaxy Note 4, and the Essential PH-1. I was also one of the early members of Substratum. Also I was the person who reverse engineered the pixel navbar to work on custom roms.
https://github.com/USA-RedDragon/AboutMe/wiki
https://github.com/USA-RedDragon
and
https://github.com/InvictrixRom paint a lot of the picture as well.
Well, of course I'm interested in the Razer Phone, though I don't think I'm the one who will give it the most love.
If I get the device, I'd test and fix all GSIs I'll make on it, like AOSP P when sources will be available (I think that if I get a Razer, it will be the first one to get P, since it's A/B and that makes things much easier)
I'd also probably try to get some hardware features to work on GSIs (like porting stock camera if that's relevant, and see what can be done with the 120Hz screen)
But I won't dive too deep, like I won't do any kernel work.
For my overall Treble testing, I think it will definitely be a great device, since I'm lacking an A/B and a Qualcomm test device, which seem to have few specificities.
Fwiw, I've reported some issues to Essential (they even answered once! https://github.com/phhusson/platfor...23ea40b255dfbba5813c29#commitcomment-28321661 ), and I plan to do this as well for Razer, since it looks like their Treble implementation isn't totally ok (though I think it passes Google certification)
phhusson said:
Well, of course I'm interested in the Razer Phone, though I don't think I'm the one who will give it the most love.
If I get the device, I'd test and fix all GSIs I'll make on it, like AOSP P when sources will be available (I think that if I get a Razer, it will be the first one to get P, since it's A/B and that makes things much easier)
I'd also probably try to get some hardware features to work on GSIs (like porting stock camera if that's relevant, and see what can be done with the 120Hz screen)
But I won't dive too deep, like I won't do any kernel work.
For my overall Treble testing, I think it will definitely be a great device, since I'm lacking an A/B and a Qualcomm test device, which seem to have few specificities.
Fwiw, I've reported some issues to Essential (they even answered once! https://github.com/phhusson/platfor...23ea40b255dfbba5813c29#commitcomment-28321661 ), and I plan to do this as well for Razer, since it looks like their Treble implementation isn't totally ok (though I think it passes Google certification)
Click to expand...
Click to collapse
Noted
Offtopic
since it looks like their Treble implementation isn't totally ok (though I think it passes Google certification)
It's Dev Preview 1, let's see how it goes by the time it's stable, I do expect changes.
since it's A/B and that makes things much easier
I think you are the first person I ever saw post A/B and easier in the same sentence lol hahaha
Ok so from the 4 interested devs I decided for @phhusson
Why?
Because even tho he said he won't be specifically focused on this device I believe having fully working Treble ROMs is what will bring the most benefit to this device in the long term, having Treble means having already 5+ available ROMs, including LOS 15.1 and RR, and that number will just grow with time.
"like porting stock camera if that's relevant"
Don't bother, it's crap, rather port Google camera
Exelios said:
Ok so from the 4 interested devs I decided for @phhusson
Why?
Because even tho he said he won't be specifically focused on this device I believe having fully working Treble ROMs is what will bring the most benefit to this device in the long term, having Treble means having already 5+ available ROMs, including LOS 15.1 and RR, and that number will just grow with time.
"like porting stock camera if that's relevant"
Don't bother, it's crap, rather port Google camera
Click to expand...
Click to collapse
You are the real MVP.
Exelios said:
I have a spare Razer Phone I want to donate to a developer in order to boost development for this device, since Razer released Treble for it the device got my attention, but it could use a bit more development.
...
Click to expand...
Click to collapse
Not sure if anyone answered you, as I don't have time to read through. I'm interested to develop on this device, mostly for NetHunter. I'm not that active on XDA, but you can look me up on Github, Gitlab @yesimxev
Official developer of NetHunter
EDIT: Just seen the last answer. Anyway, I'm interested in future possibilities too. Thanks!
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.
Hello,
I'm still using my Oneplus One with the original Cyanogen Mod.
I can definitely noticed the age of my phone nowadays. As I recently discovered that there are stable builds of Lineage OS available for the OPO I started wondering if an updated software would give my phone a bit of a revival. In general it is still in a good condition so I don't really want to just replace it.
Just wanted to hear your thoughts and opinions, if it is worth to update the software or if I rather should start searching for a replacement.
What is there to lose if you first try out the newest LineageOS, which is based on Android 11?
If you do not need things like a better camera or use your phone for gaming, the OPO is still as good as ever. I think my phone is smoother to use than it was 7 years ago because of the LineageOS team's work. Tomoms even has a performance optimized build for the OPO, which I can recommend strongly. Beware that the optimized build is more experimental than the official LineageOS.
Hi, I upgraded my oneplus one a couple of months to lineage OS 17.1 - works well and after adding Gapps is almost like a new phone. it is slightly slower but it gave a new life. little apprehensive for getting lineage Os 18.1, as it says it will be even slower due to software encryption
So far there was plenty of choice between roms with each android version as the years went by. Android 8 got a lot, 9 a bit less but still plenty, 10 a lot again but 11 seems to be largely skipped (at least by the major big roms). As far as i know, there is only Lineage, Graphene, Tugapower, Kali Nethunter and that's it. (there is Havoc-OS too but it's not official and has barely any features)
Of course it's still better than nothing at all to keep the opo working so i'm very thankful to the devs for that. Even android 10 will be useful for a few more years (i'm currently on RR android 8 and no issues so far even now). TWRP had an update in may 2022 which was a nice surprise, so that's pretty cool at least.
Is there any indication at all that someone is working on android 12 for the opo?
Many rom builders nowadays have their own site now. Below i found a site some time ago that has a lot of them in one place to easily keep track if any progress happens:
OnePlus One ROMs Archives
|
theunlockr.com
So far no major names like Resurrection Remix, Syberia, MSM-X, Havoc, Posp, among many others..
Correct me if i'm wrong. Maybe i missed something completely. Perhaps you guys have some interesting opinions aswell.
edit: not sure why mod moved it to here(i posted in general on purpose). it's not a technical problem but whatever, i guess knowing context is hard
edit2: even the galaxy s2 and s3 got android 12 now. If those devices can boot it, the opo (which is comparable so an s5) surely has to be capable enough. i hope someone out there is developing someting..