Home of the Squeezebox™ & Transporter® network music players.
Page 34 of 37 FirstFirst ... 243233343536 ... LastLast
Results 331 to 340 of 368
  1. #331
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    679
    OK. I'll see if I can spin up a VM on my Win10 laptop.

    But meanwhile I've now found that BT seems to be completely hosed on that PCP. It won't even power up the BT controller now.

    Turning the BT Controller power on...

    I've removed BT and reinstalled to no avail.

    Show Bluetooth logs
    [ INFO ] cat $BT_LOG

    Restarted multiple times etc. Has Win11 royally screwed it? Time to restore a backup image?

  2. #332
    Junior Member
    Join Date
    Oct 2022
    Posts
    2

    Hilfe pcp

    Hi,

    du sprichst Deutsch richtig?
    Kann man hier irgendwie privat schreiben?
    Brńuchte Hilfe mit der Bluetooth Verbindung.


    Quote Originally Posted by carsten_h View Post
    Sorry, but I can only answer in English (or German if you like).
    All the BT 5.x sticks I saw have only drivers for Windows, not for Linux and not for macOS. I also saw a few of them are creating only a new Audio output which is using BT 5.0 then and not creating a Bluetooth device inside the Windows PC.
    I also tried to have one BT sender in my house for LMS and now I am using a Pi Zero W which is placed on the first floor. It is working fine in the basement and the attic. If the TV is not running I also have good reception in the garden. But at the TV there is also a bluetooth sender which is destroing the bluetooth signal of the Pi Zero W.
    Also there is a big difference in the Bluetooth headsets. I tested one from Teufel (German manufacturer) which is only usable 3m around the Pi. Then I tested a Soundcore Q30 and a Sennheiser HD 350BT and both of them are working without a problem 15m around the Pi.

  3. #333
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    679
    After trying out Win11 which I thought had messed up my existing tabet BT pairing, I decided to do an image restore. After that the tablet worked fine.

    Then before trying out Win11 again tonight I thought it prudent to update BT. How wrong I was!
    First of all my tablet would no longer connect to PCP. So I deleted the BT pairing on the tablet and did a Forget on PCP.
    Then I re-paired the tablet with PCP, it reconnected but now there is no music playing to be heard.

    Do the logs make any sense?

    First of all the BT update logs:

    Code:
    [ INFO ] Updating pCP Bluetooth Extensions...
    [ INFO ] Checking for Updates from: https://repo.picoreplayer.org/repo
    
    [ INFO ] Checking: pcp-bt8.tcz                              Update Required.
    [ INFO ] Gathering Dependancies:  pcp-bt8.tcz bluez-alsa.tcz glibc_add_lib.tcz glib2.tcz gamin.tcz libelf.tcz pcre.tcz bzip2-lib.tcz gcc_libs.tcz ncurses.tcz libbluetooth.tcz bluez.tcz dbus.tcz expat2.tcz libSM.tcz libICE.tcz libX11.tcz libxcb.tcz libXau.tcz libXdmcp.tcz libudev.tcz libical.tcz icu.tcz bluetooth-5.10.77-pcpCore-v7l.tcz firmware-rpi-bt.tcz sbc.tcz readline.tcz ell.tcz libasound.tcz alsa-modules-5.10.77-pcpCore-v7l.tcz pcp-libfdk-aac.tcz libldac.tcz libopenaptx.tcz bluez-tools.tcz dbus-python3.8.tcz dbus-glib.tcz python3.8.tcz gdbm.tcz liblzma.tcz openssl.tcz ca-certificates.tcz sqlite3.tcz py3.8gobject-mini.tcz gobject-introspection.tcz python3.8-evdev.tcz python3.8-urllib3.tcz
    [ INFO ] Checking: alsa-modules-5.10.77-pcpCore-v7l.tcz     Extension version Matches
    [ INFO ] Checking: bluetooth-5.10.77-pcpCore-v7l.tcz        Extension version Matches
    [ INFO ] Checking: bluez-alsa.tcz                           Update Required.
    
    [ INFO ] Downloading: bluez-alsa.tcz                        OK
    [ INFO ] Validating MD5's of new extensions
    [ INFO ] Checking: bluez-tools.tcz                          Extension version Matches
    [ INFO ] Checking: bluez.tcz                                Extension version Matches
    [ INFO ] Checking: bzip2-lib.tcz                            Extension version Matches
    [ INFO ] Checking: ca-certificates.tcz                      Update Required.
    
    [ INFO ] Downloading: ca-certificates.tcz                   OK
    [ INFO ] Validating MD5's of new extensions
    [ INFO ] Checking: dbus-glib.tcz                            Extension version Matches
    [ INFO ] Checking: dbus-python3.8.tcz                       Extension version Matches
    [ INFO ] Checking: dbus.tcz                                 Extension version Matches
    [ INFO ] Checking: ell.tcz                                  Extension version Matches
    [ INFO ] Checking: expat2.tcz                               Extension version Matches
    [ INFO ] Checking: firmware-rpi-bt.tcz                      Update Required.
    
    [ INFO ] Downloading: firmware-rpi-bt.tcz                   OK
    [ INFO ] Validating MD5's of new extensions
    [ INFO ] Checking: gamin.tcz                                Extension version Matches
    [ INFO ] Checking: gcc_libs.tcz                             Extension version Matches
    [ INFO ] Checking: gdbm.tcz                                 Extension version Matches
    [ INFO ] Checking: glib2.tcz                                Extension version Matches
    [ INFO ] Checking: glibc_add_lib.tcz                        Extension version Matches
    [ INFO ] Checking: gobject-introspection.tcz                Extension version Matches
    [ INFO ] Checking: icu.tcz                                  Extension version Matches
    [ INFO ] Checking: libICE.tcz                               Extension version Matches
    [ INFO ] Checking: libSM.tcz                                Extension version Matches
    [ INFO ] Checking: libX11.tcz                               Extension version Matches
    [ INFO ] Checking: libXau.tcz                               Extension version Matches
    [ INFO ] Checking: libXdmcp.tcz                             Extension version Matches
    [ INFO ] Checking: libasound.tcz                            Extension version Matches
    [ INFO ] Checking: libbluetooth.tcz                         Extension version Matches
    [ INFO ] Checking: libelf.tcz                               Extension version Matches
    [ INFO ] Checking: libical.tcz                              Extension version Matches
    [ INFO ] Checking: libldac.tcz                              Update Required.
    
    [ INFO ] Downloading: libldac.tcz                           OK
    [ INFO ] Validating MD5's of new extensions
    [ INFO ] Checking: liblzma.tcz                              Extension version Matches
    [ INFO ] Checking: libopenaptx.tcz                          Update Required.
    
    [ INFO ] Downloading: libopenaptx.tcz                       OK
    [ INFO ] Validating MD5's of new extensions
    [ INFO ] Checking: libudev.tcz                              Extension version Matches
    [ INFO ] Checking: libxcb.tcz                               Extension version Matches
    [ INFO ] Checking: ncurses.tcz                              Extension version Matches
    [ INFO ] Checking: openssl.tcz                              Update Required.
    
    [ INFO ] Downloading: openssl.tcz                           OK
    [ INFO ] Validating MD5's of new extensions
    [ INFO ] Checking: pcp-libfdk-aac.tcz                       Extension version Matches
    [ INFO ] Checking: pcre.tcz                                 Extension version Matches
    [ INFO ] Checking: py3.8gobject-mini.tcz                    Extension version Matches
    [ INFO ] Checking: python3.8-evdev.tcz                      Extension version Matches
    [ INFO ] Checking: python3.8-urllib3.tcz                    Extension version Matches
    [ INFO ] Checking: python3.8.tcz                            Extension version Matches
    [ INFO ] Checking: readline.tcz                             Extension version Matches
    [ INFO ] Checking: sbc.tcz                                  Extension version Matches
    [ INFO ] Checking: sqlite3.tcz                              Extension version Matches
    
    [ INFO ] Downloading: pcp-bt8.tcz                           OK
    [ INFO ] Validating MD5's of new extensions
    
    [ INFO ] Done checking for updates
    
    [ INFO ] Reboot is required to complete update.
    [ INFO ] Reboot Required to finish update

  4. #334
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    679
    (post too long)

    Then the BT logs::
    Code:
    10-18 19:13 BST DEBUG    PCM Devices found dbus.Dictionary({dbus.ObjectPath('/org/bluealsa/hci0/dev_C0_3D_03_2E_FE_58/a2dpsnk/source'): dbus.Dictionary({dbus.String('Device'): dbus.ObjectPath('/org/bluez/hci0/dev_C0_3D_03_2E_FE_58', variant_level=1), dbus.String('Sequence'): dbus.UInt32(0, variant_level=1), dbus.String('Transport'): dbus.String('A2DP-sink', variant_level=1), dbus.String('Mode'): dbus.String('source', variant_level=1), dbus.String('Format'): dbus.UInt16(33296, variant_level=1), dbus.String('Channels'): dbus.Byte(2, variant_level=1), dbus.String('Sampling'): dbus.UInt32(44100, variant_level=1), dbus.String('Codec'): dbus.String('SBC', variant_level=1), dbus.String('Delay'): dbus.UInt16(150, variant_level=1), dbus.String('SoftVolume'): dbus.Boolean(False, variant_level=1), dbus.String('Volume'): dbus.UInt16(32639, variant_level=1)}, signature=dbus.Signature('sv'))}, signature=dbus.Signature('oa{sv}'))
    10-18 19:13 BST INFO        Device: dev_C0_3D_03_2E_FE_58, connected with a2dp
    10-18 19:14 BST INFO     ---- Caught Disconnect signal ----
    10-18 19:14 BST DEBUG       HCI: hci0
    10-18 19:14 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT: player0
    10-18 19:14 BST INFO     ---- Caught Disconnect signal ----
    10-18 19:14 BST DEBUG       HCI: hci0
    10-18 19:14 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT: fd0
    10-18 19:14 BST INFO     ---- Caught Disconnect signal ----
    10-18 19:14 BST DEBUG       HCI: hci0
    10-18 19:14 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT: sep1
    10-18 19:14 BST INFO     ---- Caught Disconnect signal ----
    10-18 19:14 BST DEBUG       HCI: hci0
    10-18 19:14 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT: sep2
    10-18 19:14 BST INFO     ---- Caught Disconnect signal ----
    10-18 19:14 BST DEBUG       HCI: hci0
    10-18 19:14 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT: sep3
    10-18 19:14 BST INFO     ---- Caught Disconnect signal ----
    10-18 19:14 BST DEBUG       HCI: hci0
    10-18 19:14 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT: sep4
    10-18 19:14 BST INFO     ---- Caught Disconnect signal ----
    10-18 19:14 BST DEBUG       HCI: hci0
    10-18 19:14 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT: sep5
    10-18 19:14 BST INFO     ---- Caught Disconnect signal ----
    10-18 19:14 BST DEBUG       HCI: hci0
    10-18 19:14 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT: a2dpsnk
    10-18 19:14 BST INFO        Stopping playback from NewDevice
    10-18 19:14 BST INFO     ---- Caught Connect signal ----
    10-18 19:14 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep1
    10-18 19:14 BST DEBUG       HCI:hci0
    10-18 19:14 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT:sep1
    10-18 19:14 BST INFO     ---- Caught Connect signal ----
    10-18 19:14 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep2
    10-18 19:14 BST DEBUG       HCI:hci0
    10-18 19:14 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT:sep2
    10-18 19:14 BST INFO     ---- Caught Connect signal ----
    10-18 19:14 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep3
    10-18 19:14 BST DEBUG       HCI:hci0
    10-18 19:14 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT:sep3
    10-18 19:14 BST INFO     ---- Caught Connect signal ----
    10-18 19:14 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep4
    10-18 19:14 BST DEBUG       HCI:hci0
    10-18 19:14 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT:sep4
    10-18 19:14 BST INFO     ---- Caught Connect signal ----
    10-18 19:14 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep5
    10-18 19:14 BST DEBUG       HCI:hci0
    10-18 19:14 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT:sep5
    10-18 19:14 BST INFO     ---- Caught Connect signal ----
    10-18 19:14 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/fd1
    10-18 19:14 BST DEBUG       HCI:hci0
    10-18 19:14 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT:fd1
    10-18 19:14 BST INFO     ---- Caught Connect signal ----
    10-18 19:14 BST DEBUG    /org/bluealsa/hci0/dev_C0_3D_03_2E_FE_58/a2dpsnk/source
    10-18 19:14 BST DEBUG       HCI:hci0
    10-18 19:14 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT:a2dpsnk
    10-18 19:14 BST INFO        Using bluealsa-aplay for device: C0:3D:03:2E:FE:58
    10-18 19:14 BST DEBUG       LMS server IP:""
    10-18 19:14 BST DEBUG       pCP Card Conf:"hifi_dac+.conf"
    10-18 19:14 BST DEBUG       pCP SSET="Digital"
    10-18 19:14 BST INFO        Starting player:"NewDevice" bluetooth, alsa device:"", volume:"Digital".
    10-18 19:14 BST INFO     ---- Caught Connect signal ----
    10-18 19:14 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/player0
    10-18 19:14 BST DEBUG       HCI:hci0
    10-18 19:14 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 19:14 BST INFO        TRANSPORT:player0
    10-18 20:18 BST INFO     ---- Caught Disconnect signal ----
    10-18 20:18 BST DEBUG       HCI: hci0
    10-18 20:18 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 20:18 BST INFO        TRANSPORT: player0
    10-18 20:18 BST INFO     ---- Caught Disconnect signal ----
    10-18 20:18 BST DEBUG       HCI: hci0
    10-18 20:18 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 20:18 BST INFO        TRANSPORT: fd1
    10-18 20:18 BST INFO     ---- Caught Disconnect signal ----
    10-18 20:18 BST DEBUG       HCI: hci0
    10-18 20:18 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 20:18 BST INFO        TRANSPORT: sep1
    10-18 20:18 BST INFO     ---- Caught Disconnect signal ----
    10-18 20:18 BST DEBUG       HCI: hci0
    10-18 20:18 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 20:18 BST INFO        TRANSPORT: sep2
    10-18 20:18 BST INFO     ---- Caught Disconnect signal ----
    10-18 20:18 BST DEBUG       HCI: hci0
    10-18 20:18 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 20:18 BST INFO        TRANSPORT: sep3
    10-18 20:18 BST INFO     ---- Caught Disconnect signal ----
    10-18 20:18 BST DEBUG       HCI: hci0
    10-18 20:18 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 20:18 BST INFO        TRANSPORT: sep4
    10-18 20:18 BST INFO     ---- Caught Disconnect signal ----
    10-18 20:18 BST DEBUG       HCI: hci0
    10-18 20:18 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 20:18 BST INFO        TRANSPORT: sep5
    10-18 20:18 BST INFO     ---- Caught Disconnect signal ----
    10-18 20:18 BST DEBUG       HCI: hci0
    10-18 20:18 BST INFO        MAC: C0:3D:03:2E:FE:58
    10-18 20:18 BST INFO        TRANSPORT: a2dpsnk
    10-18 20:18 BST INFO        Stopping playback from NewDevice
    10-18 20:45 BST INFO     ---- Caught Connect signal ----
    10-18 20:45 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep1
    10-18 20:45 BST DEBUG       HCI:hci0
    10-18 20:45 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 20:45 BST INFO        TRANSPORT:sep1
    10-18 20:45 BST INFO     ---- Caught Connect signal ----
    10-18 20:45 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep2
    10-18 20:45 BST DEBUG       HCI:hci0
    10-18 20:45 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 20:45 BST INFO        TRANSPORT:sep2
    10-18 20:45 BST INFO     ---- Caught Connect signal ----
    10-18 20:45 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep3
    10-18 20:45 BST DEBUG       HCI:hci0
    10-18 20:45 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 20:45 BST INFO        TRANSPORT:sep3
    10-18 20:45 BST INFO     ---- Caught Connect signal ----
    10-18 20:45 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep4
    10-18 20:45 BST DEBUG       HCI:hci0
    10-18 20:45 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 20:45 BST INFO        TRANSPORT:sep4
    10-18 20:45 BST INFO     ---- Caught Connect signal ----
    10-18 20:45 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/sep5
    10-18 20:45 BST DEBUG       HCI:hci0
    10-18 20:45 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 20:45 BST INFO        TRANSPORT:sep5
    10-18 20:45 BST INFO     ---- Caught Connect signal ----
    10-18 20:45 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/fd2
    10-18 20:45 BST DEBUG       HCI:hci0
    10-18 20:45 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 20:45 BST INFO        TRANSPORT:fd2
    10-18 20:45 BST INFO     ---- Caught Connect signal ----
    10-18 20:45 BST DEBUG    /org/bluealsa/hci0/dev_C0_3D_03_2E_FE_58/a2dpsnk/source
    10-18 20:45 BST DEBUG       HCI:hci0
    10-18 20:45 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 20:45 BST INFO        TRANSPORT:a2dpsnk
    10-18 20:45 BST INFO        Using bluealsa-aplay for device: C0:3D:03:2E:FE:58
    10-18 20:45 BST DEBUG       LMS server IP:""
    10-18 20:45 BST DEBUG       pCP Card Conf:"hifi_dac+.conf"
    10-18 20:45 BST DEBUG       pCP SSET="Digital"
    10-18 20:45 BST INFO        Starting player:"NewDevice" bluetooth, alsa device:"", volume:"Digital".
    10-18 20:45 BST INFO     ---- Caught Connect signal ----
    10-18 20:45 BST DEBUG    /org/bluez/hci0/dev_C0_3D_03_2E_FE_58/player0
    10-18 20:45 BST DEBUG       HCI:hci0
    10-18 20:45 BST INFO        MAC:C0:3D:03:2E:FE:58
    10-18 20:45 BST INFO        TRANSPORT:player0

  5. #335
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    679
    I tried on another PCP and was able to replicate this i.e. the updated BT s/w and the tablet can still connect but no audio is heard.

    Then I restored the image with the old BT s/w onto the original PCP and tried it with Windows 11.
    Win11 could see the PCP but it couldn't pair or connect. It reported "Try connecting your device again".
    Event Log said "The mutual authentication between the local BT adapter and a device with BT address (blah blah) failed."

    So the Win11 behaviour is the same with the old and updated PCP BT s/w.
    Thankfully the tablet can still pair with the old BT s/w and audio is head fine. So Win11 isn't screwing things up per se, it is the updated BT s/w.
    Win11 just doesn't seem to work with PCP BT s/w at all!

    Interestingly the BT address in the Win11 event log is not seen at all in the PCP logs, but I've no idea if I'm making an incorrect assumption about BT addresses being similar to MAC addrsses.
    Last edited by mr-b; 2022-10-18 at 13:50.

  6. #336
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,947
    I suspect Windows 11 is going to be a problem, I don't have any Windows 11 machines, and I don't plan on it for a while.

    As for the tablet, The BT update included new codecs, and brought volume control. I cannot tell, if things are playing without any volume, or if there is nothing playing at all.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  7. #337
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    679
    Tx, I've worked out some of what was going wrong.

    After I'd updated my second PCP and BT stopped working, I spotted there was a new status bullet "Bluealsa is running".
    Then I saw a new section with a "BT Output Device" setting which was blank. The possible values looked similar to the Squeezelite audio output setting but with ",DEV=0" tacked on the end, so I guessed at that.
    I looked at the Alsa Volume setting which recommended to check alsamixer. I found that under under Squeezelite but could not make head nor tail of the settings so i've ignored it for now.
    But the BT output now works! :-)

    Checking the the first PCP, it didn't have the Bluealsa bullet despite my verifying that no BT updates were available. After multiple browser refreshes by chance I spotted that PCP was on 8.1.0 when the second was on 8.2.0.
    So I upgraded PCP in-situ and then the four BT bullets were present. I set the BT output setting and that works too! Phew! :-)

    Maybe the BT update checker (which also seems to take well over a minute each time) could check the PCP version too, if that's a known compatibility issue?

    I'll look at Win11 again another day ...

  8. #338
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    679
    Well I've got Win11 to work on one PCP!
    But it was an arduous journey and I still can't get it to work on the other PCP. :-(
    To be fair I've had similar symptoms with Win10 but on a different laptop so I can't completely blame Win11.

    It's working on a rPi 4B and piCorePlayer v8.2.0 | www v00017 | linux 5.15.35-pcpCore-v7l (32) | piCore v13.2 | Squeezelite v1.9.9-1392-pCP.
    It's not working thus far on a 3B+ and the same PCP s/w.

    It seems that keeping PCP's "Discoverable" = Yes helps.
    Also the behaviour seems random after the Windows scans for BT devices and tries to pair. Sometimes it pairs and allows one to connect, other times Windows says after a delay that the other device "would like to pair to this Windows device"!
    Sometimes devices take ages to appear in the Windows BT scan list, sometimes not.

    Another gotcha was that the PCP "Paired Devices" entry somehow changed from Type = Player to Speaker. I think the symptom of this was that the PC's paired device connected and then disconnected immediately afterwards. I've no idea how that config change happpened but I certainly didn't change it. I've seen that twice now on different PCPs but can't reproduce it. Once I changed that back to Type = Player it remained connected.

    Another issue appears to be signal strength. Both laptops and PCPs seem to be quite different in this. I suspect my PCP's metal case doesn't exactly help in this regard.
    I might try one of the USB dongles that others report as working e.g. https://www.amazon.co.uk/Maxesla-Blu...034484&sr=8-16

    Maybe a wizard to step through might help eradicate issues and make sure every value is set correctly.

  9. #339
    Senior Member
    Join Date
    Feb 2008
    Posts
    5,637
    I've given up using the pcp Bluetooth feature in its present iteration (the previous version worked flawlessly) - too many lost and/or missing paired instances (apart from a permanent Samsung TV which I don't want! ). Not quite your issue, I know.
    ------------------------------------------------------------------------------------

  10. #340
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    679
    Quote Originally Posted by castalla View Post
    I've given up using the pcp Bluetooth feature in its present iteration (the previous version worked flawlessly) - too many lost and/or missing paired instances (apart from a permanent Samsung TV which I don't want! ). Not quite your issue, I know.
    CAn you say which version exactly?

    I've found Windows BT recently to be very flaky, and incredibly sluggish. I know BT has suffered anyway since inception due to multiple "interpretations" of its implementation.
    I keep wishing there was a low-latency wifi based alternative.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •