You set an old Android phone up as a security camera. It worked. Then one afternoon you open the viewer on your other phone and the picture is frozen, or the page will not load at all. The camera phone is sitting right there, plugged in, screen off, apparently fine.
Most people's next move is to walk over and restart the app. That is almost always the wrong move.
There are three separate things Android itself does to a running camera's network connection. All three produce the same symptom. None of them stops the recording. Restarting the app does.
Why does my phone security camera live view stop but the recording keep going?
Short answer: because they are two different jobs. Recording writes video to the phone's own storage and needs no network at all. The live view is a network connection, and Android is allowed to move, block, or kill that connection while the recording continues untouched. A frozen live view is normally a network event, not a camera event.
Does an old-phone security camera keep recording without internet?
Short answer: yes, if the app records locally. Background Camera RemoteStream writes video to the phone's own storage with the screen off, and its built-in web server serves the live view over your local network. No internet connection is required for either the recording or for viewing over the same Wi-Fi. The internet is only needed if you want to watch from outside the building, or to push a YouTube Live stream.
That distinction is the whole point. A cloud camera that loses its uplink loses the footage, because the footage was only ever on its way somewhere else. A phone recording to its own storage loses nothing but the view.
Reason 1: Android moved the phone to a different network underneath the app
Every Android app has a default network, and the system picks it, not you. The platform documentation is direct about the preference order: the system "typically prefers unmetered networks to metered ones and faster networks to slower ones."
Picture the common case in a shop or a shared house. The camera phone is streaming over mobile data. Somebody switches the router back on after a power cut, or a neighbour's open network comes back in range. Android sees a free, unmetered Wi-Fi network, decides it is better, and switches.
Here is the part nobody expects, from the same page:
"When a new network becomes the default, any new connection the app opens uses this network. At some point later, all remaining connections on the previous default network are forcefully terminated."
Read "at some point later" carefully. New connections go to the new network immediately, but the connection your live view is already using stays alive on the old network for an unspecified period, and is then killed. From the viewer's side that looks like a stream frozen on its last frame, with no error. Nothing crashed. The connection was cut out from under it.
What to do: reload the viewer page. Nine times out of ten a fresh request opens on the new network and the picture comes straight back. If you are watching over your local network, the phone's address may also have changed with the network — see Reason 3.
How to prevent it: on the camera phone, forget every Wi-Fi network except the one you want it on. A phone that cannot see an alternative cannot be moved to one.
Reason 2: Data Saver blocked it, and you are on mobile data
This one matters most on prepaid connections. Google's own documentation opens the topic with a sentence worth keeping:
"Over the life of a smartphone, the cost of a cellular data plan can easily exceed the cost of the device itself."
Data Saver exists for exactly that. Google says it is "especially useful when roaming, near the end of the billing cycle, or for a small prepaid data pack." When it is on and the phone is on a metered network, the documented behaviour is blunt: "the system blocks background data usage and signals apps to use less data in the foreground wherever possible."
A camera app streaming with the screen off is, as far as the system is concerned, exactly the sort of background data usage Data Saver exists to block. The recording continues, because writing a file to storage is not network usage. The stream does not.
The fix is documented and takes one minute: "Users can allow specific apps to use background metered data usage even when Data Saver is turned on." On most phones that is Settings → Network & internet → Data Saver → Unrestricted data, then switch on your camera app. The exact menu name varies by manufacturer, so search Settings for "Data Saver" if you cannot find it.
Two related traps on the same setting. A Wi-Fi network can itself be marked as metered — many phone hotspots are, by default — so Data Saver can bite even when you are not on mobile data at all. And the per-app "background data" toggle in the app's own data-usage screen is a separate switch from Data Saver, with the same effect. Check both.
If you want to watch what this is costing you rather than guess, we wrote up how to measure it in what happens to a phone security camera during a power cut or an internet outage.
Reason 3: the Wi-Fi came back, but it is not the same network any more
This is the one that makes people think the app is broken, because everything looks restored. The router rebooted, the phone reconnected, the Wi-Fi icon is full — and the viewer still will not load.
The documentation explains half of it:
"When the network disconnects, the
Networkobject stops being usable. Even if the device later reconnects to the same appliance, a newNetworkobject represents the new network."
"The same appliance" is doing a lot of work in that sentence. Same router, same password, same room — and the system still treats it as a new network, deliberately, so that nothing carries on using a connection it only thinks is alive.
The other half is your router. Router addresses are handed out on a lease, and after a reboot the router is free to hand your camera phone a different one than it had before. The address you bookmarked, 192.168.1.7 or whatever it was, may now belong to a television.
What to do: open the camera app on the phone and read the address it is currently showing, then use that. To prevent it: most routers have a setting variously called DHCP reservation, static lease, or address binding — pin the camera phone's address there once and the bookmark stops rotting.
The one thing not to do
All three of the above are network failures. The recording survived all three.
Restarting the camera app is the only action in this article that ends the recording. If something did happen in front of the camera during those minutes, restarting is what turns a viewing outage into missing footage — in response to a problem it does not fix, because the network condition is still there.
So: reload the viewer first. Check the phone's current address second. Check Data Saver third. Touch the app last, and only after you have saved anything you might need.
A five-minute test to run before you rely on this
- Start the camera and confirm the live view works from your second device.
- Turn the router off at the wall for two minutes and back on.
- Do not touch the camera phone.
- When the Wi-Fi is back, reload the viewer. If it does not load, read the phone's current address off its screen and try that.
- Stop the recording normally and check the file. It should cover the entire outage, including the minutes with no network.
Step 5 is the one that matters. If the file has a hole in it, the app was not recording locally, whatever its store listing said.
What the documentation does not tell you
To be fair about the limits of what is actually written down:
- "At some point later" is never given a number. There is no documented maximum time between the default network changing and the old connections being terminated.
- The documentation describes what the system does to connections, not what any particular app does about it. Whether an app reconnects on its own is the app's business, not the platform's.
- Nothing in the Data Saver documentation addresses a foreground service that is streaming continuously — the examples are all about syncs and downloads.
- Manufacturers add their own battery and data restrictions on top of the platform's, and those are not documented by Google at all.
- The Data Saver page's own guidance was last updated in January 2024, well before Android 16.
- None of this says anything about how any specific competitor's app behaves. We cannot see inside other people's apps, and neither can you from a store listing.
What to do this week
Pick the camera phone up once and do four things: forget the Wi-Fi networks it should not use, add the camera app to Data Saver's unrestricted list, reserve its address on your router, and run the five-minute test above. That is a one-time job.
If you are setting this up somewhere with no router at all, the hotspot arrangement is covered in how to use an old phone as a security camera without a Wi-Fi router. And if you are still choosing an app, we keep a running list of the free, no-subscription options that store video locally.
Background Camera RemoteStream records with the screen off to the phone's own storage, serves a live view from a web server running on the phone itself, and can push to YouTube Live when you want a stream that reaches outside the building. No account, no cloud storage, no subscription. It is free on Google Play, and there is more at superfunicular.com.
Sources
Top comments (0)