Multik Sila 1.0.21

What's new

• Each profile keeps its own server. Switching profiles while connected could put a
  random server of the new profile on screen and save it as that profile's choice,
  while the VPN kept running on the old profile. Now the app remembers which profile
  the VPN was started on and never mixes the two.
• Switching the profile while connected reconnects to it — to the server you saved
  for that profile, or the fastest one in Auto mode. What the screen shows is always
  the connection that is actually running.
• A profile opened for the first time in a session shows its saved server list right
  away instead of an empty screen while it loads.
• Android: the VPN no longer drops some time after a reconnect. Every time the core
  restarted on a running VPN (after failed checks, when the network came back, on a
  profile switch), the old tunnel was left open until a random later moment. The
  Android files of this release were replaced with this fix on 3 October; if you
  installed 1.0.21 before that, install the APK once more by hand.

Which file do I need?

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

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

• Server tags (srv_N) are assigned per profile in list order. With the core running
  on profile A, opening profile B for the first time took the core's selected tag and
  looked it up in B's list. The profile the core was started on is now stored (also in
  the settings, for a reopened Android screen); the server is taken from the core only
  for that profile, and a Clash API server switch is done only there — otherwise it is
  a full start.
• Checked on an emulator, connected throughout: Test (Trojan GT) → Free: reconnected,
  screen and core on the same server, traffic gets through → Test: reconnected, same
  again.
• The Android self-update path was confirmed end to end: an emulator went from 1.0.19
  to 1.0.20 through the app's own updater with its data intact.