Earlier quoted context omitted.
Because you need app support. Not even Microsoft could pull that off.
Doesn't windows run android apps natively now?
It doesn't. There was a plan, but Microsoft abandoned it.
Devices with GrapheneOS support should be available in 2027
61–70 of 444 posts
Re: Devices with GrapheneOS support should be available in 2027
#62I'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 Android is miles ahead in terms of security, permission management, app separation, power management, privacy...
Linux crowd can not even agree on compositor, and if systemd or sudo is a good idea.
Re: Devices with GrapheneOS support should be available in 2027
#63Earlier quoted context omitted.
Because the EU is run by lawyers and lawsuits. They probably decided there was a risk of being sued for insufficient security if they didn't enable every security feature, and they considered it as zero impact to customers because nobody uses graphene.
Yes, but that is still very confusing to me, because you're not paying other people money so that they just follow incentives without thinking, vision or backbone. The whole idea of buying something is giving people money for their (assumed correct) judgement, which then leads to desired artifacts downstream.
No, the idea of buying is that you get something in exchange for money.
Re: Devices with GrapheneOS support should be available in 2027
#64Earlier quoted context omitted.
[flagged]
[flagged]
>Of course they'll say they couldn't read it if they are after his contacts and network rather than after him.
From what a friend working in a state police cyber crime office says, "Cellebrite can't currently, unless its a Graphene OS user that's far behind on updates"
They also said iOS is equally safe unless you're an update or two behind.
Re: Devices with GrapheneOS support should be available in 2027
#65Earlier quoted context omitted.
Yes, but that is still very confusing to me, because you're not paying other people money so that they just follow incentives without thinking, vision or backbone. The whole idea of buying something is giving people money for their (assumed correct) judgement, which then leads to desired artifacts downstream.
No, the idea of buying is that you get something in exchange for money.
Yes, but not any something, but a specific something shaped by taste.
Re: Devices with GrapheneOS support should be available in 2027
#66Earlier 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
What's stopping me from using a browser to log in to my bank? Assuming my bank is one of the ones that requires you to lock down sideloading (they aren't, but i know many are).
I had to replace a credit card yesterday. Part of the default flow involves the call center sending a notification to your app.
When I told them my android version was too old, it took them twenty minutes to find out they could instead send a text message. That text message sends you to a photo-and-id verification service, but that's another issue.
Soon, there won't even be an alternative flow. There are a lot of places where there already isn't.
Re: Devices with GrapheneOS support should be available in 2027
#67I'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
Some (European) banks/healthcare apps block GOS and require stock android. Just saying
Re: Devices with GrapheneOS support should be available in 2027
#68Earlier quoted context omitted.
Because you need app support. Not even Microsoft could pull that off.
What about running the whole Android infrastructure, but on top of a non-Android Linux distro? And this, on top of a Android kernel (otherwise you won't have the drivers yo uneed) The advantage being, we can manage packages using a regular Linux distro
A lot of "non Android Linux distributions" like sailfish os actually use a lot of Android infrastructure to keep working.
Drivers doesn't just mean the kernel. It's the user space binary blobs and services that need to talk to the kernel to enable the hardware.
Other than that there's waydroid, alien dalvik etc.. that run another Android instance in a container.
The thing is a lot of Android applications use safety net/other methods to make sure they only run on. "Approved"/stock hardware.
Re: Devices with GrapheneOS support should be available in 2027
#69Earlier quoted context omitted.
What's stopping me from using a browser to log in to my bank? Assuming my bank is one of the ones that requires you to lock down sideloading (they aren't, but i know many are).
The 2FA code you need to get from the phone app to log in on a desktop. It isn't 2005 any more.
Highly location dependent. This is more true in Europe than in America.
Re: Devices with GrapheneOS support should be available in 2027
#70Earlier quoted context omitted.
What's stopping me from using a browser to log in to my bank? Assuming my bank is one of the ones that requires you to lock down sideloading (they aren't, but i know many are).
The 2FA code you need to get from the phone app to log in on a desktop. It isn't 2005 any more.
Apparently I live in 2005 then? I do 2FA with the same chip+pin method that I use to pay in the store. Works in any browser