SR3's BLE loses control after google voice search on Android O device.

[Ralph]

Hi,

We're using SR3 v1.1 for several BLE R/C,and migrating our code from SR3 v1.1  to v1.2 now for mass-production.

last week ,one of our product, set top  box updated to android 8 from android 7.

After the google voice search of the set top box is activated by the remote controller, the remote controller cannot control the set top box, but the device shows that the Bluetooth is still connected.
If the remote controller is re-powered on or waked from sleep, the remote controller and the set-top box Bluetooth are reconnected, the remote controller can control the set-top box, but as long as the voice search is started, uncontrollable situation will happen again.

So we tried SR3v1.1 & v1.2 on Nordic demo board PCA20023 , both of them have the same issue on Android O device.

We look at the log of the remote and find that the following message is displayed after each audio enable:
"warning m_audio: m_audio_process(): WARNING: Cannot allocate audio frame"

Whether it is in the android 7 or android 8 on the box will appear the same message but not every time, but in the android 7 version
Remote control still works after google voice search is performed

Is there any solution for this issue?

Thanks

[Ralph]

Hi, Filip 

What if we use ATVVP instead of HID ? What is ATVVP?  

Can you give a simple explanation, the difference between ATVVP & HID? 

Thanks.

[Filip Kubicz]

Android TV Voice (ATVV) service enables you to use Smart Remote as Bluetooth Low Energy voice input without modifying Android TV host. It should be supported in hosts since Android 8.0.
It can be enabled in SR3 firmware with CONFIG_AUDIO_ATVV_ENABLED.