Related
It's pretty clear that the road forward for CyanogenMod is a dead end at this point. While it's no huge loss for me (been running a stock Stylo 2 Plus lately, and my Relay is just a backup and occasional wireless camera controller at this point), I wouldn't mind switching out ROMs on the Relay, at least if there's something still maintained.
I was afraid something like this would happen to CM once Microsoft got its grubby little paws into the picture. Looks like Cyanogen effectively got Elop'd just like Nokia did.
A month or so back, I was getting ready to buy my wife and myself a pair of new phones to replace our Relays. I was basing my selection on CM-14.1 support. Things got confusing, and I postponed the whole matter until some time next year. Boy, and I glad I delayed.
Of course I still have to select a replacement for the Relay - one that is really supported for the long run - which may still push me into something CM-like. Now to figure out what that is.
Well if you want to be safe just go Nexus, only the Nexus one and Nexus s have lost support, galaxy Nexus and up still has developers not to mention google will support each for 2 years plus
Other safe bets are the real popular devices such as galaxies and even the OnePlus community
If you want a hardware keyboard I would suggest to learn development as you will always be limited and haven't seen one with good support since HTC g2
Hi there, why not port Ubuntu Touch? I did read that it is quite easy to port ubuntu touch to cyanogenmod supported phones...
I'm still in the process of learning how to do that... but there are no real reference on doing that and building/brewing a rom would be my first.
You certainly could but I'm not sure if that ever works too well with a HW keyboard, at that point may as well move on.
There are many of options on what to bring over but few still use phones like these, in truth i haven't touched any of my 5 hw keyboard phones in at least two/three years, i miss them but have learned to live without...
But i did just read BlackBerry has a new one soon, may not get much support though, priv was a bit of a bust...
*sigh* i know you are right. Beginning this year i started using the Nokia e7 Communicator again on custom Symbian ROM. After a few not solveable problems i imported the Relay short after as my last ray of hope. Is it that dificult as a manufacturer to build a landscape slider with 5 key rows? Just one decent powered would be enough. I don't care if i use QNX, Android, iOS or Windows Mobile, the phone is just a phone for me. I don't need 5 thousand sounboard fart apps..... god damn...
Make last Relay build available???
It appears that Cyanogenmod is offline, so nothing new is coming - ever. That said, I'd seen that things were going to go offline at the end of the year, and was rather hoping to pick up the "auto-integration" of the final AOSP merges into CM-11. I'm assuming this happens, because I don't believe any person has touched this since TDM left at the end of July.
I'm currently running a nightly I built on Dec 3 of this on my wife's and my phones, and have had no problems. I'm willing to make this build available for anyone who wants a small update for their Relay.
There's another question... How do I find out the date of the final update? I ran my build script again this morning, and got a result, but since the CM servers are dead, I suspect it just ran through its paces. I know that the Dec 3 built I'm running carries a date of 20161126 and an Android security patch level of November 1, 2016.
My last builds are very little different in file sizes, but as I sift through the build directory, I see a bunch of stuff with a Dec 15 date, so I believe I may have picked up some fixes on that build. I see that the servers actually went offline apparently on Dec 25, which also matches some of the date stamps I see in my build tree.
So - Can someone tell me a distinctive spot in my build tree where I can find out what the actual date of this stuff is? I suppose I'm going to try flashing this build one of these days, to see if there is anything better than what I've got on the phone now. If so this will be the last, best build of CM-11 for the Relay.
I will make one or both of these builds available, if there is interest. I'm not quite sure how to do that, where, etc. I have a basic Dropbox account, though I see that they will be phasing out the Public folder in April. That's a start, or I'm open to suggestions.
phred14 said:
Make last Relay build available???
It appears that Cyanogenmod is offline, so nothing new is coming - ever. That said, I'd seen that things were going to go offline at the end of the year, and was rather hoping to pick up the "auto-integration" of the final AOSP merges into CM-11. I'm assuming this happens, because I don't believe any person has touched this since TDM left at the end of July.
I'm currently running a nightly I built on Dec 3 of this on my wife's and my phones, and have had no problems. I'm willing to make this build available for anyone who wants a small update for their Relay.
There's another question... How do I find out the date of the final update? I ran my build script again this morning, and got a result, but since the CM servers are dead, I suspect it just ran through its paces. I know that the Dec 3 built I'm running carries a date of 20161126 and an Android security patch level of November 1, 2016.
My last builds are very little different in file sizes, but as I sift through the build directory, I see a bunch of stuff with a Dec 15 date, so I believe I may have picked up some fixes on that build. I see that the servers actually went offline apparently on Dec 25, which also matches some of the date stamps I see in my build tree.
So - Can someone tell me a distinctive spot in my build tree where I can find out what the actual date of this stuff is? I suppose I'm going to try flashing this build one of these days, to see if there is anything better than what I've got on the phone now. If so this will be the last, best build of CM-11 for the Relay.
I will make one or both of these builds available, if there is interest. I'm not quite sure how to do that, where, etc. I have a basic Dropbox account, though I see that they will be phasing out the Public folder in April. That's a start, or I'm open to suggestions.
Click to expand...
Click to collapse
I think we all as the last battalion of the Galaxy S Relay 4g would really appreciate if you could share your build. :fingers-crossed:
I just loaded today's build, though I haven't tested it much yet.
The Cyanogenmod version is 11-20161129-UNOFFICIAL-apexqtmo
The Android security patch level is Nov 1, 2016
The Kernel version is Sat Dec 24 15:10:38 EST 2016
So I guess I didn't get a new AOSP, nor new CM-11. But I did get a new kernel? I'd built a few times between then and now, so it looks like that's that.
I'll do a bit of testing with this one, then see if I can get it up to Dropbox Public, even if only for a quarter.
phred14 said:
I just loaded today's build, though I haven't tested it much yet.
The Cyanogenmod version is 11-20161129-UNOFFICIAL-apexqtmo
The Android security patch level is Nov 1, 2016
The Kernel version is Sat Dec 24 15:10:38 EST 2016
So I guess I didn't get a new AOSP, nor new CM-11. But I did get a new kernel? I'd built a few times between then and now, so it looks like that's that.
I'll do a bit of testing with this one, then see if I can get it up to Dropbox Public, even if only for a quarter.
Click to expand...
Click to collapse
Hi phred14, sorry to bother. Did you manage to upload that last nighly? Can you tell me if everything you test works? In the past I tried CM and was having issues with Mic, GPS and Camera, so i revert to stock.
Thanks in advance!
ninguno2 said:
Hi phred14, sorry to bother. Did you manage to upload that last nighly? Can you tell me if everything you test works? In the past I tried CM and was having issues with Mic, GPS and Camera, so i revert to stock.
Thanks in advance!
Click to expand...
Click to collapse
Yes, it's uploaded to my Google Drive with public access. I uploaded both Dec 4 and Dec 29 versions. I did a bit of specific testing with GPS and Camera on the Dec 4 version, but have not tested those functions on the Dec 29. I'm running Dec 29 now, so it does what I need - acts like a phone, texts, does wifi, and does stuff over data - and I don't know that any other functions don't work.
Do you have GPS working now? I believe that there was a specific "era" that borked the GPS in a persistent way. If you did that, which I did, you need to backflash to stock, or at least JB, then there is a procedure for flashing new. I've done this, and have working GPS.
The links to my stuff are on a separate thread under "Development", titled "Lineage OS", which is the successor to CM. We can discuss more if you're still interested. I can also take my current flash and do a bit more testing, when I have time. (Maybe not soon - we're getting work done on the house, and are in the process of moving out for a few weeks.)
phred14 said:
Yes, it's uploaded to my Google Drive with public access. I uploaded both Dec 4 and Dec 29 versions. I did a bit of specific testing with GPS and Camera on the Dec 4 version, but have not tested those functions on the Dec 29. I'm running Dec 29 now, so it does what I need - acts like a phone, texts, does wifi, and does stuff over data - and I don't know that any other functions don't work.
Do you have GPS working now? I believe that there was a specific "era" that borked the GPS in a persistent way. If you did that, which I did, you need to backflash to stock, or at least JB, then there is a procedure for flashing new. I've done this, and have working GPS.
The links to my stuff are on a separate thread under "Development", titled "Lineage OS", which is the successor to CM. We can discuss more if you're still interested. I can also take my current flash and do a bit more testing, when I have time. (Maybe not soon - we're getting work done on the house, and are in the process of moving out for a few weeks.)
Click to expand...
Click to collapse
Hi phred14, thanks for the quick answer.
Yes, my GPS is working great in JB (I'm using the last offical stock 4.1.2 T699UVBOH1_T699TMBBOH1_TMB), so I suppose i don't need a special procedure for the gps, right?
I already found the links you mention, as I understand from your answer, the camera works ok with the Dec 4 version? Can you tell me if the mic works ok with the version you're running? I remember that when using CM in the past, voice notes that i sent with whatsapp were muted (or tooo quiet) showing that the mic wasn't working. Reverting back to JB fix that too, as with the GPS.
Do you have some kind of updated guide/procedure/backup you follow before flashing CM, being I'm still at stock rom (i remember there was one on the old CM wiki)? I would really like to test your CM following the right steps.
Besides, i found another post you made about modem fixes (https://forum.xda-developers.com/showpost.php?p=63925086&postcount=20) is that still needed? As the link for RelayMC5modem.zip file is not working.
Best,
phred14 said:
A month or so back, I was getting ready to buy my wife and myself a pair of new phones to replace our Relays. I was basing my selection on CM-14.1 support. Things got confusing, and I postponed the whole matter until some time next year. Boy, and I glad I delayed.
Of course I still have to select a replacement for the Relay - one that is really supported for the long run - which may still push me into something CM-like. Now to figure out what that is.
Click to expand...
Click to collapse
Try going for something that's supported by LiquidSmooth or other custom ROMs. CM was the best, no doubt. There will always be options.
That's the beauty of Android as an OS. I'm proud of my contribution and maybe I might do more in the future. Albeit in a lesser light than FB, I see Google as a info hog.
Among devices, you should try either Nexus or older, unlocked Samsung devices.
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
Hey guys,
Just a quick question just noticed on Lineage OS download page that the Nvidia Shield Tablet is not supported anymore? Anyone has heard any news about this? Searched around google but have not found anything Its funny i have a build of lineage os still on my system wondering if its worth installing it.
Update: I checked the Lineage thread yeah it looks like they stopped supporting it hopefully with more people on board support will be open again. Anyways for those who are looking for the final build for the April update which was the last updated before support was pulled i added the link to where to download. Have fun!!
https://mega.nz/#!EJlViC5S!-NljBExnLn9F2EEQd6JI93j5nJlnzES1j2J4Ddcc8O4
Contents:
Lineage 15.1
MindTheGapps 8.1
TWRP 3.3.1
Go read the lineage thread in the last page and if you could share that same build I would be gratefull.
Disrupthor said:
Go read the lineage thread in the last page and if you could share that same build I would be gratefull.
Click to expand...
Click to collapse
Here you go check the post as i updated it as well with the list of contents.
https://mega.nz/#!EJlViC5S!-NljBExnLn9F2EEQd6JI93j5nJlnzES1j2J4Ddcc8O4
I thought they just started officially supporting it again recently. Guess it didn't last very long.
I wish Nvidia would release a new Shield Tablet. By far the best Android device I've ever owned.
A pretty bad memory leak was found in the 15.1+ builds. Until a fix for that is made, there won't be any more official releases. Fwiw, not everyone is affected badly by it. But when I have to reboot every couple days just using a browser, a couple chat clients, and an ssh client? Yeah, I'm not going to call that stable and sign off on a release. But I haven't stopped work, no. And don't plan to either.
looking fwd to the next build!
Hello guys,
Im new on this phone. im confused i have some question.
Some of news websites say that the Official OS 10 for OP7 series will be released this month.. what does that mean ?
now i have 10.0.1 and Beta 3 was released 2-3 days ago why ?
what are differences between 10.0.1 and 10 beta 3?
can you explain it guys ?
10.0.1 is stable...
The beta program showcases potential features and fixes that could be merged into stable.
Beta 3 is a work in progress...
For those of us who know what Beta software is, can anyone give detailed differences?
I'm getting frustrated with the Android auto bugs (resets theme every time you connect, randomly disconnects). Hoping they're fixed in beta 3?
skymera said:
10.0.1 is stable...
The beta program showcases potential features and fixes that could be merged into stable.
Click to expand...
Click to collapse
Super helpful post here defining a beta and stable.
You really think the Op didn't know the technical differences of the 2 definitions?
Come on man, he's obviously asking about specific features. Saying this **** isn't helpful.
Imyeltekin said:
Hello guys,
Im new on this phone. im confused i have some question.
Some of news websites say that the Official OS 10 for OP7 series will be released this month.. what does that mean ?
now i have 10.0.1 and Beta 3 was released 2-3 days ago why ?
what are differences between 10.0.1 and 10 beta 3?
can you explain it guys ?
Click to expand...
Click to collapse
I'll be honest, I completely missed Beta 3. Just hopped on 10.0.1. I'll switch back to beta at 4
xxBrun0xx said:
For those of us who know what Beta software is, can anyone give detailed differences?
I'm getting frustrated with the Android auto bugs (resets theme every time you connect, randomly disconnects). Hoping they're fixed in beta 3?
Click to expand...
Click to collapse
After having tried both the beta 3 (What I'm currently using) as well as 10.0.1 they are the same, except for a few testing features. There is a new work balance mode that randomly appears disappears in the quicksettings menu. I think it's supposed to be India only. The Android auto theme bug isn't fixed. There's also some minor crash fixes for SUPER specific situations, like what's app notification settings causing crashes. There's also a few new options with Zen mode and game mode. Mostly just experimental stuff
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..