Thats a pity, because it is not possible to order the case together with the phone.
However I'm going to order the pinephone.
I am using a nexus 5 too.
At 17.21 I send a message to a friend of mine with converse.js. She uses conversations.
I see two messages in converse.js: the message I wrote and a OMEMO warning, both at the same time.
While this is something I don't understand, I could read her answer which is shown only once with no warning.
But it is usable so far, in fact it is the only usable xmpp client on ubports. So thank you very much for your work.
I have reinstalled converse.js and deleted all app data. Then logged in and wrote a message to my wife.
I could read this message on both converse.js and conversations.
Then my wife wrote an answer. I could read it on converse.js, but not on conversations.
I wrote a message again (readable on both) and then I could read the answer on both clients.
Now I add gajim. I had to trust the other device. After that most of the messages arrived and could be read on all devices.
Seemed to work now.
Well, I have no idea what I did wrong the weeks before.
@PhoenixLandPirat Kaidan is not really usable:
The textfield is hidden when writting a message. Sometimes a message gets lost. Files cannot be send. The communication is not synchronize with other clients, ...
@advocatux I wrote a message to the loqui developer. They told me, that it seems to be a ubports problem, loquiim itself works fine.
I did not try Movim yet.
3G is not an option as I will then have no network.
I restarted and then I was able to make calls. However, that cannot be the reason, since I start anew almost every day anyway (development channel).
The stable channel would be an option. The last time I tried it, the user interface was very sluggish, almost unusable.
some further investigations about the double messages:
(1) If I send multiple messages to one person quit fast after each other, the I get only one omemo warning.
(2) Although warning and message have the same time, they do not arrive at the same time.
When I send the message the warning is displayed later although the same time as for the message is shown.
Could it be that the warning is caused by a read confirmation or something similar ?