Jivelite for piCorePlayer

[Howard Passman]

I think this is the same as the already available "Blue Glow" VU in Jivelite setup. Looks like a McIntish power amp

Sent from my Pixel 3a using Tapatalk

[Howard Passman]

I have my screensaver set for 10 seconds. The player boots and goes to the menu and then it takes about 45 seconds to go to the screen saver. After that instance it does switch after 10 seconds.

Is there a way to get the screen saver to come right up after booting rather than the menu?

Thanks,

Howard

[mr-b]

Hi

I'm trying out the clock display freezing issue workaround of a cron job to restart it nightly.

0 2 * * * /usr/bin/pkill -15 jivelite

However after doing this, I find the display says this in the morning. Playback is fine though. How do I get the display back (other than a reboot?)

[Paul Webster]

Jivelite is the UI not the player (SqueezePlay is the combined player and UI).

So you appear to have killed the UI but not restarted it.

Playing works because you have not killed the player.

[jd68]

You probably have not just killed the jivelite process but also the shell script that controls its startup and spossible restarts.

~$ ps -eaf | grep jivelite
root      5852     1  0 Feb09 ?        00:00:00 /bin/sh /opt/jivelite/bin/jivelite.sh
root      7751  5852  1 Feb09 ?        00:35:03 /opt/jivelite/bin/jivelite

You could try to kill only the process '/opt/jivelite/bin/jivelite':

0 2 1,16 * * /usr/bin/pkill -x /opt/jivelite/bin/jivelite

[mr-b]

Tx, yes I know jivelite is the UI, I was just saying that the player works as an indication that nothing else was wrong.

Also I was just going on the advice from below which says that the cmd should restart jivelite.
https://forums.slimdevices.com/showt...l=1#post908070

[mr-b]

@jd68

Tx - will give it a go.

[mr-b]

You probably have not just killed the jivelite process but also the shell script that controls its startup and spossible restarts.

~$ ps -eaf | grep jivelite
root      5852     1  0 Feb09 ?        00:00:00 /bin/sh /opt/jivelite/bin/jivelite.sh
root      7751  5852  1 Feb09 ?        00:35:03 /opt/jivelite/bin/jivelite

You could try to kill only the process '/opt/jivelite/bin/jivelite':

0 2 1,16 * * /usr/bin/pkill -x /opt/jivelite/bin/jivelite

That seems to have done the trick and the display is fine this morning. :-)
As a matter of interest, why only restart it twice a month?

[Paul Webster]

As a matter of interest, why only restart it twice a month?

Is it to guard against a 20-something days issue where there is some sort of problem handling a date offset overflow?

[Jeff07971]

Is it to guard against a 20-something days issue where there is some sort of problem handling a date offset overflow?

I just use the "reboot" cron job every 7 days at ridiculous o'clock.

Havent had the clock display freeze for many months now

Jeff