@Schlicki2808 Actually, it's me (Lothar). Great to hear that you like the app. Dekko runs a daemon in the background for notifications. There are some technical reasons why this is not so easy for DeltaTouch (let me know if you like to hear the details, it's a little bit complex). Maybe the situation will be different in the future as the use of the library provided by the Delta team that DeltaTouch is based upon will undergo some changes which might make a daemon easier to realize - not sure about that though.

For the time being, notifications depend a little bit whether you're on xenial or on focal. In any case, if background suspension is disabled for DeltaTouch, you will receive notifications if the app is running and in background. In xenial, disabling background suspension can be achieved via UT Tweak Tool. For focal, it can be done via command line (see below), or (as far as I know) a certain git version of UT Tweak Tool has to be build by yourself.

On xenial, if the app is in foreground, you will receive notifications for all accounts that are not the currently selected account (if in chatlist view) or, if you are currently viewing a chat, you will receive notifications for all conversations/accounts except for this specific chat.

On focal, UT currently suppresses any notifications for the app that is currently in foreground, I can't do anything about that.

Disabling background suspension in focal via command line (thanks to Danfro for instructions):

1. Fetch current suspended apps:

gsettings get com.canonical.qtmir lifecycle-exempt-appids

2. Add DeltaTouch to the list (the following assumes that the output of the previous command gave ['com.ubuntu.music'], please adapt to the output of your device):

gsettings set com.canonical.qtmir lifecycle-exempt-appids "['com.ubuntu.music', 'deltatouch.lotharketterer']"

@Ced In the new release, the font size is configurable via settings.

@Schlicki2808 Ok, I can try to explain my thoughts regarding a dedicated background service/daemon, but I might be horribly wrong on some or all of it as I am just an amateur. Anyone, don't hesitate to correct me in that case.

After the latest release which features database encryption, it's quite easy: A daemon which is started automatically does not know the database passphrase, so it won't work before you start the app for the first time after booting. Using a keyring would solve this, but to my knowledge, there's no keyring in Ubuntu Touch at the moment that is automatically unlocked along with the device. In addition, users might want to use a stronger password for the database than the unlock PIN.

Even if database encryption is not active, it's still more difficult to implement than a daemon for Dekko because Dekko doesn't support encrypted emails. In contrast, encrypted messages are the default in Delta Chat/DeltaTouch. So the daemon would have to be able to read the database on the device, talk to email servers and decrypt the messages (to be able to show a part of the message in the notification). In my app, I did not program these tasks myself. Instead, the app uses libdeltachat (deltachat-core-rust) by the developers of Delta Chat. I just added the GUI and a little bit of logic. I don't have the skills and the time to re-write all of this just for a daemon, so it would make sense for a daemon to use libdeltachat as well. However, I think that libdeltachat doesn't have a read-only mode for accessing the database (again, I might be wrong on this). So when the app starts, the daemon would have to drop the database (easy), and when the app is closed, take it up again (no idea how to reliably inform the daemon that the app has closed).

Another possibility would be that the app uses the daemon to access the database. At the moment, that would require an extensive interface. In the future, however, libdeltachat functions will be accessed via JSON-RPC, so an inter-process communication would be a lot easier. I'm not sure though whether such a setup would be fast enough.

What's more, apps that run a daemon had to be unconfined in the past. Probably this will change (or has it already?) with focal though.

@Schlicki2808 Actually, it's me (Lothar). Great to hear that you like the app. Dekko runs a daemon in the background for notifications. There are some technical reasons why this is not so easy for DeltaTouch (let me know if you like to hear the details, it's a little bit complex). Maybe the situation will be different in the future as the use of the library provided by the Delta team that DeltaTouch is based upon will undergo some changes which might make a daemon easier to realize - not sure about that though.

For the time being, notifications depend a little bit whether you're on xenial or on focal. In any case, if background suspension is disabled for DeltaTouch, you will receive notifications if the app is running and in background. In xenial, disabling background suspension can be achieved via UT Tweak Tool. For focal, it can be done via command line (see below), or (as far as I know) a certain git version of UT Tweak Tool has to be build by yourself.

On xenial, if the app is in foreground, you will receive notifications for all accounts that are not the currently selected account (if in chatlist view) or, if you are currently viewing a chat, you will receive notifications for all conversations/accounts except for this specific chat.

On focal, UT currently suppresses any notifications for the app that is currently in foreground, I can't do anything about that.

Disabling background suspension in focal via command line (thanks to Danfro for instructions):

1. Fetch current suspended apps:

gsettings get com.canonical.qtmir lifecycle-exempt-appids

2. Add DeltaTouch to the list (the following assumes that the output of the previous command gave ['com.ubuntu.music'], please adapt to the output of your device):

gsettings set com.canonical.qtmir lifecycle-exempt-appids "['com.ubuntu.music', 'deltatouch.lotharketterer']"

@Ced I can make the text size configurable. Webxdc is not available yet. I'm working on it, but it may take a while.

@domubpkm Hi, saw your post just now. Automatic end-to-end encryption works just as with the official Delta Chat clients. So if there's a Delta user at the other end (using one of the official apps or DeltaTouch), it will be e2e encrypted automatically. If it's just a "normal" email client on the other side, then it won't be encrypted.

Things that I noticed with version 182:

• When using the Music app, there's a frequent clicking/hissing noise and the music skips a few microseconds, similar to listening to a vinyl disc on a grammophone. It's not completely overlaying the music, but has quite a negative impact.
• In phone calls, people sometimes complain that they can barely hear me although I am speaking directly into the mic.
• Volume cannot be changed in phone calls when using headphones via the audio jack (I already reported this above).
• After about half of the reboots, the SIM card (I only have one in slot 1) is not recognized and both slots are shown as empty.
• Sometimes the auto brightness doesn't work after a reboot. This happens in stable, too, with around the same frequency.

The rest (well, what I am using anyway) works quite well, and in my experience is only slightly shakier than stable.

If your camera stays black, you can try

cd
rm -rf .cache/gstreamer-1.0

Worked for me. Thanks to Alfred for posting this solution.

Hi, today i switched to halium-devel (build no. 2021-08-10). Looks quite good, although the camera is not working (screen stays black). Torch works though (I assume I have the old module, then? Don't know as I bought the device second hand).

One more thing I noticed: In a call, the volume cannot be changed when using headphones via the audio jack. Volume control for the standard speaker works.

Thanks for your efforts!