DualCam

Why dual camera recording stops, throttles or drops frames

Running two cameras and a video encoder at once is one of the heaviest things you can ask a phone to do. When a dual recording stops early or gets visibly choppy, it is almost always one of four causes: the device got hot, storage ran low, the requested settings exceeded the multi-camera hardware budget, or the system took the camera away. Each behaves differently and each has a different fix.

The good news is that a well-built app finalises the file when any of these happen, so an interrupted take is a shorter video rather than a corrupt one. DualCam closes the file properly in every one of these cases.

Heat: the most common cause of a long take ending early

iOS reports a device-wide thermal state, and it escalates in steps. DualCam reacts at two of them. At the “serious” level, if you are not already recording and are set to 1080p, it drops you to 720p before you start, because starting a heavy take on an already hot phone is how you get an interrupted one. If you are already recording at 1080p at that level, it warns you instead of yanking the resolution mid-file.

At the “critical” level, recording stops. The file is finalised and saved with a notice explaining why. There is no way to override this, and there should not be: at that point the system is already throttling the processor and the frames you would capture would not be worth keeping.

What actually helps

  • Take the case off, especially a thick or insulating one. This is the single biggest lever.
  • Do not shoot in direct sun with the screen at full brightness if you can avoid it.
  • Do not start a long take immediately after fast charging, or while still plugged in.
  • Use 720p for long takes. Half the pixel throughput per camera is a real reduction in load.
  • Break a 20-minute session into several takes. Between takes the phone gets a chance to shed heat.

Storage: it stops before you get a broken file

A dual recording is a normal-sized video file, but it is written continuously and it will not politely stop when the disk fills. DualCam therefore checks free space in advance: it requires at least 200 MB free to start recording at all, and it stops an in-progress recording when free space falls below 100 MB. That headroom exists so the file can be closed cleanly instead of truncated mid-write.

At the app’s recording bitrate of about 10 Mbps, video consumes roughly 75 MB per minute, so a gigabyte of free space is around thirteen minutes. If you plan a long take, clear space first; “nearly full” is not a state you want to discover twelve minutes into something you cannot reshoot.

Hardware cost: when the settings do not fit

A multi-camera session carries a hardware cost that has to stay within budget. Resolution and frame rate across both cameras are the inputs. If you raise the resolution and the resulting configuration goes over budget, the session is not viable — not slow, not degraded, simply not viable.

DualCam handles this by reconfiguring, measuring, and reverting: after you change resolution it checks the cost of the new configuration, and if it is over budget it restores the previous resolution and tells you the setting is unavailable on this device. This is why 1080p may be selectable on one supported iPhone and quietly refused on an older one. It is a per-device limit, not a bug.

Interruptions: when the system takes the camera

iOS can suspend a capture session for reasons that have nothing to do with your app. DualCam surfaces each of them by name rather than showing a generic error, and if a recording is in progress it finalises and saves the file before the session goes down.

  • The app went to the background — camera access is not available to a backgrounded app.
  • Another app took the camera — the classic case is answering a video call.
  • Multiple foreground apps — the system will not give the camera to a split view or Slide Over arrangement.
  • System pressure — the device is under enough load or heat that the camera is withdrawn outright.

The practical version: put the phone in Do Not Disturb before a take that matters, and do not switch apps mid-recording.

What “dropped frames” usually means here

Both cameras are locked to 30 frames per second, and late video frames are discarded rather than queued. This is the correct trade-off for live capture — a frame that arrives too late to be composited on time is worse than no frame at all, because queueing it would push the whole pipeline further behind. So visible stutter under load is the system protecting the timeline, not the app losing your footage. If you see it, the answer is the same as for heat: lower the resolution, cool the device, shorten the take.

Common follow-up questions

Do I lose the recording when it stops?

No. In all of these cases the file is finalised and kept — you get a shorter video, not a corrupt one. The recording lands in the app’s own library, where you can review it and save or share it.

Why does my phone get so much hotter than with the normal Camera app?

Because it is doing considerably more: two camera pipelines instead of one, a GPU compositing pass every frame, and a hardware encode of the result. Comparing it to single-camera recording is not a fair comparison of efficiency.

Does a battery case or wireless charging make it worse?

Charging generates heat, and heat is the main constraint on a long dual recording. If you can, record on battery and charge afterwards.

Want to just do this?

DualCam records the iPhone front and back cameras at the same time and writes one finished MP4 while you shoot. Free, no account, no ads, nothing leaves the phone.

Download on the App Store