People should not reinvent the wheel. FOSS Android has already solved many problems which Linux always will have, by design.
Non-preemtive scheduler which doesn’t take app usage into account will drain battery fast.
Non-managed app platform is always a security risk.
The absence of a single app framework will always lead to a zoo. Any average Gnome installation bring all KDE and vise versa because different apps use different GUI and Desktop convenience libraries.
Google is trying to kill Android by moving more and more core functionality from OSS into proprietary services.
We need to fight back through forks and legislations.
Android has started as a Linux phone 15 years ago? And has already solved a ton of inherent problems.
We’re still at least a couple of years out from that, the biggest issue at present is app compatibility, specifically in the context of banking apps. For everything else it is usable with some minor quirks
Most banking (and many other) apps could be a website, and most (all?) banks have websites, so a linux phone could be compatible with most banks the same way a desktop OS is compatible with most banks.
But I agree that we’re several years out from Linux phones becoming anything more than a novelty. It’s still a good path to take. We really need a magic rectangle that is not locked down in any way.
I think the biggest issue is the 2fa for transactions which is annoyingly inconsistent between allowing SMS verification and requiring an app 2fa. I know that I have had fairly consistent issues with capital one in this respect, I don’t know if it is prevalent elsewhere
Maybe 2026 can be Year of the Linux Phone.
People should not reinvent the wheel. FOSS Android has already solved many problems which Linux always will have, by design.
Non-preemtive scheduler which doesn’t take app usage into account will drain battery fast. Non-managed app platform is always a security risk.
The absence of a single app framework will always lead to a zoo. Any average Gnome installation bring all KDE and vise versa because different apps use different GUI and Desktop convenience libraries.
Google is trying to kill Android by moving more and more core functionality from OSS into proprietary services.
We need to fight back through forks and legislations. Android has started as a Linux phone 15 years ago? And has already solved a ton of inherent problems.
We’re still at least a couple of years out from that, the biggest issue at present is app compatibility, specifically in the context of banking apps. For everything else it is usable with some minor quirks
Most banking (and many other) apps could be a website, and most (all?) banks have websites, so a linux phone could be compatible with most banks the same way a desktop OS is compatible with most banks.
But I agree that we’re several years out from Linux phones becoming anything more than a novelty. It’s still a good path to take. We really need a magic rectangle that is not locked down in any way.
I think the biggest issue is the 2fa for transactions which is annoyingly inconsistent between allowing SMS verification and requiring an app 2fa. I know that I have had fairly consistent issues with capital one in this respect, I don’t know if it is prevalent elsewhere
Are you saying there are banking sites where you have problems logging in using a web browser? Because using a web browser is what I am suggesting.
My bank requires a proprietary 2FA app for any transfers between accounts or internet transactions in local websites.