-
-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No video on call after update on v15.1.1 #2704
Comments
thank you, i just reproduced this. |
Nope( |
I tried to do a video call on 15.1.1 yesterday and wasn't able to get incoming video working. Any workaround yet? |
We will have a closer look at this issue soon! |
Thank you! |
I'm affected by this bug too. Pixel 6 / Android 13. |
Still broken with 15.1.2. |
Сonfirm |
Same issue here, Samsung Galaxy S21. |
Unfortunately this was not fixed for 15.1.2. And just to make sure: |
Well in my case Android App to WebApp is affected too. WebUser does not see the Android Video. Not sure of the other way around at the moment. Aside from that i think it's a bug in need of fixing more sooner than later. :) App is pretty much useless currently.
Am 20. Februar 2023 11:36:18 MEZ schrieb Marcel Hibbe ***@***.***>:
…Unfortunately this was not fixed for 15.1.2.
We hope to get this fixed soon! I tagged it with 16.0 for now but if we are able to fix it soon it will be a good reason for a 15.1.3!
And just to make sure:
This still "only" affects calls from android app to android app, right?
I can reproduce this, while disabling and enabling video again solves it as a workaround.
Would be helpful to have some info if this workaround also solves it or if there is still no video afterwards..
|
No, even if the video call was from a laptop to Android device, or Android to Android device.
Of course! But disabling and enabling the video does not help( |
Today i'm update my HPB for Talk. |
Thanks for testing. I wonder by the way what the scope of that bug is. Are only a handful of people affected? I tend to doubt that.
Am 25. Februar 2023 15:39:14 MEZ schrieb Akrobs ***@***.***>:
…Today i'm update my HPB for Talk.
I'm Installed new [16.0.0 RC1] Talk on my Samsung S10e and recheck it again...
Bad news, still no video, but! If i'm share screen to Android device...I'm see a screen of remote laptop, if switch to webcam - black screen(((
Disabling and enabling the video no effect.
|
I just tested again for calls web->phone with HPB. |
Just to get things straight. This bug only happens with an enabled HPB? Is that right?
Am 27. Februar 2023 12:52:55 MEZ schrieb Marcel Hibbe ***@***.***>:
…I just tested again for calls web->phone with HPB.
Sometimes it works, sometimes it fails (video not shown on android).
We are aware of the urgency and will take care of it as soon as the workload permits!
|
Yes, that's right. (Android 12, Nextcloud talk 15.1.2, Nextcloud Hub 3 (25.0.4) and Spreed version 15.0.4 here, latest HPB release.) |
I’m also affected (Nextcloud AIO v4.6.2, Nextcloud Talk v15.1.2 from Google Playstore). Tested with variouos combinations of internal/external desktop/laptop and Android devices (Android 6–12), desktops using different Linux and Windows variants. In all cases, the desktops work fine and can also see the Android video, but the Android devices never show the desktop’s video but a blank screen instead. On the Android device itself, the small image from Android’s own camera(s) gets shown. Same result when using the Talk QA. Note: On the same Android devices, using a browser (tested Firefox & Chrome) and going to a shared call link of my instance works fine! Spreed config: {
"apps": {
"spreed": {
"installed_version": "15.0.4",
"types": "dav,prevent_group_restriction",
"project_access_invalidated": "1",
"enabled": "yes",
"turn_servers": "***REMOVED SENSITIVE VALUE***",
"signaling_servers": "***REMOVED SENSITIVE VALUE***",
"has_reference_id": "yes",
"signaling_token_privkey_es256": "***REMOVED SENSITIVE VALUE***",
"signaling_token_pubkey_es256": "***REMOVED SENSITIVE VALUE***",
"signaling_ticket_secret": "***REMOVED SENSITIVE VALUE***"
}
}
} |
Downgrading Janus to 0.13.4 is more than a workaround than a fix. I think we'll need a upstream fix of Nextcloud Talk to work with the current version of Janus. Using an outdated version is not really an option IMHO. |
As far as I know is janus 0.x still maintained so it is fine to use that as long as it still gets maintenance which is the case. |
Indeed that’s the case. Janus is currently maintaining 2 versions/branches: 0.x is the single stream version, while 1.x is the multistream version. So just judging from the versioning it seems that 0.x is outdated, while it is not at this time. While I agree it makes sense to make sure Talk is working with 1.x as well in the future, at this point 0.x is the only supported version. |
@szaimen, this issue is solved using Janus 0.x branch but this other issue is still present even with the right Janus version #2704 (comment) |
Is there something preventing this change to be upstreamed if it fixes the issue? Support for Janus 1.x is in my opinion necessary for talk-android since only the Android app doesn't work with Janus 1.x while the iOS app and the website both work completely fine. Users shouldn't have to use an outdated version of janus - even if it's still maintained. |
Hi @PhilDevProg, I can't speak about iOS app, but I've tested the web app and I can confirm that is incompatible with Janus 1.x. In fact, I've discovered the incompatibility doing some debugging on the web app. EDIT: |
All, |
Nextcloud AIO V6.5 < actually rolled back the janus version int the signaling container. Still have to disable and re-enable the camera if the call is between two Android devices, but at least working. Before switching to AIO I used my own HPB stanadlone server and observed the same behavior. The tldr is dont use the 1.x version. |
Any updates on this? |
In my experience, both the website and the iOS app work fine. No lag or other issues. Only the Android app doesn't work at all. |
Hello everyone, so this issue is really not getting addressed, is it? If so, this should at least be mentioned somewhere prominently in the talk admin documentation. Else everyone who installs the HPB with current packages will run into this problem with just the talk android client while every other client works fine and bang their heads against the wall until they eventually find this thread. And yes, while technically the 0.x-branch of Janus might still be maintained, it is clearly called "legacy" on their website (even the domain for it has the word legacy in it, they make it veery clear it is l e g a c y software -> https://janus-legacy.conf.meetecho.com/). Kind of disappointing, not gonna lie. |
It will be addressed, once we have the expertise and had the chance to update all clients (iOS, Android, Web, Desktop) before hand. Only afterwards we can release server update bringing this in, otherwise the old clients will similarly fail. |
I'm not quite sure what you mean by this. All other clients except Android already seem to work well with Janus 1.x, as stated repeatedly in this thread. Granted, when I say "work" I mean it from an end user perspective, as in when i make a video call, I can see video and hear audio. I am currently running the HPB installed with the Sunweaver setup script, the installed Janus version is
And with this, audio and video calling from browser to browser, from desktop client to browser, from iOS client to browser, from desktop client to iOS client, and all three of of those combined, works fine. But bring an Android client into the session, and it receives no video signal. Receiving and sending audio as well as sending video works from Android as well. What is the difference between all other clients and the Android client that prevents it to work with the multichannel Janus? And couldn't the proposed change here be at least a temporary fix to get the Android client to be at least at feature parity with all other clients? There might very well be underlying issues in the back end that I am not aware of that need to be addressed to make it really "work" work in a technical sense, but as a user having the core component of the Nextcloud Talk app behave as advertised (on the homepage of the parent project no less) on all supported client devices should in my opinion be of higher priority as it apparently is. And please, don't take this the wrong way. Nextcloud is a great project and it has made my life considerably easier by being super flexible, feature rich, fast and easy to use. All that is missing for me now to have a complete cooperation and communication platform is this thing. And over the last year this thread has basically been my browser homepage, hoping for progress on the matter. And after seeing it being added to milestones only to then be removed again multiple times now, kind of reminds me how I feel every time i check if there is a new release date for The Winds of Winter. |
The bug that I had to toggle the camera on android is how I came here. Problem is still there. While it's good to hear that this is already an improvement, and the turing video off an on again is a workaround; this is still high amount of friction for a core functionality. |
PR #3670 is closed, but nextcloud/talk-android latest release 18.0.1, Can you tell me what version the fix will be in? |
Requiring Talk 19 and Nextcloud 29 |
The fix for spreed was backported in 28 nextcloud/spreed#11667 NC 29 seem far away ! We have some issues with 28 and our users complain, we need to fix everything before a new upgrade on our server. Thank you ! |
I have 5 phones on Android 13 and they all have the same no video when connected. Turning it off and on helps, but it's not a panacea. On Android 10 there is another problem. When you try to open a chat, the application restarts. NextCloud 28.0.5 |
Steps to reproduce
Try to call with video to other mobile
Expected behaviour
If i'm calling no incoming video on my device (S10e)
Actual behaviour
I'm revert on 15.1 version and all works fine.
Device brand and model
Samsung S10e
Android version
10
Nextcloud Talk app version
16.0.0
Nextcloud server version
26.0.1
Talk version
17.0.0RC4
Custom Signaling server configured
Yes (specify version in Additional Information)
Custom TURN server configured
Yes
Custom STUN server configured
Yes
Android logs
No response
Server log
No response
Additional information
Janus ver. 1.1.4
Coturn ver. 4.6.2
Nats ver. 2.9.12
Signaling ver. 1.1.2
The text was updated successfully, but these errors were encountered: