@AlexanderMars @tomjennings @aleksandrayulia @[email protected] Android-based operating systems including GrapheneOS are Linux distributions. These are closed source hardware with closed source firmware, poor security and extremely bad security. The hardware is very low-end and outdated too, but is being sold at a premium based on leading people to believe these are private and open devices when they're not those things. The devices objectively have awful security but that's not the end of what's wrong.
@GrapheneOS you know what they meant when mentioning the Linux ecosystem and mobile. Desktop Linux, devices being mainlined, etc.
@AlexanderMars @tomjennings @aleksandrayulia
@jawsh @AlexanderMars @tomjennings @aleksandrayulia Linux doesn't mean using the desktop software stack that's also available for FreeBSD and other platforms. It means using Linux, which Android does. They should say what they really mean which is bringing systemd, glibc and GNOME to mobile rather than Linux. Linux is already the norm on mobile and if people care so passionately about bringing systemd and GNOME to it, that's fine, but they should say what they're actually doing rather than that.
@GrapheneOS I know but it's what a majority of people mean when they say this. I'm in no way saying you're incorrect because you're not. Just that most people who mention "mobile Linux" are meaning that. Both use the Linux kernel but are still distinct from one another. I run GrapheneOS on my Pixel 8 but enjoy playing around with a secondary device running @postmarketOS
Running your same desktop apps on mobile is appealing for sure.
@AlexanderMars @tomjennings @aleksandrayulia
@jawsh @postmarketOS @AlexanderMars @tomjennings @aleksandrayulia GrapheneOS will fully support running desktop Linux and desktop Windows apps. The current proof of concept support for that via the Terminal app including the primitive GUI support will get much better and will be better integrated, similarly to how it is on ChromeOS. Virtualization is going to be used for sandboxing apps or groups of apps in GrapheneOS too. It's currently only used by Android for certain internal OS sandboxing.
@GrapheneOS I'm aware and that's great but still not the same. That being said, will these apps have access to storage and work like native apps? I've been periodically trying to set the terminal app in GrapheneOS for a few months now but still haven't gotten beyond "preparing terminal" even after letting it run 8 hours while sleeping. It's definitely something I'd like to play with in the future. @postmarketOS @AlexanderMars @tomjennings @aleksandrayulia
@jawsh @postmarketOS @AlexanderMars @tomjennings @aleksandrayulia The Terminal app currently requires that the profile you're using it in doesn't have a VPN because there isn't yet an exclusion for the interface used internally for communicating with the VM from the app running in the profile. It sounds like you're trying to use it with a VPN. It's technically already possible to use it with a VPN with VPN lockdown enabled but it's best to just use it in a profile without one for now.
@jawsh @postmarketOS @AlexanderMars @tomjennings @aleksandrayulia It only takes a few seconds for it to initialize, there's no reason to wait that long. The upstream Terminal app currently shares the Download directory from shared storage as a proof of concept but that will be replaced with a saner approach since it shouldn't be giving unconditional access to a directory that's already used for other purposes. It should end up getting support for dynamically sharing specific directories.