Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Android and iOS apps v24.6.0 not able to enable camera #15581

Open
2 of 11 tasks
Franco-Sparrow opened this issue Feb 7, 2025 · 13 comments
Open
2 of 11 tasks

Android and iOS apps v24.6.0 not able to enable camera #15581

Franco-Sparrow opened this issue Feb 7, 2025 · 13 comments

Comments

@Franco-Sparrow
Copy link

Franco-Sparrow commented Feb 7, 2025 •
edited
Loading

What happened?

Can't open phone camera once inside in the room, with Android app and iOS app. Desktop browsers and phone browsers works just fine.

Cellphone camera on Android and iOS cant be enabled when using server with internal auth:

Image

Cellphone camera on Android and iOS app works on Jitsi Meet public server (different kind of auth config):

Image

Hi Mr. @saghul

I saw that you guys fixed the problem with this issue, not present on recent version of the server. I am using same configuration files, but different host and latest stable Jitsi Meet server.

Platform

  • Chrome (or Chromium based)
  • Firefox
  • Safari
  • Other desktop browser
  • Android browser
  • iOS browser
  • Electron app
  • Android mobile app
  • iOS mobile app
  • Custom app using a mobile SDK

Browser / app / sdk version

Android: 24.6.0 build 18537858 / iOS: 24.06.0 build 1731676000

It works on older android version: 23.4.0 build 23400002. Probably older iOS app version should work as well, but dont know where to download older versions for iOS.

Relevant log output

Logs after joining from android app:


tail -f /var/log/jitsi/jicofo.log
Jicofo 2025-02-07 00:36:02.536 INFO: [82] ConferenceIqHandler.handleConferenceIq#87: Conference request for room [email protected], from [email protected]/AjOtVy0fut-6
Jicofo 2025-02-07 00:36:04.238 INFO: [82] [xmpp_connection=client] XmppProvider.discoverFeatures#286: Discovered features for [email protected]/7e2cc5f5 in 1 ms.
Jicofo 2025-02-07 00:36:04.239 INFO: [82] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] JitsiMeetConferenceImpl.onMemberJoined#750: Member joined:7e2cc5f5 stats-id=Pansy-fBH region=null audioMuted=true videoMuted=true role=PARTICIPANT isJibri=false isJigasi=false isTranscriber=false, room=main
Jicofo 2025-02-07 00:36:04.239 INFO: [82] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] JitsiMeetConferenceImpl.inviteChatMember#822: Creating participant 7e2cc5f5 with features=[XMPP_CAPS, JSON_SOURCES, RECEIVE_MULTIPLE_STREAMS, REMB, SOURCE_NAMES, SSRC_REWRITING_V1, TCC, VISITORS_V1, RTX, JINGLE, DTLS, JINGLE_RTP, AUDIO, VIDEO, SCTP, JINGLE_ICE, RAYO]
Jicofo 2025-02-07 00:36:04.241 INFO: [82] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] ColibriV2SessionManager.<init>#80: Using org.jitsi.jicofo.bridge.SingleMeshTopologyStrategy
Jicofo 2025-02-07 00:36:04.242 INFO: [82] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] JitsiMeetConferenceImpl.inviteChatMember#822: Creating participant 0737cd4c with features=[XMPP_CAPS, JSON_SOURCES, RECEIVE_MULTIPLE_STREAMS, REMB, SOURCE_NAMES, SSRC_REWRITING_V1, TCC, VISITORS_V1, E2EE, RTX, JINGLE, DTLS, JINGLE_RTP, AUDIO, VIDEO, SCTP, JINGLE_ICE, RAYO]
Jicofo 2025-02-07 00:36:04.244 INFO: [101] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] ColibriV2SessionManager.allocate#280: Allocating for 7e2cc5f5
Jicofo 2025-02-07 00:36:04.245 INFO: [102] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] ColibriV2SessionManager.allocate#280: Allocating for 0737cd4c
Jicofo 2025-02-07 00:36:04.248 INFO: [101] BridgeSelectionStrategy.select#48: Selected initial bridge Bridge[jid=[email protected]/c2807b64-9042-41bd-af2f-7fdf36c87497, version=2.3.204-g26cd91bd, relayId=null, region=null, stress=0.01] with reported stress=0.0055666889334224 for participantProperties=ParticipantProperties(region=null, visitor=false) using strategy SingleBridgeSelectionStrategy
Jicofo 2025-02-07 00:36:04.249 INFO: [101] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] ColibriV2SessionManager.allocate#326: Selected c2807b64-9042-41bd-af2f-7fdf36c87497 for $7e2cc5f5 (visitor=false, session exists: false)
Jicofo 2025-02-07 00:36:04.250 INFO: [102] BridgeSelectionStrategy.select#61: Existing bridge does not have a relay, will not consider other bridges.
Jicofo 2025-02-07 00:36:04.251 INFO: [102] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] ColibriV2SessionManager.allocate#326: Selected c2807b64-9042-41bd-af2f-7fdf36c87497 for $0737cd4c (visitor=false, session exists: true)
Jicofo 2025-02-07 00:36:04.359 INFO: [101] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac participant=7e2cc5f5] ParticipantInviteRunnable.doInviteOrReinvite#388: Sending session-initiate to: [email protected]/7e2cc5f5 sources={jvb=[audio=[2685939356], video=[4043846474], groups=[]]}
Jicofo 2025-02-07 00:36:04.360 INFO: [102] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac participant=0737cd4c] ParticipantInviteRunnable.doInviteOrReinvite#388: Sending session-initiate to: [email protected]/0737cd4c sources={jvb=[audio=[2685939356], video=[4043846474], groups=[]]}
Jicofo 2025-02-07 00:36:05.553 INFO: [102] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac participant=0737cd4c] Participant$JingleRequestHandlerImpl.onSessionOrTransportAccept#429: Received session-accept
Jicofo 2025-02-07 00:36:05.554 INFO: [102] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] ColibriV2SessionManager.updateParticipant#559: Updating 0737cd4c with transport=org.jitsi.xmpp.extensions.jingle.IceUdpTransportPacketExtension@69380e22, sources=[audio=[], video=[], groups=[]]
Jicofo 2025-02-07 00:36:08.240 INFO: [101] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac participant=7e2cc5f5] Participant$JingleRequestHandlerImpl.onSessionOrTransportAccept#429: Received session-accept
Jicofo 2025-02-07 00:36:08.241 INFO: [101] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] ColibriV2SessionManager.updateParticipant#559: Updating 7e2cc5f5 with transport=org.jitsi.xmpp.extensions.jingle.IceUdpTransportPacketExtension@93a4c8e, sources=[audio=[3025668286], video=[], groups=[]]
Jicofo 2025-02-07 00:36:08.241 INFO: [101] [room=[email protected] meeting_id=6dbdccc6-ed63-44fb-8c3e-1f9a753e9eac] JitsiMeetConferenceImpl.acceptSession#1381: Accepted initial sources from 7e2cc5f5: [audio=[3025668286], video=[], groups=[]]

Reproducibility

  • The problem is reproducible on meet.jit.si

More details?

I am hosting my own server. Server URL is the follow one:

https://zoum-mu.virtalus.com/

Jitsi Meet server version packages:

dpkg -l | grep jitsi
ii  jitsi-meet                       2.0.10008-1                                                      all          WebRTC JavaScript video conferences
ii  jitsi-meet-prosody               1.0.8384-1                                                       all          Prosody configuration for Jitsi Meet
ii  jitsi-meet-turnserver            1.0.8384-1                                                       all          Configures coturn to be used with Jitsi Meet
ii  jitsi-meet-web                   1.0.8384-1                                                       all          WebRTC JavaScript video conferences
ii  jitsi-meet-web-config            1.0.8384-1                                                       all          Configuration for web serving of Jitsi Meet
ii  jitsi-videobridge2               2.3-204-g26cd91bd-1                                              all          WebRTC compatible Selective Forwarding Unit (SFU)
ii  lua-basexx                       0.4.1-jitsi1                                                     all          baseXX encoding/decoding library for Lua
ii  lua-cjson:amd64                  2.1.0.10-jitsi1                                                  amd64        JSON parser/encoder for Lua

Host OS version:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.5 LTS
Release:        22.04
Codename:       jammy
@Franco-Sparrow Franco-Sparrow changed the title Android and iOS apps not able to enable camera on meet Android and iOS apps v24.6.0 not able to enable camera Feb 7, 2025
@saghul
Copy link
Member

saghul commented Feb 7, 2025

Can you extract device logs with adb logcat for example?

@Franco-Sparrow
Copy link
Author

Hi Mr. @saghul

This is the logfile for latest apk version 24.6.0-18537858, from PlayStore (camera not working):

jitsi-meet-apk-24.6.0-18537858.zip

@Franco-Sparrow
Copy link
Author

