DEV Community: Super Funicular

RedHook malware turns on your phone's Wireless Debugging to stream your screen — and it never touches the consent dialog

Super Funicular — Tue, 21 Jul 2026 08:05:43 +0000

On July 9, Group-IB published an analysis of a new build of the Android trojan RedHook, and it contains a first: the malware turns on Wireless Debugging on the victim's own phone and uses it to give itself shell-level privileges — no PC, no USB cable, no root, no exploit. (Group-IB's writeup; BleepingComputer's summary.)

The part that should interest anyone who builds or uses a camera app is buried in the capability list. RedHook streams the victim's screen. And once it holds shell privileges, it streams over RTMP, capturing the screen directly — bypassing the MediaProjection API and its mandatory consent dialog.

That is worth sitting with. The consent dialog is the thing Android shows you so that screen capture cannot happen silently. RedHook does not defeat it. It goes around it.

What actually happens

There is no clever zero-day here, which is what makes it worth writing about. The chain is entirely made of legitimate parts:

A victim gets a phone call or a message from someone impersonating a bank or a government office, and is walked to a site built to look like the Play Store.
They sideload the APK.
The app runs a guided walkthrough that convinces them to enable the Accessibility Service, framed as a necessary step to "enable full features."
With Accessibility, the malware drives the Settings UI itself — taps the build number seven times to unlock Developer Options, opens Wireless Debugging, hits "Pair device with pairing code," and reads the pairing code off the screen. A full-screen overlay hides all of it.
It embeds an ADB client, connects to the phone's own ADB daemon over loopback (127.0.0.1), and comes up as uid 2000.

Step 5 borrows from Shizuku, the well-known open-source tool that enthusiasts use to grant apps elevated permissions without rooting. Group-IB's phrasing is precise: "There is no exploit here, 'merely' turning a debugging interface into a path to shell-level privileges."

From uid 2000 the app can grant itself runtime permissions, run shell commands, write to Settings.Secure, silently install and uninstall packages, and capture low-level touch events. The current build supports 53 distinct server-issued commands. It also holds on hard: a 1×1-pixel activity to look like a foreground process when the screen is off, silent audio via MediaSession, a WakeLock, two services in separate processes that resurrect each other via bindService() with BIND_AUTO_CREATE, an oom_score_adj of −1000, and a BOOT_COMPLETED receiver that re-enables Wireless ADB and restores the privileged helper within seconds of power-on.

Active campaigns are targeting Vietnam and Indonesia. The technique is not regional.

Why this matters beyond banking trojans

The instinct after a story like this is to distrust the capability. Screen streaming is scary, so screen streaming is bad. Remote camera access is scary, so remote camera access is bad.

That reading is wrong, and following it makes you less safe rather than more.

RedHook is not dangerous because it streams. It is dangerous because it acquired unaccountable privilege — permission that the user cannot see, did not knowingly grant, and cannot easily revoke. The streaming is a symptom. The disease is a permission model that got escalated behind an overlay.

There are entirely legitimate reasons to want a phone to send video somewhere while its screen is off: watching a pet, keeping an eye on a doorway, running a second-angle camera, monitoring a workshop. The question is never does this app stream? It is who can start it, who can see it, and where does it go?

What to actually check on your phone

Independent of any product, do these now. They take under two minutes.

Settings → System → Developer options → Wireless debugging. If you did not deliberately turn this on, turn it off. If Developer Options is enabled and you never enabled it, that is a signal in itself.
Settings → Accessibility. Read the list of apps with the Accessibility Service. This is the single most abused permission on Android. A camera app, a flashlight, a file manager, a game — none of these have any business here. Accessibility exists for screen readers and switch access.
Check what can install packages. Settings → Apps → Special app access → Install unknown apps.
Sideload nothing you did not go looking for. Every RedHook infection starts with an APK from a site that looks like the Play Store but is not.

Group-IB's own end-user guidance leads with the same point: be on extreme alert when an application requests the Accessibility Service.

The standard a camera app should be held to

We build Background Camera RemoteStream, an Android app for recording and live-streaming from a phone with the screen off. So we have an obvious interest here, and you should read the next paragraph with that in mind.

The honest version of our pitch is not "trust us." It is that the design choices worth demanding are checkable ones:

Footage stays on the device. Recordings are stored locally. There is no cloud pipeline that has to be trusted, because there is no cloud pipeline.
No account. No sign-up means no credential to phish, no server-side profile, no password reuse blast radius.
Distribution through Google Play only. If you are ever asked to sideload our APK from a site that looks like the Play Store, that site is not us.
Streaming goes where you point it. YouTube Live is your own destination on your own account, not an intermediary we operate.

None of that is exotic. It is the baseline, and the useful takeaway from RedHook is that you should ask any camera app on your phone to meet it — ours included. We wrote more about the pattern across the category in an analysis of nine Android camera apps, and about the no-cloud approach in this baby monitor walkthrough.

The uncomfortable part for developers

Shizuku is a good tool. Wireless ADB is a good feature. Accessibility is load-bearing for people who genuinely need it. RedHook did not break any of them — it assembled them.

That is the durable lesson. The Android security model increasingly depends on a user correctly evaluating a permission prompt while an attacker is on the phone with them, actively coaching them through it. Consent dialogs are a real protection and RedHook still routed around the screen-capture one by climbing to a privilege level where the dialog does not apply.

Treat Accessibility and Wireless Debugging as high-value abuse vectors, as Group-IB puts it. And if you ship an app that touches the camera, the microphone, or the screen, assume your users have just read a story like this one — and make the permissions you request small enough to defend line by line.

Background Camera RemoteStream — background recording and live streaming from an Android phone, local storage, no account required.
Google Play · superfunicular.com

Source: RedHook Returns with a Dangerous Upgrade, Group-IB, July 9, 2026.

Can an Old Android Phone See in the Dark? An Honest Guide to Overnight Recording (2026)

Super Funicular — Tue, 21 Jul 2026 07:08:03 +0000

Short answer (updated July 2026): No. An old Android phone cannot do infrared "night vision," and no app can give it that — the IR-cut filter sitting on the sensor is physically permanent. But you almost certainly don't need IR. What you need is a small amount of visible light in the room, and then a phone will record a perfectly usable overnight video with its screen off. This guide covers what actually happens in the dark, the numbers that matter, and the five-minute setup that makes it work.

Every week someone asks a version of the same question: I've got an old Pixel in a drawer, I want to point it at the back door overnight — will it see anything?

The honest answer has two halves, and most articles only tell you the flattering one. So here's both.

