- 1. March 2016 at 12:48 #18888
I would very much appreciate an updated, Jessie-based image. Python is stuck at 3.2 with Wheezy making some newer modules impossible to install (gmusicapi, for example, requires a Python update).
I am aware it’s possible to update to Jessie, but I can imagine this causing all sorts of issues. A newer image of a clean install would certainly be useful. 🙂
Thanks!3. March 2016 at 17:16 #19102
@Bort: Thank you for your feedback. We will show your obervations (also those you might add in the future) to our developer.
@q20: Yes, the root access has changed in the new Jessie build. Log in as user “pi” as usual, enter “su” and “max2play” to get root access.
Maximilian from Max2Play4. March 2016 at 20:43 #19119
unfortunately, the command
apt-get update && apt-get upgradedestroys the system on boot (raspberry pi 3 only).
– 160301 runs
– 160303 crash
After replacing the micro SD card Samsung 16GB for cheap Medion 16GB from Aldi everything works. Strange because for raspberry pi 2 there was no problems… maybe the problem was with the update by shh.
Robert7. March 2016 at 16:51 #19151
- most apps are working with the RPi 3 and the current Beta (make sure to update to latest Max2Play-beta)
- WPS is currently not working with Raspberry Pi 3 integrated WiFi (thanks Bort for investigating) – I think there are some driver issues that need to be solved. External USB-Wi-Fi sticks are working with WPS.
- I built a bluetooth addon that wants to be tested – if you like you can get it from http://shop.max2play.com/media/downloadable/beta/bluetooth.tar – this will let you connect to bluetooth speakers and let kodi / squeezelite and other players use it as audio output
If you want to upgrade to the latest packages, you should call “apt-get update && apt-get upgrade”. This can also be done at the bottom of the web interface on the Raspberry PI Settings Addon.
I am still testing and preparing to build the final version of Max2Play 2.28. If you experience any problems in the Beta with Kodi 15.2 or other Addons, this is the place to post them 🙂
All the best
Stefan14. March 2016 at 11:14 #19249
I am sorry, but the licence verification was not available on the weekend due to some changes in our server architecture (bringing SSL encryption). It is now working again. If your licence is not marked as active please remove your email / licence code, click save and enter it again to make sure it is updated and saved.
@Robert: I had to remove your post about how to bypass validation.16. March 2016 at 9:19 #19306
Since this topic has become a catch-all for the Jessie beta, I thought I’d mention another issue: when attempting to install and run the Squeezebox server, it errors:
Trying to launch … NOT successful Click here to show detailed information
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
sudo: no tty present and no askpass program specified
Any ideas?16. March 2016 at 12:06 #19307
@q20: never had such an error. Installation and Startup on every testsetup went OK so far. Did you change something else on your SD-Card-image? The error is indicating missing user rights to start the squeezebox server – maybe your installation is broken (SD-card error). In this case you should start with a fresh SD-Card-Image.
Make sure to install Squeezebox Server Nightly 7.9 (otherwise it won’t start because of missing libraries).16. March 2016 at 17:44 #19317
@q20: I cannot really help, because there might be different problems that lead to the error. You may change permissions of the launch script by using “sudo chmod 777 /etc/init.d/logitechmediaserver” but I don’t know why this script has not the rights to start… a reinstall is probably the easiest and fastest solution.17. March 2016 at 19:08 #19340
So, another issue with the beta (and why I ran into issues before); re-sizing the SD card does not work. I’ve tried on both 32GB and 8GB cards without luck. 🙁
If I attempt to resize using raspi-config:
mmcblk0p2 is not the last partition. Don’t know how to expand.
EDIT: after a couple of reboots and updating the max2play beta, it’s all resolved itself…
You must be logged in to reply to this topic.