DEV Community: Super Funicular

A local-only home security camera from an old Android phone: setup and how the free apps compare

Super Funicular — Tue, 11 Aug 2026 04:42:52 +0000

Plenty of us have a working Android phone sitting in a drawer while paying a monthly fee for a cloud camera. Here is the local-only alternative: an old phone, a screen-off camera app, and about a minute of setup — no cloud account, no subscription.

The setup

Grab any Android phone you are not using. Install Background Camera RemoteStream (free, no account), grant camera and microphone access, then lock the phone -- recording and streaming continue with the screen off. Point it where you need eyes and open the stream on any other device on the same WiFi network.

What I tested

Recording keeps running with the screen off and the app in the background, which is the part most 'IP camera' apps get wrong on modern Android. The stream stays on your local network, so there is no cloud relay in the path and no account to create.

How it compares

Alfred Camera: easy to start, but the free tier is limited, shows ads, needs an account, and routes video through its cloud.
IP Webcam: powerful and fully local, but more technical to set up.
FadCam: a strong open-source screen-off recorder with LAN streaming of its own -- but it is sideload-only (F-Droid/GitHub, not on the Play Store), which is a real hurdle if you just want a one-tap install.
Background Camera RemoteStream: free, no account, records with the screen off, streams over your own WiFi, and installs straight from the Play Store.

Why local-only

Keeping the feed on your own network means the video never leaves your home unless you send it there. For a baby monitor, pet cam, or porch camera, that is the whole point.

If you want the step-by-step version, I wrote a fuller walkthrough here: https://dev.to/superfunicular/turn-an-old-android-phone-into-a-screen-off-security-camera-no-cloud-lan-only-5cll -- and a deeper three-app comparison here: https://dev.to/superfunicular/background-camera-remotestream-vs-fadcam-vs-ip-webcam-which-actually-travel-cam-4g2h

Open question for the dev.to community

What is your setup for reusing old Android hardware instead of buying another subscription camera? Curious what has worked for others.

App: https://play.google.com/store/apps/details?id=com.superfunicular.digicam · Site: https://superfunicular.com · Built solo by Super Funicular LLC.

Cancel the Camera Subscription: The Best Cloud-Cam Replacements in 2026 (After Ring, Nest, Alfred, Blink and Wyze All Raised Prices)

Super Funicular — Mon, 10 Aug 2026 07:08:34 +0000

Something quiet happened over the last twelve months: almost every consumer security camera you can buy got more expensive to keep, not to own. The hardware still costs what it cost. It's the monthly bill that moved.

Ring raised Protect plans on February 1, 2026 — Basic went to $5.99/mo, Plus to $12/mo, Pro to $24/mo, a 17–20% jump across the board. (Ring's own notice)
Google turned Nest Aware into "Google Home Premium" and pushed Standard to $10/mo ($100/yr) and Advanced to $20/mo ($200/yr). (PCWorld)
Blink changed plans on October 8, 2025 — Basic $3.99/mo, Plus $11.99/mo ($119.99/yr). (Blink Support)
Wyze bumped Cam Plus Annual from $19.99 to $29.99 in March 2026. (Wyze)
AlfredCamera raised Premium roughly 20%, with annual going from $29.99 to $35.99. (AlfredCamera Help Center)

If you already own one of these cameras, none of that is optional in the way it feels. The camera is a paperweight without the plan — motion clips expire in seconds, "you have a notification" leads to a paywall, and the footage you actually wanted lives on someone else's server.

So here's a different question than the usual "which camera should I buy": what can you replace a cloud camera subscription with — right now, with hardware you already own, for $0/month?

I've spent the better part of this year testing exactly that. Below is the honest ranking, our own app included and placed where I genuinely think it belongs for this specific job: getting off the subscription treadmill.

The short answer

The cheapest way to replace a cloud camera in 2026 is to stop renting one. An old Android phone you already have — a drawer-dweller from two upgrades ago — has a better camera than most $35 security cams, a battery, Wi-Fi, and a CPU. Point software at it and it becomes a camera that records with the screen off and streams to you over your own network, with nothing leaving the house and no card on file. That software is what this list is about.

How I ranked these

Every option here is judged on one axis the manufacturers don't advertise: cost of ownership at 24 months, plus how much of your footage the vendor can see. A camera that's "free to buy" and $12/month is $288 over two years and stores your living room in a data center. A phone you already own running local software is $0 and stores nothing anywhere but the phone. That gap is the whole article.

The comparison

Option	Monthly cost (2026)	24-month cost*	Where footage lives	Works with hardware you own?	Account required?
Background Camera RemoteStream	$0	$0	Only on the phone (local)	Yes — any old Android	No
Wyze Cam Plus	$2.99/mo	~$72	Wyze cloud	No (needs Wyze cam)	Yes
Ring Protect Basic	$5.99/mo	~$144	Amazon cloud	No (needs Ring device)	Yes
AlfredCamera Premium	~$5.99/mo	~$144	Alfred cloud	Partly (uses phones, caps free tier)	Yes
Blink Plus	$11.99/mo	~$288	Amazon cloud	No (needs Blink cam)	Yes
Nest Aware (Home Premium)	$10/mo	~$240	Google cloud	No (needs Nest cam)	Yes

*Subscription only, at current 2026 rates, hardware excluded. Existing subscribers may be grandfathered until renewal.

Now the reviews.

1. Background Camera RemoteStream — the actual subscription killer

Cost: $0/month, forever. Storage: local-only. Account: none.

I'll be upfront that I'm biased — we make this one — so I'm going to review it the way I'd review a competitor: by telling you what it doesn't do first.

It is not a doorbell. It doesn't ship a physical camera. It won't do person-vs-package AI labeling in the cloud, because it has no cloud. If your mental model of "security camera" is a glowing orb on a shelf that texts you when the dog walks by, this is a different shape of tool.

What it actually is: an app that turns an Android phone into a camera that keeps recording with the screen completely off, saves that video locally on the phone, and — this is the part that replaces the subscription — runs a small built-in web server so you can pull up the live view from another device on your own network. It can also stream to YouTube Live if you want a remote feed without any middleman surveillance service. There's no account, no card, no monthly anything. The footage never leaves the phone unless you choose to send it somewhere.

Why it earns the top slot for this job: the entire reason people pay Ring or Nest every month is remote access to footage and retention. RemoteStream gives you remote viewing over your network and retention limited only by the phone's storage — which, on a 128GB handset, is a lot of the recording you'd actually go back and watch. You're not renting either capability. You're running them.

The honest trade-offs: you're responsible for mounting and powering the phone (a $6 stand and a charging cable), the built-in web server is designed around your local network rather than a global "view from the airport" cloud relay, and it's Android-only. If those fit your situation — and for "replace the camera I'm tired of paying for," they usually do — the price of admission is a phone you already stopped using.

It was, incidentally, built in public over 75+ AI-assisted development sessions, which is why the technical writeups on how it survives Android's background-process killer are unusually candid.

Get it: Background Camera RemoteStream on Google Play · superfunicular.com

2. AlfredCamera — the closest philosophical cousin, but the free tier keeps shrinking

Cost: free tier exists; Premium ~$5.99/mo or $35.99/yr (up ~20% in 2026).

Alfred deserves credit: it pioneered the "use old phones as cameras" idea and it's genuinely easy. If you want a polished, cross-platform (iOS + Android) old-phone camera and you're okay with an account and cloud relay, it's a reasonable pick.

The catch is the direction of travel. The free tier is where most people live, and it's the tier that keeps getting narrower — lower resolution, watermarks, capped features — while Premium got more expensive in 2026. It's cloud-first by design, so your motion clips route through Alfred's servers. If your reason for leaving Ring was "I don't want my footage on someone's cloud," Alfred solves the hardware-cost problem but not the privacy one. I wrote a fuller breakdown of the free-tier caps in the AlfredCamera alternatives guide.

Pros: mature, easy, iOS + Android. Cons: cloud-routed footage, shrinking free tier, rising Premium price.

3. Wyze — cheapest subscription, but you still buy the hardware and rent the brain

Cost: Cam Plus $2.99/mo or $29.99/yr (raised from $19.99 in March 2026).

Wyze is the value benchmark for a reason — the cameras are cheap and Cam Plus is the least expensive of the big plans. But two things: you're buying new hardware (so it's not a "use what you own" replacement), and without Cam Plus the camera degrades to short cooldown-gated clips. Wyze has also had well-publicized incidents where users briefly saw other users' feeds, which is exactly the failure mode local-only storage doesn't have. Good budget system; not a subscription-free path.

