Related
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)
mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.
Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..
As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.
floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.
Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...
A Few months ago, OPO and Cyanogen, said 90 days after the official Lollipop release from Google, the OnePlus One OS would get the big Lollipop date. So that puts it end of Jan / early Feb. But is that still on track of happening ?
But...with the all the news lately of Cyanogen and OPO not getting along, and the whole India deal, etc...
What will OPO official release as far as the Lollipop update ? Will there still be a CM12S made specific for the OnePlus by Cyanogen ? Or will OPO just release their in house Lollipop ROM they made themselves without CM ?
The last I read, there is a big update coming in January, which would presumably be CM12S Lollipop. OnePlus also has announced that they are on the verge of releasing their own, house built ROM, so it's possible that is also coming in that time frame.
Sent from my iPad using Tapatalk
There's not much point in asking that here, nobody here can answer the question properly. Plus, even if CM were reading here, they don't respond to requests for ETA's.
Transmitted via Bacon
timmaaa said:
There's not much point in asking that here, nobody here can answer the question properly. Plus, even if CM were reading here, they don't respond to requests for ETA's.
Transmitted via Bacon
Click to expand...
Click to collapse
Not really asking for an ETA. I know they both said 90 days after Lollipop code release.
But my question is more about if it will even come at all now ? Due to the rocky relationship between OPO + Cyanogen.
Sent from my A0001
Zorachus said:
Not really asking for an ETA. I know they both said 90 days after Lollipop code release.
But my question is more about if it will even come at all now ? Due to the rocky relationship between OPO + Cyanogen.
Sent from my A0001
Click to expand...
Click to collapse
Yeah but unfortunately the answer remains the same; nobody here knows, we can only speculate. The only people who know are CM, and they won't comment on it. There's the "big" update coming in January but I'm not putting any money on it being 5.0, they haven't even hinted to that.
As with everything when it comes to ROMs/Kernels/OTAs... no one knows and employees don't release release dates because then they'll feel pressured that they'll NEED to have it done.
Would you rather have a rushed release with bugs causing your phone not to work properly? Especially if its a person who does not involve themselves with rooting/flashing?
Or would you rather have a release where it works and is tested thoroughly.
If you can't wait, try a Lollipop ROM. If you want to stay as close to stock as possible, flash CM12.
I am not asking for a specific CM12S release date.
This thread is more about asking if there will even be a CM12S released period, ever ? With all the recent bad press between OPO and Cyanogen. I am worried there might not ever be an official OnePlus One CM12S OS release at all now in a couple months ?
Sent from my A0001
And the answer is still (and always will be) nobody here can answer that.
Transmitted via Bacon
Zorachus said:
I am not asking for a specific CM12S release date.
This thread is more about asking if there will even be a CM12S released period, ever ? With all the recent bad press between OPO and Cyanogen. I am worried there might not ever be an official OnePlus One CM12S OS release at all now in a couple months ?
Sent from my A0001
Click to expand...
Click to collapse
That is specific to the market of India. I'm sure that oneplus and cyanogen have a contract that they need to abide by otherwise therell be lawsuits.
I wouldn't worry about it, I'm sure there will be a cm12s. When? Don't know.
If you can't wait, flash cm12 unofficial. Now if we talk about the oneplus two (or whatever they plan on calling it, I wouldn't be surprised if they did abandon CyanogenMod in favor of their own rom.)
Sent from my Nexus 6 using Tapatalk
zephiK said:
That is specific to the market of India. I'm sure that oneplus and cyanogen have a contract that they need to abide by otherwise therell be lawsuits.
I wouldn't worry about it, I'm sure there will be a cm12s. When? Don't know.
If you can't wait, flash cm12 unofficial. Now if we talk about the oneplus two (or whatever they plan on calling it, I wouldn't be surprised if they did abandon CyanogenMod in favor of their own rom.)
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
For the OnePlus One, you're darn right there will be lawsuits if we don't keep getting CM branded official updates. That was what the phone was marketed as, printed with Cyanogen branding, and I as a customer bought it for. If they abandon CM branded official upgrades, I'd be forced to kick off or join a class action lawsuit against both OnePlus and Cyanogen. I won't tolerate bait and switch.
maybe in february
They are suppose to deliver CM12s in Jan(this month) ..at least at the very end, it's the 90 days they promised us. Feb is too late as it won't be 90 days but more
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)
evronetwork said:
They are suppose to deliver CM12s in Jan(this month) ..at least at the very end, it's the 90 days they promised us. Feb is too late as it won't be 90 days but more
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)
Click to expand...
Click to collapse
Steve Kondik has said it will be out later next month. Check his Google+ profile. Sorry I can not post a link.
freelancer1988 said:
Steve Kondik has said it will be out later next month. Check his Google+ profile. Sorry I can not post a link.
Click to expand...
Click to collapse
I believe this is the link:
https://plus.google.com/app/basic/stream/z13evbgalmvfdffve220xb2reqilvvbw504
evronetwork said:
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)
Click to expand...
Click to collapse
You people and your benchmark scores. Give it up already
Sent from my A0001 using XDA Free mobile app
Mr Patchy Patch said:
You people and your benchmark scores. Give it up already
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I just made a pointless fact(from other people's tests) about that no need to act like that, be polite man ..you should try it next time.
I really don't care about benches, I prefer if it feels smooth-liquid, runs fast and not with 20fps at games and have 1000 points on antutu rather than having a sci-fi 80.000 points and be garbage
Just interested in
Guys can someone describe me difference shortly of CM11 and CM1s. Coz I'm on CM12 Nightly builds on my OPO atm and it's working fairly good.
Qwsazy said:
Guys can someone describe me difference shortly of CM11 and CM1s. Coz I'm on CM12 Nightly builds on my OPO atm and it's working fairly good.
Click to expand...
Click to collapse
There's very little difference except CM11S has the fancy lockscreen and camera. CM11 receives nightly updates whereas CM11S received periodic updates.
Transmitted via Bacon
Yeah it confuses me why people still beg for the same product with an S attached to it as it will make things better for them. This phone is a developer type of phone for people who will try rooting and flashing. With the recent updates in CM getting closer to stable why do we care about an 11s.
Also lets be honest if we do not have all the proper working features in a nightly you cant expect to see a stable release.... At least a 12M or something has to be put out for our phones too me before we say an 12S
@Zorachus - step back and think for a second why are you asking your question. No one associated with giving you an answer will come here and give it to you. You can Google it and see whats out there and draw your own conclusion. I feel this is what others were trying to get across to you. You are asking a question that can't be answered no matter how you slice it up
playya said:
Yeah it confuses me why people still beg for the same product with an S attached to it as it will make things better for them. This phone is a developer type of phone for people who will try rooting and flashing. With the recent updates in CM getting closer to stable why do we care about an 11s.
Also lets be honest if we do not have all the proper working features in a nightly you cant expect to see a stable release.... At least a 12M or something has to be put out for our phones too me before we say an 12S
Click to expand...
Click to collapse
Because for some people it's a matter of principle. CM stated very clearly that this device would receive official updates for two years, if the S branch is dropped they're reneging on that agreement.
Because this isn't strictly a dev phone, this is a developer-friendly phone. Not everyone wants to unlock and root their device, in fact the majority of the user base most likely don't want to. So if support is dropped then those people are left with a device that isn't receiving the updates it was promised to have, those people have a right to expect those updates.
Transmitted via Bacon
Just wondering if the SlimLP 5.1 development of the Nexus 5 rom is still going on?
All appears quiet in the main forum and am just looking for an update.
bleagues said:
Just wondering if the SlimLP 5.1 development of the Nexus 5 rom is still going on?
All appears quiet in the main forum and am just looking for an update.
Click to expand...
Click to collapse
This rom is dead!
bleagues said:
This rom is dead!
Click to expand...
Click to collapse
Aha, is it?
New Gerrit
https://review.slimroms.eu/#/q/status:open
New Homepage (under construction)
http://slimroms.eu/
We work on the update after we have sorted out many things in the last week's.
All this informations are posted in the Nexus 5 thread also.
Sometimes it's better to say nothing when know nothing.
Tylog said:
Aha, is it?
Sometimes it's better to say nothing when know nothing.
Click to expand...
Click to collapse
I'm not saying I know anything.
But I do know what I see...
That being a Lack of any NEW or UPDATED rom in quite some time. I believe it was posted in early December that weeklies and officials were coming soon. It's now almost the middle of April.
FYI, its been a week since your post...still nothing new.
I'll be one of the first to congratulate you and your team when a new official build comes out. Your product is good, I like it a lot, it's just the continued excuses and delays that make the whole thing look bad.
Unfortunately the issues with the N5 version of SlimLP persist.
For those looking for a very comparable, updated ROM, check out the ROM team Chroma has under development in the XDA N5 development page.
Anyone else starting to get concerned that now 40 days into P3a's life, there are no signs of growing development efforts?
ElementalX was all over it very quickly, but I'm starting to get worried that nobody wants to invest time into development for a budget phone, despite it selling off the charts everywhere.
Just curious if anyone else has a perspective to offer.
nickmv said:
Anyone else starting to get concerned that now 40 days into P3a's life, there are no signs of growing development efforts?
ElementalX was all over it very quickly, but I'm starting to get worried that nobody wants to invest time into development for a budget phone, despite it selling off the charts everywhere.
Just curious if anyone else has a perspective to offer.
Click to expand...
Click to collapse
My 3a is using stock rom, which I rooted. I love this phone, Bluetooth is crystal clear. I am beginning to wonder why I would need TWRP.
Yeah tbh I would have already expected TWRP to come out for the 3a already, based on the fact that the custom recovery was completed soon after the release of the Pixel 1, 2, and 3. I saw a thread that had a few people working on it, but I still have not heard anything in a while. I know TWRP is eventually going to come, but I guess we've been spoiled with the last 3 releases.
I have seen the thread showing how to install Magisk on the 3a, but it's not an official build yet either...
There's been some development on the 3a. Currently running Dirty Unicorns 13.3 and it's smooth. Besides no TWRP, I don't see why there shouldn't be some ROMs in the works.
John256145 said:
Yeah tbh I would have already expected TWRP to come out for the 3a already, based on the fact that the custom recovery was completed soon after the release of the Pixel 1, 2, and 3. I saw a thread that had a few people working on it, but I still have not heard anything in a while. I know TWRP is eventually going to come, but I guess we've been spoiled with the last 3 releases.
I have seen the thread showing how to install Magisk on the 3a, but it's not an official build yet either...
Click to expand...
Click to collapse
It is official.
Heres a photo of TWRP splash if you want hype lmao
You will need TWRP if you run anything special like a Magisk module and something goes wrong and you either have to flash stock again or TWRP and uninstall the module. I really hope we at least get TWRP,,,all the other stuff is gravy.
I though that the flagships Pixels got barely any development because they were too expensive. Apparently not.
So why does the 3a barely have any development, compared to the more expensive OnePlus 7 Pro for example? Is it because Google isn't sending out units to developers? Or is it simply not popular for some reason with the XDA community?
Bidiminished said:
I though that the flagships Pixels got barely any development because they were too expensive. Apparently not.
So why does the 3a barely have any development, compared to the more expensive OnePlus 7 Pro for example? Is it because Google isn't sending out units to developers? Or is it simply not popular for some reason with the XDA community?
Click to expand...
Click to collapse
IMO because the stock experience is just that good. What reason does someone have to flash a custom ROM over stock now? It certainly isn't because stock is too slow.
ZVNexus said:
IMO because the stock experience is just that good. What reason does someone have to flash a custom ROM over stock now? It certainly isn't because stock is too slow.
Click to expand...
Click to collapse
Very rightly said!! I used to die for flashing pixel experience roms in my redmi note 3, 5 pro, mi a2, s9! In the end i decided lets get the Pixel 3a & kill the urge
Hellrazoraj said:
Very rightly said!! I used to die for flashing pixel experience roms in my redmi note 3, 5 pro, mi a2, s9! In the end i decided lets get the Pixel 3a & kill the urge
Click to expand...
Click to collapse
I usually have lineage on any phone ive had. I dont have the urge with this. although id still like the option.
Unstroofy said:
I usually have lineage on any phone ive had. I dont have the urge with this. although id still like the option.
Click to expand...
Click to collapse
Understandable, lets wait & see in the Dev side. I guess its an easy walk in the park for devs that they are not working on the device.
Hellrazoraj said:
Unerstandable, lets wait & see in the Dev side. I guess its an easy walk in the park for devs that they are not working on the device.
Click to expand...
Click to collapse
Someone is working on lineage for the 3a. I think its gonna be a unified rom with the XL. Twrp is only a matter of time.
Pretty sure TWRP is coming. It would be strange for them to ignore a Pixel
dtb1987 said:
Pretty sure TWRP is coming. It would be strange for them to ignore a Pixel
Click to expand...
Click to collapse
They only support what they own. They don't own a P3A. End of story.
How do you know? All we can do is speculate at the moment unless someone has actually heard from someone from TWRP.
ZVNexus said:
They only support what they own. They don't own a P3A. End of story.
Click to expand...
Click to collapse
No.
Unstroofy said:
No.
Click to expand...
Click to collapse
Give me a device that they don't own that they support. Sure, there's tons of unofficial device maintainers for TWRP, but I mean actual core members of TWRP that maintain a device that they do not own themselves.
ZVNexus said:
Give me a device that they don't own that they support. Sure, there's tons of unofficial device maintainers for TWRP, but I mean actual core members of TWRP that maintain a device that they do not own themselves.
Click to expand...
Click to collapse
TWRP do not own any devices. You need to read their FAQs to have a basic understanding of how it works.
Again, people are working on twrp for the 3a.
Unstroofy said:
No.
Click to expand...
Click to collapse
https://twrp.me/faq/howtocompiletwrp.html
He's right
Also, I'm pretty sure he's the one working on twrp...
Starting off at version 9, the official P3 Rom thread now lists version 12...
I was under the impression that such devices usually received a max of 3 Android releases. So for P3, that would be 9, 10 and 11
I had also read elsewhere that version 11 will be the final release that Google will issue for the P3
12.0.0 (SP1A.210812.015, Oct 2021)FlashLinkc5f3469cfd9ac914377eac1d05eb60bde3b88d109c9e618eecf82a938bad562512.0.0 (SP1A.210812.016.A1, Oct 2021, Verizon)FlashLink514272b9973ab900dd92ab7652291498e868d9778be77979291e9ed60c287838
Now I see this
I am not interested in the Verizon release. But there is still SP1A.210812.015 which seems to be unbranded one
Is there any reason behind Google's intention to further support the P3 into yet another Android release?
jstoner said:
Starting off at version 9, the official P3 Rom thread now lists version 12...
I was under the impression that such devices usually received a max of 3 Android releases. So for P3, that would be 9, 10 and 11
I had also read elsewhere that version 11 will be the final release that Google will issue for the P3
12.0.0 (SP1A.210812.015, Oct 2021)FlashLinkc5f3469cfd9ac914377eac1d05eb60bde3b88d109c9e618eecf82a938bad562512.0.0 (SP1A.210812.016.A1, Oct 2021, Verizon)FlashLink514272b9973ab900dd92ab7652291498e868d9778be77979291e9ed60c287838
Now I see this
I am not interested in the Verizon release. But there is still SP1A.210812.015 which seems to be unbranded one
Is there any reason behind Google's intention to further support the P3 into yet another Android release?
Click to expand...
Click to collapse
It's more of a time thing. Google typically supports devices for 3 years from their release date. The Pixel 3 was released in October 2018, so its last update is Oct 2021.
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
But, the Pixel 3 / 3XL have been sunsetted as of that 3 year mark, so they will no longer receive any updates.
The 3a/3aXL will be supported to May of this year; the 4/4XL will be supported to October; and so on.
My Pixel 5 will no longer be supported beyond October 2023.
V0latyle said:
It's more of a time thing. Google typically supports devices for 3 years from their release date. The Pixel 3 was released in October 2018, so its last update is Oct 2021.
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
But, the Pixel 3 / 3XL have been sunsetted as of that 3 year mark, so they will no longer receive any updates.
The 3a/3aXL will be supported to May of this year; the 4/4XL will be supported to October; and so on.
My Pixel 5 will no longer be supported beyond October 2023.
Click to expand...
Click to collapse
So those two builds of Android 12 I mentioned above (SP1A.210812.015 and SP1A.210812.016.A1) are in fact the first and last ones for P3..?
Ackward approach to have this version 12 and leave it premature. I m sure there will be some sort of issues with it
jstoner said:
So those two builds of Android 12 I mentioned above (SP1A.210812.015 and SP1A.210812.016.A1) are in fact the first and last ones for P3..?
Ackward approach to have this version 12 and leave it premature. I m sure there will be some sort of issues with it
Click to expand...
Click to collapse
Yes, the initial release of Android 12 on the Pixel 3 /3XL is also the last update the device will ever receive. That being said, the initial 12 release is quite stable, the only bugs I found were nothing that impaired usability.
I suspect the reason why the P3 / XL got Android 12 for its final release is because of the GSI architecture on Pixel devices. Google doesn't develop multiple ROMs for multiple devices - the only thing really different are the bootloaders, baseband, drivers, and maybe kernel. Android 12 on the Pixel 6 looks and performs exactly like Android 12 on the Pixel 3. So, all Pixels get updated at the same time; the fact that the initial release of Android 12 was the final update on the P3 is more of a coincidence, really.
V0latyle said:
Yes, the initial release of Android 12 on the Pixel 3 /3XL is also the last update the device will ever receive. That being said, the initial 12 release is quite stable, the only bugs I found were nothing that impaired usability.
I suspect the reason why the P3 / XL got Android 12 for its final release is because of the GSI architecture on Pixel devices. Google doesn't develop multiple ROMs for multiple devices - the only thing really different are the bootloaders, baseband, drivers, and maybe kernel. Android 12 on the Pixel 6 looks and performs exactly like Android 12 on the Pixel 3. So, all Pixels get updated at the same time; the fact that the initial release of Android 12 was the final update on the P3 is more of a coincidence, really.
Click to expand...
Click to collapse
Excellent, thank you for the input
Way I see it, from security perspective, there isn't much of a benefit moving from latest v11 to v12 final (if its not to receive any further updates)
Perhaps someone may be tempted for a specific new feature on v12 (?), but so I far, I don't see a need for it
jstoner said:
Excellent, thank you for the input
Way I see it, from security perspective, there isn't much of a benefit moving from latest v11 to v12 final (if its not to receive any further updates)
Perhaps someone may be tempted for a specific new feature on v12 (?), but so I far, I don't see a need for it
Click to expand...
Click to collapse
To each their own. I disagree on the security perspective; Android 12 introduced a lot of privacy and security features that are a major improvement over Android 11. Even if there are no further updates, that alone would be of some benefit.
Of course, for those still using the P3, there may soon come a time when custom ROMs are safer as they often incorporate the latest kernel fixes and security updates from AOSP.
V0latyle said:
To each their own. I disagree on the security perspective; Android 12 introduced a lot of privacy and security features that are a major improvement over Android 11. Even if there are no further updates, that alone would be of some benefit.
Of course, for those still using the P3, there may soon come a time when custom ROMs are safer as they often incorporate the latest kernel fixes and security updates from AOSP.
Click to expand...
Click to collapse
Hello there new to the forum, pretty much a newb when it comes to tech talk, really..
But I am a Google Pixel 3 user, just found the news that it will no longer be supported. Asked some friends and they mentioned custom ROMs as a way around this... My old school nature finds all of this ridiculous, but it is what it is, I guess xD
In response to this, my question is when would a user like me consider switching to a custom ROM? "there may soon come a time..." ... what time might that be? When I start to see functions failing? When Android 12 updates globally but not for me?
Additionally, what would be the best resource to finding which custom ROM would fit my needs best?
Currently, my phone works great still. Hopefully I can exist for quite a while and not even think about it... but it works so good that I'd hate to go and buy a Pixel 6 when its security issues that render my device obsolete. If it means a custom ROM before $600, I'll probably take the shot.
Thanks!
neat_moss said:
Hello there new to the forum, pretty much a newb when it comes to tech talk, really..
But I am a Google Pixel 3 user, just found the news that it will no longer be supported. Asked some friends and they mentioned custom ROMs as a way around this... My old school nature finds all of this ridiculous, but it is what it is, I guess xD
In response to this, my question is when would a user like me consider switching to a custom ROM? "there may soon come a time..." ... what time might that be? When I start to see functions failing? When Android 12 updates globally but not for me?
Additionally, what would be the best resource to finding which custom ROM would fit my needs best?
Currently, my phone works great still. Hopefully I can exist for quite a while and not even think about it... but it works so good that I'd hate to go and buy a Pixel 6 when its security issues that render my device obsolete. If it means a custom ROM before $600, I'll probably take the shot.
Thanks!
Click to expand...
Click to collapse
When to switch depends entirely on your attitude towards monthly security updates. That would also effect what ROM you consider. Personally I switched about 4 months ago. I chose LineageOS because it reliably receives monthly security updates.
Do you have an unlockable bootloader? If not, all your questions are moot, because you must be able to unlock the bootloader to install a custom ROM.
dcarvil said:
When to switch depends entirely on your attitude towards monthly security updates. That would also effect what ROM you consider. Personally I switched about 4 months ago. I chose LineageOS because it reliably receives monthly security updates.
Do you have an unlockable bootloader? If not, all your questions are moot, because you must be able to unlock the bootloader to install a custom ROM.
Click to expand...
Click to collapse
LineageOS was the one recommended to me as well, sounds like a good bet.
"unlockable bootloader" is totally Greek to me though xD. Really have no idea what that means lmao. How might I find out if I have an unlockable bootloader? And if I do... how does one... unlock it? xD
And thanks for the insight!
neat_moss said:
LineageOS was the one recommended to me as well, sounds like a good bet.
"unlockable bootloader" is totally Greek to me though xD. Really have no idea what that means lmao. How might I find out if I have an unlockable bootloader? And if I do... how does one... unlock it? xD
And thanks for the insight!
Click to expand...
Click to collapse
See the "Unlocking the Bootloader" section in this thread. https://forum.xda-developers.com/t/guide-how-to-root-pixel-3-android-12.4366041/#post-86294311
Also, the LineageOS installation instructions have an "Unlocking the bootloader" section. https://wiki.lineageos.org/devices/blueline/install
If you have a Verizon or AT&T variant, you cannot unlock the bootloader.
dcarvil said:
See the "Unlocking the Bootloader" section in this thread. https://forum.xda-developers.com/t/guide-how-to-root-pixel-3-android-12.4366041/#post-86294311
Also, the LineageOS installation instructions have an "Unlocking the bootloader" section. https://wiki.lineageos.org/devices/blueline/install
If you have a Verizon or AT&T variant, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Very cool, thanks! A lot of this documentation makes sense.
Verizon or AT&T variant though... you mean the phone itself? In my case, i bought the phone directly from google and just put an AT&T SIM card into it... is that the same thing?
Thanks!
neat_moss said:
Very cool, thanks! A lot of this documentation makes sense.
Verizon or AT&T variant though... you mean the phone itself? In my case, i bought the phone directly from google and just put an AT&T SIM card into it... is that the same thing?
Thanks!
Click to expand...
Click to collapse
The AT&T variant would be a phone purchased from AT&T. If you purchased it from Google, you probably have the unlockable version. If you can enable the OEM Unlocking toggle, you can unlock the bootloader. Unlocking will wipe your phone, though, so be sure to backup everything you need.
dcarvil said:
The AT&T variant would be a phone purchased from AT&T. If you purchased it from Google, you probably have the unlockable version. If you can enable the OEM Unlocking toggle, you can unlock the bootloader. Unlocking will wipe your phone, though, so be sure to backup everything you need.
Click to expand...
Click to collapse
Thank you much! I'll likely be trying this soon enough
V0latyle said:
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
Click to expand...
Click to collapse
It seems that more v12 releases are coming out. So the initial assumption that the P3 will receive updated v12 builds up till OCT21, doesn't seem to be the case anymore
(although I am not complaining!)
In addition to the OCT21 rels:
SP1A.210812.015
SP1A.210812.016.A1
I can now see JAN22 / FEB22 rels:
SP1A.210812.016.A2
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
After reading some positive feedback on v12, I think I will be updating to that latest version
But I want an 'unbranded' ROM. So it would make sense to go for "SP1A.210812.016.C1", right?
I really hope that if this is one of the last v12 releases for P3, it is at least as stable as my latest v11 build. It would be nice to have those extra privacy features, but stability on that phone is no1 prio...
jstoner said:
It seems that more v12 releases are coming out. So the initial assumption that the P3 will receive updated v12 builds up till OCT21, doesn't seem to be the case anymore
(although I am not complaining!)
Click to expand...
Click to collapse
As I stated previously, Google only committed to 3 years of software updates on most of the Pixel line. The October '21 update was the end of the update agreement for the 3 / 3XL. Interesting that there are January and February releases too.
The 3a and 3aXL will be sunsetted in May of this year.
My Pixel 5 will receive its last update on Oct '23, and my wife's 5a will be supported up to Aug '24.
Software updates on Pixel devices
That being said, Pixel devices use AOSP, so it wouldn't be hard for someone to build updated firmware for the Pixels using the latest AOSP release. Google even makes the driver binaries available. The only caveat to this is that TWRP often doesn't keep up with the newer devices, so the update would have to be in the same format as either an OTA file, or factory image.
V0latyle said:
The October '21 update was the end of the update agreement for the 3 / 3XL. Interesting that there are January and February releases too.
Click to expand...
Click to collapse
Then maybe there was something important on the OCT21 release that needed to be fixed? No idea. I wonder if that FEB22 release is going to be the final one (in which case I d rather wait a bit longer)
Just curious about those:
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
Aren't all those releases supposed to be 'brand-less' (i.e. not associated with any provider)? So what's with that Telstra/Optus/Vodafone AU sidenote on that release?
Am I right in thinking that at the moment, "SP1A.210812.016.C1" is the one to go for? I m only interested in having a retail ROM - just as if I bought the device directly from Google..
jstoner said:
Then maybe there was something important on the OCT21 release that needed to be fixed? No idea. I wonder if that FEB22 release is going to be the final one (in which case I d rather wait a bit longer)
Click to expand...
Click to collapse
Even if there were bugs in the October release, I'm surprised they bothered with January and February too. October '21 is the last one they committed to, any more will be out of the ordinary for them.
jstoner said:
Just curious about those:
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
Aren't all those releases supposed to be 'brand-less' (i.e. not associated with any provider)? So what's with that Telstra/Optus/Vodafone AU sidenote on that release?
Click to expand...
Click to collapse
Baseband fixes, most likely. Bootloader, kernel and system are the same; usually the only difference is the baseband.
jstoner said:
Am I right in thinking that at the moment, "SP1A.210812.016.C1" is the one to go for? I m only interested in having a retail ROM - just as if I bought the device directly from Google..
Click to expand...
Click to collapse
Probably.
V0latyle said:
Even if there were bugs in the October release, I'm surprised they bothered with January and February too. October '21 is the last one they committed to, any more will be out of the ordinary for them.
Baseband fixes, most likely. Bootloader, kernel and system are the same; usually the only difference is the baseband.
Probably.
Click to expand...
Click to collapse
Sorry to bother again - but do you by any chance know where I can find Rel notes for those releases
I would like to see what the changes are e.g. from SP1A.210812.016.A2 to SP1A.210812.016.C1
Are those not supposed to be releases to public? (only for Devs?)
jstoner said:
Sorry to bother again - but do you by any chance know where I can find Rel notes for those releases
I would like to see what the changes are e.g. from SP1A.210812.016.A2 to SP1A.210812.016.C1
Click to expand...
Click to collapse
Pixel Update Bulletins | Android Open Source Project
source.android.com
These are general topics across the board and not device specific so I have no idea what is different in the P3 updates. This article provides more information, looks like it's mainly a security update and bug fixes.
jstoner said:
Are those not supposed to be releases to public? (only for Devs?)
Click to expand...
Click to collapse
No, they're intentional, the February update apparently includes fixes that were supposed to be rolled out in your last "official" update in November '21
V0latyle said:
Pixel Update Bulletins | Android Open Source Project
source.android.com
No, they're intentional, the February update apparently includes fixes that were supposed to be rolled out in your last "official" update in November '21
Click to expand...
Click to collapse
According to that source, that FEB22 update, is almost certainly the last for P3 + P3 XL
And as it turns out, my initial assumption about a major bug fix was actually true - it was the 911 calling issue (which due to life critical scenarios) was handled with priority
So it would seem that SP1A.210812.016.C1 is the one to go for P3. No need to wait further, as there won't be any more rels. From what I also read on Reddit, v12, despite only being introduced for P3, is decent enough. No major bugs so far. So I guess it is stable
For this device that I need it for, stabi is more important than security. Don't know if that changes anything or whether I should not move to v12..