Beta Software Deco X50-5G_V1_1.2.0 with IoT and CPU Optimization
This Article Applied to
Deco X50-5G_V1
Optimization and Bug Fixes:
- Fixed the issue of not detecting the IoT Network.
- Optimized the CPU Usage
- Improved the overall network stability.
Firmware Download Link
| Deco X50-5G_V1 | 1.2.0_build20241230_Beta(updated time 2024.1.6) |
Update Advice:
1. Please be sure you have read the Terms and Conditions for TP-Link Beta Firmware before proceeding.
2. How to manually update the firmware via web UI- How to Update the Firmware of Deco.
Please feel free to comment below on how this version works. Thanks in advance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@jerikoo
the CPU is 100% while the fan seems to have errors:
+QTEMP:"modem-lte-sWed Feb 26 17:22:01 2025 user.err : [fan-control]:paMaxTemp = :61
Wed Feb 26 17:22:01 2025 user.err : [fan-control]:mdmMaxTemp = :61
Wed Feb 26 17:22:01 2025 user.err : [fan-control]:wifi0Temp = :79
Wed Feb 26 17:22:01 2025 user.err : [fan-control]:wifi1Temp = :71
Wed Feb 26 17:22:01 2025 user.err : [fan-control]:fan_status = :0
Wed Feb 26 17:22:01 2025 user.err : [fan-control]:closed->closed
Wed Feb 26 17:22:01 2025 user.err : [fan-control]:fan zero
Wed Feb 26 17:22:04 2025 user.err : dail_get_slaac_addr error.
Wed Feb 26 17:22:07 2025 daemon.err nrd[592]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from 22:67:82:30:29:EA
Wed Feb 26 17:22:08 2025 user.err : dail_get_slaac_addr error.
Wed Feb 26 17:22:10 2025 user.warn : [mobile] [GetEventType] qmi_module=1, qmi_msg_id=0x0051
Wed Feb 26 17:22:10 2025 user.warn : [mobile] [PostEvent] Event (id: 0x00000000, type: 0x10000001) return directly.
Wed Feb 26 17:22:12 2025 user.err : dail_get_slaac_addr error.
Wed Feb 26 17:22:13 2025 user.warn : [mobile] [GetEventType] qmi_module=1, qmi_msg_id=0x0051
- Copy Link
- Report Inappropriate Content
@jerikoo read back on the thread and it tells you how to downgrade back to 1.15.
1.20 and betas are not stable
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi, Thank you very much for the feedback.
May I know who your SIM Carrier is?
I'd like to follow up on your case via email and ask for the senior engineer for further assistance. Please check whether you can receive my email later.
Best regards.
- Copy Link
- Report Inappropriate Content
I'm having the same issue, weekly red light issue on 1.17, on v2 it's a daily thing.
Noticed on v2 it reboots itself when this happens
But v1.17 it just freezes and needs to be powered down and back up again
This is with three uk as the provider
Tried cell lock, with no real difference for me.
Kind regards
Adam
- Copy Link
- Report Inappropriate Content
Hi, Thanks for the feedback.
Have you tried to test with another SIM card to see whether the issue continues?
How long have you had the Deco X50-5G?
If there are other Deco units in the Mesh system, it is suggested to set Deco X50-5G into "bridge mode", and then use the satellite Mesh units, for example, Deco X50 to create a separate Mesh network: How to Create a New Network in the Deco App
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
Hi @David-TP
Could you request the engineers to troubleshoot the Router OS while using high bandwith, the problem seems to be related with the throwput or the number of tpc/udp connections/threads.
The CPU hangs in 100%, even with everything disabled, including the routing/firewall (bridge mode)... either the router has a design flaw in hardware requirements, or hopefully the firmware/OS has a bug that needs to be addressed.
Are these temperature issues in the logs related?
Mon Dec 30 09:30:41 2024 user.err mobile_control: (src/qca/qca_utils.cpp:133:qca_get_channel_list): athr: ioctl[SIOCGIWRANGE] failed. err:-1
Mon Dec 30 09:30:42 2024 user.err : [fan-control]:at_cmd = :simplecom -c at+qtemp
Mon Dec 30 09:30:42 2024 user.err : [fan-control]:atResp = :at+qtemp
+QTEMP:"modem-lte-sub6-pa1","62"
+QTEMP:"modem-sdr0-pa0","0"
+QTEMP:"modem-sdr0-pa1","0"
+QTEMP:"modem-sdr0-pa2","0"
+QTEMP:"modem-sdr1-pa0","0"
+QTEMP:"modem-sdr1-pa1","0"
+QTEMP:"modem-sdr1-pa2","0"
+QTEMP:"modem-mmw0","0"
+QTEMP:"aoss-0-usr","61"
+QTEMP:"cpuss-0-usr","61"
+QTEMP:"mdmq6-0-usr","61"
+QTEMP:"mdmss-0-usr","61"
+QTEMP:"mdmss-1-usr","61"
+QTEMP:"mdmss-2-usr","61"
+QTEMP:"mdmss-3-usr","60"
+QTEMP:"modem-lte-sMon Dec 30 09:30:42 2024 user.err : [fan-control]:paMaxTemp = :62
Mon Dec 30 09:30:42 2024 user.err : [fan-control]:mdmMaxTemp = :61
Mon Dec 30 09:30:42 2024 user.err : [fan-control]:wifi0Temp = :81
Mon Dec 30 09:30:42 2024 user.err : [fan-control]:wifi1Temp = :70
Mon Dec 30 09:30:42 2024 user.err : [fan-control]:fan_status = :0
Mon Dec 30 09:30:42 2024 user.err : [fan-control]:closed->closed
Mon Dec 30 09:30:42 2024 user.err : [fan-control]:fan zero
Mon Dec 30 09:30:46 2024 user.err mobile_control: (src/qca/qca_utils.cpp:133:qca_get_channel_list): athr: ioctl[SIOCGIWRANGE] failed. err:-1
Mon Dec 30 09:30:51 2024 user.err mobile_control: (src/qca/qca_utils.cpp:133:qca_get_channel_list): athr: ioctl[SIOCGIWRANGE] failed. err:-1
Mon Dec 30 09:30:56 2024 user.err mobile_control: (src/qca/qca_utils.cpp:133:qca_get_channel_list): athr: ioctl[SIOCGIWRANGE] failed. err:-1
Mon Dec 30 09:31:01 2024 user.err mobile_control: (src/qca/qca_utils.cpp:133:qca_get_channel_list): athr: ioctl[SIOCGIWRANGE] failed. err:-1
Mon Dec 30 09:31:02 2024 user.err : [fan-control]:at_cmd = :simplecom -c at+qtemp
Mon Dec 30 09:31:02 2024 user.err : [fan-control]:atResp = :at+qtemp
+QTEMP:"modem-lte-sub6-pa1","62"
+QTEMP:"modem-sdr0-pa0","0"
+QTEMP:"modem-sdr0-pa1","0"
+QTEMP:"modem-sdr0-pa2","0"
+QTEMP:"modem-sdr1-pa0","0"
+QTEMP:"modem-sdr1-pa1","0"
+QTEMP:"modem-sdr1-pa2","0"
+QTEMP:"modem-mmw0","0"
+QTEMP:"aoss-0-usr","61"
+QTEMP:"cpuss-0-usr","62"
+QTEMP:"mdmq6-0-usr","62"
+QTEMP:"mdmss-0-usr","62"
+QTEMP:"mdmss-1-usr","62"
+QTEMP:"mdmss-2-usr","61"
+QTEMP:"mdmss-3-usr","60"
+QTEMP:"modem-lte-sMon Dec 30 09:31:02 2024 user.err : [fan-control]:paMaxTemp = :62
Mon Dec 30 09:31:02 2024 user.err : [fan-control]:mdmMaxTemp = :61
Mon Dec 30 09:31:02 2024 user.err : [fan-control]:wifi0Temp = :80
Mon Dec 30 09:31:02 2024 user.err : [fan-control]:wifi1Temp = :70
Mon Dec 30 09:31:02 2024 user.err : [fan-control]:fan_status = :0
Mon Dec 30 09:31:02 2024 user.err : [fan-control]:closed->closed
Mon Dec 30 09:31:02 2024 user.err : [fan-control]:fan zero
Thanks
- Copy Link
- Report Inappropriate Content
Thanks for the update,
I unfortunately don't have access to another sim card as I have a ongoing contract with my current provider.
I have had the x505g since September 2023
I do have x2 x50 deco units and have never thought of using bridge mode does it offer more stability ?
Will I lose the wifi access on the x50 5g unit
Kind regards
Adam
- Copy Link
- Report Inappropriate Content
Hi, Thanks for the update.
When Deco X50-5G is in bridge mode, its WiFi signal is still here but it is used for local management via the Deco APP and has no internet access.
For your case, if you would like to spend a little more time with our engineers, you could refer to the instructions here to help us capture the modem log:
How to capture the modem log on Deco X50-5G
Thanks a lot and wait for your reply.
- Copy Link
- Report Inappropriate Content
@David-TP This X50-5G is a nightmare. Why Tp link doesn't deploy a corrected firmware ? Mine is version 1.2.1...
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 15580
Replies: 117
Voters 1
