A Fairphone 4 owner has documented a move from Android to SailfishOS, offering a detailed case study of the trade-offs facing people who want a more conventional Linux environment on a phone. The account is one user's experience rather than a broad assessment of either platform.
The author attributed the switch to dissatisfaction with Google's direction for the Android Open Source Project, including dependence on Google Play Services, obstacles for custom ROM development, increased integration of AI features and tighter control over installing applications. With a Fairphone 4 capable of running several alternative operating systems, the author considered SailfishOS, Ubuntu Touch and postmarketOS before choosing SailfishOS.
Sailfish's gesture-based interface and application framework received favorable marks. The system also allows the phone to be accessed from a computer through SSH over wireless or USB connections, a feature that makes familiar Linux tools available for troubleshooting and customization. That level of access was central to the appeal of the experiment.
The move also exposed substantial limitations. On the unofficial Fairphone port used by the author, GPS and Waydroid were not working. The system included older versions of Python and the GNU C library, complicating some tasks. Community applications varied in quality, including an unofficial client needed for WhatsApp access.
Ubuntu Touch solved some problems but created others in the author's test. Waydroid worked there, making Android applications accessible, but clipboard and notification integration caused difficulty with services such as Bitwarden. The author also found the default applications less capable and could not determine how to block telephone numbers. Preferences about navigation and the top-level interface further favored SailfishOS.
The largest obstacle was not cosmetic. Banking and government authentication in Norway, as well as services such as Uber used in Brazil, still required Android applications. The author's workaround was to keep a Galaxy A17 as a secondary device, connect it through the Fairphone's hotspot for those tasks, and otherwise minimize its use.
That two-phone arrangement shows why mobile Linux remains difficult as a complete replacement even for a technically experienced user with compatible hardware. Basic telephone functions and system control are only part of the requirement; access to institutions and local services can depend on proprietary applications.
The author plans to keep notes on what succeeds and fails and may later publish a fuller report or video. A Jolla Phone 2 is also under consideration. For now, the experiment presents mobile Linux as usable enough for a primary device in this particular setup, but not yet sufficient to eliminate Android entirely.
