Android Phone as a Microphone for a Bluetooth Speaker
Yes. An Android phone works as a microphone for a Bluetooth speaker, and the app this site was built around is on Google Play, free, alongside the iOS version. A mic-to-speaker app opens the phone's microphone and plays it straight out through whatever output Android is already using. The delay you hear comes from Bluetooth itself rather than from the app, and it behaves the same way on every phone.
How an Android phone becomes the microphone
The mechanism is unglamorous, which is why it works. Android is already sending audio to your speaker over A2DP because you paired the two in Settings. A mic-to-speaker app opens the microphone, applies some gain, optionally runs the samples through a filter or two, and writes them into the same output stream music would use. The speaker never learns it has been promoted to a PA system; it is playing audio that happens to be your voice from a fraction of a second ago.
Two consequences follow, and they are the two things people get wrong:
- The app is not pairing anything. Pairing happens in Android's Bluetooth settings. Android does hand apps pairing APIs if a developer wants them, and has since roughly Android 4.4 with
createBond, with a companion-device flow added in Android 8.0. A mic-to-speaker app has no use for either, because it simply plays into whatever output the system has already selected. If the speaker is not already connected and playing, fix that in Settings rather than in the app. - The phone is the microphone, not the receiver. You cannot reverse the arrow and have the speaker send sound to the phone. Plenty of Bluetooth speakers do contain a small microphone for speakerphone calls and voice assistants, but almost none expose it as a PA input, and the karaoke models that take a microphone do it through a physical jack on the cabinet rather than the radio link. The long version is in the guide on whether a Bluetooth speaker can take a microphone input.
Setting it up, start to finish
Five steps, in this order, because the order is what most failed attempts get wrong.
- Pair and connect the speaker in Android's Bluetooth settings. Put the speaker in pairing mode, tap it in the list, wait for it to say Connected.
- Confirm it is the active output. Play a few seconds of music and listen to where the sound lands. Android will happily hold a Bluetooth connection while still routing playback to the phone's own speaker, and the output picker in the volume panel is where you correct that.
- Open the app and grant the microphone permission. Bluetooth mic: Mic to Speaker is free on Google Play and free on the App Store, so a mixed household can run the same setup on either phone. It works offline, keeps no account, records nothing and stores nothing.
- Bring the level up slowly. Gain runs from 0 to 200 percent. Start low, speak 15 to 20 centimetres from the phone, and raise it only until you are comfortably audible at the far side of the room.
- Pick a voice preset if you want one. Normal applies no filtering at all. Deep, Warm, Bright, Space, Radio and Megaphone are filter sets; Robot adds a 50 Hz ring modulator on top. For announcements, Normal or Megaphone are the two that stay intelligible.
If you want to test the idea before installing anything, the live mic monitor on this site is a web page: it opens your microphone in Chrome, gives you the same 0 to 200 percent gain control and a level meter, and plays the result out of whichever output your phone is using. It is the fastest way to find out whether the idea works in your room. Two other pages run the same way on Android: the Bluetooth microphone latency test, which plays a 30 ms chirp, records it back through the microphone, cross-correlates the two signals across five runs and reports the median round trip with the air time subtracted, and the microphone test for input level, peak, sample rate and a five-second record-and-playback check.
Do the room test before the party, not during it. Connect the speaker, open the app or the monitor, walk to the far corner while someone talks into the phone, and listen for the delay and for the point where the speaker starts to howl.
The delay, and why no app removes it
Bluetooth does not let any app, on any platform, hand you zero-latency audio. The delay lives in the codec's encode and decode stages and in the speaker's own buffer, both of them outside the reach of anything running on the phone. An app that claims otherwise is describing something the radio link does not allow. What you can do is measure your own chain and choose a codec, which is a real lever even though it is a modest one.
| Codec or link | Reported latency | Where you meet it on Android |
|---|---|---|
| A2DP end to end | Roughly 100–300 ms (Hollyland) | The profile all music streaming rides on |
| SBC | Quoted as 100–150 ms by some sources, 150–300 ms by others | The mandatory fallback; every speaker supports it |
| AAC | Roughly 100–200 ms | Negotiated with most speakers and most phones |
| aptX Low Latency | About 40 ms (Qualcomm) | Needs support at both ends; almost no speakers have it |
| LC3 / LE Audio | About 20–30 ms (Bluetooth SIG) | Android 13 or later, LE Audio hardware at both ends |
| Dedicated 2.4 GHz wireless mic | Under 20 ms | Not Bluetooth at all |
Those ranges are wide because the sources genuinely disagree, and averaging them into one number would be dishonest. The comparison is unpacked with its sources in SBC, AAC and aptX latency, and the practical consequences are in Bluetooth microphone delay.
What matters is where those numbers land against perception. Under about 20 ms you will not notice. At 40 to 50 ms lip sync starts to look visibly wrong. Past about 100 ms it feels like a bad phone call, and hearing your own voice come back late is far more distracting than hearing someone else's, an asymmetry covered in how much audio delay is actually noticeable. Even a good result on a typical phone and speaker sits where a singer will fight it and a person making an announcement will not care.
The codec picker, the one lever Android gives you
Since Android 8.0 the platform can negotiate AAC, aptX, aptX HD and LDAC on top of the mandatory SBC, and it exposes the choice in Developer options. Reach it by opening Settings, About phone, then tapping Build number seven times; Developer options then appears under System, and inside it sits Bluetooth audio codec, along with sample rate, bits per sample and channel mode. iOS has no equivalent picker, so this is the genuine extra control an Android user has.
Be clear about what it does. Switching codec changes latency somewhat, not dramatically: you are moving between the rows of the table above, not stepping outside them. LDAC at its highest quality setting buys audio bandwidth rather than speed. The list also only offers what both ends support, so aptX Low Latency on a speaker that lacks it drops you quietly back to SBC, and the selection does not always survive a reconnection.
Availability depends on the handset rather than on the Android version. Only the LDAC encoder actually ships in AOSP. aptX and aptX HD are proprietary Qualcomm code that each manufacturer licenses separately, so whether your phone can send them is a property of that phone, and the picker greys out anything it cannot do.
Trust a measurement over the menu. Run the latency test before and after you change the codec, on the speaker you are actually going to use. A codec name in a dropdown is a request; the number the test gives you is the result.
The A2DP to HFP trap
If the Bluetooth device you connect has its own microphone and something asks for it, the link falls off stereo A2DP onto the HFP headset profile and quality collapses to narrowband mono. This is a property of Bluetooth, so it happens the same way on Android and on iOS, and it is set out in the guide on why Bluetooth audio quality drops when the mic turns on.
The way around it is the whole point of this setup. Use the phone's own microphone and keep the Bluetooth link as a one-way playback path, and there is nothing to renegotiate. A plain speaker with no microphone cannot trigger the profile switch at all, which is why phone-mic-in, speaker-out sounds better than talking into a headset.
When the Android Bluetooth microphone is not working
Most reports of an Android Bluetooth microphone not working come down to one of these:
- The speaker is connected but not selected as output. Start music first, confirm where it comes out, then open the app.
- Microphone permission was never granted, or was granted as "only this time" and has expired. Check the app's permissions page rather than waiting for a prompt.
- Another app holds the microphone. A call, a recorder or a video app in the background can keep the input locked.
- Battery optimisation suspended the app. Several Android skins are aggressive about background audio; exclude the app if you need it running with the screen off.
- You expected the headset's microphone to be used. That forces the link to HFP and the output quality drops with it. Stereo A2DP playback and the headset microphone cannot both be live.
- The gain is simply too low. Speak 15 to 20 cm from the phone. Phone microphones are tuned for a close talker, not a room.
Feedback is what actually ruins the evening
Delay annoys people. Feedback ends the demonstration. The speaker plays your amplified voice, the phone's microphone hears the speaker, and the system re-amplifies its own output until it screams. It happens fastest when the phone is close to the speaker, the gain is high, and the walls are hard.
The fixes are physical and boring: put distance between phone and speaker, point the speaker away from the phone, keep the gain at the lowest usable level, and turn the volume down before you walk anywhere. The guide to microphone feedback with a Bluetooth speaker works through the geometry. The app reads the live output route on both platforms and caps the gain at 0.6 when the device's own speaker is the output, because that configuration is a guaranteed howl; the browser monitor applies a comparable guard.
When a phone is the wrong tool
A phone into a Bluetooth speaker is good for announcements, a guided tour, a toast at a small party, or a parent trying to be heard across a garden. It is a poor choice for singing, for anything filmed, and for anything that has to line up with music: the delay stays where it is and you cannot practise your way out of it.
If you need better, spend money on the right layer. A cable into a powered speaker costs little and drops the delay to the millisecond range, the gap laid out in wired versus Bluetooth microphone latency. A dedicated 2.4 GHz wireless microphone system stays under 20 ms and does not use Bluetooth at all. Neither is an app, and paying for a mic-to-speaker app in the hope that it fixes latency is money spent in the wrong place.
If there is an iPhone in the house too, the same setup is covered step by step in connecting an iPhone microphone to a Bluetooth speaker. Otherwise install the app on the Android phone you already own, or open the browser monitor first, measure your real delay, and decide from a number rather than a product description.
Hear it for yourself, without installing anything
Hear your own microphone through your speakers or headphones, with the app’s gain range and its eight voice presets.