Not that it would really succeed otherwise. You need Android app compatibility to stand a remote chance.
Like the particular programs are no issue, but the whole UNIX-userspace as done in the mainframe era and still is. Like you definitely need cooperative program suspend/resume like on Android for any kind of sane battery life, but that's unfortunately completely missing in case of GNU/Linux.
I was looking at this and thinking maybe it would improve a cheap android phone. But now I know it's running gnome I won't even consider trying
Without any different numbers, I think saying a massive memory hog is a little hyperbolic. Applications in use, especially browsers, are going to dwarf the desktop environment anyway. Having the polish is well worth it to many people, myself included.
I would definitely like to see less memory requirements for the various desktop environments, but at the end of the day I don't pay for any of this
Gnome is a bloated mess of a thing and I hate it. Why would anyone want their desktop to use over 1gb of ram. I have a 32gb laptop and I still loath the idea of throwing away memory on such a bloated awful thing.
Running gnome on a phone. Yeah... No
> Seems like a very strange bundle to bring in for an extremely power constrained device, where every % of increased battery drain is noticed by the user
I'm sure you can make your Frankenstein version that would be 10% as usable and secure as phosh by removing everything but for most users, 100mb more ram and 1% more battery drain for an OS aiming to be a daily driver is something that's worth it.
App support and camera quality I can understand more. I'm on a Linux phone using Phosh (FLX1s), and there's Android app compatibility, but it is a little rough (and of course things that rely on Play Integrity won't work). I've managed to avoid tying myself to anything that requires Google for now, but I acknowledge that I'm lucky there.
IMO it's not a matter of tap to pay and camera quality, rather a matter of whole system paradigm. Having millions of disconnected services in the "do one thing and do it right" spirit and using text based communication and hundreds of python and shell scripts is relatively maintainable and relatively easy to use, but very inefficient when it comes to CPU cycles - and on a handheld every cycle counts.
And of course every app is optimized for desktops/laptops... but I guess that's a chicken-or-egg problem: once there is a working distro, there will be apps too. And once there will be apps to use, there will be a working distro. Maybe.
That's not phosh's problem; waydroid is a pretty much independent component.
It uses some GNOME services, namely so it doesn't have to invent it's own. None of these services are memory heavy and all have a purpose (e.g. managing Bluetooth)
Not in a million worlds. Android is by far the most optimized OS (as a whole, including user space, graphics stack everything) for mobile devices. It's almost like the most widely used mobile operating system has had quite a bit of dev hours spent on it.
Additionally, minimum requirements of Android 17 are way above what SXMO allows.
With Phosh you would have a point but SXMO is lighter than a modern Android.
As it is I didn’t find it at all difficult to find the answers to your questions by going to the “about page”.
> About Phosh
> The Phosh project aims to provide a daily-usable, robust and easy to use graphical user environment for mobile devices running mainline Linux. The name is a portmanteau of phone and shell as phosh was one of the first components developed by the project. It hence coined the whole project’s name and is still one of its core components. All of Phosh is entirely Free Software.
If I read correctly, you identified the lack of smarthpone-level apps and distro as the limiting factor. In my opinion, the lack of sufficiently powerful but still open hardware is what we miss. Mainline linux with proper hardware support is pretty good but not complete on the Snapdragon 845, a 9 y/o platform. Anything newer? Nearly impossible without some android-specific layers (such as libhybris in the case of Droidian). Currently mid-high level hardware with PinePhone-like openness would probably let Phosh (and Plasma-Mobile, SXMO etc.) distros strive. The smart features, as in the apps, are mostly there.
It can be a lifestyle difference.
I personally don't being my wallet in most daily trips, have no use of it. I used to stick a credit card in my phone case but also got rid of it as more stores reliably offered wireless and QR code payments.
Mind you this comes with a specific environment I don't expect everyone to live in or long for, I'm just explaining.
Add a bunch of fat, semi-desktop binaries that actually provide some kind of functionality to make it remotely comparable, and then you just have a worse, fatter system that runs hot and wastes the battery.
Android is a unified system working together to make the device race to sleep as fast as possible, with as few wakeups as feasible (e.g. batch together events that would wake up the device).
In terms of resources I think it's roughly going like this, from lighter to heavier:
SXMO < Lomiri (Ubuntu Touch) < Plasma mobile < Android < Phosh < Gnome mobile
I could also add XFCE but they officially don't support mobile.
Android isn't the lightest mobile environment by any conceivable means, maybe it's the most featured but certainly not the most optimized for low-end devices, the days of Android 11 are over.
You need 4GB of ram, a good CPU and full hardware acceleration to run modern Android.
And if the next Android bumps the requirements again, I would put it at the end of the list.

A new major release of Phosh is out. See below for a list of changes across individual components:
A graphical shell for mobile devices
Detailed list of changes | Tarball | Checksum | Signature
A Wayland compositor for mobile devices
Detailed list of changes | Tarball | Checksum | Signature
A user friendly on-screen keyboard
Detailed list of changes | Tarball | Checksum | Signature
A Mobile (and Phosh specific) Settings Application
AdwSidebar and moving conf-tweaks to their own section.Detailed list of changes | Tarball | Checksum | Signature
A short introduction to Phosh
Detailed list of changes | Tarball | Checksum | Signature
Mobile friendly portals
Detailed list of changes | Tarball | Checksum | Signature
Rust based services for Phosh’s session.
Detailed list of changes | Tarball | Checksum | Signature
A first-boot helper for Phosh
Completion data for Phosh’s on screen keyboards
Not released in the 0.56.0 cycle, latest is 0.53.0
Phosh wallpapers, sounds and other artwork
Not released in the 0.56.0 cycle, latest is 0.55.0
Common user interface parts for call handling
Not released in the 0.56.0 cycle, latest is 0.1.5
Bits useful in mobile related, glib based projects
Detailed list of changes | Tarball | Checksum | Signature
Rust bindings for libphosh
Not released in the 0.56.0 cycle, latest is 0.0.7
Rust bindings for libpms
File selector widget and related tooling
Detailed list of changes | Tarball | Checksum | Signature
These components are purely optional:
A virtual mouse prototype
Not released in the 0.56.0 cycle, latest is 0.20.0
Without these the above wouldn’t be possible. This release is based on:
For more details on dependencies and required patches see the detailed list of changes of the individual components.
Other components often used with Phosh but not mandatory:
releases at phosh.mobi.