Pros: cheapest plan, low hardware cost. Cons: requires buying Wyze cams, cloud storage, past privacy incidents, price rising.

4. Ring — great hardware, subscription is now the point

Cost: Basic $5.99, Plus $12, Pro $24/mo (all up 17–20% Feb 2026).

Ring makes legitimately good doorbells and the app is excellent. But in 2026 the plan is the product — no subscription means no saved video at all, just live view and a chime. The 2026 increase pushed Plus to $12/mo, which is $288 over two years for the storage you assumed you were buying with the hardware. It's also Amazon-cloud by architecture, with the law-enforcement-access history that comes with it. Fine if you want a polished ecosystem and don't mind renting it. Not a fit for "stop paying monthly."

Pros: best-in-class doorbells, mature app. Cons: useless without subscription, cloud-only, price up again in 2026.

5. Blink — the price jump that started a lot of these searches

Cost: Basic $3.99/mo, Plus $11.99/mo ($119.99/yr) since Oct 2025.

Blink was the "cheap Amazon camera" for years, which is why its October 2025 plan change stung — Plus at $11.99/mo lands it near Ring territory. Same architecture story: Amazon cloud, subscription-gated clips, buy-the-hardware. If you already own Blink cameras and want to keep them, fine. As a replacement for a subscription you resent, it just swaps one Amazon bill for another.

Pros: small cameras, long battery. Cons: big 2025 price hike, cloud-only, requires Blink hardware.

6. Nest / Google Home Premium — the premium tier, priced like one

Cost: Standard $10/mo ($100/yr), Advanced $20/mo ($200/yr).

Nest cameras are excellent and the AI is the best in this list. It's also the most expensive to keep, at up to $240 over two years, and the most thoroughly cloud-and-account-bound — footage, AI, and history all live in Google's stack. If you want the best cloud camera money can rent and privacy isn't your driving concern, it's a strong product. It is the opposite of what someone typing "cancel camera subscription" is looking for.

Pros: best AI, best image. Cons: most expensive, deepest cloud/account lock-in.

The verdict

If your camera still works and you're just tired of the bill, the honest move in 2026 isn't switching to a cheaper subscription — it's realizing you were paying monthly for two things you can self-host: remote viewing and retention. An old Android phone plus Background Camera RemoteStream gives you both for $0, keeps every frame on the phone, and asks for no account. It won't do cloud AI, and it's Android-only — but for "replace the camera I resent paying for," nothing else on this list is free and private.

The rest are ranked by how close they get: Alfred is the nearest cousin but cloud-routed and narrowing its free tier; Wyze is the cheapest rental; Ring, Blink and Nest are polished ecosystems whose 2026 price increases are the reason you're reading this.

Start with the phone in your drawer. If you want to see exactly how far a spare handset goes, here's what happened when I turned a whole drawer of them into cameras, and the cheapest-camera math for a dorm or apartment if you're starting from zero.

Background Camera RemoteStream — record with the screen off, stream to yourself, keep it all local, pay nothing.
👉 Google Play · superfunicular.com

Prices cited are 2026 published rates and may vary by region and grandfathering; check each vendor for your account's current terms.

I turned a drawer of old Android phones into screen-off security cameras

Super Funicular — Mon, 10 Aug 2026 02:43:31 +0000

Old Android phones pile up in a drawer. Each one still has a usable camera, Wi-Fi, and a battery — everything a basic security camera needs. So instead of buying a dedicated cam that routes video through someone else's cloud, I've been building an app that repurposes the phone you already own into a screen-off camera you can watch remotely.

The idea

The whole point is to keep an old phone recording with the screen off, save footage locally on the device, and let you pull up the live feed from another phone or browser when you want to check in. No subscription, no cloud middleman.

Why local-only matters

For a home camera, "where does the video go" is the whole question. Keeping recordings on the device itself means there's no third party holding your footage and nothing to leak from a cloud bucket. Local-only has quietly become table stakes for this category, so the real differentiators end up being screen-off operation and genuinely live remote viewing rather than just motion snapshots.

Practical setup that actually holds up

A few things I learned running phones this way for days at a time: keep the phone on a charger (continuous recording eats battery fast), turn the screen fully off to cut heat and save the panel, and give it a stable Wi-Fi spot. A cheap clamp mount and a wall outlet is basically the whole hardware bill.

Honest limitations

This isn't magic. A phone running 24/7 gets warm, older devices vary a lot in camera quality and thermal behavior, and everything depends on your Wi-Fi staying up. It's a great fit for a porch, a garage, a nursery, or an Airbnb check-in view — less so for a hardened outdoor deployment.

Open question for the dev.to community

For those of you who've repurposed old hardware like this: what's your trick for keeping an always-on Android device thermally stable over long stretches? Undervolting, airflow, capping the recording resolution? I'd like to hear what's worked.

App (free on Play): https://play.google.com/store/apps/details?id=com.superfunicular.digicam
More: https://superfunicular.com

The Herons, the After-Dark Dump Truck, and a Phone Nobody Noticed: How a $0 Camera Saved a Backyard Marsh

Super Funicular — Sun, 09 Aug 2026 07:07:38 +0000

Everyone on the cul-de-sac agreed the marsh was "just filling in on its own." Corinne was the only one who kept the dates.

She was a retired librarian, which is to say she had spent forty years being politely certain about facts other people were vaguely sure about, and she had lived in the same house at the end of the same dead-end street for most of them. The back of her lot dropped off into a shallow protected marsh — a soggy quarter-acre of cattails and open black water that the town had zoned as wetland decades ago and then, mostly, forgotten. Corinne had not forgotten it. She had watched a pair of great blue herons work that water every spring for eleven years, stalking the shallows on their absurd stilt legs, and in the good years raising gawky, half-feathered young in the tree line at the far edge.

So she noticed, the way you notice a friend losing weight, when the open water started to shrink. First the near corner went to mud. Then the cattails at the mud's edge browned and lay down. Then, one April, the herons came back, circled twice, and did not stay.

The town's answer, when she called, was a shrug in the shape of a sentence: wetlands silt up, ma'am, it's a natural process, there's runoff from the new construction up the hill. And that was plausible enough that she almost believed it herself — until the morning she went out at dawn for the newspaper and found two fresh tire ruts cut deep into the soft ground behind her fence, and a low new shelf of gray fill dirt and busted concrete that had not been there at dusk.

Somebody was dumping. At night. Into the marsh.

What she set up, and what it honestly was

