Skip to content

Multik Sila 1.0.20

Choose a tag to compare

@MrMultik MrMultik released this 03 Oct 07:14
· 25 commits to main since this release

Download for Windows Download for Android

What's new

  • Android: the VPN connects again. With a server list that changes often (the free
    lists do, every hour), 1.0.19 could fail to connect: tapping the shield seemed to do
    nothing, and after reopening the app it showed "Protected" while nothing worked.
    Fixed.
  • A subscription update no longer drops your connection. If the server list changes
    while you are connected, the app keeps the current connection and uses the new list
    the next time you connect. This applies on Windows too.
  • Android: the server you see is the server you use. The core could keep running on
    a server picked long ago instead of the one Auto (or you) had just chosen.
  • Android: the same cores as Windows — sing-box 1.14.2 and Xray 26.9.30 (were
    1.13.16 and 26.3.27). The APK is about 22 MB bigger because of them.
  • "Protected" on Android now means the core is really running; a start that fails no
    longer leaves a VPN service hanging without a core.

Which file do I need?

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

Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.20-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
  • 1.0.19 showed the saved copy of the subscription first and the network copy next. When
    the two differed while the core was running, the app reconnected (stop, then start).
    On Android the stop is an asynchronous intent, so the new core hit the Clash API and
    Xray bridge ports still held by the old one and failed. Now a changed list is kept
    until the core is not running; stopping waits until the service reports the tunnel
    gone; isRunning reports the tunnel rather than the service object.
  • Under libbox, sing-box always enables its cache file, and the selector restores the
    last stored selection instead of the configured default. The app now sets the
    selected server over the Clash API once the tunnel is up.
  • sing-box 1.14 binds the system stack's TCP listener to the TUN interface only on Apple
    platforms. The app is excluded from its own VPN, so on Android TCP got no replies
    with the system and mixed stacks. Android always uses gVisor now.
  • Checked on an emulator with a 145-server free list and with a 9-server subscription:
    all servers pass a request through the new cores (VLESS, REALITY, xhttp, gRPC,
    Hysteria2, Trojan); Russian sites go direct, others through the server; closing and
    reopening the app leaves the VPN untouched.

Ask in Telegram