Past Updates

Details for versions 1.4.0 to 1.5.0 were skipped since those focused on UI tweaks. The move from 1.5.0 to 1.6.0 streamlined configuration storage and introduced a key feature for selecting specific nodes in rules, along with a host of fixes following the storage refactor.

What’s New

Subscriptions

Subscriptions now let you add a managed proxy list to the Tunna app, fully integrated with its health checker and stats manager. The health checker was overhauled to fit within the 50 MB memory limit of the iOS network extension and to support more than 100 nodes. Outbounds are now checked in batches for latency, and only the number defined by concurrency settings plus the static rule nodes stay in memory. Checks adapt to app state with separate intervals for foreground, background and sleep. In observability settings you’ll find active and idle intervals, while sleep checks run every 10 minutes.

Battery Usage Optimization

Latency and usage stats handling was reworked to store data from one minute up to a year per outbound. This cuts CPU load and boosts battery life. Stats update every minute when the app is in the foreground and immediately on launch. In the background they flush before sleep or when the tunnel stops. Overnight tests showed just 8 percent battery drain in sleep mode and only six minutes per hour of background activity in iOS battery stats.

What’s New

Health Checks and Performance

Version 1.3 features seamless health checks that operate in the background without disrupting existing tunnel connections. These checks use a separate, disposable Xray Core instance optimized with specifically tailored buffers and timeouts for efficient performance.

Enhanced Configuration Management

Previously, in version 1.1, changes to configuration required a complete restart of the tunnel, leading to service interruptions that impacted user experience. Version 1.2 addressed this by requiring the recreation of the entire Xray Core instance, a method effective but susceptible to tunnel failures during heavy loads such as DNS query bursts or large file downloads.

Version 1.3.3 resolves these issues by enabling configurations to be updated seamlessly, without the need for restarting the tunnel provider or recreating the Xray Core instance. It allows different components of the application’s configuration, such as inbounds, outbounds, routing, or logs, to be reloaded independently and only as needed. This targeted approach not only streamlines the update process but also minimizes the memory required for applying configuration changes, thereby avoiding significant spikes.

Optimization of Geosite Dataset

This update also enhances the Xray GeoSite dataset by limiting domain entries to a maximum of three segments and removing any entries that are already covered by regex entries. This deduplication process significantly reduces memory usage for rules involving records with numerous domain entries.