The Plasma Mobile team is happy to announce the developments in the project over the past few months!
Housekeeping This blog post was completed much later than originally planned. In the meantime, several releases have taken place:
This blog post is already quite long, so it will omit changes merged for Plasma 6.5 (releasing in October, to be announced in a future post).
With the Plasma 6.2 release, we moved Plasma Dialer and Spacebar to the Plasma release cycle, allowing us to have consistent releases of the two apps. This completes our year long move to having all Plasma Mobile related projects released as part of wider KDE releases, streamlining the work for distributions and taking a load off us on having to maintain a separate release cycle!
In other news, a Fedora spin for Plasma Mobile was released! It will only be targeting devices that can currently boot Fedora (i.e. not ARM phones), but is very exciting nonetheless!
The way that I see, Linux phones will only get traction when we are able to install android apps and use high end spec phones with good security. I hope that I'm wrong.
Liberux NEXX is supposed to be a thing but they sorely need backers. It costs about the same as an equivalent Android phone (pixel 9 pro 1tb costs $1,500, liberux nexx 1tb costs $1,300).
8 core/32gb RAM/1TB storage phone in a very sleek body, Linux phones could have their flagship soon (and unlike pinephone it sounds like Liberux is gonna do the actual work on developing the software).
I've noticed that my Poco F1 with 1/3 more battery but a good enough CPU runs around 3 times as long as my OnePlus 9, both running LineageOS 22 and same usage.
Maybe we are way past the curve where more processing power means shorter processing times/more energy savings vs. going full power for every little bit.
In summary, why would you still pay over $400 for a phone nowadays, if all you get is a better camera (which still don't make noticeably better photos) and less battery time?
While I love the idea, I just don't see this moving forward unless any of these projects can focus on splitting up these types of projects into a solid base, driver layer, and then UI layer. Instead they are all spending a ton of engineering resources building something from scratch.
So many projects have similarly started the same way and failed instead of working towards a base that replaces AOSP first, then spinning their own UI on top. The big device manufacturers figured out a decade ago this is the right way to go, and these small projects buck that and fail instead of just focusing on the thing they ultimately intend to focus on.
Get a good base that is removed from Google, THEN do this project.
The split is already there, the problem is that most Android phone manufacturers never publish the drivers (let alone make them open-source) and the only way to get anything but stock image running is to just rip parts out of the stock image, which significantly limits what you can put below it (i.e. Linux version) and on top of it (i.e Android Java gubbins). And you can't "just replace AOSP", as it's a huge complicated thing (kind of by design) which allows vendors to tightly couple the drivers to the system image. The idea of all these "mobile Linux-es" is to get rid of AOSP entirely, replacing it with "desktop Linux userspace" (systemd, musl, D-BUS, NetworkManager, pipewire, upower, mpris, libnotify, Qt/GTK, Plasma/Gnome, etc etc etc). A DE is an integral part of this; you can't build and run Nova launcher just with Wayland and Pipewire but without Dalvik and Android SDK/NDK, and remaking all of that from scratch would be an insanely hard undertaking.
To put it another way,
Get a good base that is removed from Google, THEN do this project.
This project is required if you want to make a "good base", otherwise that "good base" would just be an empty TTY that you can't interact with because there's no on-screen keyboard; besides, that "base" is already there and has been for 20 years, what's missing is the drivers.
The base for Android is also Linux. But there is another layer. That is AOSP, which is comparable to your distro, then there's another layer of your UI (ie: MIUI, One UI, Nothing UI, Pixel UI, etc) which is comparable to your DE on Linux.
That second layer is what they're referring to. Currently everyone is just playing with the third layer (the DE), to my knowledge.
Sort of. Whatever hardware these are intended to run on require something like 3X the driver code (at least in the case of the Android Linux kernel, according to Greg Kroah-Hartman). Phones tend to have more specialized and proprietary hardware, so you can't just take the standard Linux kernel, use it there, and call it a day.
But I'd be surprised if the people working on this weren't aware of that fact, and I hope they are working on abstracting the hardware layers more so that every mobile Linux project doesn't have to start from scratch every time.
Edit: source (YouTube, sorry) for the claim about how much driver code is required for mobile devices.
Last time i tried plasma mobile it was unbearably slow (even slower then the normal unbearably slow) so i switched to phosh, but I would like to try it again so let's see if these updates made it any more usable.
UPDATE: Honestly i'm impressed, it might be because currently im not running waydroid beside it like i did on my previous Phosh install but it feels very responsive. With the angelfish browser providing a way better experience then firefox. The battery life is still very bad but outside that this could be used as a regular phone.
I REALLY want to try PlaMo, but I wish I could use Mobile Linux on my phone. I can't, but oh if I could, or if I could run PlaMo on Android, it would've been great. I once even "riced" my phone to look like Plasma Mobile.
FWIW some of the Plasma Mobile apps are available as Android apps, but I my experience most of them are not really stable enough for daily usage.
If you are looking to run the whole Plasma Mobile stack, you could use Termux and proot to run it "natively", although I imagine it would likely be a huge pain to get anything working reliabilly, if at all.
You'd need an operating system that uses it. It's going to be at least as difficult as flashing a custom rom, but likely even more so, as there might not be a ready-made build. Definitely something to experiment with on a secondary phone. PostmarketOS is your best bet, here are others that support Plasma Mobile.