Thanks Ronnie,
I'm still blaming windows, but that give me a rabbit hole to look in.
Paul
Announcement
Collapse
No announcement yet.
User Profile
Collapse
-
From the LMS log file, its not clear that LMS wasn't starting, but fair enough. You can delete the cache file manually.
Code:cd /usr/local/slimserver/Cache rm cache.db
Leave a comment:
-
-
Samba on pCP does not allow for SMB1 by default, so enabling that in windows does nothing. But SMB has alot of security holes, Windows in some cases disables some of these methods.
Insecure logins and also authentication methods sometimes are locked down. If you machine is controlled by a...
Leave a comment:
-
SSH in to your pi, and see if you can see the files. LMS needs read access to the files.
It could be a configuration issue on the synology.
Leave a comment:
-
-
Of course you can, just look how we read power from the shell script. Then feel free to implement a python program to do it. There is pyLMS that may do what you want
https://pylms-python-logitech-media-....io/en/latest/...
Leave a comment:
-
The command line interface in LMS is not the same port that you should be sending the jsonrpc requests too. You should be sending the jsonrpc commands to the web server port.
The default Web Server port for LMS is 9000 (Set on Settings|Advanced|Network)
The default port for the...
Leave a comment:
-
Nothing formal, there are a few functions. You will have to read the scripts in pcp-lms-functions...
Leave a comment:
-
The average user does not want to package their own stuff. Its listed as a advanced topic on the tinycore website.
http://wiki.tinycorelinux.net/doku.p...ing_extensions
As for the directory, the location is determined by the kernel and the driver. Which is almost...
Leave a comment:
-
Just download the firmware package stated in the thread from DL6ER
Place that file in /mnt/mmcblk0p2/tce/optional
Then edit /mnt/mmcblk0p2/tce/onboot.lst and put the package name of the firmware in the list. Make sure to load the firmware before pcp-bt8.tcz is loaded.
Leave a comment:
-
Issue the command manually on an ssh session. My guess is that a variable is not set correctly. If you are reading code, there are some debug functions in there that may help you.
Leave a comment:
-
Well sometimes its the obvious things we forget to ask. Yes, only one system can use the hardware. You must stop one method before turning on the other.
Leave a comment:
-
That is the latest version.
I would try to run bluealsa manually to see what is logged. First look at bluealsa command line, and then kill the process
Code:ps ax | grep blueasla sudo pkill bluealsa
Leave a comment:
-
Make sure the footter of the web page shows 8.2.0 and also press the update button on the bluetooth page to make sure you have the latest extensions.
Then reboot your player, connect your phone, then try to play.
Post the bluetooth logs.
Leave a comment:
-
I borrowed a Galaxy Xcover Pro from work for the weekend to play with. It has Android 11 on it. Worked with the first attempt, currently using the aptX codec.
I just looked at your screenshot again. You are not using the latest version of pCP. You also should make sure you have the...
Leave a comment:
-
Will probably require some debugging. You can kill the bluealsa process (Note the command line before you kill it) Then just run it from a ssh session and see what it logs to the screen
Leave a comment:
-
The md5.txt is just a checksum file used during downloads. How did you create the extension itself?
Leave a comment:
-
Seems something is quite broke with the cache.
did you do a full scan after resizing?
Leave a comment:
-
So that type of hardware doesn’t have volume control. Did you try to disable aptx-hd and just use the plain sbc codec.
Leave a comment:
No activity results to display
Show More
Leave a comment: