summaryrefslogtreecommitdiffstats
path: root/binding-bluetooth
diff options
context:
space:
mode:
authorsaman <mahmoudi.saman1@gmail.com>2020-11-29 17:25:42 +0330
committerScott Murray <scott.murray@konsulko.com>2021-01-05 14:26:46 +0000
commitb4ebff5a25cf1346b9ea86379a8d25275bb64a32 (patch)
tree40d38cca5ff22f24612b2968870c97828338bd2f /binding-bluetooth
parent494ce56f88fc377e703896723fdd80c26aa64550 (diff)
More attention to bluez player propertieskoi_10.93.0koi_10.92.0koi/10.93.0koi/10.92.010.93.010.92.0
It is possible the bluez player does not assign to default bluez player (player0) and assign to other player such as playerN. For fixing this issue we can access to correct bluez player from "Player" property in "org.bluez.MediaControl1" interface. By reading Player property on "org.bluez.MediaControl1" interface we could access to player path and ther is not need to define a const string variable like "player0"! Bug-AGL: SPEC-3722 Signed-off-by: saman <mahmoudi.saman1@gmail.com> Change-Id: I8a5f948c511bbb61ccc67db09ad17aeb02ab5bd1
Diffstat (limited to 'binding-bluetooth')
0 files changed, 0 insertions, 0 deletions