Signal-android: One phone is silent in WebRTC call

Created on 2 Feb 2017  路  24Comments  路  Source: signalapp/Signal-Android

I have:


Bug description

Repeatedly established a call with video calls enabled on both devices. Everything works fine, except that on the Android 4 device, one can't hear anything.

Steps to reproduce

  • Establish call between both devices (doesn't matter who)

Actual result: Can't hear a thing on Android 4 device (video functionality works, and I can hear just fine on Android 6 device).

(Edit: Regular, non-WebRTC Signal calls work just fine with the same devices.)

Device info 1

Device: Samsung S III Mini
Android version: 4.1.2
Signal version: 3.29.1

Link to debug log

https://gist.github.com/2c2abf3abb689ca0a4db2607a54fe84a

Device info 2

Device: Motorola Moto G 2014
Android version: 6.0.1 (CM 13)
Signal version: 3.29.1

Link to debug log

https://gist.github.com/2b7b458444a78db6d9f6028333e4088e

Most helpful comment

Just tested the 3.31.0 branch and can confirm that this issue is fixed on my old ICS device!

All 24 comments

Cyanogenmod -> Stock ROM comes out silent.

This is very similar to my experience. I have this problem with all my Signal Calls coming from an Cyanogenmod Device. I tried to give some useful information here: #4382 .

What happens if you put your S III Mini on speaker? Can you hear something?

As far as I can tell this is not Signal specific. I would say it has something to do with CM. Although they claim they are not doing anything different than Stock ROM regarding voice/microphone handling.

However there is an entire thread (with a lot of postings :( ) about this issue. take a look.
https://forum.xda-developers.com/galaxy-s5/development/how-to-microphone-gain-increase-s5-t3190613

If someone like to tackle this, I will do my best to help.

What happens if you put your S III Mini on speaker? Can you hear something?

No, I can't hear anything on speakers as well.

I have this problem with all my Signal Calls coming from an Cyanogenmod Device.

"Oldschool" Signal calls still work perfectly between the same two devices, I haven't had problems ever.

Somewhere in the other issues it was mentioned that a headset could help. Because the mic jack is used rather than the regular.

If that doesn't help I'd say similar symptoms but different cause.

Well, as I said, regular Signal calls work just fine. And since everything else is held constant, I believe in _my_ case the WebRTC implementation is responsible.

@AlfonsoMuskedunder do you have the ability to build/test from source?

I'm afraid I don't.

Moreover, unfortunately I think I could test a new build only by the end of next week, not before. But if it was possible that someone provided me with a build, I'd be happy to test it then.

I have one shitty Ice Cream Sandwich device (4.0.4) that is silent in webrtc calls but works with legacy redphone calls.

@2-4601 wonderful, could you see if the moxie/mode_in_communication branch changes anything for that device?

I'll have to hit the gym now but I'll test that when I get back

With these changes the ICS device is still silent during a webrtc call. By silent I mean that I cannot hear anything via it's ear piece speaker nor the speaker phone.

Also now I'm hearing an annoying staccato noise on the other device during the call. And if I speak on the ICS device's microphone I do hear my own voice on the other device but my voice has a very low volume, it's barely audible behind the noise, and it has a chipmunk effect (high pitch and fast speed).

So now the microphone seems to work on the ICS device, but there are serious issues with the sound quality. I have tested three different devices with this ICS device. All combinations behave the same.

Sample audio of the noise: https://dropfile.to/cvyZNMW

Edit:
Log from ICS: https://gist.github.com/anonymous/bc93847979767914688375758dcb0d8d

dang. can you try the apprtc APK and see if you get audio with it on this device?
https://mega.nz/#!YtVUwACL!1sIjpZAsmYAnn8nN0wGvIAVURzUZpcmW7hi9QPEZG5I

That app does not seem to work with ICS?

$ adb install -r AppRTCMobile.apk 
[100%] /data/local/tmp/AppRTCMobile.apk
    pkg: /data/local/tmp/AppRTCMobile.apk
Failure [INSTALL_FAILED_OLDER_SDK]

@2-4601 ah too bad

@AlfonsoMuskedunder can you test and see if you get audio with the AppRTC apk when you get a chance?
https://mega.nz/#!YtVUwACL!1sIjpZAsmYAnn8nN0wGvIAVURzUZpcmW7hi9QPEZG5I

I just installed and tested the App with both devices. The outcome is absolutely the same. Video and microphone work on both devices, but the Samsung device's speaker is dead.

@AlfonsoMuskedunder bummer, that's the webrtc reference implementation, so it'll probably be hard for me to do better than that, but i'll try

@moxie0 How about I file an issue at AppRTC's GitHub repo? This could potentially take work off of you, and other WebRTC apps might benefit as well, who knows.

(And if you agree: Do you think their developers could learn something from the _Signal_ log files above? Otherwise I'd have to install Android Studio first etc.)

I'm having a similar issue with one device. Seems like the microphone isn't working in Signal for this device as it is the same in WebRTC and ZRTP calls. cat.log

@digititus If your microphone is affected, it's probably a different bug. The one in this here thread affects speakers in very old Android 4 devices.

In order to keep things tidy (and raise the chance that your issue will be adressed) I suggest you file a separate issue with your debug logs.

Android 4.1 is a mess compared to how Android 6 and 7 are and we need to either upgrade to better devices or install a custom ROM on these 5 year old devices. I see people using Android 6.0 on their GalaxyS3 and Signal works fine.

Just because Samsung has abandoned these devices after 2 years doesn't mean you should continue to suffer with it.

I also suggest that Signal stop supporting Android 2.3 devices and instead make 4.4 the minimum.

Dropping support might be ok if calling has never worked on some older marginal device/Android API level. However in my case the ICS device does work with RedPhone calls but not with WebRTC calls. (But personally I couldn't care less if that device stopped working with Signal because I don't even use it.)

@moxie0 It seems that the AppRTCMobile.apk you uploaded above is outdated. I have tried the latest version of the demo app, and now it works on the Samsung device!

There could be lots of reasons for that, but one might lie in recent changes to the WebRTC libraries, no? (And who knows, maybe these changes might benefit Signal as well. Just dreaming here.)

@AlfonsoMuskedunder thanks good to know, I'll update to M57 in the 3.31.0 release and see if that helps

Just tested the 3.31.0 branch and can confirm that this issue is fixed on my old ICS device!

closing with the assumption that M57 did fix things

Was this page helpful?
0 / 5 - 0 ratings