SchildiChat for Android
Follow the guide at unifiedpush.org to set up UnifiedPush. Once you have that working, SchildiChat should pick it up automatically. You can also change the distributor in Settings/Notifications/Notification Method.
If you want to use ntfy, and don't want to self-host a server yourself, feel free to use ntfy.schildi.chat.
Here are some common reasons for UnifiedPush not working:
For debugging UnifidedPush setups, first try to get the "UP-Example" application to work, which you can get on F-Droid. You may also get help at #unifiedpush:matrix.org.
You can find information about all available variants here.
Unfortunately, that's not possible right now. We will hopefully get support for multiple accounts once Elements supports it (they have it on their roadmap at least). Until then, as workaround, the best thing we can offer is using 5 variants of SchildiChat, when using our own F-Droid repo, as you can install all of these alongside each other:
We have disabled Android Auto support for the app provided in the Google Play Store, since Google requires you to fill extra legal paperwork for that, and you have to guarantee that you did thoroughly test this scenario. But in fact, we haven't tested this at all. If you want to use Android Auto with SchildiChat, you can still download SchildiChat from any of our F-Droid or direct download sources (even if it's the FCM variant) - we haven't disabled Android Auto there, but use at your own risk.
I'm maintaining a list here, but note that this may not be complete and partly outdated.
In case you enabled easy mode during initial setup, you need to first disable it in Settings / Preferences / Easy mode. Then, just click the + / #+ buttons while viewing the home rooms list. You may want to click the "Change network" options menu item in case you want to see public rooms on suggested homeservers other then your own homeserver.
Feel free to support existing issues, or file new issue on GitHub.
In case you experience bugs that require logs to debug, such as app crashes or other bugs not commonly reproducable, send a bug report from within the app (e.g. use the options menu in the chat overview, or enable "rageshake" in the settings and shake the device), and make sure to have the logs option enabled. Also make sure to always provide a concise description of what your issue is and what you did in order to get it.
You can check the downloaded apk from the SpiritCroc F-Droid repository for following SHA-256 hashes (as output e.g. by keytool -printcert -jarfile
) to ensure the app was properly signed with our signing keys:
FA:C0:73:C4:2D:F8:A2:4E:D7:9E:D6:1A:19:86:A0:08:B6:3D:64:68:99:21:70:F8:2C:29:D7:9B:C6:80:8E:AC
66:12:AD:E7:E9:31:74:A5:89:CF:5B:A2:6E:D3:AB:28:23:1A:78:96:40:54:6C:8F:30:37:5E:F0:45:BC:92:42
Schildi = Schildkröte = German for turtle. So "Turtle"-Chat. Feel free to call it Shieldy-Chat (shield for security?), if that's easier to pronounce for you.
We mainly focus on tweaking the UI to our likings and usually do not want to go deep into architectural changes to reduce merge conflicts with upstream.
Sometimes, we like to play with additional community-based features that Element does not prioritize, which means we might support a few more MSCs than Element do.
It may also happen more often than expected that we include additional bug fixes compared to Element, if the Element team misses some bugs which become apparent in our internal testing. Of course, this does not imply that SchildiChat has less bugs, since we're not safe from introducing new ones either.
To summarize, the main goal of the SchildiChat clients is as following: we want to take a Matrix client that is good, and tweak it just to match our taste, since Element's design team has a different taste than we have, and our priorities do not always align with those upstream.
We are not trying to please any particular kind of target user group, except those who share our taste :)
When you have a look at the SchildiChat version, the part before "sc" is the upstream Element version that your current SchildiChat build is based on.
Since SchildiChat is a fork of Element, "upstream" refers to "Element".
You can translate SchildiChat-specific text at translate.schildi.chat! For Element-specific translations, visit their weblate and localazy websites, and we will get it for our next upstream merge.
Thanks for asking! However, we currently do not accept donation. Our goal is not to make money with this project, but just create a chat client that we enjoy using. As a result, we also do not feel any obligations to satisfy user expecations or wishes - this is a hobby project, after all. Feel free to donate to a charity of your choice instead, or to matrix.org directly for maintaining the matrix specification.
Matrix is a chat network, and so you can use it to get in touch with the SchildiChat community! Feel free to join any of the following:
We have announcement rooms that you can join: