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..
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...
Motorola has finally started the Nougat soak test in Brazil. Let's hope it won't take too long for them to release the final version. However, the screenshots say it's Android 7.0 and not 7.1. Also, to make us believe it's really happening, we can have a look at the comments posted below the post. Few comments say they have received it and it's working smooth as of now.
Source: http://www.androidpit.com.br/teste-nougat-moto-x-force-e-style-comecarao-em-breve
Update 1: Motorola send out soak test invitations to US users
Update 2: Android Headlines reports Moto X Style Is Receiving Android 7.0 Nougat In India
Update 3: Moto X Style and X Pure Nougat update spotted on GFXBench (Yes, again. The last time it was spotted on 7.1 was in last week of December.)
Update 4: A user on reddit who is located near Chicago states he received the Nougat update.
Soak test is going on in India also.
This is a good news !!!!!!
soak test is only available for limited users and if anyone who will break their rules will be out of the soak test permanently so don't expect that someone might just end up sharing the files !! all we need to do is just wait for that moment when it gets as stable as a daily driver and we all are good to go
its most likely 7.0 but i hope we get a 7.1.1 or 7.1.2
Why not get it now?
Google "AICP clark"
I've been running it since Dec 2015 on Republic Wireless with no problems.
I got bored waiting for official nougat and went to AICP 7.1
It's pretty good, can't see myself going back to stock tbh
Put me down for Dirty Unicorns. Last things for me were camera functioning well (which it seems to be if using OpenCamera) and torch working well (which it seems to be improved).
Sagar_1401 said:
its most likely 7.0 but i hope we get a 7.1.1 or 7.1.2
Click to expand...
Click to collapse
no chance for that
iks8 said:
no chance for that
Click to expand...
Click to collapse
Doesn't matter so much. We're interested in the N blobs, i think they are the same between 7.0 and 7.1. this will at least mean better custom ROMS
josdehaes said:
Doesn't matter so much. We're interested in the N blobs, i think they are the same between 7.0 and 7.1. this will at least mean better custom ROMS
Click to expand...
Click to collapse
Even on this forum not everyone is interested with custom roms. I used to mod my phones a lot but thoose were crapy low end devices and custom roms were really adding some performance but with this phone I don't see a reason to install custom rom. Even on my old moto e I went back to stock after trying few roms, moto software is really well made imo, so it's sad that their updates are way slower than they used to be and that they relase already obsolete software ;\.
btw from my expierience there is always something broken in custom roms, and if it's not broken now it will be in next relase xd
iks8 said:
Even on this forum not everyone is interested with custom roms. I used to mod my phones a lot but thoose were crapy low end devices and custom roms were really adding some performance but with this phone I don't see a reason to install custom rom. Even on my old moto e I went back to stock after trying few roms, moto software is really well made imo, so it's sad that their updates are way slower than they used to be and that they relase already obsolete software ;\.
btw from my expierience there is always something broken in custom roms, and if it's not broken now it will be in next relase xd
Click to expand...
Click to collapse
I'm with you here. I have no desire leave the stock ROM for any reason other than updates. It's been bug-free and smooth sailing for me with Motorola's software ever since 2015, no doubt because they stick to AOSP.
The only way I'd be interested in a custom ROM is if the developers were on a very long release cycle where they spent months ironing out every tiny bug before tinkering with new things, similar to how OEMs approach stock ROMs. That seems rare these days, though I don't follow things too closely anymore. "Man this ROM is amazing... except, oh yeah, Bluetooth breaks and requires a reboot... oh, and calls drop a lot... and, uh, call volume randomly goes to max/silent for no reason... oh yeah, and MMS just doesn't show up sometimes, and the camera crashes every 3rd open requiring another reboot" seems to be the way of the world, and I don't have patience for it. Putting up with random bugs can be worth it if it frees you from TouchWiz or Sense or LG UI, but when the stock ROM is already AOSP and fast/fluid, I don't see the point.
http://www.androidauthority.com/moto-x-style-pure-edition-nougat-758023/
I have to agree that stock rooted ROMs are my way of going now. Of course that also means I won't buy from makes like Samsung who overburden their ROMs with too much frill. Besides, with manufactures like one plus, the is really no reason to revert.
good news
ptn107 said:
Google "AICP clark"
I've been running it since Dec 2015 on Republic Wireless with no problems.
Click to expand...
Click to collapse
I'm on RW too. Are you using a certain version that's working good? I just don't wanna messed up my service, but would love to try 7.1.1.
Sent from my SM-P600 using XDA-Developers Legacy app
Official Android 7.0 Nougat out for Moto X Style (Pure) in India and Brazil
AsquareX said:
Motorola has finally started the Nougat soak test in Brazil. Let's hope it won't take too long for them to release the final version. However, the screenshots say it's Android 7.0 and not 7.1. Also, to make us believe it's really happening, we can have a look at the comments posted below the post. Few comments say they have received it and it's working smooth as of now.
Saw the same on another website this morning. I wonder how long after the soak test that it will be released in the US?
Click to expand...
Click to collapse
About time. I see that the Android O developer preview is out and we don't even have 7.0 yet. Grrr!
strafer69 said:
About time.
Click to expand...
Click to collapse
not really, it's way too late imo. Start of soak test doesn't mean a lot, I guess in some regions you will have to wait like more than month since now, I guess everyone willl get it in may as it was said before, that's way too long for not so old flagship phone... We should have 7.0 already and 7.1 in may but it's not going to happen ;\ shame on you moto
iks8 said:
not really, it's way too late imo. Start of soak test doesn't mean a lot, I guess in some regions you will have to wait like more than month since now, I guess everyone willl get it in may as it was said before, that's way too long for not so old flagship phone... We should have 7.0 already and 7.1 in may but it's not going to happen ;\ shame on you moto
Click to expand...
Click to collapse
Not Moto's fault. Blame it all on Lenovo, as the Moto's work force is pretty much non-existent.
Rmsalt said:
AsquareX said:
Saw the same on another website this morning. I wonder how long after the soak test that it will be released in the US?
Click to expand...
Click to collapse
Honestly, a while... It usually goes Brazil, India, Europe, then US and UK (sometimes US/UK flip-flop). To be honest, Lenovo doesn't see the US as a major market, these phones are not carrier subsidized so their market penetration is minimal at best. US is always the last to get Moto (Lenovo) updates in the last 12-18 months. Not likely to see that change anytime soon. Each region will have it's own beta if history repeats, we are at minimum 2-3 months out in the US.
Click to expand...
Click to collapse
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.
I think LineageOS official is near.... I've found interesting information about polaris
https://review.lineageos.org/#/q/topic:polaris-bringup+(status:open+OR+status:merged)
can't wait
Still early stages, not even buildable yet
Going to bring an old thread back to life. Especially with Lineage 16.0 on its way out, do we have anyone attempting to build for this phone?
I'm not sure I've ever owned a phone with this little developer support.
15.1 device tree wont be finished , we have jumped straight to 16.0.
YazumiWuHung said:
15.1 device tree wont be finished , we have jumped straight to 16.0.
Click to expand...
Click to collapse
Oh! Thanks, didn't realize we had dev's looking into it. Thanks for your work.
gogogo....would not have thought that the difference to "mi mix 2" is so big
tom65824 said:
gogogo....would not have thought that the difference to "mi mix 2" is so big
Click to expand...
Click to collapse
Official support for Lineage hasn't been updated since July. I wouldn't hold your breath.
Yeah last update was August on 16.0
https://review.lineageos.org/#/q/project:LineageOS/android_device_xiaomi_polaris
andyphone said:
Yeah last update was August on 16.0
https://review.lineageos.org/#/q/project:LineageOS/android_device_xiaomi_polaris
Click to expand...
Click to collapse
As far as I can tell the 2 polaris repos were deleted off of their GitHub today
aeppacher said:
As far as I can tell the 2 polaris repos were deleted off of their GitHub today
Click to expand...
Click to collapse
This one still exists....
https://github.com/LineageOS/android_device_xiaomi_polaris
and here ?
https://www.getdroidtips.com/lineage-os-15-1-xiaomi-mi-mix-2s/
official?
tom65824 said:
and here ?
https://www.getdroidtips.com/lineage-os-15-1-xiaomi-mi-mix-2s/
official?
Click to expand...
Click to collapse
No, its not official. Its a treble system image. You can probably download a more updated version at the Treble-enabled device development forum.
This thread seems to be a collection of random guesses. Is there any actual source of information on the status of an official build for the Mix 2s? Surely if someone were working on it, they would post something somewhere... Not trying at all to be demanding or complain, but I would like to know if there is a reasonable chance of a release at some point.
I have until Oct. 15 to return this device. It's an outstanding phone with a PoS operating system. Without going into a big rant about miui 10, I don't want to own a phone where text messages are unreliable using anything but xiaomi's crappy (and likely invasive) messaging app.
Xar99 said:
This thread seems to be a collection of random guesses. Is there any actual source of information on the status of an official build for the Mix 2s? Surely if someone were working on it, they would post something somewhere... Not trying at all to be demanding or complain, but I would like to know if there is a reasonable chance of a release at some point.
I have until Oct. 15 to return this device. It's an outstanding phone with a PoS operating system. Without going into a big rant about miui 10, I don't want to own a phone where text messages are unreliable using anything but xiaomi's crappy (and likely invasive) messaging app.
Click to expand...
Click to collapse
I broke my cardinal rule with this handset: never buy hardware based upon the promise of future software updates because they may not ever happen.
I think if it was being worked on we would have heard by now. Devs just seem disinterested in the device.
andyphone said:
This one still exists....
Click to expand...
Click to collapse
The one andyphone linked above has quite a few commits since Oct. 1 (today, even). Good sign?
Los 16.0 should come eventually. Seems like a very capable developer is working on our device right now!
There may not be any official announcement yet, but you can easily see that work to bring up LineageOS for the Mix 2S is still underway here: https://github.com/LineageOS/android_device_xiaomi_polaris.
The last commit to this Mix 2S-specific repository was a day ago.
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