It takes 10 to 30 seconds to establish a connection, when I call another user for a video call via XMPP. I tried different devices. clients and servers. As soon as the connection is settled, I see no limitations in the video conference and the video streams at full resolution. My last test was with GrapheneOS on a Pixel 6a and Conversation as client both in the same Wireless LAN and the Users had accounts on the same server. How can I find out the cause for the long delay? How can I make it faster?

I have searched quite a bit but still javen't manged to find a general Jabber client that supports video calling. There are a few that support sending video files though.

The company I'm working for is using a Jabber server which is kind of old. It doesn't support SSL/TLS with SASL but only plain old SSL. I tried a dozen of Jabber clients for Android but none of them supports this setup. Are there any alternatives?

I noticed that after each message when OTR is enabled, 2 little ticks or crosses appear in the message bubble. Sometimes they change color from black to white. What is the meaning of these indicators? I think it something to do with message delivery and /or to flag the recipient has read the message, but I would appreciate a definitive explanation!

I want my received SMS to automagically be forwarded via Jabber (XMPP), so I can read them on my current PC. I don't want to send SMS from my computer, though I would not mind the feature as an extra bonus. How can I achieve this?

When I set up my jabber.org account in Chatsecure it doesn't connect. Another account on jabber.ccc.de works.

When running a Jabber client what happens (or what should happen) when switching networks (or when losing connectivity and the GSM/UMTS modem reconnects)? Can a mobile Android Jabber client (e.g. Jabiru ) be smart about such situations? Worst case scenario I can imagine: Client does not care, TCP (over TLS) connection to the Jabber server is lost, the Jabber status (displayed remotely) is bogus and there is a time window where messages (from buddies) are lost. I observed such a worst case for example with a stock Jabber client on a Laptop using an unreliable UMTS connection. When using a Laptop I can easily shield my Jabber session like this: * connect via autossh to a system with a stable network connection and directly run screen -Rd * start a console Jabber client inside screen Thus, when losing the mobile internet connection the connection to the Jabber server is still fine. And autossh automatically reconnects and re-attaches to the running screen session when a new mobile connection is up. Is a setup similar to this necessary when using Jabber on an Android device? Or are there Jabber protocol extensions for mobile clients that actually help to avoid losing messages etc. in network on/off situation (while being connected to a Jabber server)?

Gtalk 1.3 doesn't support multiple accounts: it just connects with the main one, with no apparent way to switch it. Upgrading to hangouts technically works, but it doesn't even bother to display user online status, so I'd rather have a real chat app. Do I have any other option, running on 2.3.7 / cm 7.2.0? If it isn't an official gtalk version, I'd appreciate if at least it was as good, integrated and non-bloated as it is, such as: • integrated with address book • downloads whole conversation (as opposite of just displaying new messages) • plain and simple

I'm disappointed that Google Hangouts is going away from XMPP. If I download the "Hangouts (replaces Talk)" app on my Galaxy Nexus (Google Nexus 3), will I be able to go back to Google Talk, if needed? Is there a way to keep Google Talk? Or is there a way to communicate with people who use Google Hangouts through Google Talk or XMPP?

I'm not an Android user, but I have an Android user as a contact in my XMPP roster (instant messaging). I noticed that his presence switches from "Away" to "Offline" rotatory when his smartphone is not in use (but constantly connected to his private WLAN). See for example the following status changes for his account from tonight (while he was sleeping, so no activity with the phone):

[00:05:13] Status: Offline
[00:06:02] Status: Away: AutoStatus (idle)
[00:18:14] Status: Offline
[00:21:17] Status: Away: AutoStatus (idle)
[00:35:15] Status: Offline
[00:36:32] Status: Away: AutoStatus (idle)
[00:50:47] Status: Offline
[00:51:52] Status: Away: AutoStatus (idle)
[01:00:08] Status: Offline
[01:01:14] Status: Away: AutoStatus (idle)
[01:15:13] Status: Offline
[01:16:31] Status: Away: AutoStatus (idle)
[01:25:13] Status: Offline
[01:25:44] Status: Away: AutoStatus (idle)
[01:40:13] Status: Offline
[01:41:00] Status: Away: AutoStatus (idle)
[01:49:14] Status: Offline
[01:50:14] Status: Away: AutoStatus (idle)
[02:15:17] Status: Offline
[02:17:32] Status: Away: AutoStatus (idle)
[02:31:19] Status: Offline
[02:32:48] Status: Away: AutoStatus (idle)
[02:52:20] Status: Offline
[02:54:04] Status: Away: AutoStatus (idle)
[03:07:52] Status: Offline
[03:09:18] Status: Away: AutoStatus (idle)
[03:22:52] Status: Offline
[03:24:34] Status: Away: AutoStatus (idle)
[03:37:55] Status: Offline
[03:39:48] Status: Away: AutoStatus (idle)
[03:53:26] Status: Offline
[03:55:03] Status: Away: AutoStatus (idle)
[04:08:57] Status: Offline
[04:10:18] Status: Away: AutoStatus (idle)
[04:23:57] Status: Offline
[04:25:32] Status: Away: AutoStatus (idle)
[04:39:28] Status: Offline
[04:40:47] Status: Away: AutoStatus (idle)
[04:54:29] Status: Offline
[04:56:04] Status: Away: AutoStatus (idle)
[05:09:30] Status: Offline
[05:11:19] Status: Away: AutoStatus (idle)
[05:24:31] Status: Offline
[05:26:34] Status: Away: AutoStatus (idle)

He uses the XMPP client [Jabiru](http://jabiru.info/) . He can't explain why this is happening; he doesn't find any settings that could be responsible for this. I googled if it is a known bug and found this [statement (in German)](http://www.android-hilfe.de/sonstige-apps-widgets/1870-jabiru-jabber-client.html#post90077) in a forum thread, which could be translated to: > Nice client, but it will probably not keep you connected when inactive, "thanks" to Androids memory management Is this true? Could it be a problem with Android itself and not this particular XMPP app? How can this be fixed? The XMPP status should stay at "Away" (and not disconnect&reconnect again and again) when the smartphone is inactive.

I've tried several, and so far I can't get one that will just work with my work jabber + conferencing (jabber 'rooms'). They all seem mostly clunky. Does anyone have a rec that has worked well for them for me to try?