Should You Turn On Developer Options to Keep an Old Phone Security Camera Recording With the Screen Off? Six Settings Checked Against Android's Docs

Most "keep your camera app running" guides end with the same step: tap Build number seven times, open Developer options, and start switching things. Our own setup guide from earlier this year did it too. It told readers to turn on Stay awake, two lines above a sentence saying screen-off recording is "critical for battery and burn-in prevention." Those two lines cannot both be right, and that contradiction is what sent me back to Android's own documentation for every developer setting that a camera guide is likely to mention.

This post goes through six of them. For each one: what Google's documentation says it does, what that means for an old phone recording with the screen off, and whether you should touch it. Short version first.

Do you need Developer options to keep a phone security camera recording with the screen off?

No. A camera app that records with the screen off through a foreground service (the thing that puts a permanent notification in your status bar) is already in one of the most protected states Android has. Android's process-lifecycle page puts a process that is "running as a foreground service, through Service.startForeground()" in the visible tier, and says these processes "are considered extremely important and aren't killed unless doing so is required to keep all foreground processes running."

None of the six settings below makes that stronger. Two of them can make your setup worse. One of them is a security risk if you leave it on. And none of them needs internet, so everything here applies to an offline, no-cloud, local-only setup as much as to one that streams.

Now the details, with the exact wording from Google's pages.

1. "Stay awake" turns the screen on, which is the opposite of what you want

Google's developer options page describes it in one line:

Stay awake: Sets your screen to stay on while the device is plugged in.

That is all it does. It does not keep apps awake. It keeps the display awake. On a camera phone that is plugged in 24 hours a day, it means the screen never turns off at all.

That costs you the four things screen-off recording exists to give you:

• Heat. The display is one of the biggest heat sources in a phone. A camera phone already has the camera sensor, the video encoder and usually Wi-Fi running all day. Adding a lit panel on top of that, in a closed shop or a warm room, is the wrong direction.
• Burn-in. On an OLED panel, a static image shown for weeks can leave a permanent ghost. A camera preview with a fixed frame and fixed buttons is about as static as an image gets.
• Visibility. A glowing phone on a shelf at night says "camera here." A dark phone says nothing.
• Battery heat. A phone that is always on charge is already warm. A lit screen adds more heat, and heat is bad for lithium batteries.

Our old guide recommended turning this on. That was wrong for a screen-off setup, and I am correcting it in that guide today with a link back here. If you followed it: Settings > System > Developer options > Stay awake > off.

2. "Background process limit" has no upside for a camera

The docs say:

Tap Background process limit to set the number of processes that can run in the background at one time.

The page does not say whether a process holding a foreground service counts as "background" for this limit, and I am not going to guess. What the process-lifecycle documentation does say is that a foreground service puts its process in the visible tier, not the cached tier that holds apps you have simply left.

But here is the practical point: there is no setting on this list that helps a camera. "Standard limit" is the default. Choosing "No background processes" or "At most 1 process" can only reduce what is allowed to keep running: your launcher, your keyboard, the Wi-Fi assistant, the very app you use to check the camera from the same phone. If you or a previous owner changed this, set it back to Standard limit.

This matters more than it sounds on second-hand phones. If you bought the camera phone used, Developer options may already be on, with settings the last owner chose. Open the menu once and look. (Our checklist for buying a second-hand phone for shop camera duty covers the checks to do at the counter; this is one more to do at home.)

3. "Don't keep activities" targets screens, not services

The docs:

Enable Don't keep activities to increase battery life by destroying every activity as soon as the user leaves the activity's main view.

An activity in Android is a screen of an app: the preview you see, the settings page, the button you press. A service is a different component. A foreground service is the part that keeps recording after you press the power button. This option is aimed at the first, not the second.

So it is not a "camera killer" in the way some forum posts suggest. But it does nothing useful either. Every time you leave the camera app and come back, its screens are rebuilt from scratch. The documented purpose is testing how apps handle being destroyed. On a phone you rarely look at, the "battery life" it promises is the screen battery you already save by keeping the screen off. Leave it off.

4. "Suspend execution for cached apps" freezes cached apps, and a recording camera is not one

This option exists on Android 11 and higher. Android's cached apps freezer page explains it:

This feature stops execution for cached processes and reduces resource usage by misbehaving apps that might attempt to operate while cached.

