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

521–530 of 653 posts

Re: GrapheneOS has been ported to Android 17

#521

Post by subscribed »

genpfault wrote: post #103
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.

What's the app data backup/restore story on GrapheneOS? My understanding is that even with pseudo-D2D (device-to-device) transfers Seedvault doesn't backup everything[1]. Are there more-functional, non-root, local (non-cloud) alternatives? [1]: https://github.com/seedvault-app/seedvault/wiki/FAQ#why-do-s...

Backup situation is absolutely awful, don't count on it.

Re: GrapheneOS has been ported to Android 17

#522

Post by HybridStatAnim8 »

tcfhgj wrote: post #484
Cider9986 wrote: post #480

Earlier quoted context omitted.

I don't think that fairphone is interested in privsec so it will never be supported.

them supporting e/OS suggests otherwise

No, them supporting e/OS corroborates the claim that their goal is not privacy or security.

Re: GrapheneOS has been ported to Android 17

#523

Post by Groxx »

strcat wrote: post #394
Groxx wrote: post #9

Earlier quoted context omitted.

Regarding 2: that is literally how SMS reactions work. Apps that recognize it just interpret it as "put that emoji on that message". It is unfortunate that it doesn't do that tho. RCS is different, which you can sometimes get working by installing Google Messages¹, which is essentially the only app that supports RCS any more. Google runs essentially all the servers too. --- 1: There are no third-party RCS apps² becau…

GrapheneOS will eventually have a GrapheneOS RCS app, but for now RCS is fully supported via Google Messages and sandboxed Google Play: https://grapheneos.org/usage#rcs

There have been consistent problems with activating RCS, for many years. But it does work for some/many, yes.

And AFAIK they have only been desiring to build their own RCS app, and researching it, but have no concrete plans. It'll probably be extremely hard to do, given how much interaction it requires with individual telecoms, and how large the specs are and how much they change - it'll be signing up for significant dedicated eng/business/etc effort that will never decrease. Though I would very much like it if it does happen.

Personally: it worked for about a year for me, then stopped for several months, then worked for two, then I disabled it. All on the same phone, same OS install, same carrier and phone plan, and same location. No issues at all on stock Android with everything else identical which my wife uses. You can find tons of cases like this with Graphene users, RCS just doesn't work/activate/??? as well for some reason.

Re: GrapheneOS has been ported to Android 17

#527

Post by Groxx »

cubefox wrote: post #367
wolvoleo wrote: post #175

Earlier quoted context omitted.

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 an…

This is an extremely strange rewriting of history in which Google is some kind of altruist, moved by the plight of suffering school-children in a brief period where the rich bullying the poor (something truly shocking and unprecedented) over the color of their messages simply couldn't be tolerated any further.

Re: GrapheneOS has been ported to Android 17

#528

Post by hparadiz »

Liquid_Fire wrote: post #410
hparadiz wrote: post #276

Earlier quoted context omitted.

We have chips but magnetic strips are still on most credit cards and payments are still accepted that way in many older payments gateways. From what I read on the topic the cost of lost business if this was disabled is greater than eating the cost of skimmer attacks. There is a several year plan to phase it out entirely. It's mostly because initially when chips came out a lot of business owners were angry that they h…

In the UK, many banks disable the magnetic strip by default, and you have to temporarily enable it from the bank's app/website if you want to use it. You'd struggle to find a POS terminal that even has a reader for them in the UK. I've only ever had to enable them in the US or Japan.

The US first got magnetic strip readers in 1970 so we just have a ton of infrastructure using them. Since most people drive pickpocketing and things of that nature are much less of an issue for us. Typical use has someone using the card for everything then paying it off at the end of the month so if there's a random extra charge the credit card company will typically let it go to maintain the active user.

Re: GrapheneOS has been ported to Android 17

#529

Post by strcat »

fsflover wrote: post #437
strcat wrote: post #320

Earlier quoted context omitted.

The kernel drivers are fully open source and moving to new kernel branches is a standard part of the update process. Pixels are currently moving from 6.1 and 6.6 to 6.12 with Android 17 QPR2. This is part of the hardware requirements for GrapheneOS listed here: https://grapheneos.org/faq#future-devices

Are you saying that GraphebneOS running on Google Pixels has no proprietary blobs apart from the firmware?

No, but all of the kernel drivers are open source and always were. The closed source userspace libraries such as the Mali GPU library aren't a barrier to porting to a new kernel version which is what was said above. We could move to 6.12 ourselves but we choose to wait for them for much broader testing which is happening with Android 17 QPR2.

Re: GrapheneOS has been ported to Android 17

#530

Post by drnick1 »

anonymousiam wrote: post #179

I took the plunge into GrapheneOS a week ago. I picked up a new Pixel10 Pro and never even tried the stock OS (except to unlock the boot loader). I've got almost everything working the way I want. There were a few non-essential banking apps that won't install. The most annoying problem I had is when I tried to install Strava, which I cannot get working. The app installs, but it will not let me sign in. I guess I need…

"Strava is an American internet service for tracking physical exercise which incorporates social networking features."

Sounds like spyware, to be honest.

Post reply on HN