v2rayF v2.6.4.6

v2.6.4.6

Fix

Daily assist: graph.instagram.com / b-graph.facebook.com removed from VpnService HTTP CONNECT exclusions.

MQTT / chat gateways stay excluded → TUN. Graph HTTPS rides 10809 with feed (QUIC UDP/443 block → TCP).

Symptom this targets: Direct send/receive/like OK, older messages / history scroll spinner forever.

Scorecard

Split cells: Instagram Direct send/receive vs Instagram Direct history scroll.

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release --filter "FullyQualifiedName~MetaHttpProxy|FullyQualifiedName~GoldenMatrix"

Android Daily + non-SS: force-stop IG → thread → scroll older messages loads; MQTT still works; Play OK.

v2rayF v2.6.4.5

v2.6.4.5

Fix

Live TUN: PacketEncodingPolicy injects packet_encoding=xudp / packetEncoding=xudp for all non-Vision VLESS/VMess when the link omits it — TLS, REALITY, WS, gRPC, httpupgrade, etc. Not only plain TCP/none.

Still skipped:

• Vision (xtls-rprx-vision) — core already muxes UDP→XUDP; stacking fights splice
• speedtest / Test All — liveTun=false (2.0.7–2.0.9 crawl)
• SS / Trojan / Hy2 — native UDP, no field

Explicit link packetEncoding still wins.

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release --filter FullyQualifiedName~TunVlessUdpDns

v2rayF v2.6.4.4

v2.6.4.4

Fix

Live TUN Build (sing-box + Xray): plain VLESS/VMess (network=tcp, security=none) without link packetEncoding → emit xudp.

TUN DNS path: UDP hijack + detour: proxy. Latency/Connect SOCKS gate: TCP only. No XUDP ⇒ UDP DNS over that outbound fails.

Not applied to Vision / TLS / REALITY / WS / grpc / … or speedtest (classic Test All stays Xray SOCKS).

Diagnostics: SOCKS-ok + TUN-weak note; Connect timeline logs the inject.

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release --filter FullyQualifiedName~TunVlessUdpDns

Connect plain VLESS TCP (:3306) → HTTPS works; SS / Reality Vision unchanged.

v2rayF v2.6.4.3

v2.6.4.3

Why

Secure Share was Xray-only and used a naive LAN IP (often wrong for Mobile Hotspot). Android classic Connect (sing-box) could not share the tunnel to other devices.

Added / Changed

• sing-box authenticated SOCKS/HTTP share inbounds (same ports as Xray)
• SoftAP / Mobile Hotspot–aware advertise IP ranking
• Windows temporary inbound firewall rules for share ports
• Settings: Secure Share for both cores; Copy SOCKS / HTTP / setup tip
• Tip rewrite: docs/tips/secure-share.md

Not in this release

Transparent ICS / zero-config hotspot NAT (clients still set a proxy once).

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release --filter FullyQualifiedName~SecureShare

Host: Connect → Secure Share on → Copy SOCKS → set proxy on a second device → exit IP matches host tunnel.

v2rayF v2.6.4.2

v2.6.4.2

Why

v2.6.4.1 field soak passed on Android and Windows. Phase C opens with a first slice: richer diagnostics and honest status — not a UI redesign.

Added

• Settings → Copy session diagnostics — Connect → SOCKS → TUN → soft recovery / multipath timeline
• Stronger Daily vs Gaming Boost copy + recover CTAs when TUN/HTTP assist is weak
• Multipath flake status under Gaming (Soft Multipath re-ranks on reconnect; Survive stays off)
• Golden-matrix lab harness + tip docs (docs/tips/phase-c.md, docs/tips/golden-matrix-2.6.4.1.md)

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release --filter FullyQualifiedName~SessionDiagnostics|FullyQualifiedName~GoldenMatrix|FullyQualifiedName~GamingBoost

On device: Connect → Settings → Copy session diagnostics → paste into private notes. Trigger weak TUN or multipath path miss and confirm status CTAs (no silent Survive).

v2rayF v2.6.4.1

v2.6.4.1

Why

Free returned zero servers on many Iran ISP paths: the shortlist lived behind raw GitHub, and the hard ≤150ms gate rejected working CDN edges that are often 150–400ms from Iran.

Changed

