Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Android element does not support audio/video calls
See original GitHub issueDescribe the bug The client on android does not connect to peers when calling video/audio. it is stuck on
To Reproduce Steps to reproduce the behavior:
- Go to a private conv with someone
- Click on call
- wait for answer
- expect connection, stuck on “call connecting”
Expected behavior calls going through
Screenshots dont have a ss
Smartphone (please complete the following information):
- Device: Lenovo ZUK Z2 Pro
- OS: Android 10
Additional context
- App version and store 1.0.12 google play
- Homeserver: hosted homeserver
- synapse running on a debian 10 vps with 1 public facing ipv4 address, no firewall.
- synapse installed from source, running manually venv
- turn server installed from debian repos
here are successive logs from turn, first one is from “android to desktop app on windows 10”, second is from desktop app on windows 10 to desktop app on manjaro
all apps on all platforms are the latest as of 21 jan 2021
The android client shows "Element does not handle events of type 'm.call.select_answer'"
Turn server failed call log:
======================================LOG BEGIN======================================
806: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:62626
806: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:62627
806: session 000000000000000031: TLS/TCP socket disconnected: CLIENT_IP_ADDRESS:62626
806: session 000000000000000031: usage: realm=<server-fqdn>, username=<>, rp=0, rb=0, sp=0, sb=0
806: session 000000000000000031: closed (2nd stage), user <> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:5349, remote CLIENT_IP_ADDRESS:62626, reason: TLS/TCP socket buffer operation error (callback)
806: session 000000000000000032: TLS/TCP socket disconnected: CLIENT_IP_ADDRESS:62627
806: session 000000000000000032: usage: realm=<server-fqdn>, username=<>, rp=0, rb=0, sp=0, sb=0
806: session 000000000000000032: closed (2nd stage), user <> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:5349, remote CLIENT_IP_ADDRESS:62627, reason: TLS/TCP socket buffer operation error (callback)
812: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:53085
812: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:53086
812: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:53088
812: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:53087
812: session 001000000000000025: realm <server-fqdn> user <>: incoming packet message processed, error 401: Unauthorized
812: IPv4. Local relay addr: SERVER_IP_ADDRESS:50473
812: session 001000000000000025: new, realm=<server-fqdn>, username=<1611230317:@voiptest:server-fqdn>, lifetime=600
812: session 001000000000000025: realm <server-fqdn> user <1611230317:@voiptest:server-fqdn>: incoming packet ALLOCATE processed, success
857: session 001000000000000023: TCP socket closed remotely CLIENT_IP_ADDRESS:53085
857: session 001000000000000023: usage: realm=<server-fqdn>, username=<>, rp=0, rb=0, sp=0, sb=0
857: session 001000000000000023: closed (2nd stage), user <> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:3478, remote CLIENT_IP_ADDRESS:53085, reason: TCP connection closed by client (callback)
857: session 001000000000000024: TCP socket closed remotely CLIENT_IP_ADDRESS:53086
857: session 001000000000000024: usage: realm=<server-fqdn>, username=<>, rp=0, rb=0, sp=0, sb=0
857: session 001000000000000024: closed (2nd stage), user <> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:3478, remote CLIENT_IP_ADDRESS:53086, reason: TCP connection closed by client (callback)
857: session 000000000000000033: TCP socket closed remotely CLIENT_IP_ADDRESS:53088
857: session 000000000000000033: usage: realm=<server-fqdn>, username=<>, rp=0, rb=0, sp=0, sb=0
857: session 000000000000000033: closed (2nd stage), user <> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:3478, remote CLIENT_IP_ADDRESS:53088, reason: TCP connection closed by client (callback)
882: session 001000000000000025: refreshed, realm=<server-fqdn>, username=<1611230317:@voiptest:server-fqdn>, lifetime=0
882: session 001000000000000025: realm <server-fqdn> user <1611230317:@voiptest:server-fqdn>: incoming packet REFRESH processed, success
882: session 001000000000000025: TCP socket closed remotely CLIENT_IP_ADDRESS:53087
882: session 001000000000000025: usage: realm=<server-fqdn>, username=<1611230317:@voiptest:server-fqdn>, rp=3, rb=292, sp=3, sb=304
882: session 001000000000000025: closed (2nd stage), user <1611230317:@voiptest:server-fqdn> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:3478, remote CLIENT_IP_ADDRESS:53087, reason: TCP connection closed by client (callback)
882: session 001000000000000025: delete: realm=<server-fqdn>, username=<1611230317:@voiptest:server-fqdn>
=======================================LOG END=======================================
turn server successful call log:
======================================LOG BEGIN======================================
1052: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:53100
1052: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:53102
1052: session 000000000000000034: realm <server-fqdn> user <>: incoming packet message processed, error 401: Unauthorized
1052: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:53101
1052: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:53103
1052: IPv4. Local relay addr: SERVER_IP_ADDRESS:58925
1052: session 000000000000000034: new, realm=<server-fqdn>, username=<1611230317:@voiptest:server-fqdn>, lifetime=600
1052: session 000000000000000034: realm <server-fqdn> user <1611230317:@voiptest:server-fqdn>: incoming packet ALLOCATE processed, success
1055: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:62646
1055: IPv4. tcp or tls connected to: CLIENT_IP_ADDRESS:62647
1055: session 001000000000000027: realm <server-fqdn> user <>: incoming packet message processed, error 401: Unauthorized
1055: session 001000000000000028: realm <server-fqdn> user <>: incoming packet message processed, error 401: Unauthorized
1055: IPv4. Local relay addr: SERVER_IP_ADDRESS:57654
1055: session 001000000000000027: new, realm=<server-fqdn>, username=<1611227971:@superpower:server-fqdn>, lifetime=600, cipher=ECDHE-RSA-AES256-GCM-SHA384, method=TLSv1.2
1055: session 001000000000000027: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet ALLOCATE processed, success
1055: IPv4. Local relay addr: SERVER_IP_ADDRESS:54156
1055: session 001000000000000028: new, realm=<server-fqdn>, username=<1611227971:@superpower:server-fqdn>, lifetime=600, cipher=ECDHE-RSA-AES256-GCM-SHA384, method=TLSv1.2
1055: session 001000000000000028: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet ALLOCATE processed, success
1055: session 001000000000000027: peer 192.168.73.1 lifetime updated: 300
1055: session 001000000000000027: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000027: peer 192.168.202.1 lifetime updated: 300
1055: session 001000000000000027: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000027: peer 192.168.1.103 lifetime updated: 300
1055: session 001000000000000027: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000027: peer 192.168.137.1 lifetime updated: 300
1055: session 001000000000000027: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000027: peer SERVER_IP_ADDRESS lifetime updated: 300
1055: session 001000000000000027: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000028: peer 192.168.73.1 lifetime updated: 300
1055: session 001000000000000028: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000028: peer 192.168.202.1 lifetime updated: 300
1055: session 001000000000000028: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000028: peer 192.168.1.103 lifetime updated: 300
1055: session 001000000000000028: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000028: peer 192.168.137.1 lifetime updated: 300
1055: session 001000000000000028: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1055: session 001000000000000028: peer SERVER_IP_ADDRESS lifetime updated: 300
1055: session 001000000000000028: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1056: session 000000000000000034: peer 192.168.137.249 lifetime updated: 300
1056: session 000000000000000034: realm <server-fqdn> user <1611230317:@voiptest:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1056: session 000000000000000034: peer SERVER_IP_ADDRESS lifetime updated: 300
1056: session 000000000000000034: realm <server-fqdn> user <1611230317:@voiptest:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1056: session 000000000000000034: peer SERVER_IP_ADDRESS lifetime updated: 300
1056: session 000000000000000034: realm <server-fqdn> user <1611230317:@voiptest:server-fqdn>: incoming packet CREATE_PERMISSION processed, success
1056: session 001000000000000027: peer SERVER_IP_ADDRESS lifetime updated: 600
1056: session 001000000000000027: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet CHANNEL_BIND processed, success
1056: session 000000000000000034: peer SERVER_IP_ADDRESS lifetime updated: 600
1056: session 000000000000000034: realm <server-fqdn> user <1611230317:@voiptest:server-fqdn>: incoming packet CHANNEL_BIND processed, success
1070: session 000000000000000035: TCP socket closed remotely CLIENT_IP_ADDRESS:53101
1070: session 000000000000000035: usage: realm=<server-fqdn>, username=<>, rp=0, rb=0, sp=0, sb=0
1070: session 000000000000000035: closed (2nd stage), user <> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:3478, remote CLIENT_IP_ADDRESS:53101, reason: TCP connection closed by client (callback)
1070: session 001000000000000026: TCP socket closed remotely CLIENT_IP_ADDRESS:53100
1070: session 000000000000000034: refreshed, realm=<server-fqdn>, username=<1611230317:@voiptest:server-fqdn>, lifetime=0
1070: session 000000000000000034: realm <server-fqdn> user <1611230317:@voiptest:server-fqdn>: incoming packet REFRESH processed, success
1070: session 000000000000000034: TCP socket closed remotely CLIENT_IP_ADDRESS:53102
1070: session 000000000000000034: usage: realm=<server-fqdn>, username=<1611230317:@voiptest:server-fqdn>, rp=720, rb=57692, sp=713, sb=82612
1070: session 000000000000000034: closed (2nd stage), user <1611230317:@voiptest:server-fqdn> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:3478, remote CLIENT_IP_ADDRESS:53102, reason: TCP connection closed by client (callback)
1070: session 000000000000000034: delete: realm=<server-fqdn>, username=<1611230317:@voiptest:server-fqdn>
1070: session 000000000000000034: peer SERVER_IP_ADDRESS deleted
1070: session 000000000000000034: peer 192.168.137.249 deleted
1070: session 000000000000000036: TCP socket closed remotely CLIENT_IP_ADDRESS:53103
1070: session 000000000000000036: usage: realm=<server-fqdn>, username=<>, rp=0, rb=0, sp=0, sb=0
1070: session 000000000000000036: closed (2nd stage), user <> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:3478, remote CLIENT_IP_ADDRESS:53103, reason: TCP connection closed by client (callback)
1070: session 001000000000000026: usage: realm=<server-fqdn>, username=<>, rp=0, rb=0, sp=0, sb=0
1070: session 001000000000000026: closed (2nd stage), user <> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:3478, remote CLIENT_IP_ADDRESS:53100, reason: TCP connection closed by client (callback)
1071: session 001000000000000027: refreshed, realm=<server-fqdn>, username=<1611227971:@superpower:server-fqdn>, lifetime=0, cipher=ECDHE-RSA-AES256-GCM-SHA384, method=TLSv1.2
1071: session 001000000000000027: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet REFRESH processed, success
1071: session 001000000000000027: TLS/TCP socket disconnected: CLIENT_IP_ADDRESS:62646
1071: session 001000000000000027: usage: realm=<server-fqdn>, username=<1611227971:@superpower:server-fqdn>, rp=738, rb=85003, sp=717, sb=57980
1071: session 001000000000000027: closed (2nd stage), user <1611227971:@superpower:server-fqdn> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:5349, remote CLIENT_IP_ADDRESS:62646, reason: TLS/TCP socket buffer operation error (callback)
1071: session 001000000000000027: delete: realm=<server-fqdn>, username=<1611227971:@superpower:server-fqdn>
1071: session 001000000000000027: peer SERVER_IP_ADDRESS deleted
1071: session 001000000000000027: peer 192.168.73.1 deleted
1071: session 001000000000000027: peer 192.168.1.103 deleted
1071: session 001000000000000027: peer 192.168.137.1 deleted
1071: session 001000000000000027: peer 192.168.202.1 deleted
1071: session 001000000000000028: refreshed, realm=<server-fqdn>, username=<1611227971:@superpower:server-fqdn>, lifetime=0, cipher=ECDHE-RSA-AES256-GCM-SHA384, method=TLSv1.2
1071: session 001000000000000028: realm <server-fqdn> user <1611227971:@superpower:server-fqdn>: incoming packet REFRESH processed, success
1071: session 001000000000000028: TLS/TCP socket disconnected: CLIENT_IP_ADDRESS:62647
1071: session 001000000000000028: usage: realm=<server-fqdn>, username=<1611227971:@superpower:server-fqdn>, rp=13, rb=1660, sp=8, sb=684
1071: session 001000000000000028: closed (2nd stage), user <1611227971:@superpower:server-fqdn> realm <server-fqdn> origin <>, local SERVER_IP_ADDRESS:5349, remote CLIENT_IP_ADDRESS:62647, reason: TLS/TCP socket buffer operation error (callback)
1071: session 001000000000000028: delete: realm=<server-fqdn>, username=<1611227971:@superpower:server-fqdn>
1071: session 001000000000000028: peer SERVER_IP_ADDRESS deleted
1071: session 001000000000000028: peer 192.168.73.1 deleted
1071: session 001000000000000028: peer 192.168.1.103 deleted
1071: session 001000000000000028: peer 192.168.137.1 deleted
1071: session 001000000000000028: peer 192.168.202.1 deleted
=======================================LOG END=======================================
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
HTML5 audio tag is not working in Android - Stack Overflow
According to html5test.com Android 4 only supports mp3 in the audio tag.
Read more >Introducing Native Matrix VoIP with Element Call!
Yup, we've just launched our beta of Element Call, a brand new and incredibly simple web-based conferencing app. Element Call has been built ......
Read more >AudioManager - Android Developers
An audio/video chat or VoIP call is established and its audio is being redirected to another device. ... AudioAttributes) : offload playback not...
Read more >Fix sound or video issues - Android - Google Duo Help
Fix video or sound issues on a call · Make sure the device's camera and microphone are not physically blocked. · Check that...
Read more >Cross-browser audio basics - Developer guides | MDN
If the <audio> element is not supported then <audio> and <source> will be ... Autoplaying audio (and video) is usually really annoying.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As far as I can see, this is because of a Element Web bug (https://github.com/vector-im/element-web/issues/16239) which is now fixed on develop.element.io and will be released momentarily.
If I display the source of the event (from the android element client), I have: “version”: 1