Optimizing Huawei Multi-Screen Collaboration Lag#
Still keeping a record for reference for those who encounter this issue.
A few days ago, I bought a new AX3pro. At home, I originally had an A2 as the main router connected to a TPLINK. So, I thought of replacing the TPLINK with the AX3pro and using Smart Connection to achieve seamless roaming. The actual connection setup is fiber modem - A2 - AX3pro - computer/phone. After setting it up, I found that the multi-screen collaboration was extremely laggy, even worse than when I used TPLINK (5G WiFi) before.
The root cause has actually been mentioned in other parts of the forum, which is the compatibility issue with the low-frequency 5G WiFi of multi-screen collaboration. In short, do not use 5G WiFi channels below 149, change it to, for example, 153. However, after changing the channel of the A2 router on the web page, it did not solve the problem, and I noticed that the computer was still connected to channel 36.
So, another reason is the use of A2 as the main router. Because the antennas of the A2 are separate, the order of setting must be 2.4G, 5G low-frequency, 5G high-frequency. When using Smart Connection on Huawei routers, the secondary router cannot change any settings and can only inherit the settings of the main router. Therefore, the AX3pro inherited the low-frequency 5G setting of the A2, fixed to use channel 36, regardless of how I changed the high-frequency channel on the A2, I could not change the actual output on the AX3pro.
The final solution is also simple, use AX3pro as the main router, and change the connection setup to fiber modem - AX3pro - A2 - computer/phone. AX3pro does not have multiple 5G WiFi antennas, so only one channel can be set. Set it to 153, and the multi-screen collaboration becomes smooth again.
Added on 2021/07/25
After updating the firmware, I found that the computer was connected to channel 36 again and couldn't disconnect. Later, I found that I could disable 5GWIFI1 on the A2 web page, and it may require repeating this process after restarting, but it's not frequent, so it's acceptable.
...It's better to replace this unlucky thing with AX2pro as soon as possible.