Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GrapheneOS has been ported to Android 17

discuss.grapheneos.org

Post reply on HN
Print view View original

361–370 of 653 posts

Re: GrapheneOS has been ported to Android 17

#361

Post by a022311 »

nsonha wrote: post #180
jordand wrote: post #12

I've been running GrapheneOS for 7 months now and I'm not going back. When I bought my Pixel 10 last year, I wasn't actually planning on trying Graphene for a while....until I noticed Google had force bundled a 'Wicked For Good' movie promo theme with the latest security update.

would it have the desktop mode and linux terminal? That's the only reason I'm eyeing a Pixel

Yep, I've used both. Desktop mode isn't exactly there yet, but hopefully with the general availability it will get with Android 17, it'll smoothen out. As for the Linux terminal I ended up sticking with a fork which provides a few extra features (https://github.com/outlawsanzhang/koiTerminal)

Re: GrapheneOS has been ported to Android 17

#362

Post by pezgrande »

cyberax wrote: post #243
y2244 wrote: post #70

Earlier quoted context omitted.

Tap to pay is mostly NFC? So is there an alternative app?

I extracted a chip (by dissolving the plastic in acetone) from my card and glued it to the wriststrap of my Pebble watch :)

Nice hack but sounds quite unsafe, I like having to unblock de phone in order to use it.

Re: GrapheneOS has been ported to Android 17

#363

Post by strcat »

flexxxxxxxxxer wrote: post #345
madduci wrote: post #232

I wish they supported much more phones

Only Google Pixel’s and Fairphone’s currently provide bare minimum for 3rd-party OS support: working verified boot with user-provided signing keys. None of the other phones doing that yet Fairphone cant be supported because it does not keep up with Android updates and in particular Linux kernel updates. Currently supported Fairphone’s have EOL (outdated, not supported) Linux kernel version. They are bad in terms of o…

There are a lot of devices with the ability to install another OS and lock the device with verified boot, but none with the required updates and security features other than Pixels. Fairphones are near the bottom for security among the available options.

It's not one of the main issues with their devices but Fairphone has had a lot of issues with verified boot including using publicly available sample private keys for signing firmware and OS images across multiple device generations. It's not a strength of their devices.

Re: GrapheneOS has been ported to Android 17

#364

Post by ignoramous »

thewebguyd wrote: post #185
ignoramous wrote: post #126

Earlier quoted context omitted.

> Apple really cashed in on privacy for a few years Apple didn't "cash in", their marketing dept made sure privacy/security engineering got just enough budget to pull off miracles & then spend even more to successfully make the public forget about the very nasty Celebgate.

> Celebgate That was a phishing campaign, not a breach.

My point isn't about engineering.

Re: GrapheneOS has been ported to Android 17

#365

Post by StrLght »

dmos62 wrote: post #326

Makes me sad, because I can't make the jump until I know my banking and related essential apps will work.

In terms of apps, I fully believe it will only get worse from here: Google’s trajectory has been pretty hostile, and third‑party developers tend to follow it.

That’s why I have two phones. One runs GrapheneOS and is my daily driver; the other (considerably less private and secure) stays at home connected to my server so I can always scrcpy into it.

Re: GrapheneOS has been ported to Android 17

#366

Post by fph »

aorth wrote: post #258
ssddanbrown wrote: post #18

Earlier quoted context omitted.

Because the code is not provided under a free/open-source license, and therefore does not meet the requirements for the main F-droid repo.

Ah interesting. They use the "FUTO source first" license. https://github.com/futo-org/android-keyboard/blob/master/LIC... Open source with limitations on commercial use.

Technically it's "source-available", not "open-source".

Re: GrapheneOS has been ported to Android 17

#367

Post by cubefox »

wolvoleo wrote: post #175
Groxx wrote: post #159

Earlier quoted context omitted.

Yeah, it's pretty awful tbh. I generally recommend disabling RCS, after learning a lot more about it - it feels like a hostile grab at global messaging at this point, heavily entrenched by telecom agreements. Use Signal or something instead. Initially there were some promising details planned, but much of it hasn't panned out, and plus now it's Just Google™. Like, roughly everyone has heard that RCS brings E2EE priva…

Yeah RCS always has been an embrace extend extinguish thing. The carriers were super pissed to lose their SMS revenue to WhatsApp and iMessage so they came up with this shit to be an active partner in the loop again, and they can bill for it again. Consumers didn't fall for that and it died off. Unfortunately Google revived it but it's a very poor standard for interoperability. Not only because the lack of true E2EE…

> Yeah RCS always has been an embrace extend extinguish thing. The carriers were super pissed to lose their SMS revenue to WhatsApp and iMessage so they came up with this shit to be an active partner in the loop again, and they can bill for it again. Consumers didn't fall for that and it died off.

I strongly disagree with this negative characterization. RCS was a replacement protocol for the extremely outdated SMS and MMS protocols. Apple only supported SMS/MMS chat with Android users in iMessage, which meant that cross-platform chats were strongly limited in many ways (e.g. the mentioned emoji reacts), which caused many US American kids to be socially punished for having an Android phone, which is likely part of the reason why Apple is so dominant in the US now, especially among younger users. (Other countries mostly don't use iMessage/SMS, but something like WhatsApp, so they never had this problem.)

RCS was the solution to these iMessage/SMS/MMS incompatibilities. It took years for Google to convince Apple to adopt it, and Apple only announced doing so after EU regulations were on the horizon. There were even internal emails which revealed that Apple used their iMessage dominance and the poor Android compatibility via SMS/MMS to boost their market share in the US.

In summary, RCS is great because it is both a modern chat protocol, unlike SMS and MMS, and an open standard, unlike the closed iMessage and WhatsApp protocols, and available cross platform, unlike iMessage.

Re: GrapheneOS has been ported to Android 17

#368

Post by strcat »

_def wrote: post #359
oceanhaiyang wrote: post #343

[flagged]

Any examples?

Here's an example of what they're responding to with inaccurate personal attacks:

https://grapheneos.social/@GrapheneOS/116353973732143171

GrapheneOS posts factual information debunking inaccurate claims from groups attacking it. Some of those groups react to their misleading claims being addressed with personal attacks. Threads about GrapheneOS on Hacker News usually have multiple posts with personal attacks towards our team from people influenced by those groups.

Re: GrapheneOS has been ported to Android 17

#369

Post by gck1 »

I was using GrapheneOS for years, until the battery died while I was on an important call, trying to get someplace. Plugged it in, but little did I remember that I had installed OS update that was pending app optimization phase that happens during next boot.

GrapheneOS has some hardening in this phase, which as I understand, essentially has to rebuild all apps without cache.

And as I have a ton of apps, I was parked for 30 minutes waiting my phone to boot up.

And because of this app optimization thing, I always delayed OS update finalizations, which probably isn't the best thing.

Unfortunately, GrapheneOS recommendation to this was to have fewer apps. Had to let it go after that.

Post reply on HN