Add a property to enable the New AVRCP Profile (1/2)
You can now use the new AVRCP Profile by setting persist.bluetooth.enablenewavrcp to true. Also fix a misundestanding with connection_handler.cc. AVRCP Control callbacks return a null address when disconnecting. Bug: 68854188 Test: Check to see that the profile is used when property is true and is not used when property is false. Change-Id: I4aa285c6bf009716cc80a80b813ba0acd3d8f9d8 (cherry picked from commit ce1a2b3f8d44a017c13a55b5e53abb51886297ad) Merged-In: I4aa285c6bf009716cc80a80b813ba0acd3d8f9d8
Showing
- system/binder/Android.bp 2 additions, 0 deletionssystem/binder/Android.bp
- system/binder/android/bluetooth/IBluetoothAvrcpTarget.aidl 29 additions, 0 deletionssystem/binder/android/bluetooth/IBluetoothAvrcpTarget.aidl
- system/bta/Android.bp 5 additions, 1 deletionsystem/bta/Android.bp
- system/bta/av/bta_av_aact.cc 7 additions, 1 deletionsystem/bta/av/bta_av_aact.cc
- system/bta/av/bta_av_act.cc 7 additions, 0 deletionssystem/bta/av/bta_av_act.cc
- system/btif/avrcp/avrcp_service.h 6 additions, 1 deletionsystem/btif/avrcp/avrcp_service.h
- system/profile/avrcp/connection_handler.cc 2 additions, 6 deletionssystem/profile/avrcp/connection_handler.cc
Loading
Please register or sign in to comment