Comment on From F-Droid to emulators, here's who's hit hardest by Android's new verification rules
xiii@lemmy.world 1 day agoIt took 6-10 years for Android to take shape.
On Linux, every app has full access to your browsing history, clipboard (passwords), photos with geo-tags, music, list of other installed apps, contacts. Unrestricted battery and network access – it’s a tracking paradise. And all it takes is one supply chain attack on npm install with typical 4000K dependency packages
Linux phones have already been around for many years. Right now we’re very close to Linux phones that are usable on a daily basis. Not as close to decent Linux phones, of course, but with the right (not at all unrealistic) resources it could be completely within reach in a year or two.
Also, Flatpaks exist and work pretty much just like Android apps.
I made a full comment in this thread. The bottomline is
It all takes years.
Linux phones are around for enthusiasts since Nokia N900 (which was/is a masterpiece) — yet nothing is remotely close to a mainstream phone.
When I hear ‘mainstream phone’, in my mind I picture an iPhone or a Samsung. So yeah, Linux phones are definitely not achieving that this decade. Though personally I don’t think they necessarily need to, at all.
Point 4 is probably not happening any time soon, if ever, either. Rest is slowly being done and progressing, so I’m not seeing any major problems there.
I don’t think anyone realistically expects a Linux phone to compete with an iPhone in terms of ease of use, quality of life features or UI/UX. As far as I’ve seen, people just want a decent phone with basic functionalities like long battery life, good camera, easy to use and smooth UI, maps and navigation. All while being more private and secure, of course.
Mainstream phone as in “I don’t need to debug it via terminal”
The issue I’m pointing at: safe, long battery life, snappy maps while driving is what took AOSP more than 5 years.
It would be very unfortunate to discard all that work and start from scratch.
timestatic@feddit.org 1 day ago
Thats why flatpaks exist for those kind of apps and sandboxes are very much possible on linux (even if not widely used for normal programs)
xiii@lemmy.world 21 hours ago
Flatpack is only a piece of the puzzle. I remember in early Android version, an app could increas gyroscope query frequency (i.e. a racing game demanding precise phone tilt), then crash and the gyroscope would drain battery within hours. And again — this is only one example.
The ecosystem must grow — to this day, I cannot set Immich as my default gallery app on LineageOS. So I take a photo, and can’t immediatelly look at it. And Android is already mature. There must be a standard and secure way of exchanging calendar events, notes, photos. Developers must adopt this new ecosystem — it takes years.
The best option we have right now is to pressure Google to allow alternative to Play Services and also sponsor AOSP development outside of Google. There are numerous Linux distros, including commercial ones, I don’t see why we can’t have numerous Android flavors.
timestatic@feddit.org 19 hours ago
Honestly I would much rather long term have decent Linux for phones, as AOSP derived programs will always rely in some way on google code. I would prefer having one large FOSS Linux ecosystem
xiii@lemmy.world 15 hours ago
From the pure technical standpoint, AOSP is better in every way. Fully managed runtime gives better control over resources scheduling, better app sandboxing. Battery life. Uniform hardware support.
All obstacles for it to be open were artificially made by lawyers.
Like Jolla runs Android emulation layer. Same Android but without its benefits.