Home of the Squeezebox™ & Transporter® network music players.
Page 86 of 97 FirstFirst ... 3676848586878896 ... LastLast
Results 851 to 860 of 968
  1. #851
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    3,189
    Depending on where you upload, it might not be in the backup set.

    Make sure the full path and file is on /opt/.filetool.lst

    i.e.

    usr/local/somepath/somefile.jpg

    Make sure to drop the leading "/"
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  2. #852
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,839
    [ Main Page ] in [ Advanced ] mode > [ Diagnostics ] scroll down to "[ INFO ] Backup mydata".

    Look at "[ INFO ] Current /opt/.filetool.lst" for what gets backed up.

  3. #853
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    3,433
    Quote Originally Posted by paul- View Post
    Depending on where you upload, it might not be in the backup set.

    Make sure the full path and file is on /opt/.filetool.lst

    i.e.

    usr/local/somepath/somefile.jpg

    Make sure to drop the leading "/"
    Thanks Paul and Greg

    ronnie

  4. #854

    Bluetooth remote with pCP

    I've already asked this in a separate thread but it either got overlooked there or nobody had any idea. Hoping for the former, I allow myself to ask here once more:

    Is it possible to use a Bluetooth remote with piCorePlayer? I can successfully pair the remote in question with builtin BT of a Pi running Raspbian. It registers as an input device and sends keypress events. I do, however, have no clue how to transfer this to pCP.

    Any help would be greatly appreciated.

  5. #855
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    3,189
    Iím sure it possible. But Iíve not done it, and I donít have such a device to even test.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  6. #856
    Could you maybe give me some pointers on how to start? How would I persistently pair a bluetooth device with pCP? I guess I need to install the bluetooth extension first but how do I proceed from there?

    I think some people are using bluetooth remotes successfully with LIRC which, as I understand, pCP supports. So it might just be a matter of pairing the remote and coming up with a working LIRC configuration for it.

  7. #857
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    3,189
    First install the Bluetooth stuff.....the easiest way is to act like you are going to use a usb speaker. If you can pair a speaker temporarily, that might be best.

    Then open a ssh session and run bluetoothd, try to pair your remote. Persistence isnít a problem, itís the automatic reconnection that might be tricky........it was for speakers.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  8. #858
    Okay, here's what I did so far:

    - Enabled built-in BT on pCP's Wifi Settings page, rebooted.
    - Installed bluetooth-4.14.81-rt47-pcpAudioCore and pcp-bluez from pCP' repository.
    - Installed evtest from the official piCore repository.
    - ssh'd in and started dbus and bluetoothd:
    Code:
    sudo /usr/local/etc/init.d/dbus start
    sudo /usr/local/lib/bluetooth/bluetoothd -nd
    - Loaded uart_hci kernel module and ran hciattach:
    Code:
    sudo modprobe hci_uart
    hciattach /dev/ttyAMA0 bcm43xx 921600 noflow
    - Started bluetoothctl and paired the device:
    Code:
    tc@piCorePlayer:~$ bluetoothctl 
    Agent registered
    [bluetooth]# power on
    Changing power on succeeded
    [CHG] Controller 43:43:A1:12:1F:AC Powered: yes
    [bluetooth]# discoverable on
    Changing discoverable on succeeded
    [CHG] Controller 43:43:A1:12:1F:AC Discoverable: yes
    [bluetooth]# pairable on
    Changing pairable on succeeded
    [bluetooth]# scan on
    Discovery started
    [CHG] Controller 43:43:A1:12:1F:AC Discovering: yes
    ...
    [NEW] Device 5F:5F:5B:A1:65:17 小米蓝牙遥控器
    ...
    [bluetooth]# pair 5F:5F:5B:A1:65:17 
    Attempting to pair with 5F:5F:5B:A1:65:17
    [CHG] Device 5F:5F:5B:A1:65:17 Connected: yes
    ...rather long output deleted...
    Pairing successful
    [CHG] Device 5F:5F:5B:A1:65:17 Name: XiaoMi RC
    [CHG] Device 5F:5F:5B:A1:65:17 Alias: XiaoMi RC
    [CHG] Device 5F:5F:5B:A1:65:17 Modalias: usb:v2717p3200d0000
    [小米蓝牙遥控器]# info 5F:5F:5B:A1:65:17
    Device 5F:5F:5B:A1:65:17 (public)
    	Name: XiaoMi RC
    	Alias: XiaoMi RC
    	Appearance: 0x03c1
    	Icon: input-keyboard
    	Paired: yes
    	Trusted: no
    	Blocked: no
    	Connected: yes
    	LegacyPairing: no
    	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
    	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
    	UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
    	UUID: Vendor specific           (f000ffc0-0451-4000-b000-000000000000)
    	Modalias: usb:v2717p3200d0000
    	RSSI: -59
    	TxPower: 0
    [小米蓝牙遥控器]#
    The device is now available as /dev/input/event0 and I can see its key presses with evtest.

    So far so good, but when I reboot I have to start the whole procedure from scratch again. So, for me, persistence is the first problem to solve. I would consider automatic reconnection a part of that.

    What I tried so far was to add "/usr/local/etc/init.d/dbus start" and "/usr/local/lib/bluetooth/bluetoothd" to /opt/bootlocal.sh (before the pCP start command as I assume that blocks while pCP is running), but that led to the Pi no longer being able to boot. I'm out of ideas for now and would be very grateful for a nudge in the right direction.

  9. #859
    Quote Originally Posted by JQW View Post
    Had an odd USB drive issue the other day. My piCorePlayer installation currently uses two SanDisk 128GB memory sticks as storage, plugged into the upper 2 USB sockets of a Pi 3 B. To update them I power the player down and update the files from a PC.

    When I came to do this this week after adding or changing a few albums, the particular drive couldn't be seen by piCorePlayer at boot up, it was as if the drive wasn't plugged in at all. Eventually, after almost 5 minutes, the drive showed up under dmesg, and it could finally be mounted.

    I presume this is a hardware issue with the drive itself.
    It seems to be an issue with these drives - they overheat and shut down. It's not a PiCorePlayer issue as I have the same symptoms under Windows, and the older of the two drives is getting worse. This seems to be a common problem with this particular SanDisk UltraFit model of drive, which appears to have been taken off the market last year.

    I've a spare HD cannibalised from a broken laptop which I can use instead.

  10. #860
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    3,189
    Manul,

    That's why I mentioned to go through the speaker setup, as it sets up the automatic starting of bluetooth and also setup persistence of paired devices.

    Once things are paired, connection should easily be managed via dbus commands.

    Paul
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

Posting Permissions

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