## 28. Android / iOS 2.5 series: user-executed recovery tests and additional screenshots

Record date: 2026-09-11. VPNTestor reviewed six additional Android screenshots, three iOS screenshots and user-confirmed test feedback. This record is append-only; the article URL, original publication date, historical text, evidence and signatures remain unchanged.

The Android screenshots display connected interfaces for two different nodes and two different website-observed exit addresses. They document visible connection states and an exit change. Geographic labels or address suffixes alone are not used to establish location, the complete traffic path or exact binding between screenshots and an installation file.

The two Android browser-local check screenshots list no public address but do list a local-scope network address; the iOS screenshots list only an anonymized hostname. The visible results are not identical. The local address displayed on Android is not a public identity, but it shows that the page can read that class of local information. This record does not infer its source or internal architecture, nor restate the result as 'no address exposed'.

The local check has no external address-discovery service configured, so it cannot exclude all public-address, name-resolution or other network leaks. The two iOS local-result images are different views of the same result, not two independent tests. The user's latest clarification states that all submitted IP-check screenshots were taken with VPN enabled; they are not used as a disconnected baseline. The real network address is neither required nor published.

The user confirmed that iOS lock-screen recovery, network switching and recovery after network interruption were tested on the same iPhone and app version, with normal recovery and immediate usability on opening. The user subsequently reported the same three recovery outcomes on Android. Both platforms are recorded as 'user-executed, recovery reported normal'; VPNTestor did not independently operate or continuously observe these recovery sequences.

'Immediately usable on opening' is a user-experience description, not a measured recovery latency. Traffic during switching or failure was not continuously monitored. Normal recovery does not establish leak-free operation throughout; user feedback, screenshot observations and independent test conclusions are recorded separately.

The product scope remains Android / iOS 2.5 series. Earlier checks identified an Android 2.5.8 build 5066 installation sample and iOS 2.5.1 build 18 device metadata. These additional screenshots do not show exact versions or independently bind themselves to those samples, so the earlier sample-identity verification scope is not expanded.

Only checksums of the nine images are published, not the originals' exact addresses, accounts, device identifiers or technical names. The signature covers this record in six languages, the image checksum list and verification instructions. It establishes file integrity and the matching key, not a comprehensive audit, a no-vulnerability conclusion or a new score. Independent regression tests, privacy-protection validation and change-impact assessment still need their own evidence.

### 28.1 Evidence and signature downloads

- [This supplementary record](/downloads/security-audits/singlinkvpn-mobile-2026/Mobile-Recovery-Feedback-2026-09-11-en.md)
- [File checksum manifest](/downloads/security-audits/singlinkvpn-mobile-2026/Mobile-Recovery-Feedback-2026-09-11.sha256)
- [Digital signature](/downloads/security-audits/singlinkvpn-mobile-2026/Mobile-Recovery-Feedback-2026-09-11.sha256.sig)
- [Public verification key](/downloads/security-audits/singlinkvpn-v2.5-2026/James-Robert-Smith-Ed25519-Public-Key.pub)
- [Image checksum list](/downloads/security-audits/singlinkvpn-mobile-2026/Mobile-Recovery-Feedback-2026-09-11-screenshots.sha256)
- [Verification instructions](/downloads/security-audits/singlinkvpn-mobile-2026/Mobile-Recovery-Feedback-2026-09-11-VERIFY.txt)