Related
I switched from Cyanogenmod 13.0 to LineageOS 14.1 when CM died in late December. Was very excited about Nougat at first, but there are a lot of bugs with mobile data, bluetooth, etc. After a couple months of flashing nightly builds hoping for things to get better, I gave up and went back to the last build of CM13 and all the bugs have disappeared and my battery life improved as well. Plus I can use Xposed which is nice.
Only problem is CM13 will never be updated so I'm stuck on December 2016 security patch level. Thus I am steadily getting more outdated. With no official Nougat ever coming to the G3, it makes me wonder if the bugs in LOS14.1 will ever be fixed since there will never be an official source to base it on. I know there are other Nougat-based roms out there but I imagine they must suffer from the same bugs as LineageOS.
I don't care about new features or anything, I just would like to have security updates because it seems like a bad idea not to.
Is this what I'm looking for? https://forum.xda-developers.com/20...nt/rom-lineageos-13-0-moto-g-3rd-gen-t3530402
Consider this - most folks with Moto G3 are on stock M. With no security updates.
With CM13 you say you are on Dec '16. That's a year and a half better than stock.
Maybe you aren't really so bad off...
Have you ever really felt any real harm having "outdated" security patch? I'm kin to hear exact cases when your phone needs a new security patch. Or maybe you are installing experimental software from deep web? There are a lot of users with devices with Android 5.0.2 or 5.1 that haven't even heard about security patches, and they feel themselves very comfortable using their daily package of normal and verified software. So I don't see any point to look for a developing MM 6.0.1 ROM, as it is already developed and bugless.
Mama Luigi said:
I switched from Cyanogenmod 13.0 to LineageOS 14.1 when CM died in late December. Was very excited about Nougat at first, but there are a lot of bugs with mobile data, bluetooth, etc. After a couple months of flashing nightly builds hoping for things to get better, I gave up and went back to the last build of CM13 and all the bugs have disappeared and my battery life improved as well. Plus I can use Xposed which is nice.
Only problem is CM13 will never be updated so I'm stuck on December 2016 security patch level. Thus I am steadily getting more outdated. With no official Nougat ever coming to the G3, it makes me wonder if the bugs in LOS14.1 will ever be fixed since there will never be an official source to base it on. I know there are other Nougat-based roms out there but I imagine they must suffer from the same bugs as LineageOS.
I don't care about new features or anything, I just would like to have security updates because it seems like a bad idea not to.
Is this what I'm looking for? https://forum.xda-developers.com/20...nt/rom-lineageos-13-0-moto-g-3rd-gen-t3530402
Click to expand...
Click to collapse
mokee is in active development
I too had this confusion....all marshmallow roms stopped development and i never wanted to try any N rom coz i thought its not stable. i tried many nougat roms and they all had many bugs...... But now I'm settled for tesla rom......its a great rom and havent found any bugs...... Its the fastest rom among N roms....... I'm using it with optimus kernel and battery backup is also very good......
https://forum.xda-developers.com/2015-moto-g/development/rom-gzroms-tesla-t3350265
KrisM22 said:
Consider this - most folks with Moto G3 are on stock M. With no security updates.
With CM13 you say you are on Dec '16. That's a year and a half better than stock.
Maybe you aren't really so bad off...
Click to expand...
Click to collapse
A January 2017 security patch for the stock 6.0 XT1540 just came out just a few weeks ago.
Mama Luigi said:
I don't care about new features or anything, I just would like to have security updates because it seems like a bad idea not to.
Click to expand...
Click to collapse
The misconception here is that those "security updates" are actually of any real world use... they are not. There are no real security exploits of any real significance to modern Android devices, all of these horrible vulnerabilities like Quadrooter, Certi-gate, Stagefright, FakeID, Towelroot, and Dirty Cow are of not really problems as outside of a controlled lab environment, there are no working exploits of any of them.
Security updates by themselves are a marketing ploy that sounds good, unless your devices is 3 or 4 years old (in which case you should just be replacing it anyway since there are no security updates).
A lot of people will disagree with me, but all these security updates are just media hype and company propaganda, there is no real worry about them because of all the other stuff we have in Android, like app sandboxing, DMverity, SElinux, and other mechanisms that even if an exploit does get past one things it has to deal with the others.
I am not an naive and I know what I am talking about, I have worked in the telecommunications and networking industry for over 25 years and deal with security in both telecom and IT daily. You have far more important things to worry about than security updates for your Android phone, unless you live on pirate apps and porn.
georgearn said:
Have you ever really felt any real harm having "outdated" security patch? I'm kin to hear exact cases when your phone needs a new security patch. Or maybe you are installing experimental software from deep web? There are a lot of users with devices with Android 5.0.2 or 5.1 that haven't even heard about security patches, and they feel themselves very comfortable using their daily package of normal and verified software. So I don't see any point to look for a developing MM 6.0.1 ROM, as it is already developed and bugless.
Click to expand...
Click to collapse
acejavelin said:
The misconception here is that those "security updates" are actually of any real world use... they are not. There are no real security exploits of any real significance to modern Android devices, all of these horrible vulnerabilities like Quadrooter, Certi-gate, Stagefright, FakeID, Towelroot, and Dirty Cow are of not really problems as outside of a controlled lab environment, there are no working exploits of any of them.
Security updates by themselves are a marketing ploy that sounds good, unless your devices is 3 or 4 years old (in which case you should just be replacing it anyway since there are no security updates).
A lot of people will disagree with me, but all these security updates are just media hype and company propaganda, there is no real worry about them because of all the other stuff we have in Android, like app sandboxing, DMverity, SElinux, and other mechanisms that even if an exploit does get past one things it has to deal with the others.
I am not an naive and I know what I am talking about, I have worked in the telecommunications and networking industry for over 25 years and deal with security in both telecom and IT daily. You have far more important things to worry about than security updates for your Android phone, unless you live on pirate apps and porn.
Click to expand...
Click to collapse
Thanks guys. No, I haven't felt "unsafe" from not being totally updated, but if you were unsafe would you even know it? Isn't that part of the problem? At any rate, I suppose the real danger isn't my phone's OS but rather my online accounts, where my personal information is stored on the servers of who knows how many companies.
Between ad blocking and just careful habits and knowledge, I'm guessing I'm also much safer than the average smartphone user.
I will keep rolling with cm13 unless/until Alberto hammers out the Bluetooth bugs in Lineage. Nougat is cool but it's not worth my headphones disconnecting multiple times per day.
Maybe this reply is off topic, but as far as my xt1550 is considered, all bugs related to data and Bluetooth have been fixed.
Regarding the "staying updated" thing, maybe you will have to jump to Nougat one day or the other if you want to increase the life of the phone.
Okay, strategy question for you. I've recently purchased the U12+, and I am loving it so far. However, I am concerned about security patches / support for the next year or so. It seems to me that if you want the best experience with patching, it's Pixel, Android One, or Essential / Sony. I am not terribly concerned about major releases, though I know we'll be getting Pie at some point.
If patching can be done after google releases them, that's all good with me... but I *think* they need to go through the vendor before they come to @LeeDroid ROM's etc... Is that true?
If so, I may need to move on... or is there hope with Android One via Treble?
charlatan01 said:
Okay, strategy question for you. I've recently purchased the U12+, and I am loving it so far. However, I am concerned about security patches / support for the next year or so. It seems to me that if you want the best experience with patching, it's Pixel, Android One, or Essential / Sony. I am not terribly concerned about major releases, though I know we'll be getting Pie at some point.
If patching can be done after google releases them, that's all good with me... but I *think* they need to go through the vendor before they come to @LeeDroid ROM's etc... Is that true?
If so, I may need to move on... or is there hope with Android One via Treble?
Click to expand...
Click to collapse
One will never come to the U12+.
Security patches are not for all devices, so if it is not unsecure there is no need for a patch.
But before it is included in leedroid HTC has to release a new base with the patches included.
Except some special patches that are baken into custom Kernels.
diamond09 said:
One will never come to the U12+.
Security patches are not for all devices, so if it is not unsecure there is no need for a patch.
Click to expand...
Click to collapse
I'm sorry, but that is just not true. Every month there are android updates, and they are NOT device specific.
Security bulletin for July.
If you're not getting monthlies, you're at risk, however small that may be.
charlatan01 said:
I'm sorry, but that is just not true. Every month there are android updates, and they are NOT device specific.
Security bulletin for July.
If you're not getting monthlies, you're at risk, however small that may be.
Click to expand...
Click to collapse
HTC includes most patches from upcoming security patches in their "older" one...like in june patch, there are patches for july etc included. that's why HTC only patches and has most of the time an older date, because they only patch necessary stuff. if they would implement everything, even the bugs from google they would have the newest date, but also a lot more to do, which is stupid, wasting time and money
Also got to take into account. Google test, creates, and updates security issues with their software build. AOSP/Pixel software. HTC and Samsung for example make significant changes to Android. Some of which are the fixes that Google either told them about or the other way around.
As mentioned before and past history has shown. HTC tends to release and fix security issues before Google does. I'm not saying HTC software is perfect, but some security might not apply to manufactures that make significant changes to Android.
But generally I believe that some things would be better if security updates came straight from Google. Android already is build around a module concept. Maybe they can do something similar concerning security patches. Peace of mind etc.
Tachi91 said:
Also got to take into account. Google test, creates, and updates security issues with their software build. AOSP/Pixel software. HTC and Samsung for example make significant changes to Android. Some of which are the fixes that Google either told them about or the other way around.
As mentioned before and past history has shown. HTC tends to release and fix security issues before Google does. I'm not saying HTC software is perfect, but some security might not apply to manufactures that make significant changes to Android.
But generally I believe that some things would be better if security updates came straight from Google. Android already is build around a module concept. Maybe they can do something similar concerning security patches. Peace of mind etc.
Click to expand...
Click to collapse
android Q changes those things. each phone released with android Q will have a generic system image (GSI), so they can be used straight from google, that'S why security updates will come directly from google and the OEM can update the vendor apart from it and also maybe patch the system with "modules" so you can still have htc sense, touchwiz or whatever comes with the phone
I wonder why after roughly 3 years Still no one showing interest in developing a custom rom for our first grade phone? Before they claimed that it is on pause because no has the kernel source code, but now we have access to the official source code and yet no one developed a brand new custom rom for Nokia phone.
Please if anyone could help write a comment below.
to be honest, at this point i simply dont care whatever is happening in this community. If you have knowledge of building a custom rom then why not giving it a go?
i simply dont possess the knowledge at the same time i am also not complaining.
Ok, so first: Nokia 8 launched in September 2017. According to my calculator, thats roughly one and a half year since it came out. Not three.
Then, regarding kernel sources: The official kernel sources for our phone are from the Oreo 8.0 release. It's possible to use older kernels for newer ROMs, but it is really not recommended. And I am not even speaking of the fact that those official kernel sources still require edits to even work. There is no support from Nokia / HMD for development on this phone. Even their unlocker app doesn't work on the majority of versions and completely broke after 2 security patches.
I would be suprised if you can find any developer who is willing to spend their time fighting the stuff that gets thrown between our feet. (broken kernel source, not being able to temporary boot images and having to flash them instead, no working kernel sources from hmd, no reliable bootloader unlock, no official rescue tool etc. etc.) And usually, developers make things because their either need them themselves, or for the joy of creating something and sharing it with people who appreciate it. And when you can port a ROM, you can make the edits you want for yourself with Magisk, so reason 1 is already not applicable.
And as hard as it might sound, this community is by no means large enough to justify porting a ROM you dont need and risking your device stability / userdata in the process.
So the TL;DR; is probably: Either do it yourself, or expect it to never actually happen, as harsh as it sounds, sadly.
THMSP said:
Ok, so first: Nokia 8 launched in September 2017. According to my calculator, thats roughly one and a half year since it came out. Not three.
Then, regarding kernel sources: The official kernel sources for our phone are from the Oreo 8.0 release. It's possible to use older kernels for newer ROMs, but it is really not recommended. And I am not even speaking of the fact that those official kernel sources still require edits to even work. There is no support from Nokia / HMD for development on this phone. Even their unlocker app doesn't work on the majority of versions and completely broke after 2 security patches.
I would be suprised if you can find any developer who is willing to spend their time fighting the stuff that gets thrown between our feet. (broken kernel source, not being able to temporary boot images and having to flash them instead, no working kernel sources from hmd, no reliable bootloader unlock, no official rescue tool etc. etc.) And usually, developers make things because their either need them themselves, or for the joy of creating something and sharing it with people who appreciate it. And when you can port a ROM, you can make the edits you want for yourself with Magisk, so reason 1 is already not applicable.
And as hard as it might sound, this community is by no means large enough to justify porting a ROM you dont need and risking your device stability / userdata in the process.
So the TL;DR; is probably: Either do it yourself, or expect it to never actually happen, as harsh as it sounds, sadly.
Click to expand...
Click to collapse
I can't agree with you more, I was just wondered how this newly released phone still has no custom rom while my LG G3 still after those years received many from lots of developers.
So sad to see our beloved NOKIA has no juice to compete in this race.
error748 said:
I can't agree with you more, I was just wondered how this newly released phone still has no custom rom while my LG G3 still after those years received many from lots of developers.
So sad to see our beloved NOKIA has no juice to compete in this race.
Click to expand...
Click to collapse
We all found out the hard way what Nokia was about by being early adopters. To me they are only interested in pushing their next device and Android One is making that easier for them. So much so the 8 is long since off their radar. It was an 'OK' phone for the money, but there's better now and it's them I'll be looking to this year.
At this point its best to just modify the current stock rom yourself by debloating it, installing kernel tweking modules via magisk, installing themes via substratum and customizing the interface using GravityBox and Xposed Edge. Thats the closest we will come to having a custom rom experience. Ive accepted that no developer will bother with this phone given all the devices that have come out since its release.
Its a lesson learnt. I love this phone but I will never buy another Nokia phone ever again. Im currently saving up for a Xiaomi phone and will use this Nokia 8 as a secondary phone in due time.
MDV106 said:
At this point its best to just modify the current stock rom yourself by debloating it, installing kernel tweking modules via magisk, installing themes via substratum and customizing the interface using GravityBox and Xposed Edge. Thats the closest we will come to having a custom rom experience. Ive accepted that no developer will bother with this phone given all the devices that have come out since its release.
Its a lesson learnt. I love this phone but I will never buy another Nokia phone ever again. Im currently saving up for a Xiaomi phone and will use this Nokia 8 as a secondary phone in due time.
Click to expand...
Click to collapse
Poco or 1+ here
MDV106 said:
At this point its best to just modify the current stock rom yourself by debloating it, installing kernel tweking modules via magisk, installing themes via substratum and customizing the interface using GravityBox and Xposed Edge. Thats the closest we will come to having a custom rom experience. Ive accepted that no developer will bother with this phone given all the devices that have come out since its release.
Its a lesson learnt. I love this phone but I will never buy another Nokia phone ever again. Im currently saving up for a Xiaomi phone and will use this Nokia 8 as a secondary phone in due time.
Click to expand...
Click to collapse
Me too, my next phone would be OnePlus 6T or Oppo.
Never ever ever go around nokia phones again
Howdy all! I've dug out a couple old Nexus 5's that I stopped using a while back when I got PH-1 and am looking to reflash one of them for a friend who needs a phone and can't afford to buy new. When I was using them last I was running LineageOS 14.1. I'd like to set him up with something stable that he can use as a daily driver for a while and was looking for suggestions. It looks like a ton of ROMs have been updated and I was hoping someone could point me in the right direction for a good current setup that will be easy on the battery and have the most features without compromising stability. Is there a commonly accepted "best" Nexus 5 build? I'm good at following directions, but a lot of the technical stuff is over my head, so trying to research everything I've missed for the last couple years is making my head spin lol. Any assistance would be greatly appreciated!
Stable ROM for Nexus 5
Hey,
I have found AOKP to be really good for my Nexus 5. It has the stability of Lineage 14.1, but also has a few nice little additions: OMS support for Substratum, customisable navbar, a few tweaks here and there. And it is still being developed, and receives regular updates.
Not too heavy on the fancy stuff, so for me it's a nice tradeoff between "stock" AOSP/Lineage, and a few little enhancements.
Also the Nexus 5 is officially supported by the developers, which is important to me.
I've tried Android O and Android P ROMs on my Nexus 5, but I still find Nougat ROMs seem to run the best.
I also have a Nexus 7 (2013) tablet, and the ROM is also available for that as well. As I have OCD, I "need" both my phone and tablet to run the same system, and AOKP gives me this.
Just my suggestion, anyway. Give it a try, and see what you think.
Cheers
Shaun
Thanks! I will check it out
if you like simpler thing i would suggest LOS 14.1 even tho our hammerhead are not supported officially you can use unofficial build by razorloves here https://forum.xda-developers.com/showpost.php?p=80268653&postcount=3145 or another one here https://forum.xda-developers.com/showpost.php?p=80210774&postcount=3 they updated it once a month at least with security updates each months
also if you want tor try LOS 14.1 CAF you can try this https://forum.xda-developers.com/showpost.php?p=80340013&postcount=753
I also have a Nexus 5 laying around that I mostly use as an extra device to test apps on. However, since my apps usually require working Bluetooth LE and other network related stuff, I have refrained from using Android Oreo and Pie based ROMs since I always read that there's some issues with this or that.
I have stayed with the latest Lineage OS 14.1 (Android 7.1.2) and it has worked pretty well. However, I have now decided to move to something a little bit fresher, but still based on Nougat. I went with the AOKP suggestion made by @shaunoleary since they are still releasing official builds. Unfortunately the AOKP's security patch level is still on February 2019.
If want something with a more up-to-date security patch level you can also try these LineageOS 14.1 builds: https://forum.xda-developers.com/go...opment/rom-cm14-1-nexus-5-hammerhead-t3510548 which are supposed to be on September 2019 security patch level.
petersaints said:
I also have a Nexus 5 laying around that I mostly use as an extra device to test apps on. However, since my apps usually require working Bluetooth LE and other network related stuff, I have refrained from using Android Oreo and Pie based ROMs since I always read that there's some issues with this or that.
I have stayed with the latest Lineage OS 14.1 (Android 7.1.2) and it has worked pretty well. However, I have now decided to move to something a little bit fresher, but still based on Nougat. I went with the AOKP suggestion made by @shaunoleary since they are still releasing official builds. Unfortunately the AOKP's security patch level is still on February 2019.
If want something with a more up-to-date security patch level you can also try these LineageOS 14.1 builds: https://forum.xda-developers.com/go...opment/rom-cm14-1-nexus-5-hammerhead-t3510548 which are supposed to be on September 2019 security patch level.
Click to expand...
Click to collapse
Hey Peter - thanks for the nod
I acknowledge that AOKP's security patch level is a bit dated, but having used LineageOS for a long time, I found some of the features AOKP throws into Lineage, I'm willing to sacrifice that for the extra goodies AOKP offers.
I have decided to stick to Nougat for as long as I can. I tried Oreo and Pie, and had noting but trouble with Bluetooth. It's such a shame when they bring out such a solid, stable release of Android like Nougat, and then stop supporting it because it's not "the latest".
Just as an aside, I have recently been using MicroG (Nanodroid package) instead of GAPPS on my N5 (and my N7 2013 as well), and have found it to be very usable now. Google Pay does not work, but aside from that, I get much better battery life than using GAPPS. In fact, my location accuracy seems to be better, and I've got Play Store working a treat.
Hi there, I have the same problem, my N5 stayed on last security patches from the official rom in Feb 2019. Then Lineage ended official support. Did someone try to install the unofficial version (made by razerlove) over the last official build. Would that work? Any hints?
I've tried them all it seems, having acquired dozens of units a few years back .. Im serious, i think im absurdly qualified to make this recommendation.
Hundreds of ROMs/kernels/use cases.
Maybe something is fast and beautiful, until you install more than a few apps, and then it chokes. Maybe it works great with most carriers but not the one you have. My point is that nexuses that aren't working get reformatted and a winnowing occurs.
And gradually a winner emerged. I now have this on 90% of n5s.
If you must have android 9, I recommend floko, but my #1 n5 ROM is
crdroid 7.1.2 LOS caf
with opengapps
and truesight 4.4 caf kernel ,
although the one it installs is fine.
https://forum.xda-developers.com/go...ent/rom-crdroid-release-weekend-t3182013/amp/
---------- Post added at 12:11 PM ---------- Previous post was at 12:07 PM ----------
Oh, and I dont know if it fits without the UA repartition mod, but I can attest to it working since I've modified most units with the mod at this point.
ha7msterx said:
I've tried them all it seems, having acquired dozens of units a few years back .. Im serious, i think im absurdly qualified to make this recommendation.
Hundreds of ROMs/kernels/use cases.
Maybe something is fast and beautiful, until you install more than a few apps, and then it chokes. Maybe it works great with most carriers but not the one you have. My point is that nexuses that aren't working get reformatted and a winnowing occurs.
And gradually a winner emerged. I now have this on 90% of n5s.
If you must have android 9, I recommend floko, but my #1 n5 ROM is
crdroid 7.1.2 LOS caf
with opengapps
and truesight 4.4 caf kernel ,
although the one it installs is fine.
https://forum.xda-developers.com/go...ent/rom-crdroid-release-weekend-t3182013/amp/
Click to expand...
Click to collapse
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..