monocles chat

DinoX development fork: WebRTC M152 and MUJI

Our working branch is master in this repository. It contains the M152 audio/video and MUJI changes on top of upstream Experimental8-v2.3.1.

What you need	Where to find it
Current source code	monocles-chat / master
Published APKs and checksums	Monocles downloads
WebRTC library for building the app	M152 Android library 152.0.0-dinox.3

The separate release variant is monocles chat, with app ID de.monocles.chat.dinox. It uses its own release signing key, disables debugging and applies R8 code/resource shrinking. It installs beside the official Monocles app. The universal package includes all four Android architectures; release downloads use names such as monocles-chat-2.3.1-m152-muji.apk. Each published APK has a checksum and a tag fixing its exact source. The release description states which checks are complete and which device tests are pending.

The earlier monocles chat test download is a debug build with a different app ID and test signature. It cannot be updated in place by the separate release app. debug means debugging is enabled and the release build's R8 shrinking is absent; it is not another name for a signed release build.

The WebRTC AAR is a build dependency, not an installable app. It stays in its own repository so other developers can reuse the same verified library. App users only need the APK. Library versions .1 and .2 are superseded by .3.

The M152/MUJI integration's JVM run passed 274 of 276 tests; two tests require an unavailable host libsignal library. Android device installation and real 1:1/MUJI calls still need testing. See build instructions and call behavior and device tests.

The original Monocles project is on Codeberg. The older monocles-chat-muji-legacy fork is historical; current work belongs here.

Upstream project information

🇩🇪… Deutsche Version der Readme hier verfügbar. / Francais ici / Italiano qui / Przeczytaj po polsku / Türkçe sürüm burada

monocles chat is a modern and secure Android XMPP client. Based on Conversations but with a lot of changes and additional features. The changes aim to improve usability and ease transition from pre-installed and other widespread chats. Here are some screenshots:

Screens designed by Pigeonalley (https://pigeonalley.com)

Download

Presettings

monocles chat has different presettings compared to blabber.im:

• don't show previews of weblinks in chat
• don't show previews of locations in chat
• don't automatically download all attachments

OTR

monocles chat supports OTR encryption! Though it's not easy to use OTR does have some advantages: https://en.wikipedia.org/wiki/Off-the-Record_Messaging#Implementation

Download

monocles chat is available for install in the F-Droid Alternatively beta-release APKs are available via codeberg: Releases

monocles chat nightly and beta

nightly or beta-release APKs are available via codeberg: Releases

Social Media

Follow us on monocles social

There are also English and German speaking XMPP-room focusing on support and development of the monocles chat.

If you are interested in the development of the chat, here is a MUC for you (English and German speaking):

Development-Chat: development@conference.monocles.de

There also is an Support-MUC where you can ask questions and get help with issues you may encounter, see further below for details.

How can I support translations ?

You can improve or create translations on Codeberg Translate. Thank you very much.

Help! I've encountered issues!

The easiest way to get some help is to join our support-MUC (both English and German).

Support-Chat invite link: support@conference.monocles.de

If we can't fix your problem there, you can open an issue here, detailing your problem, how to reproduce it and provide logs. See instructions below on how to create log files.

How to create debug logs? (adb)

GNU/Linux, OSX and other Unix-like systems:

1. First install The Android Debugging Bridge, if not already present.

   Debian and derivates like Ubuntu / Linux Mint

   sudo apt-get update
   sudo apt-get update adb
   # Debian Jessie or older:
   # sudo apt-get install android-tools-adb
   

   openSUSE 42.2 and 42.3

   sudo zypper ref
   sudo zypper install android-tools
   

   openSUSE Tumbleweed

   here you need to add the following repo (e.g. via Yast): http://download.opensuse.org/repositories/hardware/openSUSE_Tumbleweed/

   alternatively you have the option to use the 1 Click installer https://software.opensuse.org/package/android-tools

   other systems

   install adb using a method appropriate for your system

2. Now open a terminal in a directory of you're choice, or navigate to the directory using cd.

3. Follow steps [6] to [10] of the Windows instructions.

4. Start outputting your log to a file on your computer. We will be using logcat.txt. Enter:

   $ adb -d logcat -v time | grep -i "monocles chat" > logcat.txt
   

5. Follow the remaining steps [12] and [13] of the Windows instructions.

Windows:

1. Download Google's SDK-platform tools for your operating system:

   https://developer.android.com/studio/releases/platform-tools.html

2. In case they were not included: You also need the ADB_drivers for your version of Microsoft Windows:

   https://developer.android.com/studio/run/win-usb.html

3. Extract the zip-archive (e.g. to C:\ADB\)

4. Open the command line (CMD) using the start menu: Start > Execute: cmd

5. Navigate to the directory you extracted the zip to as following. We will be using C:\ADB\

   c:
   cd ADB
   

6. On your smartphone open the settings and search for the item Developer Options. If this option is not already present on your phone you will need to unlock it beforehand. To do this navigate to Settings > About phone, there locate Build number (or similar) and tap it 7-times in succession. You should now see a notification, that you are now a developer. Congrats, Developer Options are now available in your settings menu.

7. Inside Developer Options search activate the setting USB-Debugging (sometimes just called Android Debugging).

8. Connect your phone to your computer via USB cable. The necessary drivers should now be downloaded and installed if not already present. On Windows all necessary drivers should be downloaded automatically if you followed step [2] beforehand. On most GNU/Linux systems no additional action is required.

9. If everything worked out, you can now return to the command line and test if your device is being recognised. Enter adb devices -l; you should see output similar to:

   > adb devices -l
   List of devices attached
   * daemon not running. starting it now on port 5037 *
   * daemon started successfully *
   042111560169500303f4   unauthorized
   

10. If your devices is labelled as unautorized, you must first accept a prompt on your phone asking if debugging over USB should be allowed. When rerunning adb devices you should now see:

    > adb devices
    List of devices attached
    042111560169500303f4    device
    

11. Start outputting your log to a file on your computer. We will be using logcat.txt in C:\ADB\. Just enter the following (without > into the command line):

    > adb -d logcat -v time | FINDSTR monocles_chat > logcat.txt
    

12. Now reproduce the issue encountered.

13. Stop logging (Ctrl+C). Now take a close look at your log file and remove any personal and private information you may find before sending it together with a detailed description of your issue, instructions on how to reproduce to me. You can use GitHub's issue tracker: Issues