If Discord or in-game chat sounds underwater on LTE, these three fixes stop the stutter without nuking your whole phone.

Stop your phone from flipping between Wi-Fi and LTE mid-match

If your voice chat gets that metallic "robot" thing right when you walk from the couch to the kitchen, it is usually not Discord being weird. It is your phone trying to be helpful and quietly bouncing between Wi-Fi and cellular because the Wi-Fi signal dipped for half a second. Games can ride that out with client prediction. Voice chat cannot. You hear it immediately: syllables stretch, then everyone starts talking over you because they think you stopped listening.

Two settings fix most of it, and neither involves rebooting anything. First, when you sit down for ranked, commit to one connection. If you are on Wi-Fi, turn off cellular data for the session (iOS: Settings > Cellular; Android: quick toggles). If you are on LTE or 5G because your home Wi-Fi is sketchy, turn Wi-Fi off entirely so the phone cannot flirt with that one-bar network your neighbor's router is blasting into your living room.

Second, kill "Wi-Fi Assist" / "Adaptive connectivity" behavior that swaps networks behind your back. On iPhone, Wi-Fi Assist lives at the bottom of the Cellular screen. On Pixel/Samsung, it is usually under Network/Internet settings with wording like "Switch to mobile data automatically" or "Adaptive connectivity." The reason I bother: in Call of Duty: Mobile or PUBG Mobile, I can tolerate a brief ping spike. In a clutch callout, I cannot tolerate my mic turning into a fax machine. After you lock your connection, run a quick check in the app itself: start a private Discord call and pace around your usual play spot. If your audio stays clean while you move, you just removed the most common cause of "my comms are fine, then suddenly they are not."

Reset Bluetooth audio without unpairing everything

There is a specific kind of bad voice chat that is not lag. You are not cutting out, you are just narrow and crunchy, like you are calling in from a drive-thru speaker. That is Bluetooth flipping into the low-bandwidth "headset" profile (HFP/HSP) at the wrong time, usually after you bounced between apps. The classic setup is: you were watching a clip, swapped to your game, Discord grabbed the mic, then the audio never came back to the higher-quality profile. AirPods do this. So do a lot of cheaper earbuds. Some gaming-branded Bluetooth sets do it too, even if the box says "low latency."

The fix I do now is a quick Bluetooth reset that does not involve forgetting the device and re-pairing like it is 2014. Step one: in Control Center (iOS) or quick settings (Android), turn Bluetooth off for ten seconds, then back on. Step two: in Discord, tap the voice channel and toggle the output device if the app gives you a picker (speaker, phone, headset). Step three: if you are on Android, open Settings > Connected devices > your earbuds, then temporarily turn off "Phone calls" while leaving "Media audio" on, wait a beat, and turn "Phone calls" back on. That little flip forces the mic route to renegotiate.

I test it the same way every time: open Discord's voice settings and use the mic test, then say a sentence with plosives. "Push B, then peek." If the P and B pop cleanly and you do not hear that underwater compression, you are back on the good path. In-game voice in titles like Fortnite or Warzone Mobile tends to expose this faster than Discord because it is less forgiving. And if you are using a controller with a 3.5 mm jack (Backbone, Razer Kishi V2 with a wired headset), this is one of the quiet reasons I still recommend going wired when you care about comms. Bluetooth is convenient. It is also moody.

Force Discord to behave on iPhone: lock the mic and stop the silence

This one is for the iPhone players who swear they are talking and nobody is responding. Your mic icon is lit. Discord shows you in the channel. Then a teammate finally says, "Dude, you were muted for the last three fights." Half the time it is not a mute button. It is iOS deciding an app in the background does not deserve uninterrupted microphone time, especially if your screen goes dark or you swapped to check a text.

Here is what I do before a long session of mobile ranked where comms matter. First, make sure Discord has mic permission (Settings > Privacy & Security > Microphone). Sounds obvious, but iOS updates and app reinstalls have a talent for flipping this. Second, turn off Low Power Mode. Low Power Mode is great when you are doomscrolling. It is terrible when you are trying to keep a steady upstream for voice while a game is hammering the GPU. Third, keep Discord in the foreground when you connect, then switch to your game. I know that sounds like superstition, but the initial handshake is where I see the most "connected but silent" behavior.

Now the part that actually changes outcomes: in Discord, go to Voice settings and set Input Mode to "Voice Activity" if Push-to-Talk is unreliable on mobile, then disable any aggressive noise suppression if your mic keeps gating words off. Krisp is useful, but on phone mics it can chop the start of callouts. I would rather my teammate hear a little fan noise than miss "one shot" entirely. Also, if you are using AirPods, try turning off "Automatic Ear Detection" for the session. That sensor is great until one earbud shifts and iOS thinks you took it out, then your audio route does a tiny panic dance.

When I am done setting this, I do a dumb, practical test: I join a voice channel alone, lock my phone, wait 30 seconds, unlock, and talk. If the first word shows up on the meter, I trust it for the night. If it does not, I fix it then, not mid-fight.