The half nobody wants to hear: your phone will never have night vision

A dedicated $30 security camera "sees in the dark" using a trick that has nothing to do with a good sensor. It floods the room with near-infrared light — invisible to you, bright as day to the sensor — from a ring of IR LEDs, usually at 850nm or 940nm. Then it captures the reflection.

For that to work, the camera has to be able to see infrared. And by default, camera sensors see far too much of it — enough that daytime colour goes strange and washed out. So every camera ships with an IR-cut filter between the lens and the sensor to block it.

Here's the difference that decides everything:

A security camera has a mechanical IR-cut filter. It's on a tiny switching mechanism. In daylight it swings into place for accurate colour; at night it swings out, the sensor becomes IR-sensitive, the LEDs fire, and you get that grey-green night image.
A phone has a permanent IR-cut filter. It's bonded into the camera stack. It does not move. It cannot be switched off in software.

This is why every "night vision camera" app on the Play Store is, at best, a green colour filter over a noisy image. There is no software path to IR on a phone, and any app claiming otherwise is selling you a tint. We don't ship a night-vision mode in Background Camera RemoteStream for exactly this reason — it would be a lie rendered in green.

You can test the filter yourself in ten seconds: point a TV remote at your phone's camera and press a button. On most phones you'll see a faint purple flicker on the front camera (whose filter is often weaker) and little or nothing on the main rear camera. That flicker is the small amount of IR leaking past the filter. It is nowhere near enough to light a room.

The other half nobody mentions: "night mode" doesn't come with you into video

The second assumption is that modern computational photography rescues this. Your phone takes astonishing dark photos, so surely it records astonishing dark video?

No — and the reason is structural.

Night mode works by holding the shutter open longer, pushing ISO, and then capturing and merging a burst of frames to average away noise. That is a fundamentally still-photo technique. It spends a second or two of real time to produce one frame. Video needs thirty of those every second, in real time, while things are moving. Stacked frames of a moving subject produce ghosting and smear, which is worse than the noise you were trying to remove.

