piCorePlayer 8.0.0 - Bluetooth Discussion

[paul-]

Possibly something with that chipset is not cooperating. Can you try running the daemon from a ssh session?

sudo pcp-btspeaker-daemon.py

Then post what happens when it crashes.

[Grumpy Bob]

Possibly something with that chipset is not cooperating. Can you try running the daemon from a ssh session?

sudo pcp-btspeaker-daemon.py

Then post what happens when it crashes.

Here goes:

[email protected]:~$ sudo pcp-btspeaker-daemon.py
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/dbus/bus.py", line 177, in activate_name_owner
    return self.get_name_owner(bus_name)
  File "/usr/local/lib/python3.8/site-packages/dbus/bus.py", line 361, in get_name_owner
    return self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
  File "/usr/local/lib/python3.8/site-packages/dbus/connection.py", line 652, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.bluealsa': no such name

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/pcp-btspeaker-daemon.py", line 828, in <module>
    get_connected_devices()
  File "/usr/local/bin/pcp-btspeaker-daemon.py", line 214, in get_connected_devices
    device = dbus_get_pcm_devices()
  File "/usr/local/bin/pcp-btspeaker-daemon.py", line 58, in dbus_get_pcm_devices
    dev_object = bus.get_object('org.bluealsa', '/org/bluealsa')
  File "/usr/local/lib/python3.8/site-packages/dbus/bus.py", line 241, in get_object
    return self.ProxyObjectClass(self, bus_name, object_path,
  File "/usr/local/lib/python3.8/site-packages/dbus/proxies.py", line 250, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/local/lib/python3.8/site-packages/dbus/bus.py", line 182, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/local/lib/python3.8/site-packages/dbus/bus.py", line 277, in start_service_by_name
    return (True, self.call_blocking(BUS_DAEMON_NAME, BUS_DAEMON_PATH,
  File "/usr/local/lib/python3.8/site-packages/dbus/connection.py", line 652, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluealsa was not provided by any .service files
[email protected]:~$

Robert

[paul-]

An error to trap, but bluealsa is not running for some reason on that system. What happens if you run bluealsa from command line.

sudo /usr/local/bin/bluealsa --profile=a2dp-source --profile=a2dp-sink --profile=hsp-ag --profile=hfp-ag

[Grumpy Bob]

An error to trap, but bluealsa is not running for some reason on that system. What happens if you run bluealsa from command line.

sudo /usr/local/bin/bluealsa --profile=a2dp-source --profile=a2dp-sink --profile=hsp-ag --profile=hfp-ag

[email protected]:~$ sudo /usr/local/bin/bluealsa --profile=a2dp-source --profile=a2dp-s
ink --profile=hsp-ag --profile=hfp-ag
Illegal instruction
[email protected]:~$

Robert

[paul-]

Oh that's not good. Can you please confirm. The specific RPI board. (Should be able to Get this on the Diagnostics Page - Raspberry Pi Tab.)

[castalla]

Bt dropouts

In pcp 7 the Bluetooth speaker connections were super solid. I'm finding the same connections in 8 are often subject to dropouts, seems more prevalent with earbuds...

Occurs with both inbuilt bt or a bt dongle.

[paul-]

There is much less latency (buffering) in the system. We might have to add some latency back into the system.

[castalla]

There is much less latency (buffering) in the system. We might have to add some latency back into the system.

Would that be via an update to the bt routines?

[paul-]

Would that be via an update to the bt routines?

Yes it would. I just need to try to recreate the issue, since I've really not noticed a problem

[castalla]

Yes it would. I just need to try to recreate the issue, since I've really not noticed a problem

I have tried a Creative headset - no issues.

Both Urbanista Stockholm and Sounpeats trubuds suffer dropouts (not present in 7)

[paul-]

Do either of these support aac? I have added aac support in bluealsa, however I don't have any headsets that use aac to test it?

Grumpy Bob,
Update the bluetooth modules from the bluetooth page, that should correct the Invalid Instruction issue. I guess I forgot to build with proper compile flags for older boards.

Paul

[castalla]

Do either of these support aac? I have added aac support in bluealsa, however I don't have any headsets that use aac to test it?

Grumpy Bob,
Update the bluetooth modules from the bluetooth page, that should correct the Invalid Instruction issue. I guess I forgot to build with proper compile flags for older boards.

Paul

Not sure. Updated and dropouts (plus clicks) are still present (eg. Tidal aac stream)

[paul-]

Check the bluetooth logs. It should show the codec being used.

[castalla]

Check the bluetooth logs. It should show the codec being used.

Would that be:

TRANSPORT:hfpag

?

[paul-]

That is a handsfree profile, that is likely connecting, then disconnecting. Need to see more of the logs.