Why your running app voice cues go silent
Short answer
Voice cues fail for four separate reasons and reinstalling the app addresses none of them. The speech engine can be missing a voice for your language, another app can be holding audio focus, the operating system can suspend the app in the background, and a Bluetooth headset can reconnect onto a different audio route mid run. The fix depends entirely on which of the four you are hitting, so this guide is ordered by cause rather than by settings screen.
The fixes do not overlap. Voice cues fail for four separate reasons, and reinstalling the app addresses none of them.
The four causes, and how to tell them apart
Ask what else was still working. Music, the moving distance figure and the screen each rule out a different cause, and that is the fastest way to narrow this down.
| Cause | What you noticed | Where to look |
|---|---|---|
| Speech engine has no voice | Nothing ever speaks, in any app, including the settings demo | Phone accessibility settings, text to speech output |
| Another app holds audio focus | Music or a podcast plays normally, cues never arrive | The other audio app, and what it is playing |
| The app was suspended | Distance and time also stopped, or froze part way | Battery and background settings for that app |
| Wrong audio route | Sound went to the phone speaker, the car, or nowhere, after a headset reconnected | Bluetooth connection history during the run |
The standard advice is thinner than that table. Strava's own help centre tells runners to "Try reinstalling the Strava app and restarting your phone", to check that "your media volume, not just your ringer volume, is turned up to an audible level", and, on Android, to "check your Text To Speech-language options and confirm the preferred engine matches your system's language preference" (Strava help centre, Audio Announcements, checked 2 August 2026). Only the last of those reaches a cause in the table, and it stops one step short, because an engine can match your system language and still have no voice data installed for it.
Nothing on that page separates a cue that was never spoken from a cue that was spoken into a headset the phone had stopped using.
The complaint recurs. Strava's own community hub carries threads titled Audio cues don't work, Audio notifications stopped working and Audio Cues not working on the Pixel watch 2, the last of those on a watch and not a phone. That archive is no longer publicly readable, so the titles are all anyone outside Strava can now check.
Titles are not diagnoses. They are here to show that the symptom crosses devices and versions, which is the first sign that the cause sits below the app.
Speech engines and missing voices on Android
A missing voice silences every app at once. On Android the words are usually produced by a separate speech engine and not by the running app, so the useful move is to stop debugging the running app and go to the phone's own settings.
Google's own accessibility documentation states that "The default text-to-speech engine choices vary by device" and that "Options can include Google's Text-to-speech engine, the device manufacturer's engine, and any third-party text-to-speech engines that you've downloaded from the Google Play Store" (Android Accessibility Help, Text-to-speech output, checked 2 August 2026). The same page describes installing language support: open Settings and "Select Install voice data", then choose "the language that you want to install".
- Open your phone settings, then accessibility, then text to speech output.
- Press the play button to hear the built in demonstration. If that is silent, no running app will fix it.
- Check which engine is selected, and note that the manufacturer engine and the Google engine are separate installs with separate voices.
- Check the language, and install voice data if the language you run in is not present.
- Switch engines and play the demo again. A working demo on one engine and silence on the other identifies the fault precisely.
Audio focus, and a second app that will not let go
The cue is losing a contest. If the demo speaks but your run is silent while music plays, the contest is for the audio output, and Android's developer documentation is blunt about the rule: "Only one app can hold audio focus at a time" (Android developers, Manage audio focus, checked 2 August 2026).
A running app that wants to speak over your music asks for a short, temporary grant. The same page describes it: "Request transient focus with ducking (AUDIOFOCUS_GAIN_TRANSIENT_MAY_DUCK) to indicate that you expect to play audio for only a short time and that it's OK for the previous focus owner to keep playing if it 'ducks' (lowers) its audio output."
Spoken word audio is deliberately exempt. Automatic ducking only happens when the currently playing app "is not playing audio with content type AudioAttributes.CONTENT_TYPE_SPEECH", because ducking one voice under another is unintelligible, so if you run to audiobooks or podcasts the system will not quietly lower them for a cue the way it lowers music. What happens instead is left to the player. It may pause, or it may keep going at full volume over the top of the cue. It may also do nothing at all. Testing your cues against music and then running to a podcast tests the wrong thing.
- Close the second audio app entirely instead of pausing it, then start the run and add the music back afterwards.
- If cues return with the other app closed, the running app is working.
- Voice call apps, navigation apps and podcast players are the usual holders. Check the background, not the screen.
The app was suspended, so nothing was spoken
Check the recorded track first.
If the distance stopped moving at roughly the moment the voice stopped, this is not an audio problem: the app was suspended or terminated, and a suspended app has nothing to say. The track settles the question in seconds.
On Android the visible sign of an app that is allowed to keep working is the notification. Android's documentation states that "Foreground services show a status bar notification, to make users aware that your app is performing a task in the foreground and is consuming system resources" (Android developers, Foreground services, checked 2 August 2026). If that notification vanished during your run, the service was gone and the silence followed from it.
This cause has its own diagnosis on each platform, and it is a longer subject than audio. The iPhone version is covered in why an iPhone stops tracking a run in your pocket, and the Android version, including the manufacturer task managers that are more aggressive than stock Android, in Android battery settings that stop run tracking.
Bluetooth reconnection and the wrong audio route
Reconnecting is not resuming.
A headset that drops and reconnects mid run makes the system change the audio route, and both the running app and your music player have to respond. Apple's audio session guidance lists the triggers as ordinary events: plugging in a pair of headphones, connecting a Bluetooth LE headset, or unplugging a USB audio interface.
Media playback apps should pause playback if the route change reason is AVAudioSessionRouteChangeReasonOldDeviceUnavailable, but should not if the reason is AVAudioSessionRouteChangeReasonOverride.
Apple, Audio Session Programming Guide, Responding to Route Changes, checked 2 August 2026
Interruptions produce the same symptom. Apple describes an audio interruption as "the deactivation of your app's audio session", triggered when "a competing audio session from an app is activated and that session is not categorized by the system to mix with yours", and states that "For your audio to resume, you must reactivate your audio session" (Apple, Handling Audio Interruptions, checked 2 August 2026). A phone call, an alarm or a car head unit can start one. If an app does not reactivate afterwards, the run continues normally and only the voice is gone.
- Note whether the silence started at a moment your headphones beeped, reconnected, or switched between two paired devices.
- If you passed a car, check whether the phone joined the car system and sent the cue there.
- Forget and re-pair a headset that reconnects repeatedly, and test with wired headphones once to remove the route from the equation.
Silent switch, media volume and Focus modes
Volume is the least interesting cause.
It is also the easiest to eliminate, so do it early. Media volume is a separate control from ringer volume on both platforms, and a volume key pressed in silence usually moves the ringer instead. Start something playing, then press the key, so you can see which slider you actually moved. Strava's help centre reaches for this first, and adds a detail worth knowing on Android: those phones "often have three or four settings for volume".
On an iPhone the ring/silent switch does not silence every app. Whether it silences a given sound depends on the audio session category the app chose. Apple's category table marks the ambient categories as silenced by the Ring/Silent switch and by screen locking, and marks playback as not silenced, with the note that "For your app to continue playing audio when the Ring/Silent switch is set to silent and the screen is locked, make sure the UIBackgroundModes audio key has been added to your app's Info.plist file" (Apple, Audio Session Categories and Modes, checked 2 August 2026). So an app that goes quiet under the silent switch has made a choice, and an app that keeps talking has made the opposite one.
A Focus on its own does not explain a silent coach. Focus modes belong on the list because runners reach for them, and a Focus, including Do Not Disturb, filters notifications and calls (Apple, Set up a Focus, checked 2 August 2026). It does not mute an app that is playing audio. Switch it off, confirm the cues are still missing, and move on to the causes that do explain it.
Runflake takes the second position deliberately: it keeps speaking with the screen off and the phone in a pocket, and its announcements are heard even with the iPhone silent switch on, on the reasoning that a coaching cue is not media. By default it also lowers whatever music is playing while it speaks, and a runner can switch that off so music stays at full volume with the voice layered on top. How far the music drops is decided by the phone and not by the app.
A pre run check that takes two minutes
- Play the speech engine demoOn Android, open accessibility settings, then text to speech output, and press play. On an iPhone, turn on Speak Screen under Accessibility, Spoken Content, then swipe down with two fingers from the top of the screen (Apple, Hear iPhone speak the screen, checked 2 August 2026). Either way you are testing the engine and the installed voice without involving any running app.
- Start the music you will actually run toUse the same app and the same kind of content. Spoken word audio and music behave differently under audio focus, so testing with the wrong one proves nothing.
- Wear the headphones you will actually wearPair them and leave them connected. Bone conduction and open ear headsets can present as a different route from earbuds.
- Record a short walk past the first markerWalk far enough to cross the first announcement point, or set a short interval workout, so you hear a real cue rather than a settings preview.
- Lock the screen and pocket the phoneRecreate the state the run will be in. A cue that arrives with the screen on and fails with it locked points at the background cause.
- Check the recording afterwardsConfirm the distance kept accumulating for the whole walk. If it did not, fix the background problem before touching any audio setting.
When the app is working and the cue was dropped on purpose
Not every missing announcement is a fault.
A well behaved app drops cues on purpose, and knowing the rules stops you chasing a bug that does not exist. During a run a late announcement is a wrong announcement, because the number it carries stopped being true while it waited in a queue.
Runflake makes those rules explicit. A cue that has been waiting more than 12 seconds is thrown away instead of being read late, and if the satellite signal drops out and you cross several kilometre or mile markers at once, the coach announces only the last one instead of reading a backlog. Turning a setting off takes effect immediately, mid run, and turning the coach back on mid run does not make it replay a kilometre you already heard.
Spoken language is English or Korean only, and every other phone language falls back to English cues, which is worth knowing before you conclude that your language is broken.
Two more of its rules explain a cue that misbehaves rather than one that never arrives. Cues are ranked and a more urgent one cuts off a less urgent one already playing: pause, resume and finish outrank everything, turn and interval calls outrank the kilometre readout, and the optional pacer lines sit at the bottom. A split reading that stops halfway through a word was overtaken, not corrupted. Separately, while you are off a course the kilometre readout is muted so route guidance is not buried, but that muting expires after two minutes, so a runner who abandons the course still gets splits again. Runflake is built and is not yet published to the App Store or Google Play, so there is no download available today.
- A skipped marker right after a signal gap is expected, not a lost cue.
- A cue that stops mid sentence was cut off by a more urgent one, which is a ranking rule and not a fault.
- A cue category you switched off stays off from that moment, with no queue draining later.
- A phone language with no recorded script does not fail silently. It falls back.
Check the wording and its trigger before you decide something went wrong. That reference is in what running apps actually say out loud.
Common questions
- Does reinstalling a running app fix missing voice cues?
- Rarely. Reinstalling replaces the app but leaves the four things that actually go wrong untouched: the phone's speech engine and its installed voices, which app holds audio focus, the background restrictions the operating system applies, and the audio route a Bluetooth headset picks when it reconnects. Reinstalling does reset the app's own settings, which is why it sometimes appears to help.
- Why do I hear my music but not the announcements?
- Because music and spoken cues can travel by different paths. Music usually plays from a media player that already holds audio focus, while a cue is a short utterance that has to interrupt it. If the app never gets focus, or the utterance goes to a speech engine with no voice installed for your language, the music continues undisturbed and you hear nothing else.
- How can I tell a background kill from an audio problem?
- Look at the run itself, not the sound. If distance and elapsed time kept increasing while you heard nothing, the app was alive and the failure is in the audio path. If the distance stopped at roughly the moment the voice stopped, the app was suspended or terminated, and that is a background execution problem rather than a sound problem.
- Should I test voice cues before a long run?
- Yes, and it takes about two minutes. Play the speech engine demo in your phone's accessibility settings, start music, start a short recording with the headphones you plan to wear, walk far enough to cross the first announcement point, then lock the screen and put the phone where it will actually sit. Every failure described here shows up in that sequence.