I should say plainly that I have a stake in this, because I'm the person who makes the app she ended up using, and I would rather tell you the unimpressive true version than a heroic false one.

Corinne did not install an "AI wildlife protection system." No such thing exists that I'd trust with anything, and certainly not with catching a truck. What she did was find the old Android phone that had been dead in a kitchen drawer since her grandson set her up with a new one — cracked back, swollen battery she swapped for a cheap replacement — and turn it into a plain camera she could point out her own back window.

The app is Background Camera RemoteStream, and its entire job is to take a spare phone and let you watch and record from it, with no account, no subscription, and no shipping your footage off to some company's servers. She had it running in about fifteen minutes:

She installed it from the Play Store. One tap — no "create an account to continue," no card on file, no cloud sign-up.
She stood the phone on the sill of her back bedroom window on a $6 tripod, lens angled down through the glass at the ruts behind the fence, and started a session. Then she locked the screen. The camera kept recording with the screen completely off, which mattered for a dull, practical reason and a subtle one: the phone could sit powered on that sill for days without a bright display glowing in a dark window and announcing that someone was watching.
It was plugged into the outlet behind her nightstand, because a screen-off camera sips power but does not run for days on nothing.

When she was home on her own Wi-Fi, the app's built-in web server let her open a local address in the browser on her kitchen tablet and glance at the back fence over her morning tea, with nothing leaving the house. The footage wrote to the phone's own storage — not up to a subscription cloud that keeps its own copy under its own rules, but to the device on her windowsill, where she decided what was ever looked at.

Two things she was careful about, and they are the line between protecting a marsh and spying on your neighbors. The lens pointed down and out at the wetland and the ruts on public-zoned ground behind her own fence — not across into anyone's yard, not into anyone's windows. And because the footage lived on her phone and not in a company's account, she was the one who chose the single clip that ever left the device.

The night it answered the question

Here is the honest weakness, and it's the whole reason this took patience: the phone is not good in the dark. It has no night vision, no infrared, no magic — in true blackness it sees almost nothing, and I won't pretend otherwise. The dumping happened at night. For three nights she got grainy, useless dark.

So she moved the camera and let the world help her. There was a streetlight at the mouth of the cul-de-sac that threw a weak orange wash across the back corner of the marsh, and the neighbor's motion-sensor floodlight that popped on whenever anything bigger than a raccoon crossed the property line. She re-aimed the phone to frame exactly the patch those two lights touched — the spot the ruts led to — and gave up on the parts she couldn't light.

On the fourth night, at 11:40, the floodlight tripped.

She was asleep. That's the other honest part: the app has no motion alert, no notification, nothing that pinged her phone the instant the truck arrived. It simply recorded. But because it had been recording to the device the whole time, the morning gave her what the night had taken — a clip, with a timestamp, of a flatbed truck backing to the fence line in the floodlight's glare, two men, a company name legible on the door for four full seconds, and the unmistakable slide of a load of fill going into the water where the herons used to fish.

Not a hunch. Not "wetlands just silt up, ma'am." A specific truck, a specific night, a specific act.

She did not post it online, and she did not confront anyone in the street. She copied the one relevant clip to a thumb drive — she could, because it lived on her phone and not inside some service's account with its own idea of who owns the footage — and she took it to the person whose actual job this was: the state environmental conservation officer for the county, who had, it turned out, three other quiet complaints about the same contractor and not one usable piece of evidence.

Now there was one.

Why I keep telling stories like this one

The tidy ending is that the dumping stopped, the contractor was cited under the wetlands-protection statute, and the town — suddenly very interested — ordered the fill removed. That part is true and I'm glad of it. But the honest version is the useful one.

The camera did not save the marsh. A retired librarian who kept the dates saved the marsh, and a conservation officer with a statute behind him saved the marsh. What the camera did was narrower and, honestly, more valuable: it stood on a windowsill for four nights without complaint and turned a thing everyone could dismiss — it's just filling in on its own — into a file she owned and could hand to the one person able to act on it. It shrank the distance between what she was sure of and what she could prove.

And the rest of the honest accounting, because it's load-bearing: a phone on a sill is not a ranger. It has no alerts and no AI, so she caught the truck the next morning, not the instant it arrived. It is genuinely poor in the dark, which is why the whole thing hinged on borrowing a streetlight and a floodlight instead of pretending it could see black water at midnight. It isn't weatherproof, so it stayed inside, shooting through her own glass — which is exactly where a marsh-facing camera should be anyway. It had to stay plugged in. And the tidy tablet-in-the-kitchen view only worked because she was home on her own Wi-Fi; watching from her sister's house would have meant the app's unlisted live-stream path, with the few seconds of delay any live video carries.

But that is the entire point. The technology's only job was to refuse to get in the way — no monthly fee to unlock the clip she needed, no upgrade prompt holding the footage hostage, no routing four nights of her back yard through a data center so a stranger's server could keep a copy of a marsh. It ran on a phone bound for a landfill, it cost nothing, and it kept the footage inside the four walls of the house until she chose to walk one clip to the right desk.

The herons came back the following spring. I'd love to tell you the camera brought them back. It didn't. It just made sure that when someone finally acted, they were acting on what happened — not on what was easiest to ignore.

Background Camera RemoteStream is free on Google Play — no account, no subscription, recordings stay on the device: play.google.com/store/apps/details?id=com.superfunicular.digicam. More about what it does — and what it deliberately doesn't — at superfunicular.com.

More reading:

Can an old Android phone see in the dark? An honest guide to overnight recording — why Corinne borrowed a streetlight instead of trusting the sensor, explained properly.
Where your footage actually lives, and why "local" matters when you need it later — the difference between a clip you own and a clip a company holds.
How an Android phone keeps recording with the screen off: foreground services, Camera2, and the OS fighting you — the engineering behind the phone that sat dark on a windowsill for four nights.

Background Camera RemoteStream vs FadCam vs IP Webcam: which actually travel cam?

Super Funicular — Sun, 09 Aug 2026 00:42:46 +0000

TL;DR: phone repurposing on Android works with an old phone, a screen-off recorder, and about a minute of setup -- no cloud account, no monthly fee.

The setup

What I tested

How it compares

Alfred Camera: easy to start, but the free tier is limited, shows ads, needs an account, and routes video through its cloud.
IP Webcam: powerful and fully local, but more technical to set up.
FadCam: a solid offline recorder, but it does not live-stream to another device.
Background Camera RemoteStream: free, no account, records with the screen off, and streams over your own WiFi.

Why local-only

Keeping the feed on your own network means the video never leaves your home unless you send it there. For a baby monitor, pet cam, or porch camera, that is the whole point.

Open question for the dev.to community

What is your setup for reusing old Android hardware instead of buying another subscription camera? Curious what has worked for others.

App: https://play.google.com/store/apps/details?id=com.superfunicular.digicam&referrer=utm_source%3Ddevto%26utm_medium%3Darticle%26utm_campaign%3Doldphone_camera · Built solo by Super Funicular LLC.

The Cheapest Security Camera for a Dorm or Apartment in 2026 (No Monthly Fee): Old Phone vs. Wyze, Blink, Ring & Tapo

Super Funicular — Sat, 08 Aug 2026 07:08:07 +0000

Short answer

The cheapest security camera for a dorm or small apartment in 2026 with no monthly fee is the phone already sitting in your drawer. Install Background Camera RemoteStream, prop the phone up, and you have a camera that records with the screen off, stores the video on the device itself, and streams a live view to any web browser on your network — for $0, with no account and no subscription. If you'd rather buy a dedicated camera, the best no-subscription option is the TP-Link Tapo C120 (~$40, with free local microSD recording). The one to avoid on a budget is any camera that records nothing until you pay — which, in 2026, includes Ring. Here's the honest, side-by-side breakdown.

