Update README_en.md

Delete app-release.apk
bug-fixed
2026-07-27 21:51:29 +08:00 · 2026-07-27 21:48:33 +08:00 · 2026-07-27 21:48:01 +08:00 · 2026-07-27 21:33:17 +08:00 · 2026-07-26 21:51:35 +08:00 · 2026-07-24 23:03:46 +08:00
36 changed files with 1421 additions and 495 deletions
@@ -1,111 +1,186 @@
-# Quick Overview
+## What is SG?
 * **Platform Adaptation**: Supports Linux, Windows, macOS, Android, (Tob, small machines: HP-UX, Solaris, AIX)<br>
 * **CPU Architectures**: Supports x86, arm, mips, riscv (Tob: alpha, PowerPC, SPRAC)<br>
 * **Security Focus**: Intranet-to-intranet penetration, no need to map any ports to the external network, no changes to firewall configurations<br>
 * **Bandwidth Emphasis**: "4G phone + v6 broadband" accesses intranet services using P2P (based on TCP protocol, v4 supports NAT1-3 penetration)<br>
 * **Cost Savings Priority**: No need to buy VPS, no need for a public IP; old Android phones at home can be used as servers<br>
 * **Reliability Priority**: On-demand availability, can provide uninterrupted service 24/7, and unaffected by UDP protocol QoS issues<br>
 * **Control Emphasis**: Client configuration is straightforward, and service can be controlled to start/stop anytime, anywhere<br>
 * **Environmental Friendliness**: No installation required, compact size (around 1MB for the mini version), all-in-one, high performance with minimal resource usage<br>
 * **Portability Priority**: Whether working or on vacation, everything is in control as long as the phone has a network connection<br>
 * ... If this is what you want! Please continue reading patiently; if you have additional requirements, please raise an issue, and there's also interesting stuff in the [Update History].
-* **Free**, considering open source after stable testing.
+* A cross-network-segment remote port mapping tool
-* Includes an Android client and a server that needs to be installed in the intranet.
+  * Supports intranet-to-intranet and intranet-to-extranet mapping
 * A portable, flexibly-controlled access gateway
  * All configuration is done on the app client — full visibility, highly secure and controllable
  * Access entries can be configured on the mobile phone running the app, or on any SG server computer
 * A simple remote file management tool
  * Perform file management operations on both the mobile device and server endpoints
 * A simple SOCKS proxy tool
 * A simple HTTP(S) proxy tool
 * ......
-# APP Configuration (Required) --- Typical usage may be affected if not configured properly
+## Key Features
 * Must configure "Allow Background Running" permission, otherwise, the connection will be severed by the system when switching to the background.
 * Must configure "Keep Network Connection Always Active during Sleep," otherwise, the connection will be severed by the system once in sleep mode.
 * "Allow Auto-Start" permission can be configured, otherwise, Android server mode cannot start on boot (v0.30 and later versions).
 * "Microphone" permission can be configured, otherwise, the Android server cannot provide voice monitoring functionality (v0.30 and later versions).
 * Note: SG official proxy does not provide data forwarding to IPs in Hong Kong, Macau, Taiwan, and foreign countries.
-## What is smarGate?
+* All mappings are configured through the app client; the server requires zero configuration at runtime
-#### Officially named "Mobile Gateway," it exposes the server network located in the intranet on demand through the mobile client. The core engine is implemented in C++.
+* Supports server-to-app and server-to-server port mapping
-#### "Mobile Gateway" is a user's private gateway, and all shared access entry points are in the client, not like other penetration tools that promote public access entry points based on domain names. In other words, smarGate is like carrying a personal theft-proof door, while other penetration products place the theft-proof door in public places... Although they need a key, there's a profession called a locksmith.
+  * Map any port of any machine on the server's LAN to the app's mobile phone, enabling penetration access via the phone's local port
  * Through app client configuration, map any host/port on Server A's LAN to Server B's host
 * Supports chained proxy
 * Supports multi-user isolation
 * Supports IPv4/IPv6 with TCP-based P2P tunneling
 * Supports self-hosted proxy for data forwarding
 * Supports encrypted data tunnels (TLS)
 * Supports automatic tunnel selection
  * Priority: P2P → custom proxy → official proxy (fallback)
 * Supports automatic version upgrades and one-click upgrade from the app client
 * SOCKS and HTTP(S) proxy support custom IP whitelists and domain whitelists, including CIDR IP ranges and domain wildcards
 * Supports both TCP and UDP protocols
  * UDP uses UDP-over-TCP mode
 * ......
-##### It has the following technical features:
+## What Problems Does SG Solve?
-* **Security**
+
-  * The mobile client serves as the main access entry, opened on demand and closed promptly.
+* Secure access to intranet resources regardless of network boundaries
-  * Supports port mapping networking between servers (v0.31 and later versions).
+* High-bandwidth secure data transfer via P2P
-  * Computers can connect to the internal network through access to open ports on the phone in a hotspot or Wi-Fi environment (the client will display the phone's IP).
+* Exposing intranet services when you have a public IP
-  * The phone network is generally in a private network segment that others cannot access.
+* ......
-  * User isolation.
+
-* **Scalability**
+## SG Version Guide   
-  * Based on intranet segment proxy, it can work with numerous tools to achieve various network service capabilities (telnet, ssh, http services, intranet cameras, remote desktop, etc.).
+
-  * Geared towards geeks, can access custom intranet services (RPC).
+  Android provides two build variants (Product Flavors), **Base** and **Advance**, sharing the same codebase and     
-* **Convenience**
+  differentiated through compile-time feature toggles + R8 dead code elimination:
-  * Simple configuration with the mobile client.
+                                                                                                                     
-  * Dynamic addition and removal of service capabilities.
+  | Feature | Base | Advance |                                                                                       
-* **High Performance**
+  |------|:----:|:-------:|
-  * Starting from version 0.1.1, it uses a proprietary network engine with high performance. The client on a thousand-dollar phone can support over 1,000 concurrent shared accesses.
+  | Proxy Tunnel | ✓ | ✓ |                                                                                           
-  * High-performance design:
+  | File Management | ✓ | ✓ |                                                                                        
-    * Cross-platform implementation of socket multiplexing, supporting models such as poll, epoll, kqueue, port, select, IOCP, etc.
+  | Audio Capture/Transmission | ✗ | ✓ |                                                                             
-    * Uses lock-free algorithms.
+  | GPS Location Tracking | ✗ | ✓ |                                                                                  
-    * Thread pool design.
+  | App Upgrade | ✗ | ✓ |                                                                                            
-    * Socket connection pool.
+  | Screen/Camera Monitoring | ✗ | ✗ |                                                                               
-    * Multi-level task queue.
+                                                                                                                     
-    * ...
+  - **Base** — Lightweight edition. Retains only core proxy tunneling and file management, stripping out             
  high-permission/high-risk modules such as audio, location, upgrade, and monitoring. Smaller APK size with fewer    
  permissions, ideal for users who only need basic proxy and file access.                                            
  - **Advance** — Full-featured edition. Includes all feature modules except monitoring, supporting remote audio,
  location tracking, app upgrade, and other advanced capabilities. Suitable for users who require complete remote    
  management functionality.
    * Huawei phones may flag the Advance version as a "fraud app" by default. To install, first disable Pure Mode,   
  then enable Airplane Mode on the phone before installing. For similar issues on other phone brands, search for     
  solutions online.
 ## How to Use SG?
 * Download the app and register
 * Download the appropriate server version, configure it with your User ID, and run it
 * Log into the app and configure port mapping rules
 * Use the configured mappings to access your services
 ## Want to Dive Deeper?
 <details>
 <summary>
-  <mark><font size=6 color=darkred>Attachment: Interaction Diagram</font></mark>
+<mark><font size=3 color=darkred>View Details</font></mark>
 </summary>
 #
 ## Quick Overview <a href=https://github.com/lazy-luo/smarGate/wiki/快速上手手册>[Quick Start Guide]</a> <a href="https://www.bilibili.com/video/BV1LM411k7Rf">[Video Tutorial - Bilibili]</a><br>
 * **Platform support**: Linux, Windows, macOS, Android (enterprise: HP-UX, Solaris, AIX)<br>
 * **CPU architectures**: x86, ARM, MIPS, RISC-V, LoongArch64 (enterprise: Alpha, PowerPC, SPARC)<br>
 * **Security-first**: "Intranet-to-intranet" tunneling — no ports exposed to the public internet, no firewall configuration changes<br>
 * **Bandwidth-focused**: P2P access to intranet services with "4G phone + IPv6 broadband" (TCP-based, NAT1-3 traversal for IPv4)<br>
 * **Cost-effective**: No VPS required, no public IP needed; repurpose old Android phones as servers<br>
 * **Reliable**: Available on demand, supports 24/7 uninterrupted service, free from UDP QoS throttling<br>
 * **Controllable**: Single-point configuration on the client, with the ability to start/stop services anytime, anywhere<br>
 * **Lightweight**: No installation required, compact footprint (mini version ~1MB), all-in-one, high performance with minimal resource usage<br>
 * **Portable**: Whether working or on vacation, as long as your phone has a network connection, everything is under control<br>
 * ......If all this sounds like what you need, keep reading; if you want more, please submit an issue — the [Changelog] is worth checking out too<br>
 * **Free**. Considering open-sourcing after stability testing.<br>
 * Includes an Android client and a server component to be installed within the intranet.<br>
 ## App Configuration (Required) — Common Misconfiguration Issues
 * **Must** grant "Allow background execution" permission, otherwise the system will disconnect when switching to background
 * **Must** enable "Keep network connection during sleep", otherwise the system will disconnect when entering sleep mode
 * **Recommended** to grant "Allow auto-start" permission, otherwise the Android server mode cannot auto-start on boot (v0.30+)
 * **Recommended** to grant "Microphone" permission, otherwise the Android server cannot provide audio monitoring (v0.30+)
 * **Note**: SG's official proxy does not forward data to IPs in Hong Kong, Macau, Taiwan, or overseas
 ## What is smarGate?<br>
 #### Officially named "Mobile Gateway" — exposes intranet server networks on demand through a mobile client, with the core engine implemented in C++.<br>
 #### The "Mobile Gateway" is a user-private gateway. All shared access entries reside on the client, unlike other tunneling tools that primarily promote domain-oriented public access entries. Analogy: smarGate is like carrying your security door with you; other tunneling products are like placing your security door in a public space — sure, it needs a key, but there's a profession called locksmithing...<br>
 ##### Technical Highlights:<br>
 * **Security** <br>
  * The mobile client serves as the primary access gateway — open on demand, close promptly.<br>
  * Supports server-to-server port mapping networking (v0.31+).<br>
  * Computers can connect to the phone's hotspot or WiFi to access intranet services through ports exposed by the phone (the client displays the phone's IP).<br>
  * Mobile networks are generally private network segments inaccessible to others.<br>
  * User isolation.<br>
 * **Extensibility**<br>
  * Based on intranet segment proxying, can work with numerous tools to enable various network services (Telnet, SSH, HTTP services, intranet cameras, remote desktop, etc.)<br>
  * Geek-oriented: can access custom intranet services (RPC)<br>
 * **Convenience**<br>
  * Single-point configuration on the mobile client<br>
  * Dynamic addition/removal of service capabilities<br>
 * **High Performance**<br>
  * Since v0.1.1, uses a self-developed network engine with high performance — a budget phone client can support 1,000+ concurrent shared accesses<br>
  * High-performance design:<br>
    * Cross-platform socket multiplexing supporting poll, epoll, kqueue, port, select, IOCP models<br>
    * Lock-free algorithms<br>
    * Thread pool design<br>
    * Socket connection pool<br>
    * Multi-level task queues<br>
    * ...<br>
 <details>
 <summary>
 <mark><font size=6 color=darkred>Attachment: Architecture Diagram</font></mark>
 </summary>
 <img src="https://github.com/lazy-luo/smarGate/blob/master/res/smarGateArch.png" /><br>
 </details>
-## What are the main functions of smarGate?
+## What Are the Main Features of smarGate?<br>
-* **Supports Proxy Penetration**
+* **Proxy tunneling support**<br>
-  * The official provides a free proxy server (shared bandwidth, slower when shared by multiple users, best practice is to use a self-owned proxy server).
+  * Official free proxy servers are provided (shared bandwidth, slower with multiple users — best practice is to set up your own proxy server)<br>
-  * <I>If you have your own cloud server (with a public IP), you can customize your proxy server, and install proxy_server on the proxy server. All data transmission goes through the user-configured proxy server (the proxy server needs a certificate, which can be generated automatically or configured with an existing certificate).</I>
+  * <I>If you have your own cloud server (with a public IP), you can configure a custom proxy server by installing proxy_server on it. All data will be forwarded through your configured proxy server (the proxy server requires certificates, which can be auto-generated or you can use existing ones).</I> <br>
 ```
-1、Configuration of the "Proxy Server" is as follows (the proxy server must allow any port "inbound" connections):
+  1. Proxy server configuration (the proxy server must allow inbound connections on any port):
 ```
 ```
-<?xml version="1.0" encoding="GBK"?>
+  <?xml version="1.0" encoding="GBK"?>
-<app-config code="PROXY" name="proxy-server">
+    <app-config code="PROXY" name="proxy-server">
-    <app-parameter>
+        <app-parameter>
-        <proxy-service-port value="9001"/><!--Custom proxy port-->
+            <proxy-service-port value="9001"/><!-- Custom proxy port -->
-        <owner-id value="xxxx" /><!-- xxxx is the user ID returned after successful registration -->
+            <owner-id value="xxxx" /><!-- xxxx is the User ID returned after successful registration -->
-        <access-token value="nnnnn"/><!--Access token, must be a number [optional] -->
+            <access-token value="nnnnn"/><!-- Access token, must be numeric [Optional] -->
-        <ssl-create-certfile value="true" /><!-- If the following options are not used to specify the certificate, it will be generated automatically [Must ensure that openssl is installed], default is false meaning no need to generate -->
+            <ssl-create-certfile value="true" /><!-- If no certificate is specified below, auto-generate one [requires openssl installed]. Default is false (no auto-generation) -->
-        <!-- If you have a certificate and private key, configure the following items. Start a secure SSL channel. The file names need to be configured correctly. If there is no certificate, no need to configure. Enable the above option to generate the certificate automatically.
+          <!-- If you have your own certificate and private key, configure them below to enable secure SSL channels. Filenames must be correct. If you don't have certificates, you can use the auto-generation option above.
-        <ssl-cacert-file value="xxx.crt"/>
+            <ssl-cacert-file value="xxx.crt"/>
-        <ssl-privatekey-file value="xxx.key"/>
+            <ssl-privatekey-file value="xxx.key"/>
-        -->
+          -->
-    </app-parameter>
+       </app-parameter>
-    <module-parameter>
+       <moudle-parameter>
        <log-level value="LOG_ERROR"/>
        <log-write-mode value="CONSOLE_ONLY"/>
-    </module-parameter>
+      </moudle-parameter>
-</app-config>
+  </app-config>
 ```
 ```
-2. Add the following configuration to the "Server":
+  2. Add the following configuration on the server side:
 ```
 ```
 ......
-<app-parameter>
+    <app-parameter>
-    <ssl-create-certfile value="true" />
+             <ssl-create-certfile value="true" />
-    <!-- If the proxy server starts a secure SSL channel, you must configure the certificate and private key here.
+       <!-- If the proxy server has SSL enabled, certificates and private key must be configured here
-    <ssl-cacert-file value="xxx.crt"/>
+         <ssl-cacert-file value="xxx.crt"/>
-    <ssl-privatekey-file value="xxx.key"/>
+         <ssl-privatekey-file value="xxx.key"/>
-    -->
+       -->
-</app-parameter>
+    </app-parameter>
-<module-parameter>
+    <moudle-parameter>
-  ......
+      ......
-</module-parameter>
+    </moudle-parameter>
-<!-- Configure the IP or domain name + port of the proxy server mentioned above. Note: the IP must be a public IP. The ssl option must be configured correctly. If the proxy server has a certificate (including automatically generated certificates) and is effective, configure it as true, otherwise, it is false -->
+    <!-- Configure the proxy server IP or domain + port above. Note: the IP must be a public IP. The ssl option must be correctly configured — set to true if the proxy server has certificates (including auto-generated ones) and they are active, otherwise false -->
-<channel address="xxx.xxx.xxx.xxx:9001" ssl="true" token="nnnnn" /><!--Access token, must match the proxy server, if not, no need to configure -->
+    <channel address="xxx.xxx.xxx.xxx:9001" ssl="true" token="nnnnn" /><!-- Access token, must match the proxy server; omit if not configured -->
 ```
-* **Supports P2P Channel**
+* **P2P channel support**<br>
-  * Utilizes TCP protocol for P2P penetration, enhancing security.
+  * Uses TCP protocol for P2P tunneling, enhancing security<br>
-  * Not all networks support P2P, depending on the NAT types on both ends.
+  * Not all networks support P2P — depends on the NAT types at both ends
-  * From version v0.14 and above, directly supports IPv6 and provides firewall penetration.
+  * v0.14+ directly supports IPv6 with firewall traversal capability
-  * P2P Test Conclusion: Unable to establish a connection when one end is NAT4 and the other end is NAT3 or NAT4.
+  * P2P test conclusion: P2P fails when one end is NAT4 and the other is NAT3 or NAT4<br>
-Note: NAT1-〉Full Cone, NAT2-〉Restricted Cone, NAT3-〉Port Restricted Cone, NAT4-〉Symmetric
+  Note: NAT1 → Full Cone, NAT2 → Restricted Cone, NAT3 → Port Restricted Cone, NAT4 → Symmetric<br>
  <table>
    <th>Server NAT</th><th>Client NAT</th><th>P2P Success</th>
    <tr><td>NAT1-3</td><td>NAT1-3</td><td>YES</td></tr>
@@ -115,508 +190,616 @@ Note: NAT1-〉Full Cone, NAT2-〉Restricted Cone, NAT3-〉Port Restricted Cone,
    <tr><td>NAT3-4</td><td>NAT4</td><td>NO</td></tr>
  </table>
-* **Supports External Network Publishing (Contrary to Security Design Principles, Opened in v0.31)**
+* **Public exposure support** (contrary to the security-first design philosophy, opened in v0.31)<br>
-  * The main mode of other intranet penetration tools, directly mapping internal network services to external network ports.
+  * The primary mode promoted by other intranet tunneling tools — directly mapping intranet services to public-facing ports<br>
-* **Supports P2P Port Mapping Between Servers (v0.31 and Later Versions)**
+* **Server-to-server P2P port mapping** (v0.31+)<br>
-  * Specific configuration mainly supported through ip@index.
+  * Configuration primarily via the ip@index format<br>
-  * 
+
 <details>
 <summary>
-  <mark><font size=6 color=darkred>Attachment: Brief Overview of Main Functions</font></mark>
+<mark><font size=6 color=darkred>Attachment: Key Feature Summary</font></mark>
 </summary>
-  
+
-1. Supports TCP-based P2P connection tunnels
+```
-   - Secure and reliable, avoiding QoS issues
+1. TCP-based P2P connection tunnels
-  
+  — Secure and reliable, avoids QoS throttling
-2. Supports all types of protocols based on TCP for "transparent proxy"
+2. Transparent proxying for all TCP-based protocols
-   - Can proxy all internal TCP services (SSH, RDP, SMB, VNC, cameras, database services, etc.)
+  — Can proxy all intranet TCP services (SSH, RDP, SMB, VNC, cameras, databases, etc.)
-     
+3. HTTP and HTTPS-to-HTTP support
-3. Supports HTTP, HTTPS to HTTP
+  — HTTP header rewriting, proxying HTTPS services as HTTP
-   - Supports HTTP-head rewrite, can proxy HTTPS services as HTTP
+4. UDP-over-TCP
-     
+  — Proxy support for UDP-based services
-4. Supports UDP over TCP
+5. Transparent IPv6 tunneling (no need to manage IPv6 addresses)
-   - Can proxy services using the UDP protocol
+  — Automatic IPv6 tunnel establishment, always use IPv4 addresses for access
-     
+6. Custom proxy support (requires a public IP) — handles all data forwarding
-5. Transparent mode (no need to focus on IPv6 addresses) supports IPv6 tunnel
+  — Automatically connects to the custom proxy when P2P is unavailable
   - Automatically establishes a v6 tunnel, always using v4 address for access
 6. Supports custom proxy (requires public IP), taking over all data forwarding
   - When P2P is not possible, automatically connects to a custom proxy for data forwarding
 7. Custom proxy supports token and whitelist configuration
-   - Supports security mechanisms
+  — Security mechanisms included
-8. Supports multi-level cascading proxy
+8. Multi-level cascading proxy
-   - Supports chained proxies, supports multi-level acyclic proxies
+  — Chained proxy support, multi-level loop-free proxy
-9. Supports mobile phones as the only access point — Secure + Mobile Convenience
+9. Mobile phone as the sole access gateway — security + mobile convenience
-   - With the phone in hand, access is available on demand
+  — Phone in hand, access on demand
-10. Dynamic configuration for port mapping, supports "hot-plugging" of mapping configurations
+10. Fully dynamic port mapping configuration with hot-plug support
-    - Proxies are effective immediately when added or removed, no need to restart
+  — Proxy additions and deletions take effect immediately, no restart required
-11. All features are "one-point configuration" on the app side
+11. All features configurable from the app — single-point configuration
-    - Client configuration is a single point, no need for server configuration during runtime
+  — Client-side one-click configuration, server requires zero config at runtime
-12. Supports automatic detection and connection of P2P tunnels and custom proxy tunnels
+12. Automatic P2P tunnel and custom proxy tunnel detection and connection
-    - No intervention required, the app automatically connects and retries
+  — No manual intervention; the app auto-connects and auto-retries
-13. Supports dynamic negotiation of ports, supports specifying negotiated ports
+13. Dynamic and designated negotiation port support
-    - Default dynamic port negotiation, supports negotiating ports in conjunction with firewall configurations
+  — Default dynamic port negotiation; supports designated negotiation ports for firewall configuration
-14. Supports tunnel connection priority (P2P -> Custom Proxy -> Official Proxy)
+14. Tunnel connection priority (P2P → Custom Proxy → Official Proxy)
-    - During data transmission, supports priority for tunnels
+  — Priority-based tunnel selection during data transfer
-15. Supports SSL encrypted tunnel
+15. SSL-encrypted tunnels
-    - Supports SSL encryption for both P2P and proxy tunnels, ensuring data transmission is secure
+  — SSL encryption for both P2P and proxy tunnels, ensuring data confidentiality
-16. Supports traffic limitation
+16. Traffic throttling support
-    - Supports network bandwidth limitation, default is unlimited
+  — Network bandwidth limiting, unlimited by default
-17. Supports network switching (e.g., mobile <-> Wi-Fi) automatic identification + automatic connection
+17. Automatic network switch detection (e.g., Mobile ↔ WiFi) with auto-reconnection
-    - Intelligent reconnection on the app side, ensuring service availability at all times
+  — Intelligent app-side reconnection, always ensuring service availability
-18. Supports port mapping between different LAN hosts — If one end host has a public IP, it can be accessed directly from the external network (version > v0.31)
+18. Cross-LAN host port mapping — direct public access if one host has a public IP (v0.31+)
-    - Supports server-side networking mapping, traffic does not need to pass through the mobile app (traditional penetration mode)
+  — Server-to-server mesh mapping, traffic does not pass through the mobile app (traditional tunneling mode)
-19. App supports server mode, can configure the phone as a server
+19. App supports server mode — can configure the phone as a server
-    - Android phones can be used as servers
+  — Android phones can act as servers
-20. Supports remote file management functionality: browsing, uploading, downloading, deleting, supports resuming downloads (version >= v0.31.6)
+20. Remote file management: browse, upload, download, delete, with resume support (v0.31.6+)
-    - Activates file management functionality when there is P2P or custom proxy, basic operations on files on the phone and server-side computer are possible
+  — File management features activate when P2P or custom proxy connections are available; basic file operations on both phone and server
-21. Supports built-in SOCKS5, HTTP proxies (version >= v0.32.1)
+21. Built-in SOCKS5 and HTTP proxy (v0.32.1+)
-    - Since there are third-party specialized tools such as ss5, squid, etc., SOCKS5 and HTTP proxies are optional features
+  — Since professional third-party tools like SS5 and Squid exist, SOCKS5 and HTTP proxy are optional features
-22. SOCKS5, HTTP proxies support domain and IP whitelists (version >= v0.32.1)
+22. SOCKS5 and HTTP proxy support domain and IP whitelists (v0.32.1+)
-    - Domain whitelist supports four matching modes (exact match, forward match, backward match, middle match), default configuration file name: .white_list
+  — Domain whitelist supports four match modes (exact, prefix, suffix, substring), default config file: .white_list
-    - IP whitelist supports CIDR format ip-range configuration, default configuration file name: .ipchecks
+  — IP whitelist supports CIDR-format IP range configuration, default config file: .ipchecks
-      
+...to be continued
 ... To be continued
-</details>
+```
 ## User Guide:
 ### 1. Download the App and Register a New User
 * Download the Android app (app-release.apk includes both the client and server) supporting armv7 and arm64 CPU architectures.
 * Register a new user (Invitation code is required and can be any number. Note: If the required information is not filled in completely or contains Chinese characters, registration will fail).
 * After successful registration, remember to note the returned service ID (N). [Important]: After successful registration, be sure to complete the first login within 1 hour.
 <details>
 <summary>
  <mark><font size=5 color=darkred>Expand for Illustrations</font></mark>
 </summary>
 ![Login](https://github.com/lazy-luo/smarGate/blob/master/res/login.png)
 ![Register](https://github.com/lazy-luo/smarGate/blob/master/res/register.png)
 ![Register Success](https://github.com/lazy-luo/smarGate/blob/master/res/registerok.png)
 </details>
-### 2. Download Server and Configure
+## Usage Guide:<br>
-
+<a href="https://www.bilibili.com/video/BV1LM411k7Rf">Video Tutorial - Bilibili</a><br><br>
-* Download the server version suitable for the intranet server (currently supports linux-x86-32/64, windows, and linux-arm [Raspberry Pi, Synology], also: Android app comes with server mode).
+<a href="https://www.baidu.com/s?wd=smargate%20内网穿透">Usage Examples - Baidu</a><br><br>
-* Unzip the server compression package and modify the configuration file (conf-proxy.xml):
+<a href="https://www.google.com/search?q=smargate+内网穿透">Usage Examples - Google</a>
 ### 1. Download the App & Register a New User
 * Download the Android app (app-release.apk includes both client and server) — supports armv7 and arm64 CPU architectures<br>
 * Register a new user (invitation code is required, must be numeric, can be anything. Note: if required fields are incomplete or contain Chinese characters, registration will fail)<br>
 * After successful registration, be sure to remember the returned Service ID (N). **[Important]**: You must complete your first login within 1 hour of registration<br>
 <details>
 <summary>
-  <mark><font size=5 color=darkred>Configuration Example</font></mark>
+<mark><font size=5 color=darkred>Expand Screenshots</font></mark>
 </summary>
 <img src="https://github.com/lazy-luo/smarGate/blob/master/res/login.png" /><br>
 <img src="https://github.com/lazy-luo/smarGate/blob/master/res/reg.png" /><br>
 </details>
 ### 2. Download the Server & Configure
 * Download the appropriate server version for your intranet environment (currently supporting Linux x86-32/64, Windows, and Linux-ARM [Raspberry Pi, Synology]; also: Android app has built-in server mode)<br>
 * Extract the server archive and modify the configuration file (conf-proxy.xml):<br>
 <details>
 <summary>
 <mark><font size=5 color=darkred>Configuration Example</font></mark>
 </summary>
-```xml
+```
  <?xml version="1.0" encoding="GBK"?>
    <app-config code="PROXY" name="proxy-server">
       <app-parameter>
-	<!-- [ none | first | only ] , none is the default. Enable SSL encryption for P2P connections, only means only accept encrypted connections -->
+    <!-- [ none | first | only ], none is default. Enable SSL encryption for P2P connections; "only" means only encrypted connections are accepted -->
-	<ssl-tunnel-required value="first" />
+    <ssl-tunnel-required value="first" />
-	<!-- If not specifying a certificate with the following options, it will generate a certificate [must ensure openssl is installed], default is false means no need to generate -->
+    <!-- If no certificate is specified below, auto-generate one [requires openssl installed]. Default is false (no auto-generation) -->
-	<ssl-create-certfile value="true" /> 
+    <ssl-create-certfile value="true" />
- <!-- The following options are only applicable to the mini version under dynamic, specify the actual files of the ssl library and crypto library, on Linux, you can obtain them with: ldd $(which openssl)|grep -E "libssl|libcrypto"|awk '{print $1}' -->
+ <!-- The following options apply only to the mini version under dynamic. Specify the actual paths of the SSL and crypto libraries. On Linux, obtain via: ldd $(which openssl)|grep -E "libssl|libcrypto"|awk '{print $1}'
-	<libssl value="libssl.so" />
+    <libssl value="libssl.so" />
-	<libcrypto value="libcrypto.so" />
+    <libcrypto value="libcrypto.so" />
 -->
       </app-parameter>
       <moudle-parameter>
        <log-level value="LOG_ERROR"/>
        <log-write-mode value="CONSOLE_ONLY"/>
-        <app-name value="xxxxx [name of service points]." /><!-- need to modify -->
+        <app-name value="xxxxx [name of service points]." /><!-- need modify -->
-        <app-description value="yyyyy [description of service points]" /><!-- need to modify -->
+        <app-description value="yyyyy [description of service points]" /><!-- need modify -->
-	<!-- user-audit needs to be modified (N is the service ID returned after successful registration, index is the custom server instance number, it is recommended to start from 1, cannot be repeated. For example: [12345:1]) -->
+    <!-- user-audit need modify (N is the Service ID returned after successful registration; index is a custom server instance number, recommended starting from 1, must not duplicate. e.g., [12345:1])-->
        <user-audit value="N:index"/>
    </moudle-parameter>
  </app-config>
 ```
 </details>
-### 3. Run the Intranet Server (Command Parameters Explanation i: Max incoming connections, o: Max outgoing connections, w: Max threads)
+### 3. Run the Intranet Server (command parameters: i = max inbound connections, o = max outbound connections, w = max threads)<br>
-* Execute the command on Linux: `chmod +x proxy_server && nohup ./proxy_server -i1000 -o1000 -w8 >/dev/null &`
+* **Linux**: `chmod +x proxy_server && nohup ./proxy_server -i1000 -o1000 -w8 >/dev/null &` <br>
-* Execute the command on Windows: `proxy_server.exe -i1000 -o1000 -w8`
+* **Windows**: `proxy_server.exe -i1000 -o1000 -w8` <br>
-* Android Phone/Device: Run the app -> In edit mode, configure server information -> Turn on the "Server" switch -> Restart the app
+* **Android phone/device**: Run the app → in edit mode, configure server info → toggle "Server" switch on → restart the app <br>
-* For OpenWrt MIPS devices installation, see: [【Correct Usage on MIPS Linux】](https://github.com/lazy-luo/smarGate/issues/65)
+* **OpenWrt MIPS devices**: see <a href=https://github.com/lazy-luo/smarGate/issues/65>[Correct usage on MIPS Linux]</a><br>
 ### 4. Log in to the mobile app and configure port mapping
 * In the client, you can see the online server ("access point") and define port mapping rules on the client.
 ### 4. Log into the Mobile App & Configure Port Mappings <a href="https://github.com/lazy-luo/smarGate/wiki/常用服务穿透配置">[Common Service Configurations]</a><br>
 * In the client, you can see the online servers ("Access Points") and define port mapping rules on the client<br>
 <details>
 <summary>
-  <mark><font size=5 color=darkred>Expand for Illustrations</font></mark>
+<mark><font size=5 color=darkred>Expand Screenshots</font></mark>
 </summary>
 <img src="https://github.com/lazy-luo/smarGate/blob/master/res/proxy.png" /><br>
 <b>For server-to-server port mapping, append the server index number to the IP in the format: ip@idx</b>
 <img src="https://github.com/lazy-luo/smarGate/blob/master/res/server-proxy.png" /><br>
 </details>
-![Operational](https://github.com/lazy-luo/smarGate/blob/master/res/oper2.png)
+### 5. Computers or Phones Can Access Services Configured on the Mobile Client (e.g., SSH, HTTP, etc.)<br>
 <b>In the configuration, the "Remote IP" corresponds to the IP of a host in the intranet ("access point"). "localhost" or "127.0.0.1" represents the machine where the internal server-side is located.</b>
 ![Operational](https://github.com/lazy-luo/smarGate/blob/master/res/oper3.png)
 </details>
-### 5. Computers or phones can directly access the services set in the mobile client (such as SSH, HTTP, etc.)
+## Additional Notes:<br>
-
+* All versions are self-contained with bundled dependencies — ready to use out of the box.<br>
-## Additional Information:
+* The system will automatically purge "zombie accounts" that have been unused for 30+ days.<br>
-* All versions come with packaged dependencies and are ready to use.
+* Android client required permissions:<br>
-* The system will automatically clear "zombie accounts" that have not been used for more than 30 days.
+>> 1. Background execution permission (the app will disconnect when backgrounded if not granted)<br>
-* Android client requires permissions:
+>> 2. Network access permission (basic permission)<br>
-    1. Background execution permission (if not allowed, the connection will be disconnected when the app goes to the background).
+* Phone settings (Android):<br>
-    2. Network access permission (basic permission).
+>> 1. Settings → Wireless & Networks → WLAN → Keep connection during sleep → "Always" (otherwise the system will disconnect during sleep)<br>
-* Phone settings (Android):
+>> 2. Settings → Wireless & Networks → Mobile Network → Advanced → Always keep data connection → "Enabled"<br>
    1. Settings -> Wireless & networks -> WLAN -> Keep Wi-Fi on during sleep "Allow" (otherwise, the connection will be disconnected during system sleep).
    2. Settings -> Wireless & networks -> Mobile network -> Advanced -> Keep mobile data always active "Allow".
 * Q: How to download and install the Android app?
  >> A: Open the link [https://github.com/lazy-luo/smarGate/raw/master/app-release.apk](https://github.com/lazy-luo/smarGate/raw/master/app-release.apk) in the browser of your Android phone, and then install it when prompted.
  >> B: Pan.baidu.com download link for the latest test version: [https://pan.baidu.com/s/14Iq60kxHW711NVoCVKWySg](https://pan.baidu.com/s/14Iq60kxHW711NVoCVKWySg)
  >> C: Gitee address (faster download speed, no issues with image display): [https://gitee.com/lazy-luo/smarGate](https://gitee.com/lazy-luo/smarGate)
  >> D: If needed, add WeChat: ws_lzy008, specifying "smarGate". Depending on the situation, a technical discussion group may be formed.
 * Q: Do I need to install the server on every device at home to access multiple devices on the local network?
  >> A: No, you only need to install the server on any one device.
 * Q: Why sometimes unable to connect?
  >> A: The server will automatically disconnect after about 2-3 minutes of idle time and will reconnect after waiting for about 10 seconds.
 * Q: Why can't I establish a P2P connection over IPv6?
  >> A: Please update both the client and server to the latest version; make sure your phone and the internal computer can obtain a global IPv6 address; ensure it is not blocked by the firewall (Windows); check if both IPv6 can be routed out; and check the hosts file to ensure the hostname resolves to the IPv6 address.
 * Q: Why does P2P connection over IPv4 and IPv6 not have UDP ports?
  >> A: smarGate uses TCP protocol for P2P penetration, which provides better security and connection reliability.
 * Q: Why can't the phone NAS client log in?
  >> A: Make sure the phone NAS client's IP is not blacklisted, and it does not include "localhost" (127.0.0.1).
 * Q: How to share machines in a remote company network with multiple teams in different locations?
  >> A: Connect the phone to Wi-Fi, let team members' computers connect to the phone's IP: PORT, and access directly through the phone's proxy. Tested on phones with 2k resolution or higher, it can support sharing access for up to a hundred people.
 * Q: Why doesn't the Windows server have a console window?
  >> A: To prevent accidental shutdown of the server, the new version of the Windows server runs in the background. If you need to close it, use "Task Manager".
 * Q: Do I still need to go through an intermediate proxy when using P2P?
  >> A: No, connect directly point-to-point, and the network speed depends on the networks of your client and server.
 * Q: Does smarGate consume a lot of power when running in the background?
  >> A: After long-term testing, for occasional use, the power consumption is similar to any system process, extremely low. In the case of frequent background use, the overall power consumption is equivalent to occasional use of WeChat. The power management prompt "Frequent background refresh..." can be ignored; it appears whenever there is background data transfer, and the key is to look at the power consumption ranking.
 * Q: What are the connection priority rules in smarGate?
  >> A: Prefer P2P connection. If there is no P2P, use a custom proxy connection. If neither of the previous two connects, use the official proxy connection.
 * Q: Can the same user log in from multiple locations?
  >> A: Multiple logins are allowed, but only one client can perform P2P at a time. Each server machine can only run one instance, and the configuration of each instance ensures that the serial number is not duplicated, otherwise it will not work properly.
 * Q: Can the server support Android phones?
  >> A: The Android app version 0.27 has added support for "server mode".
 * Q: What does the different color represent in the client?
  >> A: P2P identification under IPv4:
    ![IPv4 P2P](https://github.com/lazy-luo/smarGate/blob/master/res/ipv4p2p.png)
  >> A: P2P identification under IPv6:
    ![IPv6 P2P](https://github.com/lazy-luo/smarGate/blob/master/res/ipv6p2p.png)
  >> A: User-defined proxy identification:
    ![User-defined proxy P2P](https://github.com/lazy-luo/smarGate/blob/master/res/userdefineproxyer.png)
 ## Best Practices
 * The following are recommended best practices for reference:
  1. Set the Android client to "Auto Login" to avoid the hassle of entering the username/password each time.
  2. Let the Android client run in the background after setting it up. If it remains in the foreground, it will refresh regularly, consuming power due to the WebView component.
  3. Keep the server running in the background at all times for security and peace of mind. Only you can access it.
 ## Disclaimer
 * Please read the following disclaimer carefully. Your use of the smarGate tool software indicates your acceptance of the following:
  1. It is strictly forbidden to use this software for computer hacking and any other activities that may harm computer information network security.
  2. This software is a regular network access tool. Please use it reasonably and legally. Do not use it for activities that violate laws, morals, and affect the interests of others. If used for illegal purposes, the user is responsible for any consequences, and the developer of this software assumes no responsibility or loss.
 ## Donation
 If you find smarGate helpful, feel free to make a donation to support the long-term development of the project!
 Note: It is recommended to include your registered username with the donation.
 <details>
 <summary>
-	<mark><font size=5 color=darkred>WeChat Donation</font></mark>
+<mark><font size=5 color=darkred>FAQ</font></mark>
 </summary>
 * **Q: How to download and install the Android app?**<br>
  >> 1. Open https://github.com/lazy-luo/smarGate/raw/master/app-release.apk in an Android browser<br>
  >> 2. Download and install from the popup dialog<br>
  >> The GitHub release may lag slightly behind the latest test version.<br>
  >> Baidu Disk download link: https://pan.baidu.com/s/14Iq60kxHW711NVoCVKWySg <br>
  >> Gitee mirror (faster access, no image display issues): https://gitee.com/lazy-luo/smarGate <br>
  >> If needed, add WeChat: ws_lzy008 with the note "smarGate" — a technical discussion group may be formed based on interest.<br>
 * **Q: To access multiple devices on the home LAN, does each device need the server installed?**<br>
   >> A: No. Just install the server on any one device.<br>
 * **Q: Why does the connection sometimes fail?**<br>
   >> A: The server will automatically disconnect after 2-3 minutes of idle time. Wait about 10 seconds for automatic reconnection.<br>
 * **Q: Why can't IPv6 P2P work?**<br>
   >> A: Update both client and server to the latest version; ensure both the phone and intranet computer can obtain a global IPv6 address; ensure the firewall is not blocking (Windows); verify that both IPv6 addresses are routable; check the hosts file to ensure hostnames resolve to IPv6 addresses.<br>
 * **Q: Why are there no UDP ports for IPv4 and IPv6 P2P connections?**<br>
   >> A: smarGate uses TCP protocol for P2P tunneling, providing better security and connection reliability.<br>
 * **Q: Why can't the mobile NAS client log in?**<br>
   >> A: Ensure that localhost (127.0.0.1) is not in the mobile NAS client's IP blacklist.<br>
 * **Q: How to share a remote office's intranet machines with multiple teams?**<br>
   >> A: Connect the phone to WiFi and have team members' computers connect to the phone's IP:PORT, directly accessing through the phone proxy. In practice, a phone priced above 2,000 yuan can support sharing among approximately 100 team members.<br>
 * **Q: Why is there no console window for the Windows server?**<br>
   >> A: To prevent accidental closure, the new version of the Windows server runs in the background. If you need to close it, use Task Manager.<br>
 * **Q: Does P2P traffic still go through the intermediary proxy?**<br>
   >> A: No. It's a direct peer-to-peer connection. The speed depends on the networks where your client and server are located.<br>
 * **Q: Is smarGate's background operation power-hungry?**<br>
   >> A: After extensive testing, for occasional usage, power consumption is extremely low — comparable to any system process. For frequent background usage, overall power consumption is similar to occasional WeChat usage. Power management warnings about "frequent background refresh..." can be ignored — any background data transfer triggers these alerts; the key metric is the power consumption ranking.<br>
 * **Q: What are smarGate's connection priority rules?**<br>
   >> A: P2P connection is preferred. When P2P is unavailable, a custom proxy connection is used. When neither is available, the official proxy connection is used.<br>
 * **Q: Can the same user log in from multiple locations?**<br>
   >> A: Yes, multi-point login is supported, but only one client can establish P2P connections at a time. Only one server instance can run on a single machine; ensure server instance indices do not duplicate, otherwise normal operation will be affected.<br>
 * **Q: Can the server run on an Android phone?**<br>
   >> A: Starting from v0.27, the Android app has added "Server Mode" support.<br>
 * **Q: What do the different colors on the client mean?**<br>
   >> A: IPv4 P2P indicator:<br>
   ![ipv4 p2p](https://github.com/lazy-luo/smarGate/blob/master/res/ipv4p2p.png)<br>
   >> A: IPv6 P2P indicator:<br>
   ![ipv6 p2p](https://github.com/lazy-luo/smarGate/blob/master/res/ipv6p2p.png)<br>
   >> A: Custom route indicator:<br>
   ![userdefineproxyer p2p](https://github.com/lazy-luo/smarGate/blob/master/res/userdefineproxyer.png)<br>
 </details>
 ## Best Practices<br>
 * Recommended best practices for reference:<br>
  1. Set the Android client to "Auto Login" to avoid the hassle of entering username/password each time;<br>
  2. After configuration, let the Android client run in the background. Keeping it in the foreground causes periodic refreshes and the WebView control consumes power unnecessarily;<br>
  3. Keep the server running in the background — it's safe and secure, only you can access it;<br>
  ...Usage scenarios...<br>
  <a href="https://cloud.tencent.com/developer/article/1926888">[Home Camera P2P Direct Connection]</a><br>
 ## Disclaimer<br>
 * Please read the following disclaimer carefully. By using the smarGate software tool, you indicate your acceptance of the following:<br>
  1. It is strictly prohibited to use this software for computer hacking or any other activities that compromise computer network security;<br>
  2. This software is a legitimate network access tool. Please use it reasonably and lawfully; do not use it for activities that violate laws, ethics, or the interests of others. If used for illegal purposes, the resulting adverse consequences shall be borne by the user; the developer of this software assumes no responsibility or liability for any losses.<br>
 ## Donation
 If you find smarGate helpful, donations are welcome to support the long-term development of the project!<br>
 PS: It is recommended to include your registered username with the donation.<br>
 <details>
 <summary>
 <mark><font size=5 color=darkred>WeChat Donation</font></mark>
 </summary>
 <img src="https://github.com/lazy-luo/smarGate/blob/master/res/donation.png"/>
 </details>
-## Appendix
+## Appendix<br>
 <details>
 <summary>
-	<mark><font size=5 color=darkred>Update History</font></mark>
+<mark><font size=5 color=darkred>Changelog</font></mark>
 </summary>
-  
+
 ### 2026-07-24 — Updated to v0.41.1<br>
 1. Added three new service display layouts, switchable via the top toolbar with one click:<br>
 - **Card Mode**: Classic card view — service information at a glance
 - **Tab Mode**: Horizontal scrolling tab bar at the top, grouped by access point, with scroll position auto-memorized
 - **Compact Mode**: Compressed list view, click to expand details — ideal for managing large numbers of services
 2. Theme selection support; layout preference automatically persisted (localStorage), restored on next launch<br>
 3. Network engine optimization — improved performance and stability<br>
 4. Added multi-language support for Persian, Korean, and Russian<br>
 5. Version updated to v0.41.1<br>
 ### 2026-03-03 — Updated to v0.40.6<br>
 1. Fixed TCP connection delayed disconnect issue<br>
 2. Tuned the network engine for improved performance<br>
 3. Version updated to v0.40.6<br>
 ### 2025-09-26 — Updated to v0.40.5<br>
 1. Fixed a bug where connections would intermittently drop in proxy mode<br>
 2. Enhanced stability and improved performance<br>
 3. Added auto-start scripts. Usage:<br>
 * Windows
 ```
 On Windows, ensure enable_autostart.bat and enable_autostart.ps1 are in the same directory as the server executable.
 Open a cmd window and run:
 enable_autostart.bat on    → enable auto-start
 enable_autostart.bat off   → disable auto-start
 The script requires administrator privileges.
 ```
 * Linux/macOS
 ```
 Ensure enable_autostart.sh is in the same directory as the server executable.
 enable_autostart.sh on     → enable auto-start
 enable_autostart.sh off    → disable auto-start
 ```
 4. Version updated to v0.40.5<br>
 ### 2025-03-25<br>
 1. File management now supports deleting empty directories<br>
 2. Server-to-server connections now connect on demand (retry once within 20 seconds)<br>
 3. Enhanced stability — fixed unexpected exit issues<br>
 ### 2024-10-12 — Updated to v0.40.4:<br>
 1. Added PROXY protocol — single port supports both SOCKS5 and HTTP proxy<br>
 2. Added HTTP proxy username/password authentication<br>
 ```
 <app-parameter>
    ...
    <httpx-user value="user" />
    <httpx-passwd value="pwd" />
    <socks-user value="user" />
    <socks-passwd value="pwd" />
    ...
 </app-parameter>
 ```
 3. Other optimizations<br>
 ### 2024-08-20<br>
 1. Improved file transfer speed<br>
 2. Other optimizations<br>
 ### 2024-08-17<br>
 1. Fixed a bug where the server would be lost for extended periods when the network egress changed<br>
 2. Improved P2P connection mechanism — increased P2P connection success rate<br>
 ### 2024-08-06 — Updated to v0.40.3<br>
 1. Fixed an intermittent proxy connection drop bug on Windows<br>
 2. Fixed a high CPU usage bug on Windows under low bandwidth<br>
 3. Server now supports dynamic resource reclamation — suitable for memory-constrained devices<br>
 4. Added build package supporting LoongArch64 architecture<br>
 5. Version updated to v0.40.3<br>
 ### 2024-07-11<br>
 1. Fixed a bug where the proxy address was incorrectly displayed as localhost<br>
 2. Fixed an intermittent coredump bug on Windows<br>
 ### 2024-05-11<br>
 1. Enabled asynchronous connections to prevent slow connections from blocking normal connections<br>
 2. Fixed a bug where chained proxy, SOCKS5, and HTTP proxy connections could not be released under certain conditions<br>
 ### 2024-04-27 — Updated to v0.40.2:<br>
 1. Improved P2P connection success rate<br>
 2. Fixed some known bugs<br>
 3. Version updated to v0.40.2<br>
 ### 2024-04-18:<br>
 1. Fixed favorites bug<br>
 2. Added service memo/note feature for easier service identification and tagging<br>
 ### 2024-04-10:<br>
 1. VIP users now support Baidu Maps location tracking<br>
 * App server supports GPS positioning
 * Register on Baidu Maps Open Platform, apply for a "Browser" AK, then configure the AK in the SG client to use the map positioning feature
 2. Version updated to v0.40.1<br>
 ### 2024-02-02:<br>
 1. App usability update — future versions will adopt an entirely new interface<br>
 2. Fixed a bug where IPv6 tunnels could not be created under certain conditions<br>
 3. App now includes a Favorites feature for a clear overview of frequently used connections<br>
 4. Version updated to v0.32.3<br>
 ### 2023-11-28:<br>
-1. Safety protection for the elderly and children, supports GPS positioning for easy tracking of the latitude and longitude of the care recipient (manual authorization required).<br>
+1. Safety protection for children and elderly — GPS positioning support to track the location of care recipients (manual authorization required)<br>
-   * This feature is only supported on the Android server.<br>
+* This feature only supports Android server<br>
-   * If the coordinates are successfully obtained, the latitude and longitude will be automatically copied to the clipboard.<br>
+* Once coordinates are successfully obtained, latitude and longitude are automatically copied to the clipboard<br>
 2. Other optimizations<br>
-### Update to v0.32.2 on 2023-11-17:<br>
+### 2023-11-17 — Updated to v0.32.2:<br>
-1. Support for username/password authentication in the SOCKS protocol.<br>
+1. SOCKS protocol now supports username/password authentication<br>
-2. Support for saving and playing recordings (VIP).<br>
+2. Audio recording save and playback support (VIP)<br>
-3. Version updated to v0.32.2.<br>
+3. Version updated to v0.32.2<br>
-### Update to v0.32.1 on 2023-10-25:<br>
+### 2023-10-25 — Updated to v0.32.1:<br>
 1. Bug fixes<br>
-2. Improved support for SOCKS protocol (IPv4 TCP only).<br>
+2. Improved SOCKS protocol support (IPv4 TCP only)<br>
-3. Improved support for HTTP proxy protocol.<br>
+3. Improved HTTP proxy protocol support<br>
-4. App supports VIP function license.<br>
+4. App now supports VIP feature licensing<br>
-5. Version updated to v0.32.1.<br>
+5. Version updated to v0.32.1<br>
-### Update to v0.31.12 on 2023-09-08:<br>
+### 2023-09-08 — Updated to v0.31.12:<br>
 1. Bug fixes<br>
-2. Experimental support for SOCKS protocol (IPv4 TCP only).<br>
+2. Experimental SOCKS protocol support (IPv4 TCP only)<br>
-3. Added built-in support for HTTP proxy protocol.<br>
+3. Added built-in HTTP proxy protocol support<br>
-4. Memory recycling (for devices with memory limitations).<br>
+4. Memory reclamation (suitable for memory-constrained devices)<br>
-5. Improved response speed with full asynchronous mode.<br>
+5. Fully asynchronous approach for improved responsiveness<br>
-6. Version updated to v0.31.12.<br>
+6. Version updated to v0.31.12<br>
-### Update to v0.31.11 on 2023-08-29:<br>
+### 2023-08-29 — Updated to v0.31.11:<br>
-1. File management supports default sorting by time.<br>
+1. File management now supports default sorting by time<br>
-2. Added support for macOS M1/M2.<br>
+2. Added macOS M1/M2 support<br>
-3. Version updated to v0.31.11.<br>
+3. Version updated to v0.31.11<br>
-### Update to v0.31.10 on 2023-06-03:<br>
+### 2023-06-03 — Updated to v0.31.10:<br>
-1. Network reliability optimization.<br>
+1. Network reliability optimization<br>
-2. Improved network transmission efficiency.<br>
+2. Optimized network transmission efficiency<br>
-3. Version updated to v0.31.10.<br>
+3. Version updated to v0.31.10<br>
-### Update to v0.31.9 on 2023-03-04:<br>
+### 2023-03-04 — Updated to v0.31.9:<br>
-1. App server mode adds "Accessibility" service, user manually opens it for automatic restart.<br>
+1. App server mode now includes an "Accessibility" service — users can enable it to achieve automatic restart<br>
-2. App-side operation optimization: Added automatic fill-in feature for click operations, making it easier to add configurations.<br>
+2. App operation optimization: added auto-fill on click for easier configuration of new entries<br>
-3. Fixed the BUG that custom proxy installation on MIPS routers could not provide services.<br>
+3. Fixed a bug where custom proxy services could not be provided when installed on MIPS routers<br>
-4. Provided server-side custom proxy domain timed IP refresh function (dynamic domain).<br>
+4. Added periodic IP refresh for custom proxy domain names on the server side (dynamic DNS)<br>
-5. Other optimizations.<br>
+5. Other optimizations<br>
-### Update to v0.31.8 on 2022-12-14:<br>
+### 2022-12-14 — Updated to v0.31.8:<br>
-1. App server mode supports configuring custom proxies and SSL encryption.<br>
+1. App server mode now supports custom proxy configuration and SSL encryption<br>
-2. Custom proxy server supports SSL self-signed certificate distribution.<br>
+2. Custom proxy server supports SSL self-signed certificate distribution<br>
-3. Other optimizations.<br>
+3. Other optimizations<br>
-### Update to v0.31.7 on 2022-11-04:<br>
+### 2022-11-04 — Updated to v0.31.7:<br>
-1. Provided one-click version upgrade function, no manual update required.<br>
+1. Added one-click version upgrade — no manual update required<br>
-   * This feature's version source points to GitHub. If unable to update, please confirm GitHub connectivity.<br>
+* This feature sources versions from GitHub; if updates fail, check GitHub connectivity<br>
-   * Generally, usability is restored in about 10-20 seconds after the update.<br>
+* Service typically restores within 10-20 seconds after updating<br>
-   * The server provides an automatic update option (checks once a day), which is off by default.<br>
+* Server provides an auto-update option (checks once daily), disabled by default<br>
-   ```xml
+```
-   <auto-update value="true" />
+<auto-update value="true" />
-   ```
+```
 ### Update to v0.31.6 on 2022-10-20:<br>
 1. File management adds file deletion functionality.<br>
 2. File management adds breakpoint resume functionality.<br>
 3. File management adds file timestamp.<br>
 4. File management on Windows adds disk switching operation.<br>
   * This feature is only activated when there is P2P or custom proxy connection.<br>
   * Upload and download through drag-and-drop mode.<br>
   * Confirmation box for file deletion pops up with a double click.<br>
-### Update to v0.31.5 on 2022-10-14:<br>
+### 2022-10-20 — Updated to v0.31.6:<br>
-1. Fixed the bug where custom proxy couldn't connect under short interval reconnection.<br>
+1. File management now supports file deletion<br>
-2. Added simple file upload and download functionality for easy synchronization of documents in different locations.<br>
+2. File management now supports resumable transfer (breakpoint resume)<br>
-   * This feature is only activated when there is P2P or custom proxy connection.<br>
+3. File management now displays file timestamps<br>
-   * Upload and download through drag-and-drop mode.<br>
+4. File management now supports disk switching on Windows<br>
-3. Version updated to v0.31.5.<br>
+* This feature activates only when P2P or custom proxy connections are available<br>
 * Upload and download via drag-and-drop<br>
 * Double-click to open the file deletion confirmation dialog<br>
-### Update on 2022-09-05:<br>
+### 2022-10-14 — Updated to v0.31.5:<br>
-1. Resolved the bug of abnormal disconnection in custom proxy connection.<br>
+1. Fixed a bug where custom proxy connections would fail after short-interval reconnection attempts<br>
-2. Version remains unchanged.<br>
+2. Added basic file upload/download functionality for convenient cross-location document synchronization<br>
 * This feature activates only when P2P or custom proxy connections are available<br>
 * Upload and download via drag-and-drop<br>
-### Update to v0.31.4 on 2022-08-30:<br>
+3. Version updated to v0.31.5<br>
 1. Reduced virtual memory usage during runtime.<br>
 2. Routine optimizations.<br>
 3. Version updated to v0.31.4.<br>
-### Update to v0.31.3 on 2022-08-14:<br>
+### 2022-09-05:<br>
-1. Fixed the bug where MIPS architecture systems couldn't connect to custom proxies.<br>
+1. Fixed a bug where custom proxy connections would disconnect abnormally<br>
-2. Fixed the issue of long loading time for HTTP protocol.<br>
+2. Version unchanged<br>
 3. Version updated to v0.31.3.<br>
-### Update to v0.31.2 on 2022-08-06:<br>
+### 2022-08-30 — Updated to v0.31.4:<br>
-1. Fixed occasional crashes on the Windows platform, enhanced stability.<br>
+1. Reduced runtime virtual memory usage<br>
-2. Keep-alive operations for P2P connection and custom proxy to minimize reconnection time window, improving availability.<br>
+2. Routine optimizations<br>
-3. Other usability optimizations, reduced app consumption.<br>
+3. Version updated to v0.31.4<br>
 4. Version updated to v0.31.2.<br>
-### Update to v0.31.1 on 2022-07-28:<br>
+### 2022-08-14 — Updated to v0.31.3:<br>
-1. Fixed the bug where, under specific circumstances, network configurations did not take effect when the server restarted.<br>
+1. Fixed a bug where MIPS architecture systems could not connect to custom proxies<br>
-2. Fixed NAT1 server P2P negotiation bug.<br>
+2. Fixed an issue with long HTTP protocol loading times<br>
-3. Version updated to v0.31.1.<br>
+3. Version updated to v0.31.3<br>
-### Update to v0.31 on 2022-07-22:<br>
+### 2022-08-06 — Updated to v0.31.2:<br>
-1. Provided port mapping between servers, allowing direct access from the public network if the server has a public IP (only needs to be configured on the app).
+1. Fixed an intermittent crash bug on Windows — enhanced stability<br>
-   * Configuration: In the original mapping configuration, "Remote IP" supports configuration in the form of ip@idx (idx is the sequence number of different "access points").
+2. Added keep-alive for P2P and custom proxy connections to minimize reconnection time windows and improve availability<br>
-   * The "Local Port" configured in this way is actually on the host where the current "access point" is located (Note: not on the phone where the app is located).
+3. Other usability optimizations — reduced app power consumption<br>
-   * If P2P between servers is successful (or custom proxy connection is successful), the configured mapping will take effect, otherwise, it will not.
+4. Version updated to v0.31.2<br>
   * On the app, the proxy status between servers is refreshed only when there is a P2P connection.
   * After successful configuration, it takes about 10 seconds to see the actual status on the app.
 2. Version upgraded to v0.31.<br>
-### Update on 2022-06-30:<br>
+### 2022-07-28 — Updated to v0.31.1:<br>
-1. Fixed the bug where the server could not proxy normally on 32-bit big-endian machines.<br>
+1. Fixed a bug where server restarts under certain conditions caused mesh network configuration to become ineffective<br>
-2. Version remains unchanged.<br>
+2. Fixed a P2P negotiation bug for NAT1 servers<br>
 3. Version updated to v0.31.1<br>
-### Update on 2022-05-17:<br>
+### 2022-07-22 — Updated to v0.31:<br>
-1. Server supports automatically generating self-signed certificates (default file name is server.xxx).
+1. Added server-to-server port mapping — servers with public IPs can be directly accessed from the public internet (configuration via app only)
-   * Configuration: ssl-create-certfile option<br>
+* Configuration: In the existing mapping "Remote IP" field, use the format ip@idx (where idx is the access point index)
-     ```
+* The "local port" configured this way is actually on the host of the current access point (note: NOT on the app phone)
-     <app-parameter>	
+* The mapping takes effect only if P2P (or custom proxy) between the servers succeeds
-       <ssl-create-certfile value="true" />
+* Server-to-server proxy status is refreshed on the app only during P2P connections
-     ...
+* After configuration, wait about 10 seconds for the actual status to appear on the app
     </app-parameter>
     ```
   * Make sure to install openssl.
   * Do not specify certificate files (do not configure ssl-cacert-file and ssl-privatekey-file).
 ### Update on 2022-05-04:<br>
 1. Support for riscv32/64 architecture, linked with musl library during compilation like mips architecture.<br>
 2. Optimized network transmission layer.<br>
 3. Version remains unchanged.<br>
-### Update to v0.30.4 on 2022-02-07: <br>
+2. Version updated to v0.31<br>
 1. Provided support for mips64el.<br>
 2. Added system icon display on the app.<br>
 3. Other optimizations.<br>
-### Update to v0.30.3 on 2021-11-06: <br>
+### 2022-06-30:<br>
-1. Fixed the bug where app-side memory usage only displayed JVM without native.<br>
+1. Fixed a bug where 32-bit big-endian machines could not proxy correctly when running the server<br>
-2. Optimized network engine, improving stability and fairness under high concurrency.<br>
+2. Version unchanged<br>
-### Update to v0.30.2 on 2021-10-17: <br>
+### 2022-05-17:<br>
-1. Custom proxy supports SSL verification.<br>
+1. Server now supports auto-generation of self-signed certificates (default filename: server.xxx)<br>
-2. In the case of P2P network, supports configuring SSL tunnel ( **requires server-side certificate configuration** )<br>
+  a. Configure the ssl-create-certfile option<br>
 ```
 <app-parameter>
-     <ssl-tunnel-required value="first" /><!-- Options: none, first, only -->
+  <ssl-create-certfile value="true" />
-     ...
+...
-   </app-parameter>
+</app-parameter>
-   ```
+```
-3. Other optimizations.<br>
+  b. Ensure openssl is installed<br>
-  
+  c. Do not specify certificate files (do not configure ssl-cacert-file or ssl-privatekey-file)<br>
 ### Update to v0.30 on 2021-09-24: <br>
 1. Provided Android server-side automatic startup support (only in server mode, and manual authorization is required).<br>
 2. In the case of P2P network, Android server-side supports real-time audio (microphone permission needs manual authorization, must open the SG interface to record).<br>
 3. Other optimizations.<br>
-### Update to v0.29.2 on 2021-05-03: <br>
+### 2022-05-04:<br>
-1. Fixed the issue of not being able to exit on high versions of Android.<br>
+1. Added RISC-V 32/64 architecture support — compiled with musl library (same as MIPS architecture)<br>
-2. Optimized network: Fixed a BUG that may cause network latency, further improving network transmission speed.<br>
+2. Optimized network transport layer<br>
-3. Provided version number display for easier client and server version management.<br>
+3. Version unchanged<br>
 4. Optimized app CPU usage, reduced power consumption.<br>
-### Update to v0.29 on 2021-03-05: <br>
+### 2022-02-07 — Updated to v0.30.4:<br>
-1. Fixed the issue of server-side core dump when switching between IPv6 and IPv4 networks.<br>
+1. Added MIPS64el support<br>
-2. Added IPv4-only network mode option on the client side, for scenarios where IPv6 is present but IPv4 is needed for P2P connections due to special requirements (forces the use of IPv4 for network penetration).<br>
+2. Added system icon display on the app side<br>
-3. Some other bug fixes.<br>
+3. Other optimizations<br>
   Note: Due to fatal issues with core dump in specific scenarios, both the client and server need to be updated to version 0.29.
-### Update to v0.28 on 2020-12-13: <br>
+### 2021-11-06 — Updated to v0.30.3:<br>
-1. Custom proxy added token support to prevent unauthorized access. Also supports configuring an access permission list (access-token can only input numbers, access-restricting can input allowed SIDs, multiple SIDs separated by ":"; access-restricting can be left unconfigured).<br>
+1. Fixed a bug where the app's memory usage display only showed JVM memory, excluding native memory<br>
-   A. Proxy server configuration:
+2. Optimized the network engine — improved stability and fairness under high concurrency<br>
-   ```
+
-   <app-parameter>
+### 2021-10-17 — Updated to v0.30.2:<br>
-    <proxy-service-port value="9001"/>
+1. Custom proxy now supports SSL verification<br>
-    <access-token value="nnnnn"/>
+2. P2P connections can now be configured as SSL tunnels ( **server must have certificates configured** )<br>
-    <access-restricting value="xxxxx"/>
+```
-    …
+<app-parameter>
-   </app-parameter>
+  <ssl-tunnel-required value="first" /><!-- 3 values: none, first, only -->
-   ```
+  ...
-  B、Server-side configuration (token must match the proxy server):
+</app-parameter>
 ```
 3. Other optimizations<br>
 ### 2021-09-24 — Updated to v0.30:<br>
 1. Added Android server auto-start on boot support (server mode only, requires manual authorization)<br>
 2. Android server in P2P mode now supports real-time audio (microphone permission requires manual authorization; the SG app must be open to record)<br>
 3. Other optimizations<br>
 ### 2021-05-03 — Updated to v0.29.2:<br>
 1. Fixed an issue where the app could not exit on newer Android versions<br>
 2. Network optimization: fixed a bug that could cause network latency, further improved network transfer speed<br>
 3. Added version number display for easier client and server version management<br>
 4. Optimized app CPU usage — reduced power consumption<br>
 ### 2021-03-05 — Updated to v0.29:<br>
 1. Fixed a server core dump issue when switching between IPv6 and IPv4 networks<br>
 2. Client now includes an "IPv4-only" network mode option — for scenarios where IPv4 P2P connection is required in an IPv6 network environment (forces P2P via IPv4)<br>
 3. Other bug fixes<br>
 Note: Due to a critical core dump issue in certain scenarios, v0.29 requires simultaneous update of both client and server.
 ### 2020-12-13 — Updated to v0.28:<br>
 1. Custom proxy now supports token-based access control to prevent unauthorized access. Also supports access restriction list configuration (access-token must be numeric; access-restricting accepts allowed SIDs, multiple SIDs separated by ":"; access-restricting is optional).<br>
 A. Proxy server configuration:
 ```
 <app-parameter>
  <proxy-service-port value="9001"/>
  <access-token value="nnnnn"/>
  <access-restricting value="xxxxx"/>
  ...
 </app-parameter>
 ```
 B. Server configuration (token must match the proxy server):
 ```
 <channel address="x.x.x.x:9001" ssl="true" token="nnnnn" />
 ```
-2.Optimized the tunnel timeout disconnect mechanism (only for P2P tunnels and user agent tunnels): As long as there is a connection and the connection is normal, the client will randomly delay sending heartbeats to prevent timeout disconnections.<br>
+2. Optimized tunnel timeout disconnect mechanism (P2P tunnels and user proxy tunnels only): When connections are active and in normal condition, the client sends heartbeats at random intervals to prevent timeout disconnection.<br>
-Scenario: When accessing SSH, if there is no input for a long time, it will maintain a heartbeat to prevent disconnection after 1 or 2 minutes of inactivity.<br>
+ Scenario: During SSH sessions, the connection stays alive even with extended periods of inactivity — no more disconnection after 1-2 minutes of idling.
 ### Update to v0.27 on 2020-05-23: <br>
 1. Removed the root permission acquisition feature to maintain the minimum permission requirement. Currently not developing support for configuring ports below 1024.<br>
 2. Due to personal Raspberry Pi being damaged by a child, making use of the remaining value of old smartphones, Android app added "Server Mode" support, enabling it to be used as a server at home.<br>
-### Update to v0.26 on 2020-04-30: <br>
+### 2020-05-23 — Updated to v0.27:<br>
-1. Fixed the issue where configured HTTP services might be unavailable when IP is switched.<br>
+1. Removed root permission acquisition — maintaining minimal permission requirements. Support for configuring ports below 1024 is currently not planned.<br>
-~~2. For rooted phones, attempted to acquire root permissions, supporting the configuration of reserved ports below 1024.~~ (This feature has been removed.)<br>
+2. Since my personal Raspberry Pi was broken by my child, I had to maximize the remaining value of old phones — Android app now supports "Server Mode", allowing old phones to serve as home servers.<br>
-3. Solved the problem of absolute path execution (mostly for startup scripts) and not specifying the -f parameter causing the inability to locate the default configuration file.<br>
+
-4. Server-side added HTTP-based content replacement option (affects efficiency, ignores compressed data). For some non-standard intranet web applications that return IP ports in JavaScript to the browser, content filtering is not applied by default.<br>
+### 2020-04-30 — Updated to v0.26:<br>
 1. Fixed an issue where configured HTTP services might become unavailable when the IP changed<br>
 ~~2. For rooted phones, attempted to acquire root privileges to support configuring reserved ports below 1024~~<br>
 3. Fixed an issue where absolute path execution (common in startup scripts) without the -f parameter could not locate the default configuration file<br>
 4. Server now includes an HTTP content replacement option (affects efficiency, ignores compressed data. For non-standard intranet web applications that embed IP:port in JS and return it to the browser). Default: no content filtering.<br>
 ```
-	……
+    ...
-	<moudle-parameter>
+    <moudle-parameter>
-		<http-content-type-filter value="application/javascript" />
+        <http-content-type-filter value="application/javascript" />
-		……
+        ...
-	<moudle-parameter/>
+    <moudle-parameter/>
-	……
+    ...
 ```
-5. Server-side added an option to specify the P2P negotiation port, with the default being a random port.<br>
+5. Server now includes a designated P2P negotiation port option — default is random port<br>
 ```
-	……
+    ...
-	<moudle-parameter>
+    <moudle-parameter>
-		<negotiation-port value="xxxxx" />
+        <negotiation-port value="xxxxx" />
-		……
+        ...
-	<moudle-parameter/>
+    <moudle-parameter/>
-	……
+    ...
 ```
 6. Added an "Official Proxy" toggle — enabled by default. When disabled, data will never be forwarded through the official proxy.<br>
-6. Added an "Official Proxy" switch, defaulting to open. When closed, data will not be forwarded through the official proxy under any circumstances.<br>
+### 2020-03-13:<br>
-### 2020-03-13：<br>
+1. Fixed a TCP-CORK bug where writable-event loss caused network latency under certain conditions<br>
-1. Fixed a bug causing network latency due to the loss of writable-event under specific conditions with tcp-cork.<br>
+2. Improved memory pool runtime performance<br>
-2. Improved the performance of the memory pool.<br>
+3. Added -f command line parameter to specify the full path of the configuration file<br>
-3. Added the `-f` command line parameter to specify the full path of the configuration file.<br>
+4. Other optimizations — version unchanged<br>
 4. Other optimizations, version remains unchanged.<br>
-### 2020-01-18 updated to v0.25：<br>
+### 2020-01-18 — Updated to v0.25:<br>
-1. Fixed the issue of HTTP proxy failure.<br>
+1. Fixed an HTTP proxy failure bug<br>
-2. The app now provides IPv6 address display.<br>
+2. App now displays IPv6 addresses<br>
-3. Version updated to 0.25.<br>
+3. Version updated to v0.25<br>
-### 2019-11-30 updated to v0.24：<br>
+### 2019-11-30 — Updated to v0.24:<br>
-1. Peanut shell supports UDP now? Okay, support UDP port forwarding, friends who stream games can give it a try.<br>
+1. PeanutShell now supports UDP? Alright then — UDP port forwarding is now supported. Game streaming users can give it a try.<br>
-2. Support UDP over TCP mode.<br>
+2. UDP over TCP mode supported<br>
-3. Other minor optimizations.<br>
+3. Other minor optimizations<br>
-### 2019-11-03：<br>
+### 2019-11-03:<br>
-1. Fixed memory leak bug.<br>
+1. Fixed a memory leak bug<br>
-2. Other minor optimizations, version remains unchanged.<br>
+2. Other minor optimizations — version unchanged<br>
-3. Improved P2P reconnection reliability.<br>
+3. Improved P2P reconnection reliability<br>
-### 2019-09-30 updated to v0.23：<br>
+### 2019-09-30 — Updated to v0.23:<br>
-1. Fixed high CPU usage bug under weak network conditions on Windows server.<br>
+1. Fixed a high CPU usage bug on the Windows server under weak network conditions<br>
-2. Overall improved network transmission speed.<br>
+2. Overall network transfer speed improvement<br>
-### 2019-09-20 updated to v0.22：<br>
+### 2019-09-20 — Updated to v0.22:<br>
-1. Improved P2P detection reliability.<br>
+1. Improved P2P detection reliability<br>
-2. Fixed a bug on Windows that prevented P2P connection under certain conditions.<br>
+2. Fixed a Windows bug where P2P connections could not be established under certain conditions<br>
-3. The client now provides manual P2P reconnection feature (automatic reconnection may fail under weak network conditions, in such cases, manual reconnection can be used).<br>
+3. Client now provides manual P2P reconnection (automatic reconnection may fail in weak network conditions; manual retry is available)
-### 2019-09-15：<br>
+### 2019-09-15:<br>
-1. Further reduced server CPU usage under low-speed conditions.<br>
+1. Further reduced server CPU usage at low transfer rates<br>
-2. General optimizations, version remains unchanged.<br>
+2. Routine optimization — version unchanged<br>
-### 2019-09-10 updated to v0.21：<br>
+### 2019-09-10 — Updated to v0.21:<br>
-1. Network performance optimization.<br>
+1. Network performance optimization<br>
-2. The client now supports displaying real-time network speed.<br>
+2. Client now displays real-time network speed<br>
-### 2019-09-05：<br>
+### 2019-09-05:<br>
-1. Fixed the bug of automatic login failure after changing the password on the client.<br>
+1. Fixed a bug where auto-login would fail after changing the password on the client<br>
-2. Provided automatic login timeout control.<br>
+2. Added auto-login timeout control<br>
-### 2019-09-01 updated to v0.20：<br>
+### 2019-09-01 — Updated to v0.20:<br>
-1. Optimized connection checking performance (provided parallel asynchronous detection).<br>
+1. Optimized connection check performance (parallel asynchronous detection)<br>
-2. Supports proxying HTTPS to HTTP (client-side HTTP access, server-side HTTPS).<br>
+2. HTTPS-to-HTTP proxying support (client accesses via HTTP, server connects via HTTPS)<br>
-### 2019-08-18 updated to v0.19：<br>
+### 2019-08-18 — Updated to v0.19:<br>
-1. Performance optimization.<br>
+1. Performance optimization<br>
-2. Fixed a bug where server connections could not be reliably disconnected under certain conditions (custom routing).<br>
+2. Fixed a bug where server connections could not be reliably disconnected under certain conditions (custom routes)<br>
-3. Static compilation, no longer dependent on the gcc dynamic library of the inux system, can run directly in alpine (requires creating a symbolic link).<br>
+3. Static compilation — no longer depends on Linux system GCC dynamic libraries; can run directly on Alpine (requires symlink creation)<br>
-4. Supports compiling as a mini version, no longer statically compiling OpenSSL; fully compatible with OpenSSL library from 0.9.8 to 1.1.1, binary package reduced to about 1M (already placed in the dynamic directory, SSL library needs to be configured).<br>
+4. Added mini version build support — no longer statically compiles OpenSSL; dynamically compatible with OpenSSL library versions from 0.9.8 to 1.1.1. Binary package reduced to ~1MB (placed in the dynamic directory; requires SSL library configuration).<br>
-### 2019-05-27 updated to v0.18：<br>
+### 2019-05-27 — Updated to v0.18:<br>
-1. Performance optimization.<br>
+1. Performance optimization<br>
-2. Provided IPv6 P2P switch mechanism: `<ipv4-tunnel-first value="false"/>` Set to "true" to close IPv6 P2P, the default value is "false".<br>
+2. Added IPv6 P2P toggle mechanism: `<ipv4-tunnel-first value="false"/>` — set to "true" to disable IPv6 P2P. Default is "false"<br>
-3. Added client IPv6 flag and connection status display.<br>
+3. Added IPv6 indicator and connection status prompts on the client<br>
-### 2019-05-21：<br>
+### 2019-05-21:<br>
-1. Fixed the bug that IPv6 could not be detected under Raspbian jessie.<br>
+1. Fixed a bug where IPv6 could not be detected on Raspbian Jessie<br>
-### 2019-05-16 updated to v0.17：<br>
+### 2019-05-16 — Updated to v0.17:<br>
-1. Performance optimization.<br>
+1. Performance optimization<br>
-2. Provided P2P disconnect and reconnect mechanism.<br>
+2. Added P2P disconnection and reconnection mechanism<br>
-### 2019-05-04：<br>
+### 2019-05-04:<br>
-1. Fixed a bug where the server occasionally had high CPU usage when mounting private routes with a thread count < 4, version remains unchanged.<br>
+1. Fixed an intermittent high CPU usage bug on the server when running with fewer than 4 threads and a private route was mounted — version unchanged<br>
-### 2019-04-23 updated to v0.16：<br>
+### 2019-04-23 — Updated to v0.16:<br>
-1. Fixed a bug where the server occasionally core dumped when mounting private routes.<br>
+1. Fixed an intermittent core dump bug on the server when a private route was mounted<br>
-### 2019-04-16 updated to v0.15：<br>
+### 2019-04-16 — Updated to v0.15:<br>
-1. Fixed the bug of IPV4/IPV6 network switching, unable to P2P.<br>
+1. Fixed a bug where P2P would fail when switching between IPv4 and IPv6 networks<br>
-### 2019-04-15 updated to v0.14：<br>
+### 2019-04-15 — Updated to v0.14:<br>
-1. Fixed the issue of network switching reconnection failure.<br>
+1. Fixed network switch reconnection failures<br>
-2. Engine performance optimization.<br>
+2. Engine performance optimization<br>
-3. Added support for IPv6 firewall penetration (mobile end supports IPv6, and the internal network server supports IPv6).<br>
+3. Added IPv6 firewall traversal support (requires IPv6 support on the mobile device and the intranet server)<br>
-   [Important Note] Version 0.14 is incompatible with previous versions, be sure to update!<br>
+**[Important Notice]** v0.14 is incompatible with previous versions. Please update all components!<br>
 ### ....Initial version v0.13<br>
 ### .... Initial version v0.13<br>
 </details>
@@ -42,7 +42,7 @@ var g_languages = [
    ,"等待事件"//40
    ,"检测线程"//41
    ,"服务集合"//42
-    ,"本地端口"//43
+    ,"本地绑定"//43
    ,"路由指向"//44
    ,"协议"//45
    ,"远程IP"//46
@@ -132,7 +132,7 @@ var g_languages = [
    ,"已成功获取定位信息" //130
    ,"请输入账号"//131
    ,"请输入密码"//132
-    ,"账号最短为 5 个字符"//133
+    ,"账号最短为 3 个字符"//133
    ,"密码长度至少为 6 个字符"//134
    ,"邀请码必须输入数字，且不为0"//135
    ,"邮箱地址格式错误"//136
@@ -187,6 +187,22 @@ var g_languages = [
    ,"描述"//185
    ,"备注设置"//186
    ,"请输入服务简短备注"//187
    ,"设置[电池优化]"//188
    ,"设置后台[无限制]"//189
    ,"关闭应用速冻"//190
    ,"允许后台高耗电"//191
    ,"前往[电池优化]-[应用名称]，设置[不允许]"//192
    ,"设置MIUI系统后台配置为[无限制]"//193
    ,"前往[电池]-[应用名称]，关闭[后台冻结]和[检测到异常时自动优化]"//194
    ,"前往[电池]-[后台耗电管理]-[应用名称]，设置[允许后台高耗电]"//195
    ,"跳转设置失败"//196
    ,"未知机型，请自行设置后台运行权限"//197
    ,"展开"//198
    ,"收起"//199
    ,"浅色"//200
    ,"深色"//201
    ,"跟随系统"//202
    ,"主题模式"//203
    ],
    ["English"
    , "OK" //1
@@ -231,7 +247,7 @@ var g_languages = [
    , "Pending" //40
    , "Products" //41
    , "Services" //42
-    , "Local port" //43
+    , "Local bind" //43
    , "Routing to" //44
    , "Protocol" //45
    , "Peer IP" //46
@@ -321,7 +337,7 @@ var g_languages = [
    , "Successfully obtained location information" //130
    , "Please enter your account"//131
    , "Please enter password"//132
-    , "The minimum account length is 5 characters"//133
+    , "The minimum account length is 3 characters"//133
    , "The password length should be at least 6 characters"//134
    , "The invitation code must be entered as a number and not 0"//135
    , "Email address format error"//136
@@ -376,5 +392,639 @@ var g_languages = [
    , "MEMO"//185
    , "Notes modify"//186
    , "Enter notes of the services"//187
    , "Settings [Battery Optimization]"//188
    , "Set up background [unlimited]"//189
    , "Close application quick freeze"//190
    , "Allow high power consumption in the background"//191
    , "Go to [Battery Optimization]-[App Name] and set [Not Allowed]"//192
    , "Set the MIUI system background configuration to [Unlimited]"//193
    , "Go to [Battery]-[App Name], turn off [Background Freeze] and [Automatic Optimization when Abnormality Detected]"//194
    , "Go to [Battery]-[Background Power Consumption Management]-[App Name] and set [Allow background high power consumption]"//195
    , "Load setting failed"//196
    , "Unknown model, please set background running permissions yourself"//197
    ,"Expand"//198
    ,"Collapse"//199
    ,"Light"//200
    ,"Dark"//201
    ,"Auto"//202
    ,"Theme"//203
    ]
    ,
    ["فارسی"
    ,"تایید"//1
    ,"لغو"//2
    ,"تازه‌سازی"//3
    ,"پاک کردن"//4
    ,"تغییر رمز"//5
    ,"ذخیره"//6
    ,"تغییر حالت"//7
    ,"حذف"//8
    ,"ورود"//9
    ,"ثبت نام"//10
    ,"بازگشت به ورود"//11
    ,"SmarGate"//12
    ,"ورود کاربر"//13
    ,"نام کاربری"//14
    ,"رمز عبور"//15
    ,"ورود خودکار"//16
    ,"ثبت نام کاربر"//17
    ,"کد دعوت"//18
    ,"تایید رمز"//19
    ,"نام"//20
    ,"شماره تماس"//21
    ,"ایمیل"//22
    ,"قوانین کاربری"//23
    ,"کد دعوت الزامی است"//24
    ,"توضیحات"//25
    ,"اطلاعات"//26
    ,"ارسال ↑"//27
    ,"دریافت ↓"//28
    ,"کل حافظه"//29
    ,"مصرفی"//30
    ,"حداکثر مصرف"//31
    ,"وضعیت"//32
    ,"آنلاین"//33
    ,"آفلاین"//34
    ,"خلاصه"//35
    ,"کارگرها"//36
    ,"آزاد"//37
    ,"حداکثر سوکت"//38
    ,"اتصالات"//39
    ,"در انتظار"//40
    ,"محصولات"//41
    ,"سرویس‌ها"//42
    ,"اتصال محلی"//43
    ,"مسیریابی به"//44
    ,"پروتکل"//45
    ,"IP همتا"//46
    ,"پورت همتا"//47
    ,"سرور"//48
    ,"پیکربندی"//49
    ,"نماینده"//50
    ,"پیکربندی نقطه دسترسی"//51
    ,"شناسه نقطه"//52
    ,"نام نقطه"//53
    ,"توضیحات نقطه"//54
    ,"پورت مذاکره"//55
    ,"عددی کمتر از 64 وارد کنید..."//56
    ,"نام گره را وارد کنید..."//57
    ,"توضیح کوتاه وارد کنید..."//58
    ,"به طور پیش‌فرض نیازی به تعیین نیست..."//59
    ,"شماره نقطه دسترسی باید وارد شود و عدد صحیح کمتر از 64 باشد"//60
    ,"تغییر رمز عبور"//61
    ,"قدیمی"//62
    ,"جدید"//63
    ,"تبریک: درخواست ثبت نام موفقیت‌آمیز بود. لطفاً شناسه سرویس خود را به خوبی نگهداری کنید"//64
    ,"ورود ناموفق. لطفاً نام کاربری و رمز عبور را بررسی کنید!"//65
    ,"در حال ورود..."//66
    ,"ثبت نام ناموفق. لطفاً اطلاعات را به درستی تکمیل کنید!"//67
    ,"تغییر رمز عبور ناموفق!!"//68
    ,"لطفاً صبر کنید..."//69
    ,"در حال ثبت نام..."//70
    ,"رمز عبور قدیمی الزامی است"//71
    ,"رمز عبور نمی‌تواند خالی باشد"//72
    ,"رمز جدید نمی‌تواند با رمز قدیمی یکسان باشد"//73
    ,"تایید رمز عبور مطابقت ندارد"//74
    ,"نام نقطه دسترسی نمی‌تواند خالی باشد و طول آن کمتر از 64 است"//75
    ,"توضیح کوتاه نقطه دسترسی نمی‌تواند خالی باشد و طول آن کمتر از 64 است"//76
    ,"کد دعوت الزامی است"//77
    ,"نام کاربری الزامی است"//78
    ,"رمز عبور باید تنظیم شود"//79
    ,"تایید رمز عبور باید تنظیم شده و با رمز عبور مطابقت داشته باشد"//80
    ,"نام مستعار الزامی است"//81
    ,"آیا واقعاً می‌خواهید پروکسی پیکربندی شده فعلی را حذف کنید؟"//82
    ,"در حال ورود خودکار، لطفاً صبر کنید..."//83
    ,"شبکه در دسترس نیست، لطفاً تنظیمات شبکه را بررسی کنید"//84
    ,"پورت"//85
    ,"حالت سرور"//86
    ,"نقطه دسترسی"//87
    ,"در انتظار تشخیص"//88
    ,"در حال تشخیص اتصال..."//89
    ,"نسخه قدیمی"//90
    ,"ورود ناموفق! کاربر وجود ندارد یا رمز عبور اشتباه است"//91
    ,"رمز عبور با موفقیت تغییر کرد! لطفاً آن را به خوبی نگهداری کنید"//92
    ,"رمز عبور با موفقیت تغییر کرد! ورود بعدی نیاز به وارد کردن رمز جدید دارد"//93
    ,"ثبت نام ناموفق! کد دعوت اشتباه است"//94
    ,"تغییر رمز عبور ناموفق. لطفاً بعداً دوباره تلاش کنید"//95
    ,"خطای پیکربندی ارسال [پورت محلی باید بیشتر از 1024 باشد]"//96
    ,"خطای پیکربندی پورت ارسال [کمتر از 65536]"//97
    ,"خطای پیکربندی پورت راه دور، محدوده [1-65535]"//98
    ,"خطای پیکربندی ارسال [تداخل پورت]"//99
    ,"خطای پیکربندی ارسال [خطای ناشناخته]"//100
    ,"پیکربندی با موفقیت تغییر کرد! در راه‌اندازی بعدی اعمال خواهد شد"//101
    ,"SmarGate در حال ارائه سرویس باقی خواهد ماند"//102
    ,"زمان شروع سرویس"//103
    ,"سرویس‌های در معرض نمایش"//104
    ,"پروکسی سرور"//105
    ,"لطفاً عملیات فایل را انتخاب کنید:"//106
    ,"آپلود"//107
    ,"دانلود"//108
    ,"مدیریت فایل"//109
    ,"نام فایل"//110
    ,"اندازه"//111
    ,"نسخه فعلی برای پشتیبانی از به‌روزرسانی خودکار بسیار پایین است، لطفاً به صورت دستی به‌روزرسانی کنید!"//112
    ,"پروکسی کاربر"//113
    ,"IP:port پروکسی کاربر..."//114
    ,"توکن دسترسی"//115
    ,"توکن سرور پروکسی..."//116
    ,"SSL برای P2P"//117
    ,"هیچ"//118
    ,"اول"//119
    ,"فقط"//120
    ,"ثبت مجوز موفقیت‌آمیز!"//121
    ,"خطای ثبت مجوز!"//122
    ,"ثبت مجوز"//123
    ,"کلید مجوز"//124
    ,"کلید مجوز باید وارد شود"//125
    ,"VIP روزهای باقی‌مانده:"//126
    ,"پخش"//127
    ,"درخواست موقعیت مکانی ارسال شد..."//128
    ,"درخواست موقعیت مکانی ناموفق بود"//129
    ,"اطلاعات موقعیت مکانی با موفقیت دریافت شد"//130
    ,"لطفاً حساب کاربری خود را وارد کنید"//131
    ,"لطفاً رمز عبور را وارد کنید"//132
    ,"حداقل طول حساب کاربری 3 کاراکتر است"//133
    ,"طول رمز عبور باید حداقل 6 کاراکتر باشد"//134
    ,"کد دعوت باید به صورت عدد وارد شود و صفر نباشد"//135
    ,"خطای فرمت آدرس ایمیل"//136
    ,"لطفاً کد دعوت را وارد کنید"//137
    ,"لطفاً رمز عبور را تایید کنید"//138
    ,"لطفاً شماره تلفن را وارد کنید"//139
    ,"لطفاً ایمیل خود را وارد کنید"//140
    ,"پس از ثبت نام موفق، لطفاً اولین ورود را ظرف 2 ساعت انجام دهید. نام کاربری و رمز عبور خود را به خوبی نگهداری کنید، داده‌های کاربری فقط به صورت محلی ذخیره می‌شوند."//141
    ,"رمز عبور دو بار وارد شده مطابقت ندارد"//142
    ,"تنظیمات"//143
    ,"کشیدن به چپ برای باز کردن تنظیمات"//144
    ,"پس از تنظیم، می‌توانید به راست بکشید تا بازگردید"//145
    ,"انتخاب زبان"//146
    ,"تنظیمات عمومی"//147
    ,"تنظیمات پیشرفته"//148
    ,"تایید عملیات"//149
    ,"آیا از حذف این رکورد مورد علاقه اطمینان دارید؟"//150
    ,"شما کاربر رایگان هستید"//151
    ,"تایید حذف رکورد پروکسی؟"//152
    ,"افزودن پیکربندی نگاشت"//153
    ,"توجه: لطفاً به دقت بررسی کنید. اگر شماره سریال اشتباه وارد کنید، باید نیم ساعت قبل از ادامه ثبت نام صبر کنید"//154
    ,"کشیدن به پایین برای تازه‌سازی"//155
    ,"رها کردن برای تازه‌سازی فوری"//156
    ,"در حال تازه‌سازی..."//157
    ,"اطلاعات"//158
    ,"خطا"//159
    ,"علاقه‌مندی‌ها"//160
    ,"ارائه علاقه‌مندی برای اتصالات پرکاربرد"//161
    ,"لطفاً عنوان نشانک را وارد کنید"//162
    ,"افزودن به علاقه‌مندی‌ها"//163
    ,"عملکرد انتقال فایل فقط زمانی قابل استفاده است که P2P یا پروکسی سفارشی فعال باشد"//164
    ,"شما در حال حاضر مجوز این ویژگی را ندارید"//165
    ,"پوشه مقصد"//166
    ,"پوشه فعلی"//167
    ,"ناحیه ماموریت"//168
    ,"برای تغییر میزبان فایل کلیک کنید"//169
    ,"عملیات تازه‌سازی نیاز به فاصله 30 ثانیه دارد"//170
    ,"عملیات ناموفق، ورودی ممکن است قبلاً اضافه شده باشد"//171
    ,"آیا به حالت سرور تغییر کند؟"//172
    ,"پس از تغییر حالت سرور/کلاینت، باید برنامه را مجدداً راه‌اندازی کنید تا اعمال شود!"//173
    ,"لطفاً نام خود را وارد کنید"//174
    ,"لطفاً پس از 30 ثانیه دوباره تلاش کنید"//175
    ,"ثبت نام کاربر جدید ناموفق!"//176
    ,"سرعت شبکه بسیار پایین است، بارگذاری داده‌ها با خطای زمان مواجه شد!"//177
    ,"تایید حذف فایل انتخاب شده؟"//178
    ,"تایید انتقال فایل انتخاب شده؟"//179
    ,"در حال بارگذاری..."//180
    ,"لطفاً کلید AK نسخه مرورگر نقشه بایدو را خودتان درخواست دهید. اگر برای اولین بار از نقشه استفاده می‌کنید، لطفاً AK را در تنظیمات وارد کنید"//181
    ,"تنظیم کد AK"//182
    ,"کد AK نقشه بایدو را وارد کنید"//183
    ,"نقشه"//184
    ,"یادداشت"//185
    ,"ویرایش یادداشت"//186
    ,"یادداشت سرویس را وارد کنید"//187
    ,"تنظیمات [بهینه‌سازی باتری]"//188
    ,"تنظیم پس‌زمینه [نامحدود]"//189
    ,"بستن انجماد سریع برنامه"//190
    ,"اجازه مصرف بالای باتری در پس‌زمینه"//191
    ,"به [بهینه‌سازی باتری]-[نام برنامه] بروید و [مجاز نیست] را تنظیم کنید"//192
    ,"پیکربندی پس‌زمینه سیستم MIUI را روی [نامحدود] تنظیم کنید"//193
    ,"به [باتری]-[نام برنامه] بروید، [انجماد پس‌زمینه] و [بهینه‌سازی خودکار هنگام تشخیص خطا] را خاموش کنید"//194
    ,"به [باتری]-[مدیریت مصرف پس‌زمینه]-[نام برنامه] بروید و [اجازه مصرف بالای باتری در پس‌زمینه] را تنظیم کنید"//195
    ,"بارگذاری تنظیمات ناموفق"//196
    ,"مدل ناشناخته، لطفاً مجوزهای اجرای پس‌زمینه را خودتان تنظیم کنید"//197
    ,"باز کردن"//198
    ,"جمع کردن"//199
    ,"روشن"//200
    ,"تاریک"//201
    ,"خودکار"//202
    ,"پوسته"//203
    ]
    ,
    ["한국어"
    ,"확인"//1
    ,"취소"//2
    ,"새로고침"//3
    ,"지우기"//4
    ,"비밀번호 변경"//5
    ,"저장"//6
    ,"모드 전환"//7
    ,"삭제"//8
    ,"로그인"//9
    ,"회원가입"//10
    ,"로그인으로 돌아가기"//11
    ,"SmarGate"//12
    ,"사용자 로그인"//13
    ,"사용자 이름"//14
    ,"비밀번호"//15
    ,"자동 로그인"//16
    ,"사용자 등록"//17
    ,"초대 코드"//18
    ,"비밀번호 확인"//19
    ,"이름"//20
    ,"전화번호"//21
    ,"이메일"//22
    ,"사용자 약관"//23
    ,"초대 코드를 입력해야 합니다"//24
    ,"설명"//25
    ,"정보"//26
    ,"전송 ↑"//27
    ,"수신 ↓"//28
    ,"전체 메모리"//29
    ,"사용량"//30
    ,"최대 사용량"//31
    ,"상태"//32
    ,"온라인"//33
    ,"오프라인"//34
    ,"요약"//35
    ,"작업자"//36
    ,"유휴"//37
    ,"최대 소켓"//38
    ,"연결"//39
    ,"대기 중"//40
    ,"제품"//41
    ,"서비스"//42
    ,"로컬 바인드"//43
    ,"라우팅 대상"//44
    ,"프로토콜"//45
    ,"피어 IP"//46
    ,"피어 포트"//47
    ,"서버"//48
    ,"구성"//49
    ,"에이전트"//50
    ,"엔드포인트 구성"//51
    ,"엔드포인트 번호"//52
    ,"엔드포인트 이름"//53
    ,"엔드포인트 설명"//54
    ,"협상 포트"//55
    ,"64 미만의 숫자 입력..."//56
    ,"노드 이름 입력..."//57
    ,"간단한 설명 입력..."//58
    ,"기본적으로 지정할 필요 없음..."//59
    ,"액세스 포인트 번호를 입력해야 하며 64 미만의 정수여야 합니다"//60
    ,"비밀번호 변경"//61
    ,"이전 비밀번호"//62
    ,"새 비밀번호"//63
    ,"축하합니다: 등록 요청이 성공했습니다. 서비스 ID를 잘 보관하세요"//64
    ,"로그인 실패. 사용자 이름과 비밀번호를 확인하세요!"//65
    ,"로그인 중..."//66
    ,"등록 실패. 정보가 올바르게 입력되었는지 확인하세요!"//67
    ,"비밀번호 변경 실패!!"//68
    ,"잠시 기다려 주세요..."//69
    ,"등록 중..."//70
    ,"이전 비밀번호를 입력해야 합니다"//71
    ,"비밀번호는 비워둘 수 없습니다"//72
    ,"새 비밀번호는 이전 비밀번호와 같을 수 없습니다"//73
    ,"비밀번호 확인이 일치하지 않습니다"//74
    ,"엔드포인트 이름은 비워둘 수 없으며 길이는 64 미만입니다"//75
    ,"엔드포인트 간단 설명은 비워둘 수 없으며 길이는 64 미만입니다"//76
    ,"초대 코드를 입력해야 합니다"//77
    ,"사용자 이름을 입력해야 합니다"//78
    ,"비밀번호를 설정해야 합니다"//79
    ,"비밀번호 확인을 설정하고 비밀번호와 일치해야 합니다"//80
    ,"닉네임을 입력해야 합니다"//81
    ,"현재 구성된 프록시를 정말 삭제하시겠습니까?"//82
    ,"자동 로그인 중입니다. 잠시 기다려 주세요..."//83
    ,"네트워크를 사용할 수 없습니다. 네트워크 설정을 확인하세요"//84
    ,"포트"//85
    ,"서버 모드"//86
    ,"엔드포인트"//87
    ,"감지 대기 중"//88
    ,"연결 감지 중..."//89
    ,"이전 버전"//90
    ,"로그인 실패! 사용자가 존재하지 않거나 비밀번호 오류"//91
    ,"비밀번호가 성공적으로 변경되었습니다! 비밀번호를 잘 보관하세요"//92
    ,"비밀번호가 성공적으로 변경되었습니다! 다음 로그인 시 새 비밀번호를 입력해야 합니다"//93
    ,"등록 실패! 초대 코드 오류"//94
    ,"비밀번호 변경 실패. 나중에 다시 시도해 주세요"//95
    ,"전달 구성 오류 [로컬 포트는 1024보다 커야 함]"//96
    ,"전달 포트 구성 오류 [65536 미만]"//97
    ,"원격 포트 구성 오류, 범위 [1-65535]"//98
    ,"전달 구성 오류 [포트 충돌]"//99
    ,"전달 구성 오류 [알 수 없는 오류]"//100
    ,"구성 수정 성공! 다음 재부팅 시 적용됩니다"//101
    ,"SmarGate가 계속 서비스를 제공합니다"//102
    ,"서비스 시작 시간"//103
    ,"노출된 서비스"//104
    ,"서버 프록시"//105
    ,"파일 작업을 선택하세요:"//106
    ,"업로드"//107
    ,"다운로드"//108
    ,"파일 관리자"//109
    ,"파일 이름"//110
    ,"크기"//111
    ,"현재 버전이 자동 업데이트를 지원하기에 너무 낮습니다. 수동으로 업데이트하세요!"//112
    ,"사용자 프록시"//113
    ,"사용자 프록시 IP:port..."//114
    ,"액세스 토큰"//115
    ,"프록시 서버 토큰..."//116
    ,"P2P용 SSL"//117
    ,"없음"//118
    ,"처음"//119
    ,"만"//120
    ,"라이선스 등록 성공!"//121
    ,"라이선스 등록 실패!"//122
    ,"라이선스 등록"//123
    ,"라이선스 키"//124
    ,"라이선스 키를 입력해야 합니다"//125
    ,"VIP 남은 일수:"//126
    ,"재생"//127
    ,"위치 요청이 전송되었습니다..."//128
    ,"위치 요청 실패"//129
    ,"위치 정보를 성공적으로 가져왔습니다"//130
    ,"계정을 입력하세요"//131
    ,"비밀번호를 입력하세요"//132
    ,"계정 최소 길이는 3자입니다"//133
    ,"비밀번호 길이는 최소 6자 이상이어야 합니다"//134
    ,"초대 코드는 숫자로 입력해야 하며 0이 아니어야 합니다"//135
    ,"이메일 주소 형식 오류"//136
    ,"초대 코드를 입력하세요"//137
    ,"비밀번호를 확인하세요"//138
    ,"전화번호를 입력하세요"//139
    ,"이메일을 입력하세요"//140
    ,"등록 성공 후 2시간 이내에 첫 로그인을 완료하세요. 사용자 이름과 비밀번호를 잘 보관하세요. 사용자 데이터는 로컬에만 저장됩니다."//141
    ,"두 번 입력한 비밀번호가 일치하지 않습니다"//142
    ,"설정"//143
    ,"왼쪽으로 밀어 설정 열기"//144
    ,"설정 후 오른쪽으로 밀어 돌아가기"//145
    ,"언어 선택"//146
    ,"일반 설정"//147
    ,"고급 설정"//148
    ,"작업 확인"//149
    ,"이 즐겨찾기 기록을 삭제하시겠습니까?"//150
    ,"무료 사용자입니다"//151
    ,"프록시 기록을 삭제하시겠습니까?"//152
    ,"매핑 구성 추가"//153
    ,"주의: 신중하게 확인하세요. 잘못된 일련번호를 입력하면 등록을 계속하기 전에 30분을 기다려야 합니다"//154
    ,"아래로 당겨 새로고침"//155
    ,"놓아서 즉시 새로고침"//156
    ,"새로고침 중..."//157
    ,"정보"//158
    ,"오류"//159
    ,"즐겨찾기"//160
    ,"자주 사용하는 연결을 즐겨찾기에 추가"//161
    ,"북마크 제목을 입력하세요"//162
    ,"즐겨찾기에 추가"//163
    ,"파일 전송 기능은 P2P 또는 사용자 정의 프록시가 활성화된 경우에만 사용할 수 있습니다"//164
    ,"현재 이 기능에 대한 권한이 없습니다"//165
    ,"대상 폴더"//166
    ,"현재 폴더"//167
    ,"작업 영역"//168
    ,"클릭하여 파일 호스트 전환"//169
    ,"새로고침 작업은 30초 간격이 필요합니다"//170
    ,"작업 실패, 항목이 이미 추가되었을 수 있습니다"//171
    ,"서버 모드로 전환하시겠습니까?"//172
    ,"서버/클라이언트 모드 전환 후 앱을 재시작해야 적용됩니다!"//173
    ,"이름을 입력하세요"//174
    ,"30초 후에 다시 시도하세요"//175
    ,"새 사용자 등록 실패!"//176
    ,"네트워크가 너무 느립니다. 데이터 로딩 시간 초과!"//177
    ,"선택한 파일을 삭제하시겠습니까?"//178
    ,"선택한 파일을 전송하시겠습니까?"//179
    ,"로딩 중..."//180
    ,"바이두 지도 브라우저 버전 AK를 직접 신청하세요. 처음 지도를 사용하는 경우 구성에서 AK를 설정하세요"//181
    ,"AK 코드 설정"//182
    ,"바이두 지도의 AK 코드 입력"//183
    ,"지도"//184
    ,"메모"//185
    ,"메모 수정"//186
    ,"서비스 메모 입력"//187
    ,"설정 [배터리 최적화]"//188
    ,"백그라운드 [무제한] 설정"//189
    ,"앱 빠른 동결 닫기"//190
    ,"백그라운드 높은 전력 소비 허용"//191
    ,"[배터리 최적화]-[앱 이름]으로 이동하여 [허용 안 함] 설정"//192
    ,"MIUI 시스템 백그라운드 구성을 [무제한]으로 설정"//193
    ,"[배터리]-[앱 이름]으로 이동하여 [백그라운드 동결] 및 [이상 감지 시 자동 최적화] 끄기"//194
    ,"[배터리]-[백그라운드 전력 관리]-[앱 이름]으로 이동하여 [백그라운드 높은 전력 소비 허용] 설정"//195
    ,"설정 로드 실패"//196
    ,"알 수 없는 모델입니다. 백그라운드 실행 권한을 직접 설정하세요"//197
    ,"펼치기"//198
    ,"접기"//199
    ,"라이트"//200
    ,"다크"//201
    ,"자동"//202
    ,"테마"//203
    ]
    ,
    ["Русский"
    ,"ОК"//1
    ,"Отмена"//2
    ,"Обновить"//3
    ,"Очистить"//4
    ,"Сменить пароль"//5
    ,"Сохранить"//6
    ,"Сменить режим"//7
    ,"Удалить"//8
    ,"Вход"//9
    ,"Регистрация"//10
    ,"Вернуться ко входу"//11
    ,"SmarGate"//12
    ,"Вход пользователя"//13
    ,"Имя пользователя"//14
    ,"Пароль"//15
    ,"Автовход"//16
    ,"Регистрация пользователя"//17
    ,"Код приглашения"//18
    ,"Подтверждение"//19
    ,"Имя"//20
    ,"Телефон"//21
    ,"Эл. почта"//22
    ,"Соглашение"//23
    ,"Необходимо ввести код приглашения"//24
    ,"Описание"//25
    ,"Информация"//26
    ,"Отправлено ↑"//27
    ,"Получено ↓"//28
    ,"Всего памяти"//29
    ,"Использовано"//30
    ,"Макс. использование"//31
    ,"Статус"//32
    ,"Онлайн"//33
    ,"Офлайн"//34
    ,"Сводка"//35
    ,"Рабочие потоки"//36
    ,"Простаивающие"//37
    ,"Макс. сокетов"//38
    ,"Подключений"//39
    ,"Ожидание"//40
    ,"Продукты"//41
    ,"Сервисы"//42
    ,"Локальный бинд"//43
    ,"Маршрут к"//44
    ,"Протокол"//45
    ,"IP узла"//46
    ,"Порт узла"//47
    ,"Сервер"//48
    ,"Настроить"//49
    ,"Агент"//50
    ,"Конфигурация точки доступа"//51
    ,"Индекс точки"//52
    ,"Имя точки"//53
    ,"Описание точки"//54
    ,"Порт согласования"//55
    ,"Введите число менее 64..."//56
    ,"Введите имя узла..."//57
    ,"Введите краткое описание..."//58
    ,"По умолчанию не требуется..."//59
    ,"Необходимо ввести номер точки доступа — целое число <64"//60
    ,"Смена пароля"//61
    ,"Старый"//62
    ,"Новый"//63
    ,"Поздравляем: запрос на регистрацию успешен. Сохраните ваш ID сервиса"//64
    ,"Ошибка входа. Проверьте имя пользователя и пароль!"//65
    ,"Вход..."//66
    ,"Ошибка регистрации. Проверьте правильность заполнения данных!"//67
    ,"Ошибка смены пароля!!"//68
    ,"Пожалуйста, подождите..."//69
    ,"Регистрация..."//70
    ,"Необходимо ввести старый пароль"//71
    ,"Пароль не может быть пустым"//72
    ,"Новый пароль не должен совпадать со старым"//73
    ,"Подтверждение пароля не совпадает"//74
    ,"Имя точки доступа не может быть пустым, длина <64"//75
    ,"Краткое описание точки не может быть пустым, длина <64"//76
    ,"Необходимо ввести код приглашения"//77
    ,"Необходимо ввести имя пользователя"//78
    ,"Необходимо задать пароль"//79
    ,"Необходимо задать подтверждение пароля, совпадающее с паролем"//80
    ,"Необходимо ввести псевдоним"//81
    ,"Вы действительно хотите удалить текущий настроенный прокси?"//82
    ,"Выполняется автоматический вход, подождите..."//83
    ,"Сеть недоступна, проверьте настройки сети"//84
    ,"Порт"//85
    ,"Режим сервера"//86
    ,"Точка доступа"//87
    ,"Ожидание обнаружения"//88
    ,"Обнаружение соединения..."//89
    ,"Старая версия"//90
    ,"Ошибка входа! Пользователь не существует или неверный пароль"//91
    ,"Пароль успешно изменён! Храните его в безопасности"//92
    ,"Пароль успешно изменён! При следующем входе потребуется новый пароль"//93
    ,"Ошибка регистрации! Неверный код приглашения"//94
    ,"Ошибка смены пароля. Попробуйте позже"//95
    ,"Ошибка конфигурации пересылки [локальный порт должен быть >1024]"//96
    ,"Ошибка конфигурации порта пересылки [менее 65536]"//97
    ,"Ошибка конфигурации удалённого порта, диапазон [1-65535]"//98
    ,"Ошибка конфигурации пересылки [конфликт портов]"//99
    ,"Ошибка конфигурации пересылки [неизвестная ошибка]"//100
    ,"Конфигурация успешно изменена! Вступит в силу при следующем перезапуске"//101
    ,"SmarGate продолжит предоставление услуг"//102
    ,"Время запуска сервиса"//103
    ,"Открытые сервисы"//104
    ,"Серверный прокси"//105
    ,"Выберите операцию с файлом:"//106
    ,"Загрузить"//107
    ,"Скачать"//108
    ,"Файловый менеджер"//109
    ,"Имя файла"//110
    ,"Размер"//111
    ,"Текущая версия слишком стара для автоматического обновления, обновите вручную!"//112
    ,"Пользовательский прокси"//113
    ,"Пользовательский прокси IP:port..."//114
    ,"Токен доступа"//115
    ,"Токен прокси-сервера..."//116
    ,"SSL для P2P"//117
    ,"нет"//118
    ,"первый"//119
    ,"только"//120
    ,"Лицензия успешно зарегистрирована!"//121
    ,"Ошибка регистрации лицензии!"//122
    ,"Регистрация лицензии"//123
    ,"Лицензионный ключ"//124
    ,"Необходимо ввести лицензионный ключ"//125
    ,"VIP осталось дней:"//126
    ,"Воспроизвести"//127
    ,"Запрос местоположения отправлен..."//128
    ,"Ошибка запроса местоположения"//129
    ,"Местоположение успешно получено"//130
    ,"Введите аккаунт"//131
    ,"Введите пароль"//132
    ,"Минимальная длина аккаунта — 3 символа"//133
    ,"Длина пароля должна быть не менее 6 символов"//134
    ,"Код приглашения должен быть числом и не равен 0"//135
    ,"Неверный формат эл. почты"//136
    ,"Введите код приглашения"//137
    ,"Подтвердите пароль"//138
    ,"Введите номер телефона"//139
    ,"Введите эл. почту"//140
    ,"После успешной регистрации выполните первый вход в течение 2 часов. Сохраните имя пользователя и пароль — данные хранятся только локально."//141
    ,"Пароли, введённые дважды, не совпадают"//142
    ,"Настройки"//143
    ,"Свайп влево, чтобы открыть настройки"//144
    ,"После настройки свайпните вправо, чтобы вернуться"//145
    ,"Выбор языка"//146
    ,"Общие настройки"//147
    ,"Расширенные настройки"//148
    ,"Подтверждение операции"//149
    ,"Вы уверены, что хотите удалить эту запись из избранного?"//150
    ,"Вы бесплатный пользователь"//151
    ,"Подтвердите удаление записи прокси?"//152
    ,"Добавить конфигурацию сопоставления"//153
    ,"Внимание: проверьте внимательно. При неверном вводе серийного номера придётся ждать полчаса для продолжения регистрации"//154
    ,"Потяните вниз для обновления"//155
    ,"Отпустите для немедленного обновления"//156
    ,"Обновление..."//157
    ,"Информация"//158
    ,"Ошибка"//159
    ,"Избранное"//160
    ,"Добавление часто используемых подключений в избранное"//161
    ,"Введите название закладки"//162
    ,"Добавить в избранное"//163
    ,"Функция передачи файлов доступна только при активном P2P или пользовательском прокси"//164
    ,"У вас нет прав на эту функцию"//165
    ,"Целевая папка"//166
    ,"Текущая папка"//167
    ,"Область задач"//168
    ,"Нажмите для переключения файлового хоста"//169
    ,"Операция обновления требует интервала в 30 секунд"//170
    ,"Операция не удалась, запись, возможно, уже добавлена"//171
    ,"Переключиться в режим сервера?"//172
    ,"После переключения режима сервер/клиент необходимо перезапустить приложение!"//173
    ,"Введите ваше имя"//174
    ,"Повторите попытку через 30 секунд"//175
    ,"Ошибка регистрации нового пользователя!"//176
    ,"Сеть слишком медленная, время загрузки данных истекло!"//177
    ,"Подтвердите удаление выбранного файла?"//178
    ,"Подтвердите передачу выбранного файла?"//179
    ,"Загрузка..."//180
    ,"Пожалуйста, самостоятельно запросите AK для браузерной версии Baidu Maps. При первом использовании карты укажите AK в настройках"//181
    ,"Настройка кода AK"//182
    ,"Введите код AK Baidu Maps"//183
    ,"Карта"//184
    ,"Памятка"//185
    ,"Изменить памятку"//186
    ,"Введите краткую заметку о сервисе"//187
    ,"Настройки [Оптимизация батареи]"//188
    ,"Установить фон [Без ограничений]"//189
    ,"Отключить быструю заморозку приложения"//190
    ,"Разрешить высокое энергопотребление в фоне"//191
    ,"Перейдите в [Оптимизация батареи]-[Имя приложения] и установите [Запрещено]"//192
    ,"Установите фоновую конфигурацию MIUI в [Без ограничений]"//193
    ,"Перейдите в [Батарея]-[Имя приложения], отключите [Фоновую заморозку] и [Автооптимизацию при обнаружении аномалий]"//194
    ,"Перейдите в [Батарея]-[Управление фоновым энергопотреблением]-[Имя приложения] и установите [Разрешить высокое фоновое энергопотребление]"//195
    ,"Ошибка загрузки настроек"//196
    ,"Неизвестная модель, настройте разрешения фонового выполнения самостоятельно"//197
    ,"Развернуть"//198
    ,"Свернуть"//199
    ,"Светлая"//200
    ,"Тёмная"//201
    ,"Авто"//202
    ,"Тема"//203
    ]
  ];
@@ -35,7 +35,22 @@
 * 需要P2P高带宽安全传输的场景
 * 有公网IP，需要将内网服务发布出去的场景
 * ......
 ## SG版本说明                                                                                                      
 Android 提供 **Base** 和 **Advance** 两个构建变体（Product Flavor），共用同一代码库，通过编译时功能开关 + R8死代码消除实现差异化：
 | 功能 | Base | Advance |
 |------|:----:|:-------:|
 | 代理隧道 | ✓ | ✓ |                                                                                               
 | 文件管理 | ✓ | ✓ |                                                                                               
 | 音频采集/传输 | ✗ | ✓ |                                                                                          
 | GPS 定位追踪 | ✗ | ✓ |                                                                                           
 | 应用升级 | ✗ | ✓ |                                                                                               
 | 屏幕/摄像头监控 | ✗ | ✗ |
 - **Base** — 轻量版。仅保留核心代理隧道和文件管理，裁剪掉音频、定位、升级、监控等高权限/高风险功能模块。APK体积更小，权限更少，适合只需基础代理和文件访问的用户。
 - **Advance** — 完整版。包含除监控外的全部功能模块，支持远程音频、位置追踪、应用升级等高级特性。适合需要完整远程管理能力的用户。
  * 完整版华为手机会被默认识别为“诈骗程序”，需首先关闭纯净模式，下载后设置手机为“飞行模式”后再安装。其它手机类似问题自行搜索解决办法。
 ## SG怎么使用？
 * 下载APP并注册
 * 下载合适的服务端版本，根据用户ID进行配置并运行
@@ -51,8 +66,8 @@
 # 
 ## 快速概览<a href=https://github.com/lazy-luo/smarGate/wiki/快速上手手册>【快速上手手册】</a> <a href="https://www.bilibili.com/video/BV1LM411k7Rf">【三方视频教学- B站】</a><br>
-* 平台适配，支持linux、windows、macos、android、（tob，小型机：hp-unix、solaris、AIX）<br>
+* 平台适配，支持linux、windows、macos、android（tob，小型机：hp-unix、solaris、AIX）<br>
-* cpu架构，支持x86、arm、mips、riscv（tob：alpha、PowerPC、SPRAC）<br>
+* cpu架构，支持x86、arm、mips、riscv、LoongArch64（tob：alpha、PowerPC、SPRAC）<br>
 * 注重安全，“内网”到“内网”的穿透，无需映射任何端口到外网，不更改任何防火墙配置<br>
 * 注重带宽，”4G手机+v6宽带“采用P2P方式访问内网服务（基于TCP协议，v4支持NAT1-3穿透）<br>
 * 注重节约，无需购买vps、无需公网IP；家中淘汰Android手机可做服务器<br>
@@ -376,6 +391,81 @@ ps：捐赠建议附上注册用户名<br>
 	<mark><font size=5 color=darkred>更新历史</font></mark>
 </summary>
 ### 2026-07-24更新到v0.41.1<br>                                                                    
 1、新增三种服务展示布局，顶部工具栏一键切换：<br>
 - **卡片模式（Card）**：经典卡片视图，服务信息一目了然                                           
 - **标签模式（Tab）**：顶部Tab栏横向滚动，按访问点分组切换，滚动位置自动记忆                     
 - **紧凑模式（Compact）**：列表式压缩展示，点击展开查看详情，适合大批量服务管理
 2、支持主题选择，布局偏好自动持久化（localStorage），下次启动恢复上次选择<br>
 3、网络引擎优化，提示性能及稳定性<br>
 4、新增”波斯语“、“韩语”、“俄罗斯语”的多语言支持<br>
 5、版本更新到v0.41.1<br>
 ### 2026-03-03更新到v0.40.6<br>
 1、解决tcp连接延迟断开的问题<br>
 2、调整网络引擎，提升性能<br>
 3、版本更新到v0.40.6<br>
 ### 2025-09-26更新到v0.40.5<br>
 1、解决代理模式下连接概率性断开的BUG<br>
 2、增强稳定性，提升性能<br>
 3、增加开机自启动脚本，使用方式如下：<br>
 * windows
 ```
 windows下，确保 enable_autostart.bat 和 enable_autostart.ps1 文件与服务端在同一个目录
 打开cmd窗口，开启自启动输入:
 enable_autostart.bat on
 关闭自启动输入:
 enable_autostart.bat off
 过程中要求脚本以管理员方式运行
 ```
 * linux/macOS
 ```
 确保 enable_autostart.sh 文件与服务端在同一个目录
 开启自启动输入:
 enable_autostart.sh on
 关闭自启动输入:
 enable_autostart.sh off
 ```
 4、版本更新到v0.40.5<br>
 ### 2025-03-25<br>
 1、文件管理新增空目录删除功能<br>
 2、服务端间连接增加使用时连接功能（20秒内重连1次）<br>
 3、增强稳定性，修复异常退出问题<br>
 ### 2024-10-12更新到v0.40.4：<br>
 1、新增PROXY协议，单端口同时支持socks5及http代理<br>
 2、新增http代理用户/密码认证<br>
 ```
 <app-parameter>
 	...
 	<httpx-user value="user" />
 	<httpx-passwd value="pwd" />
 	<socks-user value="user" />
 	<socks-passwd value="pwd" />
 	...
 </app-parameter>
 ```
 3、其它优化<br>
 ### 2024-08-20<br>
 1、提升文件传输速度<br>
 2、其它优化<br>
 ### 2024-08-17<br>
 1、修复网络出口变化时服务端长时间丢失的BUG<br>
 2、改进P2P连接机制，提升P2P连接成功率<br>
 ### 2024-08-06更新到v0.40.3<br>
 1、修复windows下代理连接偶发断开的BUG<br>
 2、修复windows下低带宽时高CPU占用的BUG<br>
 3、服务端支持动态资源回收，适合内存限制设备<br>
 4、新增编译包，支持LoongArch64架构<br>
 5、版本更新到v0.40.3<br>
 ### 2024-07-11<br>
 1、修复代理地址错误显示为localhost的BUG<br>
 2、修复windows下偶发coredump的BUG<br>
@@ -682,3 +772,6 @@ ps：捐赠建议附上注册用户名<br>
 【重要提示】v0.14版本将于之前版本不兼容，请务必更新版本！！！<br>
 ### ....初始版本v0.13<br>
 </details>
Author	SHA1	Message	Date
zhiyong.luo	783fc5ad0d	Update README_en.md	2026-07-27 21:51:29 +08:00
zhiyong.luo	3fe2b40321	Delete app-release.apk	2026-07-27 21:48:33 +08:00
zhiyong.luo	8fc050ec39	bug-fixed	2026-07-27 21:48:01 +08:00
zhiyong.luo	e57f32a8de	Update readme.md	2026-07-27 21:33:17 +08:00
zhiyong.luo	e3f789a2df	bug-fixed	2026-07-26 21:51:35 +08:00
zhiyong.luo	7ccec1919e	Update README_en.md	2026-07-24 23:03:46 +08:00
zhiyong.luo	d0603f087b	Update readme.md	2026-07-24 22:57:19 +08:00
zhiyong.luo	81b1afd0cb	Update readme.md	2026-07-24 22:55:06 +08:00
zhiyong.luo	11f6018c13	upgrade	2026-07-24 22:39:41 +08:00
zhiyong.luo	c2794c135f	bug-fixed	2026-07-24 22:38:01 +08:00
zhiyong.luo	fbef0bb707	Delete dynamic/windows_mini_x86v0.40.6.tar	2026-07-24 22:36:40 +08:00
zhiyong.luo	0c55b95f58	Delete dynamic/macos_mini_universalv0.40.6.tar	2026-07-24 22:36:25 +08:00
zhiyong.luo	65fdfccfa4	Delete dynamic/linux_mini_x86v0.40.6.tar	2026-07-24 22:36:10 +08:00
zhiyong.luo	c56533a0ca	Delete dynamic/linux_mini_x86_64v0.40.6.tar	2026-07-24 22:35:53 +08:00
zhiyong.luo	0fe98ea4bf	Delete dynamic/linux_mini_riscv64v0.40.6.tar	2026-07-24 22:35:37 +08:00
zhiyong.luo	fb2e83bd61	Delete dynamic/linux_mini_riscv32v0.40.6.tar	2026-07-24 22:35:22 +08:00
zhiyong.luo	268d694a9e	Delete dynamic/linux_mini_mipsel64v0.40.6.tar	2026-07-24 22:35:05 +08:00
zhiyong.luo	e484565643	Delete dynamic/linux_mini_mipsel32v0.40.6.tar	2026-07-24 22:34:50 +08:00
zhiyong.luo	b9ef355a72	Delete dynamic/linux_mini_mipsel32-uclibcv0.40.6.tar	2026-07-24 22:34:38 +08:00
zhiyong.luo	c8fa3d1f44	Delete dynamic/linux_mini_mips64v0.40.6.tar	2026-07-24 22:34:24 +08:00
zhiyong.luo	7d46950c28	Delete dynamic/linux_mini_mips32v0.40.6.tar	2026-07-24 22:34:12 +08:00
zhiyong.luo	ff830addbd	Delete dynamic/linux_mini_loongarch64v0.40.6.tar	2026-07-24 22:33:57 +08:00
zhiyong.luo	7fb00e0380	Delete dynamic/linux_mini_arm64v0.40.6.tar	2026-07-24 22:33:35 +08:00
zhiyong.luo	9abece0149	Delete dynamic/linux_mini_arm32v0.40.6.tar	2026-07-24 22:32:50 +08:00
zhiyong.luo	371e829493	bug-fixed	2026-07-24 22:31:50 +08:00
zhiyong.luo	ee5aa9fcfa	Delete windows_x86v0.40.6.tar	2026-07-24 22:30:23 +08:00
zhiyong.luo	6f4dd0c113	Delete linux_x86v0.40.6.tar	2026-07-24 22:30:09 +08:00
zhiyong.luo	a5004e5005	Delete linux_x86_64v0.40.6.tar	2026-07-24 22:29:52 +08:00
zhiyong.luo	2da3959397	Delete linux_arm32v0.40.6.tar	2026-07-24 22:29:35 +08:00
zhiyong.luo	ffe17b72e9	Delete app-release.apk	2026-07-24 22:29:19 +08:00
zhiyong.luo	9b7b8ffbf5	bug-fixed	2026-04-17 22:17:05 +08:00
zhiyong.luo	f563fce37e	bug-fixed	2026-04-17 22:12:39 +08:00
zhiyong.luo	2207cbdde0	bug-fixed	2026-03-22 20:25:31 +08:00
zhiyong.luo	489fd7edfd	Update readme.md	2026-03-03 22:05:46 +08:00
zhiyong.luo	404022e397	bug-fixed	2026-03-03 21:55:47 +08:00
zhiyong.luo	dadf91d49c	Delete dynamic/windows_mini_x86v0.40.5.tar	2026-03-03 21:54:10 +08:00
zhiyong.luo	824ed30928	Delete dynamic/macos_mini_universalv0.40.5.tar	2026-03-03 21:53:57 +08:00
zhiyong.luo	e4eb71d1b2	Delete dynamic/linux_mini_x86v0.40.5.tar	2026-03-03 21:53:44 +08:00
zhiyong.luo	de04b8a705	Delete dynamic/linux_mini_x86_64v0.40.5.tar	2026-03-03 21:53:33 +08:00
zhiyong.luo	922dfe0290	Delete dynamic/linux_mini_riscv64v0.40.5.tar	2026-03-03 21:53:20 +08:00
zhiyong.luo	69c1a5d9f5	Delete dynamic/linux_mini_riscv32v0.40.5.tar	2026-03-03 21:53:09 +08:00
zhiyong.luo	9085d664e4	Delete dynamic/linux_mini_mipsel64v0.40.5.tar	2026-03-03 21:52:58 +08:00
zhiyong.luo	d85518c688	Delete dynamic/linux_mini_mipsel32v0.40.5.tar	2026-03-03 21:52:50 +08:00
zhiyong.luo	a2e23d8a4d	Delete dynamic/linux_mini_mipsel32-uclibcv0.40.5.tar	2026-03-03 21:52:40 +08:00
zhiyong.luo	fa9da57987	Delete dynamic/linux_mini_mips64v0.40.5.tar	2026-03-03 21:52:28 +08:00
zhiyong.luo	313b68cdab	Delete dynamic/linux_mini_mips32v0.40.5.tar	2026-03-03 21:52:16 +08:00
zhiyong.luo	2932180a1f	Delete dynamic/linux_mini_loongarch64v0.40.5.tar	2026-03-03 21:52:05 +08:00
zhiyong.luo	a451a33d6e	Delete dynamic/linux_mini_arm64v0.40.5.tar	2026-03-03 21:51:53 +08:00
zhiyong.luo	5de7ced040	Delete dynamic/linux_mini_arm32v0.40.5.tar	2026-03-03 21:51:37 +08:00
zhiyong.luo	1cc1aafc21	bug-fixed	2026-03-03 21:49:10 +08:00
zhiyong.luo	6890584522	Delete linux_x86v0.40.5.tar	2026-03-03 21:47:40 +08:00
zhiyong.luo	fd33768707	Delete windows_x86v0.40.5.tar	2026-03-03 21:47:24 +08:00
zhiyong.luo	b8c4ff66c3	Delete linux_x86_64v0.40.5.tar	2026-03-03 21:47:06 +08:00
zhiyong.luo	d90f576ac3	Delete linux_arm32v0.40.5.tar	2026-03-03 21:46:48 +08:00
zhiyong.luo	90943b8616	Delete app-release.apk	2026-03-03 21:46:32 +08:00
zhiyong.luo	61e6934d8d	bug-fixed	2025-11-15 11:03:05 +08:00
zhiyong.luo	70f07d3839	bug-fixed	2025-11-15 11:02:16 +08:00
zhiyong.luo	7785691b30	bug-fixed	2025-11-15 10:27:47 +08:00
zhiyong.luo	b1a307ed31	bug-fixed	2025-11-15 10:26:45 +08:00
zhiyong.luo	9c82d86831	bug-fixed	2025-11-14 23:03:13 +08:00
zhiyong.luo	1bec1018f6	bug-fixed	2025-11-14 23:02:16 +08:00
zhiyong.luo	f10d152386	bug-fixed	2025-11-04 22:28:16 +08:00
zhiyong.luo	b9fc37927c	bug-fixed	2025-11-04 22:27:06 +08:00
zhiyong.luo	869d478947	bug-fixed	2025-10-26 18:54:11 +08:00
zhiyong.luo	fd10c67cd6	bug-fixed	2025-10-26 18:53:02 +08:00
zhiyong.luo	ff727bbf66	bug-fixed	2025-10-12 18:21:06 +08:00
zhiyong.luo	743bfda88e	bug-fixed	2025-10-12 18:19:51 +08:00
zhiyong.luo	4156bdd28c	bug-fixed	2025-09-28 23:20:51 +08:00
zhiyong.luo	212f551f6c	bug-fixed	2025-09-28 23:18:07 +08:00
zhiyong.luo	f70d8fa1c9	bug-fixed	2025-09-25 21:24:51 +08:00
zhiyong.luo	2379718df6	bug-fixed	2025-09-25 21:23:38 +08:00
zhiyong.luo	eebeb6e6ce	Update readme.md	2025-09-25 21:22:18 +08:00
zhiyong.luo	f2a56644e5	bug-fixed	2025-09-23 18:47:47 +08:00
zhiyong.luo	9e7055e404	bug-fixed	2025-09-23 18:46:47 +08:00
zhiyong.luo	dc9f297f79	bug-fixed	2025-09-21 22:08:14 +08:00
zhiyong.luo	436116da92	bug-fixed	2025-09-20 10:06:46 +08:00
zhiyong.luo	bc5542ca7c	bug-fixed	2025-09-20 10:05:34 +08:00
zhiyong.luo	a11a5202a4	Update readme.md	2025-09-20 09:33:13 +08:00
zhiyong.luo	921269cce6	bug-fixed	2025-09-20 09:28:40 +08:00
zhiyong.luo	93102df95b	Delete dynamic/macos_mini_universalv0.40.4.tar	2025-09-20 09:26:50 +08:00
zhiyong.luo	17b1d90b7f	Delete dynamic/linux_mini_x86v0.40.4.tar	2025-09-20 09:26:42 +08:00
zhiyong.luo	717a52c56a	Delete dynamic/linux_mini_x86_64v0.40.4.tar	2025-09-20 09:26:31 +08:00
zhiyong.luo	920c32a91e	Delete dynamic/linux_mini_riscv64v0.40.4.tar	2025-09-20 09:26:22 +08:00
zhiyong.luo	682bc7a724	Delete dynamic/linux_mini_riscv32v0.40.4.tar	2025-09-20 09:26:10 +08:00
zhiyong.luo	3c4bd913a0	Delete dynamic/linux_mini_mipsel64v0.40.4.tar	2025-09-20 09:26:01 +08:00
zhiyong.luo	8fe03b6bca	Delete dynamic/linux_mini_mipsel32v0.40.4.tar	2025-09-20 09:25:51 +08:00
zhiyong.luo	4a3c14457c	Delete dynamic/linux_mini_mipsel32-uclibcv0.40.4.tar	2025-09-20 09:25:42 +08:00
zhiyong.luo	abb658bc88	Delete dynamic/linux_mini_mips64v0.40.4.tar	2025-09-20 09:25:33 +08:00
zhiyong.luo	15992d6d97	Delete dynamic/linux_mini_mips32v0.40.4.tar	2025-09-20 09:25:23 +08:00
zhiyong.luo	ac304cf2f5	Delete dynamic/linux_mini_loongarch64v0.40.4.tar	2025-09-20 09:25:14 +08:00
zhiyong.luo	15a0812634	Delete dynamic/linux_mini_arm64v0.40.4.tar	2025-09-20 09:25:04 +08:00
zhiyong.luo	a0fc70710b	Delete dynamic/linux_mini_arm32v0.40.4.tar	2025-09-20 09:24:46 +08:00
zhiyong.luo	4717d8bce3	Delete windows_x86v0.40.4.tar	2025-09-20 09:24:26 +08:00
zhiyong.luo	37cdb9e1b8	Delete linux_x86v0.40.4.tar	2025-09-20 09:24:08 +08:00
zhiyong.luo	9eb42ef487	Delete linux_x86_64v0.40.4.tar	2025-09-20 09:23:58 +08:00
zhiyong.luo	d97e95ae0b	Delete linux_arm32v0.40.4.tar	2025-09-20 09:23:48 +08:00
zhiyong.luo	e440af62b0	bug-fixed	2025-09-20 09:22:30 +08:00
zhiyong.luo	a7e0e721f3	bug-fixed	2025-04-14 19:38:04 +08:00
zhiyong.luo	04b1b3a9c0	bug-fixed	2025-04-14 19:37:16 +08:00
zhiyong.luo	784352c44d	bug-fixed	2025-04-05 23:11:06 +08:00
zhiyong.luo	f3a83e67a7	bug-fixed	2025-04-05 22:54:50 +08:00
zhiyong.luo	9c411fd5d9	bug-fixed	2025-04-05 22:53:29 +08:00
zhiyong.luo	f2035b848b	Update readme.md	2025-03-25 23:47:45 +08:00
zhiyong.luo	a0b2caf0b6	Update readme.md	2025-03-25 23:42:31 +08:00
zhiyong.luo	417f4e9354	bug-fixed	2025-03-25 23:37:04 +08:00
zhiyong.luo	969db39060	bug-fixed	2025-03-25 23:35:41 +08:00
zhiyong.luo	fc285b9916	bug-fixed	2025-03-24 21:20:55 +08:00
zhiyong.luo	5301e80916	bug-fixed	2025-03-24 21:17:29 +08:00
zhiyong.luo	61e738d8c4	bug-fixed	2025-02-28 22:29:46 +08:00
zhiyong.luo	5c5117f828	bug-fixed	2025-02-28 22:27:46 +08:00
zhiyong.luo	ba741f70cd	bug-fixed	2024-12-14 11:38:34 +08:00
zhiyong.luo	8860ac3595	bug-fixed	2024-12-14 11:36:48 +08:00
zhiyong.luo	9986a346ed	bug-fixed	2024-12-14 11:35:21 +08:00
zhiyong.luo	8da94071dc	bug-fixed	2024-10-15 20:18:30 +08:00
zhiyong.luo	e44d26bf2a	bug-fixed	2024-10-15 20:17:23 +08:00
zhiyong.luo	16a26182b2	Update readme.md	2024-10-12 23:57:32 +08:00
zhiyong.luo	79f395c093	Update readme.md	2024-10-12 22:59:15 +08:00
zhiyong.luo	c16d1fcdf5	bug-fixed	2024-10-12 22:56:32 +08:00
zhiyong.luo	a875ae051c	Delete dynamic/macos_mini_universalv0.40.3.tar	2024-10-12 22:55:51 +08:00
zhiyong.luo	2eb1524030	Delete dynamic/linux_mini_x86v0.40.3.tar	2024-10-12 22:55:42 +08:00
zhiyong.luo	09f737df0f	Delete dynamic/linux_mini_x86_64v0.40.3.tar	2024-10-12 22:55:32 +08:00
zhiyong.luo	4ffc86cfae	Delete dynamic/linux_mini_riscv64v0.40.3.tar	2024-10-12 22:55:22 +08:00
zhiyong.luo	511edc8d70	Delete dynamic/linux_mini_riscv32v0.40.3.tar	2024-10-12 22:55:13 +08:00
zhiyong.luo	d7a6eb28f3	Delete dynamic/linux_mini_mipsel64v0.40.3.tar	2024-10-12 22:55:04 +08:00
zhiyong.luo	864b354180	Delete dynamic/linux_mini_mipsel32v0.40.3.tar	2024-10-12 22:54:54 +08:00
zhiyong.luo	033c6f09d5	Delete dynamic/linux_mini_mipsel32-uclibcv0.40.3.tar	2024-10-12 22:54:38 +08:00
zhiyong.luo	a0d590b3f0	Delete dynamic/linux_mini_mips64v0.40.3.tar	2024-10-12 22:54:26 +08:00
zhiyong.luo	8818711a5c	Delete dynamic/linux_mini_mips32v0.40.3.tar	2024-10-12 22:54:16 +08:00
zhiyong.luo	05e44409f5	Delete dynamic/linux_mini_loongarch64v0.40.3.tar	2024-10-12 22:54:03 +08:00
zhiyong.luo	ec10470b82	Delete dynamic/linux_mini_arm64v0.40.3.tar	2024-10-12 22:53:52 +08:00
zhiyong.luo	a5d117df84	Delete dynamic/linux_mini_arm32v0.40.3.tar	2024-10-12 22:53:40 +08:00
zhiyong.luo	d4600b95a7	bug-fixed	2024-10-12 22:53:17 +08:00
zhiyong.luo	a323452a82	Delete windows_x86v0.40.3.tar	2024-10-12 22:52:48 +08:00
zhiyong.luo	9d4d3a1bff	Delete linux_x86v0.40.3.tar	2024-10-12 22:52:36 +08:00
zhiyong.luo	71aaa0c421	Delete linux_x86_64v0.40.3.tar	2024-10-12 22:52:26 +08:00
zhiyong.luo	4c809b8577	Delete linux_arm32v0.40.3.tar	2024-10-12 22:52:09 +08:00
zhiyong.luo	fd884aca05	bug-fixed	2024-09-25 19:24:37 +08:00
zhiyong.luo	a347054e17	bug-fixed	2024-09-25 19:23:25 +08:00
zhiyong.luo	7ce9f7ab98	bug-fixed	2024-09-23 19:51:29 +08:00
zhiyong.luo	0d07d5d84b	bug-fixed	2024-09-23 19:50:36 +08:00
zhiyong.luo	11f5d69309	bug-fixed	2024-09-20 22:14:30 +08:00
zhiyong.luo	b04f4b19cb	bug-fixed	2024-09-20 22:13:46 +08:00
zhiyong.luo	297b07f5cc	bug-fixed	2024-09-20 00:11:12 +08:00
zhiyong.luo	5c84ac3835	bug-fixed	2024-09-19 23:55:19 +08:00
zhiyong.luo	9ff76358eb	bug-fixed	2024-09-10 23:02:18 +08:00
zhiyong.luo	ccd4b7265d	bug-fixed	2024-09-10 23:01:22 +08:00
zhiyong.luo	5f1e37f9b2	bug-fixed	2024-09-08 15:17:08 +08:00
zhiyong.luo	e8aa34c0b9	bug-fixed	2024-09-08 15:16:11 +08:00
zhiyong.luo	a107c598f3	bug-fixed	2024-09-07 13:07:55 +08:00
zhiyong.luo	5de5a737d0	bug-fixed	2024-09-07 13:07:06 +08:00
zhiyong.luo	10c95b1129	bug-fixed	2024-09-06 22:58:14 +08:00
zhiyong.luo	2e10283976	bug-fixed	2024-09-06 22:57:07 +08:00
zhiyong.luo	6678b19f11	bug-fixed	2024-09-05 19:31:43 +08:00
zhiyong.luo	dac82f87a9	bug-fixed	2024-09-05 19:30:50 +08:00
zhiyong.luo	e2f165fa1a	bug-fixed	2024-09-02 20:26:44 +08:00
zhiyong.luo	f11ba77b30	bug-fixed	2024-09-02 20:25:50 +08:00
zhiyong.luo	5ab5d43d60	bug-fixed	2024-08-31 10:55:07 +08:00
zhiyong.luo	507176936a	bug-fixed	2024-08-31 10:53:40 +08:00
zhiyong.luo	0af55588c9	bug-fixed	2024-08-27 00:20:25 +08:00
zhiyong.luo	2706478a3c	bug-fixed	2024-08-27 00:16:40 +08:00
zhiyong.luo	5b9186e0c1	bug-fixed	2024-08-24 14:29:28 +08:00
zhiyong.luo	7d7928cbb1	bug-fixed	2024-08-24 14:28:37 +08:00
zhiyong.luo	0507f6c943	Update readme.md	2024-08-20 21:13:08 +08:00
zhiyong.luo	fc9e4195ad	bug-fixed	2024-08-20 21:10:23 +08:00
zhiyong.luo	c278332b59	bug-fixed	2024-08-20 21:09:36 +08:00
zhiyong.luo	41e0de9db4	bug-fixed	2024-08-17 16:15:03 +08:00
zhiyong.luo	537d605ce2	bug-fixed	2024-08-17 16:09:50 +08:00
zhiyong.luo	ad741eabbd	Update readme.md	2024-08-17 13:07:04 +08:00
zhiyong.luo	3a2eccc378	bug-fixed	2024-08-17 12:12:39 +08:00
zhiyong.luo	39eaa5623e	bug-fixed	2024-08-17 12:11:44 +08:00
zhiyong.luo	5eba2ece13	bug-fixed	2024-08-17 10:52:06 +08:00
zhiyong.luo	4055258b42	bug-fixed	2024-08-17 10:50:28 +08:00
zhiyong.luo	a6f16782cc	bug-fixed	2024-08-17 00:25:27 +08:00
zhiyong.luo	afdfee6bbb	bug-fixed	2024-08-17 00:24:32 +08:00
zhiyong.luo	59e3575ae0	bug-fixed	2024-08-16 22:54:52 +08:00
zhiyong.luo	ce0648a3ad	bug-fixed	2024-08-16 22:53:58 +08:00
zhiyong.luo	84fea8dce5	bug-fixed	2024-08-16 18:54:22 +08:00
zhiyong.luo	7aff241795	bug-fixed	2024-08-16 18:53:25 +08:00
zhiyong.luo	b878451582	bug-fixed	2024-08-15 18:26:56 +08:00
zhiyong.luo	ef6a5f73c1	bug-fixed	2024-08-15 18:24:03 +08:00
zhiyong.luo	b8f828227c	bug-fixed	2024-08-14 22:56:27 +08:00
zhiyong.luo	34cb8eb212	bug-fixed	2024-08-14 22:55:08 +08:00
zhiyong.luo	c1d2450821	bug-fixed	2024-08-14 21:50:23 +08:00
zhiyong.luo	e943a37952	bug-fixed	2024-08-14 21:48:58 +08:00
zhiyong.luo	6c1a1b3fa5	bug-fixed	2024-08-14 12:47:03 +08:00
zhiyong.luo	0e7ba63051	bug-fixed	2024-08-14 12:45:11 +08:00
zhiyong.luo	d8e6e2981d	bug-fixed	2024-08-14 00:06:51 +08:00
zhiyong.luo	54fe3692c9	bug-fixed	2024-08-14 00:05:50 +08:00
zhiyong.luo	d22e3f570e	bug-fixed	2024-08-13 22:12:05 +08:00
zhiyong.luo	7c8f6f00f0	bug-fixed	2024-08-13 22:11:15 +08:00
zhiyong.luo	e34d5a6ac4	Update readme.md	2024-08-08 21:16:55 +08:00
zhiyong.luo	dfa9e736d6	Update readme.md	2024-08-08 18:32:03 +08:00
zhiyong.luo	c064a8f75d	bug-fixed	2024-08-08 18:29:56 +08:00
zhiyong.luo	c7a1b6a63c	Update readme.md	2024-08-07 19:03:03 +08:00
zhiyong.luo	54ea1c5fcd	bug-fixed	2024-08-07 18:29:59 +08:00
zhiyong.luo	af589a1f19	Delete dynamic/macos_mini_universalv0.40.2.tar	2024-08-07 18:27:22 +08:00
zhiyong.luo	cb8c091106	Delete dynamic/linux_mini_x86v0.40.2.tar	2024-08-07 18:27:14 +08:00
zhiyong.luo	75beeef7e1	Delete dynamic/linux_mini_x86_64v0.40.2.tar	2024-08-07 18:27:06 +08:00
zhiyong.luo	9d01a75f26	Delete dynamic/linux_mini_riscv64v0.40.2.tar	2024-08-07 18:26:58 +08:00
zhiyong.luo	aa053a1e2f	Delete dynamic/linux_mini_mipsel64v0.40.2.tar	2024-08-07 18:26:49 +08:00
zhiyong.luo	b613e19974	Delete dynamic/linux_mini_mipsel32v0.40.2.tar	2024-08-07 18:26:41 +08:00
zhiyong.luo	3a39cf0b7d	Delete dynamic/linux_mini_mipsel32-uclibcv0.40.2.tar	2024-08-07 18:26:34 +08:00
zhiyong.luo	ca6daad11c	Delete dynamic/linux_mini_mips64v0.40.2.tar	2024-08-07 18:26:25 +08:00
zhiyong.luo	e966a691a9	Delete dynamic/linux_mini_mips32v0.40.2.tar	2024-08-07 18:26:17 +08:00
zhiyong.luo	4dfd78f507	Delete dynamic/linux_mini_arm64v0.40.2.tar	2024-08-07 18:26:09 +08:00
zhiyong.luo	3563feee57	Delete dynamic/linux_mini_arm32v0.40.2.tar	2024-08-07 18:25:57 +08:00
zhiyong.luo	45e457ea5c	bug-fixed	2024-08-07 18:25:34 +08:00
zhiyong.luo	f1edadbf0e	Delete windows_x86v0.40.2.tar	2024-08-07 18:21:22 +08:00
zhiyong.luo	cd11720ce0	Delete linux_x86v0.40.2.tar	2024-08-07 18:21:11 +08:00
zhiyong.luo	b79cce7922	Delete linux_x86_64v0.40.2.tar	2024-08-07 18:20:57 +08:00
zhiyong.luo	5d459a0da8	Delete app-release.apk	2024-08-07 18:20:45 +08:00
zhiyong.luo	29f2b87d6a	Delete linux_arm32v0.40.2.tar	2024-08-07 18:20:14 +08:00
zhiyong.luo	79e3ef7809	Update readme.md	2024-08-06 23:19:31 +08:00