nextcloud / nextcloud/talk-android
Problems with voice and video calls!
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
- Open the Nextcloud Talk app on an Android device (e.g., Xiaomi Redmi Note 12 Pro 5G).
- Initiate an audio or video call.
- Wait for the call to connect.
Expected behaviour
The call should connect successfully and the connection should be stable. For context, the exact same setup works perfectly fine when making calls from Windows, Linux, and iOS devices.
Actual behaviour
The call either completely fails to connect or connects with extremely poor video/audio quality. This issue appears to be strictly limited to the Android operating system.
Talk app
Talk app version: Latest
Custom Signaling server configured: yes
Custom TURN server configured: yes
Custom STUN server configured: yes
Client Device
Device model: Xiaomi Redmi Note 12 Pro 5G
Operating system: Android
Microphone available: yes
Camera available: yes
Battery optimization: Disabled (unrestricted priority set for the app)
Browser name/version: N/A (Using the native Android app)
Server configuration
Operating system: Debian 12
Web server: Nginx
Database: (Not specified)
PHP version: 8.2
Nextcloud Version: Latest
Additional Context / Feature Request
Since it is difficult to troubleshoot this without logs, it would be extremely helpful if a feature could be added to the Talk app allowing users to view and export application logs directly from the app's interface.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing an audio and video call in the native Android Talk app on the reported Xiaomi Redmi Note 12 Pro 5G setup, using the configured signaling, TURN, and STUN servers. Compare the failed or degraded call with the working Windows, Linux, and iOS cases, and collect application logs; done means the Android call behavior is explained and a reproducible fix or diagnostic result is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100