If you're setting up a dorm room, a first apartment, or a shared house this fall, the pitch you keep hearing is "a good camera is only $30." That's true. What the price tag hides is the second bill — the monthly plan that most of these cameras quietly need before they'll actually save a clip. So the real question isn't "which camera is cheapest to buy," it's "which one is cheapest to own a year from now."

The catch with cheap cameras: the camera isn't the cost

A $36 camera with a $30/year plan costs you $66 the first year and $30 every year after. Two of them and you're paying more per year than the hardware ever cost. For a student on a budget, that recurring line item is the whole problem — and it's the reason "reuse a phone you already own" keeps winning on pure economics.

There's a privacy angle too. Most of the cheap cloud cameras route your live view and event clips through the vendor's servers, tied to an account. That's convenient, and it's why remote viewing "just works." It also means your footage lives on infrastructure you don't control, under a business model that can change — as several 2026 price hikes have shown. If you've ever wondered what actually happens to your footage when a free camera app shuts down or gets acquired, that's the risk in one sentence.

A note on prices: everything below was checked in August 2026 and is what each vendor advertises in the US. Camera prices swing hard around Prime Day and back-to-school sales, and subscription tiers change — always confirm with the vendor before you buy.

The comparison at a glance

Camera	Upfront cost	Usable with no subscription?	Local storage	Night vision	Weatherproof	Best for
Background Camera RemoteStream	$0 (reuse a phone)	Yes — always	Yes, on the phone	No	No	Cheapest, most private, reuse spare phones
TP-Link Tapo C120	~$40	Yes (free microSD)	Yes (microSD)	Yes (color)	Yes (IP66)	Best bought no-subscription camera
Wyze Cam v4	~$36	Partly (thin free tier)	Yes (microSD)	Yes (color)	No (indoor)	Cheap hardware if you add a card
Blink Mini 2	~$40	Partly (needs Sync Module for local)	Via Sync Module 2 + USB	Yes	No (indoor)	Amazon/Alexa households
Ring Indoor / Pan-Tilt Cam	~$50–$60	No — records nothing free	No	Yes	No (indoor)	People already in the Ring ecosystem

Now the detail, ranked for the "cheap, no monthly fee, dorm-or-apartment" job.

1. Background Camera RemoteStream — the $0, no-subscription pick

If the whole point is to spend as little as possible and never sign up for a plan, this is the app I'd reach for. It turns a phone you already own into a camera, so the marginal cost is zero — and it's built so that "free" and "local" are the design, not a trial.

What it does well:

It costs nothing. You're reusing hardware you already have. No $40 camera, no card to buy if the phone has storage, and critically, no monthly plan — ever. For a student with a drawer of old phones, this is unbeatable on price.
Records with the screen completely off. It runs as a proper Android foreground service, so the display can be black and the phone can sit face-down on a shelf while it keeps recording. That's the single most useful thing an old-phone camera can do, and a lot of apps do it badly. (If you want the engineering version of why that's hard, here's how a phone keeps recording with the screen off — but you don't need to read it to use the app.)
Stores footage locally, on the device. No vendor cloud in the middle. There's no account to breach and no server that can change its retention policy. In 2026, local-only recording is table stakes, and this app treats it as the default instead of a paid upgrade.
Serves a live feed to your web browser. It runs a small built-in web server, so on the same Wi-Fi you just open a browser on your laptop and watch the camera — no extra app on the viewing device.
Streams to YouTube Live for genuine remote viewing. When you need to watch from a lecture hall or across town, push an unlisted YouTube Live stream for a from-anywhere view without exposing anything publicly.
No account, no camera cap. Set up one phone or five. Nothing counts your cameras and nothing asks for money.

Honest limits — because a comparison that only lists upsides is useless:

It is not a motion-alert / AI product. No person detection, no push notification when something moves, no smart event timeline. It records and streams; it does not analyze. If you specifically want "ping my phone when someone walks in," a hardware camera with a plan does that and this doesn't.
No night vision. Phone cameras can't see in a dark room, and no app changes the physics — plan for a lit space or a nightlight. I wrote an honest guide to overnight recording on an old phone about exactly this.
No two-way audio, and it's not weatherproof — it's an indoor camera.
Keep it plugged in for 24/7 use, and LAN browser viewing needs you on the same network (use the YouTube Live path or a hotspot for true remote access). On locked-down campus Wi-Fi, device-to-device viewing is sometimes blocked — the dorm-room setup guide covers the workaround.

Verdict: if your priorities are cheapest-possible, private, local, and no subscription, nothing here beats a phone you already own. It trades away smart alerts and night vision to be the option that never sends you a bill. Get it on Google Play, with more at superfunicular.com.

2. TP-Link Tapo C120 — the best camera you can buy with no plan

If you'd rather have a purpose-built camera and you're willing to spend once, the Tapo C120 is the one I'd point a budget-minded person to. Its MSRP is about $39.99 and it's frequently discounted to the $29–$35 range. The reason it's #2 and not further down: it does the important things without a subscription.

Pros: free local recording to a microSD card (up to 512 GB, sold separately), 2K QHD resolution, an IP66 weatherproof rating so it works indoors or out, color night vision, and free on-device person/pet/vehicle detection. There's an optional Tapo Care cloud plan, but you genuinely don't need it for recording and alerts.

Cons: it's still a cloud-account camera at heart (you set it up through the Tapo app and TP-Link's servers for remote access), you're buying a new device and a card, and the microSD is your only local backstop — lose the camera, lose the footage.

Best for: someone who wants night vision and a weatherproof body, will spend ~$40 once, and refuses a monthly plan. It's the strongest hardware answer to "no subscription."

3. Wyze Cam v4 — cheap to buy, thinner than it looks for free

The Wyze Cam v4 runs about $36 and packs 2.5K resolution, color night vision, and a spotlight — a lot of camera for the money. The catch is the free tier. Without a plan you get limited event clips and cooldowns; the smooth "record everything and get smart alerts" experience lives in Cam Plus, which is $2.99/month, and Cam Plus Annual rose from $19.99 to $29.99/year as of March 2026. You can dodge the subscription by adding a microSD card for local continuous recording, which is the move if you go this route.

Pros: genuinely cheap hardware, good image quality, color night vision, optional free local recording with a card.

Cons: the out-of-the-box free experience is thin, the best features are gated behind a plan whose annual price just went up ~50%, indoor-only for this model, and it's cloud-account based.

Best for: a bargain hunter who'll buy the camera and a microSD card and skip Cam Plus on purpose.

4. Blink Mini 2 — fine if you already live in Amazon's world

The Blink Mini 2 lists around $39.99 (and drops much lower on Prime Day). Blink's headline plans are Basic at $3.99/month or $39.99/year for one device, and Plus at $11.99/month or $119.99/year for unlimited devices. The saving grace for the subscription-averse: Blink supports local storage via a Sync Module 2 plus a USB drive, no plan required — but that's another accessory to buy.

Pros: tight Alexa/Amazon integration, small and cheap, a real no-subscription path if you add the Sync Module.

Cons: to get local storage or offline clips you're buying extra hardware, most of the polished experience assumes a plan, and it's indoor-only in this form. Deepest value only if you're already an Echo household.

