Push-to-talk dictation for Android.
Phone Whisper lets you speak into most apps without switching keyboards. Tap the floating button, speak, tap again, and your text is inserted into the currently focused text field when the app exposes a standard Android input field.\
It supports:
- Local on-device transcription with sherpa-onnx
- Cloud transcription with any OpenAI-compatible STT API (OpenAI Whisper, OpenRouter, ...)
- Optional cleanup with an OpenAI-compatible chat model to fix punctuation and grammar
- Edge docking & semi-hide: Tucks smoothly into screen edge when idle (semi-transparent handle), adaptive to phones and tablets across orientations
- Double-tap wake up: Requires double-tap on edge dock to expand, preventing accidental touches
- Notification toggle: Ongoing notification bar button to quickly show or completely hide the floating window anytime
If you try it and it genuinely saves you time, consider sponsoring
- I like SwiftKey and want to keep it as keyboard but...
- Most keyboard dictation felt too inaccurate
- Gemini's voice input auto submits your transcription (which is pretty bad) so you can't edit it before sending
- Post processing yields much better results, specially adding a list of keywords and technical terms you often use
- Inserting text into the field you're already using lets you keep editing it like any other draft.
Grab the latest APK from GitHub Releases.
Open it on your phone, install it, then launch the app once to finish setup.
Requires JDK 17 and Android SDK.
git clone https://github.com/Ray4AI/phone-whisper.git && cd phone-whisper
make buildRequires JDK 17 and Android SDK.
git clone https://github.com/kafkasl/phone-whisper.git && cd phone-whisper
make buildAPK output:
app/build/outputs/apk/debug/app-debug.apkIf you use ADB:
make adb-install- A small overlay button floats on screen
- Tap once to start recording
- Tap again to stop
- Audio is transcribed locally or in the cloud
- The text is inserted into the focused text field
- If insertion fails, the text is copied to the clipboard
- Open Phone Whisper
- Grant the audio recording permission
- Enable the Accessibility Service
- Choose your transcription mode:
- Local: download a model in the app
- Cloud: configure an OpenAI-compatible STT endpoint (see below)
Once setup is done, the floating button is ready.
Any provider that implements OpenAI's POST /v1/audio/transcriptions works.
| Setting | OpenAI | OpenRouter |
|---|---|---|
| API Base URL | https://api.openai.com/v1 (default) |
https://openrouter.ai/api/v1 |
| Transcription model | whisper-1 |
microsoft/mai-transcribe-2 |
| Cleanup model | gpt-4o-mini |
e.g. openai/gpt-4o-mini |
The API Base URL row offers OpenAI and OpenRouter presets, or you can point it at any custom OpenAI-compatible endpoint.
Both transcription and cleanup support an arbitrary JSON object merged into the request body (Transcription extra body / Cleanup extra body). Extra keys override the defaults, so you can tune provider routing, reasoning, temperature, etc:
{ "temperature": 0.1, "provider": { "order": ["Azure"] } }{ "reasoning": { "effort": "high" } }Notes:
- Leaving the extra body empty sends a standard OpenAI-style multipart request (maximum compatibility with OpenAI and OpenRouter).
- When an extra body is set, the transcription request is sent as JSON with
base64-encoded audio instead, so nested options like
providerare supported. The multipart 25 MB cap no longer applies in this mode. - JSON is validated when you save; invalid input is rejected.
Phone Whisper uses Android Accessibility Service for one narrow reason: to insert dictated text into the currently focused text field across apps.
It does not replace your keyboard. It does not run background automation. It only acts after you explicitly tap the overlay button.
Phone Whisper supports two modes:
- Local mode: audio stays on-device
- Cloud mode: audio is sent directly from your device to the transcription endpoint you configure (OpenAI, OpenRouter, ...)
- Optional cleanup: transcript text is sent directly from your device to the chat endpoint you configure
I don't run a backend for this app. In cloud mode, requests go straight from your phone to your provider using your own API key.
Full policy: PRIVACY.md
Models are stored in app storage under:
/data/data/com.kafkasl.phonewhisper/files/models/Current catalog:
| Model | Size | Notes |
|---|---|---|
| Parakeet 110M | 100 MB | Best default |
| Whisper Base | 199 MB | Solid baseline |
| Parakeet 0.6B | 465 MB | Best quality |
| Moonshine Tiny | 103 MB | Fastest |
The app downloads and extracts models directly from the sherpa-onnx release archives.
make build # build debug APK
make test # run unit tests
make adb-install # build + install via ADB
make clean # clean build artifactsGitHub Actions builds a debug APK on every push to main (artifact:
phone-whisper-debug-apk). Pushing a tag like v0.4.1 additionally creates a
GitHub Release with the APK attached.
Phone Whisper works best in apps that use standard Android text fields. Some apps use custom text surfaces or terminal-style views, which may not support direct accessibility paste. When insertion is not possible, Phone Whisper falls back to copying the transcript to the clipboard.
Termux's main terminal area is not a standard Android text field, so direct insertion may not work there.
To use Phone Whisper in Termux:
- Focus Termux
- Swipe the extra keys row (
ESC,CTRL,ALT, arrows, etc.) left or right - Switch to Termux's native text input box
- Dictate there
Once text is inserted into the native input box, Termux sends it to the terminal normally.
- Accessibility permission is required for cross-app insertion
- Some apps may block paste or text injection
- Some apps use custom input surfaces instead of standard Android text fields
- Local models are large
- Cloud mode requires your own OpenAI API key
If Phone Whisper saves you time, you can sponsor the project on GitHub:
Personal project. Do whatever you want with it.