Android Error

[dabit3]

I've been trying to debug this for a while but can't come up with anything.

Everything works great on iOS, but in Android, after creating a call, I get what looks like an infinite loop stating the following errors:

01-04 17:54:42.714 8477-9330/com.channelmobile D/PJSIP: 17:54:42.714          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.715 8477-9330/com.channelmobile D/PJSIP: 17:54:42.715          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.715 8477-9330/com.channelmobile D/PJSIP: 17:54:42.715          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.715 8477-9330/com.channelmobile D/PJSIP: 17:54:42.715          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.715 8477-9330/com.channelmobile D/PJSIP: 17:54:42.715          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.715 8477-9330/com.channelmobile D/PJSIP: 17:54:42.715          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.715 8477-9330/com.channelmobile D/PJSIP: 17:54:42.715          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.716 8477-9330/com.channelmobile D/PJSIP: 17:54:42.716          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.716 8477-9330/com.channelmobile D/PJSIP: 17:54:42.716          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.718 8477-9330/com.channelmobile D/PJSIP: 17:54:42.718          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.719 8477-9330/com.channelmobile D/PJSIP: 17:54:42.719          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.719 8477-9330/com.channelmobile D/PJSIP: 17:54:42.719          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.720 8477-9330/com.channelmobile D/PJSIP: 17:54:42.720          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.721 8477-9330/com.channelmobile D/PJSIP: 17:54:42.721          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.721 8477-9330/com.channelmobile D/PJSIP: 17:54:42.721          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.721 8477-9330/com.channelmobile D/PJSIP: 17:54:42.721          speex  warning: No playback frame available (your application is buggy and/or got xruns)
01-04 17:54:42.724 8477-9329/com.channelmobile D/PJSIP: 17:54:42.724          speex !warning: Auto-filling the buffer (your application is buggy and/or got xruns)

This gets thrown when the Twilio.connect({To: '+61234567890'}); method is called in javascript.

Any idea what may be causing this?

[dabit3]

@rogchap any idea what may be going on here?

[dabit3]

Also, @fabriziomoscon if you have a minute, I would appreciate your help with this, thank you!

[fabriziomoscon]

Does it affect the telephone call at all? Or are you just concerned about the errors in the log? I remember I was also noticing massive blocks of error coming from PJSIP, but somehow they were not affecting my calls.

I have completely moved my Android implementation to https://github.com/hoxfon/react-native-twilio-programmable-voice, because for my app it doesn't make sense having the call receiver working only when the app is opened. And the Client SDK has that big limitation, because it doesn't use push notification to notify about the received calls.
I haven't had a chance to build the ios part of my library yet - which I would be more than happy to delegate to more iOS competent developers - but I believe that moving to the Programmable Voice SDK is also recommended by Twilio.

I am sorry I couldn't help more

[dabit3]

@fabriziomoscon No, it does not affect the call itself, but once the call is finished and hung up, the app crashes when trying to initiate a second call.

I will definitely take a look at the twilio-programmable-voice-sdk, that looks really promising.

Thanks so much for your help!

[fabriziomoscon]

I remember while using this library I also have experienced few annoying crashes on hangup. I don't think I found the reason though.

[dabit3]

Ah, very useful info, I appreciate your quick responses today.

[jzhan-canva]

Hi @dabit3 , I'm having the same issue, did you move to react-native-twilio-programmable-voice already?

[dabit3]

@zhantx yes I did!