There is two parts to consider I think:
- iOS updates are not reversible (technically it can be done, but for lambda users it's a lost cause).
- Apple is very aggressive towards making users upgrade, nagging indefinitely if there is any available newer version
So, users are very aggressively pushed towards the newer version, can't go back, but their phone becomes less useable, for new features they might not care about. As it is now, not offering the major update to old phones will be a grace in a number of cases.
It would still be nice if users wanting to upgrade can have a path forward, understanding the trade-offs. But users should be less complaining if their device keeps working basically the same way as when they bought it years ago.
I want to be clear that this is a lost cause for effectively everyone: I'm saurik, and, even with access to people like geohot and iH8Sn0w, if you give me a phone that is running a later version of the operating system and ask to downgrade, I'm going to say you need to lobby your congressperson to force Apple to allow that... the only thing that even sort of works is if you had a buggy version of the firmware to start with and did some prep work you can sometimes manage to get a downgrade to work if the firmware you upgrade to (or the bootloader itself) is also buggy... it isn't like it is "just really hard to do because it requires manual labor": it is only possible due to mistakes in Apple's attempts to make sure it can't be done.
The precedent is neither scary nor controversial. The European law says a device should keep functioning for a reasonable amount of time. A car completely breaking apart after 25 months is not normal. A smartphone being insecure is not normal either. Especially not considering how much personal data these contain.
I'd bought an iPad pro just a few months before, and suddenly I couldn't use apps I require (no updates available).
Instead of downgrading to the new-and-busted-iOS version I just sold the friggin iPad (not "fit for purpose") and went back to my ancient iPad (original model). Doesn't get used for browsing the net obviously, but at least that model still works.
My car costs multiple tens of thousands of euro and yet it's still only 24 months (people actually tried this one at a court, failed).
If you bought your Samsung phone in the EU, you will get the 24 month warranty automatically from all EU-native suppliers. Of course if you ship it from somewhere else like the US or Asia, it's very different. If it's from EU, send it in as non-functional.
There are many things that are counter-productive in the EU, this one is probably one of the smallest ones.
Here's a lawyer's take on it [1]. Although I'm not sure if its EU specific or NL specific. According to [2] [3] [4] there are some differences between NL and EU on this account. They specifically mention the car example in those sources, btw.
[1] https://blog.iusmentis.com/2018/09/27/honderden-klachten-ove...
[2] http://www.conformiteit.nl/conformiteit-conformiteitbeginsel...
But devices can never work the same as when they were purchased for two reasons.
1) Running an older OS with the originally shipped apps means that you are exposed to widely known exploits which weren't known when the device was purchased. You may counter that we could mandate security updates for older OSs for x years, but this raises all sorts of practical issues determining what bugs are serious enough for backports, and what effect fixing a security issue has on performance.
2) Third parties don't all have the resources or incentives to support older OSs, and app compatibility or usability is just as likely to drive people to upgrade as a slightly slower phone. This would be a big problem for smaller dev shops, and Apple largely solves it through its smooth but overbearing upgrade process, but even large and successful companies want to minimize the costs of supporting older OSs. MS Office apps for instance require iOS 11 and up. So your phone used to run an older version of Word ok, but 3 years after not upgrading the OS, it no longer does, or it is no longer compatible with MSs upgraded cloud services, or you restore but MS has stopped making a compatible version available on the App Store due to technical and security debt.
What sort of regulatory apparatus is going to adjudicate these issues, and wouldn't uncertainty around it place shackles on innovation?
Regardless, the relatively small fines levied are already behind the curve, and market forces have already pushed Apple to addressing the issue. iOS 12 had a large focus on speeding up older devices, and my soon-to-be 6 year old iPhone 5S seems to run nearly as well as it ever has. Lisa Jackson had a prominent spot during the last keynote declaring that Apple was focusing on increasing device longevity [1] . OS updates are the key to this.
The problem with (1) is now you've completely stagnated the market, and if your competitors choose either of the other options you're left lagging behind and you lose sales.
The problem with (2) is now customers of older phones will be upset that they didn't get the full upgrade for reasons they don't understand. The iPhone 4S and Siri or the iPhone X and Animoji show the reaction you should expect.
The problem with (3) is now you have planned obsolescence and old phones just become throw-away leading to an ecological disaster.
None of these are good options.
I don't see how planned obsolescence via missing bells and whistles present in new phones is any worse than planned obsolescence via all functionality getting slower.
Written on my iPhone 5S (2013) running iOS 8 (2014) - it is still a phone and is just as fast as it was in 2014. Is that planned obsolescence?
No. But it probably has known unpatched vulnerabilities, and you're putting yourself and people around you in danger of a security hack.
It's unfortunate that I can't get security patches. I'm not willing to update to iOS 76 to get the fixes because I don't want to run code that is tested on an A12 on my 5 year old phone, and I don't want to buy a new phone because this one works fine and isn't larger than my hands.
Samsung could trivially provide security updates on old version as Google does most of the heavy-lifting so they have no excuse for recommending upgrades on older, slower phones. Apple doesn't presently have a mechanism for this on iOS, to my knowledge.
Only if they use online services that are taken down; not all apps are like this. Even if they are, it is still a better scenario than throwing the entire phone away because it's unusably slow or unsafe to use due to lack of security fixes.
The new features being talked about are ones that make an old phone slower. I owned an iPhone 5s and updated to the latest iOS version for 4 years and never noticed any slowness. So, basically, (2) means I would miss out on new features because other people complain about slowness that I don't notice.
And every Reddit client ever, or Reddit in general. Shameless amount of cookies and a horribly bloated UI just to do the same thing they were doing 10 years ago with double the client resource usage.
The amazing/sad thing is reddit with other clients can be blazingly fast. I just tried redreader from the f-droid store (android open source store) and using it feels like the content is loaded locally.
Says who, the government? We are talking about court-imposed fines here, not consumer wishes. Do we want a literal slow-software police?
That obvious answer is no, but as I think back on how many times I've been frustrated by some poorly performing piece of shit application over the past year, it's starting to not seem so bad of a solution.
This court case shows that we kinda now already have one.
The phones from 5 years ago already had amazing processors with billions of cycles per second. They can probably do nearly everything.
But you know us software engineers: "make it faster till it runs wells on my test kit, then oh well ship it!"
I think this ruling is a nudge into a better way. Yes deplay updates for more than 2 years, but don't stop optimizing new stuff when the latest phone can run it pretty well - keep optimizing until devices from the last 5 years run it very well.
That's patently wrong. The point of the fine was not that the phones were noticeably slower after the upgrade. The point of the fine was that the slowness was motivated as a way of inducing forced obsolescence. The manufacturers forced the updates with no rollback mechanism to render phones unusable and thus force their users to purchase replacements. If users could roll back the changes then the manufacturers wouldnt be fined.
Yes please!
It's a lot easier to "not write slow software" if you're not constrained by power limitations. Apple went to all the trouble of switching CPU architectures just to get on a better side of that problem.
It's a bit slow on loading, but after that it's really fast !
Also, I remember the calculator app being unreliable due to animations: https://www.macrumors.com/2017/10/24/ios-11-calculator-anima...
Is this not a legitimate problem?
† The google feed seems to have a consistent lag upon switching to it from the home screen (double tap on the multitasking button is normal) that the animations hide. It loads somewhere around 150ms slower than most applications, even taking longer than the first launch for unused apps.
I believe the problem was that the updates made existing functionality slower. e.g. the same Facebook app you had before the update scrolls slower afterwards or the old launcher is replaced with one that's more jittery, without letting you use the old one.
Adding new features is fine, just don't break the old ones.
And in any case: they're free not to offer feature upgrades to old phones; I just doubt that's a wise choice in the market. If they really can't provide a few updates and reasonable performance - good riddance, their successors surely will.
"this update will harm performance but improves security and gives access to new features; your choice" (imagined release note on update clickthrough)
?
A checkbox isn't that hard.
A naive assumption. In fact, each checkbox exponentially increases the number of possible runtime environments you have to maintain and test.
"Installing this update will give you access to feature X, but will slow down your phone."
For comparison, my AT&T Samsung Galaxy S6 forces me to install updates, which I hate. Wasn't my choice to get this particular phone, wouldn't do it again.
This will mean: almost never updates at all.
Well, I have to admit: my mother will be happy about it.
You're leaving out the easy solution though - allow users to "downgrade"! The reason this is such a huge issue isn't that they're giving customers the option to upgrade, it's that they refuse to let you go back if you find out the new version is slow. Additionally, when they break functionality on the old version (looking at you facetime) they need to fix it without forcing you to upgrade to a whole new release. (Issue a patch for JUST THAT).
It also means you lose security updates, and generally hold your platform back. Part of what makes iOS so much better to develop for is the general availability of modern APIs to most of the user base. If you increase those on older versions, then you hold back development of the platform as a whole.
iOS 12 was a major step forward in performance and battery consumption. Moves like that — making it a company priority - are a better way forward than allowing people to go backward.
This isn't a technology or a QA problem, it's vendors refusing to acknowledge that customers own their devices.
It sounds like a terrible user experience.
If you told me it was a fresh OS with no ability to recover your old data, then maybe I could see it. But even then we’re assuming you didn’t use any cloud services that migrated your data once all devices had been upgraded, which isn’t true for either major platform. We’re also assuming that you can downgrade all firmware that’s changed successfully (which is expensive new QA).
I’d rather just have companies really prioritize performance to begin with.
>So you as a user are going to take a backup of os version N, then upgrade to N+1, live on it for a long time, then both want to pay/keep the storage costs of N AND potentially months later downgrade and lose all new data to go back to N?
You realize Apple already does this, right? Backups go to your laptop if you have itunes installed and icloud by default unless you tell it jnot to.
>It sounds like a terrible user experience.
I've literally never heard anyone complain about the experience.
>If you told me it was a fresh OS with no ability to recover your old data, then maybe I could see it. But even then we’re assuming you didn’t use any cloud services that migrated your data once all devices had been upgraded, which isn’t true for either major platform. We’re also assuming that you can downgrade all firmware that’s changed successfully (which is expensive new QA).
What are you talking about? Have you actually used a modern smartphone? When I restore, everything that was in the cloud resyncs. Everything that was local is still local. if my iphone were to blow up tomorrow, and I were to do a restore, it would be no different than a downgrade.
>I’d rather just have companies really prioritize performance to begin with.
Ahh, right, so they should be designing their OS for 4 year old hardware? Or maybe they should just allow users to downgrade, which would require almost 0 effort on their part.
If you restore from a months old backup, then you’ve lost months worth of data. That’s not a great experience if you can’t backup before downgrading, and super hard to explain to the user why. What you may or may not have “heard” is not a good sample size for decision making.
Just because your phone syncs to the cloud doesn’t mean the way that your data is stored is somehow immutable. It’s extremely common to have various “versions” of people’s data (schemas, most likely) that get migrated once all of a users devices have gone into a new version. This was public in a recent version of notes which said new features would only become available once all of one’s Macs were on High Sierra and all iOS devices were on 11. Restoring on a recent version post-migration IS different than a downgrade.
I believe companies should support old hardware, and Apple clearly prioritizes this as well. Moving software forward is important for the whole ecosystem. As I’ve outlined, it is far more than 0 effort to support downgrades.
That's not what's at issue here though. The update was literally along the lines of "if (old phone) then { set_cpu_throttle_threshold(lower); }".
Now the intentions were good, even if paternalistic in that the newer features were more demanding on older devices and throttling in theory was supposed to provide a better user experience with the device under high demand--freezing for 5s instead of crashing and rebooting. But still it was literally a patch to make old devices run slower, which regardless of intention should not be allowed.
Newer iOS updates allow you to disable the CPU throttle. It turns out that "high demand" scenarios that cause the phone to crash can be triggered by mundane actions like taking photos.
If you disallow throttling by law, old devices will just crash all the time.
This was what Apple apologists said when this issue first came to light, but hasn't Apple already shot its own excuse in the foot? iOS 11.3/12.0 came out, removing the throttles, and I haven't seen anything about a rash of phones all constantly shutting off now.
AFAICT, this switch won't affect throttling in other cases, such as near/sub-freezing temperatures.
* this is a pretty complex issue; "throttling" isn't even a great term once you actually start to understand how the power management works
If that's true, it reduces my fear. I know that's true wrt Apple's batteries. But what I read for the OS updates is that they suggested/shipped newer software they knew would degrade the performance as opposed to intentionally degrading it.
As for intentions, while they may have been good (I think it's just easier maintenance to keep one running stable branch), if they were that consumer friendly they would have been more open to the user about the harms of upgrading.
Apple obviously was not intending to harm users here (I don't know the Samsung case well enough to comment), they absolutely messed up the messaging by not making a notice about their work-around front-and-center, but I disagree with the precedent that this fine is setting.
The crashes which were being avoided would only have happened on bad batteries. But the throttling happened in all instances, bad battery or not.
It obviously wasn't an "iOS 12 gimps the iPhone 7" issue - I mean, Apple sells new iPhone 7 phones with iOS 12 on them right now.
A bit of a scary precedent. The 5m fine on Apple for intentionally reducing resource usage to such a large extent without notification seems kinda reasonable. But the 5m fine for both Apple and Samsung for their updates causing slowdown on older devices is a different issue.
If I were a company fearing that suggesting an OS upgrade for an older phone would cause slowdown on that older phone, I am now incentivized to not suggest that update. We might want companies to support old OSs forever or stop adding resource-intensive features or feature gate them or whatever. But short of legislating that specifically, all this does is make old phones even more of a liability than they already were.