voxeet/voxeet-sdk-android-audio

Manage and improve Android Audio lifecycle (Routes, headsets, ...)

voxeet-sdk-android-audio's Issues

Crash on latest Audio version

When having bluetooth disconnecting or reconnecting multiple times (possible system lifecycle), the bluetooth implementation of the library could crash in the audio v2.

Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.os.Handler.removeCallbacks(java.lang.Runnable)' on a null object reference
       at com.voxeet.audio2.manager.BluetoothHeadsetDeviceManager.onNewBluetoothServiceConnectivity(BluetoothHeadsetDeviceManager.java:127)
       at com.voxeet.audio2.manager.BluetoothHeadsetDeviceManager.lambda$6wqK44RXdYIe7s4vy9u-gr34RVo(BluetoothHeadsetDeviceManager.java)
       at com.voxeet.audio2.manager.-$$Lambda$BluetoothHeadsetDeviceManager$cGuJelgeSC4-1iRlROCOl6EjarU.apply(-.java:4)
       at com.voxeet.audio2.manager.bluetooth.BluetoothHeadsetServiceListener$1.onServiceDisconnected(BluetoothHeadsetServiceListener.java:48)
       at android.bluetooth.BluetoothHeadset$3.handleMessage(BluetoothHeadset.java:1206)
       at android.os.Handler.dispatchMessage(Handler.java:107)
       at android.os.Looper.loop(Looper.java:214)
       at android.app.ActivityThread.main(ActivityThread.java:7356)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)

The expected behaviour is to simply avoid the mechanism to be resending the command

dlopen failed: library "libomp.so" not found

hi there,
i download this project and try to compile but than i got this issue dlopen failed: library "libomp.so" not found
Can you guide me how i can fix this. i try to google but did not understand the issue. thanks

sending a disconnect for a connecting device should cancel the call

When connecting to a bluetooth device, the process can take up some seconds. However, calling disconnect on this device in this timeframe is not cancelling the action.

It could be an improvement when calling both quickly when dealing with connecting to a conference and then leaving it "early"

Samsung Fold 3 control volume keeps being call mode

Using the dolby.io app, the phone call mode is still activated after leaving the conference. However, checking the code shows that the normal mode is properly called.

Expected behavior:

Calling connect to the device with DeviceType.NORMAL_MEDIA mode should be enough (!)

Actual behavior:

Calling connect to the device with DeviceType.NORMAL_MEDIA mode is keeping the call mode in the app

Notes:

However calling manually,

AudioFocusManager focusManager = new AudioFocusManager(AudioFocusMode.MEDIA);
MediaMode mode = new MediaMode(audioManager, focusManager);
return mode.abandonAudioFocus(); //default behavior is switching to abandon focus + normal
//and resolving the promise of course

To be investigated :

• what makes the NORMAL_MEDIA's connect not working on the Samsung device (following a previously call to the SPEAKER_MODE connect)
• fixing the SPEAKER_MODE's disconnect to call the abandon focus ? (need to check for implications)
• fixing NORMAL_MEDIA

This will likely bring a non breaking API modification but a behavioural modifications. The libraries using this audio sdk (like the Dolby.io SDK) will likely need an update to integrate this fix/improvement