Your old Android is a better home server than a Raspberry Pi

4 min read 1 source clear_take
├── "The economics of home servers have inverted — used phones now beat single-board computers on cost and features"
│  └── seg6 (Hacker News) → read

Argues that a $60-80 used Pixel 4a delivers the same effective compute as a $135 Raspberry Pi 5 kit while throwing in a battery, cellular modem, Wi-Fi 6, OLED display, and storage for free. Contends the SBC industry has been quietly outcompeted by the used phone market and hasn't noticed because the two categories are shelved separately.

├── "The built-in battery is the killer feature — phones are self-contained UPS-equipped servers out of the box"
│  └── seg6 (Hacker News) → read

Highlights that the phone's 4,000mAh lithium battery functions as a zero-configuration UPS, surviving blackouts without any added hardware. Combined with the cellular modem that can ping a healthcheck endpoint when home Wi-Fi drops, the phone offers resilience features that a Pi requires multiple add-on purchases to match.

└── "Manufacturer abandonment of still-functional phones is a wasted resource that hobbyists can reclaim"
  └── seg6 (Hacker News) → read

Frames the used phone glut as a direct consequence of vendors halting security patches on hardware that is otherwise fully capable. Using Termux with a Debian proot and Tailscale for access, the author demonstrates that these 'abandoned' devices can be productively reused as capable Linux servers with minimal effort.

What happened

A post titled *"My server is a phone now"* hit the Hacker News front page this week (313 points and climbing) with a deceptively simple thesis: the author replaced their Raspberry Pi home server with a secondhand Android phone, and everything got better. Not marginally better — categorically. The phone runs quieter, uses less power, survives blackouts without a UPS, and cost less than the Pi 5 plus enclosure plus NVMe hat plus PSU plus SD card it displaced.

The hardware inventory reads like a self-own for the SBC industry. A midrange 2021 Android handset ships with an 8-core ARM64 SoC, 6-8GB of LPDDR5, 128GB of UFS storage, a cellular modem, Wi-Fi 6, Bluetooth, GPS, a microphone, a camera, an OLED status display, and — critically — a 4,000mAh lithium battery that functions as a built-in UPS with zero configuration. The author's build uses Termux with a Debian proot for the userland, ssh over Tailscale for access, and a cronjob that pings a healthcheck endpoint from the cell modem when the home Wi-Fi drops. Total spend: about $75 on eBay.

The post is not the first of its genre — Louis Rossmann and a handful of PostmarketOS hackers have been beating this drum for years — but it landed differently in 2026, with Raspberry Pi 5 kits now pushing $120 before storage and the used-phone market saturated with fully functional devices that manufacturers have simply stopped patching.

Why it matters

The interesting part isn't that a phone can be a server. Phones have been Linux boxes with radios strapped to them since 2008. The interesting part is that the economics have quietly inverted. A Pi 5 with 8GB, an official PSU, a case with a fan, and a 128GB SD card is now roughly $135. A used Pixel 4a with the same effective specs, plus a battery, plus a modem, plus a screen, is $60-80 depending on cosmetic condition. The SBC market spent a decade competing on price against phones and lost — the industry just hasn't noticed because the two categories were shelved separately at Micro Center.

Power draw makes the comparison uglier. A Pi 5 under light load pulls 3-5W at the wall. A modern phone in airplane mode running the same workload pulls 0.8-1.5W and throttles gracefully instead of thermal-shutting-down. Over a year of 24/7 operation at $0.15/kWh, the phone saves roughly $4-5 in electricity — trivial in absolute terms, but it means a solar panel the size of a paperback can run the whole thing.

Then there's the resilience story, which is where the post gets genuinely persuasive. Home servers die from three things: power loss, SD card wear, and thermal events. Every smartphone ever manufactured has hardware-level protection against all three, because losing your phone to a brownout would be a warranty nightmare Samsung and Apple engineered out a decade ago. The battery smooths power. The UFS storage has a controller with wear leveling that makes Pi SD cards look like paper. The SoC will throttle to 200MHz before it lets itself cook. You get datacenter-grade reliability engineering as a free side effect of consumer QA budgets.

The HN thread surfaced the counterargument fast: batteries degrade, phones are locked down, and the whole thing is one Android security update away from bricking your SSH access. All fair. But the top-voted rebuttal was blunt: *"my Pi's SD card has died three times in two years; my old phone battery is at 82% health after six."* The failure modes of consumer hardware, it turns out, are better characterized than the failure modes of hobbyist hardware — because the consumer stuff shipped in billions of units and got debugged.

What this means for your stack

If you're running Home Assistant, Pi-hole, a Syncthing node, a Tailscale exit node, a small Postgres, or basically any always-on personal service, the sensible move for your next refresh is: don't buy a Pi. Go to eBay, filter for "Pixel 4a" or "OnePlus 7" or "Galaxy S10" under $80, and install either Termux (easy mode, keeps Android) or PostmarketOS (hard mode, real Linux). The days of the Raspberry Pi being the default answer for "I need a small always-on computer" are functionally over — the Pi Foundation just hasn't been told yet.

A few practical notes from the thread and adjacent PostmarketOS wiki: pick a device with an unlockable bootloader if you want mainline Linux (Pixels are the safest bet). Disable charging above 80% via `acc` or Battery Charge Limit to keep the battery healthy for years instead of months — this is the single biggest reliability tweak and takes ten minutes. Route everything through Tailscale or a Cloudflare tunnel so you're not fighting carrier NAT. And if the phone has a cell modem, put a $5/mo prepaid SIM in it for out-of-band access when your home internet dies — a capability a Pi cannot match at any price.

The things a phone-server is bad at are also worth naming. Serious storage is out — you're stuck with USB-OTG which is finicky and slow. GPIO is basically nonexistent, so hardware hacking projects still want a Pi or an ESP32. And if you need more than one Ethernet port, you're back to a mini-PC. Phones win the "headless Linux box for services" niche, not the "embedded controller" one.

Looking ahead

The deeper story here is e-waste as opportunity. Roughly 1.5 billion smartphones are manufactured every year and the median device gets retired at 3-4 years old with 90% of its silicon still working. The homelab community is one of the few places that can absorb that supply at scale, and posts like this one are how the pattern spreads. Expect the next wave of self-hosted docs — Home Assistant, Nextcloud, Immich — to start including "install on a used Android" as a first-class deployment target within the next 18 months. The Pi Foundation should be nervous. The environment should be delighted.

Hacker News 494 pts 236 comments

My server is a phone now

→ read on Hacker News

// share this

// get daily digest

Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.