Live data from Hacker News

GrapheneOS has been ported to Android 17

discuss.grapheneos.org

211–220 of 653 posts

Re: GrapheneOS has been ported to Android 17

#211
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…

Does it affect the photo quality? It used to require letting go of the default photo app and thus a downgrade in photo processing.

Install a 3rd party GCam and then the answer is no https://www.celsoazevedo.com/files/android/google-camera/

Re: GrapheneOS has been ported to Android 17

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

I want to run graphene but I make android apps and need to test on device with a somewhat standard setup… login with google, etc. is this reasonable to do with graphene?

Hmm, you should have cheaper and separate phone for work anyway?

Re: GrapheneOS has been ported to Android 17

#213
post #43

Earlier quoted context omitted.

> The Pixel was never sold in my country Okay, see, that's an important thing to add to your original post. Saves everyone a lot of time. If they don't sell them in your country, it's not "no thank you" as you said, it's "this doesn't apply to me".

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), LightOS (by Lightphone, AOSP), AphyOS (used by Punkt. mp03, also based on AOSP). These tend to be minimal, used on feature phones / dumbphones / minimalist phones. And there are /e/OS and iodéOS.

Among Linux-based non-Android options are Sailfish OS (Jolla), Ubuntu Touch (Ubuntu), PineOS (Pinephone), and PureOS (Purism), Tizen, Mobian (based on Debian), postMarketOS (based on Alpine Linux). These tend to be maximalist, offering a fuller experience than Android, with support for native Linux applications and configurations.

There are some non-Linux OSes, of which I'm aware of System 30+ (a/k/a S30+, Nokia), OpenHarmony (by Huawei), and ... something described as "realtime OS" or "RTOS" which actually had a name, for a Japanese flip phone, but which has slipped my mind (probably something reviewed by Jose Briones on his YouTube channel).

And of course there's iOS.

Briones by the way is an absolutely excellent resource: https://josebriones.org/>. He's also one of the mods of /r/dumbphones at Reddit.

There are trade-offs, and what you choose depends on what you value, in the marketplace, in capabilities, in your own peace of mind.

If you want a full-featured device with wide acceptance, few limitations, and want nothing to do with Google, look at iOS devices.

If you want (nearly) full Android capabilities, but without Google's prying eyes and ears, GrapheneOS or LineageOS are probably your best bets. Whilst Graphene currently only works on Google Pixel devices, there's been a partnership announced with Motorola, there may be others in future (my speculation, with no other basis). And ironic as it seems, Graphene + Pixel actually does get you further from Google in many ways, though I still understand your position.

If you want full freedom / maximal privacy, and are prepared to make compromises on capabilities and battery life, look at one of the Linux-based, non-Android options. I've heard of quite a few bugs with these.

If you're looking for specific hardware capabilities (e-ink, folding / candybar, keyboard (T-9, qwerty, ...), small, large, tablet, headphone jack, etc., etc., or specific software capabilities, you're going to further refine your search. (Briones has a Dumbphone Finder at his website which does this pretty well.)

If you want modularity or repairability, there are devices such as Fairphone or Keyphone with (some) replaceable components.

If you want minimalism, look at an AOSP-based device, or perhaps S30+. These will give you feature phones capable of calls, texts, and a few apps, but not much else. For more complete computing you'll need either a desktop or a laptop.

There are more extreme options. I'm considering, for example, whether or not a roving SIP WiFi-only phone might be an option, and if so, what would be necessary to make that work. It would rely on a WiFi network provider (public or non-public network, or a cellular modem), and wouldn't function everywhere but should function in many locations sufficiently to be useful.

Most non-smartphone options I've looked at, and in particular the usual "dumbphone" suspects (Light Phone, Punkt.) tend to run an AOSP-based OS, with Nokia being the principle exception.

Briones FWIW uses the Light Phone III as his daily driver. That's somewhat spendy, and quite minimal, but he has his reasons, discussed at length at his blog and YT channel.

