Live data from Hacker News

Your phone is about to stop being yours

keepandroidopen.org

731–740 of 927 posts

Re: Your phone is about to stop being yours

#731

Earlier quoted context omitted.

Let's not be naive by pretending improving user security is the main purpose of that move.

May or may not be. It does significantly improve security.

I miss data to confirm any of this does significantly improve security.

Anecdata: I have yet to meet someone who have been targeted by unknowingly side-loading apps.

If they really want to improve security they can work on much more impactful changes. I know people having been scammed by ads proudly delivered by instagram and google. I read about malicious apps that somehow went through official store filtering.

Re: Your phone is about to stop being yours

#732
Respectfully, I think this is the wrong fight. And I fear it may be counter-productive, because all the effort put into asking Google to make it a little less painful to install an unverified app is not put into the real fight.

IMHO, it should be fine for Google or Apple to do whatever they want with their OS. What should be forbidden is to prevent people from installing an alternative OS on their hardware. But this is not all Google's doing there: all the Android manufacturers are actively preventing users from doing it.

When I buy an Android phone, I should be able to unlock the bootloader, add custom signing keys, install whatever OS I choose, and relock the bootloader. Interestingly, currently this is possible on Google Pixels, but not on most other Android devices.

When I use an Android phone, a company building an app should not be allowed to ban my OS "because it is not the Google OS". That is, using Play Integrity or whatever they do to ban alternative OSes should be forbidden. But again, this is not entirely Google's fault: the companies choose to add those checks in their ** app. And it is a bigger problem there, because while I can install an alternative OS on my Android device (e.g. GrapheneOS or LineageOS), I can NOT install an alternative client for e.g. my bank.

Back to side-loading: really it's mostly a problem for F-Droid on Stock Android, as far as I can see. And really, people who care about using F-Droid would probably be happy to use an alternative OS, if it was reasonably possible. We should fight for that.

Re: Your phone is about to stop being yours

#733
> this flow runs entirely through Google Play Services, not the Android OS. Google can change it, tighten it, or kill it at any time, with no OS update required and no consent needed.

I am curious: Can you opt-out with the device not connected to the network?

From the statement in the article it seems that may not be possible?

Re: Your phone is about to stop being yours

#734
post #258

This is the most important part: >> Developers Do not sign up. Don't join the program by signing up for the Android Developer Console and agreeing to their irrevocable Terms and Conditions. Don't verify your identity. Don't play ball. Google's plan only works if developers comply. Don't. Talk other developers and organizations out of signing up. Add the FreeDroidWarn library to your apps to warn users. Run a website?…

That's not the solution - developers or businesses are squeezed into signing up anyway to survive/make a profit. The only viable alternative is to create an alternative - Linux phones.

I agree. There isn't even a need to create alternative OSes: they exist. Be it Linux phones or (more realistically for the vast majority of users) AOSP-based OSes like GrapheneOS and LineageOS.

The real problem is that:

1. Most manufacturers prevent us from unlocking the bootloader, adding custom signing keys and relocking it. Interestingly the Google Pixels allow that. This should be mandatory.

2. Many apps choose to ban alternative OSes by use of Play Integrity, i.e. checking that the OS is signed by Google. This should be illegal.

3. Bonus: it should be mandatory for manufacturers to make it reasonably easy to support from an alternative OS. That means publishing device trees, for instance. This should be mandatory.

I really believe we should fight for that. Then we wouldn't have to care about what Google does on their side.

Re: Your phone is about to stop being yours

#735
post #387

Earlier quoted context omitted.

> I’m aware of alternate mainframe OSs but I’m not sure how common using one was. Extremely common at major universities and research centres. CTSS, ITS, TENEX, Multics, Unix and even VM/370 were all alternate operating at some point. > Other than OS2, alternate OSs for other systems were rather rare, You weren't there, were you? A lot of people replaced MS-DOS with DR-DOS before Microsoft deliberately broke it with…

> at major universities and research centres So not common outside of ivory towers, no?

