To make it more concrete. This is seemingly the interesting part from the wifi log: 000005bc 11:06:36: ENTER: CWiFiServerProtocol::ProcessGetModificationsRequest() 000005bc 11:06:36: Calling callback... 000005bc 11:08:06: Callback returned. 000005bc 11:08:07: ENTER: CWiFiProtocol::SendCommandV() 000005bc 11:08:07: SendCommandV buffer - 30e64a0 000005bc 11:08:07: SendCommandV nLen 12 000005bc 11:08:07: SendString(`OK 62360,209 `) 000005bc 11:08:07: SendBlock(size: 13) 000005bc 11:08:07: 13 bytes sent 000005bc 11:08:07: LEAVE: CWiFiProtocol::SendCommandV() 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 6000) 000005bc 11:08:07: 6000 bytes sent 000005bc 11:08:07: SendBlock(size: 2360) 000005bc 11:08:07: 2360 bytes sent 000005bc 11:08:07: Cleaning up 000005bc 11:08:07: Cleaned up 000005bc 11:08:07: LEAVE: CWiFiServerProtocol::ProcessGetModificationsRequest() = 1 000005bc 11:08:07: ENTER: CSocketClient::GetLine() 00002648 11:08:36: ERROR: Timeout obtaining socket read availability (code 0)
Why can the callback take 1,5 minutes? Is this regarding the PC or the Android device? If I interpret the log correctly it then continues but my guess is that because of the lost 1,5 minutes the socket timeout is reached and therefore it is closed. In general the communication over my wifi is fast between the devices and I haven't had any issues apart this one with MyLifeOrganized?! I am simply stumped :-( Dan schrieb am Mittwoch, 30. Dezember 2020 um 20:44:29 UTC+1: > Hi, > > I cannot get WiFi sync to work. The initial connect with the PIN is ok and > the first sync also. All tasks are synced. However if I try another sync > after roughly a minute the error "java.net.SocketTimeoutException: Read > timed out" pops up. This is then the case for every sync. > > I have tried/analyzed dozen of things but with no success: > - Resetting > - Reducing amount of tasks > - Checked network settings (i.a. Windows firewall) -> However it does not > really make any sense that it is network related as the first sync works or > am I mistaken?! > - Checked the logs. > - Tried different MLO versions. > - Contacted MLO support ages ago but it ended with no solution. > - etc. > > Has anybody got an idea? Thanks for any help! > > Best regards, > Dan > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/8c7da8bf-7881-440e-b0e7-85616c5c1d85n%40googlegroups.com.
