The connection timeout is very short.
More often it is from the same subnet. Longer remote network.
Where to twist?
It should be 10 seconds. In what situations is this not enough? Is the connection very bad between phone and router?
Stable connection over the local network, breaks very often.
Stable connection remotely, gaps are much smaller.
We have not seen anything like this. Make sure your phone is not in some “low power” mode, or having other problems.
Ok, one more question.
Detect Internet request is activated when connecting, exiting the menu… Why so much?
And while this function is not clear. Help to understand and apply.
Thanks 
Detect internet constantly monitors if your router has internet connection and if it’s reachable from outside. It is to give you clear information if all is OK with the internet. This feature has nothing to do with the smartphone app. Router itself is monitoring if it can access the internet.
After I turned on “Detect Internet” in this mode, frequent disconnections stopped
In the past I’ve seen cases where detect internet pulls it’s own DHCP lease, which can cause all sorts of momentary problems, it’s been disabled on all devices we support for several years so not sure if the behavior is any different today.
I also noticed that now in the Log it has ceased to meet:
xx:xx:xx:xx:xx:xx@wlan2: disconnected, received deauth: sending station leaving (3), signal strength -49
The terminal out of the box for entering commands, as it did not work, does not work
I do not need it, but on a note
What if we differentiate on which interface “Limited access”?
To be honest, I don’t understand what the question is ?
I guess Konstantin wonders to which of interfaces applies the “(Limited access)” part. I guess it wouldn’t be a question is the output was “Available on lte1 (Limited access), ether1” … or if the comment explicitly mentioned interface name.
Or if MT dropped the “detect internet” function altogether
@mkx In both cases rights 
From version to version it still loses the “saved” list