Multik Sila 1.0.26

What's new

• Auto mode keeps looking until it finds a server that works. In 1.0.25 it checked
  only the 36 best servers by latency and then gave up. On free lists, where the
  fastest servers are often dead, the VPN stayed on with no traffic and never moved to
  another server. Now it goes through the whole list, skips servers that already
  failed, and the log shows how the search is going.
• Connecting to a big list no longer stalls before it starts. With about a thousand
  servers, the app spent almost a minute looking up server addresses one by one before
  the tunnel even started. That now takes under a second on Android.
• Latency tests on big lists are faster. For lists of more than 300 servers, the
  "to the server" test checks more servers at once: 784 addresses take 12 seconds
  instead of 28.

Which file do I need?

Device	File
Windows 10 / 11	MultikSila-1.0.26-setup.exe
Android — almost any phone	MultikSila-1.0.26-android-arm64-v8a.apk
Android — old 32-bit phones	MultikSila-1.0.26-android-armeabi-v7a.apk
Android emulator	MultikSila-1.0.26-android-x86_64.apk

Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.26-windows-x64.zip is what it downloads for that — you don't need it.

On Android with 1.0.13 or newer the app offers this update itself; the first time,
Android asks you to allow installing from Multik Sila. On 1.0.12 or older, install this
file by hand once.

Technical details

• Working-server search (Auto mode, after connecting and after a failed health check):
  12 servers at once including the current one, then 24 at a time, down the whole list
  sorted by latency. Every server that fails is marked unhealthy, so later checks and
  auto-select skip it. If none works, the marks are cleared: the cause is then shared
  (network, blocking), not the servers. On an emulator, a list of 150 dead servers was
  searched in full in 37 seconds; 1.0.25 stopped after 36.
• Config generation resolved server names one at a time, and under TUN resolved them
  a second time without a cache (for the server-address bypass rule): 56 seconds for
  1209 servers on an emulator. Names are now resolved 32 at a time, and Android skips
  that bypass rule: the app and its cores are already excluded from its own VPN.
  Result: 0.4 seconds.
• TCP latency for lists over 300 servers runs 128 connections at a time instead of 48.
  Measured over a real Wi-Fi connection on 784 addresses from a free list: 28 s vs
  12 s, with the same servers answering.
• Latency results update the screen at most every 250 ms instead of on every answer.