SqueezePlay for Joggler (Native, Ubuntu & SQPOS)

[roobarb!]

Should this still be working?

It should indeed. I'll need to check the paths being used.

[Man in a van]

Without more detail of your set up (plugin used, etc) perhaps this may help.

https://forums.slimdevices.com/showthre ... post937084

[proddick]

I have eventually got round to fitting a Netgear WNDA3200 to one of my Squeezeplay Jogglers. Opening it up and fitting went far easier than I expected so I should have done a long time ago

It works fine connecting to a 2.4Ghz WIFI (better than stock interface) but I can't connect to a 5Ghz one. Is this possible? Do I need to edit a file or something to enable dual-band?

[plm]

Is there an issue with the SqueezePlay repository at the moment? I just used the Update menu within SqueezePlay on a Joggler to see if there'd been any updates and it told me I was on version 1.60 but that version E.rr was available.

For anyone that thinks it's a good idea to try it - don't! I had a fat-finger moment and ended up inadvertently trying to install something that isn't there, and had to re-image my Joggler as a consequence.

This has been fixed now - turns out that when we moved the server, I didn't update the location of the database in the update script. Oops! It would only have affected people attempting to perform an update (as you describe) or if somebody was trying to install from scratch using the installation script.

Anyway, everything's back working properly now, so far as I can see!

Is this broken again? I just tried an update on a freshly-imaged Joggler and it couldn't connect to the update server.

[roobarb!]

Is there an issue with the SqueezePlay repository at the moment? I just used the Update menu within SqueezePlay on a Joggler to see if there'd been any updates and it told me I was on version 1.60 but that version E.rr was available.

For anyone that thinks it's a good idea to try it - don't! I had a fat-finger moment and ended up inadvertently trying to install something that isn't there, and had to re-image my Joggler as a consequence.

This has been fixed now - turns out that when we moved the server, I didn't update the location of the database in the update script. Oops! It would only have affected people attempting to perform an update (as you describe) or if somebody was trying to install from scratch using the installation script.

Anyway, everything's back working properly now, so far as I can see!

Is this broken again? I just tried an update on a freshly-imaged Joggler and it couldn't connect to the update server.

Probably. I've not looked at it in quite some time, but I can promise you there have been no updates.

I'm working on something on that server at the moment, if I get chance I'll image up a frame and take a look.