The problem: fast internet, bad calls
Godara had a fast connection, a router close to the laptop and a dedicated microphone. His calls still suffered from stuttering, audio and video falling out of sync, and random drops. Restarting the router, disconnecting other devices and closing bandwidth-heavy apps changed nothing.
His central point is that a speed test doesn't explain a bad call. Real-time video depends on latency, jitter (latency that swings around) and packet loss (the share of data that never arrives). A connection can show triple-digit Mbps and still do badly on all three.
His own numbers show the gap. Pinging Google looked fine, but Zoom's statistics page reported 8.3% packet loss and 74 ms jitter.
Measure the call itself first
Godara suggests a quick check: open Command Prompt and run ping google.com -n 25. If the times swing between, say, 10 ms and 150 ms, you have jitter. That test is limited, though. It measures round trips to one host over 25 probes. It isn't the path your call's audio and video take, so a clean ping doesn't clear your Wi-Fi. That is exactly what happened in his case.
The in-call stats are the better measure. Microsoft's Teams guidance gives these typical values:
- Teams' Call health view updates every 15 seconds (open it from More actions > Settings > Call health).
- Round-trip time under 200 ms.
- Received packet loss under 2%.
- Received audio jitter under 30 ms.
Those are Teams guideline figures, not universal thresholds. Godara's Zoom readings are well outside them and outside the 2% packet-loss mark he cites. Microsoft's Microsoft 365 network assessment also makes the same distinction. It scores Teams media quality from UDP latency, jitter and packet loss rather than from download speed.
The three settings that helped
You reach them by right-clicking your Wi-Fi adapter under Network adapters in Device Manager, then choosing Properties > Advanced.
1. Preferred Band: Prefer 5 GHz
- Godara's laptop stopped dropping to 2.4 GHz when a strong 5 GHz signal was available.
- The trade-off is range. 2.4 GHz reaches farther and passes through walls better.
- Microsoft's Surface guidance warns against forcing 5 GHz only, because many public hotspots still use 2.4 GHz. It also says that in crowded apartment buildings, temporarily using 5 GHz can reduce interference.
2. Channel Width: 20 MHz, on 2.4 GHz only
- He set this on the 2.4 GHz band and noticed a clear improvement when calling from a study farther from the router.
- Speed dropped, but video calls need only a few Mbps.
- Don't carry this over to 5 GHz. He didn't test it there.
- The setting's name and values vary by adapter. Dell's guide for Intel adapters lists the 802.11n channel width setting with a recommended value of Auto. That is the opposite of a fixed 20 MHz, so treat the 20 MHz choice as a targeted fix for a weak 2.4 GHz link.
3. Roaming Aggressiveness: Lowest
- This stops the adapter from constantly scanning for other access points. It scans only when the current signal is weak.
- Dell's guide for Intel adapters also recommends Lowest or Medium-Low for stationary home devices. It suggests Medium only where you physically move between access points.
- Microsoft's Surface page lists Medium as the default and says to raise aggressiveness only if needed in dense Wi-Fi environments. It adds that higher aggressiveness can drain the battery faster.
- If you have a mesh system or several access points and walk around during calls, stay on the default.
Settings he left alone
Godara left these at their defaults:
- The forced wireless modes (802.11a/b/g and 802.11n/ac/ax).
- Both "Wake on…" settings.
- Packet Coalescing.
His reasoning is that they either won't help or could make things worse. He didn't publish separate measurements for each one, so this is judgment rather than test data. Microsoft's own advice for Surface devices is also to keep default Wi-Fi settings where possible.
Your adapter may not have these options
Advanced properties are adapter-specific, so another laptop may show different names or fewer options. Microsoft's Wi-Fi troubleshooting page mentions looking for a Wireless Mode or Band setting. The PowerShell commands Get-NetAdapterAdvancedProperty and Set-NetAdapterAdvancedProperty can list and change what your driver exposes, as the NeoTeo guide notes. Get the exact property name from the first command before using the second.
A safe way to test
- Run a real call and record the packet loss and jitter from the app's stats. Note the time and where you were sitting.
- Write down the current value of the setting you're about to change.
- Change one setting, click OK, and let the adapter reconnect. The connection may drop briefly.
- Repeat a similar call and compare the stats.
- Revert if the result is worse. Changing several settings at once means you can't tell which one mattered.
Do the basics first
Godara says the adapter tweaks wouldn't have mattered without these basics:
- Sit in the same room as the router.
- Pause heavy downloads and streaming.
- Turn on Quality of Service (QoS) in the router.
- Switch off power-saving features.
- Turn off Windows Delivery Optimization.
Those are his reported setup, not tested findings. Microsoft's Windows Wi-Fi guide independently covers some related steps:
- Ping your router (the default gateway) to check the local wireless link.
- Compare against a wired connection if you can.
- Disable power saving on the Wi-Fi adapter.
- Check the driver version and date in Device Manager.
- Use network reset only as a last resort.
Our take
The useful lesson is the method, not the three values. Check the call's own stats, change one setting at a time, and accept that the right answer depends on how far you sit from the router and whether you move around. Lowest roaming aggressiveness and a preferred band are low-risk to try, and Dell's guidance backs both for a stationary home laptop. Narrowing the channel width costs speed, so try it last.
This is a single writer's setup. No adapter model, driver version or before-and-after data was published, so these numbers prove nothing about your hardware.