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

Devices with GrapheneOS support should be available in 2027

grapheneos.social

Post reply on HN
Print view View original

241–250 of 444 posts

Re: Devices with GrapheneOS support should be available in 2027

#241

Post by drnick1 »

bigfishrunning wrote: post #175
Aachen wrote: post #80

Earlier quoted context omitted.

Except that it's all Android? I'm not selecting which phone I buy on whether the stock OS comes with lockscreen shortcuts. At best, a software requirement someone might use as a deciding factor is OS support and bootloader unlock. The real differences are in hardware: size, battery life, chipset speed, RAM or other local model enablers, picture quality (this part also depends on good software to be fair), included ac…

> Except that it's all Android? If only this were true. Samsung makes arguably the best hardware, but I refuse to buy a phone with Facebook pre-loaded and unremovable, a second (worse) app store preloaded and unremovable, and a bunch of redundant samsung-branded copies of the google apps. The best android images are as close to vanilla AOSP android as possible -- this used to mean Sony or Google branded phones, excep…

The good news though is that by replacing the Pixel's stock OS by Graphene, you get something close to AOSP and arguably better. The hardware is nothing to write home about, but the phones are well priced and the bootloaders are unlockable.

Re: Devices with GrapheneOS support should be available in 2027

#242

Post by FartyMcFarter »

gruez wrote: post #225
FartyMcFarter wrote: post #190

Earlier quoted context omitted.