Best for: people already inside the Amazon ecosystem who'll add a Sync Module to avoid the monthly fee.

5. Ring Indoor / Pan-Tilt Cam — the one that punishes a budget

Ring makes nice hardware — the indoor and Pan-Tilt cams run roughly $50–$60 — but it's the worst fit for "no monthly fee," because without a subscription a Ring camera records nothing. You get a live view and that's it; every saved clip requires a Ring Home plan: Basic at $4.99/month ($49.99/year) for one device, Standard at $10/month ($100/year), or Premium at $20/month ($200/year). There's no local-storage escape hatch the way there is with Tapo, Wyze, or Blink.

Pros: polished app, reliable, strong ecosystem if you already own a Ring doorbell.

Cons: the free experience is essentially a live window with no recording, so the "real" price is hardware plus a recurring plan, forever. For a student watching every dollar, that's the opposite of what you want.

Best for: someone already invested in Ring who's fine paying the plan. On pure budget grounds, it's last.

How to choose

Work backward from your actual constraint:

Spend as little as possible, no plan, and I have a spare phone → Background Camera RemoteStream. It's $0 and never bills you.
I'll buy one camera, want night vision and weatherproofing, and refuse a subscription → Tapo C120.
I want cheap hardware and I'll add a microSD to skip the plan → Wyze Cam v4.
I'm already an Alexa household → Blink Mini 2 with a Sync Module.
I already own Ring gear and don't mind the plan → Ring — otherwise skip it on a budget.

The through-line for 2026 is that "cheap security camera" and "no monthly fee" are two different promises, and a lot of products only make the first one. If you want to see how the software side of that plays out, here's a roundup of the best apps to turn an old Android phone into a home camera, and a closer look at what "free" actually gets you in a camera app once you read the fine print.

Bottom line

If you're furnishing a dorm or a first apartment and the budget is tight, don't start by buying a camera — start with the phone you already have. Background Camera RemoteStream records with the screen off, keeps the footage on the device, serves it to your browser over your own network, and never charges you a monthly fee, for $0. If you'd rather own dedicated hardware, buy the Tapo C120 and skip the cloud plan. Either way, the money-saving move in 2026 is the same one: refuse the second bill.

Try it: Background Camera RemoteStream on Google Play · superfunicular.com

I analyzed 3 Android camera apps. The pattern surprised me

Super Funicular — Sat, 08 Aug 2026 04:43:29 +0000

TL;DR: phone repurposing on Android works with an old phone, a screen-off recorder, and about a minute of setup -- no cloud account, no monthly fee.

The setup

What I tested

How it compares

Alfred Camera: easy to start, but the free tier is limited, shows ads, needs an account, and routes video through its cloud.
IP Webcam: powerful and fully local, but more technical to set up.
FadCam: a solid offline recorder, but it does not live-stream to another device.
Background Camera RemoteStream: free, no account, records with the screen off, and streams over your own WiFi.

Why local-only

Keeping the feed on your own network means the video never leaves your home unless you send it there. For a baby monitor, pet cam, or porch camera, that is the whole point.

Open question for the dev.to community

What is your setup for reusing old Android hardware instead of buying another subscription camera? Curious what has worked for others.

App: https://play.google.com/store/apps/details?id=com.superfunicular.digicam&referrer=utm_source%3Ddevto%26utm_medium%3Darticle%26utm_campaign%3Doldphone_camera · Built solo by Super Funicular LLC.

I tested 30 home-security apps so you don't have to. Here's what survived.

Super Funicular — Fri, 07 Aug 2026 14:41:30 +0000

TL;DR: phone repurposing on Android works with an old phone, a screen-off recorder, and about a minute of setup -- no cloud account, no monthly fee.

The setup

What I tested

How it compares

Alfred Camera: easy to start, but the free tier is limited, shows ads, needs an account, and routes video through its cloud.
IP Webcam: powerful and fully local, but more technical to set up.
FadCam: a solid offline recorder, but it does not live-stream to another device.
Background Camera RemoteStream: free, no account, records with the screen off, and streams over your own WiFi.

Why local-only

Keeping the feed on your own network means the video never leaves your home unless you send it there. For a baby monitor, pet cam, or porch camera, that is the whole point.

Open question for the dev.to community

What is your setup for reusing old Android hardware instead of buying another subscription camera? Curious what has worked for others.

App: https://play.google.com/store/apps/details?id=com.superfunicular.digicam&referrer=utm_source%3Ddevto%26utm_medium%3Darticle%26utm_campaign%3Doldphone_camera · Built solo by Super Funicular LLC.

Turn an Old Android Phone Into a Free Camera for Your Bike or Parked Car on Campus (Screen-Off, No Subscription)

Super Funicular — Fri, 07 Aug 2026 07:07:47 +0000

Ask any campus safety office what gets stolen most and the answer is almost always the same two things: bikes and stuff out of cars. A bike locked to a rack outside the library. A backpack visible on the passenger seat in a lot you can only park in between 8am and 6pm. These are the possessions that live outside your dorm, in shared space, exactly when you're stuck in a lecture hall three buildings away and can't keep an eye on them.

The usual advice is to buy a dedicated camera. But a battery outdoor cam plus the subscription to actually watch the footage is a real recurring cost on a student budget — and most of them route your video through a company's servers to do it. If you have an old Android phone in a drawer (the one you upgraded from last year), you already have most of what you need. Here's how to point it at your bike rack or parking spot and check the live view from your phone in class, without paying for a thing and without your footage leaving your control.

What you actually need

Not much:

An old Android phone. Anything from roughly the last several years with a working camera and Wi-Fi is fine. It doesn't need a SIM card.
A window or ledge with a view of the bike rack, the spot where you park, or the walkway your bike is chained along.
A charger and outlet nearby. Watching an outdoor area is a longer job than a quick indoor check, so plan to keep the phone plugged in.
Background Camera RemoteStream installed on the old phone.

The app is built around exactly this situation: it records with the screen off, keeps everything local by default, and runs a small built-in web server so you can watch the live feed from another device on the same Wi-Fi — no account, no monthly fee, no cloud.

Why "screen-off" is the whole trick

A phone propped in a window with its screen glowing all day is a dead giveaway and a battery drain. The feature that makes an old phone genuinely usable as a stakeout camera is the ability to keep capturing after the screen turns off. Android actively fights long-running background work to save battery, so this isn't something every camera app handles well — a lot of them quietly stop the moment the display sleeps.

Background Camera RemoteStream is designed to keep the camera running as a foreground service with the screen dark. That means the phone looks off, sips less power, and still sees everything. If you're curious about why this is hard and how it works under the hood, I wrote a technical companion on how an Android phone keeps recording video with the screen off. For this guide, the only thing that matters is: you can set it and leave, and the screen going dark won't stop it.

Step-by-step: watching a bike rack or parking spot

1. Position for identifying details, not just "a wide shot"

This is where a vehicle/bike watch differs from a general room camera. A blurry wide angle of a parking lot tells you a theft happened; it doesn't tell you who or gives you nothing to hand to campus police. Aim for the details that matter:

