[roll] Roll fuchsia [bt][avrcp] Set browsed player after browse connection is set up.

After browse connection is set up, the controller sets the browsed
player. If a player is addressed, we set the browsed player to the
addressed player. Otherwise, we set it to a player with the highest
browse capability. The player will be set as browsable if it supports
of browsing.

Browse player is set in the peer not in the controller, so that
different controller instances (i.e. from ControllerService and from
BrowseControllerService) that point to the same peer can have the
already addressed browsed player information.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/830496
Original-Revision: acf79c852ab08bac9cc73f99d23fbb2cd0ecdb50
GitOrigin-RevId: a5a81efbef310ff215cc7ce0da9ff37f5478be79
Change-Id: I18330b1483fdf9ba90f059875e583021521e1510
1 file changed
tree: 581b539dbe5b47c6497a9b056c0e6e01c8cd6f60
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.