AUDIO GUIDE / FIX A PROBLEM

Android audio stops when the screen turns off: what to check

Troubleshoot background audio interruptions on Android, including Pixel battery settings and Samsung sleeping apps, with a repeatable MicDrop test.

START HERE

Check the affected app’s background battery permission, then repeat the same locked-screen test. Keep working defaults; try a per-app exemption only if interruptions continue. Record whether Battery Saver or a Samsung sleeping-app rule is involved.

Confirm that screen lock is the trigger

Audio stopping after the screen turns off suggests a background restriction, but it is not proof. The PC might go to sleep at the same time, Wi-Fi might disconnect, or another app might take audio focus. Start with a short comparison that can distinguish these cases.

  1. Keep the Windows host awake and use phone-speaker playback on the home network.
  2. Listen with the screen on and note whether interruptions already occur.
  3. Lock the phone without changing its location. Note the time to interruption and whether the playback notification remains visible.
  4. Unlock it and record whether audio resumes automatically, after opening the app, or only after reconnecting.

Repeat the same test after each settings change. A ten-second success does not establish that a setup will last through a longer session; the MicDrop beta checklist suggests a separate 20–30 minute background check.

Pixel and other Android phones

Menu names differ by manufacturer and Android version. On Pixel, find Settings → Apps → MicDrop → App battery usage and inspect Allow background usage. Note the starting state before editing it.

If background use is disabled, enable it. If the app is Restricted, try Optimized first. When Optimized already works, keep it. If interruptions persist, try Unrestricted or the equivalent per-app exemption and repeat the same test. Google recommends keeping battery optimization enabled generally; there is no need to turn off Adaptive Battery for the entire phone.

Samsung sleeping-app settings

Also inspect Battery → Background usage limits; some versions place Battery inside Battery and device care. Remove MicDrop from Sleeping or Deep sleeping apps if present. If background interruptions continue, test adding it to Never sleeping apps. Record that change separately from the ordinary battery setting.

A manufacturer-specific rule can explain why a generic Android instruction seemed ineffective. Do not assume a menu missing on another phone is an installation error.

Check interruptions beyond battery optimization

  • Battery Saver: record whether it is enabled and compare a run with it off if the failure happens only then.
  • Incoming calls or another audio app: note the interruption and test resume behavior separately from a quiet locked-screen run.
  • Wi-Fi changes: stay in one place for the baseline; then test movement or reconnection deliberately.
  • Microphone sessions: verify phone permission, microphone mute, and the selected input. Playback success alone does not validate background microphone capture.

For MicDrop, notification Play is playback-only. Do not assume pressing it authorizes a new microphone session. Begin microphone use explicitly on the phone and verify the receiving app before relying on duplex.

Keep the narrowest change that helps

An unrestricted app can consume more battery. If the exemption does not change the result, restore the original setting and investigate the next cause. Neither a battery exemption nor a persistent notification guarantees uninterrupted audio.

Report the app version, phone/OS, original battery setting, elapsed time, screen state, and what restored playback. Save the original failing result alongside any successful workaround. Copy MicDrop's last stream report when available and review it before sharing. For iPhone, use the iPhone guide; iOS has a different background-audio model.

Sources & version notes

Checked against the documentation below on November 13, 2026. App labels and platform support can change; use matching MicDrop builds and check the current release notes. These are setup guides, not new hardware benchmark results.