Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 299

Hybrid View

  1. #1
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    1,597

    Jivelite on a Joggler

    I have a couple of O2 Jogglers that I use solely as touch controllers in a couple of locations around the house. I'm running Squeezeplay OS on them, but an unwanted side-effect is that each Joggler shows up as a player in LMS. It was suggested to me (in this thread) that I should try to get Jivelite running instead, since the interface would be the same, but without the software players.

    I have very little Linux experience, but I've been having a go this evening. I've made some progress, but have hit some snags, and I'm hoping some on here might be able to help me with them.

    I started by making a bootable USB stick with the ext4 Ubuntu base/server image from here. My reason for going for a base/server image was that I thought I could fit one of those images into the 1GB of flash storage on the Joggler, but since it wouldn't boot up after trying to 'reflash' that image (probably because the image expands to ~2GB) I have switched to booting off a USB stick. It might therefore have made more sense to start with a more complete image, so that more packages/features are available from the start, but I do still hope to fit the finished setup into the flash memory, so a smaller starting point is better. So one question I have is what would be the best (smallest?) starting point to base this install on, or is there an easy way to remove stuff from a working system to leave just what's needed to run Jivelite? Whoever created Squeezeplay OS must have done something like that I guess.

    Then I followed the instructions for compiling and installing Lua and Jivelite, as given in step 4 here. I had to connect the Joggler via an ethernet cable, since I've been unable to get the wifi connected (a task for later). So another question - any tips for getting the wifi going? I followed instructions that I found on a couple of different sites, but nothing has worked so far.

    The Jivelite and Lua compilations went OK in the end though - no warnings or errors. But Jivelite won't start. It gives me an "Invalid width or height" error. I figured this might be due to the wallpaper. The Hagensieker site has some files for the 800x480 screen size of the Joggler, so I copied those into the specified locations (without checking whether they were actually any different from the existing versions of those files), and on looking through SetupWallpaper.lua I noticed that the 800x480 wallpaper names should have a 'PCP_' prefix. In my wallpapers folder I only had files with BB_, FAB4_ and JIVE_ prefixes, so I copied all the PCP_ files from a pCP installation. But no joy - I still get the "Invalid width or height" error.

    So my main question is therefore, what's causing this "Invalid height or width" error, and how do I go about fixing it?

    Maybe my first question should have been "Is there already a flashable image for a Joggler that simply runs Jivelite?"?

  2. #2
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    3,167
    Ther's hope at the end of the tunnel

    Name:  AF1QipN1wLHlYwObpYdJ6OiBLdIMumdArgXODJLPIp7G=s512-p-qv=pnoib7126mqj1lopqbhsjl8u7sbil99gv,m=4d6d.jpeg
Views: 838
Size:  74.4 KB

    ronnie

  3. #3
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    1,597
    Quote Originally Posted by Man in a van View Post
    Ther's hope at the end of the tunnel
    Thanks Ronnie

    If that's Jivelite running on that Joggler (rather than Squeezeplay), then it's not encouragement that I need - I need the Dummies' Guide!
    How did you get to that point? I don't see a USB stick in the side of the Joggler, so whatever it is it's running from flash memory.

    I'm thinking that TinyCore might be a good place to start, partly to fit it into the 1GB Joggler flash (is 512mb of RAM going to be enough for TinyCore?), and partly so that, like pCP, I can kill the power without worrying about corruption. Could an option to backup the device configuration (wifi, Jivelite Menu configuration etc) be added as an Applet?

  4. #4
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    3,167
    Well, the problem i have at the moment is to get jivelite to autostart.

    I can start it from a script, but I want to put a link in "Autostart" and I can't find where that is at the moment.

    Also the image (joggler skin) is the wrong size (the bottom part with the controls is missing) as it is not fully expanded.

    The version on the desktop I did yesterday.

    It's running on an old shuttle I have with Raspberry Pi Desktop for PC and Mac installed. I can get that to autostart.

    I'll post a little how to in a bit

    ronnie

  5. #5
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    1,597
    Thanks - it would be good to compare notes.

    I've made progress. The Hagensieker site had some notes on how to make an RPi installation work with a smaller screen here. The line that worked was this one (edited to suit my folder structure):

    Code:
    sudo SDL_FBDEV=/dev/fb0 ./triode-jivelite/bin/jivelite
    This was enough to start Jivelite, and I could use the keyboard to navigate around and select the Joggler skin.

    The touch screen needs calibrating, and there's a long todo list (wifi, flash memory, autostart), but it's progress.

    Last edited by chill; 2019-01-16 at 08:02.

  6. #6
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    3,167
    Name:  jivelite.jpg
Views: 824
Size:  177.5 KB

    This is full screen on the joggler but started from another computer via ssh.

  7. #7
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,388
    Quote Originally Posted by chill View Post
    That screenshot shows a rather outdated version of Jivelite or Squeezeplay. Spot the difference in the button bar at the bottom on your and Man's screenshot.
    Michael

    http://www.herger.net/slim-plugins - Spotty, MusicArtistInfo

  8. #8
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    2,183
    Is it using systemd to start it?
    As in “systemctl start”

    If it is the you can leave it all set-up and then
    systemctl enable <servicename>
    To enable it to start on boot
    and
    systemctl disable <servicename>
    To stop it starting on boot
    Paul Webster
    http://dabdig.blogspot.com
    Author Radio France (FIP etc) plugin

  9. #9
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    1,597
    Quote Originally Posted by Paul Webster View Post
    Is it using systemd to start it?
    As in “systemctl start”

    If it is the you can leave it all set-up and then
    systemctl enable <servicename>
    To enable it to start on boot
    and
    systemctl disable <servicename>
    To stop it starting on boot
    Oh good grief - that's much simpler. Thank you Paul for pointing this noob to the correct way to do this! Works a treat.

    So now my applet will only need to run a few simple commands. Disabling it will leave it there ready to be re-enabled by the applet.

  10. #10
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    1,597
    Nearly there I think.

    I have an 'LMS' applet that sits under the 'settings' section:



    It currently allows the LMS service to be disabled or enabled (referred to as 'Autostart LMS'), and it allows the service to be started/stopped/restarted.



    There's currently no checking, or warning, if you try to stop/start/restart the service if it wasn't loaded at boot, and I'd also like to add some visual feedback to show whether LMS is running. But it's getting close.

Posting Permissions

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