• Default Worker mirror: https://pulseconfigs-mirror.drmikecrypto.workers.dev
• Prefer Free latency 1–150ms; if slots remain, fill up to 450ms
• Tip docs aligned (docs/tips/pulse-free-servers.md)

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release --filter FullyQualifiedName~PulseFree

On Iranian cellular/Wi‑Fi (VPN off): tap Free — expect up to 5 Free slots when any candidate passes ≤450ms on-device.

v2rayF v2.6.4.0

v2.6.4.0

Why

Free used to dump the published top5 into the list. That ignored your path: a node that is “good” in the pack can be 500ms+ (or dead) on IR/CN ISP routes, and re-taps could churn user-looking entries.

Changed

• Free keeps at most 5 servers tagged Source=pulse-free.
• On-device probe: TCP then proxy path; keep only 1–150ms.
• Re-tap: keep Fast Free; replace slow/failed Free only; never touch user imports.
• Prefer candidates.json shortlist; soft POST /refresh when Worker base is known.
• 60s cooldown; green Free badge in the list.
• Optional PulseWorkerBase in settings (no UI field).

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release

Tap Free twice: first fill ≤5 under 150ms; second should keep good Free and only swap slow ones. Imported servers must stay.

v2rayF v2.6.3.6

v2.6.3.6

Why

Gaming mode only flipped Chromium HTTP assist off. That is necessary for Unity/UDP but not a booster. Users (and GearUP comparisons) expect UDP-aware path selection, multipath that reacts mid-match, and no fragment/Survive latency poison — without pretending we own a private AIR backbone.

Added

• Gaming Boost preset: full TUN; assist / fragment / Survive off; Smart Multipath + Smart Connect on; GamingBoostActive persisted.
• UDP-aware Smart Connect (RankProfile.Gaming): prefer Hy2/TUIC/WG; penalize Vision/REALITY when a nearby UDP peer works.
• Xray burstObservatory interval 15s when Gaming + multipath (else 1m).
• Tighter path-health cadence while Gaming Boost is Connected.
• Bundled game-catalog.json + Settings Apply game catalog → App Network Direct (optional; default stays full tunnel).
• Tip: docs/tips/gaming-boost.md.

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release

Settings → Gaming Boost → Save → Connect. Assist/fragment off; multipath tip for Xray classic. Play/Translate may fail (expected). UDP/Unity row should match V2Box on the same link.

v2rayF v2.6.3.5

v2.6.3.5

Why

Windows TUN could stay Connected with localhost SOCKS green while the v2rayF WinTun adapter was gone — kill switch still armed → device blackhole. Android already fail-closed on missing VpnService Network (TunVpnMissingMs); desktop only returned advisory HTTPS miss (-1).

Fixes

• Desktop ProbeTunAppPathAsync: missing v2rayF adapter → TunVpnMissingMs (same Connect fail-closed gate as Android).
• Kill switch waits on DesktopTunInterface (no PowerShell adapter race).
• Soft recovery / session resume escalate when WinTun stays missing after RefreshRuntime.
• Golden-matrix soak runbook + scorecard rows for lock/unlock and Windows TUN honesty.

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release

Windows (Admin + TUN): Connect → Get-NetAdapter -Name v2rayF present; sleep/wake must recover or tear down — never Connected blackhole. Android lock/unlock checklist still in docs/tips/golden-matrix-2.6.3.4.md.

v2rayF v2.6.3.4

v2.6.3.4

Why

After lock → unlock while Connected, system internet died until Disconnect+Connect. Wake resume treated localhost SOCKS + VpnService Network as healthy even when the TUN app-path was dead, then only called ReportVpnReady. When soft recovery did run, SessionResume used forceRebind: false (hash no-op, same fd). Unlock without opening v2rayF often never fired resume at all.

Fixes

• Resume early-success requires IsResumePathHealthy (live path and not TunWeak).
• SessionResume EstablishVpnAsync(..., forceRebind: true) when 90s rebind throttle allows; otherwise still RefreshRuntime with current fd.
• VpnService registers USER_PRESENT + SCREEN_ON → NotifySessionRecovery (existing 5s throttle).
• Connect / IG MQTT exclusions / Meta QUIC shove / fail-closed-on-missing-VPN unchanged.

Verify

dotnet test src/v2rayF.Core.Tests/v2rayF.Core.Tests.csproj -c Release

Android: Connect → lock 1–2 min → unlock → Chrome HTTPS without opening v2rayF. IG Direct / Play still OK.