Or more devious, intentionally bricking the phone to push more people to upgrade. You know those mandatory updates for 7-8 years aren’t popular with manufacturers.
I think Occam’s razor applies more here; The simplest explanation is often the correct one. Why does a multi-billion corp ship a broken update? Even if testing is on the back burner, profit margins are the ultimate reason. Less testing to save money or intentionally busted to force upgrades to make more money.
At this point I just want Linux driver support from manufacturers and let the community handle features.
It’s Android, so yeah… minus the AI slop. I’ve never heard anyone say Android is “vibe coded.” Same with Windows, but Microslop has been touting AI coding for a while.
So, Android… AOSP (Android Open Source Project) is developed by Google, then Samsung forks it. “Fork” is a bad word within the Android communities as the popular blogs whitewash the term (they mostly say skin, some say theme, but you should know what software forking is if you — anyone — wish to speak with any authority about software development), but that’s what happens. Samsung forks the code. So OneUI is sort of a port of Android to the Samsung hardware. Then, unlike Google and Apple, Samsung has dozens if not hundreds of configurations, so they then port OneUI to all the different devices. This is why Google and Apple keep their devices few and similar, it’s much easier to maintain (and even then, they still make mistakes sometimes).
The S22 is a flagship, but it’s also like four generations back (the S26 is about to be announced, but it’ll be out this year/season/quarter/whatever). (No hate, I still have an S10! That’s from 2019!)
So yeah, it was probably tested… via automation, very quick overview, and it’s entirely possible they missed something.
I would not go so far as to say they want to brick S22s to push S26 sales, but I wouldn’t put that past any OEM… including Apple.
(Disclosure of bias: Android user since 2010, iPhone user since 2016, my daily driver is an iPhone 16 Pro Max. I’ve used Android phones from like half a dozen OEMs and I’ve dabbled in custom firmware (always flashing, never coding). I’ve rooted, I’ve broke bootloaders, I’ve broke whole phones, I’ve used all kinds of Xposed modules, I’ve evaded root detection… but I’m tired, boss… which is why I main an iPhone. Still maintain an old Android phone and I still like Android, though. It’s not that I like Apple more. It’s that I’ve been around long enough to see the fault in all of them. They’re all shit. Pick the one you can put up with.)
Do they not test their shit before pushing it to everyone? Or is it just like Windows made with 30% AI
Or more devious, intentionally bricking the phone to push more people to upgrade. You know those mandatory updates for 7-8 years aren’t popular with manufacturers.
“Never attribute to malice that which is adequately explained by stupidity.”
I think Occam’s razor applies more here; The simplest explanation is often the correct one. Why does a multi-billion corp ship a broken update? Even if testing is on the back burner, profit margins are the ultimate reason. Less testing to save money or intentionally busted to force upgrades to make more money.
At this point I just want Linux driver support from manufacturers and let the community handle features.
Isnt the simplest explanation they made a mistake?
I think it’s worse - they probably have dozens of software and hardware revisions. Testing one doesn’t guarantee proper behavior on others
It’s Android, so yeah… minus the AI slop. I’ve never heard anyone say Android is “vibe coded.” Same with Windows, but Microslop has been touting AI coding for a while.
So, Android… AOSP (Android Open Source Project) is developed by Google, then Samsung forks it. “Fork” is a bad word within the Android communities as the popular blogs whitewash the term (they mostly say skin, some say theme, but you should know what software forking is if you — anyone — wish to speak with any authority about software development), but that’s what happens. Samsung forks the code. So OneUI is sort of a port of Android to the Samsung hardware. Then, unlike Google and Apple, Samsung has dozens if not hundreds of configurations, so they then port OneUI to all the different devices. This is why Google and Apple keep their devices few and similar, it’s much easier to maintain (and even then, they still make mistakes sometimes).
The S22 is a flagship, but it’s also like four generations back (the S26 is about to be announced, but it’ll be out this year/season/quarter/whatever). (No hate, I still have an S10! That’s from 2019!)
So yeah, it was probably tested… via automation, very quick overview, and it’s entirely possible they missed something.
I would not go so far as to say they want to brick S22s to push S26 sales, but I wouldn’t put that past any OEM… including Apple.
(Disclosure of bias: Android user since 2010, iPhone user since 2016, my daily driver is an iPhone 16 Pro Max. I’ve used Android phones from like half a dozen OEMs and I’ve dabbled in custom firmware (always flashing, never coding). I’ve rooted, I’ve broke bootloaders, I’ve broke whole phones, I’ve used all kinds of Xposed modules, I’ve evaded root detection… but I’m tired, boss… which is why I main an iPhone. Still maintain an old Android phone and I still like Android, though. It’s not that I like Apple more. It’s that I’ve been around long enough to see the fault in all of them. They’re all shit. Pick the one you can put up with.)