Skip to main content

Are you running #Conversations_im on an Realme or OnePlus devices with stock ROM? Are calls still working for you on version 2.14.2 and above?

Not working would likely manifest itself as a dialog that says "Call not sent" or the operating system opening the default calling app instead of the Conversations UI. Incoming calls would likely be rejected as busy immediately. (There may or may not be other symptoms.)

Please let me know either way and tell me your Android version.

#XMPP

#xmpp #conversations_im

Nicoco reshared this.

in reply to Daniel Gultsch

Daniel Gultsch
Daniel Gultsch
• •

For context: With Conversations 2.14 calls are more tightly integrated into the operating system. This means the OS can ask you what you want to do when a regular phone call comes in while on a Conversations call. (Hang up or reject the incoming one.) It also means the OS controls the audio routing which can help with Bluetooth car integration.

However this means the OS can now break things even though we use standard Android APIs¹.

¹: https://developer.android.com/develop/connectivity/telecom/selfManaged


Build a calling app

Android Developers
in reply to Daniel Gultsch

Daniel Gultsch
Daniel Gultsch
• •
I have a strong hunch that "older" Oppo devices (OnePlus + Realme) have a broken implementation of that particular system API. I’m currently trying to determine how old is old (Android 11? Android 12?) to maybe disable "Call Integration" for that entire family of devices.
in reply to Daniel Gultsch

peturbg
peturbg
• •
other issue: on latest conversations.... From today we will write from f-droid version as they have full programs freedom. There is option called: " channel binding" or what was his name. When I try enable it it comment " incompatible server" do you know what config need be added to work.... I try seek in internet and pasted all my ejabberd.yml to chat got versión 4 and it comment all config is good. This is like, as when
in reply to Daniel Gultsch

Kyva :veenk_logo:
Kyva :veenk_logo:
• •
I run Conversations in OnePlus 7 Pro with /e/ Rom and calls are working fine ​:BlobCat_Flower:​
in reply to Kyva :veenk_logo:

Daniel Gultsch
Daniel Gultsch
• •

@kyva I’m suspecting that only the stock ROMs (colorOS, oxygenOS, what ever it’s called) are broken while third party ROMs (Lineage OS, /e/) work fine.

It raises an interesting question though. Can we put OPPO devices on a black list but not Lineage and /e/. There doesn’t seem to be a standard API for detecting the 'Android Distribution'.

@Kyva :veenk_logo:
in reply to Daniel Gultsch

ndo
ndo
• •
just called my wife using C. 2.15 on a OnePlus with OxygenOS 13. She was using same version of C. on a Oppo phone running ColorOS 13. No issues. Later I'll try to receive instead of calling.
in reply to Daniel Gultsch

Martin
Martin
• •
I received a video and an audio call today on my oneplus 8t running oxygenos android 14. Everything went smooth except the video of the caller froze in the video call but that's not a new issue and I guess this is related to the caller using an apple device.
in reply to Daniel Gultsch

peturbg
peturbg
• •
Hi.... We are affected from this bug " call not set" realme x50 pro 5g stock rom Android 11 and realme 5 pro stock rom latest Android 11. Other realme 5 pro I had custom latest evolution x and latest conversions from f-droid is working. We pay for conversations on Google play but now we can't update it.... Neither use it as United States of America intent block Russia, bir they accept other thing from Russia.
⇧