Live data from Hacker News

Daily driving a Linux phone, but why?

thefoggiest.dev

231–237 of 237 posts

Re: Daily driving a Linux phone, but why?

#231
post #115

Earlier quoted context omitted.

All the Linux phones that i‘ve used have felt very sluggish, even if they were pretty recent models. GrapheneOS on the other hand is very snappy.

Of course that's why we use and love GNU / Linux, because of snap and snappiness! _ No GNU/Linux user ever Please take my freedom in exchange for snappiness and security. _ (a)NO(ther) GNU/Linux user Users have the right to a secure deGoogled Android Linux after they give Google hundreds of dollars for a Pixel. _ Stickard G. Pallman

Why does it have to be either freedom or snappiness?

Do you get the linux phones for free as opposed to paying for a pixel phone?

Re: Daily driving a Linux phone, but why?

#232
post #10
post #8

Isn't every Android phone a Linux phone? OK, i guess we want something that is less encumbered and more transparent with more digital sovereignty for the user than the Android that we get from the various big phone vendors. What's the difference between an AOSP Android phone and a Linux phone? For me, there is no substantial difference. The Android based phone is likely to be way more usable the various "Linux phones…

GrapheneOS only supports a few specific Google phones, so it's not an option for most cases

Isn‘t linux phones even more restrictive concerning the phones it runs on?

Re: Daily driving a Linux phone, but why?

#233

Earlier quoted context omitted.

It does in the sense that all the applications you install will be via flatpak, so they get sandboxed that way. Of course it depends on how locked down the sandbox is configured for each of those applications.

The S in Flatpak stands for Security. Flatpak is primarily a convenience mechanism for app makers. Any security boundary you may find in it is optional, all defaults are always toward not breaking apps. Apps pretty much uniformly either silently get read access to all your files, and even when that is not true they often get permanent read-write access to any file you open in them. Go look at the permissions for GNOM…

>Apps pretty much uniformly either silently get read access to all your files

This is outdated information. The situation has improved since the publishing of flatkill with flathub loudly warning about permissions and less apps having full R/W access.

Android apps can be configured insecurely too although less severe, still it's the users responsibility to check and modify permission.

In either case it's a substantial improvement from no isolation at all with much easier handling than other sanbox tools or MACs.

Re: Daily driving a Linux phone, but why?

#234
post #224

Earlier quoted context omitted.

How can you compare iOS or Android security with desktop Linux security? Have you checked what it takes to achieve those 0-click root exploits on iOS or Android compared to a desktop Linux distro? Not even in the same league.

Have you checked the time it takes apple or any android vendor to fix anything vs the time it takes a linux distribution? Months vs hours.

Sounds like a vendor issue also present on desktop. Just get a pixel and enjoy first class update support with GrapheneOS.

Re: Daily driving a Linux phone, but why?

#235

Earlier quoted context omitted.

The S in Flatpak stands for Security. Flatpak is primarily a convenience mechanism for app makers. Any security boundary you may find in it is optional, all defaults are always toward not breaking apps. Apps pretty much uniformly either silently get read access to all your files, and even when that is not true they often get permanent read-write access to any file you open in them. Go look at the permissions for GNOM…

>Apps pretty much uniformly either silently get read access to all your files This is outdated information. The situation has improved since the publishing of flatkill with flathub loudly warning about permissions and less apps having full R/W access. Android apps can be configured insecurely too although less severe, still it's the users responsibility to check and modify permission. In either case it's a substantia…

> less apps having full R/W access.

Not good enough when apps can still silently have full access to home and /media without the user even realizing.

Re: Daily driving a Linux phone, but why?

#236

Earlier quoted context omitted.

I had a similar experience with GrapheneOS. There is a balance in act between continuing down the privacy rabbit hole versus being able to communicate effectively with your social circle and it is easy to double down on privacy at the cost of relationships if you are not aware of how it is affecting others.

I have my own problems with GrapheneOS, but I thought they made a great effort to make sure that it didn't really have that kind of downside. What problems did you hit?

I put all of my social media apps on a secondary profile or in Private Spaces. Never got notifications and checked the apps very infrequently. Not a great experience when i would take hours/days to respond to people I'd imagine.

Re: Daily driving a Linux phone, but why?

#237
post #85

Because Android and iOS serve other masters. Its's not just that this is morally unsound, it's fucking infuriating. Imagine JD Rockefeller had arranged it so that your pen and paper constantly nagged you and tried to trick you into buying things. I'm calling it now, society is going to collapse and it's going to be because of software and hardware working together in tandem to make life miserable and expensive and on…

Fascism is our actual governance system - if you define it as 'government and corporations working together', as Mussolini did. It is just that we are mostly under the illusion that we live in a democracy. It is long in the planning that software and hardware work together - look into technocracy. Smart anything = spy. Smart meters are tools to monitor resource usage. Smart phones are spying/reporting on you. Ai will…

[deleted]
Post reply on HN