dinoxim/monocles-chat
1
0
Code Issues Pull requests Projects Releases 13 Packages Wiki Activity
13 releases 16 tags
  • v2.3.1-muji.16 db1245d31c

    Monocles 2.3.1 MUJI .16 — ARM64 M149 and M152 Pre-release

    dinoxim released this 2026-10-21 22:16:42 +02:00 | 0 commits to master since this release

    Two signed ARM64 Android APKs for MUJI/OMEMO review. These are prerelease builds, not a release of original Monocles.

    Download Contents Installation
    M152 Full DinoX fork, WebRTC M152 and video effects. 71.9 MiB. de.monocles.chat.dinox
    M149 MUJI/OMEMO upstream proposal, original WebRTC M149, no DinoX video effects or vision runtime. 62.1 MiB. de.monocles.chat.dinox.m149

    The two variants can be installed together. M149 has a separate profile and the launcher name monocles chat M149. Neither replaces original Monocles or the separate .interop20261015 test app. Both use the retained DinoX fork release certificate. M149 is not simply a WebRTC switch in the complete M152 fork; its source deliberately excludes effects and their runtime.

    Both variants support legacy OMEMO v1 and Monocles' PQ OMEMO2 path. For calls with DinoX, select OMEMO v1: DinoX has no enabled PQ path. PQ calls in this release are between compatible Monocles clients. WebRTC M149/M152 is the media engine version, not the choice of encryption. Both use libsignal 0.94.1, source 10861bff671740174f4e99f7e30dc492fcf6ec8b.

    What changed

    MUJI negotiation keeps media names, payload types and codec parameters consistent. Expanding a direct call preserves the existing transport and encryption choice. Participant departure, shared media ownership, asynchronous identity checks and OMEMO bundle publication have additional checks and regression coverage. The proposal builds on original Monocles' MUJI implementation and nickname/READY rules.

    M152 source: db1245d31c753071f506d19afed6b7c240c83000 (the release tag).
    M149 source: d849c8df4a759d722e7a2dc6a0eaa58c4ad13057, based on original master 89bffe8351d2c752db1558eb47e996648deafe52 (separate review branch).

    The MUJI/OMEMO-only upstream contribution is Codeberg PR #559, submitted directly through AGit. The separate M152/effects contribution updates Codeberg PR #554 and depends on #559.

    Checks and remaining tests

    The M152 source passed 945 JVM tests. Its ARM64 APK passed signature, application ID, ZIP integrity, ARM64-only payload, 16 KiB ZIP alignment, absence of instrumentation/test payload, and static M152 JNI/JNI Zero checks.

    The isolated M149 source passed 781 JVM tests, zero failures/errors/skips. Its signed ARM64 APK passed the same identity/ABI/ZIP/test-payload checks. Its packaged WebRTC JNI is byte-identical to the original M149 AAR. The separately extracted M152/effects proposal passed 947 JVM tests, zero failures/errors/skips; this proposal is not the source commit of the full-fork M152 APK.

    These two new APKs have not yet completed fresh device/live-call acceptance. Earlier M152 tests passed direct OMEMO-v1 audio/video with DinoX, mixed three-party audio expansion and a short mixed three-party video run. Separate Monocles PQ tests passed direct audio/video, three-party audio expansion, and audio/video in an existing private three-party room. These are historical results, not acceptance of these new binaries. See the separate OMEMO-v1 and PQ test matrix for exact evidence and open cases.

    Still required on the new binaries: direct calls and participant invitations, existing private-room audio/video with three participants, all media directions after leave/rejoin, full device/fingerprint binding over the call lifecycle, and physical-device camera/microphone/Bluetooth/notification/rotation checks. PQ cases must use Monocles participants only.

    Package and build details

    Only arm64-v8a is included. No instrumentation APK, private test bridge, JUnit classes or libsignal_jni_testing.so is shipped. Required third-party license notices are retained, including notices whose names mention testing.

    Both are non-debuggable, signed release APKs without R8 minification or resource shrinking. The first M152 R8 pass exceeded the bounded server build time; the successful build reused compilation with shrinking disabled. The M149 build uses the same explicit packaging choice. No claim of a successful optimized R8 build is made.

    SHA-256 files and build notes are attached. Architecture-specific build instructions and runtime references for the full fork: Android builds.

    Downloads