Live data from Hacker News

Devices with GrapheneOS support should be available in 2027

grapheneos.social

101–110 of 444 posts

Re: Devices with GrapheneOS support should be available in 2027

#101

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.

I don't either. Don't we have free market capitalism? Why don't I have a Linux phone? And why do I need to worry that my government and banking apps won't work if I get a Linux phone?

> Don't we have free market capitalism?

Not in the mobile world no, it's not a free market by any means

Re: Devices with GrapheneOS support should be available in 2027

#102
post #39

Earlier quoted context omitted.

Doesn't windows run android apps natively now?

It doesn't. There was a plan, but Microsoft abandoned it.

They did end up releasing Windows Subsystem for Android via the Windows Insider Program, which was enough for the OSS community to take it over after it was abandoned. It still exists and has worked quite well for my use case: https://github.com/MustardChef/WSABuilds

Re: Devices with GrapheneOS support should be available in 2027

#103
post #70
post #51

Earlier quoted context omitted.

The 2FA code you need to get from the phone app to log in on a desktop. It isn't 2005 any more.

Apparently I live in 2005 then? I do 2FA with the same chip+pin method that I use to pay in the store. Works in any browser

Maybe that is possible in Germany. It is impossible here in Sweden.

Or in other words: of course you can have mobile bankid without a smartphone, just use a tablet computer ;)

Re: Devices with GrapheneOS support should be available in 2027

#104
post #21

Earlier quoted context omitted.

Security-through-obscurity (i.e. using a custom ROM on a lesser-known device) does have some upsides, since you're less likely to be compatible with off-the-shelf exploits. But this is much less true now that LLMs exist, and anyone who can afford the tokens can port any exploit to any and all vulnerable devices. Who maintains the kernel+driver trees used by the LineageOS port you're using? And what's the modem's secu…

Just gave me something else to be annoyed about today ("anyone who can afford the tokens can port any exploit to any and all vulnerable devices.") Not sure that is exactly correct yet but guessing not long til it would be. Bleh.

I can tell you from first-hand experience that it is true already (Well, it's true for the specific exploit/device pairings I've tried, I've not tried to construct an omni-exploit)

Completely random public example: https://github.com/BuSung-dev/Root-My-Galaxy-Payloads/pull/1... (where GLM 5.2 is credited with the port) (Check out the other PRs in that repo for other similar examples)

Re: Devices with GrapheneOS support should be available in 2027

#105
post #84

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.

once Huawei was forbidden from using Android - that's when people ie western markets & the world at large should've shifted. look at HarmonyOS. in China - there's no google apps available on their 'android' versions. their platforms are already performant and fluid - so people should build on that.

It's a shame that the newest version of harmonyOS isn't open source.

Re: Devices with GrapheneOS support should be available in 2027

#107
post #56

Earlier quoted context omitted.

Because you need app support. Not even Microsoft could pull that off.

You mean Microsoft proactively kept shooting devs in the kneecaps? Leaving phones behind on old incompatible OS versions 2 times in 3 years and switching app frameworks 3 times in 4 years does not a good app developer experience make. Piled on top of that, Google became actively hostile to 3rd party developers building support for YouTube (and Gmail and Gmaps, but those had workarounds / alternatives).

What a colossal disaster. I was a huge Windows Phone fan, so their yearly missteps were quite painful to watch. I was especially annoyed when my first gen WP wasn't going to get an upgrade to WP8. My HTC 7 Pro is still my favourite phone I've ever owned, but after that I finally gave up and switched to Android.

Re: Devices with GrapheneOS support should be available in 2027

#108
post #22

Earlier quoted context omitted.

Are you also one of those people who think AES is backdoored because the NSA recommends it?

A member of the NSA also provided the ECDSA P-256 curve seeds but totally can't remember why

It would be funny if it actually was intentionally selected, but for DES-like instead of Dual EC reasons, and they're just too embarrassed by Dual EC to admit it.

Re: Devices with GrapheneOS support should be available in 2027

#109
post #77

Earlier quoted context omitted.

[dead]

I think it's a stretch to call OP doing a "witch-hunt" here. That Android guy is a mini LinkedIn celebrity with 100k followers.

This doesn't excuse a message that literally reads like call to action.
Post reply on HN