Repository navigation
Releases: MrMultik/Multik-Sila
Release list
Multik Sila 1.0.28
What's new
- Google search and some sites no longer fail with "connection reset". Chrome
looks up addresses on its own (secure DNS) and gets IPv6 ones. With IPv6 turned off
in the app (the default), the tunnel accepted such a connection and only then cut it,
so Chrome showedERR_CONNECTION_RESETinstead of switching to IPv4. Now the tunnel
refuses IPv6 at the very first packet and the browser goes over IPv4 right away. - One odd server no longer spoils the latency test. Free lists often carry a server
with a setting sing-box does not accept. It used to stop the whole "full path" test:
on Windows every server was left without a number, on Android the test quietly fell
back to a plain handshake. Now that server is skipped (the log says so) and the rest
are measured. - Auto mode no longer gets stuck on a server it cannot use. The connection check
could keep picking a server sing-box had refused, so the app stayed on a dead one.
Which file do I need?
| Device | File |
|---|---|
| Windows 10 / 11 | MultikSila-1.0.28-setup.exe |
| Android — almost any phone | MultikSila-1.0.28-android-arm64-v8a.apk |
| Android — old 32-bit phones | MultikSila-1.0.28-android-armeabi-v7a.apk |
| Android emulator | MultikSila-1.0.28-android-x86_64.apk |
Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.28-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
- IPv6: with the DNS strategy
ipv4_onlythe route already had
{"ip_version": 6, "action": "reject"}, but after{"action": "sniff"}. sing-box
decides a reject before the connection exists (pre-match) only up to the first sniff
rule for TCP, so the TUN finished the handshake and then sent a reset. A logical rule
ahead of sniff now rejects IPv6 TCP (port 53 and private addresses excepted), and the
TUN answers the SYN itself. Windows and Android TUN. - Rejected sing-box outbounds (
initialize outbound[N]) are now handled the same way
by the main core and both latency probes: the server is dropped, its latency cleared,
the selection moved off it, and the probe restarts without it. Checked with sing-box
1.14.3: a bad uTLS fingerprint makes the probe exit in about 0.25 s with the outbound's
index. - Cores unchanged: Xray 26.10.10 and sing-box 1.14.3.
Multik Sila 1.0.27
What's new
- New cores: Xray 26.10.10 and sing-box 1.14.3. On Android the cores are part of the
app, so this release is how phones get them. On Windows the app updates its cores on
its own and most installs already have them; the installer now ships them too.
Checked against a server running Xray 26.10.10 with REALITY over TCP, XHTTP and gRPC:
everything connects, with the old version and with this one. - Reopening the app no longer looks like a new connection. With the VPN on,
opening the app briefly showed "no connection" and then "traffic gets through", as if
it reconnected. It was a check that ran before the server list had loaded. Now the
check waits for the list.
Which file do I need?
| Device | File |
|---|---|
| Windows 10 / 11 | MultikSila-1.0.27-setup.exe |
| Android — almost any phone | MultikSila-1.0.27-android-arm64-v8a.apk |
| Android — old 32-bit phones | MultikSila-1.0.27-android-armeabi-v7a.apk |
| Android emulator | MultikSila-1.0.27-android-x86_64.apk |
Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.27-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
- Android: the in-app cores are built from Xray-core v26.10.10 (701af60) and sing-box
v1.14.3. Windows: bundledxray.exe26.10.10 andsing-box.exe1.14.3; the GitHub
build pins both by version and SHA-256 of the official archives. - Xray 26.10.10 changes no wire protocol since 26.9.30 (23 commits). One change matters
for clients: TLS is now verified against Xray's built-in Mozilla root certificates
instead of the operating system's store. A server whose TLS certificate comes from a
private certificate authority will stop connecting; REALITY and servers with ordinary
public certificates are not affected. - Test bench: Xray 26.10.10 server with VLESS + REALITY over TCP (Vision), XHTTP and
gRPC. Clients: Xray 26.10.10 on Windows with a config generated by the app's own link
parser, the previous 1.0.26 on an Android emulator (Xray 26.9.30), and this build. All
three transports passed for all three clients. This build was also checked on a public
free list: latency through the probe core, Auto mode, traffic through the tunnel. - Reopen fix: when the screen comes back while the tunnel is running, the traffic check
waits until the server list is loaded instead of searching an empty list.
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.
Multik Sila 1.0.25
What's new
- One odd server no longer stops the VPN from starting. Some free server lists
contain servers written for other apps, for example withfp=unsafein the link.
The app refused to connect at all with an error like
unknown uTLS fingerprint: unsafe. Such settings are now converted to ones the
core understands. If the core still rejects a server, the app skips that one
server, says so in the log and connects without it. - Auto mode finds a working free server much faster. It used to check servers one
by one and wait up to 15 seconds for each dead one. Now it checks the current server
and the next best ones at the same time. On a list of 141 free servers, the time from
tapping the shield to "traffic gets through" went from 32 seconds to 4. - Android: "Full path through the proxy" latency now works without a connection.
Before, without the VPN on, this mode quietly measured only the time to connect to
the server, so the numbers changed once you connected. Now it sends a real request
through every server, with or without the VPN.
Which file do I need?
| Device | File |
|---|---|
| Windows 10 / 11 | MultikSila-1.0.25-setup.exe |
| Android — almost any phone | MultikSila-1.0.25-android-arm64-v8a.apk |
| Android — old 32-bit phones | MultikSila-1.0.25-android-armeabi-v7a.apk |
| Android emulator | MultikSila-1.0.25-android-x86_64.apk |
Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.25-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
- Links are usually written for Xray, which accepts uTLS fingerprints and VLESS flows
that sing-box 1.14 does not:unsafe(plain Go TLS),hellochrome_131and other
hello…names,chromefp,flow=xtls-rprx-vision-udp443. sing-box failed the whole
config withinitialize outbound[N]: …. They are now mapped when the subscription is
parsed (unsafe= TLS without uTLS; REALITY servers, which go through Xray, get
chrome, since Xray does not allowunsafewith REALITY). - Safety net for anything else: the outbound index from the core's error identifies the
server, which is dropped before an immediate restart (Android: the VPN service's error
event; Windows: the core's stderr). No extra check before every connect. - All five igareck lists pass
sing-box checkthrough the app's own parser; without the
fix three of them could not start. Checked on an emulator with a list containing
fp=unsafeplus a server with a made-up flow: the bad server was skipped and the
tunnel came up. - Auto mode: the Clash API
delaycheck runs in batches of 12 (up to 36 servers); the
current server wins if it answers within 3 s. Lists over 60 servers are measured with
2 handshakes per server instead of 5. - Android full-path latency without a connection: an in-app probe sing-box without a
tunnel (plus its own Xray instance for Xray servers), measured through its Clash API,
like the probe processes on Windows. If it cannot start, the app falls back to the
handshake time.
Multik Sila 1.0.24
What's new
- Android: large server lists connect again. With a big subscription — the free
lists now have 400+ servers in one file — tapping the shield did nothing, and half a
minute later the app closed. The configuration was too large for Android to hand to
the VPN service in one message. It now goes through a file, so the size of the list
no longer matters. A list that connected last week could stop connecting simply
because it grew. - Android: when the VPN does not start, the app says why — right under the shield,
not only in the log. - If another VPN app is running on the phone (Android allows only one at a time), the
app says so: turn it off, and if it has "Always-on VPN" enabled in Android settings,
turn that off too.
Which file do I need?
| Device | File |
|---|---|
| Windows 10 / 11 | MultikSila-1.0.24-setup.exe |
| Android — almost any phone | MultikSila-1.0.24-android-arm64-v8a.apk |
| Android — old 32-bit phones | MultikSila-1.0.24-android-armeabi-v7a.apk |
| Android emulator | MultikSila-1.0.24-android-x86_64.apk |
Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.24-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 sing-box config and the Xray bridge configs were passed to the VPN service as
Intent extras. For the 405-serverBLACK_VLESS_RUS.txtthe parcel was 596 080 bytes:
startForegroundServicefailed withTransactionTooLargeException, and 30 s later
Android killed the app withForegroundServiceDidNotStartInTimeException. Now the
activity writes them tonext_tunnel.jsonin the app's private files and starts the
service with no payload. - Checked on an emulator with the same list: the tunnel comes up with all 405 servers in
the core's selector, traffic gets through, no crash. All five igareck lists also pass
sing-box check(1.14.2) andxray run -testthrough the app's own config builder. - No changes for Windows in this release.
Multik Sila 1.0.23
What's new
- Windows: the desktop shortcut shows the new icon. After updating from inside the
app, the shortcut kept showing the old shield from 1.0.17 even though the program
itself has carried the "M" icon since 1.0.18 — Windows kept the old picture in its
icon cache, keyed by the program's path. The shortcuts now take the icon from a
separate icon file of the program: the installer creates them that way, and the app
switches existing shortcuts to it once after an update. The Windows files of this
release were replaced with this fix on 3 October; if you updated to 1.0.23 before
that and the shortcut still shows the shield, run the installer once.
Which file do I need?
| Device | File |
|---|---|
| Windows 10 / 11 | MultikSila-1.0.23-setup.exe |
| Android — almost any phone | MultikSila-1.0.23-android-arm64-v8a.apk |
| Android — old 32-bit phones | MultikSila-1.0.23-android-armeabi-v7a.apk |
| Android emulator | MultikSila-1.0.23-android-x86_64.apk |
Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.23-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 shortcut has no icon of its own (
IconLocationis empty) and takes it from
proxy_app_test.exe; the in-app update replaces the files but neither recreates the
shortcut nor notifies the shell. apply_update.batnow runsie4uinit.exe -showafter copying the files. The script
is written by the version being replaced, so the new version also runs it once at
first start (remembered per version). The installer setsChangesAssociations=yes.- The cache refresh alone did not help on a real PC: Explorer keys the icon by the exe
path. Shortcuts now getIconFilename=data\flutter_assets\assets\tray_icon.ico
(the same multi-size "M" .ico, byte for byte) — from the installer's[Icons], and
for existing shortcuts from the app once per version (a PowerShell script via
-EncodedCommand, so a Cyrillic profile path survives). - No changes for Android in this release.
Multik Sila 1.0.22
What's new
- Android: a Multik Sila tile in quick settings. Pull down the notification shade
and tap the tile to turn the VPN on or off without opening the app. It reconnects
to the profile and server you used last time. The tile lights up and shows
"Connected" / "Off" (and "Connecting…" while the tunnel comes up). - Adding the tile. On Android 13 and newer the app offers it once, after your first
connection. You can also add it any time in Settings → Startup and automation →
Quick settings tile. On older Android, open quick settings, tap the pencil and drag
"Multik Sila" up. New tiles land at the end of the list, so you may want to drag it
to the first page. - If the VPN has never been turned on, or Android took the VPN permission away (another
VPN app was used), the tile opens the app instead. - Android: the VPN no longer drops some time after a reconnect (also in the replaced
1.0.21 files).
Which file do I need?
| Device | File |
|---|---|
| Windows 10 / 11 | MultikSila-1.0.22-setup.exe |
| Android — almost any phone | MultikSila-1.0.22-android-arm64-v8a.apk |
| Android — old 32-bit phones | MultikSila-1.0.22-android-armeabi-v7a.apk |
| Android emulator | MultikSila-1.0.22-android-x86_64.apk |
Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.22-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
SilaTileService(aTileService). The VPN service keeps the last configuration the
tunnel came up with (last_tunnel.jsonin the app's private files, next to
config.json); the tile starts the service with it. Android 13+:
StatusBarManager.requestAddTileServicefor the one-time offer and the settings
button.- A tile that is already listening gets no new
onStartListeningfrom
requestListeningState, so the service also updates the visible tile directly. - Checked on an Android 15 emulator with the app in the background and the panel kept
open: off → on within a second, traffic gets through on the same server; on → off;
opening the app afterwards shows the right state. - No changes for Windows in this release.
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.
Multik Sila 1.0.20
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;isRunningreports 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 configureddefault. 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 thesystemandmixedstacks. 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.
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.
- "To the server" is the default. It measures each server directly, past the VPN,
-
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_Ntags 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
serverNameis left out of the list fingerprint, likeshortIdand
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.