How to choose a router bandwidth of 20/40/80/160MHz? Even with 160MHz on, the phone is still 1201M. I've stepped through all three hurdles one by one

when my home broadband upgraded to gigabit, I changed my AX3000T's 5G bandwidth from 80MHz to 160MHz, thinking that now my phone could negotiate up to 2402M. Checking backend, the phone was obediently hanging on the 1201M, completely unmoving. After struggling all night, I finally realized that bandwidth isn't something the router can decide alone—phones, channel segments, radar—these three gates block you one by one.

first distinguish between channel and bandwidth: which channel is a pipe running, and how wide is a pipeline built

many people get confused when they enter the backend; the channel and bandwidth are side by side, and they look similar. My understanding is to use a road as an analogy: channel is which lane your car is running on, and bandwidth is how many lanes have been built on that road wide. The two parameters are independent, each managing its own affairs.

The

2.4G band covers only 83.5MHz, divided into 13 lanes, each only 20MHz wide, making it extremely crowded. So 2.4G bandwidth is naturally hard to reach; with 40MHz capped, it still has to occupy other people's lanes. The 5G band is spacious; a 20MHz channel can merge with a neighboring channel. Two channels merging into one channel is 40MHz, four channels merging into one channel is 80MHz, and eight channels merging into one channel is 160MHz. The professional term for this merging is "channel bundling." The bandwidth option you see in the backend selects several channels.

to elaborate on the term 'bundling': '40MHz' means you bundle your 20MHz channel together with the neighboring one; 80MHz means bundle four wires together; 160MHz is eight bundles together. The more you bundle, the wider the lane and the fiercer the traffic, but the more space it occupies—this cost will recur later.

The

5G band channel is divided into two segments: low 36 to 64, high 149 to 165, with a large middle section for radar and other routers, which cannot be touched by home routers. Remember this two-stage layout; it will be used when discussing the 160MHz pitfall.

As for which lane has fewer neighbors or how to use your phone to check for interference, I covered this thoroughly in my on channel interference troubleshooting before, so I won't repeat it here. Today, we'll only talk about bandwidth.

Doubling bandwidth and doubling speed: I've calculated this three times

to start with the conclusion: negotiation rate is roughly equal to bandwidth× spatial flow × modulation efficiency , multiplying the three components. Bandwidth is the easiest part to understand; with each level flip, the rate basically doubles.

use the most common 2x2 antenna phone at home (WiFi 6 model), and the numbers look like this:

understand, the numbers your phone has been hanging around for years—867M, 1201M, 2402M—are multiplied this way. Here's a premise to mention: negotiation is "just lower but not high"—routers 4x4, phones 2x2, counted as 2x2; The router is set to 160MHz, but the phone only supports 80MHz, so 80MHz is counted as the standard. about the space flow article I have carefully calculated this shortcoming, so I'll just note this conclusion here.

so when bandwidth is increased from 80 to 160, the speed can indeed go from 1201 to 2402, doubling on paper. But don't get too excited—the 160MHz hurdle is still ahead, so first solidify the basics.

2. 4G stays at 20MHz, 5G starts at 80MHz

2.4G's advice is simple: lock at 20MHz, don't touch 40MHz. As mentioned earlier, each of the 13 lanes is only 20MHz wide. If you turn on 40MHz, you'll take up the entrance of two or three households at once. When neighbors have a lot of signal, they start fighting each other. In tests of heavy interference, 40MHz is not only not fast but actually slower. My home has 2.4G at 20MHz channel 1 all year round, and it's as stable as an old dog.

5G is big, 80MHz is used with your eyes closed, and you can pick anywhere from 149 onward. My main setup is 5G 80MHz with fixed channel 149, negotiated 1201M, and in actual tests, it can run around 940M, just enough for gigabit broadband to fill .

also has a counterintuitive experience: in areas with poor signal, lowering the bandwidth by one notch can actually be more stable. For devices with many walls and far from routers, 80MHz broadband requires high signal quality, and if negotiation fails, the chain drops; Manually locking 40MHz is narrow but requires low signal and can connect without disconnecting. The old laptop in my study was revived at 40MHz. The speed is a bit low, but it's better than interrupted feed.

did you turn on a 160MHz phone or 1201M? Three hurdles are overcome one by one

back to the pitfall I fell into at the beginning. The router's bandwidth is set to 160, but the phone doesn't recognize it. There are basically three reasons, sorted by probability:

Hurdle One: The phone itself does not support 160MHz. these aren't specs for flagship phones; many mid-range phones cap at 80MHz, while Snapdragon 8 series and Dimensity flagships only have 160MHz. Moreover, the phone supports two modes: "160MHz" and "80+80MHz," with the first mode basically available in China. The method is quite basic: Go to the official website and check the specs list, looking for 'Wi-Fi 6 160MHz'; Or just check the negotiated speed—Android checks 'link speed' on the WiFi detail page, Windows runs a netsh wlan show interfaces checks the reception speed: 1201M is the 80MHz range, 2402M is the 160MHz range.

Hurdle 2: The channel falls between 149 and 161. This is the darkest trap, and many people get stuck here. The four lanes 149/153/157/161 combined are only 80MHz wide (the 165 lanes are not bundled), so physically, they cannot form 160MHz. To reach 160MHz, the channel must be moved to the low-frequency range from 36 to 64. I checked Huawei's official response to users, and the original message was: when the channel is set to 149-161, you can't set the 160MHz bandwidth, so you need to switch to a lower channel of 36-64 and try again. I struggled on 149 for a long time, but ended up heading in the wrong direction.

Obstacle 3: The 52/56/60/64 channels in the low-frequency band are DFS channels, so you have to make way for the radar. these channels share frequency bands with weather radar, routers must first listen for radar signals before using them. If radar is truly detected (sometimes a false alarm), the router will automatically reduce the bandwidth back to 80MHz to avoid detection. ASUS's official FAQ also clearly states: even if the terminal supports 160MHz, when placed on the DFS channel, the device may only connect to 80MHz.

there's a strange phenomenon that explains it: during the day your phone still has 2402M, but at night it changes to 1201M. It doesn't necessarily mean the router is broken; it's probably because it hit the radar during the avoidance period. I later figured it out: when wrote the MLO , my phone was locked at 80MHz, and the root was the DFS mechanism.

there's another issue to settle in advance: even if 160MHz is negotiated, 2402M will only be useful intranet—like transferring from phone to NAS or between computers. Your broadband gigabit port is capped at 940M, but foreign downloads at 2402M are nowhere near enough—basically there's only one car driving on an eight-lane road. Think about others living in apartment buildings: when you activate 160MHz, all eight channels are under your name, while your neighbors' 80MHz is suppressed by you—put yourself in their shoes.

Here's the troubleshooting order: First, confirm if your phone supports 160MHz (official specs). Try negotiating → router bandwidth to 160M→ If it doesn't reach 2402M, check if the channel is moving from 149-161 →to 36-64→ or if it drops back to 1201M at night. That's DFS avoidance—accept it or revert to 80MHz. Bandwidth is often a different matter looks good on paper and is stable to use. In the end, my home went back to 80MHz with 149 and 2402M for a couple of days as a trial card.