The exceptions prove the point. Google's Night Sight Video on the Pixel 8 Pro and Pixel 9 series works via Video Boost — which uploads your footage to Google's servers and replaces the local file with the processed version hours later. It requires Google Photos and cloud backup to function at all. (Google has been moving this on-device for the Pixel 11's Ultra Low Light mode, which won't need a connection — but that's one flagship line, not "phones.")

That's worth sitting with if privacy is why you're reading this. The single best low-light video feature on Android in 2026 works by sending the video off the device. If you're setting up an overnight camera specifically so footage doesn't leave your house, the marquee night-video feature is the thing you'd have to turn off.

The numbers that actually decide whether this works

Skip the marketing and look at illumination, measured in lux.

Scene	Roughly	What a phone does with it
Overcast daylight indoors, near a window	~1,000+ lux	Clean, easy, full frame rate
Normal lit living room, lamps on	~100–300 lux	Fine. This is the target.
Single dim lamp, or a hallway light two rooms away	~30 lux	The edge — single-frame capture starts to struggle here
Heavy dusk / TV-glow only	~3 lux	Only survivable with frame-merging, which video doesn't get
Genuinely dark room, curtains shut	~0–0.3 lux	Black. No app fixes this.

Research on mobile capture puts the single-image struggle point at around 30 lux, with merge-based techniques extending usable capture down to about 3 lux and needing further modification below that. Video sits on the harder side of that line, because it can't merge freely.

Meanwhile a typical surveillance camera spec quotes something like 2 lux as its minimum in colour day mode — and then leans on IR below that. So the gap between a phone and a dedicated camera in a lit room is much smaller than the marketing suggests. The gap in a pitch-black room is total.

Which points straight at the fix.

The fix is a lamp, not an app

The entire problem collapses if you put light in the room. Not floodlight — a normal amount.

Option 1: leave one lamp on. A single LED bulb in the room you're monitoring puts you comfortably in the 100+ lux band. A 9W LED costs pennies a night to run and gets you full-colour footage with a readable frame rate. Colour, incidentally, is worth more than you'd think — "grey jacket" is a far weaker description than "red jacket."

Option 2: a motion-activated light. A cheap PIR-triggered lamp or a smart bulb on a motion routine. The room is dark until something moves, then it isn't. This is what actually matters anyway: you don't need footage of an empty dark room, you need footage of the moment something happened. It also means you're not lighting the house all night.

Option 3: put the camera where the light already is. A phone facing a window catches streetlight and headlights. A phone in a hallway catches the light bleeding under doors. Front porches usually already have a light on a switch.

Option 4: accept a lower frame rate. If you're recording a driveway rather than a person's face, a darker, grainier clip that establishes a car arrived at 2:14am is still evidence. Perfect is not the bar.

What does not work: buying a standalone IR illuminator and pointing it at the room. The phone can't see it. You'd be lighting the room for a camera that has been deliberately blinded to that wavelength. This is the single most common wasted purchase in this whole category.

The five-minute overnight setup

Once you've solved light, the rest is straightforward. Here's the actual sequence:

Plug it in. Overnight recording on battery is a losing game — you'll wake up to a dead phone and four hours of footage. Permanent power, always.
Pick the spot before you mount anything. Wedge the phone where you think you want it, record two minutes, and watch it back. Framing mistakes are invisible on a 6-inch screen at eye level and glaring on playback.
Turn on the lamp you chose above, and re-check that clip in the actual lighting you'll be using — not with the ceiling light on.
Start the recording and let the screen go off. This is the whole reason to use a purpose-built app rather than the stock camera: the stock app stops when the screen does. Background Camera RemoteStream keeps recording with the display off via a foreground service, which also means a black phone on a shelf isn't advertising itself as a camera. The full mechanics of that path are covered in the screen-off recording and streaming walkthrough.
Decide how you'll watch it. Two options, and they're different jobs. On the same Wi-Fi, the app's built-in web server lets you open a browser on a laptop and watch the live view without installing anything — that's the browser-over-your-own-network setup. From outside the house, the unlisted YouTube Live path is the one that reaches you anywhere.
Do the storage maths before you commit. This is the constraint that actually bites on overnight jobs — eight hours a night adds up fast, and a full disk ends a recording just as thoroughly as a dead battery. There's a full breakdown in the storage and retention piece, but the short version: budget your nights against free space before night one, not after.

Being straight with you about the tradeoffs

An old phone is genuinely good at this, and genuinely worse at some things. Both are true:

Where the phone wins: it costs nothing, footage stays on the device with no account and no subscription, there's no vendor who can change the price or shut the service down, and you can watch it in a browser on your own network or stream it out when you choose to.

Where a dedicated camera wins: true IR night vision in a pitch-black room, weatherproofing for outdoors, motion alerts and AI person-detection, and a mount designed for the job. We don't do motion alerts or object detection — if you need to be notified, rather than to review, a purpose-built camera with a subscription is the honest recommendation, and we've said so before in the honest cloud-cam replacement comparison.

The overnight use case sits right on that line, which is why it deserves a straight answer rather than a pitch.

FAQ

Can any Android app give my phone infrared night vision?

No. The IR-cut filter is a physical layer bonded into the camera module and cannot be disabled in software. Apps advertising "night vision" apply a green or amplified tint to an already-dark image.

Will an external IR illuminator help my phone camera see at night?

No — that's the most common mistake here. The phone's filter blocks the exact wavelengths the illuminator emits. Spend the money on a normal LED bulb or a motion-triggered light instead.

How much light does a phone actually need to record usable video?

A normally lit room (roughly 100–300 lux — one or two lamps) is comfortable. Around 30 lux it gets difficult, and below a few lux it isn't usable for video regardless of the phone.

Does night mode work while recording video?

Generally not. Night mode merges a burst of still frames, which video can't do in real time without ghosting moving subjects. Pixel's Night Sight Video is the notable exception, and on the 8 Pro and 9 series it works by uploading footage to Google's servers for processing.

Can I record overnight with the screen off?

Yes — that's the core of what Background Camera RemoteStream does. Recording continues via a foreground service with the display off, footage is stored locally on the device, and you can view the live feed in a browser on the same network or via an unlisted YouTube Live stream from anywhere.

Is it better to leave a light on all night or use a motion light?

A motion light is usually the better answer. You rarely need footage of an empty dark room — you need the moment something moved, and that's exactly when the light fires.

Try it: Background Camera RemoteStream on Google Play — record with the screen off, keep footage local, watch it in a browser on your own network. More at superfunicular.com.

Related: if the room in question has a cot in it rather than a back door, the private baby-monitor setup covers the same overnight problem with different priorities.

Most people get subscription home security wrong. Here's what actually works.

Super Funicular — Sun, 19 Jul 2026 15:37:22 +0000

You do not have a security problem. You have a "can I see that room right now?" problem. Those are different products, and the market only sells you the expensive one.

Every consumer camera pitch starts at the same place: a doorbell, a monthly plan, a cloud account, an app that wants your address. That bundle is designed for a household that wants evidence after an incident.

Most people asking for a camera do not want evidence. They want a live look. Is the dog on the couch. Did the contractor actually show up. Is the back door shut. That is a streaming problem, and streaming is the one thing the subscription bundle handles worst — it is the part they meter, throttle, and put behind the higher tier.

The design problem

Strip it down. To answer "what is happening in that room right now" from somewhere else, you need exactly four things:

A camera sensor in the room.
Power to it.
A network path out.
Something on the other end that can watch.

An old Android phone in a drawer is items 1, 2 and 3 in one object. It has a decent sensor, a charge port, and a radio that already knows your Wi-Fi. The hardware problem was solved years ago and then thrown in a drawer.

What is not solved is the software assumption underneath it: Android is built for a phone you are holding. Screen on, app in front, user present. The moment a phone becomes a fixed camera, every one of those assumptions is wrong — and that is where the actual engineering lives.

What actually has to be built

The interesting constraints are not "record video." They are:

Screen off. A phone propped on a shelf with its display burning for six hours is a heat problem, a battery problem, and a "that is obviously a camera" problem. Recording and streaming have to survive the screen going dark, which means fighting the OS's assumption that a dark screen means nobody cares.

Aggressive power management. Android will happily suspend a long-running background process to save battery. A camera that quietly stops after 40 minutes is worse than no camera, because you believed it was running.

A route out that is not a private LAN. This is the honest split between the DIY options. Plenty of tools will stream to another device on the same Wi-Fi. That covers the nursery down the hall. It does not cover the thing people actually ask for, which is watching from the office, the airport, the other country. Getting a stream off the local network without shipping every frame through someone's paid cloud is the hard part — and pushing to a destination you already own, like a private YouTube Live stream, is one of the few routes that does not reinvent NAT traversal badly.

Not looking like a camera. Half the practical value of a repurposed phone is that it is a phone. That only holds if the screen is off and nothing announces itself.

Where each option actually lands

Subscription cameras — best-in-class if what you want is retained footage, motion alerts and an ecosystem. You are renting hardware and paying for storage of moments you will almost certainly never watch.
LAN-only DIY apps — genuinely good, free, and open. Also genuinely limited to your own network unless you are willing to run a VPN or punch holes in your router.
A repurposed phone with a screen-off recorder that can broadcast out — no new hardware, no monthly line item, works from outside the house. The tradeoff is real: you are responsible for placement, power, and pointing it somewhere useful.

The wrong version of this argument is "subscriptions are a scam." They are not. The wrong default is assuming the subscription is the only shape this can take, when the majority of people asking are trying to answer a question that costs nothing to answer.

Where I land

I build Background Camera RemoteStream — an Android app for exactly this: an old phone, screen off, recording or broadcasting out. So take the framing above as coming from someone with a side in it. The design problem stands on its own either way.

Open question for the dev.to community

For those of you who have wired up a home camera setup — did you end up on a subscription product, a LAN-only stack, or something self-hosted? And what was the thing that actually decided it: cost, latency, remote access, or just not wanting one more account?

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

This week on @Digital_Nomad_Media — 25 new clips (2026-W29)

Super Funicular — Sun, 19 Jul 2026 14:02:30 +0000

Quick weekly digest from my YouTube channel — every clip below is fresh in the last 7 days.

Rough Tough Dig Nomad ✌️🤠

Never give up.

28s

Swim day for the dogs

51s

Stocking up for Stockings ✌️🎅

29s

Adventure Dog

65s

Good ole Baptist Health Care ⚕️

32s

Wanna go Pee? Lady the PeeBull

21s

The life of a Nomad ✌️🤠

25s

Dashing thru the snow ✌️🤠

59s

Happy Holidays

19s

Wanna?

15s

Not on her watch!

62s

Puppy play time ✌️🤠

36s

From Shitzville to Japan ✌️🤠

40s

Can you take a hint? ✌️🤠

13s

Will 2021 come around again? ✌️🤠

58s

Your A.I. assistant one day in the future 🤠✌️

13s

Wiggle it a little bit

69s

Mission afailedlished! ✌️🤠

31s

I was attacked by a blizzard on my way over here.....i barely survived. ✌️😶‍🌫️

35s

Attack of the Sasquatch ✌️🤠

63s

We're OPEN! (Kind of)

36s

To be euthanized?

21s

Our Lake House. Part 1 ✌️🤠

22s

Taking Marchello to War. ✌️🤠

41s

I also built an app — DigiCam

I also made DigiCam, listed as Background Camera RemoteStream on Google Play. It's the world's first screen-off YouTube live streaming app: stream live with the screen off for ~10× the battery life, plus background recording, remote web console control, file-based YouTube Live, and playlists. Privacy-first, all local storage. Free with ads or Pro for the full feature set:
https://play.google.com/store/apps/details?id=com.superfunicular.digicam

Watch the full channel: @Digital_Nomad_Media

Tags: #SuperFunicular #DigiCam #DigiNomad #YouTubeShorts #ContentCreator #ladythepitbull #TrixieTheTerrible #cutedog

I Analyzed 9 Android Camera Apps. The Pattern Surprised Me

Super Funicular — Sun, 19 Jul 2026 04:42:14 +0000

I went through nine Android camera apps back to back — the ones that keep coming up when people ask "can I turn my old phone into a camera?" The pattern that fell out wasn't about features. It was about what each app assumes your phone is FOR.

Every single one of these apps puts your phone into one of three boxes:

An accessory for your PC — the phone is a webcam, the computer is the product.
A sensor for a vendor's cloud — the phone captures, their servers (and their meter) decide what you see.
A camera locked to your living room — local recording or LAN streaming, useless the moment you leave the house.

Almost nothing treats the phone as what it actually is: a complete, standalone camera + computer + radio that can capture and publish video on its own.

Here's the list.

The 9 apps

1. Background Camera RemoteStream (the gap-filler — and yes, it's mine)

Records with the screen completely off and streams live to YouTube Live directly from the phone — so "remote viewing" works from anywhere with zero vendor cloud in the middle and no subscription meter. Point an old phone at your driveway, turn the screen off, watch from another continent. Disclosure: I built this one, specifically because nothing below covered this combination. Play Store · superfunicular.com

2. IP Webcam

The veteran. Turns the phone into a network camera with a browser-viewable stream. Rock solid — but the stream lives on your LAN. Watching from outside your network means port forwarding, dynamic DNS, or a VPN. Box 3.

3. AlfredCamera

The polished "old phone as security cam" pairing app. Slick, but your video rides through their cloud, and the free tier was recently trimmed to two cameras — the meter is the business model. Box 2.

4. AtHome Camera

Same shape as Alfred: camera phone + viewer app + an account in the middle. Works, but you're renting access to your own video feed. Box 2.

5. DroidCam

Excellent at what it does — turning your phone into a webcam for your PC. But the phone is demoted to a peripheral; without the desktop client it does nothing. Box 1.

6. Iriun Webcam

DroidCam's high-resolution sibling. Same deal: phone-as-webcam, desktop app required, camera has no life of its own. Box 1.

7. Haven

The Guardian Project's open-source room monitor — genuinely clever use of all the phone's sensors, built with Snowden's involvement. But development has been quiet for years, and it's a motion-evidence logger more than a live camera. Box 3, with history.

8. FadCam

Open-source background video recorder — one of the few others that takes screen-off capture seriously. But it's distributed off the Play Store (sideload from GitHub), and its live streaming is LAN-only HLS: fine on your sofa, gone when you leave the house. Box 3.

9. Quick Video Recorder

Background and scheduled recording, simple and quiet. But recording is where it ends — there's no remote viewing story at all. Box 3.

The pattern

Two apps make your phone a PC accessory. Two route your video through a subscription cloud. Four keep it trapped in your house. The one thing an old Android phone is perfectly positioned to be — a self-contained camera you can check from anywhere, with nobody's server in between — is the combination almost everyone skips.

I think that's a design-culture artifact, not a technical constraint. The hardware has been capable of this for a decade. But "phone streams directly to a service you control" has no recurring revenue attached, so the ecosystem kept building meters instead.

Open question

For those who've wired up old phones as cameras: did you end up in box 1, 2, or 3 — and did you get remote viewing working without a vendor cloud? Curious what stacks people actually run. I'll answer every comment.

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.

Background Camera RemoteStream vs FadCam vs Quick Video Recorder: which actually works as a work-from-home camera?

Super Funicular — Sun, 19 Jul 2026 02:42:35 +0000

TL;DR: an old Android phone plus a screen-off recorder app makes a perfectly good work-from-home camera — watch the front door for deliveries, keep an eye on a pet, or check the home office while you're at a co-working space. Three apps get recommended for this constantly. They solve three different problems. Here's an honest breakdown — with a disclosure up front: I build the first one.

The use case

"Work-from-home camera" here means: a spare phone pointed at something you care about (door, desk, pet, kid's playroom) that keeps recording or streaming with the screen off, so it doesn't glow like a beacon or burn its panel in, and that you can check remotely without buying hardware or a cloud subscription.

The three apps that come up: Background Camera RemoteStream (mine), FadCam (open source), and Quick Video Recorder (GeniusTools Labs).

What each one actually is

Background Camera RemoteStream — screen-off recording, local-only storage, a built-in web server so you can view the camera from any browser on your Wi-Fi, and an unlisted YouTube Live option when you need to check in from outside the house. No account, no cloud storage, no subscription.

FadCam — open-source, ad-free, no tracking. Screen-off recording, live streaming over your local network with remote control via a web UI, and a clever "Privacy Black Mode." Free with an optional one-time Pro tier. Genuinely good software — the catch is distribution: it's on F-Droid and GitHub, not the Play Store, so installing means sideloading. And its streaming is LAN-only — no off-network path.

Quick Video Recorder — 4.7★ with 29k+ reviews and 1M+ installs, so it's the one your search results push first. Per its Play listing: background recording with the preview off, scheduled recordings, front/back camera, SD-card storage, dash-cam mode. It's a recorder, though — there's no remote viewing or streaming at all. It's ad-supported with in-app purchases, and top reviews mention ads gating basic actions and a default recording time limit that surprises people mid-recording.

The comparison that matters

	Background Camera RemoteStream	FadCam	Quick Video Recorder
Screen-off recording	✅	✅	✅
View live from another device (LAN)	✅ browser	✅ web UI	❌
View live from outside your network	✅ unlisted YouTube Live	❌ LAN only	❌
Install path	Play Store	F-Droid / GitHub sideload	Play Store
Cloud account required	❌	❌	❌
Ads	❌	❌	✅
Pricing	free + one-time Pro	free + one-time Pro	free + IAP/subscription

So which one?

You want a check-in camera you can open from anywhere, installed in one tap: Background Camera RemoteStream. The YouTube Live path is the differentiator — an unlisted stream you can open from a laptop at a café.
You're comfortable sideloading and only need to check it from inside the house: FadCam is an excellent FOSS pick, and I mean that without an asterisk.
You just want scheduled local recordings and don't care about remote viewing: Quick Video Recorder does that, if you can live with the ads.

The honest framing: none of these are "hidden camera" tools — point them at your own property, and check your local recording-consent laws for anything with audio.

Open question for the dev.to community

For those who've deployed an old phone as a permanent camera: what's your battery strategy? Straight-to-charger 24/7, a smart plug cycling 40–80%, or something better? That's the part no app solves for you.

$200 Amazon Ring vs $0 old phone: same features?

Super Funicular — Sun, 19 Jul 2026 00:42:02 +0000

TL;DR: a $200 outdoor camera is really a subscription funnel with a lens on it. The phone in your drawer already has better hardware for the job — the only hard part is software, and that part is solved.

The $200 side of the ledger

Current Ring pricing, checked today: the Spotlight Cam (2nd gen, 2K) is $169.99 and the Spotlight Cam Pro is about $229. Neither number is the real price. Without a plan you get live view only — recorded clip history sits behind Ring Home at $4.99/mo (Basic) to $9.99/mo (Standard). So the cheapest usable porch-cam setup is roughly $230 in year one, and the meter keeps running after that.

None of this is because clip storage is expensive. It's because recurring revenue is the point and the camera is the acquisition cost. Several big consumer camera apps have been tightening free tiers lately for exactly this reason.

The $0 side of the ledger

An old Android phone — the one in your drawer right now — ships with:

a camera that outclasses most sub-$100 security cams in daylight
Wi-Fi, a full networking stack, and local storage
a battery, which is a built-in UPS that Ring charges extra to approximate
a general-purpose OS you can point at any streaming endpoint you like

Feature-by-feature (live view, recording, remote viewing, motion coverage of one fixed zone), the overlap with a $200 camera is uncomfortably large.

The actual hard part

Here's the honest engineering reason everyone doesn't already do this: Android really does not want to be a security camera. The OS aggressively reclaims camera access from backgrounded apps, kills long-running services to save battery, and turns the screen into a burn-in liability if you leave it on. Keeping a camera pipeline alive for days with the screen off — and still reachable remotely — is a real design problem, not a weekend hack.

That design problem is the entire reason our app exists. Background Camera RemoteStream keeps recording and streaming with the screen off, lets you watch remotely, and does it without a cloud account or a per-camera cap. Free to install. The phone was $0 because you already own it.

Where the $200 camera honestly wins

Fairness section, because the comparison is only interesting if it's honest:

Weatherproofing. A phone on the porch needs shelter; a Spotlight Cam doesn't.
The spotlight and siren. A phone has a flashlight and a speaker, which is not the same thing.
Sitting on a charger 24/7 is a battery-longevity tax on the phone.
Purpose-built night optics beat a mid-range phone sensor after dark.

If those four things matter for your placement, buy the camera. If the placement is indoors pointing at a door, a hallway, a pet, or a rental you're checking on — the drawer phone covers it.

Open question for dev.to

What actually keeps people paying for subscription cameras — the hardware, the UX polish, family sharing, or just defaults and inertia? Genuinely curious what the dealbreaker is for people here who've tried the repurposed-phone route and gone back.

Site: superfunicular.com

Build-in-Public, Week 10: Impressions Fell From ~40k/Week to Under 10k — and the Cause Wasn't the Algorithm

Super Funicular — Sat, 18 Jul 2026 07:10:35 +0000

There was no Week 8 update. There was no Week 9 either. This post is the explanation, and it doubles as the most useful postmortem this series has produced so far — useful precisely because the cause turned out to be boring.

Quick context for new readers: I build Background Camera RemoteStream, a free Android app that records with the screen off, stores everything locally, and can stream to an unlisted YouTube Live feed — no account, no cloud, no subscription. The marketing for it is an experiment I've been running in public since May: a largely agent-automated content pipeline, built the same way the app was built (75+ Claude Code sessions), publishing daily and reporting real numbers here every week. Week 7 was the last installment. Then the streak broke.

The headline numbers, stated plainly

As of this morning, measured directly against the dev.to API and my internal tracker:

115 articles published on dev.to, 1,641 total views, 7 reactions, 21 comments — all-time
Cross-channel impressions (mostly X and Threads, per my internal tracker): a peak of roughly 40k/week in mid-June, falling to under 10k/week by early July — a ~75% drop in about three weeks
22 dev.to articles shipped in the last two weeks — that lane never stopped
The 10 pieces published since July 13 have 20 dev.to views between them — feed distribution here remains close to zero; what compounds is search (my all-time top article, a no-subscription listicle, sits at 122 views, nearly all search)

Sit with the tension in those numbers for a second, because it's the whole story: one lane kept shipping daily the entire time, and total reach still collapsed 75%.

The postmortem: output collapse, not audience loss

When the impressions line fell off a cliff, every instinct said algorithm change, shadow throttle, audience gone. The actual diagnosis, once I audited the pipeline end to end, was that the social lane — the one carrying most of the impressions — had quietly stopped publishing for almost three weeks (June 26 to July 15) while the blog lane's daily output masked the silence. Nothing dramatic broke. Several boring things stacked:

The content queue silted up. Roughly 40% of the pending queue was drafted for platforms I couldn't actually post to anymore (deprecated formats, channels without working auth, one platform that needs an account type I don't have). The generator refused to make new content while the queue looked "full" — full of unpublishable dead stock. Purging it took the queue from 191 items to 119 and unblocked generation instantly.
The selection bandit was sampling fantasy arms. The picker that decides what to publish next was choosing from a blind cross-product of ~365 platform×format×topic combinations — and about 93% of its draws were unsatisfiable (no inventory, or a platform that was closed). It "ran" every day and published almost nothing. The fix was one embarrassing filter: only sample arms that have pending inventory on a platform that actually works.
The measurement layer undercounted. Manually published pieces weren't being logged to the same table the scorecard reads, so the collapse looked even deeper than it was — which pushed the diagnosis toward "audience loss" instead of "output loss" for longer than it should have.

None of these would have survived a single honest glance at one number: pieces actually published per day, across all lanes. I wasn't tracking it. The lane with a daily human-visible artifact (a blog post I could see) felt like proof the system was healthy. The lane without one failed silently.

The fixes that shipped

A hard output floor: ≥8 published pieces per day, total, across all lanes. Not a target — a floor that every publishing task is required to check. It was met for the first time on July 17 (11 pieces). It was missed on July 18 morning (5) because of a tooling outage, which at least proves the floor is now measured.
Dead-stock purge + honest platform list. Content only gets generated for channels that verifiably work today.
The bandit filter described above.
One ledger. Every publish — automated or manual — writes to the same log the scorecard reads. If it isn't logged, it didn't happen.

The Week 10–12 experiment: two always-on native lanes

The restoration plan I'm testing for the next two weeks is a two-live-lanes cadence: the dev.to canonical article every day (this lane), plus a native LinkedIn post at least 5 of every 7 days — with X and Threads volume layered on top rather than treated as the foundation.

Why LinkedIn gets promoted to a lane of its own: back in Week 3, the same piece of content did 34 impressions as a native LinkedIn post on a 4-follower account and 0 Day-1 views as a dev.to post. That ratio has held directionally ever since — native text on LinkedIn gets distributed to strangers; dev.to's feed gives me almost nothing, but its articles keep paying search rent for months. So: LinkedIn for reach-now, dev.to for reach-later, and neither lane is allowed to go dark silently again.

Targets on the record, so future-me can be graded: 25k impressions/week by July 31, 100k/week by August 31. Those are recovery targets, not projections — Week 13's post will report the real line.

What's still honestly not working

7 reactions across 115 articles. dev.to's feed has never adopted this catalog, and ten pieces in five days earning 20 combined views says it still hasn't.
Bluesky: 22 followers, zero engagement. Parked.
The app's Play Store listing converts around 5.5% over a trailing 7 days (early-July measurement) — decent for cold traffic, but the input volume is the bottleneck, which is the entire point of this postmortem.

Three takeaways if you're running your own pipeline

Instrument output before you diagnose audience. A reach collapse has two possible causes, and only one of them is fashionable to blame. Check "did I actually ship?" first — per lane, not in aggregate.

Floors beat goals for systems that run without you. A goal fails silently; a floor that must be checked every run fails loudly, which is the only useful way to fail.

A healthy-looking lane will hide a dead one. If one channel produces a daily visible artifact and another doesn't, your intuition about "the system is running" is being formed entirely by the visible one.

The app this experiment funds with attention: Background Camera RemoteStream on Google Play — records with the screen off, local-only storage, built-in LAN web viewer, unlisted YouTube Live streaming from anywhere. Free, no account, no cloud. More at superfunicular.com.

Related reading: yesterday's night-before checklist for watching your home while traveling, and the engineering side of this project in Storage, Not Heat, Is the Real Limit on 24/7 Android Recording.

Going Away This Summer? The Night-Before Checklist for Watching Your Home From Anywhere — No Subscription, No Cloud (2026)

Super Funicular — Sat, 18 Jul 2026 07:06:55 +0000

There's a moment on every summer trip — usually somewhere past the second hour of driving, or right as the plane door closes — when the question arrives uninvited: is the house okay?

The camera industry has a well-priced answer for that feeling: buy a cloud camera, create an account, and start a subscription that outlives your vacation by roughly fifty weeks. Wyze's plan runs about $29.99/yr and Ring's about $69.99/yr as advertised in mid-2026 (verify with the vendor — prices move constantly). Reasonable products, but notice the shape of the deal: a two-week need, billed annually, with your empty house streaming to someone else's cloud the whole time.

There's a $0 alternative you probably already own: an old Android phone, one free app, and thirty minutes the night before you leave. I make the app in question — Background Camera RemoteStream — so this is a maker's guide, with the caveats stated plainly, including the one thing this setup genuinely can't do for a traveler.

I've written a general primer on watching your home or pet while traveling before. This article is the part that guide compresses into a sentence: the pre-departure checklist — what to set up, and crucially what to test, before you lock the door behind you. Because the difference between away-monitoring that works and away-monitoring that quietly died on day two is almost never the app. It's the dry run nobody does.

What away-monitoring actually requires (it's not what home-monitoring requires)

When you're home, a phone-camera on your Wi-Fi is easy — the app's built-in web server lets any browser in the house watch the feed without a single byte leaving your network. But that's a same-Wi-Fi feature by design. When you're 400 miles away, it does nothing for you.

Traveling changes the requirements to exactly three things:

A live view that works from anywhere — over cellular at a rest stop, over hotel Wi-Fi.
Recordings that survive whether or not you ever glance at the stream.
A setup that stays up with nobody home to fix it.

Here's how the app covers the first two, and what the honest answer is on the third.

The 30-minute setup, night before

1. Prep the donor phone (10 minutes). Any Android phone from the last six or seven years is more than enough. If it's a hand-me-down or a kid's outgrown device, do the account cleanup properly — remove the Google account before factory resetting, or Android's Factory Reset Protection will lock you out. I wrote the full prep checklist here. The ideal camera phone holds nothing but the camera app.

2. Install and place it (5 minutes). One tap on Google Play. Point it at the thing you'd actually want to see: the main entry hall beats a window view (glass backlights the image all day and shows you your own yard). Prop it high, landscape, plugged into a wall outlet directly — not a power strip that someone "helpfully" switched off, not an outlet on a timer. This sounds paranoid until it happens.

One quietly useful detail: the app records with the screen off, running the camera as a foreground service with the display dark. On a two-week trip that's not just battery care — a glowing phone screen propped in a dark, motionless house is visible from outside, and it advertises both camera here and nobody home. Dark screen, dark house, camera still rolling.

3. Set up the from-anywhere view (10 minutes). The app streams to an unlisted YouTube Live link. Unlisted means it isn't searchable and isn't on your channel page — the only people who can watch are people who have the exact URL. Keep that link to yourself (or your household), and you have a private window into your hallway from any browser on earth, with no account created in the app and no vendor cloud storing your empty house. If you want the full technical picture of how a dark phone keeps a live stream running, that's written up end to end here.

Two pieces of link hygiene: don't paste the link anywhere public (unlisted is privacy by obscurity of the URL, not authentication), and after the trip, end the stream and start a fresh one next time — old links, like old keys, are cheap to rotate.

4. Do the storage math (5 minutes). Recordings stay local, on the phone — no cloud copy, which is the privacy point, but it makes capacity your number to check. The arithmetic: at a typical ~4 Mbps for 1080p, an hour of video is about 1.8 GB. A phone with 80 GB free holds about 44 hours — under two days of continuous recording, and a full two-week trip of it would need ~600 GB no phone has. So decide what recording is for on this trip: drop the resolution, record the hours you care about, or treat the live stream as primary and recordings as supplementary. Any answer is fine; the wrong answer is assuming it'll sort itself out.

The step everyone skips: the 24-hour dry run

Set everything up the day before, not the morning of, and let it run overnight. Then, before you leave, run three tests:

The away test. Turn off Wi-Fi on your main phone and open the unlisted link over cellular, from the driveway. If you only ever checked the stream from your own couch, you haven't tested the thing the trip needs.
The overnight test. Is the stream still live in the morning? Did the phone stay plugged in, stay cool, keep recording? One overnight catches most placement and power mistakes.
The upload test. The stream rides your home connection's upload bandwidth, which is the thin side of most home internet. If the overnight stream stuttered, drop the stream quality a notch — a stable modest picture beats a beautiful feed that dies.

Fifteen spare minutes the night before versus discovering a dead feed from a beach chair: the trade of the summer.

Honest caveats — read these before you trust it

No motion alerts. This app gives you a live window and local recordings, not a "person detected" push notification. You glance when you think of it; it doesn't tap your shoulder. If alerts are the whole point for you, that's a real reason to pay Wyze or Ring for their cloud AI — I won't pretend otherwise.

Live-glance latency. YouTube Live is a broadcast pipeline; expect tens of seconds of delay. For "is the house fine?" that's irrelevant. For real-time reaction, it's not the tool.

The away-sysadmin problem — the big one. No cloud means nobody else is watching the watcher. If the power blips, the router reboots and hangs, or the phone somehow dies on day four, there is no company noticing and no remote hand to fix it — and unlike at home, you can't walk over either. Reduce the odds (direct wall power, the dry run, a router that's been stable for months), but for a long trip the honest backup isn't software at all: it's a neighbor with a key. Which is also the answer to the broader point — this is monitoring, not a security system. It shows you your house; it doesn't dispatch anyone.

The browser view stays home. The built-in web server is same-Wi-Fi by design — that's what keeps it local. While traveling, the unlisted YouTube Live link is your path; the LAN view is for when you're back.

The flip side of doing your own sysadmin work is that the failure modes of other people's infrastructure can't touch you — there's no company whose shutdown, acquisition, or policy change can take your footage with it. I wrote about what happens to your footage when a free camera app shuts down — local-only means that story can't happen to you.

The verdict

A two-week trip is precisely the wrong occasion to start an annual subscription and exactly the right occasion for the phone in your drawer. Thirty minutes the night before — prep, place, stream, storage math — plus the one discipline nobody bothers with, the 24-hour dry run, and you get the thing you actually wanted: opening a private link from anywhere and seeing your own quiet hallway, footage staying inside your own house the entire time.

Get Background Camera RemoteStream free on Google Play, and read more at superfunicular.com. Have a good trip — and check the feed once from the driveway before you go.

Turn the Old Phone in Your Junk Drawer Into a Baby Monitor (No Subscription, No Cloud Account)

Super Funicular — Fri, 17 Jul 2026 02:44:43 +0000

The baby monitor aisle has quietly turned into a subscription aisle. Most dedicated camera products now route the video feed of your sleeping kid through the vendor's cloud, put the useful features (history, alerts, multi-device viewing) behind a monthly plan, and stop working properly the day the company sunsets the service. That's a strange deal: you buy the hardware, but the actual monitoring is rented.

Meanwhile there's probably a perfectly good camera, WiFi radio, and battery backup sitting in your junk drawer — your last phone.

This is a short tutorial for turning an old Android phone into a baby monitor where the video stays under your control. No new hardware, no account with a camera vendor, no monthly fee.

What you need

Any spare Android phone (this is a great job for a device too old for daily use)
A charger — the phone stays plugged in
A camera app that can record and stream with the screen off — I build Background Camera RemoteStream, so that's what the steps below use, but the general recipe works with anything that has these capabilities

Step 1 — Position the phone

Prop or mount the old phone with the rear camera facing the crib. A cheap gooseneck holder works; so does a bookshelf. Plug it in — video is power-hungry and this phone's battery is presumably not its best feature anymore.

Step 2 — Turn the screen off (this matters more than you'd think)

A glowing rectangle in a dark nursery is both a nightlight you didn't ask for and a "please poke me" invitation once your kid can stand. Screen-off operation means the phone looks inert while the camera keeps running. It also cuts power draw and heat, which matters for a device that's plugged in around the clock.

Step 3 — Pick your viewing path

There are two that cover basically every situation:

Same WiFi (you're home, baby is napping upstairs): the app runs a small web server on the phone, so any browser on your network — laptop, tablet, your daily phone — can open the live view directly. Phone-to-browser over your LAN; the feed never leaves your house.

Away from home (date night, grandparents babysitting, you're traveling): stream to an unlisted YouTube Live from the phone and open the link from anywhere. One honest caveat, because it's your kid on camera: unlisted means not searchable, but anyone who has the link can watch. Treat the link like a house key — share it with the babysitter, not the group chat. If that trade-off doesn't sit right with you, stay on the LAN-only path.

Step 4 — Record locally if you want history

Recordings go to the phone's own storage. There's no vendor server involved, which is the entire point: nobody's cloud, nobody's retention policy, nobody's "we've updated our privacy terms" email about footage of your nursery.

What this is not

Worth saying plainly: this is a video check-in, not a medical device. It doesn't measure breathing or heart rate, and no camera setup — DIY or store-bought — substitutes for age-appropriate safe-sleep practice. Also keep the phone and its cable fully out of the child's reach.

Why I keep pushing the old-phone angle

Phones get replaced on a two-to-three-year rhythm while remaining genuinely capable computers. Repurposing one is cheaper than a camera subscription, keeps e-waste in service, and — for the specific case of pointing a camera at your child — keeps the footage in your home instead of a data center. If you want more jobs for that drawer phone, I ranked five of them here, and wrote up the kid-upgrade variant of this setup here.

Open question for the dev.to community

Parents who went the commercial route: did the subscription creep bother you, or is the polish worth it? And if you've DIY'd a monitor from a phone or a Pi camera, what did you use for the away-from-home path — I keep going back and forth on whether unlisted-link streaming is the right default or whether everything should stay LAN-only.

App: Background Camera RemoteStream on Google Play · more at superfunicular.com · Built solo by Super Funicular LLC.

Before You Recycle That Old Android Phone: 5 Jobs It Still Does (Ranked)

Super Funicular — Fri, 17 Jul 2026 00:45:05 +0000

Your phone didn't stop working when you upgraded. The battery still charges, the cameras still focus, the WiFi still connects. It just stopped being your phone — and the industry would very much like you to trade it in for $40 or drop it in a recycling bin.

Before you do: an old Android phone is a small Linux computer with two cameras, a microphone, a screen, and a battery backup built in. Here are five jobs it can still do, ranked by how much value you get per minute of setup.

1. Home security camera while you travel

This is the highest-value one, and it's why summer is the right time to set it up. Leaving for two weeks — vacation rental, visiting family, wherever — and your home just sits there? Prop the old phone on a shelf facing the door, plug it in, and it becomes a security camera you can check from anywhere.

I use Background Camera RemoteStream for this (disclosure: I built it), and the design goals were exactly this scenario:

Records with the screen off — the phone looks dead on the shelf, doesn't glow all night, and doesn't cook its battery driving a display nobody is watching.
Remote viewing from anywhere via an unlisted YouTube Live stream — no port forwarding, no cloud account with a stranger, and the viewing side is just YouTube, which works on whatever device you have with you.
Local viewing over your LAN through a built-in web server, for when you're home and just want a quick look from your laptop.
Footage stays local on the phone's storage. There is no company server between you and your video.

The whole setup is: install, point the camera, tap record, leave. A dedicated security camera does this too — after you buy it, and usually after you sign up for whichever subscription unlocks remote viewing and clip history. Many popular camera apps and hardware ecosystems put the features that actually matter (remote access, recording retention) behind a monthly plan. The phone in your drawer does it for the cost of the electricity to keep it charged.

Same setup covers the reverse case, by the way: pointing a camera at your own apartment while you're away is the legitimate version of travel-security anxiety. (Pointing one at guests in a rental you host is not — don't be that host.)

2. Baby or pet monitor

Identical hardware story, different room. The phone watches the crib or the dog, you watch the stream from the couch or the office. I wrote a full ranked comparison of seven ways to do this — from a bare video call to dedicated monitor hardware — here: 7 Ways to Turn an Old Android Phone Into a Baby Monitor (Ranked).

3. Dashcam

A phone mount, a long USB cable to the 12V socket, and any dashcam app turns the old phone into a dashcam you don't have to hardwire. It's not as tidy as a purpose-built unit, but the camera sensor in a 3-year-old flagship is better than the sensor in most budget dashcams, and you already own it.

4. Dedicated offline media player

Strip it down: no SIM, no personal accounts, just your podcast app and music synced over WiFi. It becomes the gym/workshop/kitchen device you don't mind dropping, with none of your real phone's notifications. Bonus: your actual phone's battery stops taking the hit.

5. Kitchen recipe screen / e-reader

The lowest-tech entry, but people who do it keep doing it: a phone in a cheap stand, permanently on the counter or nightstand, running a recipe app or reading app. No setup beyond a stand. It's the "just works" tier.

What I'd skip

Old-phone listicles usually pad out to 10+ items with things like "make it a webcam for your desktop" (job #1 covers this better — see the work-from-home camera comparison) or "donate it to science." If a use case needs the phone to be fast, it's a bad fit — these jobs all work because cameras, radios, and screens age far slower than SoCs.

One practical note for any 24/7 plugged-in job (#1, #2, #5): if the phone supports a charging limit (many Androids can cap at 80–85%), turn it on. Batteries dislike sitting at 100% for months.

Open question

For those running an old phone as a permanent fixture: what's your solution for the phone silently dying while you're away — watchdog app, smart plug power-cycling, something else? That's the failure mode I think about most for job #1, and I'd like to hear real-world setups before I over-engineer one.

App from job #1: Background Camera RemoteStream on Google Play · more at superfunicular.com · built solo by Super Funicular LLC.

5 ways to use an old Android phone as a work-from-home camera (ranked)

Super Funicular — Thu, 16 Jul 2026 08:45:23 +0000

You're at your desk on a call. The doorbell rings — a package, a contractor, the dog walker. If you work from home, half your interruptions are "I just need to see what's happening in the other room / at the front door." You don't need a security system for that. You probably have the answer in a drawer.

Here are five ways to press an old Android phone into service as a work-from-home camera, ranked by how well they fit the WFH use case: quick glances from the machine you're already sitting at, without babysitting the phone.

1. Background Camera RemoteStream (screen off, check it from your browser)

Background Camera RemoteStream is built for exactly this shape of problem: the phone records with the screen off (no glowing rectangle pointed at your hallway all day), stores footage locally — no account, no cloud, no subscription — and runs an embedded web server, so you check the feed from a browser tab on your work machine over your LAN. If you also want to peek while you're out, it can push an unlisted YouTube Live stream.

Setup is genuinely short: install, point the phone, open the phone's address in your desktop browser. The honest trade-off: you're the sysadmin. Local storage means it's on you to manage the footage, and LAN access means out-of-home viewing goes through the YouTube Live route.

2. IP Webcam

The long-running classic. Serves an MJPEG stream over your LAN that any browser or VLC can open. Endlessly configurable and free, but the setup is more manual, and the UX shows its age. Great if you enjoy tinkering; less great if you want it working before your next meeting.

3. AlfredCamera

The easiest cloud option: install on both your old phone and your main one, sign in, done. The trade-offs are the standard cloud ones — account required, footage goes through their servers, and the useful features sit behind a subscription. If a browser tab on your LAN already covers you, you may not need any of that.

4. DroidCam (if what you actually want is a webcam)

Different job, worth listing because the searches overlap: DroidCam turns the phone into a webcam for your video calls — your face, not your house. If your actual problem is "my laptop camera is terrible," this is your answer, and none of the monitoring apps above are.

5. A cheap used security camera

The non-app answer. A second-hand cam is inexpensive and purpose-built, but now you own another device, usually another account, and often another cloud dependency — to solve a problem the phone in your drawer already solves.

Related from me: 7 ways to turn an old Android phone into a baby monitor (ranked) — same idea, different room.

Open question for the WFH crowd: if your employer routes your work machine through a full-tunnel VPN, your LAN devices become unreachable from it. How do you handle "glance at a local camera" from a locked-down work laptop — second browser on a personal device, split tunneling, something smarter?

App: Background Camera RemoteStream on Google Play · Built solo by Super Funicular LLC.