Frame so your bike (or your car's door and windows) fills a good chunk of the shot rather than sitting as a speck in the distance.
If you can, angle so the walkway or approach is in frame — you want to catch someone arriving, not just the aftermath.
Clean the window glass you're shooting through. Reflections and grime cost you more clarity than any setting.

2. Prop it steady and plug it in

Use a cheap phone stand, a stack of books, or a suction mount against the glass. The phone won't move once it's placed, so stability is a one-time setup. Run the charger to it — an outdoor watch that spans a full class block or an afternoon will outlast a battery, and a plugged-in phone can run indefinitely.

3. Start the capture and let the screen sleep

Open Background Camera RemoteStream, frame your shot, and start recording. Then let the screen turn off. The capture keeps going. Because footage is written to the phone's own storage and nothing is uploaded anywhere, you're not agreeing to let a company keep clips of everyone who walks through that lot — a real consideration when your "camera" is pointed at a public, shared space full of other students.

4. Watch the live feed from class

Here's the part that makes it useful mid-day. The app runs a small web server on the phone itself, so from your laptop or your current phone — on the same campus Wi-Fi network — you can open a browser, go to the address the app shows you, and see the live view. No app-to-cloud-to-app round trip. If you want the full walkthrough of the remote-viewing side, I covered it in streaming your Android phone's camera to another device.

One honest caveat: because the live view works over your local network, checking it from across campus depends on your school's Wi-Fi setup. Many campus networks isolate devices from each other for security, which can block device-to-device connections. Test it on your network first — start the feed, walk to a nearby building, and confirm you can still load it before you rely on it. Where remote LAN viewing isn't available, the app still records locally the whole time, so you always have the footage waiting for you when you get back.

5. If something happens, you have the footage — on your device

If you come back to a cut lock or a rifled glovebox, the recording is already saved on the phone, in your hands. You control whether it gets shared, and with whom — nothing is sitting on a third-party server waiting on a subscription payment to stay accessible. That "it's mine and it stays mine" property is the entire point of a local-first design, and it's worth understanding what the alternative costs you: what happens to your footage when a free camera app shuts down or gets acquired.

Tips that make it actually work

Do a dry run. Before you trust it with your bike, set it up, walk away, come back, and check that the recording captured what you expected at the clarity you need. Adjust the angle once and you're done.
Mind the light. Shooting toward a bright sky or a streetlight at night can blow out the exact person you want to see. Frame so the subject area is lit, not backlit.
Keep it discreet. A phone tucked at the edge of a windowsill draws less attention than one propped dead-center.
Charge, don't gamble. For anything longer than a quick check, keep it plugged in. A dead phone at 2pm means no footage for the 3pm theft.
Know your network. If campus Wi-Fi blocks the live view, treat the phone as a recorder you review later rather than a real-time monitor. Both modes are useful.

Why this beats buying a gadget

For a student, the math is simple. A dedicated outdoor camera is money up front, and the ones that let you watch remotely usually want a monthly fee and route your video through their cloud. The old phone in your drawer is free, you already own it, and with Background Camera RemoteStream it records with the screen off and keeps everything local. No account to create, no subscription to cancel at the end of the semester, no company holding your footage.

It won't replace a professionally monitored system, and it isn't magic — glass reflections, campus network rules, and battery life are all real limits you have to work around. But for the specific, common problem of "I want to keep an eye on my bike or my car while I'm stuck in class," an old Android phone and a free app cover it surprisingly well.

If you're setting up more than one watch this semester — your bike outside and your room inside, say — it's worth skimming the wider roundup of apps to turn an old Android phone into a home camera in 2026 to see how the local-only approach compares.

Background Camera RemoteStream turns a spare Android phone into a screen-off, local-only camera with a built-in web server for live viewing over your own network — no account, no subscription, no cloud.

Get it on Google Play: https://play.google.com/store/apps/details?id=com.superfunicular.digicam
Learn more: https://superfunicular.com

How an Android Phone Keeps Recording Video With the Screen Off: Foreground Services, Camera2, and the OS Fighting You (2026)

Super Funicular — Thu, 06 Aug 2026 07:08:15 +0000

"Record with the screen off" sounds like a checkbox. It is, in fact, the single hardest thing a phone-as-camera app has to do, because almost every part of modern Android is designed to stop exactly this behavior. The OS wants to kill background work, throttle CPU when the screen is dark, and reclaim the camera the moment your app stops being the visible foreground. If you want a spare Android phone to sit on a windowsill and quietly record for hours with a black screen, you are working directly against the grain of the platform's power model.

I build Background Camera RemoteStream, an app whose entire reason to exist is screen-off recording and live viewing, so I've spent a lot of time in this particular fight. This is an architecture-level walkthrough of how screen-off capture actually works on Android in 2026 — the Camera2 pieces, the foreground-service rules that changed under Android 14, and the background-execution limits you have to design around. It's aimed at the r/androiddev / Hacker News reader who wants to understand the mechanism, not a marketing tour. I'll be honest about the tradeoffs and the things the OS simply won't let you do.

Why "screen off" is the hard part, not "record"

Recording video on Android is a solved problem when your app is in the foreground with a visible preview. The camera delivers frames, you route them to an encoder, you write an MP4. The difficulty appears the instant the screen goes dark, because two independent OS subsystems change their behavior:

Process lifecycle / background execution limits. Since Android 8 (Oreo), an app that isn't visible is a background app, and background apps get their services killed, their network restricted, and their wakeups batched. A plain Service started from a backgrounded app is a candidate for termination within minutes.
Power management (Doze and App Standby). When the device is stationary with the screen off, Doze progressively defers background CPU, network, and alarms. This is great for battery and terrible for something that is supposed to keep working while nothing appears to be happening.

So the real engineering question isn't "how do I record video," it's "how do I convince the OS that this dark-screen phone is doing legitimate, user-visible work that it must not interrupt." The answer is a foreground service, and getting that right in 2026 is more involved than it used to be.

Foreground services: the contract with the OS

A foreground service is Android's mechanism for saying "the user knows this is happening, keep it alive." The visible sign is the persistent notification you can't swipe away — that notification is not decoration, it's the price of admission. In exchange for showing it, the system dramatically lowers the priority with which it will kill your process and exempts a lot of your work from the harshest background limits.

The lifecycle, in the order it has to happen:

The app starts the service (from an allowed context) and, within a few seconds, calls startForeground() with a notification.
If you don't call startForeground() in time, the system throws ForegroundServiceDidNotStartInTimeException and kills you. Slow initialization is a real trap here — you want the notification up before you touch the camera.
The service holds the process at foreground priority for as long as it runs, which is what lets capture survive the screen turning off.

This part is old and stable. What changed — and what trips up anyone porting an older app forward — is that as of Android 14 (API 34), every foreground service must declare a type.

The Android 14 foreground-service-type rule

Beginning with Android 14, you must declare an appropriate foregroundServiceType for each foreground service in your manifest, request the matching permission, and — for Play distribution — justify the type in the Play Console. For a camera app the relevant type is camera, and it comes with a specific permission:

<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_CAMERA" />
<uses-permission android:name="android.permission.CAMERA" />

<service
    android:name=".CaptureService"
    android:foregroundServiceType="camera"
    android:exported="false" />

Two consequences worth internalizing:

If you call startForeground() for a service whose type you didn't declare in the manifest, the system throws MissingForegroundServiceTypeException. There is no graceful degradation — declare it or crash.
The camera type is what lets your foreground service keep accessing the camera while running in the background. That's the whole point: without the correct FGS type, the moment the app is no longer visible, camera access is on borrowed time.

If you also record audio, the microphone type has a sharper edge: the RECORD_AUDIO runtime permission is subject to while-in-use restrictions, so you generally can't start a microphone foreground service while your app is already in the background. The practical design rule that falls out of this: start capture while you're still the visible foreground app (the user taps "start"), then let the screen go off. Trying to cold-start sensor capture from a truly backgrounded state is where things quietly stop working on modern OS versions.

Camera2 without a preview: the part people get wrong

Here's the insight that makes screen-off recording possible at all: Camera2 doesn't require a preview surface. People assume the camera needs something on screen to render into. It doesn't. Camera2 delivers frames to whatever output Surfaces you hand it in the capture session, and those surfaces don't have to be attached to any visible view.

A screen-off capture session, conceptually:

Open the camera via CameraManager.openCamera() and hold the CameraDevice.
Create your output target — commonly a MediaRecorder surface (for writing an MP4) and/or a MediaCodec/ImageReader surface (for encoding frames you'll stream). None of these is a SurfaceView or TextureView, so none of them needs the display.
Build a repeating capture request (TEMPLATE_RECORD) targeting those surfaces and set it repeating on the CameraCaptureSession.

Because there's no TextureView in the pipeline, the display can turn off and the capture session keeps producing frames into your encoder surface. The screen being dark is, from the camera pipeline's perspective, irrelevant — you were never drawing to the screen in the first place. That decoupling is the core trick, and it's why "screen off" and "recording" are not actually in tension once the architecture is right: the tension was only ever with the process lifecycle, which the foreground service solves.

The complications that remain are the real-world ones:

Lifecycle races. The camera is a single-consumer resource. If another app (or your own preview Activity being destroyed) tears down a surface while the session is live, you get CameraAccessException or a silent stall. You have to treat surface creation/teardown and session state as a careful state machine, not a set of independent callbacks.
Thermal and power reality. Continuous encode is genuinely warm work. A phone doing this on a windowsill needs to be on a charger — not because the software is inefficient, but because sustained H.264/HEVC encoding plus sensor draw is simply a real power load. This is a hardware truth, not a bug to optimize away.
OEM variance. Camera2's guaranteed capabilities are a floor, not a ceiling; different chipsets expose different INFO_SUPPORTED_HARDWARE_LEVEL and resolution/FPS combos. Defensive code queries the CameraCharacteristics and degrades gracefully rather than assuming a fixed profile.

Keeping it alive: Doze, wake locks, and battery optimizations

The foreground service earns you a lot of protection, but Doze and aggressive OEM battery managers can still interfere with a long-running session, especially over many hours. The honest state of things in 2026:

A properly typed foreground service is the primary defense, and for an actively-capturing camera service it covers most of what you need — the system treats an ongoing FGS as user-visible work.
Some deployments still request the user exempt the app from battery optimization (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS) for maximum reliability on OEMs with heavy-handed task killers. This is a permission you should ask for sparingly and explain, not sprinkle on reflexively — Play scrutinizes it.
Aggressive PARTIAL_WAKE_LOCK usage is mostly a legacy pattern here; the foreground service model is meant to replace hand-rolled wake locks for this class of work. Where the camera pipeline is active and the FGS is up, the CPU work needed to keep encoding proceeds.

The uncomfortable truth is that there is no single API that guarantees "run forever with the screen off on every phone." What you get is a stack of correct choices — right service type, notification up in time, capture started from the foreground, sensible power expectations — that together make it reliable in practice. Anyone promising more than that on the modern platform is overselling.

Where the frames go next

Recording to a local MP4 is only half of what a phone-as-camera app usually wants; the other half is seeing the feed live. That's a separate subsystem, and I wrote a full deep-dive on how the phone serves its own live camera feed over your LAN with an embedded Ktor server, including the single-latest-frame buffer that decouples capture rate from delivery rate so multiple browser viewers don't back-pressure the encoder. For watching from outside the network, the frames get muxed to RTMP instead — the screen-off YouTube Live path, end to end, is written up here. Both of those consume the exact same capture session described above; the FGS-plus-Camera2 foundation is what everything else stands on. If you want the wider tour of the hard parts of building this kind of app, the overview of recording-with-the-screen-off and streaming-over-LAN is here.

The architecture in one paragraph

Screen-off recording on Android is a foreground service of type camera (declared in the manifest with FOREGROUND_SERVICE_CAMERA, or you crash on startForeground()), started while the app is still visible so the while-in-use rules are satisfied, holding a Camera2 CameraCaptureSession whose outputs are encoder/recorder surfaces rather than on-screen views — which is precisely why the display can go dark without stopping the pipeline. Doze and OEM battery managers are handled by the FGS priority itself, occasionally supplemented by a battery-optimization exemption, and the whole thing lives on a charger because sustained encoding is real power. That's the shape of it. There's no magic — just a small number of platform contracts that all have to be honored at once, and a design that respects the camera as a single-consumer, lifecycle-sensitive resource.

Why this design is also the privacy story

There's a nice property that falls out of this architecture almost for free: because the capture pipeline writes to a local MediaRecorder surface by default, the footage lives on the device, not in a vendor cloud. The "record with the screen off" plumbing and the "your video doesn't leave your phone" guarantee are the same design decision viewed from two angles. That matters more than it sounds, because what happens to your footage when a free camera app shuts down or gets acquired is a real risk with cloud-first apps and a non-issue when the bytes never left local storage.

If you want to see the whole thing in action rather than in prose, Background Camera RemoteStream is on Google Play and there's more about the approach at superfunicular.com. And if you're building your own, the summary is short: the camera was never the hard part. The OS was.

How to Watch Your Front Porch With an Old Android Phone (Screen-Off, No Doorbell, No Subscription)

Super Funicular — Thu, 06 Aug 2026 07:05:41 +0000

Package theft is one of those problems that feels like it requires a whole subscription ecosystem to solve. Buy the doorbell, wire it up, pay the monthly fee, agree to let a company keep clips of everyone who walks past your door on their servers. It's a lot of setup — and recurring cost — for what is really a simple question: did someone take the box off my porch, and can I see who?

If you have an old Android phone sitting in a drawer, you can answer that question today for free. Here's a practical, honest guide to pointing a spare phone at your front door — recording with the screen off, keeping the footage on the device, and checking the view from your laptop or your current phone — with no doorbell hardware, no account, and no monthly bill. The app I'll use is Background Camera RemoteStream, which I build, so I'll be straight with you about where it fits and where a $150 doorbell still wins.

What this setup does — and what it doesn't

Before you prop a phone against a window, set expectations.

What you get:

Records video with the phone's screen off, so it looks like a dead phone on a sill instead of a glowing display burning all day.
Keeps footage in local, on-device storage — nothing uploads to a cloud account by default, so you're not handing clips of your street to anyone.
Runs a small built-in web server so you can open the live view in a browser on another device on the same Wi-Fi — no second app to install.
Can push an unlisted YouTube Live stream for when you want to watch from outside the house.
Costs $0 with no account, no subscription, and no cloud.

What it doesn't do — plan around this:

No motion alerts and no AI person-detection. It records or streams; it will not ping your phone the moment someone steps onto the porch. If "text me when a person appears" is the whole point for you, a dedicated doorbell does that and this doesn't.
No night vision. A phone camera can't see a dark porch the way a doorbell's infrared can. If most of your deliveries or your worries happen after dark, leave a porch light on — I wrote an honest guide to why old phones can't see in the dark that explains the physics and the workarounds.
It is not weatherproof. This is the big one for a porch. A phone left outside will cook in the sun, fog up, or die in the rain. The whole trick here is to shoot from inside, through a window, pointed out at the porch — never to leave the phone exposed.
No two-way audio, no siren, no doorbell button. It's a camera, not an intercom.
It must stay on power. Continuous recording or streaming drains a battery in a couple of hours, so treat it as a device that lives on a charger.

If those tradeoffs are fine — and for "just show me who took the box" they usually are — here's the setup.

Step 1: Find the window and the angle

The single most important decision is placement, because you're working around the no-weatherproofing rule. Find a window that looks out onto your porch or the spot where deliveries land: a front window, a sidelight next to the door, a glass storm door. You want the phone inside, glass between it and the weather, lens close to the pane.

Two things to get right:

Kill the reflections. Glass throws back whatever light is behind the phone. Turn off the lights in that room, close the curtains around the phone if you can, and press the lens as close to the glass as possible. A dark room behind the camera and a lit porch in front is the ideal.
Frame the drop zone, not the whole street. Point it at where boxes actually land and where a person would stand to grab one. A tighter frame on your own doorstep gives you a usable, identifiable image and keeps you from filming the entire sidewalk (more on why that matters in the consent section).

A cheap phone stand, a suction mount, or a stack of books on the windowsill is all the hardware you need. Put it near an outlet — remember, it lives on the charger.

Step 2: Install the app and choose local storage

Install Background Camera RemoteStream from Google Play on the spare phone. If you're repurposing an old daily driver, sign out of your accounts or wipe it first.

Pick the rear camera — it's sharper than the front and better for reading a face or a jacket at porch distance. If your main goal is evidence you can review later rather than a live window, use the local recording mode so the files are saved on the device. That "the footage is just on my own phone" reality is genuinely reassuring compared to a cloud plan, and it's worth understanding what happens to your footage when a free camera app shuts down or gets acquired before you trust any app with the job — with local-only storage, there's no company account for your clips to disappear into.

Step 3: Decide how you'll watch

There are two ways to see the feed, and they solve different problems.

Option A — Local browser view (same Wi-Fi). The app runs a tiny web server on the phone. On your laptop or current phone, open the address it shows you and the live view loads right in the browser. Nothing leaves your home network. This is the most private option and it's perfect for glancing at the porch while you're home — "was that the delivery?" without getting up.

Option B — Unlisted YouTube Live. For checking from away from home — the office, the store, a trip — the app can stream to an unlisted YouTube Live link that only you have. The honest tradeoff: this is the one mode where your video leaves the phone and travels over Google's servers, so it's a different privacy model than the local-only view, and there are a few seconds of latency. If you want the details, I walk through the screen-off YouTube Live path end to end here.

A sensible default: local browser view when you're home, unlisted YouTube Live when you're out and expecting a delivery.

Step 4: Start it recording with the screen off

In the app, choose the rear camera, start the capture, and lock the phone. Recording keeps running with the screen dark thanks to a foreground service — you'll see a small notification so you always know it's on. Prop it at the window on its charger, and the core of it is done. Because the screen is off, the phone looks inert; because it's plugged in, it won't quietly die three hours before the box arrives.

Step 5: Test it before you trust it

Do a dry run before the afternoon you're actually waiting on a package:

Start the capture, walk out to the porch, and stand where a delivery driver would. Then check your view — local browser or YouTube — and see whether you can actually make out a face and read the scene.
Look at the image at the time of day you care about. If your deliveries land at dusk, test at dusk, and turn the porch light on to see if it's enough.
Check the reflection. If you see the room behind the phone more than the porch, darken the room or reposition against the glass.
Confirm the notification stays up and the phone keeps recording after the screen has been off for a while.

Tuning the angle and the lighting on a calm day beats discovering the frame was useless right after your box walked off.

A note on consent and the law

Pointing a camera at your own porch is normal, but a window camera facing a shared entryway or the street can catch your neighbors and passersby, and the rules vary by where you live. A few sensible habits: frame your own doorstep rather than the whole block, be mindful of a neighbor's door or windows, and know that audio recording is more tightly regulated than video in many places — this app is video-only for the live view, which keeps things simpler. If you're in an apartment or HOA, a quick check of your building's policy saves headaches later. None of this is legal advice; it's just the courtesy-and-common-sense version.

When you should buy the doorbell instead

I'd rather you set this up knowing the edges. Buy a real doorbell camera if you need instant motion alerts, reliable night vision, a weatherproof unit mounted right at the door, or a doorbell button and two-way talk so you can tell the driver where to leave the box. Those are real features and a phone in a window doesn't replace them.

But if what you actually want is a free, private, no-subscription way to see who's on your porch and to have footage on your own device when something goes missing — an old Android phone and a window do the job today, for nothing. If you're weighing the options, I keep a roundup of the best ways to turn an old phone into a home camera in 2026 that lays out the alternatives honestly.

Grab Background Camera RemoteStream on Google Play, or read more about the approach at superfunicular.com. Your next delivery is a good excuse to test it.

Turn an old Android phone into a screen-off security camera (no cloud, LAN-only)

Super Funicular — Wed, 05 Aug 2026 04:39:40 +0000

Old Android phones pile up in drawers. Instead of letting one die there, you can point it at a doorway, a driveway, or a pet's favorite corner and let it record. Here is a straightforward, cloud-free way to do it, and the reasoning behind each choice.

Why an old phone is a good camera

A three-year-old phone still has a decent sensor, Wi-Fi, and a battery. The two things that usually get in the way are the screen (it drains power and announces that the phone is recording) and cloud services (a monthly fee plus your footage on someone else's server). Solve those two and an old handset becomes a capable local camera.

The core trick: recording with the screen off

The feature that makes this practical is screen-off recording. The camera keeps capturing while the display is fully dark, so the phone sips power instead of gulping it and does not glow in a dark room. On Android you get this either through a background-camera recorder app or, on some OEM camera apps, a "screen off" toggle buried in settings.

Setup in about a minute

Mount the old phone where you want coverage. A cheap gooseneck clamp or even a stack of books works.
Keep it on a charger. Continuous recording will outrun any battery, so treat it as a wired device.
Install a background-camera app that supports screen-off capture and, ideally, live viewing from a second device over your local network.
Start recording, turn the screen off, and confirm from your main phone or laptop that the stream or the saved clips are coming through.

Local network vs cloud

If you only need to review footage later, saving clips to the phone's own storage is enough. If you want to watch a live feed, look for an app that streams over your LAN so the video never leaves your home network. That keeps latency low and keeps a subscription out of the picture. The trade-off is range: LAN-only means you watch from the same network, not from anywhere in the world, unless you add your own VPN.

How the common options compare

Option	Local-only viewing	Cost	Notes
Alfred Camera (free tier)	No, cloud-based	Free tier limited to 2 cameras; paid ~$35.99/yr	Cloud relay, easy setup
AtHome Camera	Partial	Free with paid tiers	720p on free tier
IP Webcam	Yes, LAN	Free	Local streaming, more manual setup
WardenCam	Yes	Free/paid	Effectively unmaintained since mid-2023
Background Camera RemoteStream	Yes, LAN live view	Free	Phone-as-camera, screen-off recording, live remote view on your own network

Figures reflect what these apps advertised as of mid-2026; check each store listing before you rely on a number.

What to watch out for

Heat is the real enemy of a phone that records all day on a charger. Give it airflow and avoid sealed enclosures in direct sun. Also confirm your recorder actually keeps running when the screen sleeps; some phones aggressively kill background apps, so you may need to exclude the app from battery optimization.

Try it

The app I build for this is Background Camera RemoteStream. It does screen-off recording and live viewing over your local network, with no cloud account and no per-camera fee.

Play Store: https://play.google.com/store/apps/details?id=com.superfunicular.digicam
More: https://superfunicular.com

If you have a spare Android phone, this is a 60-second project that beats buying another gadget.