The key word is cached. The same page says that an app that needs to keep working can "change the process status to noncached," and gives the examples: "a bound foreground service or foreground status." A camera app that is actively recording with a foreground service is not cached, so it is not the target.

Two details from that page are still worth knowing:

• On Android 14 and higher, cached processes are "frozen 10 seconds after entering the cached state."
• "If all processes for a particular app are frozen, the system terminates any active TCP sockets maintained by the app."

That second point is the useful one for troubleshooting. If your viewer is an app on a second phone, and you switch away from it, that viewer can become cached, then frozen, and its network connection can be cut. When you come back, the picture may need to reconnect. That is the viewing phone doing its job of saving battery, not the camera phone failing. (Browsers have their own version of this for background tabs; we wrote about what a browser does to a camera view left in a hidden tab.)

On most phones this option is set by the manufacturer. Leave it at the default.

5. "Aggressive Wi-Fi to cellular handover" can spend your data pack

The docs:

Aggressive Wi-Fi to cellular handover: When the signal is low, makes Wi-Fi more efficient in handing over the data connection to a cellular network.

On a phone with no SIM, this does nothing. On a camera phone that still has a prepaid SIM in it, it is a quiet risk. If the shop Wi-Fi is weak at the back of the room, this setting makes it easier for the phone to move its data to mobile. A live stream to YouTube uses a lot of data per hour. On a small daily pack, a weak-Wi-Fi evening could use it up.

If the camera phone has a SIM, turn this off, and read our earlier piece on whether Data Saver stops a screen-off stream on mobile data for the other half of the picture. If you only watch the camera on your local Wi-Fi, consider taking the SIM out entirely.

6. USB debugging and Wireless debugging: turn them off on an unattended camera

These are the settings Developer options exists for. They let a computer install apps, read files and control the phone. That is exactly why they do not belong on a phone that sits alone in a shop or a hallway.

• USB debugging means anyone who plugs a computer into the phone, and taps "Allow" on a screen that is not being watched, can control it.
• Wireless debugging (Android 11 and higher) does the same over the network.

Android malware has abused exactly this path; we covered what the Kimwolf botnet case showed about repurposed Android cameras. A camera app that works properly does not need either one. Turn both off.

The fastest fix: switch Developer options off entirely

Google's page has a sentence most guides skip:

At the top of the Developer options screen, you can toggle the options on and off ... When off, most options are disabled except those that don't require communication between the device and your development computer.

So if you enabled Developer options only because a guide told you to, the simplest safe step is: open it, check Stay awake is off, then switch the main toggle at the top off. (One Developer options entry we have covered before, Wi-Fi non-persistent MAC randomization, is another reason to check this menu if your camera's address keeps changing.)

What actually keeps a screen-off camera running

If none of these switches help, what does? The parts that are not hidden in a developer menu:

1. A foreground service with its notification. That is what puts the camera in the "visible" tier. Do not hide or swipe away the app's notification channel.
2. Battery optimization set to "Unrestricted" for the camera app (wording varies by brand). Manufacturer battery savers are worth checking before anything in Developer options.
3. Charger plugged in, screen off. Screen-off saves heat and power; the charger does the rest.
4. Local storage with room to spare. A camera that fills its storage stops recording no matter how the system treats it.

That is how Background Camera RemoteStream is designed to work: it records with the screen off through a foreground service, keeps recordings on the phone, and serves a live view to devices on your own network through a small built-in web server, with optional YouTube Live when you want to watch from outside. No cloud storage, no subscription, and no Developer options needed.

Quick checklist

• Developer options was never enabled: do nothing.
• It is enabled (you, a guide, or a previous owner):
  • Stay awake: off
  • Background process limit: Standard limit
  • Don't keep activities: off
  • Aggressive Wi-Fi to cellular handover: off if there is a SIM
  • USB debugging and Wireless debugging: off
  • Then switch the main Developer options toggle off.

Sources

• Android Developers, Configure on-device developer options (Stay awake, Background process limit, Don't keep activities, Aggressive Wi-Fi to cellular handover, main toggle behavior)
• Android Developers, Processes and app lifecycle (foreground service = visible process; cached process definition)
• Android Open Source Project, Cached apps freezer (Android 11+, cached-only freezing, 10-second freeze on Android 14+, TCP socket termination)

Background Camera RemoteStream is built by Super Funicular LLC. Get it on Google Play. More at superfunicular.com.