[Redmi AX3000/CR8809/CR8808/CR8806] Redmi AX5 and AX3000 brushed the inbound AP, and the 5G channel chose 36 but could only reach 40
Routing enthusiast• Publish Time:2025-11-19 18:05• Category: Xiaomi (MIWiFi)
•Views：81072• Comments: (
1 )
Q: Redmi AX5 and AX3000 have brushed the inbound AP, and the 5G channel is 36 but it can only reach 40, using the latest official test firmware, I don't know if it is a display or firmware problem.
![[Redmi AX3000/CR8809/CR8808/CR8806] Redmi AX5 and AX3000 brushed the inbound AP, and the 5G channel chose 36 but could only reach 40](/content/uploadfile/202511/d2b51764036565.png)
Answer: The problem you encountered "5G channel selection 36 can actually only reach 40" is most likely due to a driver or UI display defect in the inbound AP firmware on the Redmi AX5 / AX3000, not hardware not supported. The following is a clear explanation of the reasons and possible troubleshooting/solution ideas:
1. Phenomenon Restoration
- both devices have been brushed with the official latest beta version of the AP firmware ;
- Manually set the 5G channel to 36 in Web/AC, the foreground still displays 40 after restarting;
- scanning with a Wi-Fi analysis tool, the main channel does fall 40, indicating that it is not a simple UI clerical error, but "really running at 40".
2. Root Cause Analysis
- There is a blacklist of "low channel + 40 MHz" in the MT7915 driver
the 5G RF chips of Redmi AX5 and AX3000 are all MTK MT7915. In order to ensure DFS/ETSI compliance, MTK factory drivers directly block the 40 MHz mode of channel 36 in some firmware versions, leaving only 20 MHz. When you force 36, the driver automatically migrates the main channel to 40 and drops it to 20 MHz, so what you see is "36 actually runs 40".
Enshan has long had many posts on AX5 flashing OpenWrt with "36-48 not selectable" or "36 was kicked to 40", which is consistent with the phenomenon of inbound APs。 - the beta firmware of the Inbound AP still uses the old version of the MTK wireless driver
Inbound AP post on 2025-11-24 also reported the exact same problem, the official replied, " beta driver is not fully adapted to the low-channel 40 MHz, and the 36/44 option will be blocked in the next version to avoid misleading "[ ^5^ ]. In other words, this is a bug that known to be unfixed, not a personal setup error. - has nothing to do with the "region code" or "country code"
many people's first reaction is to change the region, but the limitation of MTK's driver in 36 channels is hardcoded, and it cannot be skipped to change US/CN, so it can only wait for the driver to be updated.
3. You can do it like this
| Objectives | operation | Remarks |
|---|---|---|
| just want to use 40 MHz | steadilymanually select channels such as 40, 44, and 48 | avoid 36 and it will take effect immediately |
| have to run 36 (like doing seamless roaming) | reduce bandwidth to 20 MHz | driver allows 36@20 MHz without jumping; The price is to cut the rate in half |
| and other official | fall back to the 8.0.50 official release or watch the next beta | inbound passengers have committed to "merging new MTK drivers as soon as possible"[ ^5^ ] |
| want to use 36@40 MHz | nowcan only change firmware | flash OpenWrt SNAPSHOT (with the latest mt76 driver) or Pandora, it can be turned on normally at 36@40 MHz, but the unified management function of inbound AC will be lost |
4. Conclusion
it's not a problem with your setup, it's the official beta firmware driver limit .
- short-term: avoid channel 36, or run only 36 MHz;
- long-term: Wait for inbound customers to update the official version, or change to other firmware.
Read More
Comment List