Why an Old Android Phone Beats a Raspberry Pi for Photos
That scratched, retired Android phone in your drawer is far more capable than it looks. Under the worn-out case is a compact, battery-powered computer that often outperforms entry-level single-board machines used for self-hosting. It typically offers a faster processor, more built‑in storage, reliable Wi‑Fi, and a display for quick debugging. Crucially, the battery doubles as a built‑in UPS, keeping your self-hosted photo server online through brief power cuts. Instead of paying ongoing fees for a cloud backup, you can run a Google Photos alternative locally and retain full ownership of your library. This approach removes your dependency on remote servers and AI-driven analysis of your images, without demanding a noisy desktop or a dedicated NAS box. For many households, converting an old Android phone into private photo storage is the simplest, quietest, and most cost‑effective path to a self-hosted photo server.
Prepare the Phone and Install Termux
Start by wiping the old phone or at least removing personal apps you no longer need. Disable unnecessary background services, reduce screen brightness, and enable developer options so the device runs cooler and more efficiently while plugged in permanently. Next, install Termux from F-Droid rather than a generic app store, ensuring access to the latest repositories and packages. When you first open Termux, you’ll see a Linux-style command line—this is your gateway to turning Android into a self-hosted photo server. Run a package update, then execute the termux-setup-storage command. This critical step gives Termux permission to read and write to the phone’s shared storage so your future photo library isn’t trapped inside the app’s sandbox. With storage access granted and the terminal ready, your old Android phone is now set up as a lightweight development environment for private photo storage.
Install Lychee and Build Your Self-Hosted Photo Stack
Lychee is a modern, browser-based photo manager that feels similar to Google Photos but runs entirely on your hardware. Inside Termux, install the essentials: PHP, the Apache web server, Git, and SQLite. SQLite keeps the database lightweight and avoids the overhead of a full MySQL server, which is important for older devices that might otherwise overheat or slow down during indexing. Use Git to clone the Lychee repository, then Composer to install PHP dependencies. On Android, you may need additional PHP extensions, such as ImageMagick and Sodium, to handle thumbnail generation and cryptographic functions correctly. Once the dependencies are installed, run Lychee’s migration command to create the internal database structure, then adjust folder permissions so the app can write to storage and cache directories. Finally, increase PHP’s upload limits so large photo batches import cleanly. At this point, your self-hosted photo server stack is live.
Access, Backup, and Live Without Cloud Subscriptions
With Lychee running on your old Android phone, you can access your private photo server from any browser on your home network and, with appropriate port forwarding and security, from anywhere. Upload photos directly from your daily driver phone or camera, letting Lychee organize them into albums and generate thumbnails for quick browsing. Because everything stays on your hardware, you maintain full control over your data without recurring subscription fees or automated AI analysis. The phone’s battery helps maintain uptime during short outages, and its compact size means you can place it discreetly near your router. For many users, this setup works as a primary backup; for others, it becomes a secondary layer alongside an external drive or NAS. Either way, reusing an old Android phone in this way transforms e‑waste into a practical, always‑available Google Photos alternative.