asked 2019-07-27 18:05:53 +0200
Heads up; I had a working installation of Threema Messenger (3.70) under SFOSX 3 / XPERIA X. With there update to 4.02, voice calls are not working anymore (application crashes when initiating or accepting a calls).
answered 2019-08-02 21:08:05 +0200
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Seems fixed with "Threema 4.1 for Android", at least on my Xperia X and Sailfish 3.1
edit [5 Feb 2020]: I noticed (as @Linus Kasch pointed out above) that calling is non-functional again with Threema 4.22 and Sailfish 3.2. Neither on Xperia X nor on a friend's XA2. Unfortunately I don't know which update caused it. It rings but never connects to the other side.
edit [19 Feb 2020]: I had a chat with Threema Support and sent them log-files by request. However, as soon as I mentioned that I run Threema on AlienDalvik with SailfishOS they told me "we are sorry, we don't support SailfishOS". I pointed towards this thread and that Threema call works with Threema 3.7 and 4.1, but not with 4.0 and 4.2. So lets see if they can solve it although the don't officially support this platform.
edit [26 Feb 2020]: Threema support cannot find the issue in the Logs yet. Does anyone have an idea how to tackle it from SailfishOS side?
edit [03 March 2020]: Some news from Threema support who really tries to help. This applies to the XA2 implementation layer of Android and I translated it from the Support's German answer:
It seems that Sailfish is not able to collect reflexive and relay candidates when collecting ICE-candidates (interactive connectivity establishment) with a STUN/TURN-server. This might be related to the network protocol or the configuration of the network stack. Threema uses the WebRTC library for Threema Calls.
So to me it seems this might also be connected to this issue, which is already tracked by Jolla: https://together.jolla.com/question/202371/threema-web-not-working/
Interestingly, I just made a Threema call via WiFi without problems. Xperia X with SFOS 3.3 and Threema 4.34.
NobodyInPerson ( 2020-07-11 11:02:34 +0200 )editanswered 2020-02-27 16:15:27 +0200
Seems NOT fixed with Threema 4.3 for Android, at least on my Xperia XA2 and Sailfish 3.2.1.20. Sorry for the fake news from before.
Asked: 2019-07-27 18:05:53 +0200
Seen: 1,577 times
Last updated: Mar 03 '20
Could you observe if this is error was triggered by the Sailfish Update to 3.1 or the threema update to 4.02? I have the same issue (Xperia X) but unfortunately both updates came almost simultaneously.
Spark ( 2019-07-27 22:55:44 +0200 )editGood point; no I can't.
Recap:
Because Jolla is not focussing on SFOSX Aliendalvik/Android's support for XPERIA X now. I do not expect any big changes between SFOSX 3.0 and 3.1 of Aliendalvik/Android. A quick look into the current version shows; that the only thing that was changed was; Update cipher suites to support TLSv1.2.
Maybe some one can test it before updating to SFOSX 3.1 but its sounds plausible that the change to Threema 4.02 brings this bug with it.
Leon ( 2019-07-27 23:51:17 +0200 )editExactly the same problem here. It was caused by the Threema 4 update, while running on SFOSX 3.0. I've updated to SFOSX 3.1 after Threema 4 voice calls stopped working.
ty ( 2019-07-29 10:47:34 +0200 )edit- Threema 4.11 (Build 507) works fine with a Jolla 1 and SFOSX 3.1
- Threema 4.2 (Build 514) with a Jolla 1 and SFOSX 3.1 can call and and send audio but wont recive audiostream. "Ton temporär stummgeschaltet wegen Verlust des Audio-Fokus"
- Threema 4.2 (Build 514) and Sony Xperia XA2 and SFOS 3.2.012 cant use Threema-Calls an voice messages are to quite..
Linus Kasch ( 2019-11-25 13:28:20 +0200 )editUnfortunately does Threema get worse on SFOS 3.3. Now even Pictures for Adress-Entries are not able to set anymore. Calls were not possible anymore since SFOS 3.2 and the problem remain on SFOS 3.3 :-(
8sam ( 2020-04-03 23:22:51 +0200 )edit