Quick Answer: An old smartphone can work as a Raspberry Pi alternative when your project needs a camera, GPS, storage, a clock, a battery, and mobile data in one device. Used phones can cost roughly ¥300–500 in the author's listings. The trade-offs are real: phones have no GPIO header, Android's power management fights scheduled work, and matching units are hard to source in bulk.

A Raspberry Pi is a good board. Add a high-resolution camera, a GPS module, storage, an RTC, a UPS HAT, a display, and a cellular modem, though, and the bill climbs fast. The author of so.long.thanks.fish hit exactly this wall while designing a light-control project. Their answer was to look at what a used phone already contains. Here's what they found, and where the idea breaks down.

What a used phone already includes

Most of the hardware you'd buy for a Pi build is already sealed inside a phone. The Redmi 13C 5G gives the author a camera that saves 50MP JPEGs. The Huawei Mate 30 5G has a 40MP main camera plus a telephoto lens. Both include GPS, storage, a clock, a battery, mobile data, and a touchscreen.

Here's what that means in practice:

  • Camera: A 50MP sensor is a file-size number, not a detail measurement. The author is photographing the same target with the Redmi and an Arducam 64MP side by side to see what each one actually resolves.
  • Connectivity: Built-in GPS and mobile data remove two HATs and a SIM adapter from the bill of materials.
  • Power: The battery is a backup you didn't have to buy, though you'll need to watch its health.

The cost argument is strong on paper. Used phones of this class turn up on Taobao for roughly ¥300–500, or about £33–56, €40–67, or $45–75 at the mid-market rates the author used on 10 November 2026.

The real cost comparison

The author's listings put the Pi route well above the phone. The table below uses those figures, which are illustrative November 2026 prices. It excludes the custom light-controller PCB, any SIM or data plan, and the enclosure.

ItemUsed Redmi or Mate 30Raspberry Pi 4 (4GB) route
Core: computer, camera, GPS, storage¥300–500 (phone price)~¥1,483 (Pi ¥880, Arducam ~¥400, GPS HAT ~¥153, 64GB microSD ~¥50)
Clock, battery backup, display, mobile dataIncluded~¥987 (RTC HAT ~¥80, UPS HAT ~¥133, 5-inch touchscreen ~¥247, 4G HAT ~¥527)
Fully equipped total (cellular HAT's GPS replaces GPS HAT)¥300–500~¥2,317, plus batteries
Camera resolution50MP JPEG (Redmi), 40MP (Mate 30)64MP (Arducam), a different sensor and lens

The comparison has two caveats. First, the Pi's modem is 4G while both phones are 5G, so connectivity isn't identical. Second, the phone's cost is for a device that already includes its sensors, while the Pi's cost is for a board you still have to populate. That's the real difference: you're not buying a cheaper computer, you're buying a different bundle of parts.

This next part matters more than it looks.

Where the phone fails: GPIO and USB

Here's the catch that most "use your old phone" posts skip. A Raspberry Pi exposes a 40-pin GPIO header with I²C, SPI, UART, and PWM directly on the board. A phone has none of that. Its only physical interface for your custom hardware is USB-C.

The author plans to talk to the light-control PCB over USB-C. That's workable, but it's a different architecture:

  1. The phone must act as a USB host via an OTG cable, using Android's USB host API documented at developer.android.com.
  2. The PCB needs a USB-to-serial bridge or a microcontroller that speaks a USB device class Android recognizes.
  3. Your app needs to hold the connection open, which Android may not do reliably in the background.

The trade-off is clear: a phone gives you more sensors and fewer parts, but the moment you need to drive hardware, its advantage shrinks to whatever your USB link can carry. Prototype that link before you commit to a batch. A cheap USB-serial adapter and a test app will tell you more in an afternoon than any spec sheet.

Android power management will fight your schedule

Phones are built to sleep aggressively. That's good for battery life and bad for scheduled hardware work. Android's Doze and App Standby modes defer background activity when the device is idle and unplugged. Your job at 03:00 can slip by hours if you don't plan for it.

The author got the Redmi sleeping and waking for scheduled work, which required rooting and tuning. The Huawei Mate 30 is harder to root, so they're using it for a kiosk app instead. That's a useful split: root access gives you control, while a kiosk app on an unrooted phone gives you a locked-down display with less control.

For apps that must run on time, Android's developer documentation on Doze and App Standby describes exact alarms and allowed-while-idle exceptions. Use them, then test with the device unplugged and the screen off overnight. If a phone isn't rooted, expect it to ignore some of your timing assumptions.

The supply problem nobody prices in

This is the counter-intuitive part. The common advice says phones are cheap, so use them. The reality is that the phone's price is not the hard number. The hard number is how many matching units you can buy.

Two good used phones are easy to find. A few hundred with healthy batteries and predictable camera behavior takes real work. Batteries age unevenly, camera modules vary between production runs, and sellers rarely document either. A Raspberry Pi 4 is a catalogued SKU with a known board revision. A used phone is a lottery ticket with a plausible spec sheet.

That isn't a reason to avoid phones. It's a reason to build a test rig before you order: charge cycle checks, a standard camera target, and a documented pass/fail threshold for each unit. The author's side-by-side camera test is exactly that kind of check.

When to use a phone vs a Pi

Here's where the choice gets practical. Use a phone when the sensors matter more than the pins, the device needs cellular data, and you want something that can be shipped as a self-contained unit. Use a Pi when you need many GPIO lines, long-term OS support, or a board you can document and reproduce.

The author's installation idea shows the phone case well. Instead of sending a gallery a Raspberry Pi and asking for Wi-Fi access or an open port, you could post a configured phone. Plug it into the display, and it runs. With mobile data and remote access, you can fix problems without touching the venue's network. That's a deployment advantage the Pi can't match without extra hardware.

But that advantage depends on the phone staying alive, updated, and rooted (if you need root). A Pi gives you a clearer maintenance path. Pick the platform that fits your failure modes, not the one with the lower sticker price.

Frequently Asked Questions

what is a raspberry pi alternative for camera projects?

An old Android phone with a high-resolution camera can replace a Pi plus camera module, GPS HAT, storage, and mobile data hardware. The Redmi 13C 5G and Huawei Mate 30 5G are examples the source article uses. Check battery health and camera output first, because performance varies between used units.

why use an old phone instead of a raspberry pi?

A used phone bundles a camera, GPS, storage, a clock, a battery, mobile data, and a touchscreen in one device. In the author's listings, that comes to roughly ¥300–500 against about ¥2,317 for a fully equipped Pi build. You trade away GPIO pins and some control over power management.

how do I connect an old phone to a microcontroller?

Use USB host mode with an OTG cable and a USB-to-serial bridge or a microcontroller with a standard USB device class. Android's USB host API lets your app open the connection. Test the link with a cheap adapter before committing to a batch of phones or a custom PCB.

can a rooted old phone run scheduled tasks reliably?

Often, yes, but Android's Doze and App Standby modes can delay background work. Use exact alarms and allowed-while-idle exceptions, then test overnight with the screen off and the device unplugged. Unrooted phones are more restricted, so plan for that difference.

Choosing between a phone and a Pi comes down to what your project needs to touch. If the camera, GPS, and cellular link matter more than GPIO, a used phone can be the cheaper, more self-contained option, as the original post explains. Buy one used phone this week, check its battery health and camera output against a test target, and compare the result with your current Raspberry Pi alternative bill of materials. Pass this to anyone stuck on a Pi build with a growing parts list.