I've actually been using HarmonyOS for half a year now, and it feels pretty good — the notifications and system smoothness are on par with iOS. The reason I don't use an iPhone is that I need NFC access control, which iOS doesn't support.
Huawei has invested a large amount of manpower to station people in major companies to help develop HarmonyOS. I think they have already broken the vicious cycle of "no users -> no apps -> even fewer users."
Moreover, in the current AI era, it has become easier for Chinese developers to port software to HarmonyOS. For example, Moonlight, the streaming software I often use, has several natively customized and optimized versions available in the HarmonyOS app store.
“From 2019 to 2024, versions 1 to 4.3 (4.5 TV) of the operating system were built by integrating the Android Open Source Project (AOSP) with OpenHarmony, allowing it to support both HarmonyOS and Android apps. The current iteration of HarmonyOS became known as HarmonyOS NEXT (later it was renamed HarmonyOS 5 in launched of Pura X). HarmonyOS NEXT was announced on August 4, 2023, and officially launched on October 22, 2024. It also replaced the OpenHarmony multi-kernel system with its own HongMeng Kernel at its core and removed all Android code. Since version 5, HarmonyOS only supports apps in its native "App" format.
HarmonyOS 5.x+ both discards the common Unix-like Linux kernel and replaces the previous multiple-kernel, kernel agnostic system from OpenHarmony with its own bespoke HarmonyOS microkernel as a single framework.”
⇒ this shows it’s possible to create a new stack. It’s not Linux, though, and I think a large reason for this succeeding is that it started in the Chinese market after the US sanctioned Huawei.
Even so, I think it's helpful in that it weakens the duopoly. If app builders are getting used to building apps for other platforms than Android/iOS, it hopefully also becomes easier for others to gain some foothold.
Especially given the heavy commissions and other developer-hostile behaviour of these two. They've been essentially treating devs like shit and IMO a reckoning has been coming for a while now. Of course, you do have to meet the users where they are, at least up to a point.
I can't tell you whether this is a good idea, but I am sure this will never happen outside China, which is supposedly what the question is about.
Also bear in mind that Huawei is likely worth more than a trillion dollars. There aren't many companies at that scale.
[0] https://www.sz.gov.cn/en_szgov/news/latest/content/post_1117...
I assume it requires some mind of Android compatibility layer that won't pass Play Integrity checks..
However, as I understood, in China HarmonyOS next has no Anroid-emulation layer (which is probably a wise decision if you want to drive domestic app-developers to support your platform...)
In my daily use, only three apps run in the virtual machine: 1Password, Steam, and Chrome. They all run normally, but they're a bit laggy.
The 16:10 screen makes it very convenient for watching videos and reading e-books.
The chip is the Kirin 9020. Although it's only equivalent to Android flagship chips from a few years ago, it doesn't feel laggy in daily use.
This is what genuine competition is and drives things forward.
I just looked it and while it looks different, that's not bad. As long as it works, I'm fine with what I have.
...and in my comment, I kindly disagreed with you. I have used many things with great enjoyment which were called ugly by many people.
It's OK and natural to have different opinions and priorities, and hardware design is not a first priority as long as it's uncomfortable on my checklist.
As a side note, apparently, you can add an extra camera module with a 1" sensor to that "lock" you seem to dislike. Considering the best camera is the one you have, having an additional camera with better sensor for people who are inclined to dabble into photography is a great thing.
...and I'm contemplating on how can I take my mirrorless with me during flights in a compact way even if I have an iPhone.
if you can't run all your favorite bank apps in your phone any phone is dead nowadays, no matter whether it is Linux or HarmonyOS
and seems EU is fine with keeping Apple/Google duopoly in app verification, so although you can use European bank and pay with QR codes without MC/Visa, you still need US company verifying your phone so you can use European bank app, sad state of current things
I appreciate your intended point was probably more specific, perhaps 'will not be a mass market success in the west', but there is a great diversity of people in the world and many of them have different requirements of a phone
gojek too
singapore also has some pretty great ideas
go travel a bit, there's an entire world out there that isn't waiting around
when i go to the mall here, i counted 6 korean copycat shops lol
asia is living a completely different lifestyle than us, and its popular even with us, especially with women, and its actually good, and we're still here saying asian shit is irrelevant
And millions of Chinese bash it everyday. Shit storage efficiency, stagnated UX experience, very closed ecosystem and external link blocking, I could go on.
hey apple, when are we getting expanded memory, maybe better battery? oh we're still stuck under 4000mAh, cool cool cool
Same with Gojek. They tried launching in other countries, but it never caught on outside of Indonesia, where yes it's huge and awesome.
Grab, on the other hand, has been very successful internationally.
> asia is living a completely different lifestyle than us, and its popular even with us, especially with women, and its actually good, and we're still here saying asian shit is irrelevant
I lived in China 5+ years and spent plenty of time in other Asian countries travelling, so how to say it politely - stop talking about "us" and preaching me about lifestyle in Asia if you are completely clueless.
WeChat is shit app pushed down the Chinese throats (I remember when QQ was still the king), because it doesn't have competition in China and you can't really exist in China without it, closed sourced with no E2E encryption for starters, there is reason why pretty much nobody outside China/Chinese community uses this actively spying app.
So yes, if by Asian shit, you mean HarmonyOS and WeChat, then yes, Asian shit is irrelevant, because pretty much nobody outside Asia uses it for good reasons (HarmonyOS because it is unusable if you wanna use normal banking apps and most of the other apps relying on GMS besides those very very few ported apps or using some virtual machine workarounds, personally I don't need banking apps and used smartphones without gapps for the last 10 years, but I am realist realizing I may be among like <0.5% Android users in Europe, completely irelevant negligible number).
In fact, it is a competitor against both iOS, Android and Linux-based devices.
- Worse compatibility with the millions of Android apps already out there.
- Hardware vendors (outside Apple) all target Android.
- The usability of Android/iOS is far better than non-Android Linux phones.
- The security of non-Android Linux phones is in a bad state (e.g. lacking proper app sandboxing). Heck, even the Android emulation layers that some of these phones have, throw the strong Android sandbox model out of the window.
The answer is very obvious and it is AOSP. Even though Google is trying to close AOSP more (e.g. by not pushing source continuously to the AOSP Git repos and keeping QPR1/3 for themselves), it is still an open source system. Play Services can either be run sandboxed or emulated with microG. AOSP allows alternative systems to hit the ground running, you get great app compatibility, a tested security model, great usability, and support from hardware vendors, including vendors that are alternative friendly (used to be Pixel, now Motorola, Fairphone, etc.). If ever needed, AOSP could be forked and it would still be leagues ahead of non-Android Linux phones.
All the downsides that apply to AOSP-based systems (like things getting blocked by Play Integrity, unlockable bootloaders) also apply to non-Android Linux systems.
Once we can actually target the hardware, open source alternatives will be much better than first party options.
You can already see the potential in the open source world.
Linux has Waydroid so Android apps can be run on Linux at full speed without emulation. That means, if you had a Linux phone, you have the entire Android library - the only thing lacking is the launcher. How hard is a launcher to program? It's just Steam's big picture mode.
Other examples of the nice things we can't have; FEX lets you run Steam games on phone hardware. Open source drivers can unlock displayport over USBC. Instantly your phone becomes a thin client / laptop replacement that can play PC games (poorly, but 1080p games are possible).
We are _not allowed_ to do these things. I love OS development and, if I was allowed, I'd make iOS look like janky trash.
The problem is not only hardware support, the problem is also that the stack on top of it is very immature compared to AOSP and not something you could give to a daily phone user.
It’s funny that you mention Waydroid. It throws most of Android’s strong security model out of the window.
It still has tiny market reach. Very few people are going to invest the time needed to build a quality user experience for like 1000 users.
Just imagine what would happen if Linux could be installed on the iPhone. There would be SteamOS distributions within an hour of the announcement.
> It’s funny that you mention Waydroid. It throws most of Android’s strong security model out of the window.
Haha yea, it's more an example of capabilities that could be rolled into highly polished user experiences. Again, if Linux could be installed on the iPhone - I'm certain Waydroid maintainers would shut the project down from PRs.
~~* competition *~~
You are moving the goalposts, you said:
The lack of polish is a function of the inability to use the hardware. The hardware is tightly gatekept so competition _cannot_ exist. [...] Once we can actually target the hardware, open source alternatives will be much better than first party options.
So, it's not the hardware gatekeeping that is the issue, it's that nobody is polishing the experience for hardware that already exists and qualifies. The hardware can also be purchased very easily in some regions (e.g. Europe). I can literally hop on a bike right now and pick up a Fairphone in ten minutes. I know that it's different in e.g. the US, but Murena has been selling them in the US for years now.
If Fairphone wanted, I'm relatively sure that they could form a cooperation with Jolla, Librem, KDE or other entities in the space and get Plasma Mobile, Sailfish or whatever working on their phones and/or design the next-gen Fairphone with hardware that has as few quirks as possible and is as "easy" to get to work with Linux as possible. I'm also relatively sure that so far, that would not have made economic sense for them. However, there seems to be a bit of a surge in people wanting alternatives. The recent Jolla phone has way more orders and pre-orders than were anticipated, for example. And SailfishOS is certainly "polished" enough that the circle of people who can use it well (or at least live with it) has expanded beyond the developer / hacker / activist crowd.
Now, if we had support for say, a pixel, that would probably change things. Incidentally, there seems to be initial support for the tensor G5 (pixel 10 onwards)
The most effective path would be for the FLOSS ecosystem to pour their resources into making AOSP independent from Google. But instead people will just fork N half- or non-working solutions for reasons.
But you have no guarantee what happens tomorrow with it, depending on what Google feels like. You just have to eat whatever Google decides.
With Linux there's no such centralized control. So the time and effort will pay out later on down the road. Let Google have its AOSP.
Given that Android apps target old API levels, it would also stay compatible for years and nothing would hold you from implementing APIs from the docs.
To be honest, I don't think AOSP will fully close up, since Google probably fears the regulatory pressure and the fallout from vendors. The larger risk is Play Integrity, but that applies equally to other Linux systems if you want to tap into the large Android app ecosystem. But the solution for that is not technical, the EU and other regulatory bodies should make forbid it in its current form due to anti-competitiveness.
Hacking on the Linux stack is several orders of magnitude more practical than AOSP though. AOSP's build system is massively unwieldy for individual contributors to work on. You can't easily work on any of the system components without dedicating >100 GiB of storage for a build, for example. Everything is scattered across hundreds of repositories tied together with a bespoke repository management tool.
This all works for a company equipped with entire build infrastructure teams, not for a grassroots project trying to keep up maintenance with (at best) limited funding. It's why Nura (fka postmarketOS) is a thing whereas the various AOSP forks barely ever modify the core experience.
Since then the problem has always been the same, rebooting the DE experience for the sake of it, desktop environment wars, rebooting the development stack from GNOME and KDE, and the problem that despite all OEMs have Linux running on their data centers, the community has to reverse engineer the hardware from the same OEMs.
But yeah, then there was the constant forking, preferring rebooting development over iterative improvement (e.g. GNOME 2 -> 3 was really a hard cut for a lot of people, resulting in forks that exist till this day), hostility towards closed-source applications (you can hate them as much as you want, but people are not abandoning Photoshop/Illustrator for GIMP/Inkscape on a whim), etc.
Hopefully something changes with all the government-driven sovereignty desktops that are popping up, the resulting influx of money, and KDE EV et al. becoming very mature organizations.
If I would draft policy that could make it I'd suggest;
- Scoped to companies above a "number of units sold globally" threshold.
- Documentation must be supplied 3, maybe 5 years after hardware release (similar to "generic drugs").
This means small hardware startups are not burdened by the overhead in creating docs, and megacorps retain the ability to extract profit during the period of maximum profitability for the product. The eventual expiry would encourage companies to innovate (I think malicious compliance is unlikely).
With the recent push to decouple dependance on US technology companies, I see this as possible (though still unlikely) in the EU, perhaps Canada.
Yes it won't be pure religious FOSS with 100% open, so what.
Also this is the future for laptops as well, for those that keep repeating the mantra of ARM/RISC-V replacing x86/x64 architectures.
Apple doesn't sell Linux powered devices, nor do I want that from them.
This perspective I can't wrap my head around. Like I get that you wouldn't use it, and that's fine - but if Linux was available and we made it incredible, that would push Apple (and Google) to do better. So you'd get a better MacOS / iOS by proxy.
Like, don't we want competition? What motivates people to desire an unchallenged status quo?
I've been thinking about it for a long time, but it seems like such a privacy risk even when self-hosted. The massive upside is that the phone is just a VM. The idea makes the entire phone debate irrelevant since you can access your "phone" from any other computer that has internet access. If the connection is lost, the local device can always sync later or at least provide basic call/text functionality.
Must be why Desktop Linux has great usability right? Oh wait
It's better than Windows 11 at least - though we probably can't credit that to improvements to the Linux DE
The usual suspects are the keyboard support in Windows (enabling the extended keyboard navigation in MacOS made some apps act very strangely), and most of the look and feel of MacOS. There have even been things I really liked in ChromeOS.
Obviously there are many nice touches in the big Linux DEs, and I would rather be in KDE Plasma than anywhere else. Because of this, I'm generally not surprised when I encounter something that is done better than Windows or MacOS.
However...!
Yesterday I was editing filenames in the file browser, and accidentally navigated down to the next file in the folder - still in filename editing mode! It was a feature I didn't even know I wanted. Suddenly, I could edit a whole list of files, just as if it were rows in a text file. Now it's Monday, and I'm back in Windows. I am unlikely to need to use that feature, but still wish I didn't know what I was missing.
In case you do ever need it - you can do this in Windows with the tab key.
Anyone have the equivalent for MacOS? :) I don't have any MacOS devices handy.
Play Services is absolutely not needed for a usable Android experience. I am running GrapheneOS without any Google crap and you could not pay me to do so.
I also run LineageOS with no Play Services (and have for years), but it is missing some pretty noteworthy stuff: Google Maps, Google Pay, etc.
Like IP address and location?
Most of the apps on Android and iOS aren't necessarily useful.
I agree and thus donate to independent AOSP development (such as GrapheneOS).
It would probably be a great idea to replace many android components with components from the linux userspace ecosystem so that more code sharing between desktop linux distros and this is possible
I disagree. Working on AOSP with Google having so much control of it is just a waste of time. You have no guarantees what you are working for, in the future.
I'd go full Linux, the effort is worth it and will pay out in the future. Google has the AOSP project by the balls and it's a very high risk investing anything into it, as a developer.
With today's LLM tech might as well do something nice with Linux.
But no, let's reinvent the wheel and start the complete ecosystem from scratch. Of course, looking at the history of Linux, this is not surprising at all. Even something immature as mobile Linux already has multiple projects + stacks (Sailfish, ubports, Plasma Mobile, PureOS, etc.) trying to achieve the same. I say this as a long time Linux user (since 1994), the Linux desktop community manages to shoot itself in the foot over and over again.
I really enjoy having a phone that gives me full root control, and that is very similar to the Fedora (GNOME) distribution that I have on my desktop and laptop.
Buying a Linux phone from a pure Linux hardware vendor like Purism helps sustaining the mobile Linux ecosystem.
Yes, the Librem 5 is a bit older phone with some rough edges, but for me it is a really good phone. It gives freedom in the free software sense, and consistency with my Linux computers. I gladly accept some minor inconvenience to have a phone that respects my freedom and privacy.
I cannot foresee the future, but for me the experience on a Linux phone that I control is far more superior than any phone that spies on me and takes away my freedom, like Android or iOS, basically any phone from any manufacturer that disrespects me.
Drivers and firmware are the biggest hurdle outside of locked bootloaders for competition in the operating system space.
Examples; Anything Apple (MacBook, iPhone), anything Samsung, anything Google, the list goes on.
There _is_ open hardware, but it has poor performance / battery / build quality and the vast majority of users will not accept that.
IMO "the right to repair software" is essential and this duopoly is a function of explicit monopolistic practices.
Maybe LLMs can help open the "reverse engineering" Pandora's box - but we have yet to see that realised - at least for drivers / firmware
I'd be fine with that model - let them make money for 5 years recouping their R&D costs, then they must offer documentation so the community can repair / maintain the hardware themselves.
I personally see it as falling under "the right to repair" and selfishly, I know we can do more with the hardware than they are demonstrating. It's endlessly frustrating that we are not allowed to and then the devices just disappear forever.
In the US, all patents have 20 year terms (from initial patent filing). Of course, patents don’t tell you how to make something, so it’s not sufficient for something like smartphones or medicine.
- We'll probably want the security model, with the nice sandboxing and I would argue the verified boot.
- We'll want the battery optimisation.
- We'll want access to the firmwares of the components running in the phone.
- ...
From the very first step "start from Linux-the-kernel", every single question I ask myself goes towards the Android design and away from the classical Linux distro design.
In other words, the open source Linux distribution that is the closest to a modern mobile system is... Android :-).
Like they created UNIX, they declared it done, created Plan 9, followed by Inferno, most as a reaction to JavaOS, but still, the creators of UNIX moved on.
Whereas the FOSS community seems to be stuck in recreating Bell Labs in the 1970's.
A lot of people from the FOSS community seem to believe that (at least from recurring discussions) that Linux is secure because the software is open source and you can trust the maintainers. The idea that even trusted software can have vulnerabilities and that the 80s/90s security model of the standard Linux desktop means that you are only one Mastodon/e-mail/RSS/whatever client vulnerability away from exfiltration of your whole home directory does not even occur to them. All the while all these applications use (XML/image/...) parsers from the 90/00s written in C.
The only reason we don't see mass-exfiltration of data is because the Linux desktop marketshare is effectively meaningless. Though we see some results of the desktop security disaster (also to some extend of macOS) through leaked credentials obtained by compromised NPM, PyPI, etc. packages.
Or that isn't the case and this is all just a silly comparison.
And its not a case of simply implementing some feature, since all apps have to written with this stuff in mind: apps can be suspended/killed at any time and should be able to restart gracefully, notifications go through a side channel, etc etc
Do these phones have any of this?
Other times I'm sure I've hit 60-70.
Because of iOS's app management feature, most of the apps are actually dead, but if I go back and open any of them, they will open and load on the screen on which I left them.
Android does this too.
Desktop Linux cannot.
Can I open 60-70 or even 35 Electron apps simultaneously on 8GB of RAM on Linux?
And no, I do not want to to back to closing apps, that is simply an inferior experience.
What is difficult is e.g. supporting the undocumented photo/video camera and other essential parts of the hardware that lack documentation.
You need a stack that is designed from first principles for phones. Luckily we have one that is open source (AOSP).
Spoiler: I have :-)
It is sometimes annoying to me. I cycle a lot and sometimes my wife or somebody else sends a message when I'm on the go (like picking up some extra groceries) and then I miss it.
I have had several generations of ThinkPads and to this day, battery life is typically ~50-60% of that of Windows, even with all battery optimizations applied. And Windows is terrible compared to Mac or Android/iOS phones.
And I say this as a long-time Linux user (used Linux in some form since 1994). It's just a very hard nut to crack if you miss a certain amount of vertical of integration and coordination across the ecosystem.
Look at Asahi. Almost a decade in and we can use the GPU at like 30% of its ability on 6 year old hardware.
That a project with major interest. No one cares about spending a decade reverse engineering the hardware on a Google Pixel or Samsung Galaxy.
If they gave us proper full hardware documentation, we could create high quality alternatives. Again, we can't so you don't see it.
Competition is good. We should always advocate for things that enable competition.
I'm not sure this is true anymore and it is becoming less true with each new LLM release.
> No one cares about spending a decade reverse engineering the hardware on a Google Pixel or Samsung Galaxy.
Actually, this might a cool idea - just get a few super cheap smartphones, connect them all to a PC, give LLM access and tell it "make linux gud like android pls" and just give it a weekend.
You may see that the driver writes some hundreds of magic constants in some hardware registers, but you do not know what they mean. You may be able to do exactly what the binary driver, does, but you will not be able to improve it, e.g. to enable features that happen to be not enabled in that driver.
So a LLM can speed up the initial part of reverse engineering if you have the files with binary drivers, which may be difficult to extract from certain phones, but a lot of work remains to discover all that the hardware can do.
I see three aspects there.
The first is that google is currently rugpulling via various means and _really_ playing those anticompetetiveness-cards. That wasn't the case previously. So there wasn't much motivation to care, because android was "open enough".
The second is that the world is getting less geopolitically stable. So the whole ecosystem lockdowns are not just a personal preference thing but might be actually vital.
The third is that LLMs are kinda good at these optimization loops if you hand them a framework in which they can sample good data.
I also had a fourth thought but it left my mind :(
LLM-driven optimization is a good point. However, Linux desktop communities tend to be quite aggressively anti-LLM. E.g. GrapheneOS has been heavily attacked by these people for only using an LLM for security auditing. But maybe these projects will fork into LLM-accepted forks who will then rapidly out-innovate.
This one of the most understated reasons.
There is simply not enough rich app activity information for the session manager to do smart management.
Compare it to what iOS and Android apps report about themseleves and the conditions they are forced to run in (such as being arbitrarily killed and restarted).
Obviously the Linux kernel is perfectly able to sit in a stack like this (see: Android), it's the XDG standards which are not well suited for this.
Of course it's more complicated than that, but it's not impossible, since the foundation is already there.
There's nothing inherently special about their optimisations, but hardware is incredibly complex and without documentation, open source drivers cannot be written that are anywhere close to what engineers with hardware docs can build.
Asahi Linux is a great example. It's an unbelievable project but still far from first party Apple drivers.
Once the hardware can actually be used, competition in the OS space will follow.
They have no incentive to offer documentation and competition is bad - so they won't allow that. Regulators must step in here.
In other words, the 'app culture', and the attendant normalisation of data stealing, must end. This effectively takes "app-" and platform-dependency out of the picture. Services are no more burdened with supporting n number of platforms; nor do they have an incentive to push people to start using their apps. Services can still offer an app, and users still have a choice to use one. But, the baseline client should be a browser. And there shouldn't be any discrimination between mobile vs. desktop browsers, either.
So a new phone means just moving the VM. The only unique thing my Android layer has to do is route the internet..
Every player in this space currently has this incentive imho.
While everyone that was doing vertical integration in the last century, had the whole product to sell, the OEMs selling IBM PC clones were all alike, so they always had something to differentiate, being the shovelware that was offered alongside the PC, pre-installed, painted cases, whatever.
The software side (Phosh, KDE, etc) is now improving fast (both IMO because the obscure frameworks they're written in are easier to contribute to with AI, but also just thanks to time and maturity).
And if the firmware/hardware side can graduate the treadmill of endless bring-up and instead work on performance and fun stuff, that would be fantastic. We need our Raspberry Pi moment. First the Librem and Pinephone were our hope, then the OnePlus 6, but they all stayed 80% usable. Currently it was the Fairphone, but now tbd which the savior device will be. Exciting!
edit: The hardware supply chain is an issue, though. It's all Android hardware under the hood because that's the only thing you can buy. So there are crutches necessary to translate between Android drivers with their hardware abstraction layer and "proper" Linux. Libhybris does that in case of Sailfish OS / Jolla (the company behind the OS) and it works well but I wouldn't call it elegant, necessarily.
Demand simply is too low. FTA: (https://amosbbatto.wordpress.com/2026/10/05/linux-phones-alt...):
“Jolla has sold 15,000 units of its phone as of August 2026 just by taking pre-orders for production batches from its web site”
In comparison, Apple easily sells 15,000 phones each hour of the year.
So, the best hope for such a Linux phone would be to have something installable on hardware of a third party that normally ships Android. I don’t see that happen because such hardware gets locked down more and more to defend against cybercrime.
Also you need to build an ecosystem so that users and developers can get involved & open hardware fully supported by Sailfish OS is a good start.
Also a lot of mainstream mobile hardware is locked down on purpose to effectively enforce planned obsolescence, which makes it harder to port a sane OS on it.
Maybe i should aim for a second smallest possible android phone just for banking to set my mobile computing free. (İ was already tried using unihertz jelly star as my daily driver for a while)
No they want, unless they cater to normies, instead of trying to be X Windows and UNIX CLI on a tiny phone.
And for better or worse, actually make deals with OEMs, instead of trying to reverse engineer them, phones aren't like IBM PC compatibles.
The average phone user couldn't give a damn about the underlying OS - they buy on price and features - not the "hackability", or whatever drives the good readers of Hacker news to buy phones.
so if that's been the case on desktop, smartphones are just so far out of the picture. i dont see how the year of the linux smartphone could ever come before the year of the linux desktop.
I really hope I'm wrong. thanks for reading my meh-ly informed 2¢.
My non-technical relatives run Debian just fine. I don't understand what you are talking about. It has unattendend upgrades and doesn't have to be configured or tinkered with after install.
I started to list my few, basic must-haves - aware that everyone has a different list - but my own short list got embarrassingly long, very quickly. I thought I had simple requirements!
Obvious basics which surely aren't too much to ask: email, calendar, reminder and note syncing, password manager with TOTP generator, instant messaging (willingly to compromise and have only Signal or WhatsApp), route navigation, basic browsing, half-decent camera, ...
Phone calls - so I probably need 4G and 5G...
Oh - plus uncountable other small apps or utilities that hardly seem worth mentioning: calculator, file browser, compass, voice memos, ...
And then I thought about the ever-growing list of big, ugly Apps that I could live without, but really do make my life easier. Banking apps (sigh - I hate how many of these virtually require an app), the app to unlock my apartment block door, Outlook, Teams, ...
And then I started having sensible, disappointing thoughts. Maybe I'd rather just keep the iPhone 13 Mini. I just got a new battery (and bonus screen) installed by Apple on the weekend...
But seriously, when that starts to be unusable... if I have to carry something obnoxiously large, it better run mainstream Linux and turn into a desktop when I plug a USB-C dock into it!
Sure all the conventional mobile ecosystem stuff wont work. But that's entirely a giant ball of cancer anyway. Only a fool would want to deal with that filth.
Quite interesting for us OS nerds, less so for those that only care about UNIX on their phone.
Android is Linux.
I sure wish the Zii Egg had made it out of prototype stages. It showed the most promise - a bare-metal Linux OS, multiple cores, very, very easy to write apps for it - just plain C/C++ really.
Linux phones never happened because the distro's constructed for them were overly complicated, unnecessarily encumbered with 'smart features', and just generally (imho), sabotaged by the cult of collective development. Its the sort of project that requires a BDFL pushing things forward - none of the failed Linux phones ever had that.
These days, I'd rather see someone produce an ESP32 phone with LoRA and maybe SDR, and leave it at that.
But, there is another issue. The modems. It is always the modems. Until someone courageously open sources the modem chip and its firmware, there is no hope.
you can stop using US Visa/MC cards, but it's kinda pointless if you EU bank app still requires verification from US Google/Apple for app to run
I wish European govs would stop requiring Google Play services in Android phone and provided their own solution
that's like saying I have new solution to wheel, which will be called European circle, it will be the same wheel we already have, but under the new fancy EU name!