I'm leaning fairly strongly toward an option now, though my main hesitation is that KaiOS devices have very limited phone/SMS spam and/or traffic management. I'd prefer known-contacts-only could reach the device, that doesn't seem to be possible (KaiOS has only specific-caller blocking, and apparently a limited API for enabling more robust phone blocking). On the flipside, the device can be powered off, and/or battery removed.... I'm also looking at some VOIP/SIP options.

Re: GrapheneOS has been ported to Android 17

#214
post #177

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…

>but I found some odd performance quirks - apps would be slow to install and run, downloads were slow, etc. Has anyone had similar issues? not sure about downloads specifically, but app installs are slow because grapheneos forces AOT compilation (JIT is disabled), presumably for security reasons.

Ah that makes sense, thanks!

Re: GrapheneOS has been ported to Android 17

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

I want to run graphene but I make android apps and need to test on device with a somewhat standard setup… login with google, etc. is this reasonable to do with graphene?

I'd get a 2nd phone for that and it never leaves the house/location - living inside a bag with conductive material

Re: GrapheneOS has been ported to Android 17

#216
post #63

Earlier quoted context omitted.

When I got a new phone last year, I purposely got a Pixel (open box 9a) to put GrapheneOS on it immediately. Been happy living the de-Googled Android life since. I was sad that I had to go through the OOBE setup on the stock image to unlock the bootloader. At least it doesn't force an internet connection and login, unlike Windows.

If it's any consolation, the wipe* requirement before unlocking the bootloader is generally a good thing, even if it's inconvenient. Someone who is targeting your personal data gets access to your encrypted phone, either by stealing it or in an evil maid situation. They unlock the bootloader and install privileged code that helps them recover the symmetric encryption key or intercept your PIN. Then they either have y…

AFAIK you can't unlock bootloader without wiping the data, that's my experience from last 15 years unlocking bootloaders on various phones

so it's kinda pointless to wipe data prior wiping them again during the bootloader unlocking process

Re: GrapheneOS has been ported to Android 17

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

How's the P10 camera on graphene? Literally 90% of the reason I'm on a pixel is because I love the low-light smarts that the camera software has, but I don't know if I'll lose that with Graphene.

You can install the Google Camera, if you use sandboxed Google Play. It has all the same features AFAIK.

Re: GrapheneOS has been ported to Android 17

#218

What's the biggest draw of GrapheneOS apart from de-googling? Does it have a better battery life? And compliance with NFC payments?

If you actually degoogle, supposedly battery life is better but if you start adding back in sandboxed play services, you lose some of the gains.

Re: GrapheneOS has been ported to Android 17

#219

Earlier quoted context omitted.

Does it affect the photo quality? It used to require letting go of the default photo app and thus a downgrade in photo processing.

Install a 3rd party GCam and then the answer is no https://www.celsoazevedo.com/files/android/google-camera/

That sounds like the answer is actually yes: we're not talking about the lack of a camera app, but the lack of a camera app that knows the details of the usually-proprietary camera firmware

Re: GrapheneOS has been ported to Android 17

#220

Earlier quoted context omitted.

When I got a new phone last year, I purposely got a Pixel (open box 9a) to put GrapheneOS on it immediately. Been happy living the de-Googled Android life since. I was sad that I had to go through the OOBE setup on the stock image to unlock the bootloader. At least it doesn't force an internet connection and login, unlike Windows.

While the OOBE of the stock image doesn't force an Internet connection, the ability to unlock the bootloader does - whether you can do it or not depends on the phone manufacturer's desire, and Android for some reason uses an Internet connection to check that. My understanding is that it is impossible to unlock the bootloader on a new recent (Android 7+ at least; possiblt earlier) Android phone until it has connected…

it should be possible on Sony and OnePlus phones and maybe other brands, though it can require obtaining code from internet on other device, but the device being unlocked itself doesn't need to have internet connection
Post reply on HN