Skip to content

Releases: Devil1716/bluetooth-manet-android

v1.4.4

Choose a tag to compare

@github-actions github-actions released this 21 Sep 05:50

Full Changelog: v1.4.3...v1.4.4

Mesh 1.4.3

Choose a tag to compare

@github-actions github-actions released this 21 Sep 04:44

File transfers no longer crash the app, including on low-RAM phones.

Fixes

  • Stream files from disk instead of loading the whole file into memory
  • Cap the Bluetooth write queue so a transfer cannot OOM the process
  • Send files off the main thread so the app stays responsive
  • Reassemble incoming files on disk and keep a smaller BLE packet buffer

Existing 1.3.6+ installs can update in place from this APK (app-release.apk).

v1.4.2

Choose a tag to compare

@Devil1716 Devil1716 released this 15 Sep 05:53

Full Changelog: v1.4.1...v1.4.2

v1.4.1

Choose a tag to compare

@Devil1716 Devil1716 released this 10 Sep 17:46

MESH v1.4.1 — delivery, identity, and a real release APK

This build is app-release.apk (versionCode 27), not a debug APK. Installs from v1.3.6–v1.4.0 can update in place. Studio debug builds still need an uninstall first.

What users should notice

  • Messages typed with nobody nearby stay waiting for a nearby phone instead of flipping to failed.
  • A checkmark means the other phone acknowledged the message, not that a neighbor merely forwarded it.
  • If a known contact advertises a different signing key, the chat shows a fingerprint warning and ignores the new key.
  • Nearby empty states distinguish Bluetooth off, missing permission, and still searching.
  • The Mesh notification has Stop nearby chat.

Under the hood

  • Pending messages are kept until an authenticated ACK or 24 hours, not deleted after the first hop.
  • Direct ACKs can use the incoming Bluetooth link (two-phone chat).
  • Packets are authenticated before they occupy the duplicate cache.
  • New installs keep the signing key in Android Keystore; existing installs keep their current identity files.
  • The upload keystore is no longer tracked in git. Git history still contains it — treat that certificate as compromised, and put signing secrets in GitHub Actions if you want CI to build future releases.

Chat payloads are still signed plaintext, not end-to-end encrypted. Relays and radios in range can read message bodies.

Checks

  • ./gradlew testDebugUnitTest assembleDebug passed on the developer machine.
  • This APK is a non-debuggable release build, signed with the existing Mesh upload certificate.
  • Two- and three-phone radio tests were not run for this tag. See docs/HARDWARE_TEST.md.

v1.4.0

Choose a tag to compare

@github-actions github-actions released this 10 Sep 16:47

Full Changelog: v1.3.7...v1.4.0

v1.3.7

Choose a tag to compare

@github-actions github-actions released this 10 Sep 09:30
475e45d

What's Changed

  • Make Mesh feel like a shipped messenger by @Devil1716 in #1

New Contributors

Full Changelog: v1.3.4...v1.3.7

v1.3.6

Choose a tag to compare

@github-actions github-actions released this 10 Sep 07:02
9d7b5c7

Full Changelog: v1.3.5...v1.3.6

v1.3.5

Choose a tag to compare

@github-actions github-actions released this 10 Sep 06:50
c80966a

Full Changelog: v1.3.4...v1.3.5

v1.3.4

Choose a tag to compare

@github-actions github-actions released this 09 Sep 18:14

Full Changelog: v1.3.3...v1.3.4

v1.3.3

Choose a tag to compare

@github-actions github-actions released this 06 Sep 11:39

Full Changelog: v1.3.2...v1.3.3