Repository navigation
v0.10.2
One fix, for a fault found on a phone running 0.10.1. No new settings or permissions.
Disconnecting with apps still connected
Disconnecting, or a restart of the mesh node, while a mesh app had a TCP connection open left one of the app's internal threads stuck for good. Each time this happened:
- the disconnect or restart took 3 seconds longer;
- the stuck thread, and the memory of the connections it held, stayed until the app was closed.
The fault is as old as the split tunnel; it was not introduced by 0.10.1. Disconnecting now ends the thread at once.
The same cause had a second effect while connected. A connection that ended abnormally, for example because the server reset it or the network changed, was kept by the app until an internal timeout. Until then the same app could not open a new connection from the same port. Such a connection is now closed after at most 3 seconds.
Installing over 0.10.1 keeps identity and settings.
Checked on a Pixel 9 Pro (arm64) with this release's APK, installed over 0.10.1: connect, pages loaded in a mesh app, and two disconnects with connections open — each left no thread behind. The other two ABIs were built and checked in CI but have not run on hardware for this release.
Which APK
Most phones: fips-android-v0.10.2-arm64-v8a.apk. If you are unsure, -universal.apk carries all three ABIs for a first install; the in-app updater picks the per-ABI APK.
Signing
Release certificate SHA-256: aa905e32bd0058874d252990abba26c78ddd8fca018195ebd1cd232a99a7a8e1