dinoxim/monocles-chat-muji-legacy
1
0
Code Issues Pull requests Projects Releases 9 Packages Wiki Activity Actions
9 releases 9 tags
  • v2.2.2-muji-legacy.9 80fd6d61b6

    monocles chat MUJI legacy test build 9 Pre-release

    dinoxim released this 2026-09-13 00:57:20 +02:00 | 0 commits to main since this release

    Experimental private-MUC MUJI interoperability build.

    Test 9 applies the frozen conference content names, payload IDs and packet times before committing native offers, answers and ICE-restart descriptions. It checks the actual WebRTC result before signaling it. Optional RTX omission remains supported; incompatible names and timing are rejected before READY.

    Pair this APK with DinoX cd010185, including its new ABI 39 / IPC 9 runtime. DinoX now commits the same identities in the native media transport and Jingle descriptions. Controlled tests reproduced the earlier connected-without-media failure and verify bidirectional synthetic audio/video after the fix.

    Validation: 85 Android JVM tests and APK/signature checks passed. DinoX passed the strict Linux build, 873 XMPP cases, the selected engine/signaling suites, four native Windows VM smoke programs and the complete portable Windows build with its strict test phase. Android WebRTC 129 has not been exercised on a device here; a real DinoX-Monocles call and the earlier Android runtime crash remain acceptance checks.

    The APK uses the separate package ID de.monocles.chat.mujilegacy, legacy OMEMO and the same test/debug signing key as Test 8. It contains arm64-v8a, armeabi-v7a, x86 and x86_64 native libraries. See MUJI_TESTING.md for installation and the call test matrix.

    Monocles source: 80fd6d61b6c1dec5a3b21ac4b78fc2816eaa280a. APK SHA-256: 4d35e3756bd85c185c241d2e833a67039e7faf264f3904fa5b6146843c2991c6.

    Downloads
  • v2.2.2-muji-legacy.8 855a8fa099

    monocles chat MUJI legacy test build 8 Pre-release

    dinoxim released this 2026-09-12 22:26:26 +02:00 | 2 commits to main since this release

    Experimental private-MUC MUJI interoperability build.

    Test 8 selects a shared conference payload mapping across READY participants and accepts primary codecs without optional RTX. It rejects changed payload identities, orphan RTX, and answer codecs absent from the local offer or the sender's READY advertisement.

    Use this build with DinoX 634cb36e, which rejects orphan RTX in native MUJI answers. Direct 1:1 calls retain their existing path.

    Validation: 62 focused Android tests passed; APK build and signature verification succeeded. DinoX passed its strict build, 869 XMPP tests and two Google/libwebrtc smoke tests. A real cross-client audio/video call has not yet been verified with these changes. The earlier Android runtime crash is not claimed fixed by these codec tests.

    The APK keeps legacy OMEMO and the separate package ID de.monocles.chat.mujilegacy. It uses the same test/debug signing key as Test 7 and can update that test package. See MUJI_TESTING.md for installation and the runtime test matrix.

    APK SHA-256: e2ab86be0b8217f47c35e86524dc8f6842565f97c768dc38a982d358767cd431

    Downloads
  • v2.2.2-muji-legacy.7 182332e1d9

    monocles chat MUJI legacy test build 7 Pre-release

    dinoxim released this 2026-08-29 13:28:10 +02:00 | 4 commits to main since this release

    Experimental private-MUC MUJI interoperability build.

    Test 7 aligns XEP-0338 BUNDLE content mapping with DinoX and keeps MUJI WebRTC operations alive until native callbacks finish or the bounded close timeout reports a failure. Direct 1:1 calls stay on the existing non-MUJI path.

    This build keeps legacy OMEMO and uses the separate package ID de.monocles.chat.mujilegacy. See MUJI_TESTING.md for the test matrix.

    Downloads
  • v2.2.2-muji-legacy.6 b9c3497ac5

    monocles chat MUJI legacy test build 6 Pre-release

    dinoxim released this 2026-08-28 23:11:29 +02:00 | 6 commits to main since this release

    Experimental private-MUC MUJI interoperability build.\n\nTest 6 binds remote video received through WebRTC Unified Plan callbacks, follows the shared local camera track after delayed capture startup, and hardens callback cleanup while participant legs close. Use it with DinoX commit b3647d50, which queues valid trickle ICE candidates until the remote description is ready.\n\nThis build keeps legacy OMEMO. Runtime testing is still required; see MUJI_TESTING.md.

    Downloads
  • v2.2.2-muji-legacy.5 36d98c1e54

    monocles chat MUJI legacy test build 5 Pre-release

    dinoxim released this 2026-08-28 15:39:17 +02:00 | 8 commits to main since this release

    Experimental private-MUC MUJI interoperability build.

    This build keeps legacy OMEMO and fixes conference-wide MID/payload use inside the peer connection, early ICE backlog handling, one Android audio-routing owner per conference, and fault-tolerant Bluetooth/audio cleanup. Direct 1:1 calls continue through the existing non-MUJI path.

    Runtime testing with DinoX is still required; see MUJI_TESTING.md.

    Downloads
  • v2.2.2-muji-legacy.4 fd87325b0b

    MUJI interoperability test 4 Pre-release

    dinoxim released this 2026-08-28 13:47:29 +02:00 | 15 commits to main since this release

    This build fixes the conference payload-map failure found during private-MUC calls between DinoX and monocles chat.

    • freezes one exact READY payload map for every pairwise Jingle leg
    • preserves and validates RTP parameters, RTCP feedback and RTX/apt dependencies
    • translates local payload-ID collisions by codec identity
    • binds incoming media to the sender's READY advertisement
    • removes failed peer legs without changing the direct 1:1 call path

    Validation: 38 focused MUJI/RTP tests passed. The universal APK is signed with the Android debug key and remains an experimental interoperability build.

    Downloads
  • v2.2.2-muji-legacy.3 8a81ec03cb

    MUJI legacy test build 3 Pre-release

    dinoxim released this 2026-08-28 11:33:43 +02:00 | 18 commits to main since this release

    This test build fixes MUJI joining in an already joined private MUC. Reflected availability updates are recognised as self-presence by exact full occupant JID even when the room does not repeat status code 110.

    It is an experimental side-by-side debug build and is not an official monocles release. See MUJI_TESTING.md for the test procedure.

    SHA-256: 56b289b46fe7ed351b45c3f63259265ab1a00d60c40a0c7e41972c89dc2e918f

    Downloads
  • v2.2.2-muji-legacy.2 8547a92e73

    MUJI legacy test build 2 Pre-release

    dinoxim released this 2026-08-28 10:18:04 +02:00 | 21 commits to main since this release

    Test build 2 for private, non-anonymous MUC audio and video calls.

    Changes since test build 1:

    • routes live XEP-0482 invitations to the originating room and ignores archived or replayed invitations
    • joins only after explicit acceptance and validates the exact inviter and participant full JIDs
    • prevents overlapping 1:1 and MUJI call admission
    • hardens conference teardown, Jingle setup and WebRTC ICE races

    Build:

    • Package: de.monocles.chat.mujilegacy
    • Version: 2.2.2-muji-legacy
    • SHA-256: 4fc4aec78034c13aec137c96bc144946cc585a2b47837b521c39eb3bbc2ebfef
    • Debug signed; arm64-v8a, armeabi-v7a, x86 and x86_64
    • 16 unit tests pass

    This remains a test build with legacy OMEMO only. Runtime interoperability still needs testing.

    Downloads
  • v2.2.2-muji-legacy.1 e3ed0ccc20

    MUJI legacy test build 1 Pre-release

    dinoxim released this 2026-08-27 12:14:24 +02:00 | 24 commits to main since this release

    Test build for private, non-anonymous MUC audio/video calls.

    Review:

    Build:

    • Package: de.monocles.chat.mujilegacy
    • Version: 2.2.2-muji-legacy
    • SHA-256: b0261d2a8547b3f05c42839841ba84b9a6b28342d5c78a8ec48137af76023028
    • Debug signed; arm64-v8a, armeabi-v7a, x86 and x86_64

    Limits:

    • Legacy OMEMO only; no PQ/OMEMO2
    • Private members-only, non-anonymous MUCs only
    • Full mesh; no SFU
    • MUJI DTLS fingerprints are not bound to legacy OMEMO identities
    • Runtime interoperability still requires testing
    Downloads