I went to a regional state university. We had an older IBM mainframe with a hypervisor and the students and faculty were all users on MUSIC/OS. This was in the early/mid 1990s.

Re: Your phone is about to stop being yours

#736
post #8

I don't care, I run Graphene, and my phone is definitely mine. Most Android apps just work, and the ones that don't are the kind of malware I am happy to do without.

I use GrapheneOS too. Most of the time it works great, with some weird bugs around group messages and needing to restart every now and then to get to a fully functional state between the browser and keyboard properly working with each other and the network connectivity going away. I do enjoy full control on network connectivity and notifications. But beyond whether the OS is good or not, "fuck you, I've got mine" is…

> "fuck you, I've got mine" is not only sad as a position in general, it is also a bad tactical choice

I don't think the parent was saying that.

My opinion is that it is actually the real fight: it should be mandatory for manufacturers to make it possible to have an alternative OS (which includes allowing to unlock/relock the bootloader and add custom signing keys) and it should be mandatory for big companies (e.g. banks) to not ban those alternative OSes with Play Integrity or whatever goddamn checks they make.

Fighting about what Google does on the Google flavour of AOSP is a distraction, IMO.

Re: Your phone is about to stop being yours

#737

Someone here on HN used the term "cloud terminal" for modern electronic devices, and I think that is a very fitting name for phones and tablets. They are definitely not computers because they do not actually give the user access to general purpose computing in the sense that the users can control exactly what computations the device is going to execute. They are just terminals whose production costs we cover but whic…

IDK, not really a fan of redefining computer to make a rhetorical point. It seems counter-productive to tell people the computing device they think as a computer isn’t really a computer. It’s like saying my car isn’t really a car because I can’t adjust spark timing. Someone could make that semantic argument but it’s hard to imagine anyone would care.

> IDK, not really a fan of redefining computer to make a rhetorical point.

Yes! This reminds me of Stallman who is in my opinion a visionary decades ahead of his time, but in terms of marketing he did that a lot and it ended up just distracting from the conversation. All of a sudden instead of discussing the actual issue, we're disussing rhetoric.

Re: Your phone is about to stop being yours

#738
post #51
post #8

I don't care, I run Graphene, and my phone is definitely mine. Most Android apps just work, and the ones that don't are the kind of malware I am happy to do without.

I'm running GrapheneOS too and while I've experienced the same, I'm dreading the day any of my banking apps update and suddenly start demanding full Play Integrity API support (GrapheneOS only has Basic) causing them to fail to open. Hasn't happened yet but it could.

Happened to me. Stopped working on GrapheneOS because of some goddamn check they make, but still runs on an outdated /e/OS signed with the Google test keys (i.e. without a proper secure boot).

The real fight is to prevent companies (like those banks) to do that kind of shit. And to force manufacturers into allowing us to install alternative systems, instead of preventing unlocking/relocking of the bootloader for instance).

Re: Your phone is about to stop being yours

#739
post #13
post #8

I don't care, I run Graphene, and my phone is definitely mine. Most Android apps just work, and the ones that don't are the kind of malware I am happy to do without.

I have a pixel 10 pro and have tried no less than 5 times to get my apps to work on graphene, no luck. I'm no slouch either, I've developed for android for almost a decade. I'm not disagreeing with ya, just adding a comment so folks are aware that the "Graphene just works" crowd is sometimes a bit hyperbolic.

How many apps do you have that don't run there? Would you be willing to share them? I have been using GrapheneOS for a couple years and almost everything works seamlessly (except when e.g. a bank decides to ban GrapheneOS).

Re: Your phone is about to stop being yours

#740
post #8

I don't care, I run Graphene, and my phone is definitely mine. Most Android apps just work, and the ones that don't are the kind of malware I am happy to do without.

Ironically, you’ve had to pay Google for the privilege of opting out of their new rules.

Which is because other manufacturers don't allow you to unlock/relock the bootloader, right?
Post reply on HN