Setup Wispr Flow on Android (Android Settings)

Google Pixel and stock Android

Pixel devices need no manufacturer-specific setup beyond the core permissions above. For best reliability, set Wispr Flow's battery usage to Unrestricted.

1. Set Wispr Flow's battery usage to Unrestricted in Settings → Apps → Wispr Flow → Battery.

2. Open any app with a text field. The Flow Bubble should appear above your keyboard.

3. Tap the Flow Bubble (or long-press for push-to-talk) and dictate a short phrase. If text appears in the field, setup is complete.

Samsung (One UI)

One UI's battery manager will close Flow in the background unless you mark it Unrestricted.

1. Complete the core permission steps above (Overlay, Accessibility, Microphone).

2. Add Wispr Flow to Never sleeping apps via Settings → Battery → Background usage limits → Never sleeping apps.

3. Set Wispr Flow's battery usage to Unrestricted in Settings → Apps → Wispr Flow → Battery.

4. Disable Put unused apps to sleep under Background usage limits.

5. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

Xiaomi / Redmi / POCO (MIUI / HyperOS)

MIUI and HyperOS require several separate steps for Flow to keep running reliably in the background.

1. Complete the core permission steps above (Overlay, Accessibility, Microphone).

2. Enable Autostart for Wispr Flow in Settings → Apps → Manage apps → Wispr Flow → Autostart.

3. Lock Wispr Flow in Recent Apps (swipe down on the app card).

4. Set Battery saver to No restrictions on the Battery Details screen for Wispr Flow.

5. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

Huawei and Honor

Huawei and Honor devices aggressively close background apps unless App launch and battery optimization are configured for Flow.

1. Complete the core permission steps above.

2. Open Settings → Apps → App launch → Wispr Flow, switch it to Manage manually, and turn on all three toggles (Auto-launch, Secondary launch, Run in background).

3. Set Wispr Flow's battery optimization to Don't allow.

4. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

Oppo

Oppo devices use a different set of toggles to keep Flow running in the background.

1. Complete the core permission steps above.

2. Open Settings → App Management → App List → Wispr Flow and enable Allow Auto-Launch and Allow Background Activity.

3. Disable power saving mode, or add Wispr Flow to its exceptions.

4. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

OnePlus

OnePlus devices need Flow exempted from battery optimization, App Auto-Launch enabled, and Flow locked in recent apps.

1. Complete the core permission steps above.

2. Enable App Auto-Launch for Wispr Flow.

3. Set Wispr Flow's battery optimization to Don't optimize.

4. Lock Wispr Flow in recent apps so it isn't closed when you swipe it away.

5. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

Motorola / Lenovo

These devices need Flow exempted from battery optimization and locked in recent apps to keep the bubble alive in the background.

1. Complete the core permission steps above.

2. Set Wispr Flow's battery optimization to Don't optimize.

3. Lock Wispr Flow in recent apps so it isn't closed when you swipe it away.

4. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

Transsion (Tecno, Infinix, itel)

Transsion devices require enabling Autostart and locking Flow in recent apps in addition to battery exemption.

1. Enable Autostart for Wispr Flow in Settings → Security → Permissions → Autostart.

2. Complete the core permission steps above.

3. Set Wispr Flow's battery optimization to Don't optimize.

4. Lock Wispr Flow in recent apps so it isn't closed when you swipe it away.

5. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

Realme

Realme devices need Flow exempted from battery optimization and Auto Launch enabled to keep the bubble alive in the background.

1. Complete the core permission steps above.

2. Enable Auto Launch and Allow Background Activity for Wispr Flow.

3. Set Wispr Flow's battery optimization to Not optimized.

4. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

Vivo

Vivo devices need Autostart enabled and Flow locked in recent apps to keep running in the background.

1. Complete the core permission steps above.

2. Enable Autostart via Settings → More Settings → Applications → Autostart, and toggle Wispr Flow on.

3. Lock Wispr Flow in recent apps so it isn't closed when you swipe it away.

4. Test by focusing a text field and tapping the Flow Bubble. If dictated text appears, setup is complete.

