this post was submitted on 14 Aug 2023
1 points (100.0% liked)
Linux
48067 readers
780 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I totally get what OP is asking and am constantly annoyed by the same thing.
There's a ton of software that can ONLY be run on a mobile OS, and rather than deal with the nightmare that is a physical Android phone with all of its limitations and restrictions, it would be nice to have these things running in a VM that I can fully control. There's software that demands access to insane and ridiculous permissions, and I'm not going to install those to my physical Android phone and deal with the privacy problems. But a completely isolated VM with burner accounts that I can run in a window on the desktop I'm already using most of the time anyway? I'll take that. Also, I don't see the need to shell out the ridiculous price premiums for phone models with the most storage space when I only use a handful of apps when I'm mobile anyway. An app I might need two or three times a year still takes up that space on my phone when it could easily live on a VM and be used only when I need it at home.
Also, when Android releases new version updates and my phone manufacturer doesn't keep up? Why should I have to go out and buy a new phone just to appease the handful of apps that decide THEY want to be cutting edge and THEY'RE going to be the ones to force me to waste money? I should be able to just spin up another VM with the new Android version and use those sporadic apps on there until I decide to upgrade my phone in my own good time.
Also, Android X86 is fine, but the most problematic apps that mess with users and force apps to newer Android versions for no other reason than being "cutting-edge" aren't made by the kinds of companies with the forethought or customer focus to provide x86 compatible apks.
Basically, I don't see why it's so hard to run a full virtual, sandboxed ARM emulated vanilla Android environment, or why people aren't clamoring for this. It's the most practical, straightforward solution to the fragmentation/bad vendor update model that physical hardware forces on us and I assume most of us hate.
YES THANK YOU i always feel like im alone in wanting an easy to use solution like this
You are DEFINITELY not alone. Every 6 months or so I come back to this and hope someone has done something, and every time I'm disappointed. I'd do it myself, but my username isn't an ironic joke.
[This comment has been deleted by an automated system]
I absolutely refuse to spend that much money on a platform with so little respect for users. You shouldn't even NEED an update guarantee. You don't go out and buy a computer and check for guarantees that it's going to include OS updates... you KNOW it's going to continue updating until the hardware physically can't handle it anymore and you get sick of it and go upgrade it. The Android system and its heavy ROM customization and reliance on vendor updates is fundamentally broken, and it is NOT a problem to be pawned off on USERS to fix by throwing more money at it. The only reason there's ANY difference in the Android environment vs X86 computers is because people tolerate it for whatever reason. This is a problem to be fixed, and the first responsibility for fixing this is on Google, and failing that responsible app developers should be developing for the lowest still supported Android version for SEVERAL reasons.
There are good reasons to update an app to use a new Android version. Complacency in a broken environment of continuous obsolescence as a money making scam isn't one of them.
[This comment has been deleted by an automated system]
My anger is that the decision of an upgrade is made FOR me when the functionality of my phone should be limited by the physical limits of the hardware, and not the development limits of the phone vendor. A company should NEVER tell me "We don't think this is going to give you a good user experience so we're disabling it for you." That is MY decision. If I want to suffer through running your app more slowly, that's up to me, and I don't need the decision made on my behalf, especially when the end result is costing me money. I'm sorry, but that is absolutely unacceptable. EU legislation is nice - I'm particularly looking forward to replaceable batteries making a comeback - but legislation forcing vendor updates doesn't fix the fundamental problem that it shouldn't even be their responsibility. I know the only real differentiating factor between vendors is their particular ROMs and whatever custom bloatware they ship with, but unlocked boot loaders and an operating system with a kernel that is not so inextricably linked to particular hardware that it can be installed and run on ANY Android phone is the real solution. Desktop operating systems don't have 47 different installation images for 47 different special pieces of hardware, and there's absolutely no reason that Android should need that either. Maybe there was an argument that ARM CPUs weren't powerful enough, or space was at a premium for a kernel to have unnecessary hardware support 10 years ago, but the hardware is certainly powerful enough now, and all of those CPU cycles get wasted on crap like app scanning when the system starts, services I can't identify and probably don't need, assistants that are constantly listening to my microphone... I won't say those things are all well and good - I loathe them - but if we're going to have them that should come AFTER development of a generic Android image with a kernel that supports a wide variety of hardware. At this point, vendors can't NOT conform - what are they going to do, develop their own mobile OSs again? Android has become the defacto standard and has no competition. You can force vendors to build hardware that conforms to standards and support generic OS installation now.
If this is true, I haven't seen it. I've got Android 10 phones and as far as I know, I sure can't download a generic Android 12 ROM and just install it. I'm stuck waiting for system updates.
It's surprising that I'm STILL hearing this when I'm running 6 PCs with free operating systems that work, aren't bloated, and are loaded to the brim with world class software that is all free and reliable, some of which was written 20 years ago and barely been touched since because it STILL works.
What you're saying is perfectly valid for SERVICES, which involve ongoing costs, but not everything needs to be a service. In fact, I'd argue most things SHOULDN'T be services. And if I write an app TODAY that works PERFECTLY for some task, I can't just leave it there and rely on it to keep being used in the future. Because of the architecture of the Android system, I have to continually put in work to make it conform to new standards, which of course, keeps reliable, functional FOSS from getting ANY kind of long term usage in the mobile space.
My favorite dictionary app was written for Android Kitkat. Completely offline and functional and did everything it needed to PERFECTLY. I upgraded my daily driver phone to a Android 12 and with there being NO changes to the dictionary app that did EVERYTHING that was necessary for free, that app was broken, because it didn't conform to some new standard. Another app let me remotely mount my SSHFS folders and use my personal server, but THAT broke when Android removed the modules from the kernel. The entire history of the platform is LITTERED with this garbage where developers are FORCED to continually put in work on things that should be "develop once and it's done", and that's INTENTIONAL.
It's a scam of squeezing money out all the way down.
Since mr fantasy land can’t find it in himself to thank you for all the knowledge you shared in this interaction I wanted to make sure I took the time to. Thank you, I learned a great deal from your comments and your ability to communicate information is superb.
[This comment has been deleted by an automated system]
Change the model. The sameness of Android phones is one the worst thing about them, and the software changes with each unique one are almost exclusively battery hogging and poorly written. If phone companies were forced to open their hardware platforms maybe we'd see more risk again. Perhaps differentiated with ACTUAL VARIETY of hardware. Phones with physical keyboards... phones with e-paper... These things are actually actively selected AGAINST in the current model because the limitations of system updates means even if you get used to a better workflow with unique hardware, there's no guarantee that you will get ANY updates or that there will EVER be a better version of the hardware released, but if the platforms were open, the lives of these things could be extended almost indefinitely. And besides,there's absolutely no reason developers couldn't have special software features still installed into their phones and still give me the option to dump a vanilla android image on there. Most PC users don't buy a PC and then wipe the OS and customize their installation, so there's no reason to believe open platforms would change anything for end users, and forcing companies to get more creative in innovating isn't a bad thing in this nightmare market of samey overpriced clones.
It DOES fail directly installed from the APK, but I don't want to get bogged down in this.
I've thought about that and I might do that if Pine ever contracts a less scammy shipping partner. Regardless, this special hardware is antithetical to developing a mobile Linux ecosystem anyway. Linux thrives because it runs on ANYTHING. That gives the widest possible user base who then contribute back to the system and makes the entire ecosystem BETTER. You can buy ANY PC and just install what you want, and that's not less profitable for PC manufacturers. Smartphone manufacturers are greedily wanting to ENFORCE that environment to be Google's specific flavor of Android modified the way THEY want, and the fact it's based on that very same Linux kernel, locking down and limiting and forbidding users from using that hardware in better ways, is morally appalling and disgusting. I don't disagree that this is an option, but this is a workaround to a system that shouldn't function this way.
[This comment has been deleted by an automated system]