Long DNS timeouts when offline
asked 2019-11-22 09:33:41 +0200
Some time ago (might well be over a year ago) something changed on my Jolla 1. I started noticing that sometimes opening apps can take a long time. MapFactor Navigator, which is a navigation app which can work offline, takes 15 seconds to launch while online, but 75 seconds while offline. K9 mail and Telegram also take much longer to open when offline.
I've come to the conclusion this has something to do with changes to network timeouts. Trying to ping some server from the console seems to confirm the issue: When I ping some server by name (while offline), it takes 20 seconds for the command to fail. Pinging by IP address fails instantly as does pinging by name while online. So it seems to be related to DNS requests. It does not matter whether I have no data in my cell phone subscription or turned data off and have no connected wifi network or turned wifi off or have flight mode enabled.
The device should be able to tell immediately that whatever network action is attempted, it will fail. But somehow a 20 second timeout is used. Apps that at startup attempt to connect to some server get an annoying and unnecessary penalty when no internet is available. There was a time that there was no timeout.
Is this a know issue? Is there some way I can fix this?
I noticed this bug too. I am developing an app in Rust and noticed that GET requests block from 15 to 20 seconds when my phone is offline. The requests are almost instantaneous when the phone is online.
Did you find a way to fix this? Or more information on the subject?
tg ( 2020-03-17 02:01:22 +0200 )edit