Related
I know that 7.1.2 on the Nexus 6 is not supported by Google, but anyone know if any of the developers tried incorporating based on the AOSP 7.1.2 chain?
You realize those are preview builds for the other devices right? Code isn't pushed to AOSP yet AFAIK. I think the highest is 7.1.1_r22
edit: maybe it is? https://android.googlesource.com/platform/system/core/+/android-n-mr2-preview-1
Not worth trying at the moment. The source will change from preview to the final build. It's better to wait until the final build gets pushed out and the full source code reaches aosp. In other words, patience, young grasshopper. We will get custom Roms based on 7.1.2 ?
Arju said:
Not worth trying at the moment. The source will change from preview to the final build. It's better to wait until the final build gets pushed out and the full source code reaches aosp. In other words, patience, young grasshopper. We will get custom Roms based on 7.1.2
Click to expand...
Click to collapse
Thanks gentlemen! I understand you want to base on the final build to hopefully get rid of most of the bugs..
and the big improvements between 7.1.1 and 7.1.2 are what?
Personally I think we all get too excited by these updates. Me, I struggle to see the major differences between Kitkat and 7.1.1 (I'm pretty unobservant, but hey, it's just a communication/entertainment device, yeah?) so although I look forward to playing with the new version I raraly see any killer difference. Android, to my eyes, is about as advanced as it can get until it can actually give me a backrub and a cup of fresh-brewed coffee in the morning. I'm not holding my breath...
dahawthorne said:
Personally I think we all get too excited by these updates. Me, I struggle to see the major differences between Kitkat and 7.1.1 (I'm pretty unobservant, but hey, it's just a communication/entertainment device, yeah?) so although I look forward to playing with the new version I raraly see any killer difference. Android, to my eyes, is about as advanced as it can get until it can actually give me a backrub and a cup of fresh-brewed coffee in the morning. I'm not holding my breath...
Click to expand...
Click to collapse
Are you also blind? Because Kitkat and Nougat are miles apart.
I'm short-sighted. No need to be offensive.
Examples? I can play videos, talk to people, text. What major (and I mean major) differences are there then? It's a phone and communications device. Kitkat did that. Nougat is just icing.
Go on, justify your statement rather than just being offended and offensive.
@admiralspeedy: No, @dahawthorne is right in that the changes in Android recently have been more evolutionary than revolutionary. The last really significant change in Android was switching from Dalvik to ART, which was experimental in Android 4.4.x and enabled in Android 5.x. and up.
Note that Material Design isn't a significant change, and neither is SEAndroid enforcement.
Strephon Alkhalikoi said:
@admiralspeedy: No, @dahawthorne is right in that the changes in Android recently have been more evolutionary than revolutionary. The last really significant change in Android was switching from Dalvik to ART, which was experimental in Android 4.4.x and enabled in Android 5.x. and up.
Note that Material Design isn't a significant change, and neither is SEAndroid enforcement.
Click to expand...
Click to collapse
Everything can't be "revolutionary" and being evolutionary hardly means that there are very few big changes. KitKat is the last iteration of Android to use the Holo theme and now through Lollipop, Marshmallow and Nougat we've had several major improvements to the entire Android interface through material design. The interface changes alone are enough to consider KitKat and anything newer, vastly different. You also mentioned Dalvik to ART, which is a huge change, but you failed to mention proper 64-bit support (beginning with Lollipop), more customization (such as the notification tray toggles), native multi-window, the official fingerprint API, and when the next iteration is released, KitKat will probably be dropped from security patches unless a ton of people are still hanging on to it.
Really the list goes on but I think it's quite ridiculous to say that the evolutionary changes made from KitKat to Nougat are hardly substantial.
But @dahawthorne never said there were no significant changes. All he said is he couldn't see them. As for what you've listed, nothing there is truly significant, not even 64-bit computing. That's not to say they're not welcome or anything like that, but Dalvik to ART is significant because it fundamentally changed how Android worked under the hood.
P. S. Calling other posters blind because you can't see their point? Ironic.
admiralspeedy said:
Everything can't be "revolutionary" and being evolutionary hardly means that there are very few big changes. KitKat is the last iteration of Android to use the Holo theme and now through Lollipop, Marshmallow and Nougat we've had several major improvements to the entire Android interface through material design. The interface changes alone are enough to consider KitKat and anything newer, vastly different. You also mentioned Dalvik to ART, which is a huge change, but you failed to mention proper 64-bit support (beginning with Lollipop), more customization (such as the notification tray toggles), native multi-window, the official fingerprint API, and when the next iteration is released, KitKat will probably be dropped from security patches unless a ton of people are still hanging on to it.
Really the list goes on but I think it's quite ridiculous to say that the evolutionary changes made from KitKat to Nougat are hardly substantial.
Click to expand...
Click to collapse
I think that my point would be best-illustrated by handing two phones (Kitkat & Nougat) to a "normal" user (i.e. non-XDA person interested in using the phone and uninterested in the technology). I can easily imagine the scenario because I'm married to one. She might say that the new icons look nice, and the design is easy on the eye. Dalvik/ART? Couldn't care less. 64-bit? Even *I* couldn't care less. Multi-window? Impractical even on my N6's large screen, and effectively a tech showpiece, a solution looking for a problem. My N6 and my wife's N5 don't have a fingerprint reader, and in any case that's more of a hardware feature requiring software rather than a software feature in its own right. And persuading her to let me install new security versions is like pulling teeth.
I therefore stand full-square behind my original "little difference" statement, because to the "normal" user that's exactly the case.
this thread actually is about differences between 7.11 and 7.12
and, whether you think there are major differences between lollipop, kitkat and nougat, I think we ALL can agree that the differences between a 7.11 os and a 7.12 os will hardly be worth anyone's time to get excited about.
maybe when it moves to 8.0 it will be significant, but a one dot move in ANY OS generally means absolutely nothing
dahawthorne said:
I think that my point would be best-illustrated by handing two phones (Kitkat & Nougat) to a "normal" user (i.e. non-XDA person interested in using the phone and uninterested in the technology). I can easily imagine the scenario because I'm married to one. She might say that the new icons look nice, and the design is easy on the eye. Dalvik/ART? Couldn't care less. 64-bit? Even *I* couldn't care less. Multi-window? Impractical even on my N6's large screen, and effectively a tech showpiece, a solution looking for a problem. My N6 and my wife's N5 don't have a fingerprint reader, and in any case that's more of a hardware feature requiring software rather than a software feature in its own right. And persuading her to let me install new security versions is like pulling teeth.
I therefore stand full-square behind my original "little difference" statement, because to the "normal" user that's exactly the case.
Click to expand...
Click to collapse
Agreed. The average person couldn't care less or even really tell a difference. My gf is the same way. She doesn't even Ike doing the monthly security updates to the point she made disable it lol. As long as it makes calls, texts, Facebook and a few websites then she is happy.
wase4711 said:
this thread actually is about differences between 7.11 and 7.12
and, whether you think there are major differences between lollipop, kitkat and nougat, I think we ALL can agree that the differences between a 7.11 os and a 7.12 os will hardly be worth anyone's time to get excited about.
maybe when it moves to 8.0 it will be significant, but a one dot move in ANY OS generally means absolutely nothing
Click to expand...
Click to collapse
l2tp protocol should be fixed in 7.1..2 according to issue #196939. it is something i was waiting for almost two years.
never heard of that, never read about that, have no clue about that, and you wont find any discussion about it on XDA, so, its not an issue that is at the forefront in anyone I knows mind...
wase4711 said:
never heard of that, never read about that, have no clue about that, and you wont find any discussion about it on XDA, so, its not an issue that is at the forefront in anyone I knows mind...
Click to expand...
Click to collapse
This is true that you are not seeing talks about it but just because you dont see anything said about it on XDA doesnt mean it is not in the forfront of anyones mind.
Talks like that really arent dont in the threads anymore but in private chats. 99% of any real development talks are done away from users these days.
As for 7.1.2 this will start to get really hard as this is when 32bit support dies and all of Google code is for 64 bit chips. Developers are already starting to see the change over and soo it will be true death for 32 bit devices. As porting it backwards is almost not conceivable.
To be honest, 32-bit supports won't go away, in fact it's required. Why? ARM Cortex A35 and A7 CPUs which will be here to stay, even though it's obviously true that industry and ROM developers are moving to 64-bit support (ie. AARCH64 AKA ARM64 mode) - ie. Cortex A53 and up to A73, the 32-bit ARM processors will still be used for many years to come, obviously for embedded battery life reasons, like Android Wear.
Otherwise, Nexus 6 will be my last 32-bit device (I know Android Oreo will still come onto Nexus 6 via Lineage OS, obviously because it will still support 32-bit mode for some reasons - Android Wear is based on full-blown Android OS, so if you remove 32-bit mode support, you risk breaking the watch ecosystem). I am kind of torn between ASUS ZenFone AR or Pixel 2. Hard choice.
Dr. Mario said:
To be honest, 32-bit supports won't go away, in fact it's required. Why? ARM Cortex A35 and A7 CPUs which will be here to stay, even though it's obviously true that industry and ROM developers are moving to 64-bit support (ie. AARCH64 AKA ARM64 mode) - ie. Cortex A53 and up to A73, the 32-bit ARM processors will still be used for many years to come, obviously for embedded battery life reasons, like Android Wear.
Otherwise, Nexus 6 will be my last 32-bit device (I know Android Oreo will still come onto Nexus 6 via Lineage OS, obviously because it will still support 32-bit mode for some reasons - Android Wear is based on full-blown Android OS, so if you remove 32-bit mode support, you risk breaking the watch ecosystem). I am kind of torn between ASUS ZenFone AR or Pixel 2. Hard choice.
Click to expand...
Click to collapse
Just because those chips are here doesnt mean the OS has to support it. Plus with the adaption rate of devices, by the time that it would matter 99% of devices will already being running a 64 bit chip.
Look at it this way. Google only works on code for their base devices. All 64bit.
As of LOS. If they dont have a base to work from then it will be very hard indeed.
They will not risk that. It is already in the works if you think about it. Only the n6 is a 32bit device that google supports. So they already have it setup for 64bit to work with the watch.
If you watch google source code you will see the transition.
True, but who knows, as of now? Google occasionally pull the surprises (I don't trust commit notes from certain companies such as Google, they occasionally put too much eggs into a basket - recent Nexus and Pixel muck-ups proves that), so it's possible they would either continue with transition or just cancel it and stick with hybrid builds. It's now more of a wait and see thing.
Serious question: Since the N6 is EOL, why would Google/Moto develop a new radio and bootloader and push it out with a security update? That seems like a fair amount of support for an EOL device.
I don't know for certain, but from what I remember the nexus 6 had some serious problems with the 7.0 update. Maybe this is the remedy?
joeh258 said:
I don't know for certain, but from what I remember the nexus 6 had some serious problems with the 7.0 update. Maybe this is the remedy?
Click to expand...
Click to collapse
I can't imagine it with 7.0. I've been running 7 since the day it released, never any issues. I have heard that 7.1.1 has had issues, however. So perhaps it is in regards to that??
cameraddict said:
Serious question: Since the N6 is EOL, why would Google/Moto develop a new radio and bootloader and push it out with a security update? That seems like a fair amount of support for an EOL device.
Click to expand...
Click to collapse
Google is still patching security vulns, and will be for some time. We are EOL but Google is hard at work making Android more secure to compete with
Apple and Samsung for the big money corporate / government sales.
https://source.android.com/security/bulletin/2017-04-01.html
Pkt_Lnt said:
Google is still patching security vulns, and will be for some time. We are EOL but Google is hard at work making Android more secure to compete with
Apple and Samsung for the big money corporate / government sales.
https://source.android.com/security/bulletin/2017-04-01.html
Click to expand...
Click to collapse
Yes, of course, I understand this. But I'm curious why the radio and bootloader?? Maybe I just never paid attention before, but I don't ever remember this being the case with a security update in the past, with any of the devices I've owned.
I browsed that link, I didn't see anything that seemed to pertain to patches to the radio or bootloader.
cameraddict said:
Yes, of course, I understand this. But I'm curious why the radio and bootloader?? Maybe I just never paid attention before, but I don't ever remember this being the case with a security update in the past, with any of the devices I've owned.
I browsed that link, I didn't see anything that seemed to pertain to patches to the radio or bootloader.
Click to expand...
Click to collapse
Just some WAG on my part but this seems related to the bootloader.
https://source.android.com/security/verifiedboot/verified-boot
Bootloader requirements
The bootloader is the guardian of the device state and is responsible for initializing the TEE and binding its root of trust.
Most importantly, the bootloader verifies the integrity of the boot and/or recovery partition before moving execution to the kernel and display the warnings specified in the section Boot state.
Click to expand...
Click to collapse
And these seem related maybe? (I'm just an old cell phone tech from the 90s-00s who is still an armchair geek.)
https://source.android.com/security/bulletin/2017-04-01
Radio?
Elevation of privilege vulnerability in Telephony
An elevation of privilege vulnerability in the Telephony component could enable a local malicious application to access capabilities outside of its permission levels. This issue is rated as Moderate because it could be used to gain access to elevated capabilities, which are not normally accessible to a third-party application.
CVE References Severity Updated Google devices Updated AOSP versions Date reported
CVE-2017-0554 A-33815946 [2] Moderate All 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 D
Click to expand...
Click to collapse
Bootloader?
Information disclosure vulnerability in Factory Reset
An information disclosure vulnerability in the factory reset process could enable a local malicious attacker to access data from the previous owner. This issue is rated as Moderate due to the possibility of bypassing device protection.
CVE References Severity Updated Google devices Updated AOSP versions Date reported
CVE-2017-0560 A-30681079 Moderate All 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1
Click to expand...
Click to collapse
Pkt_Lnt said:
Just some WAG on my part but this seems related to the bootloader.
https://source.android.com/security/verifiedboot/verified-boot
And these seem related maybe? (I'm just an old cell phone tech from the 90s-00s who is still an armchair geek.)
https://source.android.com/security/bulletin/2017-04-01
Radio?
Bootloader?
Click to expand...
Click to collapse
Ya know... I didn't see the bottom of the page that had all of the actual threats addressed. I think I may have had a partial page load problem (been having wifi/ISP issues lately).
So, yeah, it seems that the lines you pulled out make sense! Thanks for taking the time to go through it more thoroughly!
Peace
Hi. I've got an Australian Note 9 XSA unit and have recently updated to Pie. Not a fan of the layout at all and would like to rollback to Oreo. I've downloaded Oreo from Updato however before I flash via Odin, I was wondering if it's safe to reflash back and if so, do I apply all parts of the firmware (AP, BL, CP, CSC, HOME CSC)?
Seems that a downgrade in odin is fine. Odin won't flash anything anyway if it cant so feel free to try. As long as its the relevant firmware for your device and region then it's fine.
But whats the point in downgrading? From here on forward, there won't be any other UI for your Note 9 then OneUI. Of course you can flash a custom rom, but on the "official" channel, you won't get around it. You could stay on 8.1. and december 2018 security patch as long as you want, but that also means you'll leave your device unprotected against certain types of "new" malware.
I also considered downgrading because I really don't like the new UI. It feels slower, looks a bit weird sometimes and the recents menu is a mess. The only good thing I can see is the gesture navigation. But then I thought, why should I downgrade? At a certain point of time I will update my phone and EVERY new update for the Note 9 will be with OneUI.
What's bad about the layout? Must be nice to have already gotten the pie update. Still waiting here in the US. Should of just bought a older phone so you wouldn't have to worry about updates anymore.
Sent from my SM-N960U using Tapatalk
OberstGrausam said:
But whats the point in downgrading? From here on forward, there won't be any other UI for your Note 9 then OneUI. Of course you can flash a custom rom, but on the "official" channel, you won't get around it. You could stay on 8.1. and december 2018 security patch as long as you want, but that also means you'll leave your device unprotected against certain types of "new" malware.
I also considered downgrading because I really don't like the new UI. It feels slower, looks a bit weird sometimes and the recents menu is a mess. The only good thing I can see is the gesture navigation. But then I thought, why should I downgrade? At a certain point of time I will update my phone and EVERY new update for the Note 9 will be with OneUI.
Click to expand...
Click to collapse
I am also in the same camp; thinking not to upgrade at all..... but I can't assess how real the threat of malware is or indeed the potential of any kind of damage
LolwutMikka said:
Hi. I've got an Australian Note 9 XSA unit and have recently updated to Pie. Not a fan of the layout at all and would like to rollback to Oreo. I've downloaded Oreo from Updato however before I flash via Odin, I was wondering if it's safe to reflash back and if so, do I apply all parts of the firmware (AP, BL, CP, CSC, HOME CSC)?
Click to expand...
Click to collapse
If you do downgrade, you must select csc_oxm for reset.
---------- Post added at 07:50 AM ---------- Previous post was at 07:47 AM ----------
It usually uses csc_home for update and csc_oxm for downgrade, while the other ones select them normally, bl, ap, cp.
william-johnson said:
I am also in the same camp; thinking not to upgrade at all..... but I can't assess how real the threat of malware is or indeed the potential of any kind of damage
Click to expand...
Click to collapse
That line of thinking sounds weird to me...
You're savvy enough to be on XDA but are oblivious to IT security on a basic level?
tl;dr: threat is real, upgrade. And yes, personally not a fan of One UI either, but I'm waiting for the update so I can get it over with.
I basically never operate my smartphones with just one hand, so most of the changes don't help me and instead make stuff look funny or too rough.
I'll just set UI and font to the smallest size like I do on every mobile OS and pray that it looks half as bad as it does with normal settings.
Sent from my Samsung SM-N960F using XDA Labs
I'm thinking of down grading.
The only feature I like is the raise to wake and night mode.
I used an app for night theme before the upgrade and maybe I can just deal with the loss of wake.
If I'm stuck on December security so what? I've never had malware on a phone yet only a rogue app that I had to uninstall.
Depends what you like I suppose
need to find out this for purchase
Probably not
Gunnerabsek said:
need to find out this for purchase
Click to expand...
Click to collapse
I don't think so
Because Samsung only provides 2 android updates
Note 8 already got oreo and pie update so forget it.
Maybe in future someone can possibly cook a android q custom rom compatible with our note 8.
Trex888 said:
I don't think so
Because Samsung only provides 2 android updates
Note 8 already got oreo and pie update so forget it.
Maybe in future someone can possibly cook a android q custom rom compatible with our note 8.
Click to expand...
Click to collapse
Was Treble just an 8.1 thing then? Never had one of those devices and haven't had any of the newer samsung's until recently. I imagine we can't use it because of some signature check on the system partition that doesn't allow a generic AP? Because I thought 9.0 was supposed to be even more compatible with treble, or maybe I haven't looked into it in awhile.
I imagine we are really just at the tip of the iceberg still on using Safestrap to customize Stock 9.0 to it's fullest potential. I haven't gotten that far yet as far as Using Safestrap on Stock Pie. I'm trying to up my exploit game somehow. I understand the PoC's and the high level descriptions, and thus how things could maybe be chained together, but I'm not a low enough level coder yet. My Linux game is still a little weak sauce. By the time I'm done with Rev 5 Nougat root I might understand the environment enough to implement my ideas a little bit though.
But if we can use Safestrap to install a Stock 9.0 Build that also includes Safestrap then that does mean we should have quite a bit of leeway to get Q Roms backported, even if they aren't rooted. Didn't we do this for the Galaxy S5? I'm just saying, the security bulletins posted in the last 8-9 months do seem to show a path towards root through something like a User Controlled C&C Platform. It wouldn't be a stereotypical full root everyone thinks of, but it would get the foot in the door like dirtycow did.
To start though, we like to use busybox for a lot of things, but our devices natively use toybox, and toolbox. Samsung hasn't used busybox for anything, so us putting it there and usurping control from toybox is an automatic red flag. The device recognizes and accepts toybox over busybox naturally. I feel like we have a better chance of getting a modified or user controlled version of toybox onto the device than we do busybox or standard supersu. I don't think Pie was planned for in the code before CF left us. Because didn't we have to change over to sbin for a lot of things in Oreo? Maybe we actually just need a new path altogether. System Root seems to have had the best success in recent generations, but what elliwigy did on the Note9 is a good concept to start with I think.
Maybe I'm just crazy a bit, but we've seen that traditional root method keep getting harder and harder to use and new methods are very few and far between anymore. I just keep putting the concepts out in hopes others can put some dots together.
Bought this on Android 11 in Early 2021.
Currently on Android 12.
What version of Android will we be going up to?
Where does Samsung post the future/intended updates schedule?
Is it going to be Android 14 as the last version?
Android 12 - Late 2021
Android 13 - Late 2022
Android 14 - Late 2023 --> Last update?
Samsung promised 3 major Android updates and 4 years of security updates. Usually, as time passes and device becomes older, it slips down in priority for os updates. So while we got the A12 update (half cooked or not) at the top of Samsung's list, older phones eligible for the same are going to recieve it a little later, depending on how old they are. So A13 may come in early 2023 instead of Dec 2022 (when the S22U starts getting it) and A14 may come a little later in 2024. By that time the S23U will be in front of the line for A14.
I must admit that Samsung has really stepped up its game when it comes to pushing updates (I'm talking quantity here, quality is another matter) to its devices, both new and old. And they may actually improve the update situation for older devices if things go really well. Only time will tell.
But im fairly sure we'll get timely security updates till the end of 2024.
enigmaamit said:
Samsung promised 3 major Android updates and 4 years of security updates. Usually, as time passes and device becomes older, it slips down in priority for os updates. So while we got the A12 update (half cooked or not) at the top of Samsung's list, older phones eligible for the same are going to recieve it a little later, depending on how old they are. So A13 may come in early 2023 instead of Dec 2022 (when the S22U starts getting it) and A14 may come a little later in 2024. By that time the S23U will be in front of the line for A14.
I must admit that Samsung has really stepped up its game when it comes to pushing updates (I'm talking quantity here, quality is another matter) to its devices, both new and old. And they may actually improve the update situation for older devices if things go really well. Only time will tell.
But im fairly sure we'll get timely security updates till the end of 2024.
Click to expand...
Click to collapse
Meanwhile, the iPhone 6S and 6S Plus arrived in September 2015 running iOS 9.
It is currently on iOS 15.3!
That's 7 years!
IMO, this phone deserves to go up to Android 15! But, alas, 'tis only scheduled for going up to 14!
nixnixnixnix4 said:
Meanwhile, the iPhone 6S and 6S Plus arrived in September 2015 running iOS 9.
It is currently on iOS 15.3!
That's 7 years!
IMO, this phone deserves to go up to Android 15! But, alas, 'tis only scheduled for going up to 14!
Click to expand...
Click to collapse
I tend to agree that this would be very nice.
My feeling is that this is due to the pretty closed Apple ecosystem. They have everything in their own hand (hardware and software), thus its much easier for them to maintain compatability between both for longer time.
For Android the OS is evolving separately and is then spread out to all the hardware platforms out there - this is much more prone to create incompatabilities over time. Thus the shorter period of maintenance here.....
s3axel said:
I tend to agree that this would be very nice.
My feeling is that this is due to the pretty closed Apple ecosystem. They have everything in their own hand (hardware and software), thus its much easier for them to maintain compatability between both for longer time.
For Android the OS is evolving separately and is then spread out to all the hardware platforms out there - this is much more prone to create incompatabilities over time. Thus the shorter period of maintenance here.....
Click to expand...
Click to collapse
They better lower their prices significantly then AND give 5 years of updates.
At this rate. the iPhone 10 will be supported beyond 2027, despite being released in 2017.
nixnixnixnix4 said:
They better lower their prices significantly then AND give 5 years of updates.
At this rate. the iPhone 10 will be supported beyond 2027, despite being released in 2017.
Click to expand...
Click to collapse
True enough !
I think in the end this topic may be one of the key differentiators between Android and IOS and, depending on preferences, may trigger a buying decision. This may also in the end push Android phone makers to move towards longer maintenance cycles..... On top of that I personally think its heavily advisable from an ecological standpoint !
nixnixnixnix4 said:
They better lower their prices significantly then AND give 5 years of updates.
At this rate. the iPhone 10 will be supported beyond 2027, despite being released in 2017.
Click to expand...
Click to collapse
With all the talk of increasing phone prices and plateauing phone performance, iPhones seem to have a lower cost of ownership per year if you look at the duration for which they are officially supported, despite the high initial cost. 'Technically' the only thing that degrades over time is the battery, which can be replaced fairly easily - even multiple times. But reality is sometimes different. I had an iPhone 6S until a year ago. New battery, 100% health. But it wasn't as good as it was on older iOS versions. Every update added a few features but somehow killed it a little bit. Just enough to keep it functional, but a little more limpy than before.
Getting new updates for years is amazing, but whether the OS updates add to the phone ownership experience or subtract from it is the thing to see here. If new OS updates slow down the phone or degrade battery life, isn't it better to stay on the OS version that is best optimised for that particular device during its peak years? And just get security patches, without messing around with OS version?
Updates nowadays seem to be a coin toss for most major version upgrades, both on iOS as well as Android. And usually the older phones suffer most. Sometimes a new major OS update almost cripples a phone. My OnePlus 6 worked so well on A10, till A11 borked it! Fortunately i was able to revert back. Apple doesn't even allow downgrading the OS after a short period (signing). Same with Android rollback prevention. Sometimes you're stuck with a bad 'upgrade' with no way to end the nightmare, except get a new device.
However, all said and done, apple neuters it's phones a lot less when compared to most Android manufacturers.
I've become very wary of updating software on anything nowadays unless there's an issue I need fixed or a new feature that I'm willing to risk anything for.
enigmaamit said:
Samsung promised 3 major Android updates and 4 years of security updates. Usually, as time passes and device becomes older, it slips down in priority for os updates. So while we got the A12 update (half cooked or not) at the top of Samsung's list, older phones eligible for the same are going to recieve it a little later, depending on how old they are. So A13 may come in early 2023 instead of Dec 2022 (when the S22U starts getting it) and A14 may come a little later in 2024. By that time the S23U will be in front of the line for A14.
I must admit that Samsung has really stepped up its game when it comes to pushing updates (I'm talking quantity here, quality is another matter) to its devices, both new and old. And they may actually improve the update situation for older devices if things go really well. Only time will tell.
But im fairly sure we'll get timely security updates till the end of 2024.
Click to expand...
Click to collapse
You are in a dream. Woke up. Most of us we stop updating our phones after first update. I learn my lesson, after every samsung update something is broken or feature taken away. When you buy a new phone, you have to rooted and fix yourself what you need, otherwise you are stuck in a loop hole with updates, fixes, waiting till next month for fix . I never update my s20 ultra and working smoothly and better than s21 ultra with stupid android 12 and other updates
mihaiccccv said:
...Most of us we stop updating our phones after first update....
Click to expand...
Click to collapse
I'm not sure that's entirely accurate. What you describe isn't what 'most' people follow. It's just a minority of tech enthusiasts who can figure out how to block updates. Everyone else just follows the system prompt.
enigmaamit said:
I'm not sure that's entirely accurate. What you describe isn't what 'most' people follow. It's just a minority of tech enthusiasts who can figure out how to block updates. Everyone else just follows the system prompt.
Click to expand...
Click to collapse
I know that is a minority, and I think most of the people who access XDA know what they doing or looking to learn. With all the information available here, you cannot stay androind sheep and dance how tech companies wants. I just love how android world it's define by developers " we are willing to share "
OK. So, apparently, Samsung is promising 4 OS generation updates with 5 years of security updates.
So, the S21 series will be going to Android 15.
I'll replace this phone in early 2025 then.