Live data from Hacker News

GrapheneOS has been ported to Android 17

discuss.grapheneos.org

491–500 of 653 posts

Re: GrapheneOS has been ported to Android 17

#491
post #479

Jumped to GrapheneOS a few months ago. Works great. The keyboard was bad but you should install FUTO, as some other comments recommend. My only issue with it has been a few apps not working correctly, and not the ones I expected. I did my research before hand and knew that my banking apps would work, thinking those would be the main challenge. Turns out the bike-sharing system in my city, Madrid, won't work. I ended…

Why don't you connect with the makers of Madrid and see what they can do about it? That is sometimes the best way to fix these types of incompatibilities.

Re: GrapheneOS has been ported to Android 17

#492
post #454

Earlier quoted context omitted.

> How can you be free when you're not private or secure? Are you serious? Have you even seen the state of modern operating systems compared to the operating systems of the 80s and 90s? I've had way more fun and learnt lot more about computers messing around with OSes that let you did whatever the hell you wanted to. Modern OSes have sacrificed a lot in that name of security. As for privacy, that's a completely separa…

You can't have privacy without security.

That is a vague, meaningless statement. What sort of privacy are we taking about? What sort of security? What's the target? What's the attack vector? What's the environment? What's your threat model?

Without all of those details, your statement is meaningless.

Re: GrapheneOS has been ported to Android 17

#493
post #356

Earlier quoted context omitted.

I recommend Magic Earth. Free with traffic and navigation, and strong privacy promises (unlike Here Maps).

> I recommend Magic Earth. LOL Bruh... this has a 1.7 rating on Android based on 42k reviews https://play.google.com/store/apps/details?id=com.generalmag...

It used to be really good, and then it went to a subscription model, with a lot of back-and-forth uncertainty about the change. I suspect the rating reflects that.

Re: GrapheneOS has been ported to Android 17

#494
post #147

Earlier quoted context omitted.

I've settled on running CoMaps in the Owner profile, with Google Maps/Waze/etc. in the Owner profile's Private Space for when they're necessary.

Can that setup work with android auto? If so, I'll need to try that.

I use CoMaps in the owner profile with Android Auto. Only caveat is that even with Android Auto developer mode enabled, I still had to install CoMaps from Play Store to get it to show up in Android Auto.

Re: GrapheneOS has been ported to Android 17

#495
post #487

Earlier quoted context omitted.

It seems to me that /e/ is opposed to privacy and security. https://xcancel.com/GrapheneOS/status/2066908368560656652#m

It's interesting how you are able to conclude that. e/OS is clearly a step up from default Android

Insinuating that real privacy /security is for pedophiles and criminals is primarily what supports my conclusion.

It doesn't matter what your marketing says, what's important is what your devices do, and /e/ is much less secure or private than iOS.

Attacking GrapheneOS which makes real progress at privsec.

Thinking that badness enumeration is effective for improving privacy while ignoring real solutions like improving the app sandbox and adding more permissions.

Adding Google services and giving them extra privileges. GrapheneOS ships with zero Google services by default.

https://xcancel.com/GrapheneOS/status/2040887784253141142#m

Re: GrapheneOS has been ported to Android 17

#496
post #20

Earlier quoted context omitted.

Ha! Me too! Exact same. Bought a Pixel 10. Intended to do the default Android for a while. But it was filled with ads for “Wicked” which had me looking at my phone with a sneer on my face I couldn't erase - as if someone had smeared feces all over it and threw it on my bed. So I jumped straight to GrapheneOS, which was way easier and less extreme than I had been warned. So beautifully minimal, with no crap. Now my ph…

What about banking Apps? No problem there? Some of them have ridiculous secur... compliance rules.

My banks app complains will block me and tell me to disable developer mode, but if I turn it right back on after launching the app it won't complain for maybe another week. The post that really annoys me, though, is that if you don't set up biometric unlock they will not allow you to use the extended login cookie, so you need to put in your password every time, most don't work with password managers either (whether intentionally or not).

Re: GrapheneOS has been ported to Android 17

#497
post #393

Earlier quoted context omitted.

I agree with this post and add one anecdotal data point. I had installed graphene os on a pixel but after a couple months and a couple loops between lineage, stock, and graphene, I eventually settled on stock android. I have group messages with family and some of the family are on apple, some on android, and RCS only works with google messages and google services installed. It's infuriating that I can't send RCS mess…

RCS via Google Messages and sandboxed Google Play is fully supported on GrapheneOS: https://grapheneos.org/usage#rcs

Yes. It was kind of a bumpy road getting there, but I haven't had any problems for the last 6 months or so.

Re: GrapheneOS has been ported to Android 17

#498
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.

> [...] until I noticed Google had force bundled a 'Wicked For Good' movie promo theme with the latest security update. This is how users learn to not update anything.

Won't matter when they force the updates anyway. You think that's your phone?

Re: GrapheneOS has been ported to Android 17

#499
post #43

Earlier quoted context omitted.

I don't see how it's relevant. I couldn't possibly have made it any more clear I would not buy a Google device, new or used, because I don't like Google.

That's a value judgement, and it's a fair one. It does throw an additional constraint in the works though. FWIW, I've been looking at the mobile / portable computing space fairly intensively for a month or so. I share your quite dim view of Google. GrapheneOS does seem to be one of the most attractive Android alternatives. There are also Lineage (based on CyanogenMod), AOSP, KaiOS (based on AOSP, via Firefox OS), Lig…

This probably falls under "capabilities", but another consideration worth strong consideration is mobile network support. With the past phase-outs of 2G/GSM, ongoing 3G phase out, converstion to LTE and VoLTE, and expansion of 5G networks, as well as differing network and frequency standards around the world, finding a device which will work with your preferred mobile provider(s) is a challenge.

This is one of my strikes against the Punkt mp02: it doesn't work with most of my carrier options. I was hoping that either that device's capabilities would be extended, or its replacement would follow a similar ethic and expand bandwidth / protocols, but neither occurred. Further reading on Punkt's offerings has further cooled my interest (bugs, fragile HW, spendy).

RCS and group chat support seems to be another sticker, though with a small-form-factor laptop or tablet you should be able to work around that.

The other sticker for me (mentioned in my original post) is voice/SMS/messaging filtering options. The increase in spam / unsolicited contacts across the comms spectrum is immensely frustrating, and few devices / OSs / apps really address the situation adequately and in a privacy-respecting manner. That's still giving me a lot of hesitency on what really ought not to be this complex a decision, though for now I'm thinking it's a good thing to spend the time.

Re: GrapheneOS has been ported to Android 17

#500
post #318

Earlier quoted context omitted.

They definitely can, they just don't want to.

And that's the unserious part, they really don't want anything to do with consumers despite making consumer products (gmail, Android, etc.) so you're always at the mercy of their automatic systems.

Google has historically always sucked at being a product company. Despite this, they're quite successful at it.
Post reply on HN