I've redone the test and sent the logs using the "Send Logs"
function (apparently per email to email@example.com or so,
hope you got them).
Do you have specific suggestions which codecs to disable, or
should I just "randomly" (or systematically) test all codecs
We need to try not full band codec like PCMU and this should be
enough. Please let me know if PCMU or PCMA works on your device.
Today it worked fine with a call from Jitsi on a Galaxy Tab 3 to
Desktop Jitsi, with both audio and video working fine (without any
changes to the codec configuration). Not sure what the problem was
the first time, but it is great that this worked!
Yes, it is the former. You may be right, it sounds at least
very plausible to me that this is some problem with the proximity
sensor ... could be. I've not yet had the possibility to redo
this and send logs, but I will try it when I can.
I'm not sure if I understand. Does it happen just when the call is
started or after the video is enabled with the button ? Can you
also try selecting camera with "MediaRecorder" next to it's name ?
It starts as soon as the call is made. When calling from the mobile
device the screen even goes black while still ringing.
We're currently on the track of issue with AndroidCamera and some
other with proximity sensor. The latter is when the screen goes
black just after the call screen appears(it detects false positive
NEAR distance). We hope to fix both of them soon.
I've sent some logs via email now, hopefully they arrived and are useful.
OpenPGP: 901C 5216 0537 1D2A F071 5A0E 4D94 6EED 04F7 CF52
Namecoin: id/domob -> https://nameid.org/?name=domob
To go: Mon-Pri
On 2014-02-05 20:59, Paweł Domas wrote:
On Wed, Feb 5, 2014 at 6:58 PM, Daniel Kraft <firstname.lastname@example.org> wrote: