Probably an unpopular opinion, but I don't think most people who buy a Linux phone actually want a Linux phone. They want an open-source phone. The Linux philosophy isn't important to them, they essentially want open-source iOS (with all of the polish and out-of-the-box doodads). They want the ability to make modifications, and they want the freedom and transparency that open-source gives them, but they don't necessarily want to open a PR against the camera app if they want it to more closely match the polish of iOS.
>but I don't think most people who buy a Linux phone actually want a Linux phone. They want an open-source phone.
Both of those are missing the point IMO. What people really want, is a phone that is on their side. iOS doesn't support open standards like Vulkan mainly because it's not in Apple's interest to support them. Not because it's in the user's interest, necessarily.
What people really want is a phone that they can trust to be on their side implicitly. The nugget of brilliance in Free Software is saying "if you do all this stuff, then the power will be so tilted towards you that you will be able to trust your software to be on your side".
People want something that's both polished, and won't [forego polish in one particular area for the sake of the company's interests/$$$].
> What people really want, is a phone that is on their side.
This. No matter how convenient and useful current smartphones are in daily life, there's always the nagging discomfort by knowing you are carrying a half-nefarious spying device. One where even the so-called reputable vendors can't be trusted to not put in malicious adware, planned obsolecense, and do everything in their power to ensure you don't really own the thing.
About a year ago I switched from Windows to Linux for my home media PC, and it's such a relaxing experience. My computer just does what I tell it to do, and nothing changes unless I want it to.
By contrast, whenever I do have to boot into Windows to run some specific application, it's like I've invited a corporate representative from Microsoft into my home. Things are changed for me on updates. The OS suggests things to me I have no interest in. When I want to use Microsoft software, I have to log into accounts for some reason, which often means a round trip through email to reset the password. Once Windows even changed firmware settings without asking me which broke things in Linux.
The best things about Linux are not what it does, but what it doesn't do. I want this for my phone as well.
Its time to upgrade your PC. Now. We don't care you're running a presentation. yeah We'll let you delay it... for now.
Its time to dim your screen. We don't care if you're reading a recipe while you cook. No we won't put a widget to allow this temporarily. We think its better buried in the settings. And you'll have to set it back later.
Its time for feature X to not work or not exist anywhere. We don't care that it worked in the old version. We don't like it.
> Summed up in the following:
> Its time to upgrade your PC. Now. We don't care you're running a presentation. yeah We'll let you delay it... for now.
My roommate in college refused the Windows update request enough times that it just took the decision out of his hands and _told_ him it was rebooting...in the middle of a LAN Starcraft game we were having. (Hilariously, Starcraft also ran perfectly on my Wine/Ubuntu and had all sort of weird bugs and visual artifacts on his Vista/7)
I truly can't imagine how anyone can consider a system that reboots without your consent, no matter whether you're playing Starcraft or giving a presentation or launching nuclear warheads, to be appropriate for serious work. It seems like one of the very basic jobs of an OS to _not turn off while you might be doing something important_. Perhaps the answer is as simple as "there's a setting buried somewhere that all technically-literate Windows users change", but the default behavior is beyond insane.
I heard RMS once say "proprietary software subjugates people" and at the time I thought it was over-the-top, sort of out-of-place like "the people's front of judea" opinionating in the middle of a software meeting.
But wow, phones and computers nowadays are like a giant steamroller, squashing users common sense, interests and privacy.
The "settings app" is a convoluted mess which is made worse by the fact that it wholeheartedly embraced the weird "everything is an app, except for some things" philosophy.
There are settings that only apply to some "apps", there are "app wide settings", there are important settings hidden 4 layers deep under some category where one would never suspect them to be.
Then there's the fact that MS has the tendency to just silently revert settings, often privacy and telemetry related, after updates. On that end, Windows 10 very much feels like it's actively working against the user, it feels like you are only a tolerated guest on your own system.
> MS has the tendency to just silently revert settings
This is so user-hostile it's not even funny. Imagine if you had someone in your life who silently went back on agreements when you weren't looking. You would work to remove them from your life as soon as possible.
I don't, but MS ships an annual update that for the past couple years has included expansion of the Settings App and remove of Control Panel widgets. The original Settings App that shipped with Windows 10 was, as the op said, useless.
As MS has slowly whittled down and removed features from the Control Panel, they have simultaneously added analogs where appropriate in the Settings App. The Settings App in 20H2 is very different and far from useless when compared to what shipped a year ago, or when Windows 10 launched.
The main criticism of Windows settings is the silent reversion of settings which is tantamount to ignoring them. If Microsoft improved the clarity of the settings menu then that's nice, but ultimately irrelevant.
You shouldn't need a third-party utility for re-disabling settings after updates, and it's pretty clear at this point that Microsoft just doesn't give a damn about respecting the user's choices.
You have summed my feelings about it excellently. The other day I installed an app in Linux that logs my activities, such as documents opened and programs used, and indexes it into a searchable database ("I can't remember that pdf I was reading last weekend, let me get it"). The most jarring feeling about that was... that for once I wasn't not thinking how privacy invasive all that data collection was! I'm used to seeing programs and websites attempting to collect all sorts of nefarious data and trying my best to stop that collection (including not using the product at all). I was stunned how useful it was once I realised it was all local and serving my interests, not those of its manufacturer.
> About a year ago I switched from Windows to Linux for my home media PC, and it's such a relaxing experience. My computer just does what I tell it to do, and nothing changes unless I want it to.
My experience with Linux on the Desktop is that it wants to install updates. It doesn't force me to install updates, which I appreciate. However, eventually I also want to install updates. Unfortunately, on numerous occasions these updates have rendered the system unbootable. This is not a worthwhile tradeoff.
This has never happened to me with Windows. I'm aware that it does happen to some users, but I have trouble believing that I'm just really unlucky with Ubuntu/Debian/PopOS and Fedora.
However, eventually I also want to install updates. Unfortunately, on numerous occasions these updates have rendered the system unbootable. This is not a worthwhile tradeoff.
Are these "updates" or "upgrades"? If the problems are with updates, I would say that your experience is not typical of most Linux users.
Its a shame that you are having problems because the modern Linux experience is pretty slick.
I had the same experience with ubuntu upgrades. Something was always broken.
I don't think you can blame linux, it's just a specific distro trying to do a task which is too hard and fail.
Not sure if it's still the case with ubuntu, I just run Arch which is a rolling release distro; I decide when to upgrade and what it implies + their info on breaking updates is always punctual.
Linux Mint has addressed this specifically. They enabled auto-updates in 20.1 only after they launched and tested Timeshift, which is a backup tool that enables you to boot into a past snapshot of the system much like FreeBSD's snapshots. It's geared mainly towards btrfs however, as ext4 doesn't support snapshots.
And to be fair, updates broke my Windows systems multiple times in the past as well. This isn't really a problem by itself since errors and mistakes happen, the problem is that the state of recovery tools in both systems is somewhat lacking. Linux can be repaired from Live USB and has Timeshift, but it doesn't have an easily accessible built-in rescue environment that's actually useful. Windows has DaRT, but all decent Live USB's for it are third-party and it's very hard to repair its internals if the existing tools don't work. FreeBSD is probably the closest to being bulletproof, but it has its own problems.
> I'm aware that it does happen to some users, but I have trouble believing that I'm just really unlucky with Ubuntu/Debian/PopOS and Fedora.
"Unlucky" is probably the wrong word, since I doubt all those failures were independent, but you're presumably in some niche with a high probability of update failure (just as the users failing their Windows updates are). For a counter anecdote, I've used Linux laptops/workstations (primarily Debian/Ubuntu, but dabbled in others) exclusively for 15 years and have never had an update break _anything_.
If I had to guess, I'd say that it's a hardware compatibility issue? Linux can still be a _terrible_ experience relative to Windows if you have strong opinions about the hardware you want to use. IME, all the people who talk about Linux being a vastly superior user experience to OS X/Windows are those whose hardware preferences line up with good Linux support.
Lucky you! When this happened to me with Windows last time, I had no idea what to do and how to diagnose it even though I spent a lot of time on it and had the knowledge of all of the Internet available. I had to reinstall and painstakingly redo my whole setup.
When it happened to me with GNU/Linux, it gave me enough rope to actually debug what happened, so I could fix it and get back to where I was before. And I went through several Ubuntu and Debian dist-upgrades, and now I'm even using Arch which is a rolling distro that's somewhat expected to break from time to time.
So sure, it does happen more often than it did on Windows - but I don't think I actually waste more time with that than I did when using Windows.
I had Ubuntu 20.04 LTS on a Dell Inspiron 3137. I ran apt-get update and it crashed and would not boot. I was preparing to lend the laptop out to family so I had to put Windows back on it. It happens. Your personal experience is not everyone's experience.
I would be intrigued to know what happened with this one.
Across well over a decade of using Apt on Debian, Ubuntu & Mint, the amount of times I have seen Apt crash, is never. By contrast I have seen Apt tasks fail leaving packages partially installed. If relevant, it may seem a trivial, semantic difference, but I think it is a little more important than that.
Following the typical Microsoft paradigm of 'just reboot and hope for the best' will rarely result in the desired outcome, and in the case of something like grub could well end up with a system that will not boot.
For me a key difference in this case, is I have never encountered an unbootable Linux system (outside of hardware issues), that I could not fix with some basic tools. I can't say the same of Microsoft products (Personally, I don't consider a fresh install a fix :) ).
I also would love to know more about this. The thing I do is wait for LTS version 20.04.1 or 20.04.2 before installing so all the kinks will be ironed out.
I've been running linux on the desktop for 3 years now and have never had an update break anything. If you stick to the more stable debian derivatives and forgo some of the bleeding edge features in a rolling distro like Arch (btw I do not use Arch), the update process should be pretty seamless.
Is that not the point here? Labeling something a "trope" isn't a self-contained argument. The reliability of Linux systems is terrible for certain contexts: modern gaming[1], universal hardware compatibility, taking advantage of bleeding-edge software updates (the analogue to which doesn't exist on Windows), etc.
IME, there's a lot of talking past each other when it comes to OSes. The vastly superior experience that Linux fans describe requires a couple of one-time boxes to be ticked, like constraining yourself to known compatible hardware platforms and stable software versions. There are plenty of people who don't realize this dynamic exists and trip over it, and it's not dodging the question to make them aware of these limitations and let them decide whether the cost/benefit fits their situation. Eg, in my case, I like Thinkpads, don't game, and need a stable, reliable, and performant system that I can be productive on. The pitfalls of Linux don't affect me personally, and I obviously can't meet the needs I describe with a Windows system (or to a lesser extent, OS X).
[1] I hear this is getting much better with things like Valve's Proton, but I assume that Linux is still far worse than Windows for a dedicated PC gamer that wants to play new games.
I think you make an excellent point. Many of the posts admonishing Windows speak to the loss of freedom but, as you pointed out, you have to willingly give up a great deal of freedom if you want stable Linux.
I'm not trying to bash on Linux, merely point out that for everything it does right there's just as much it does wrong. The same is true of Windows and MacOS.
No arguments there! It's a pretty good rule of thumb that the no-exceptions maximalist view is wrong, on almost any topic over which there's meaningful disagreement.
I never said they were doing it wrong. I said the distribution matters. If, for example, you are running Arch Nightly and constantly pulling in the latest and greatest features, you're likely to see some stability issues. If you're using something like Ubuntu LTS, you'll miss out on a few new bells and whistles, but you'll get a very stable OS.
Saying "linux" has a poor update process or stability issues is meaningless.
> If, for example, you are running Arch Nightly and constantly pulling in the latest and greatest features, you're likely to see some stability issues. If you're using something like Ubuntu LTS, you'll miss out on a few new bells and whistles, but you'll get a very stable OS.
"You're doing it wrong, if you did it right it would work"
That's true of software in general. You can use (often older) more stable tech and lose access to some newer features, or you can used the latest and greatest and get a few more features and accept a reduction in stability in exchange.
I've been running Debian testing for a long time, where I kind of expect things to break now and again; and I'm pretty surprised by your experience. The only breakage I've experienced were minor inconveniences, maybe it's familiarity with the OS? Modern Linux DE experience is quite good now a days.
I totally get your point regarding Windows, but does Android do this, too? The only thing mine does is auto-update apps, and only because I told it to. I didn't have to turn on auto updating. OS updates are still only suggested, never applied automatically.
But it spies on you. And transmits data about you to Google. And has pre-installed apps you cannot fully uninstall. And it changes your privacy settings without you knowing when new features are added.
Google spying on you is the least of your worries, they are the most transparent of all the big tech companies if you ever manage to dig into your Google profile these days.
If anything Google is so far ahead they are advocating more privacy and less data being sent if you choose, because they don't sell it directly to people like a local grocery store with its own app or Amazon does.
Federated learning AI is basically making it where Google can continue to have all the benefits of massive data mining without any personal information ever having to leak out
> OS updates are still only suggested, never applied automatically.
The parts involved with spying on you will update regardless of what you want or say. Unless of course you're not using the play store (or any other google services).
my android phone has a nagging "security update" popup that I cannot delete. I don't update so it stays with my phone all the time (it takes a huge amount in the pause screen), i have to deny the updates each time i restart my phone (which doesn't happen often). Nonetheless, it's true I can still use my phone (and the appstore)... huh, now that I take a closer look at this annoying update it appears to be from samsung not from google.
Why would you not update your phone security updates? Do you even read anything about Android updates. It's extremely important for vital security flaws if you use any sort of modern apps.
It's a huge advocate of keeping all my data private but now knowing how useful it is to anonymize, encrypt and use it all on my device with things like Google Pay, I strongly advocate if you're using Google or Samsung services to update.
Plus these updates usually are Android level and not related to Samsung or Google
Most of those updates only apply to the latest. So it isn't just Android it is all the other parts too. For a few months you can only get security, but eventually they decide the only version they support is the one with whatever changed google made to the core not related to security as well.
This is simply not true, unfortunately. I run a Fedora system for more than ten years, and during this period updates shoved into my system tons of unwanted stuff. I still prefer the system to the alternatives, but let me tell you, there is simply no way I would install flatpak into my system, and if it wasn't for the terrible log spam it filled my log with, I probably wouldn't even know it arrived. But it would still be calling home and look for new packages that I will never want to use.
Maybe, even probably, no one have any nefarious motives behind the latest changes, but someone decided that if I want to upgrade my system now I have to start using systemd-resolve, and while I can and probably will alter it so it won't bother me, I wouldn't be installing it on my own.
Also, Firefox is the king of unwanted changes with little to no warnings, and while technically it isn't Linux, one day an innocent yum or dnf update install just killed my customized setup, flagged all my beloved addons as unsupported, and left them in disabled state.
>My computer just does what I tell it to do, and nothing changes unless I want it to.
>whenever I do have to boot into Windows to run some specific application, it's like I've invited a corporate representative from Microsoft into my home. Things are changed for me on updates
Yeah, it is really nice to have a consistent interface. But there is a flip side. Sometimes, people have to change in light of new security problems, and these sometimes need to be done quickly. The most obnoxious of these updates are interface changes (both UI and API). I think Windows does this too much and maybe for non-security related issues. The only real example I can think of is how OpenSSL uses envelope functions because ppl would abuse the primitives [Source: Alexandra Boldyreva, Christopher Patton, Thomas Shrimpton:
Hedging Public-Key Encryption in the Real World].
I literally and honestly feel like the only difference here is that vast majority of linux distributions don't have auto updates enabled and windows does. I'm literally afraid of running apt-get upgrade in Ubuntu because always, inevitably, things change and move about , which I hate with passion.
The problem isn't automatic updates, it's the philosophy behind those updates. On Ubuntu (last time I used it some 5 years ago), an update fixed bugs in software and that's it. Occasionally you'd get a new feature here and there, but rarely in the shell and existing features always stayed in their places. On Windows 10, updates ship breaking changes basically every time and there is no regard for consistency. Whether the updates are manual or automatic is an implementation detail - eventually, you'll update either way. The big difference is between a rolling release with no promise of compatibility and a versioned release with LTS.
Strange, my experience is also the exact opposite. I really wonder why that is?
I'm running about 10 windows 10 machines, various builds, auto updates enabled. Some in a domain, some in a workgroup. The last time an update bricked a system, or even broke a feature, must be over a year ago.
Now on Ubuntu, I have the same experience as some other posters. I'm reasonably confident that I can update if I do it semi regularly. But the number of times I've experienced breakage that lead to hours of bugfixing during $DAYJOB, is way too high. Now everything is in its own tightly controller docker, no more random breakage (unless docker breaks, or a key expires...).
A debian 9 apt upgrade actually managed to render my install inoperable once. But that might be semi-unfair as it had to do with graphics drivers.
Are you running windows systems on semi-recent hardware? Or is it all decades old thinkpad laptops with shitty thirdparty drivers?
This is literally the opposite to me. Running apt update/upgrade never breaks anything except a long time ago when I ran out of disk space during an update. This could have been handled better, but it isn't a usual scenario for me.
I can attest to this anxiety. There is always this question of what will happen if the update is botched and it bricks my system. This is why I consciously stay slim on the host OS (I have used Fedora in the past, and am now using Arch), and run almost all of my applications via Docker from a local container repository. The /home/username directory is backed up rigorously in the internal network so as to cover my ass if an update bricks my computer. As paranoid as I am to go through this, I am yet to need that backup because of a botched update ;-) The only times I reached out to backup were "I deleted this, but I shouldn't have..." scenarios.
The same paranoia applies to my MacBook Pro as well that was provided by work. All user generated content gets backed up regularly to aid recovery if things go north.
It's more than that isn't it? On Ubuntu I never candy crush come pre-installed, and I never have random popups on the bottom right corner of the screen for all types of reasons
Counter example. I switched from Linux to Windows because I find its desktop-experience to be superior. In my mind software and hardware is evolving at a rate that makes it impractical to support the notion that I could usefully modify it myself so it mostly comes down to trust. Do I trust Microsoft more to protect my long-term interest than some unknown group of open source maintainers? Looking at being able to access old data and run old programs I feel MS have been doing a great job. Now if they come up with a way for me to make sure that my data is in some standardized format AND protected in such a way that I could reasonably expect nobody (not even MS) to read it (but still be able to offload it elsewhere) I’d be entirely happy.
Literally the only significant amount of data I've ever lost in my life, either on a personal or professional context, were: 1. half a decade of emails dropped by Microsoft from my old Hotmail account with no reason or warning; 2. all my highlights on a 3000-page book series lost due to a iOS update breaking compatibility with the app I was using for it.
> Do I trust Microsoft more to protect my long-term interest than some unknown group of open source maintainers?
Do you? I don't. Microsoft is exclusively profit-oriented, they'll sell all your information in a heartbeat if they believe to have a legal way to do it and that it won't kill them in the next 5 years.
A group of open source maintainers (the more radical the better) will not. They will (usually) not polish the product as well, and they might be difficult to deal with if you found an issue (but you _can_ talk to them, unlike Microsoft).
I definitely trust open source people more, because they do their thing for ideological reasons and based on principles, not to maximize engagement and ad-spend and their yearly bonus.
Your concerns are the same that I had up until about 3 years ago when Microsoft and Google changed everything because at least at Google they do not care about your actual data because they can aggregate and anonymize it and a level that nobody else in the entire world can.
This is why it's way more dangerous to give data to even open source apps that are encrypted and secure because if they ever do change your privacy policy and you don't pay attention to it, they could say they start selling your data and you continue to agree to it.
That's why I like using a system which gives me control over which updates I want to receive. I'm not forced to take updates on an operating system which can also change the privacy policy on me and has done so in the past.
The Stockholm Syndrome is strong with this one. The fact they pitch their skills at anonymizing and aggregating data doesn't change the fact you can't trust Google to not utilize data exfiltration techniques in the first place. Your argument about open source license changes applies just as much, if not moreso to Google as well.
Google has actually went even further in making it transparent where they show every bit of data they have on you. You can delete it all review it all have it auto delete, they don't need any of it
> What people really want, is a phone that is on their side.
This will never happen. Personal radio communication is innocuous compared to what a modern cell phone is, yet personal radio communication is heavily restricted since decades.
Maybe we will eventually see an open source radio stack and truly open source apps. This will only happen once surveillance and kill switches have been moved to another layer.
A cell phone will never be on our side, it is far to dangerous.
There exist cellular and wireless cards for PCs too, and still a Linux PC is on our side. But if that's somehow not enough:
You could use proof-carrying code or reproducible artifacts to keep the radio stack out of the users' control while still making it obvious what it is that radio stack does.
The BIOS analog would then only accept radio code that behaves in a particular way, but it would be clear from the (open) source that the radio code is not spying on you.
I’m not sure how you’re measuring the differences between cell phones and “personal radio communication” here. Cell phones are personal devices built around 3-5 different kinds of radios.
If you’re contrasting it with the HAM/Shortwave community, there’s an obvious difference in transmission power. The Electromagnetic Spectrum is a public resource we have to share intelligently. All the core tech in a cell phone is about how to use spectrum efficiently, delivering high speeds with minimal interference. Shortwave is much less sophisticated and operates at much higher power. There are real costs to amateur radio enthusiasts blasting transmissions with incorrectly configured equipment.
Android had plenty tools in the past to allow that. Xprivacy even used to allow you to select which Contacts you want to allow for which app. So you could use WhatsApp but only allow a handful of contacts to be read.
One of the frustrations people have with Google is that they're making it increasingly closed and problematic to make modifications. Given that nowadays some banks for example are mobile only and everyone is waiting for Google to completely shut down modified boot systems(probably in response to Qualcomm TrustZone being untrustworthy), people are re evaluating whether it makes sense to invest in the Android ecosystem.
EDIT: google could have capitalized on this and made it a part of their offering.
That's because you're trying to use apps that use the services of Google. Pixel phones are still the best to use to wipe and put other operating systems on
On Android phones, if you enable "developer" in settings, the app "fake GPS settings" can do that.
Caveat: It's been almost 4 or 5 years since I used it. I used to prank colleagues on Facebook by posting from a local prison or other weird places. Have had no use for it since I deleted my fb account. So I don't know if it can still do what you want.
Also I think the apps can check for this. It's also been several years for me but I remember using an external Bluetooth GPS receiver needed this setting to allow an app to read the BT data and feed it into Android & some Apps just refused to work.
That is because of Androids stupid permissions-system where you have to give all requested permissions to an app before being able to install it.
On iOS the app installs and works and THEN it might ask you for GPS permission and you can deny that and the app keeps working, just without the feature that needs GPS.
I just installed Mi Home, a chinese app which requested every permission there is. I just denied all of them, could still use the app and am 0 afraid that the app somehow accessed my data.
> you can deny that and the app keeps working, just without the feature that needs GPS
A phone that would truly value the user would allow the user to provide a fake GPS location. Then you could use features that need GPS and not give up your privacy. But Apple doesn't allow that since it would make the phone less useful for companies who want to use phones for tracking.
A phone that truly valued the user would allow users to install multiple copies of an app, and allow the user to log in with different accounts. But Apple doesn't allow that, because they don't want people to share devices.
Yeah, your GPS example doesn’t hold up. How is denying an app location info consistent with your position that Apple wanting to enable companies to track users?
So you, I suspect, don’t want to “avoid tracking” so much as you want to avoid geo-gating of apps and content.
Content distributors rely on such features to satisfy legal obligations about what content they can show where. If the OS started adding features like “pretend I’m in location X” or “download movie regardless of app restrictions” (as an example of another feature that could be argued is pro-user) then at some point you’ll have a platform that isn’t commercially supported or viable.
Honestly, Apple is by far the most pro-user company in this field and there are countless examples of this.
But a very small minority chafe against the restrictions that are actually in most users interests (eg not allowing side loading of apps, which for most people would simply be an attack vector).
> Yeah, your GPS example doesn’t hold up. How is denying an app location info consistent with your position that Apple wanting to enable companies to track users?
Many apps require location data for access to features. If you can't provide a fake location, your only choice is to either accept tracking, or not use the service.
Lots of companies use phone apps for tracking (eg. for tracking location of agents). The company will immediately realise when you turn off GPS access. If you had a way to spoof a location (eg. tell the phone to pretend you stayed in the current location), you could go to the toilet without your employers knowledge and without leaving your phone behind.
Abusers often use phone apps to track their victims. If you are in an abusive relationship, you may be too scared to turn off Find My Friends. If the phone was actually on your side, you would be able to enter a fake location, and your abuser wouldn't have to know that you visited your parents on your way home from work.
Apple wants location data from iOS users to be hard to fake, because it is more valuable this way. Apple's most important asset is the value of their ecosystem. It's why they can charge companies 30% to access it. The user's needs are secondary.
Yeah, I don't buy it, frankly these all seems like minority use cases. I imagine if you were to poll all i-phone owners this would all be bottom of the list in terms of wants. I think a lot of people here conflate "What I as a tech and privacy enthusiast want" and "What everyone wants" very often. The feature you suggest would be used by a very small percentage.
That's not to say I wouldn't want it either but I'm pretty privacy conscious, and a tech enthusiast. I just don't think you can say Apple is putting user's needs second, I don't imagine most users need this.
> Abusers often use phone apps to track their victims. If you are in an abusive relationship, you may be too scared to turn off Find My Friends. If the phone was actually on your side, you would be able to enter a fake location, and your abuser wouldn't have to know that you visited your parents on your way home from work.
This exact same feature you are asking for would be useful for people abducting children, who could make it look like the child was still at school while they took them away.
This is far more likely to be why Apple hasn’t implemented it.
Yeah I’m going to need examples of what features get locked by not providing location. I’m just not buying this is anything other than wanting to avoid geo restrictions on content. I mean I understand the desire for this but I also understand the desire not to pay for content, so this is a thin one when it comes to “freedom”.
Oh and as for tracking, at least for the company they can already track you by what towers you’re connected to. So there’s no technical limitation on this being provided to apps regardless of what you might spoof.
> Yeah I’m going to need examples of what features get locked by not providing location.
Strava refuses to let you track your ride if you don't allow always-on background tracking. (They changed this about a year ago. Previously "while using the app" was sufficient)
A lunch menu app that I used before Covid allowed you to show nearby restaurants based on location. But there was no way to manually enter a location (without GPS it was just a huge unsorted list).
These are two examples that come to my mind (I'm not a person who uses a lot of different apps, I'm sure there's more out there. Try rejecting location access for a few apps and see what happens)
Edit: I'm also not sure why you are so hung up on geo restrictions. I don't really care about geo restrictions, and even if, you could avoid them trivially with VPNs that are widely available. That just has nothing to do with keeping my GPS coordinates private.
Just to clarify, Android has had the ability to request permissions ad hoc in the user journey since Android 6.0.
But it is true that Android won't reject apps that refuse to work without a permission while iOS mandates that basic functionalities of an app work even when permission is denied.
And meanwhile, 6 years later an app can be submitted to the play store that ignores that and just blanket asks for permissions and refuses to run without them.
"But given its importance and that i0S 14 already has a similar feature, it's more likely to ship than not. What could make Google's implementation better than Apple's is how easy it is to access more information requires you to head to the settings to see exactly what's going"
Well then, you should make sure that you're providing a useful service with that data, or allow data collection to be turned off.
Think of it like this: if I'm actively using an app that's giving me turn-by-turn directions, then of course I'm not going to want to spoof GPS, since it would make the app useless to me. But if your app demands GPS data just for ad analytics, then yes, I would absolutely and without any remorse spoof GPS data for that app. In that latter case, I don't care that a developer might be unhappy with it, because as a user I'm unhappy that the developer is slurping up data they don't need!
Good question. I still think that its up to user to decide what data he shares with app. If its crucial for app to know that gps position is not faked, app could do some heuristic. Check if user is not moving faster than some limit, does not stop moving for extended periods of time etc. Basically anticheat engine. Only area where this whould be relevant i think is online multiplayer games. Otherwise, if user is faking gps he is messing up his own experience.
2 different permissions: Possible faked GPS data, and Not faked GPS data. An app would really need to explain why it can't accept possibly faked GPS data.
I like that idea, although to me that is kinda the status quo and I'm not sure the folks who want to be able to fake anything at will would be ok with that.
i argue it's not an issue. If the user decides to spoof to cheat in the game, there are other ways to detect it (such as speed limiting - which, as i understand, pokemon go already does).
If the app wants to force a user to not modify their phone just so they have a secure enclave for which they can implement DRM, then i can't agree to it. This includes things like spoofing, but also things like memory edits or hacking save files, or anything else client side. If the app needs secure storage that's unchangeable, they can save it on their servers.
I don't play Pokémon go, but with my understanding of the game I'm not sure how spoofing the GPS would impact other users in a negative way.
Considering that most of the world has some form of travel restrictions over the past year, and I believe that being able to interact with friends in the game requires you be be in very close proximity. Can you explain how spoofing GPS data so that people are allowed to play together even though they are not close is bad?
>I'm not sure how spoofing the GPS would impact other users in a negative way.
You could attack a pokemon gym at your convenience (from your couch, whatever time of the day). This negatively impacts other players because a legit, non-cheating spoofer will have to expend far more effort to do the same thing.
>Can you explain how spoofing GPS data so that people are allowed to play together even though they are not close is bad?
Friend interaction or just interaction in the game has to do with raiding and trading. You can already league battle (pvp) over any distance.
Niantic has made some changes along these lines - main one is the remote raid pass. One person close enough to a gym can invite friends to raid, no spoofing needed. They also upped the trade distance, how close you need to be to interact with a gym/pokestop, etc.
So the answer to your question is the game itself has made changes to address actual in-game scenarios. That leaves spoofing GPS as a way to asymmetrically cheat against gyms, or perhaps trivialize collecting pokemon (some are region locked and so on).
In games like Pokemon Go (and similar augmented reality games) players go to real world locations in order to gather resources, and battle the pokemon of another user who currently holds that position.
If you can just spoof, the whole nature of augmented reality falls apart and someone could simply spoof themselves anywhere and take those positions. It was a big problem before the android os made it harder to spoof.
There's no point/ fun in playing augmented reality games if enough people simply cheat and the real world limitations aren't a factor.
I played pokemon go seriously for a few years (both at the beginning and recently) and honestly spoofers are an issue only because imho Niantic is incompetent and doesn't care.[1]
not to say how it you are anywhere not in a medium size city you need either spoofers or endless grind to unlock significant parts of the game
[1] to be fair I left before the pandemic, so I cannot comment on how they handled that
As a user I don't really care about what you want or need. You're not supposed to get any data at all unless it's strictly necessary. You're also supposed to delete any data that you do get after you're done using it in a way that benefits me and me alone.
I'm a developer too, but no, sorry, the user comes first. They're paying the bills and your salary.
If your app needs to get info that benefits the user (as the mapping app GPS example), nobody will deny it because it makes sense.
If your app wants to get info that benefits you but not the user, it only makes sense for that data to be denied (preferably) or faked (as a backup plan). You have no right to it.
> It’s easy to feel that iOS isn’t on your side when you can’t use a non-WebKit browser and can’t use an adblocker.
Not only does Safari allow for 3rd-party adblock extensions that are pretty good, there are iOS browsers available, like iCab Mobile[0] for instance, that allow for extremely fine-grained, granular and tweakable ad-blocking, filtering, domain-blocking, and CSS and javascript rules - all of which can be user-edited and refined to fit exactly the user's own requirements.
There are always so many comments like the above in these threads: often characterized by people banging on iOS because it "can't be customized the way I want it after I paid so much for my iPhone". But these seem to be just standard consumer-mindset complaining from users that don't even have the intellectual curiosity to investigate whether there's actually anything already available that solves their imagined problem, or even try to fix it themselves - just as the article says.
You still can't use a non webkit browser though. It's Internet Explorer levels of non-competition.
I would love to be able to say to my users, when they experience an issue with Safari - "you can try a different browser". But I can't because the same issue will be present in Chrome.
But that's what you a developer want, not necessarily the users. I'm extremely happy that you can't tell me to use another browser and have to fix your code for Safari instead. I think that you have a right to decide which browser I can use, even if I'm your costumer. I knew the rules when I bought my iPhone and had to accept them, even if it means only using webkit. Being forced to switch to Chrome when using a specific website just because the developer didn't feel like making it work in Safari is very annoying on the Mac and would make me go nut on the phone.
It's not "fix my code" when Safari doesn't even support the feature or it's simply broken - or most annoyingly, it works one day and breaks with an update. (See: webrtc stuff)
You might have known the rules, but most users don't. Plenty will come to me saying they've tried both Safari and Chrome and that it won't work in either, indicating they have no knowledge of webkit.
Android also randomly breaks things now and then, but I can at least direct users to Firefox, which never seems to have any problems.
Please understand redirecting users to another browser is only ever a last resort. If I can fix the code I will, but sometimes something just stops working and I can't even reproduce it.
...and I have a teacher who is relying on my app for their classes this week and "try firefox" could save them...
There exist adblockers but as far as I’m aware they all work at a network level and not at a script level, which means that 1. They suck and 2. You can’t use a VPN and an adblocker at the same time.
Quick appreciation regarding the intellectual humility required to add this to the end of your comment. In my humble opinion, this kind of attitude and approach represents some of the best of the HN community.
It's true that Safari content blocking is rules-based, but its not on a network level, the logic is implemented in the WebKit renderer. So in addition to blocking URL patterns, it is also possible to make rules to hide specific elements by CSS selector.
It’s the other way round actually. On iOS you can install an adblock ruleset provider that Safari can use natively. On Android it’s only VPN or an adblock-enabled browser (that is usually yet another set of issues) because Chrome is adblock’s enemy. At least that’s my experience after long research while using both OS (recently, mid '20-21).
Properly configured, you can get much better adblocking capabilities on an Android phone than you can on iOS.
There's a weird situation with mobile phones where for most people who aren't going to go out of their way to make their devices private, Apple's ecosystem is the right choice; it has better defaults and better sandboxing. But once you do decide to go out of your way to make your device private, Apple's ecosystem stops being the right choice.
On a rooted Android phone I have network-level adblocking on my device that directly works with the firewall. I also run Ublock Origin in my phone browser, which blows every single Safari adblocker out of the water. I can also cut off Internet access to specific apps and games, not just to domains. I also have access to a litany of Open Source apps that wouldn't be allowed on app stores like NewPipe that improve my privacy by replacing services. And LineageOS imposes additional sandboxing on top of Android's built-in features.
But if a friend buys a phone, they're not going to do any of that. They can't get NewPipe because they're not using F-Droid. They're probably going to stick with Chrome, which has next to no adblocking or extra privacy controls. An iPhone will be more private and more secure for them in almost every way.
So it's a weird situation where which device is more private depends a lot on who you are. For most average consumers, it's likely iOS. But it's not quite so simple to say that iOS has the best privacy overall.
For network level blocking on Android there's no need to root or go down any rabbit holes. Just set your DNS to a adblocking service like nextdns. It's natively available since Android 9 and there are workarounds for older versions (usually by using an app that pretends to be a VPN).
You can do DNS based adblocking on Android as well using the built in "private DNS" support in combination with something like NextDNS. Doesnt need a VPN or special browser.
I don't know about Chrome adblocking because I'm using Firefox on all my Android devices. I installed uBlock Origin and I'm using it to block elements with CSS rules (lots of annoying sticky headers and useless navigation bars.) Sometimes I use it to block scripts. My primary adblocker is Blockada which is a local VPN and blocks all ads in all apps. This means that usually no ads make their way to Firefox and I remove their empty spaces from pages with uBlock.
The shortcoming of using Blockada is that I can't use another VPN. I don't really need it yet, but if I would that could be a big problem.
I don't know why Google doesn't allow chaining VPNs. Maybe the UX would be too difficult on a phone, maybe it's a real edge case not worth spending money on, maybe it would be used only to block ads.
If you want both: a blokada-like adblocker and a VPN, setting one up with Algo and WireGuard is quite easy. I've been using it for ages and it just works without me needing to interfere.
They kind of suck because of the reasons you mention but you can absolutely use them with a VPN and I do think they've gotten better over the past six years or so that I've used them.
This hits the nail in the head. For a phone, open source doesn't matter and Linux doesn't matter.
It's all about for who's benefit the product is built. I like the phrasing of having a phone "on my side".
In a recent thread here on obsolete hardware I was commenting how up to the fairly recent past products were built with the idea of competing on features the user wanted (or at least presumably wanted).
But no longer - in the last ten years that has shifted in too many industries to be all about features that the company wants (spyware, tracking, DRM, cloud lock-in, and on and on). The phone duopoly is a poster child of this evil trend. Neither platform puts the user first and into the drivers seat.
So no, I don't want an open source phone nor a Linux phone, specifically. (Not saying I'd mind if one or both are true, that'd be cool, but not a deciding factor.) I want a phone where I the customer are in full control of what it does. I must be able to override anything the OS wants to do and to override anything any app wants to do.
> What people really want, is a phone that is on their side. iOS doesn't support open standards like Vulkan mainly because it's not in Apple's interest to support them. Not because it's in the user's interest, necessarily.
I couldn't agree with "people want a phone that is on their side" more.
I also agree that Linux matters as much as iOS's BSD heart—that is, it doesn't. But this is also why the Vulkan example doesn't serve your point. As with Linux, technical implementation details aren't why people are using iPhones.
Most people use iPhones because of the complete experience. For the few who care whether the iPhone is "on their side", it is clear that Apple's business model is generally aligned with their interests. This is either unknown or untrue for alternatives.
This is where open source phone vendors will fail. Trust is not simply a technology problem.
Except the iPhone is really not on the users side. I do tend to think the iPhone isn't going to spy on me, or at least if it is, it's going to be doing so to a much lesser extent than Android.
But it's also not going to, for example, let me install a web browser which is anything other than a Safari reskin.
There are other factors to 'being on the users side' than just privacy.
Honestly Vulkan was just a lazy example, but it's hard to give a good one when I don't use Apple products in the first place.
A better example might be places where it's hard to switch away from Apple's systems, or perhaps how they only support hardware that doesn't last very long and are notoriously hostile to attempts to repair your device.
> What people really want is a phone that they can trust to be on their side implicitly.
Absolutely! These days our computers only do things that align with big company interests. I want a phone that will obey me even if it means ruin for its maker.
> iOS doesn't support open standards like Vulkan mainly because it's not in Apple's interest to support them.
Or maybe because Vulkan was a standard so long and late in the making that Apple released their own graphical stack a year before the Vulkan was even announced?
I want a phone I can own, like my sofa. It is out there in my living room just waiting for me to do whatever I want to do with it.
My Android phone doesn't work that way. The company behind it expects me to do certain tasks with the phone. Some tasks are open for gradual adoption, other aren't, meaning they are mandated. After all those years, I'm beginning to dislike that.
It is perfect, since you have zero expectation your sofa should be transformed into something else, or make any provisions or concessions in its design towards looking or performing like some personalized flavor of sofa.
Similarly, the sooner we get over the trope that any handset maker must be forced into selling a tiny general purpose computing device instead of an iPod PDA communicator, the better. It is what it is, let makers just make it the best, without unnecessary and less reliable modularity. Yes people want that, it’s a market segment, and so other makers can make things for that category.
Good point. And the company behind Android mainly wants to ensure they can get as much data from you as possible. You will never fully be able to disable the data upload to Google.
A primary requirement I've had over the past few years when purchasing a phone is whether it is supported by Lineageos. Less data is collected hopefully, without gapps installed.
Interesting how this seems to be the common belief, but AFAIK AOSP does not do this, while ironically Lineage uses Google for connectivity servers and fallback DNS.
> I want a phone I can own, like my sofa. It is out there in my living room just waiting for me to do whatever I want to do with it.
The reality of this is much different. To the average person buying a Linux phone, their new sofa has 3 legs on Tuesday, they can only invite 2 friends to sit on it if it’s an odd number day, and sometimes the fabric glows in the dark. 1% of the time it works exactly how they dreamed and 99% of the time it’s frustrating.
But they own it and can fix all those problems if they’re so inclined! Or they can be at the mercy of people who can fix those problems and hope they don’t see the random glow in the dark fabric as a feature and that they don’t prioritize the problems they’re having over the problems they’re having.
Or they can buy an iPhone or flagship Android phone and have it work exactly like they want it to 99% of the time and be frustrating 1% of the time.
The average person’s iPhone/Android is the sofa in their living room just waiting to be used.
> The average person’s iPhone/Android is the sofa in their living room just waiting to be used.
Except, it isn't.
Because at random times the sofa company comes in and reorganises the way the cushions are positioned. And then they take away the ability to use the tilt function.
Then, because they really need to know how they use the couch, they'll start tracking when you sit and lie on the couch. So when you have your day off and its outside the scheduled expectations, when you sit on the couch they suddenly come over and put locks and chains on the couch because it clearly wasn't you who was using the couch.
Most people just accept this, because what are you going to do? Buy a couch that doesn't have tilt or cushions? You want those! You don't want a wicker chair, you want a comfy couch, so you have to deal with the couch company making life hell every so often. Because there isn't an alternative for the average person.
I field calls from my parents at least once a week about something that has "broken". The tech support is like pulling teeth, because everything is hidden from the user. They don't know what they did wrong and all that they want is for it to "work". And half the time I can't help them - because the phone doesn't belong to them and the OS or apps has decided that X feature is no longer worth supporting, and force-updated them to the latest version. Rolling back to the version that did work is difficult or impossible.
They also installed sensors in the cushions that detect and measure gasses. They will know when you eat, what you eat, what your friends eat, when you and your friends are having a good time or when you are stressed. They will share this data with 3rd parties. You probably consented to this in some agreement. Your friends probably don't know their data is shared via your consent.
I like open source too, but I'm not serious about it, I want to be able to fix things or file an issue on GitHub or whatever if necessary, but I don't have the energy to worry about proprietary blobs.
Having control of my phone and its configuration like I do my Linux desktop is what I want, but I'm slightly resigned to perhaps not getting it because of app support (I tried Anbox on my desktop, it was buggy and slow, with a fraction of the RAM I dread to imagine) - so I've been thinking about and occasionally working on a Terraform provider for Android instead. So far I'm using it to install all apps, no Play Store at all; I'd like to have it handle settings too.
So yes, it is Linux more than OSS that appeals to me here, because it's control more than openness that interests me in it. (I suppose some wouldn't see a distinction, and that's partly why it is more important to others.)
I think you have it completely backwards. You want a phone that runs a FOSS operating system. It doesn’t matter to you that it is Linux or a BSD or some other open source kernel.
Android is a Linux phone but it’s decidedly not open.
No, it's not particularly important to me that the OS is FOSS (it's a bonus I appreciate, but what I dislike about my work Mac is that it's hard to configure and changes between versions and bundles crapware, etc., not that it's not FOSS).
Another Unix would be ok as long as it's not hidden away under a forced UI, with some things unconfigurable, required, etc.
But ultimately I want to share dotfiles between my desktop and phone (sure I might have to accept some amount of conditional guards..) - and that pretty much means Linux and ideally Arch. But only because that's what I happen to use on non-phones.
One VM per app would need a lot of RAM. Maybe one VM for Linux/Android, and one for iOS, would be a decent compromise. We'd still 'waste' some RAM, but isolation between different Android apps could be handled by cgroups/namespaces.
He said Android or iOS. It seems like massive overkill to have a phone that can run both. Even running Android apps well is a pretty tall order, running iOS apps natively on your own open source phone seems like a pipedream. It took even Google a long time and a lot of investment to get Android apps to work reasonably well on ChromeOS.
True. The question is whether the Linux emulation can be good enough to satisfy Android. There are lots of funny quirks ...
I wish something like CloudAPI/Capsicum would take off to be more secure, while also being an open platform, instead of Linux ubiquity rendering standards irrelevant.
I have no idea. I was asking because I wanted to understand better the position of the person to whom I replied. They said they wanted Linux specifically, and not just open source.
I didn't understand why it's so important for it to be Linux, as opposed to any other operating system that's as hackable/customizable. So I wanted to know if I had missed something.
> I didn't understand why it's so important for it to be Linux, as opposed to any other operating system that's as hackable/customizable.
I should apologize for my response then. I'd thought you were alluding to iOS, and thought that it was strange to bring that up when discussing configurable OS's.
I don't think it being Linux is too important for people. If somebody made a working FreeBSD for a phone and there was official support for that device, then people wouldn't be all "Well, it's not Linux". I don't think I've seen any interest from BSD maintainers to bring any form of it to phones though.
As it is now, the PinePhone is officially supported by Manjaro and that makes it the most obvious option. Also, all attempts thus far to bring open source to mobile has been some form of Linux, so it's natural that when people think "open source phone", it's probably going to be using Linux. PinePhone itself already has 18-ish different distros, including ports of Debian and Ubuntu, so it's certainly well on its way.
I've had a Nokia N900 and the few Palm/HP Pre models that were released, the former ran Maemo and the latter webOS. Both OSes were based on Linux.
I want a Linux kernel, because even though today I'd list the modern niceties like namespaces, containers, WireGuard, NFS 4.2+, back in the Maemo days, having a Linux kernel still paid dividends. All of the standard networking and WLAN debugging tools you had on desktop Linux were available in your pocket, FUSE meant you could use sshfs, etc. The userland was the same GNU userland you'd find on most Linux distros, you could use X11 forwarding via ssh, GTK apps worked, and you had apt as the system package manager.
I want that again. Android doesn't come close, and neither does iOS.
I have my media collection shared via NFS over my VPN. I want to use MPD locally on my phone like I could on Maemo.
Also, if I'm at a friend's place who has a Roku, Chromecast etc, I can already cast media from my NFS collection easily from my Linux laptop via VPN. I want to be able to do the same thing with my phone.
At least personally, I want a phone that works similarly to my Linux machines. I have scripts that maintain a synchronized configuration across all of them, and I don't want my phone to be some snowflake that must be treated specially.
I want access to the same applications; I want to be able to run strace on random processes to understand what they're doing; I want to be able to organize my files under $HOME the same way I do in my other machines.
I want a Linux phone (ideally of a similar distro). It being open source is just part of that.
This is also the reason why I'm not really attracted to PineTime, despite it being open source.
If by polish you refer to aesthetic stuff like animations and whatnot, I don't really care about it.
I don't understand this comment. Am I not allowed to use Linux if I haven't ever committed code to an open source project? I've been using Linux for 15 years. Are you taking away my Linux card and am I being banned from the platform?
Because your argument makes no sense at all as to why I might want a Linux phone. I want a Linux phone for the same reasons why I use a Linux laptop and PC. Freedom, control over my computing environment and my data, that sort of thing.
Taking a step back, there is no mobile OS out there that provides the things that I want. The closest that I've seen is Linux for the PinePhone. So, yeah, I want a Linux phone. It's not that my initial premise was "I want a Linux phone". It's "I want control and I want to have the freedom to do what I want with my device, so what system currently offers that kind of freedom while being feasible on technical and usability levels?"
I bought a Pine Phone. I want a Linux phone. I don't want "open-source iOS", whatever that is. I don't care about that kind of "polish", I want access to (a good portion of) the same "Linux software library" that I use on my Linux laptops, VMs and Raspberry Pis. Plus it's nice to be able to make a phone call from it or take a photo occasionally.
Some polish would help. Ubuntu phone OS is just awful. The first thing I did was starting to check what else is available. That is not a step a typical use is willing to make.
And sadly, pine is still not my daily driver. At this time, it is a toy.
I want control over my devices, so linux phone is not a bad idea. We keep missing on execution though.
> And sadly, pine is still not my daily driver. At this time, it is a toy.
It was never sold as a daily driver and this was always made abundantly clear in every Pine store page since the beginning of time. Even now they only call their latest version "beta" for a good reason.
I'd want one so I can run some Python scripts in the background. Where I can use apt and install whatever I want from the repositories. Use ffmpeg to record audio and video and stream it in the LAN or even over the mobile network.
Some of these devices already have 12 GB RAM and octacore processors, that's more than a Raspberry Pi.
When these devices reach their EOL as a phone/tablet, they would make wonderful SBCs with integrated touchscreen, camera and microphone, and in the future also good AI co-processors for good on-device speech or face recognition. All this with an up-to-date OS, and not an Android version which is over 4 years old.
Whatever I try with Android, sooner or later the processes get killed.
What's worst is that when Chrome gets updated, any app using a WebView gets killed. Why not just let it continue running and make it use the new WebView after it gets started again manually?
I guess I always looked at Android's propensity to killing processes ultimately not just as a RAM saving tool, but as a battery saving tool.
That whole process lifecycle thing that you have to jump through with activities and bundles and what have you is so that your app disappears not just out of RAM, but out of the scheduler too from a piece of code that can make such decisions at a complete system level. Yes, it kills processes essentially arbitrarily, but the processes should have all of the hooks and places to squirrel away state to come back from the aether as if nothing happened. Programming Android code should embrace that rather than fight it.
As for webview, I think they're generally pushing a security fix and think that your app should be able to pull itself back together, the same as if a browser was refreshed.
I do have 5 tablets in my home, held with magnets against the walls, which do nothing else but have a custom app running which displays a full-screen WebView.
It shows stuff like weather, clock, calendar, land-line phone calls and has buttons for light scenes.
I used to use Chrome for this, but I always had to manually maximize the page, and hosting it in a custom app has additional benefits, like loading and maximizing the page as soon as the device boots, and offering a JavaScript interface so that the page can interact with Java functionality. It's much better that just hosting the page in Chrome.
Each time Chrome gets updated, the app gets killed. And even though the app has set up an alarm which makes Android call into the app every minute to ensure it is running, for some reason this doesn't bring up the UI (probably something which I need to debug).
But I know that if this app were running on Linux directly, in some Python Qt app with a Qt WebView, it would never get killed, as it has plenty of resources available.
I've also considered integrating Mozilla's rendering engine into the app, but decided not to, I can't remember why, but there were some drawbacks in doing so.
It would be hard to imagine using such an app in an industrial setting, where the app would need to be visible all the time, displaying gauges and stuff like that. The hardware could do that, with a proper OS.
> When these devices reach their EOL as a phone/tablet, they would make wonderful SBCs with integrated touchscreen
Try postmarketos, it's designed to run vanilla Linux on old devices such as phones.
CPU and USB OTG generally works, which already make for a pretty general-purpose machine. The touchscreen also works most of the time. The rest is generally hit-or-miss, depending on how much time you or the maintainer spends on making it work, or if there has been a mainlining effort.
You're probably right but— why buy a Linux phone then? There's LineageOS and F-Droid, or even Replicant if you're all-in on free software and don't mind running on a Galaxy 8.
I'm maybe not the guy to ask, I have curiousity and professional interest in open source phone stuff but I've had an iPhone since the 4, and plan to spend a total of less than 5 hours a year debugging my phone for the foreseeable future.
I'm not sure that pruning apps off my homescreen or rebooting a few times a year to solve some heisenbug really counts as debugging, but it's already closer than I care to be.
I think the issue with LineageOS (and CM before it) is that they're always playing catch-up, both in terms of porting to the latest version of Android, and in terms of supporting new hardware. Want to run Lineage on your brand-new phone? Nope. Want the latest version of Android a few months after it's released? Not gonna be LineageOS. (To be fair, most Android manufacturers take more than a few months to get the latest version of Android out to their users, assuming they do it at all.)
You can say "so what, it still works!" but I think there are weird psychological effects at play when you can make a direct comparison like "Android 37 was released 8 weeks ago but LineageOS is still on 36!" It makes Lineage feel like a second class citizen.
In contrast, if you have a phone that is designed specifically to run a custom non-Android-based OS, there's nothing to directly compare it to. Sure, you can say things like "I wish my FoobarOS phone had Google Pay like Android does", but you still inherently get the fact that they are completely different platforms and won't have app/feature parity.
I used to run CM years ago, but quit even before the LineageOS fork/transition, because I was always looking at the latest-and-greatest Android releases (even for my particular phone hardware) and feeling left behind. And it was even worse when things should have worked but didn't because of some peculiarity of CM, or things like apps refusing to run on rooted phones.
I'm really considering getting a PinePhone just to try it out. I know that I will miss Google Pay and some other things, but I'd be going into it not expecting those to be there, and expecting it to be a different platform with a different experience and different features.
To be honest, this is in your head, and heads vary. I for one don't experience this feeling whatsoever:
>You can say "so what, it still works!" but I think there are weird psychological effects at play when you can make a direct comparison like "Android 37 was released 8 weeks ago but LineageOS is still on 36!" It makes Lineage feel like a second class citizen.
Eight weeks, really? That's a blink of an eye. I didn't even know we're on Android 37, thought it was 9 or something.
Pixel 2+ with GrapheneOS, RattlesnakeOS, or CalyxOS provide pure AOSP experience sans Google and track latest Android releases within days. Depending on your needs you can control your own image build pipelines and still get verifiable boot and automated OTA updates.
Lineage runs on phones that have far superior hardware spec wise to the Pinephone and Librem 5. And I'd wager there's more people working on Lineage than there are working on Librem's and Pine's phone OSes combined.
Because when you rely on the android ecosystem, the rug gets pulled out more and more. LineageOS works on less and less new and common phones and SaftyNet blocks you from more and more features.
Android also comes with a bunch of anti features like an api to block the user from taking screenshots. Its better to completely replace the OS with something Google doesn't control.
> Android also comes with a bunch of anti features like an api to block the user from taking screenshots.
When it came out there's a malware campaign that tries to extract MFA codes from Google Authenticator by taking screenshots, there was a lot of criticism towards Google for not setting the flag that activated that API and made screenshots impossible, and it's a good solution, there's no viable scenario in which you'd want to screenshot your MFA TOTP codes. I admit that i'm sometimes annoyed with it's use in banking apps, but IMHO it's a needed feature for security.
Why do random apps get access to the screenshot feature? Why would there ever be a reason to prevent a screenshot when the user presses the hardware buttons for a screenshot?
Because it's an API for a bunch of reasons ( custom apps for better features, probably taking a video of what you're doing uses the same API), so any app can use it.
Because when my device stops me, the user, from doing something I want, thats an antifeature. In this case I want to take a screenshot, and the device prevents this.
It actually is hard. When I looked in to it the only way to fix the issue was using xposed modules which did not work on my version of android/phone and is a security risk because I now have to load some untrusted module as root so I can get the phone to stop blocking me from what I'm trying to do.
Why? If you look at the list of supported devices there are lots of older models. I'm currently using the latest LineageOS on a Galaxy S4 (8 years old) and it works perfectly.
If you want commercial support have a look at https://esolutions.shop/ (/e/ is based on LineageOS).
I'm not even sure if most users who use Linux computers actually want Linux computers. If they do, why are there so many attempts towards recreating the macOS UI and UX in Linux, such as with Elementary OS? Or back in the '90s/'00s, attempts towards recreating the Windows UI/UX?
Maybe people also do just want general open-source computing, and Linux just happens to be the one that's furthest along, its philosophy and ideology be damned.
Personally, I'm hoping Haiku eventually gets further along to be usable as a Linux alternative, and it's fun to wonder what it would be like as a mobile OS.
> why are there so many attempts towards recreating the macOS UI and UX in Linux
I imagine it's because, when the year of the Linux desktop didn't arrive, developers everywhere decided they could make it happen if only they tried hard enough to put together the perfect UI, and so the kitchen-sink approach proliferated.
> Or back in the '90s/'00s, attempts towards recreating the Windows UI/UX?
I take exception to this one. In fact it was Microsoft with Windows 7 (released in 2007) which copied much of the UI of older Linux desktops like KDE and GNOME versions 1.0 (circa 1997). See:
Linux desktop environments were better back then. XFce is the only tolerable one I can think of, today. Even there, I hate the defaults and preferred it in the XFce3 days when it was just an (improved) CDE clone. Fluxbox or bust!
>I'm not even sure if most users who use Linux computers actually want Linux computers. If they do, why are there so many attempts towards recreating the macOS UI and UX in Linux, such as with Elementary OS?
Why the hell do you think those things are related? I can easily make my OS look macOS, windows, something weird inbetween or some pink vapourwave hell from the 90's or some minimalist tiling WM and that's the beauty of it. That's exactly one of the things I want.
I don't use Linux because of a particular DE with presets that let's me mimic windows. If that was all why wouldn't I just use windows.
> I don't think most people who buy a Linux phone actually want a Linux phone. They want an open-source phone. The Linux philosophy isn't important to them, they essentially want open-source iOS
Seems like the phenomenon of people choosing Linux, only to choose a windows manager that makes the entire thing look like a non-open OS, fits this same line of thinking. At the end of the day, most people don't care about the particulars of Linux, or its ideologies. They just want an open and customizable OS, and if there's a variant that looks like a more widely-used OS, so much as the better.
If there were more open OS's that were as far along as Linux, it would likely be less popular. The important thing is open-source phones or computers, not Linux ones.
The Linux philosophy is important to me in a desktop, but I don't think I'd really care about it on a phone. If it were eventually to be both, then I would, but I never really believed in that goal. If I'm going to use a computer in desktop mode, I'd rather just have a proper desktop, with hardware that is unrestrained by the smaller form factor.
You can use a Librem 5 in this exact way. I do it - it's fast enough to run an IDE and do some programming (as long as the thing you work on compiles in reasonable time), check e-mail, IM and social media, do some light browsing etc. I have GIMP, Inkscape, Audacity and LMMS there, which together with Qt Creator are pretty much all the tools I need for my gamedev work - and now I can do that on my phone attached to a screen, keyboard and mouse. Jamulus, Mumble, mpd, even some lighter games and emulators - it all works, straight from Debian repos. It's pretty fun.
I have even ran a full Plasma Desktop on an external screen this way - and it worked surprisingly well even despite of GPU acceleration not being available there because of a bug.
Linux users want phones with comfortable infrastructure that is hackable, and known, and richly powerful, with a wide base of people generating creative contributions. Linux isn't popular (with the hip crowd) because merely because it's better (though it is), or because it's hackable (though it is) Linux is popular because it's a rich technical ecosystem with robust layers of technology operating together but each modifiable, lovingly adopted by power users, each opting in to trying to improve themselves & their systems.
You can recreate the "ability to make modifications" (although you'll struggle to come to anywhere near the seriously integrated layers of technology Linux environments so robustly build). You can offer "Freedom and transparency" to be able to tinker. But it's the co-participation with other tinkerers, with many venerable but separate & adjustable/hackable layers, that makes Linux so rifely diverse & compelling.
In short, my strong belief is: people want Linux phones. The technical ecosystem is more interesting as a whole than any array of boxes/capabilities one might tick.
I definitely want an open-source phone for all the reasons you mentioned, but I absolutely also want a Linux phone.
I'd love to live in a world where BSD or Minix became The Thing™, but since it didn't I basically live and breath Linux for work and that spills over into my personal usage too. Interoperability between my phone and my laptop is huge. I recently started using KDE Connect (and okay - that doesn't have to be Linux-specific) and being able to seamlessly copy / paste between devices, etc. is a game changer for me.
I agree. I love Android philosophy, but it's getting more and more closed with every year. Just one example: call recording. It was available in the past, in modern Android versions those apps no longer work.
I don't know how representative I am, but I just want something that respects my privacy and doesn't try to monetize my every interaction, while being open enough that I can run what I want on it (apps, not OS). Android fails at the first and iOS fails at the second.
I like in principle that Android is open source (minus all the proprietary junk getting jammed into Play Services). I or someone could verify that it's not sending my data to a sketchy third party, but only to a point. Unless the OS and all apps are completely open source, any closed source component could be secretly betray me. Ironically, though, I trust Apple a lot more to write privacy-respecting code even though it's all proprietary. But on Android I do what I can to mitigate these issues, by running as much tracking- and ad-blocking software as I can (a thing that isn't really possible on iOS, at least not to the same extent). And I do have some apps sideloaded that I'd miss if I had an iPhone. But I still assume that Google is not being a good steward of any data it gleans from my Android usage, and that sucks.
I don't care too much about the ability to make modifications. The hurdle to jump to go from a stock to custom ROM is pretty high nowadays, as I expect most financial apps (and probably some others) to aggressively detect enabled root access and refuse to run. And the process of building your own OS images to make tweaks is not particularly fun, and can be a mess to clean up if you make a mistake. It's critical to me that my phone doesn't have downtime, so I'm less likely to mess around with it.
The problem with the current crop of "Linux phones" is that (while they do respect privacy, don't try to monetize every interaction, and are open enough to run what I want on them) they don't have anywhere near the polish of iOS or Android, and are (understandably) missing key applications that I use daily. So anything I use will have trade offs. For better or worse (probably worse) I've chosen the easier path of Android, at least for now.
Having said that, I do think I want to get a PinePhone, not to use as my primary mobile device, but as something to tinker around with. Maybe it's something that eventually could be a primary device, at least for some situations, but I don't see that as being the case without a lot of work, and a lot of customization that I have to do myself, which I don't really care to do all that much.
I guess? But Linux provides those things. Break it apart, what this is saying is, "you don't want X, you want something that doesn't exist that theoretically provides all of the advantages of X."
Which, sure. I could (and do) use LineageOS right now. It's not as good. I still need to go through the Android app development process, I'm still fighting the system every step of the way. It's still a pain to de-Google things, I still have to deal with an architecture that if fundamentally designed to work best with Google services. I still have to deal with what I see as design flaws in Android itself.
So I don't technically need this to be Linux. I recently bought a smartwatch that runs on an ESP32 chip and is programmed using Arduino code/C++. It's not running Linux, but it fits a lot of my needs and it will communicate well with my Linux computer. And you're right, I didn't have serious qualms about that because of the kernel. In fact, the simpler dev process was what made it attractive.
However, there isn't that kind of thing for phones. If you want an Open Source phone that is easy to modify and develop on, Linux is the option that's pushing in that direction.
> but they don't necessarily want to open a PR against the camera app if they want it to more closely match the polish of iOS.
It's deeper than that: I want the ability to fix my own problems. I don't want to open a pull request, I want software that is understandable enough and an ecosystem that is open enough and broad enough that it is reasonable for me to fix my own problems. I (personally) can do that on Linux, but I can't (currently) do it on Android devices, they're a pain to work with and I hate them.
I am used to Linux on my computers, including the fragmentation of software. Sometimes the fragmentation is an advantage because it means there's a diversity of software that is hyper-specialized rather than one or two solutions that are built to kind-of satisfy "most" people's needs. More than Linux itself, what I am used to is the idea that if something goes wrong or if I want my computer to do something, I can make it happen without asking anybody else's permission, without building a giant project that I need to invest serious time into, that I can pull things apart and build pipelines with Unixy tools.
I want that on my phone. It doesn't have to be Linux, but nothing else is providing it, so it does have to be Linux unless someone else is going to build a better OS. I'm not holding my breath for that.
I bought one because I was hoping to tinker with things, and also I wanted to be able to do things that iOS won't allow. (like have a filesystem)
I had imagined that because KDE was so solid on my desktop that it would be really solid on the phone, but I think the phone is not just fast enough.
I was really happy with my feature phone, but had to give it up because I kept pocket dialing the emergency services. I wish I could find a shell that was as simple.
It allows me to run any linux desktop program, which includes programs that can be run with wine, anbox or even a virtual machine. If it's fast enough i wouldn't need a PC at all.
So I would say that is the long term goal: convergence. Linux has a major advantage over other operating systems in this regard.
Most of those need apps re-signed all the time and can't do push notifications.
iSH almost looks usable and then you try compiling something or cloning a git repo and your iphone will get hotter than a pinephone watching youtube (and whatever you do can be fairly precisely measured in ~15 minute increments because it takes ages.)
I think they mostly just want a cheaper iPhone that they can mostly play with the cosmetics and have free apps. For most, the ability to improve the code is not really a thing.
My home is top to bottom Linux. Linux media server. Linux laptop for work. My wife is on Linux. My parents are on Linux (since i have to support them).
Linux's rough patches on the desktop/laptop is one thing, and for me - easy to deal with.
on a mobile device, the polish matters in usability in big way. Running into a problem on a phone is infinitely more of a PITA than a machine with a sizeable screen and a full keyboard attached, where remote access is easy if necessary.
Exactly. They want a phone that, to the extent possible, is not a surveillance device vacuuming up all their data and sending it to apple and google. Obviously the phone companies and ISPs can still vacuum up data even with a linux phone, but you've got to start somewhere.
I don't want a Linux phone because I don't really need a terminal on my phone, I have other devices for that, and the rest of the Linux ecosystem is built for server/desktop, so I don't need that on my phone either. Canonical made the best attempt at getting Ubuntu there, but it started to impact the desktop users and Canonical has limited resources. Apple is trying to converge iOS and MacOS with their iPad Pro and Apple Silicon, we'll see how that goes in the next decade.
I want to know that the source code on my phone has been peer reviewed. However, this does not always mean backdoors are caught. For example, the NSA injected a potential back door into openSSL. It was caught, but only a small number of people are smart enough to catch something like this. STILL: it was open source. I like that. I would buy a linux phone even if it sucked a little, knowing that I could view the source code.
>Probably an unpopular opinion, but I don't think most people who buy a Linux phone actually want a Linux phone. They want an open-source phone.
That's true, but to some degree. I'm OK with LineageOS, wouldn't care if that has Linux or BSD. As long as I can switch distro, reinstall and do not lose warranty or permanently damage bootloader.
> but I don't think most people who buy a Linux phone actually want a Linux phone. They want an open-source phone.
Would be very strange that in the vast group of Linux users you can make a claim that "most of them want X". Seeing the amount of fragmentation happening out there, a lot of them have different priorities.
I have a phone, I don't use it for too many purposes, whatever software that is installed on it doesn't bother me much because there are larger pie to fry.
Now desktop OS and laptop choices/ cloud native stuff is a hill I'm willing to die on, because I'm a lot more invested.
Laptops and desktops are being replaced by phones. The appeal of a FOSS phone is that it makes the world safe for general purpose computing by taking back some of the territory lost to phones.