Flow Bubble shows a warning triangle, a restart icon, or a pulsing spinner

Flow signals accessibility service disruptions with one of three bubble repair states:

• Pulsing bubble with a loading spinner: Flow is reconnecting. The bubble is not tappable during this state and resolves on its own once the connection is restored. If reconnection doesn't succeed, it automatically escalates to the restart icon state below.

• Restart / retry icon ("Flow isn't responding"): Accessibility permission is still granted, but the service has stopped. Tap the bubble to restart Flow. This does not open Accessibility Settings.

• Warning triangle bubble: Accessibility permission has been revoked in Settings. Tap the bubble to open Flow's in-app accessibility repair screen and re-enable Wispr Flow.

If the warning triangle persists after re-enabling accessibility permission, update Wispr Flow to the latest version from the Google Play Store and restart the app.

Recovery notifications: what the two types mean

Flow can send two different recovery notifications, with different copy and different actions:

• "Wispr Flow needs attention" / "Re-enable accessibility for Wispr Flow to keep working." Tapping this notification opens the in-app accessibility repair screen.

• "Flow isn't responding" / "Tap to restart Wispr Flow." Tapping this notification opens the app home — the service has stopped but accessibility permission is still granted.

Bugs fixed in recent updates

The following issues were fixed in recent versions of Wispr Flow. Update to the latest version from the Google Play Store to resolve any of them.

• Dictation didn't work in Chrome search boxes: Tapping the Flow Bubble in Chrome's search box would not insert dictated text.

• Flow Bubble was clipped in landscape orientation on some devices: On devices with navigation bars or display cutouts, the Flow Bubble could appear partially cut off when the device was rotated to landscape or reverse-landscape.

• Flow Bubble didn't appear after enabling the accessibility service: The main Flow service did not start automatically after the accessibility service was enabled. Restart the app after updating, then tap into a text field to confirm the bubble appears.

• Flow Bubble flickered or behaved erratically when tapping into text fields: The Flow Bubble could flicker or behave erratically when you tapped into a text field. It now behaves correctly.

• Text inserted twice in chat apps: In some messaging apps with unreliable input field behavior (WhatsApp, Telegram, Messenger, Signal, Slack), dictated text could be inserted twice.

• Flow Bubble did not start automatically after device restart: When accessibility permission was already granted, the Flow Bubble now starts automatically when your device boots.

• Snooze lost when the keyboard opened: Putting Flow into snooze and then opening the keyboard would cancel snooze. Snooze now stays active when the keyboard appears.

• Shake-to-unsnooze stopped working: Shaking the device to exit snooze mode was not responding. Shake-to-unsnooze works again.

• Snooze card stayed on screen after force-stopping Flow: The snooze card could get stuck on screen after the app was force-stopped. It now clears correctly.

• Flow Bubble didn't shrink on search fields: The bubble did not reduce in size when focused on search fields. It now shrinks as expected.

• Flow Bubble positioned incorrectly in landscape: The bubble could appear in the wrong position when the device was rotated to landscape. Positioning is now correct in landscape orientation.

• Microphone re-grant after revocation: If microphone permission was revoked while Flow was starting up, the Flow Bubble and overlay now remain visible so you can re-grant microphone permission without relaunching the app.

• Re-granting overlay permission from the home screen didn't return to the app: Re-granting the overlay permission from the home screen error card now reliably returns Flow to the foreground after you grant it in Settings.

• Flow Bubble did not appear when replying to notifications inline: The Flow Bubble was missing when replying to notifications from the notification shade. The Flow Bubble now appears in inline notification reply boxes on Pixel/AOSP, Samsung, Xiaomi/MIUI, OPPO/OnePlus (ColorOS), Realme, Vivo, Asus ROG UI, and Huawei.

• Flow Bubble did not appear in browser address bars: The Flow Bubble was missing when tapping the address bar in Chrome, Firefox, Edge, Brave, Samsung Internet, and other supported browsers. The bubble now appears so you can dictate URLs and search queries by voice.

