Posts: 14
Joined: Jan 2016
Reputation:
0
Or at the very least, it is not providing enough control over where to send audio to.
Posts: 1,600
Joined: Dec 2009
Reputation:
124
2016-01-23, 13:10
(This post was last modified: 2016-01-23, 13:11 by Sam.Nazarko.)
OSMC's A2DP streaming is experimental, and the test thread I created clearly states that.
When you have issues streaming you need to provide logs, let us know the dongle you're using (dmesg), and if possible try another dongle. It also helps to know which device you're streaming from, as some differ in AVRCP implementation.
You don't pair or trust in Kodi at all. OSMC has a Kodi add-on that is doing this withthe network manager via DBus.
You should read the official testing thread and follow that. I'm not sure that you've actually installed the experimental a2dp-app-osmc via SSH. If you haven't done this, you'll never get A2DP working.
This is not Kodi's job. It's not an application's role to control the networking stack in such a way.
Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
Thanks for clarifying, Sam.
Posts: 14
Joined: Jan 2016
Reputation:
0
Back on topic, Kodi's future is with the OSMC distro. I love Kodi on my Raspberry Pi 2. I'm not talking about this anymore here, now that I know the Bluetooth part of Kodi is an OSMC addon provided by OSMC. I'll bug them. (Lock Post Please)