Multik Sila 1.0.19

What's new

• The app remembers your server. The server you picked, or the one Auto picked, is
  still selected after the app restarts. Before, it always started on the first server
  of the list. Latency numbers are kept too, so you no longer see "— ms" everywhere
  after a restart.

• No more surprise reconnects. Some subscription panels hand out a different
  REALITY server name on every refresh. The app took that for a new server list and
  reconnected you — on the scheduled refresh, and on Android every time you reopened
  the app.

• Android: reopening the app is instant. The server, its latency and the check
  result are there at once. Before, the screen stayed empty for a few seconds and showed
  "Checking whether traffic gets out…" as if it were connecting again.

• The traffic check waits 15 seconds instead of 5 before it calls a server dead.
  On a slow mobile network a working server sometimes didn't make it in 5.

• Android: the latency method picker is back.

  • "To the server" is the default. It measures each server directly, past the VPN,
    so the numbers are the same with and without a connection.
  • "Full path" sends a real request through each server while you are connected.

  If your phone was set to another method, it switches to "To the server" once.

• The hint under "Pick the fastest server when connecting" now says what the app
  actually does: Auto mode only, and it re-measures numbers older than two minutes.

Which file do I need?

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

Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.19-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

• The selected server and the last full latency run are stored per profile, by server
  name (names in a subscription are unique; srv_N tags follow list order). Restored
  latencies keep their measurement time, so Auto still re-measures before connecting
  when they are older than two minutes.
• On start, the saved copy of the subscription is shown first and the network copy
  follows; the same list for the core changes nothing.
• REALITY serverName is left out of the list fingerprint, like shortId and
  spiderX. On a live subscription, 6 of 6 pairs of back-to-back fetches differed
  only in it.
• Android: when the screen opens while the VPN service runs, the app takes the server
  from the running core (Clash API selector) and checks traffic without the
  "Checking…" label. "Connect on launch" asks the service whether the tunnel is up
  before connecting. The app log is appended across screen reopens instead of being
  replaced.
• Checked on an emulator: connect, close and reopen twice — same server, numbers and
  check result within a second, and the system log shows no VPN disconnect. A
  manually picked server survives a reopen.