Dear Support Team, We have observed behavior that appears to be a malfunction with the WP7605. Please advise on how to resolve this issue. ・Devices running the latest firmware (Rev17) experience frequent communication dropouts. The fix patch has already been applied. ・Once the communication statu…

I saw that Macnica has already opened the Salesforce ticket 01922926 to discuss this issue BTW, is this issue related to the patch mentioned in here? [image] Ping does not go through Please see if this one-line modification in drivers/soc/qcom/smsm.c (around…

Thank you for your response. I will test this on the official FW R17 to verify the relevance of this issue. Meanwhile, while we investigate the cause, we are also exploring potential workarounds. In that regard, I would like to ask: what methods are available to speed up reconnection when communi…

Is there improvememt on the issue if you disable edrx feature by AT+CEDRXS=0 ? How long does it take for reconnect to network for radio off and radio on? Have you tried at+cops in manual mode and see if it can reattach to network faster?

When we tested using the official FW R17, the same issue occurred. We do not believe this issue is caused by the patch. Upon checking the logs, we found that the radio continued to turn on and off after a communication disconnection was detected. Based on past experience—specifically, an issue in…

Then you need to figure out why there is frequent dropout from base station. Is this related to your legato application? Or is it due to poor signal strenght in some area? For example, if you are not running your legato application (i.e. pure FW R17.1) do you see the network dropout issue? If ye…

In R13, there was an issue where it could take up to 30 minutes for data communication to resume after being rejected by the base station. To address this, we monitored the status using le_data_AddConnectionStateHandler and, upon detecting a disconnection, executed le_mrc_SetRadioPower(LE_OFF) and l…

Furthermore, when we ran R13 and R17 in the same environment, we found that R17 very frequently detects disconnections via le_data_AddConnectionStateHandler (which rarely occurs in R13). If the behavior of le_data_AddConnectionStateHandler differs between R13 and R17, we will design our program bas…

In R13, have you checked the AT!GSTATUS? during that 30 minutes for the signal strength? In R17, after receiving disconnect in le_data_AddConnectionStateHandler(), if you check AT!GSTATUS?, is it still registering to network? In R17, how long does it take to reconnect without radio on/off?

Since the occurrence frequency is low in R13, we have not been able to confirm the signal strength. In R17, we are currently testing two scenarios: one where the radio is not turned on or off after a disconnection is detected by le_data_AddConnectionStateHandler, and another where le_data_Request() …

if just 30ms between “connect” and “disconnect”, then probably this is not network deregistration. And the reconnection of data channel should be done automatically according to the legato documentation above, so you don’t need to do radio on/off actually. In addition, you don’t need to call le_da…

Regarding Connection Issues with the WP7605

jyijyi June 16, 2026, 9:10am 2

I saw that Macnica has already opened the Salesforce ticket 01922926 to discuss this issue

BTW, is this issue related to the patch mentioned in here?

For example, if you remove this line or using the official FW R17, will you see this issue?

If no, then that means there is regression bug on the patch.

Topic		Replies	Views
Wp77xx doesn`t get radio signal	6	292	March 18, 2022
DataConnectionService: No interface up indication after network registration restored Legato Application Framework	23	3167	February 13, 2023
Problem with data connection servie	20	521	April 4, 2022
WP7702 keeps disconnecting	7	522	October 7, 2022
WP7702 fails to connect Legato Application Framework	8	349	September 20, 2023

Regarding Connection Issues with the WP7605

Related topics