Why an Old Android Phone Beats a Raspberry Pi for Self‑Hosting
That scratched, retired Android phone in your drawer is far from obsolete. Underneath the aging screen is a surprisingly powerful little computer that often outperforms the Raspberry Pi people buy specifically for self-hosting. You get a capable processor, decent onboard storage, fast Wi‑Fi, and an integrated battery that keeps your services running through brief power cuts. All of that makes it an ideal base for a self-hosted photo server. Instead of paying ongoing Google Photos subscription fees and giving a cloud provider control over your memories, you can run a modern, Google Photos–style gallery entirely on your own hardware. This approach delivers private photo storage, full data ownership, and freedom from changing cloud policies. If you’re reasonably tech‑savvy and comfortable with a command line, turning an old phone into a Google Photos alternative can be both a fun weekend project and a long‑term backup solution.
Preparing Your Phone: Termux and Storage Access
To turn your phone into a self-hosted photo server, you first need a Linux‑like environment. Install Termux from F‑Droid rather than the Play Store to get up‑to‑date repositories and better package support. When you launch Termux, you’re greeted by a command-line interface that unlocks your phone’s true potential but can feel intimidating if you’re new to terminals. Start by running a package update and upgrade so your environment is current. Next, issue the termux-setup-storage command. This crucial step grants Termux visibility into your device’s internal storage and media folders; without it, your future photo server would be trapped in Android’s sandbox and unable to see your pictures. Once storage access is configured, you’ve effectively bridged Android’s filesystem and your Linux environment. At this point, your old Android is ready for the software stack that will power your private photo storage and Android photo backup solution.
Installing Lychee: A Google Photos–Style Gallery on Your Phone
Lychee is a clean, professional-grade photo management system that feels familiar if you’ve used Google Photos, but it runs entirely on your own hardware. It’s built on PHP and Laravel, which means you’ll set up a lightweight web stack inside Termux: install PHP, the Apache web server, Git, and a database engine. For an old phone, SQLite is ideal because it’s light on resources yet handles sizeable photo libraries, avoiding the overhead of a full MySQL instance. After installing Composer, the PHP dependency manager, clone the Lychee repository directly from GitHub and run composer install. This step can take longer than on a desktop server because smartphone CPUs are slower, so be patient. Once dependencies are in place, use Lychee’s Artisan tools to run database migrations, which create the internal structure for albums, metadata, and user accounts. You now have the core of a self-hosted photo server running locally on your Android.
Configuring Thumbnails, Permissions, and Upload Limits
To make Lychee usable as a full Google Photos alternative, you need smooth thumbnail generation and proper filesystem permissions. On Android, graphics libraries behave differently than on typical Linux servers, so you may need to install extra PHP extensions such as Sodium and ImageMagick inside Termux. These tools handle image processing tasks and prevent your gallery from turning into a wall of broken icons. After installing them, point PHP to the correct libraries so Lychee knows where to find its image tools. Next, adjust directory permissions so Lychee can write to storage and cache folders; Android is strict about file access, so this step is essential. While you’re editing configuration files, increase PHP’s default upload limits so large photos and videos don’t fail silently. With thumbnails rendering correctly and permissions tuned, your old phone becomes a responsive, private photo storage solution accessible from any browser on your network.
Living With a Self‑Hosted Android Photo Backup
Once Lychee is running reliably, your old phone effectively behaves like a tiny, battery‑backed photo server. You can access galleries from laptops, tablets, or your main phone, enjoying features like albums and easy sharing without sending your media to a third‑party cloud. This setup eliminates recurring Google Photos subscription fees while giving you complete control over retention, organization, and access policies. Because everything runs locally, there’s no opaque AI analysis of your images or sudden policy shifts to worry about. For maximum resilience, many people still keep this as part of a broader backup strategy alongside external drives or other servers. However you integrate it, repurposing Android hardware extends the life of a capable device, cuts e‑waste, and delivers a flexible self-hosted photo server. For anyone comfortable tinkering with Termux and basic Linux tools, it’s a compelling, privacy‑first Google Photos alternative.