4 ms·
To be clear, Google did the right thing here. Xiaomi proposed an evil user-hostile patch, which Google refused to merge.
by josephcsible 4y ago
To be clear, Google did the right thing here. Xiaomi proposed an evil user-hostile patch, which Google refused to merge.
- mistrial9 4y ago> evil user-hostile patch I do not doubt you, but that is not a fact-based statement. Can we do better?
- saagarjha 4y agoWhat would “better” be in this context? The decision to merge a patch is functions correctly is necessarily opinionated.
- josephcsible 4y agoThe patch inhibits the owner of the phone from accessing data stored on the phone.
- tomc1985 4y agoFunny, I thought this was Hacker News, not Reuters. What are facts, in this day and age, anyway? I guess 'objective reality' doesn't quite have the same ring to it.
- pjmlp 4y agoWhich means in the end Xiaomi phones will have feature anyway. The Android ecosystem is full of fragmentation, the same one that Google fanboys argue that Android was designed to fix in regards to J2ME. Another two common example among Android devleper complaints, is OEM support for cameras, and background services being killed in name of battery resources. Whatever Google decides is of little value for an ecosystem where the majority of consumers aren't getting Pixel phones.
- cowtools 4y agoWhat matters is that the consumers have choice to use free software if they want. If someone makes an app for a (locked-down) samsung phone, it's going to work on a pixel phone running some AOSP distro. If google took some hardline policy or license that prevented the likes of samsung or xiaomi from tinkering with the OS, then all of these companies would be spinning up their own OSes and you would have even more fragmentation. the end result would be worse for the remaining AOSP/Pixel users. Even if the consumers had privacy and control by default (which is a good thing, don't get me wrong), they still have to choose to take steps to maintain that privacy and control, because user respecting software is necessary but not sufficient for freedom. I think the android userbase will come around when they realize that plain AOSP and vanilla android are just way better than all the bloated shit these manufacturers are doing with android.
- pjmlp 4y agoThe OEMs are spinning their own OSes for years, as anyone trying to make their app work across the ecosystem painfully knows, what AOSP allows is that they don't need to start from zero. Android userbase, the one that actually matters to app developers, just goes to the shopping mall and gets whatever cheap Android devices are on sale with pre-paid cards. Again, Pixel phones are more symbolic than anything, outside US very few countries have them on sale on those shopping malls.
- jchw 4y ago> The Android ecosystem is full of fragmentation, the same one that Google fanboys argue that Android was designed to fix in regards to J2ME. I know that there's probably some specific argument that really exists that you're actually referring to, but nobody I know uses Android because of this. Nobody I know was comparing Android to J2ME either. More casual users tend to use it because they dislike iPhone and possibly feel limited by it. More advanced users tend to use it because it's generally more customizable, open source and at least in the past, was much easier to mod and patch. It is true that unlike Windows devices, every Android phone is a snowflake. That's a real problem. But for many people, they don't really care about that problem, only the derivative consequences, like not being able to upgrade their phone to the latest version, or security issues that result from shoddy OEMs. And frankly, users are right to not care: it is not a given that these derivative problems can't be solved in a different way that is satisfactory. (And yes, of course, many users today buy Android devices because they're cheap. But they still had to cross a threshold in the market before they could become the mass market success that they are today, and that happened with mostly enthusiasts.)
- pjmlp 4y agoI was talking about a common argument that used to exist in Android developer circles in its early days of existence. As for the users, if we go down that path, they don't even care about Linux kernel, AOSP, Project Treble, or whatever. That happened because of Google, the continuous adoption failure of FOSS phones since OpenMoko proves that enthusiasts aren't enough to sustain a business at scale.
- jchw 4y agoLet’s be honest: the primary problem with any of the FOSS options before and after Android is that they literally suck. A phone has to have good SMS and phone capabilities, decent performance, and some kind of non-anemic app ecosystem to really exist today. Some of the open source options for phones never managed to achieve any of these, and the ones that exist today still struggle at it, and yet may possibly still be sustainable. Ultimately, I don’t buy the argument that developers opinions about J2ME vs Android had anything to do with it. The T-Mobile G1 is why Android broke through the market. I believe that is in part due to Google’s backing, which instantly made it newsworthy at least in enthusiast circles. The closest thing we have now is the Pinephone, but it largely doesn’t work (though I still find it in much better shape than many of its FOSS phone peers, probably bested by Librem 5 but I don’t own one to know for sure.) To be sure, it doesn't look close to breaking through to the mainstream any time soon, but it’s also not really ready. It has no app ecosystem and no carriers shipping it, and core functionality is still mostly barely working.
- fomine3 4y agoPossibly Google rejects GApps to be installed to the device that the patch applied, or doesn't care.
- pjmlp 4y agoGiven how they have behaved until now, they won't care. Answer about OEM changes regarding killing background jobs, at this year's Google IO Android Fireside, paraphrasing, "Android is a rich environment that depends on its OEMs, and the inovations that they bring into the picture, so it is always a balance that we need to strive for". Video is available in case you want to cross check the exact words.
- xt00 4y agoYes they did -- but as a thought experiment, these types of security measures could be totally reasonable to have if the owner of the phone had root. Sure, lock my phone down until the cows come home.. but I hold the master key (or I can get it easily in a fashion I have control over -- if you fear being forced to under duress then you can set something up to prevent that). Lets be real here (as many people mentioned) the key exists, its just not in your hands as the phone owner. It is in the manufacturers hands. And we want it. The one problem to solve is how to verify that you own the device. Saying that that is too hard to solve is not a good enough reason to deny people from having it. There are 100 solutions to this that cryptography folks could devise -- probably folks here could think of tons (one time keys, requiring physically going to a safe place to retrieve the key, requiring a secondary person, having the ability to provide provable information to the person who wants the key that the person who you are threatening does not have the ability to unlock it, etc) -- but yea, there is theft, hacking, border security snooping phones, etc.. those all exist, so blocking those people from getting root on your device is critical -- now lets think of solutions rather than saying OK Apple and Google get to own my device. If we are one patch away from essentially having no clue whats running on our phones, then we are in way more trouble than we thought we are in... we should have "right to root" on our devices now.