Background recording troubleshooter.

Why background recordings stop

Almost every "my recording stopped" report traces back to one of six things, and they are worth keeping separate because their fixes are completely different:

The troubleshooter above sorts your answers into these categories using a fixed rule set, then gives you the steps that match your platform and manufacturer. It doesn't guess with an AI model, and it doesn't upload anything.

Why iPhone recordings stop after calls

iOS treats the microphone as an exclusive resource. When a call — cellular, FaceTime or a VoIP app — activates, the system takes the input and interrupts the audio session of whatever was recording. This applies to every app on the App Store equally; there is no entitlement that lets a third-party recorder keep capturing through a call.

What that means in practice:

• audio recorded before the call is already on disk and is safe;
• there is no microphone input for the recorder during the call;
• after the call, iOS can signal that the interruption ended, but a successful resume isn't guaranteed;
• the reliable habit is to check the recorder's status after any call.

The same interruption happens with Siri, keyboard dictation, live transcription apps and recording video. See iPhone recording stops after a call and recording stops after Siri for the specific cases.

Why Android closes recording apps

Android's background rules are layered, and manufacturers add more layers on top. A recorder needs to run as a foreground microphone service with a visible ongoing notification — that's the configuration the platform expects — and even then, per-app battery settings can override it.

The layers, roughly in the order worth checking:

1. Microphone permission, including the always-allow option where offered.
2. Notification permission — blocking the ongoing notification undermines the service that keeps recording alive.
3. Per-app battery usage set to Unrestricted.
4. Battery Saver off, including the automatic trigger at low charge.
5. Adaptive Battery, which can restrict an app you rarely bring to the foreground.
6. Manufacturer sleeping-app, deep-sleep and auto-start lists.
7. Third-party cleaner, security and task-killer apps.

Step 6 is the one people skip, and on Samsung, Xiaomi, Oppo, Vivo, Realme, OnePlus and Huawei it is usually the decisive one. Start with Android recording stops in the background, then the page for your phone: Samsung or Pixel.

Battery optimization and background recording

Battery optimisation is not a bug to be defeated — it exists because continuous background work costs power. The trade-off is worth making deliberately:

• recording itself is a steady, modest draw: the microphone plus a background process;
• transcription, screen time, location and network activity cost more than the recording does;
• an older battery makes any continuous task look worse than it is;
• scheduled windows are cheaper than 24/7 capture when you only need certain hours.

Measure it on your own phone rather than trusting a number from a review: charge to 100%, record two hours with the screen off, and note what it cost. Then decide whether to run continuously or on a schedule. Our guide to recording all day without draining the battery goes further, the audio storage calculator does the same for space, and the phone compatibility checker scores both together for your specific device before you commit to a mode.

Microphone conflicts

Mobile operating systems allocate active microphone capture to one app at a time. That's a privacy feature — it's the reason two apps can't silently listen at once — and it's the direct cause of a large share of interrupted recordings.

Common holders of the microphone:

• phone calls and VoIP calls, including a background call that never fully ended;
• Siri, Google Assistant and other wake-word assistants;
• keyboard dictation and voice typing;
• the camera while recording video;
• screen recorders configured to capture microphone audio;
• messaging apps recording a voice note;
• live transcription and captioning apps.

If you see an explicit message about the microphone being in use, find and release the holder. If a recording quietly ended and you can't explain why, an accidental assistant trigger is worth ruling out before you change any battery settings.

Scheduled recording failures

Scheduling uses a different mechanism from continuous recording, so continuous capture working perfectly tells you nothing about whether a schedule will fire. A schedule needs the app to still be alive at the start time and permitted to act.

Check, in this order: whether the app was force-closed or swiped away, whether the device restarted, notification permission, exact-alarm permission on Android, battery restrictions and auto-start, the schedule's own days and times, the device clock and time zone, free storage, and whether the microphone was busy at the start time. The full walk-through is on scheduled recording did not start.

Then test the actual path: set a schedule five minutes ahead, leave the app in the background, lock the screen and wait. Repeat it once after a restart, and once overnight.

How to test background recording reliability

Change one thing at a time and prove it with a ladder of tests. This is faster than changing five settings at once, because it tells you which change mattered.

1. Restart the phone.
2. Open your recorder and start a 15-minute recording.
3. Lock the screen and put the phone down.
4. Avoid calls and any app that uses the microphone.
5. Check whether the recording covers the full 15 minutes.
6. Repeat, introducing one suspected interruption at a time — a call, then a voice assistant, then Battery Saver, then app switching.
7. Write down the exact time and event that causes the failure.

Keep a simple pass/fail note for: 15 minutes locked, one hour locked, overnight, a call mid-session, app switching, and a scheduled start. The first test that fails names your cause.

Test the setup on your device before relying on it for something you can't repeat. Background behaviour varies between phone models and OS versions, so your own test result is worth more than any app's marketing copy.