• Tapping "Go to Settings" multiple times caused background problems: Tapping the button more than once when granting overlay or accessibility permission could trigger overlapping checks. Tapping it multiple times is now safe.

• Flow did not return to the foreground after granting accessibility permission: During onboarding, Flow would sometimes stay in the background after permission was granted. Flow now reliably brings itself back to the foreground as soon as the permission is granted.

• Flow Bubble disappeared after the system closed the app: If the system force-stopped Flow, the bubble would not return on its own. Flow now restarts automatically after unexpected system closures (not after a manual sign-out). If background restart fails, Flow recovers the next time you bring the app to the foreground.

• Accessibility permission revoked with no easy way to restore it: Re-granting accessibility permission previously required navigating through system settings. Flow now detects this and takes you directly to an in-app screen to restore it.

• Accessibility permission silently turned off on some devices: On some devices with aggressive battery managers, Android may silently revoke Flow's accessibility permission, causing it to stop without warning. Flow detects this and sends a notification — tapping it opens Flow's in-app accessibility repair screen.

• Style or formatting choices not applied: Changing a style or formatting setting previously required restarting Flow. Selections now apply immediately on your next dictation.

• Recording bubble cut off: The recording bubble could appear visually clipped on some devices.

• Onboarding incorrect on foldables: On foldable phones using the inner display, onboarding screens could display with buttons not pinned to the bottom.

• Dictionary or Snippets list appeared empty: Reapplying a search or filter in Dictionary or Snippets could incorrectly show an empty list even when results existed.

Why does Flow need accessibility permission?

Flow uses Android's accessibility service to detect when you focus a text field and to insert dictated text into it. Without it, the Flow Bubble cannot read or write into other apps.

Why does Flow need Display Over Other Apps permission?

The Flow Bubble is a floating overlay that appears on top of whatever app you're using. Android requires explicit overlay permission for any app that draws on top of others.

What happens if I allow notifications?

Allowing notifications lets Flow alert you if a permission is silently revoked (so you can restore it quickly) and send you helpful tips and updates tied to your account — such as onboarding guidance and reminders. You can manage notification preferences at any time in Settings → Apps → Wispr Flow → Notifications.

Where do I change Flow Bubble size, opacity, or privacy mode?

Open Flow and go to Settings. General contains Languages, Flow Bubble Size, and Flow Bubble Opacity. Data & Privacy contains the Privacy mode toggle to keep data stored only on your device.

• Flow Bubble Size has four steps: 0.70×, 0.85× (default), 1.00×, and 1.15×. The Bubble Size screen also includes three optional shrink toggles: Shrink the bubble when not in use, Shrink to a dot, and Shrink the bubble in search fields.

• Flow Bubble Opacity has five steps: 20%, 40%, 60%, 80% (default), and 100%.

Both the Bubble Size and Bubble Opacity screens include a live preview and a Reset button.

Will Flow work offline?

No. Flow requires an internet connection to transcribe audio. A weak connection may cause delays or failed transcriptions.

Can I use Flow with a Bluetooth headset?

Yes. Flow uses whichever microphone Android has selected as the active input. Connect your Bluetooth headset before tapping the Flow Bubble.

Flow stopped working after my phone closed it in the background — do I need to reinstall?

No. Flow restarts itself automatically. If the Flow Bubble shows a warning triangle, tap it to open Flow's accessibility repair screen and re-enable Wispr Flow.

Does Flow start automatically when I restart my phone?

Yes. Once accessibility permission is granted, Flow starts automatically when your device boots, and also after app updates from the Play Store. On some devices with aggressive battery managers (Xiaomi, Vivo, Oppo, Samsung), the accessibility service may not reconnect automatically.

Can I dictate in browser address bars and notification replies?

Yes. The Flow Bubble appears in address bars across Chrome, Firefox, Edge, Brave, Samsung Internet, Opera, Vivaldi, DuckDuckGo, Kiwi, UC Browser, Yandex, and many other Chromium-based browsers, and in inline notification reply boxes (for example, replying to a WhatsApp message from the notification shade).