Skip to content

MeshLive 0.5.0-beta

Latest

Choose a tag to compare

@gautamgpt1 gautamgpt1 released this 12 Nov 02:57
· 2 commits to main since this release

MeshLive 0.5.0-beta

Open-source build signed with the project's release key; Google Play delivers the same app with the same key.
Application id: io.github.meshlive.app. Source: tag v0.5.0-beta in this repository (commit 691df5646487a08b53b1b5318bac42f3f1eddc38).
Licence: GPL-3.0-or-later; the full text is in LICENSE and third-party licences are in THIRD_PARTY_NOTICES.md of the source.

What changed

  • Calls and live streams can move to Wi-Fi. When both phones support it, a call or stream that connected over
    Bluetooth can move to Wi-Fi Aware, or to Wi-Fi Direct on phones without it, and Bluetooth stays connected as the
    standby that takes over if Wi-Fi stops. It is off by default: Settings > Use Wi-Fi when it helps.
  • Calls start sooner. The camera starts at Accept before the rest of the call setup, a phone waiting for calls
    answers a connection faster, and a slow first connection is retried sooner; in tests calls joined about a second
    sooner from Accept.
  • A frozen call picture now recovers by itself.
  • Moving a call from Bluetooth to Wi-Fi is more reliable: on the pair where it failed, no switch failed with the fix.
  • Security and privacy fixes for relayed streams and calls.
  • The Calls screen uses less battery while it waits for people nearby: its searching indicator stops after 12 s
    instead of redrawing the screen continuously.
  • MeshLive is on Google Play, signed with the same key as the files on this page.

Which file to download

File ABI versionCode SHA-256
MeshLive-0.5.0-beta-arm64-v8a.apk arm64-v8a 112 aa84a9addec4214876f62dbe52cd0893c300f42ee7a0ed36c886e8167f772f0d
MeshLive-0.5.0-beta-armeabi-v7a.apk armeabi-v7a 111 df07cac04e1896a70fcd43d1445cb7bbad66a14e50f026debd0525ab14bc2afc
MeshLive-0.5.0-beta-universal.apk universal 110 f98c9d5c097a104540803674581fc19850b6205aa783473dd9290e781056ba12
  • arm64-v8a: Almost every phone sold since about 2016 (64-bit ARM). Pick this one if unsure.
  • armeabi-v7a: Older or 32-bit-only ARM phones (some Android Go models). A 64-bit phone can also run it, but it is slower and Android will not move it to the 64-bit build by itself.
  • universal: Both libraries in one larger file, for sideloading when you do not know the ABI. Not published to F-Droid.

If adb shell getprop ro.product.cpu.abilist lists arm64-v8a, use the arm64-v8a file.

F-Droid build

File ABI versionCode SHA-256
MeshLive-0.5.0-beta-fdroid-arm64-v8a.apk arm64-v8a 112 26cb31151f7a9524a1476c5c9084ba228f305b8c2d8e4889eda885056422ef6e
MeshLive-0.5.0-beta-fdroid-armeabi-v7a.apk armeabi-v7a 111 bd3d58160c8ded0efe90cda8cf06b47769951320c02a950edff0c2c3a427f3bf

The F-Droid flavour of the same source: no update checker and no permission to install apps. F-Droid rebuilds it
from tag v0.5.0-beta and publishes these signed files only when its own build matches them byte for byte (apart from
the signature). Same key as the files above, so the two kinds of install update each other.

Verify before installing

  1. Hash: sha256sum -c SHA256SUMS --ignore-missing (PowerShell: Get-FileHash <file> -Algorithm SHA256).
  2. Signer: apksigner verify --print-certs MeshLive-0.5.0-beta-arm64-v8a.apk must print exactly one signer whose
    certificate SHA-256 digest is (colon form):
2E:EF:C0:5A:44:45:22:52:9D:9F:75:D7:EB:CE:FD:08:86:47:07:F2:1A:79:04:1D:B5:1E:BF:F8:36:49:E2:13

A different fingerprint means a different publisher: do not install it.
3. Source: SOURCE-MANIFEST.txt lists the commit, the SHA-256 of every tracked file and the pinned native
sources (libaom and libvpx commits and tree SHA-256s, libopus tarball SHA-256; python tools/fetch_native_sources.py
fetches and verifies them). python tools/make_release.py --manifest-only reproduces it from a checkout.

Measured on

The release gate for 0.5.0 was a tagged set of 80 calls on five phones, started the way a person starts the app
(rotating IDs, hidden identities and the app's own video settings on): Samsung Galaxy S24, Galaxy S22 and Galaxy M31,
ASUS ROG Phone II and OPPO A15s, over GATT, LE CoC and Classic Bluetooth, Wi-Fi Aware (S24 and S22) and Wi-Fi Direct,
plus relayed calls through a third phone. The join time is dial to ringing plus Accept to the first real picture, from
an idle phone. Galaxy S22 and Galaxy S24, both directions: every call joined within 4 s. ASUS calling the OPPO A15s:
every call joined, a quarter of them in 6-11 s. Galaxy M31 and Galaxy S24: calls joined in 4-9 s, the M31 being the slowest phone. OPPO A15s calling the ASUS: see Known limits. Overall 40 of 58 counted calls joined within 6 s (69%), short of the project's 90% line; the release ships with that result recorded. Untested combinations
are not claimed to work.

Known limits

  • An OPPO A15s calling an ASUS ROG Phone II often does not ring, or rings only after 11-25 s; calling the other way
    works. This is not new in 0.5.0. A fix is planned: a phone pair whose faster Bluetooth mode failed will start the
    next call in the slower, reliable mode.
  • Wi-Fi is off by default (Settings > Use Wi-Fi when it helps). Wi-Fi Aware is not used while a phone is connected to a
    2.4 GHz Wi-Fi network, because it would share that radio with Bluetooth; Wi-Fi Direct still is.
  • Classic Bluetooth calls need the two phones to be paired in Android's Bluetooth settings first.