Live data from Hacker News

Devices with GrapheneOS support should be available in 2027

grapheneos.social

231–240 of 444 posts

Re: Devices with GrapheneOS support should be available in 2027

#231
post #186

This is good news but not so much good news for us poors. I was waiting four this announcement in hopes of getting away from google totally but with the 2026 Moto Signature going for $1000 I am sure the 2027 will be more so I will probably get Pixel 10 instead. Maybe this will lighten the price on the Pixel 10's though...

If this is successful, I can see this trickling down to the lower end phones in the following years. If for no other reason than keeping their hardware as similar as possible.

Re: Devices with GrapheneOS support should be available in 2027

#232

I've never really understood why we chase Android-alikes on mobile platforms instead of trying to build on mainstream Linux. I know some folks in the nix community (nix-on-droid and other projects) have tried to bring us closer to this, but projects like Graphene seem to have a lot of traction.

Yes, there's SailfishOS, there's Ubuntu Touch, and a couple more. It would be nice if one of them could gain traction so people can have a third choice.

Re: Devices with GrapheneOS support should be available in 2027

#233

[flagged]

> Prior to moving it to Google Drive, they started squashing the history into a single commit prior to pushing release tags. The tarballs provided via Google Drive have exactly the same source code. However, they went out of the way to make it more inconvenient in several ways.

Ugh.

Also I can't believe it's been 10 years since they shut down Google Code.

Re: Devices with GrapheneOS support should be available in 2027

#234
post #71

Earlier quoted context omitted.

Yeah, its the "well, legally, we have to provide the source code, but we make it as painful and slow for you as we can without it becoming a blatant violation of the GPL."

Not quite, they could make you request it by post and send it on a stack of floppies.

Greenbar printouts.

Re: Devices with GrapheneOS support should be available in 2027

#235

I've never really understood why we chase Android-alikes on mobile platforms instead of trying to build on mainstream Linux. I know some folks in the nix community (nix-on-droid and other projects) have tried to bring us closer to this, but projects like Graphene seem to have a lot of traction.

Seems like it's the same problem as chromium. Is it better to get off the Google controlled ecosystem? Yes. Is it easier to leverage the Google controlled ecosystem? Also yes.

People will tell you that chromium is "more up to date" as if Google wasn't the one setting the standards, making it impossible for anyone else to be similarly complete. Seems like we have a very similar problem here...

Re: Devices with GrapheneOS support should be available in 2027

#236
post #162

Earlier quoted context omitted.

In many countries, all major local banks require their phone app as the second factor to log in to the browser version of their online banking. Sometimes functionality is removed from the browser version and made available only in the phone app.

"Many" is doing a lot of work here. A more accurate statement would be that some banks in some countries require invasive apps, but fortunately it isn't the case everywhere (yet).

This is a huge problem in EU countries!

The relevant regulations are Commission Delegated Regulation (EU) 2018/389 and the earlier Directive (EU) 2015/2366.

While these laws are deliberately vague when it comes to specific technologies, they do require at least two independent factors from different categories, such as knowledge (password) and possession (phone).

That, in and of itself, wouldn't be a problem. The way most banks implement it, however, is by giving you two choices:

1. You use their mobile app (which likely requires device attestation and Google Play Services, so won't work on a plain LineageOS install)

2. You use their CardTAN device, which is extremely inconvenient to always carry around.

Sure, we nerds might argue they should just let us use our Yubikeys or regular old TOTP, but pretty much no bank implements that. (Why? Your guess is as good as mine.)

Personally, I had to buy a second stock Samsung phone just for banking apps. And yes, there are still alternatives (only very very few though), but no, none of them are convenient, for various unrelated reasons.

I wouldn't be surprised if this continues to spread to the US too, under the sneaky disguise of "security".

Re: Devices with GrapheneOS support should be available in 2027

#237

Earlier quoted context omitted.

AOSP has way better security and therefore privacy than desktop linux.

[flagged]

> AOSP is only more "secure" because, on some devices like Pixels, it exploits hardware features typically not found on general purpose computers.

You don't think, say, isolating apps has anything to do with it?

Re: Devices with GrapheneOS support should be available in 2027

#238
post #143
post #36

Earlier quoted context omitted.

All the existing apps are on Android and iOS. Graphene lets you run them. You can't have a bank account on a Linux phone* because they won't let you, but you can on Android including on Graphene. * before replying snarkily that Android is Linux, please take a long walk off a short pier, thanks

Banks care very little about actual security. Some force you either to SMS codes, or to their app on a hopelessly broken platform based on shoving many untrusted spying apps onto one device and hoping some SW will be able to keep them apart. Almost none support strong dedicated HW authenticators or second factors. Not even as an option to those who care. Anyway it's always possible to just reverse their web api and u…

A lot of it is security theater plus lazy (as in "doing the minimum amount of work possible") compliance with regulations

Re: Devices with GrapheneOS support should be available in 2027

#240
post #96
post #67

Earlier quoted context omitted.

Some (European) banks/healthcare apps block GOS and require stock android. Just saying

Yep. Had to change banks because of my old one suddenly dropping grapheme support by adding stupid attestation mechanics. They surely must have gotten feedback from me and others because the next update it worked again. But I and probably others where already a lost customer.

same here... unfortunately, there are too few users of alternative Android distros for the banks to care...at all
Post reply on HN