Live data from Hacker News

GrapheneOS has been ported to Android 17

discuss.grapheneos.org

91–100 of 653 posts

Re: GrapheneOS has been ported to Android 17

#91
post #17

The post doesn't say - what's new? Anything to look forward to besides the security patches for A17 being available for longer than they will be for A16? Asking as an A11 user who will probably soon need to switch to a new device. I haven't noticed anything on other people's phones that isn't available on mine, including on my work phone that runs an up-to-date GrapheneOS (but I don't need to do much more than callin…

Presumably any new Android 17 features that aren't counter to GrapheneOS's mission, such as "Bubbles allows you to turn any app into a compact, floating window" https://blog.google/products-and-platforms/platforms/android...

Does GrapheneOS run on tablets? I don't see a whole chat app (shown in the example) fitting on my phone screen alongside something like a web browser, and the screenshot is from a square screen

Re: GrapheneOS has been ported to Android 17

#93
post #32

Earlier quoted context omitted.

We took control, we're keeping control

[flagged]

And how many options are there exactly? How many of them are capable of at least making and receiving a phone call without any issues 99% of the time?

While I agree with your general sentiment, I feel necessary to acknowledge that it's just not there (yet?). GrapheneOS is a great option if you want to have a fully working and secure device.

Re: GrapheneOS has been ported to Android 17

#94
post #26

What are North American people doing for replacing contactless payment? Last time I checked, the solution was to use Curve but it only works for Europe.

Garmin pay if you're ok with Garmin is one possibility.

It's even available in my country! Never heard of it, would have assumed it's not being sold here. Let's see what that costs when I click the "shop now" button that's front and center

> Attention required!

> Sorry, you have been blocked

> The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.

Thanks cloudflare *handshake* garmin. I suppose I'll stay with chip and pin for now

Re: GrapheneOS has been ported to Android 17

#95
post #66

Earlier quoted context omitted.

Google Authenticator works?

I think Google authenticator implements the standard OTP which lots of apps (including keepass) should support. Microsoft uses their own propietary crap

I use a basic OTP password instead of Microsoft's ironically less secure (see SMS as 2FA) with my work MS account. Perhaps your org disabled it but it is definitely something a Microsoft account can do.

Re: GrapheneOS has been ported to Android 17

#96
post #25

Earlier quoted context omitted.

Yes! FUTO keyboard, then go into VOICE INPUT → MODELS → Explore Voice Input Models → English-244: “Best for the most accurate results, but more demanding.” The voice recognition is built on Whisper, and is amazing. You can speak conversationally for a long time and it gets everything right, with smart decisions based on context. My stupid thumbs text no more.

I just did. I had been using FUTO voice, but I see that FUTO keyboard also supports voice input, so I'm not sure if I should delete FUTO voice as being redundant now.

I don't believe it's necessary, it's move of an "if you want a dedicated voice keyboard, the UX is a little better" option. I don't have both installed though, as anecdotal evidence.

Re: GrapheneOS has been ported to Android 17

#97

I had been using LineageOS + microG for many years on my Pixel 3. I upgraded to a Pixel 8 and tried out GrapheneOS and the install experience was good, but I found some odd performance quirks - apps would be slow to install and run, downloads were slow, etc. Has anyone had similar issues? Many apps that work on microG don't work in GrapheneOS without installing Google services anyway. I'm by no means across the full…

A lot of developers are lured into building in a dependency on Google services, so yes you'll need microG or, as GrapheneOS prefers, the original Google code running on your device for those apps to function. Or patch the app, like Langis does for Signal (not necessary for it to function without Google in this case, but it removes its calling out to Google's apps and services for those who don't want that). If you're happy with that setup and don't need protect-from-the-government levels of security (street thugs aren't going to ransomware your device by abusing an unlocked bootloader or send exploit chains that work on anything but the hardened allocator), LineageOS is probably the better choice for you. GrapheneOS has some nice things like easily denying the network permission for an app (even if they could theoretically work around it with intents) and having a custom A-GNSS server, but you can do the same on LineageOS by using root and something like AFWall+ for the network and configuring Graphene's A-GNSS (SUPL) proxy in the system settings (don't forget to donate if you use it and are able)

Re: GrapheneOS has been ported to Android 17

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

> Wicked For Good

Is this an antithesis to Don't Be Evil?

Re: GrapheneOS has been ported to Android 17

#99
Since grapheneOS only supports latest Google pixel phones, I tried installing LineageOS on my Mi11. Sadly, if you own a Xiaomi, you can’t just install another os. You need to unlock the bootloader and Xiomi limits you with a global quota of daily unlocked phones, you basically need to enter at midnight and hope. This is a complete nonsense, we have zero governance on our devices after paying them so much.
Post reply on HN