Skip to main content

Recording Encounters on Android

Written by Wesley Combs
Updated today

Recording Encounters on Android

Article Type: User Guide
Target Audience: Android Users
Last Updated: January 2026

Overview

Learn how to effectively record patient encounters using Ambient Scribe on your Android device, including tips for optimal audio quality and managing recordings.

Starting a New Recording

Quick Start

  1. Open Ambient Scribe

  2. Tap the Record button on the home screen

  3. The recording indicator turns red when active

  4. A notification appears in the status bar

  5. Begin your patient conversation

With Patient Context (EHR Users)

If you launch from your EHR:

  1. Select the patient in your EHR

  2. Launch Ambient Scribe from the EHR

  3. Patient context is automatically loaded

  4. Tap Record to begin

Recording Best Practices

Optimal Setup

  • Position: Hold device 12-18 inches from conversation

  • Environment: Choose a quiet location when possible

  • Orientation: Keep device stationary during recording

  • Battery: Ensure device has adequate charge (20%+ recommended)

Audio Quality Tips

Do

Don't

Speak clearly at normal volume

Whisper or speak too loudly

Position device between speakers

Cover the microphone

Use in quiet environments

Record near noisy equipment

Keep device stationary

Move device during recording

Pause and Resume

When to Pause

Use pause when:
- Taking a phone call
- Patient needs privacy
- Stepping out temporarily
- Non-clinical conversation occurs

How to Pause

  1. Tap the Pause button during recording

  2. Notification updates to show paused status

  3. Audio capture stops

How to Resume

  1. Tap Resume when ready

  2. Recording continues from where you paused

  3. All content is combined in the final note

Background Recording

Ambient Scribe supports recording while using other apps:

How It Works

  1. Start a recording normally

  2. Press the Home button or switch apps

  3. A persistent notification shows that Ambient Scribe is recording

  4. Recording continues in the background

Recording Notification

A persistent notification shows that Ambient Scribe is recording. Tap the notification to return to the app.

Returning to the App

  • Tap the notification to return

  • Or open app from app drawer

  • Your recording is still active

Foreground Service

Android requires a persistent notification during recording:

What It Means

  • Notification stays visible while recording

  • Cannot be dismissed during recording

  • Ensures Android doesn't kill the recording

  • Normal Android behavior for long-running tasks

Notification Display

The notification shows:
- Recording status
- Elapsed time

Ending a Recording

Standard End

  1. Tap the End Encounter button

  2. Confirm you want to end the recording

  3. Wait for processing to begin

What Happens Next

  1. Audio is uploaded for processing

  2. Transcription is generated

  3. Note is created using your template

  4. You're notified when ready

Processing Time

  • Short encounters (< 10 min): 1-2 minutes

  • Medium encounters (10-30 min): 2-5 minutes

  • Long encounters (30+ min): 5-10 minutes

Recording Indicators

Indicator

Meaning

🔴 Red dot

Actively recording

⏸️ Pause icon

Recording paused

✅ Checkmark

Complete

Battery Optimization Important

Android may stop recordings to save battery. Prevent this:

Disable Battery Optimization

  1. Settings > Apps > Ambient Scribe

  2. Tap Battery

  3. Select "Unrestricted" or "Don't optimize"

Keep Screen On (Optional)

For long recordings, consider:
- Keeping screen on at low brightness
- Or trusting background recording with optimization disabled

Managing Recording Quality

Check Audio Levels

  • Watch the audio level indicator

  • Peaks should reach middle of range

  • Consistent levels indicate good positioning

If Quality Seems Poor

  1. Move device closer to speakers

  2. Reduce background noise

  3. Check microphone isn't blocked

  4. Consider using a wired headset microphone

External Microphones

Ambient Scribe supports external microphones:

Compatible Options

  • USB-C microphones

  • 3.5mm jack microphones (with adapter if needed)

  • Bluetooth headsets

  • Wired earbuds

Setup

  1. Connect your external microphone

  2. Android automatically routes audio

  3. Test with a short recording first

Troubleshooting Recordings

Recording Won't Start

  1. Check microphone permission is granted

  2. Close and reopen the app

  3. Clear app cache

  4. Restart device if issue persists

Recording Stops Unexpectedly

  1. Disable battery optimization (see above)

  2. Check available storage (need at least 500MB)

  3. Keep phone charged

  4. Disable aggressive power saving modes

Poor Audio Quality

  1. Check case isn't blocking microphone

  2. Move closer to conversation

  3. Reduce ambient noise

  4. Clean microphone opening carefully

Recording Not Uploading

  1. Check internet connection

  2. Switch between WiFi and mobile data

  3. Force close and reopen app

  4. Recording will retry automatically

Data Usage

Mobile Data Usage

Recording Length

Approximate Data

10 minutes

5-10 MB

30 minutes

15-30 MB

60 minutes

30-60 MB

  • Use WiFi for longer recordings

  • Reduces mobile data usage

  • Often faster upload speeds

Privacy During Recording

Patient Notification

  • Inform patients that you're using an AI scribe

  • Recording is for clinical documentation only

  • Data handling follows HIPAA requirements

What's Recorded

  • All audio while recording is active

  • Paused periods are not recorded

  • No video is captured

Split Screen / Multi-Window

Android allows split-screen multitasking:

Recording in Split Screen

  1. Recording continues in split screen mode

  2. Useful for referencing patient info

  3. Keep Ambient Scribe visible if possible

Limitations

  • Some devices may have issues with split screen

  • If recording stops, use full-screen mode

Need Help?

Having trouble with recordings? Contact support with details about your device model and the issue you're experiencing.

Did this answer your question?