> Google, this small tech company (correct me if I'm wrong), is peddling source code via tarballs on google drive. What is the context for this? It's not clear from the linked social media post. The Android kernel source code is in git: https://android.googlesource.com/kernel/common/ Plus there's a lot of other Android source hosted on Google's git servers: https://android.googlesource.com/

>The Android kernel source code is in git: https://android.googlesource.com/kernel/common/ That's the mainline kernel. Actual devices use various LTS kernels, for instance the pixel 9a uses kernel 6.1[1], which was hasn't been updated in a year[2] [1] https://wiki.lineageos.org/devices/tegu/ [2] https://android.googlesource.com/device/google/tegu-kernels/...

There are other kernel 6.1 branches there, e.g. https://android.googlesource.com/kernel/common/+/refs/heads/...

I'm not sure which one the latest update for the Pixel 9a is using, I have an older Pixel 8. When I look at the Settings -> Android Version I can see it's using a build from January 2026 (also 6.1).

Re: Devices with GrapheneOS support should be available in 2027

#243

Post by fsflover »

florianherrengt wrote: post #221
tfrancisl wrote: post #25

I've never really understood why we chase Android-alikes on mobile platforms instead of trying to build on mainstream Linux. I know some folks in the nix community (nix-on-droid and other projects) have tried to bring us closer to this, but projects like Graphene seem to have a lot of traction.

I have a Pinephone Pro. It's nowhere near usable as a daily driver.

This is not a good example. Pinephone Pro had a very small developer community (of volunteers) and thus quite undeveloped software. It was discontinued for this reason. Librem 5 and Pinephone are usable as daily drivers, albeit they do require compromises.

Re: Devices with GrapheneOS support should be available in 2027

#244

Post by [deleted] »

zer00eyz wrote: post #215
smallmancontrov wrote: post #183

Earlier quoted context omitted.

I am in awe at the amount of capital Google's market dominance affords them and the consistency with which they squander that capital. https://killedbygoogle.com/ This is not the way.

Well. Lest you forget that modern computing exists because ATT built unix and then threw it out to the public, at speed, as they drove away from it as fast as possible. (Something about being an actual monopoly...). There is at least one thing, on that list that I can almost assure you will be coming back (in concept and spirt) in the next 5 years. Likely open source, because google tossed it... Meanwhile it has othe…

[deleted]

Re: Devices with GrapheneOS support should be available in 2027

#245

Post by seba_dos1 »

inigyou wrote: post #36
tfrancisl wrote: post #25

I've never really understood why we chase Android-alikes on mobile platforms instead of trying to build on mainstream Linux. I know some folks in the nix community (nix-on-droid and other projects) have tried to bring us closer to this, but projects like Graphene seem to have a lot of traction.

All the existing apps are on Android and iOS. Graphene lets you run them. You can't have a bank account on a Linux phone* because they won't let you, but you can on Android including on Graphene. * before replying snarkily that Android is Linux, please take a long walk off a short pier, thanks

[flagged]

Re: Devices with GrapheneOS support should be available in 2027

#246

Post by tfrancisl »

gf000 wrote: post #199
tfrancisl wrote: post #25

I've never really understood why we chase Android-alikes on mobile platforms instead of trying to build on mainstream Linux. I know some folks in the nix community (nix-on-droid and other projects) have tried to bring us closer to this, but projects like Graphene seem to have a lot of traction.

Because it's a mobile platform and "GNU+Linux" is laughably terrible in this space. It's almost like Android has put millions of expert dev hours into making it the most used OS in the world. Like GNU+linux on laptops only works the way it does because of android-upstreamed battery saver kernel features. But a mobile is also people's most used devices with all of their data, bank accounts etc there - it has to be saf…

Nix comes in because im tired of dealing with procedural solutions to things that should be solved declaratively. I run NixOS everywhere I can because I can actually reason about what is installed on the system. "Package management" like apt and pacman and even app stores has never done it for me.

As to your other userspace concerns... these are all solveable. Perhaps with some elbow grease, but devices like the Steam Deck prove that mobile linux isnt as much of a problem re: userspace as you claim.

Ed.: I'd also like to add that the fuss around security is _mostly_ Google propaganda. Android is not meaningfully more secure, _without application level changes_ than Linux.

Re: Devices with GrapheneOS support should be available in 2027

#247

Post by aniviacat »

joelthelion wrote: post #213
J-Kuhn wrote: post #71

Earlier quoted context omitted.

Yeah, its the "well, legally, we have to provide the source code, but we make it as painful and slow for you as we can without it becoming a blatant violation of the GPL."

I'm pretty sure there is a lot of code in Android that belongs to Google and is not part of an upstream GPL project. They would be completely entitled to stop sharing it.

Isn't that the point of Google Play Services? To keep their proprietary code separate, in a super-app that doesn't obey the GPL?

Re: Devices with GrapheneOS support should be available in 2027

#248

Post by kllrnohj »

DANmode wrote: post #165
tfrancisl wrote: post #25

I've never really understood why we chase Android-alikes on mobile platforms instead of trying to build on mainstream Linux. I know some folks in the nix community (nix-on-droid and other projects) have tried to bring us closer to this, but projects like Graphene seem to have a lot of traction.

Your point is valid for every flavor of Android except GrapheneOS. GrapheneOS’ security model makes that of desktop Linux look like a joke. This is an objective analysis based on x86 security, GrapheneOS hardening (including isolation and hardened mem allocator), Pixel hardware security.

Even AOSP has selinux enabled by default with very comprehensive and scoped policies. That, along with app isolation and permission system, already leaves desktop Linux far, far in the dust on security.

Re: Devices with GrapheneOS support should be available in 2027

#249

Post by __MatrixMan__ »

wseqyrku wrote: post #192
inigyou wrote: post #36

Earlier quoted context omitted.

All the existing apps are on Android and iOS. Graphene lets you run them. You can't have a bank account on a Linux phone* because they won't let you, but you can on Android including on Graphene. * before replying snarkily that Android is Linux, please take a long walk off a short pier, thanks

I can't care less about "apps". Web is already powerful enough to do all sort of stuff on device. That said, I think wasi containers support for a mobile OS would be a game changer. (^ Here's a startup idea if you're looking out for one. I for one throw out all my devices from the balcony to get this)

You can run wasm components in tauri apps, and tauri supports building for android.

I haven't figured out how to make them talk with each other though. I imagine that's the place where I'd notice this lack of support.

Post reply on HN