This is the logfile for apk version 24.5.0-24050002, from F-Droid (camera not working):

jitsi-meet-apk-24.5.0-24050002.zip

@Franco-Sparrow
Copy link
Author

This is the logfile for older version 23.4.0-23400002, from F-Droid (camera is working):

jitsi-meet-apk-23.4.0-23400002.zip

@Franco-Sparrow
Copy link
Author

Hi

May I have a follow up on this Sir? is it confirmed an issue on app side?

Thanks in advance for your support

@saghul
Copy link
Member

saghul commented Feb 10, 2025

I checked what we changed across versions and I can't spot anything relevant. The camera driver seems to fail and that's why video gets muted:

02-07 13:33:04.050 22528  6053 E CameraCaptureSession: Session 0: Exception while stopping repeating: 
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): cancelRequest:620: Camera 1: Error clearing streaming request: Function not implemented (-38)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.hardware.camera2.CameraManager.throwAsPublicException(CameraManager.java:1426)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.hardware.camera2.impl.ICameraDeviceUserWrapper.cancelRequest(ICameraDeviceUserWrapper.java:99)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.hardware.camera2.impl.CameraDeviceImpl.stopRepeating(CameraDeviceImpl.java:1409)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.hardware.camera2.impl.CameraCaptureSessionImpl.close(CameraCaptureSessionImpl.java:587)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.hardware.camera2.impl.CameraCaptureSessionImpl$2.onDisconnected(CameraCaptureSessionImpl.java:798)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.hardware.camera2.impl.CameraDeviceImpl$7.run(CameraDeviceImpl.java:288)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.Handler.handleCallback(Handler.java:942)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.Handler.dispatchMessage(Handler.java:99)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.Looper.loopOnce(Looper.java:211)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.Looper.loop(Looper.java:300)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.HandlerThread.run(HandlerThread.java:67)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: Caused by: android.os.ServiceSpecificException: cancelRequest:620: Camera 1: Error clearing streaming request: Function not implemented (-38) (code 10)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.Parcel.createExceptionOrNull(Parcel.java:3025)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.Parcel.createException(Parcel.java:2995)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.Parcel.readException(Parcel.java:2978)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.os.Parcel.readException(Parcel.java:2920)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.hardware.camera2.ICameraDeviceUser$Stub$Proxy.cancelRequest(ICameraDeviceUser.java:648)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	at android.hardware.camera2.impl.ICameraDeviceUserWrapper.cancelRequest(ICameraDeviceUserWrapper.java:97)
02-07 13:33:04.050 22528  6053 E CameraCaptureSession: 	... 9 more
02-07 13:33:04.050 22528  6053 I org.webrtc.Logging: Camera2Session: Stop internal
02-07 13:33:04.051 22528  6053 I org.webrtc.Logging: SurfaceTextureHelper: stopListening()

The original request succeeds a few lineas above, but dies quickly after.

I don't know what could've caused that.

@Franco-Sparrow
Copy link
Author

OK. Weell the bug is confirmed right? This is happening not just for my phone, but for others too, different phones, different OS.

For now my solution is to use old app version. Maybe you could check whats different on these versions:

  • 23.4.2-23400002 ✅
  • 24.2.2-24020201 ✅
  • 24.3.0-24030001 ❌
  • 24.5.0-24050001 ❌

@saghul
Copy link
Member

saghul commented Feb 10, 2025

Those are f-droid app versions, which we don't build or support.

Have you tried the play store beta?

@Franco-Sparrow
Copy link
Author

We all tried with app available on PlayStore (not beta) and that one is not available on F-Droid. Is not working for apps available on PlayStore nor iOS Store.

@saghul
Copy link
Member

saghul commented Feb 10, 2025

That is very strange.

Are you able to reproduce the problem when connecting to meet.jit.si?

What versions of the software are you running?

You can sign up for the betas here: https://jitsi.github.io/handbook/docs/releases#apps-beta

@Franco-Sparrow
Copy link
Author

Franco-Sparrow commented Feb 10, 2025 •
edited
Loading

All these questions are at the begining of the issue :)

I will try with beta app version and let you know.

@saghul
Copy link
Member

saghul commented Feb 10, 2025

Oops sorry! I go through many of them in a day and forget 😅

@jonasjancarik
Copy link

Funnily enough, for me the Android app always joins a call with the camera enabled even if I disable it before joining... I'll open an issue for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@saghul @jonasjancarik @Franco-Sparrow