Can't get Custom Clock app to work

Max2Play Home › Forums › Max2Play Add-ons › Can't get Custom Clock app to work

Viewing 9 posts - 1 through 9 (of 9 total)
  • Back to forum
    Posted in: Max2Play Add-ons
  • ftarz premium
    1. März 2019 at 6:33 #44587

    I’ve installed m2p V2.47 on a RPi. I installed squeezelite and jivelite. Everything seems to work except for the Custom Clock and License Manager apps.

    I can install both and get Custome Clock to show-up in the Extras window, but nothing happens when I select it.

    I’m trying to move from piCorePlayer to m2p but can’t get anything related to the custom clocks to work.

    Frank

    Cassio299 premium
    2. März 2019 at 7:58 #44599

    Hi Frank

    Custom Clock is one of Erlands many plugins.

    All Erlands plugins are now free of charge, so you shall uninstall the license Manager check if custom clock works there after.

    If that doesn’t help, visit the official support forum an make a search for Custom Clock: click here

    Peter

    Cassio299 premium
    2. März 2019 at 7:59 #44600

    Dobb reply, sorry!!

    • This reply was modified 5 years, 1 month ago by Cassio299.
    ftarz premium
    5. März 2019 at 5:12 #44652

    Well I’ve tried installing the CustomClockApp on a virgin max2play V2.47 install with Squeezelite and jivelite installed and without the licensemanager (both from the jivelite app install and from the LMS plugins. Whatever I try I cannot get the CustomClockApp to work.

    The app shows-up in jivelite, but nothing happens when I try to run it in anyway.

    I’ve been trying to figure-out how to get Squeezelite logging to work so I can follow what’s happening and not happening, but when I start it with -d all=debug, I don’t see any debug logging.

    Can anyone help here?

    Frank

    Heiner premium
    5. März 2019 at 11:12 #44655

    Hi ftarz,

    You need to observe the LMS log as playback is handled there.

    You can try manually installing it as this seems to have been an issue for someone else in the past (slimdevices thread).

    ftarz premium
    7. März 2019 at 6:50 #44684

    Well I’ve looked at the squeezelite log file but it doesn’t show anything related to the custom clock app. In fact it doesn’t show much after the start-up of the server anyway.

    I think the custom clock app is installed OK:
    root@max2play:~# find / -name „*Custom*“
    /opt/jivelite/jivelite/share/jive/applets/CustomizeHomeMenu
    /opt/jivelite/jivelite/share/jive/applets/CustomizeHomeMenu/CustomizeHomeMenuMeta.lua
    /opt/jivelite/jivelite/share/jive/applets/CustomizeHomeMenu/CustomizeHomeMenuApplet.lua
    /usr/share/perl5/Dpkg/Source/Package/V3/Custom.pm
    /usr/share/kodi/addons/skin.estouchy/xml/CustomVolume.xml
    /usr/share/kodi/addons/skin.estouchy/xml/CustomFirstRun.xml
    /usr/share/kodi/addons/skin.estuary/xml/Custom_1109_TopBarOverlay.xml
    /usr/share/kodi/addons/skin.estuary/xml/Custom_1101_SettingsList.xml
    /usr/share/kodi/addons/skin.estuary/xml/Custom_1102_TextViewer.xml
    /usr/share/kodi/addons/skin.estuary/xml/Custom_1100_AddonLauncher.xml
    /usr/share/kodi/addons/skin.estuary/xml/Custom_1103_VolumeSlider.xml
    /usr/share/kodi/addons/skin.estuary/xml/Custom_1105_MusicOSDSettings.xml
    /usr/share/kodi/addons/skin.estuary/xml/Custom_1104_Fanart.xml
    /usr/share/kodi/addons/skin.estuary/xml/Custom_1107_SearchDialog.xml
    find: ‘/run/user/1000/gvfs’: Permission denied
    /home/pi/.jivelite/userpath/applets/CustomClock
    /home/pi/.jivelite/userpath/applets/CustomClock/CustomVUMeter.lua
    /home/pi/.jivelite/userpath/applets/CustomClock/CustomClockMeta.lua
    /home/pi/.jivelite/userpath/applets/CustomClock/CustomSpectrumMeter.lua
    /home/pi/.jivelite/userpath/applets/CustomClock/CustomClockApplet.lua
    /home/pi/.jivelite/userpath/settings/CustomizeHomeMenu.lua
    root@max2play:~#

    I’ve tried several times to get the custom clock app working, but no luck. Everything else, including the SuperDateTime plugin, works just fine. I’ve tried with different versions of LMS installed (7.9, 7.9.1, 7.9.2): no difference. I’ve tried with different versions of Jivelite installed, but also no luck. I see the icon for the custom clock, but absolutely nothing happens when I touch it. Likewise nothing happens when I try to set-up a custom clock entry for a screen saver.

    I don’t know enough about how the window manager in max2play works to figure-out what’s wrong. It appears to be something the affects just the custom clock app.

    Frank

    Heiner premium
    7. März 2019 at 13:58 #44686

    Hi Frank,

    The LMS log is in the Squeezebox Server plugin web interface, not in Squeezelite. You can find a link debug info at the bottom of each plugin’s web interface.

    However, since only this specific applet seems to be the issue it is more likely that you will the solution from the applet itself. Here’s the discussion on it.

    ftarz premium
    8. März 2019 at 6:22 #44711

    OK, I’ve done some digging and discovered what’s happening here.

    First to respond to the previous post:
    > The LMS log is in the Squeezebox Server plugin web interface, not in Squeezelite. You can find a link debug info at the bottom of each
    > plugin’s web interface.
    The squeezelite log and the LMS log are the same thing. The plugin web interface gets its log file from the squeezelite log.

    To answer what’s happening with the CustomClock applet, I installed raspian on an SDcard and then installed LMS (Squeezelite) by following this: http://wiki.slimdevices.com/index.php/Debian_Package#installing_7.9.2.

    Then I installed Jivelite by following this: http://www.hagensieker.com/jivelite/index.php

    You can set-up the squeezelite service to start at boot, SSH into the Pi, manually start Jivelite and follow the warning and error messages in the SSH session.

    Upon starting Jivelite I see this in the SSH session:
    JiveLite 0.1.0
    20190308 03:26:32.049 INFO jivelite – JiveMain.lua:267 JiveLite version 0.1.0
    20190308 03:26:32.109 INFO jivelite.ui.draw – jiveL_initSDL:205 800,480 32 bits/pixel 4 bytes/pixel [R<<16 G<<8 B<<0]
    20190308 03:26:32.109 INFO jivelite.ui.draw – jiveL_initSDL:206 Hardware acceleration is available
    20190308 03:26:32.109 INFO jivelite.ui.draw – jiveL_initSDL:207 Window manager is not available
    20190308 03:26:32.138 INFO jivelite.applets – AppletManager.lua:92 User Path: /root/.jivelite/userpath
    20190308 03:26:32.253 INFO jivelite.applets – AppletManager.lua:318 Registering: DesktopJive
    20190308 03:26:32.254 INFO jivelite.applets – AppletManager.lua:318 Registering: BlankScreenSaver
    20190308 03:26:32.260 INFO jivelite.applets – AppletManager.lua:318 Registering: ChooseMusicSource
    20190308 03:26:32.266 INFO jivelite.applets – AppletManager.lua:318 Registering: CustomClock
    20190308 03:26:32.273 INFO jivelite.applets – AppletManager.lua:318 Registering: CustomizeHomeMenu
    20190308 03:26:32.274 INFO jivelite.applets – AppletManager.lua:318 Registering: HDGridSkin
    20190308 03:26:32.276 INFO jivelite.applets – AppletManager.lua:318 Registering: HDSkin
    20190308 03:26:32.279 INFO jivelite.applets – AppletManager.lua:318 Registering: HttpAuth
    20190308 03:26:32.293 INFO jivelite.applets – AppletManager.lua:318 Registering: ImageViewer
    20190308 03:26:32.298 INFO jivelite.applets – AppletManager.lua:318 Registering: JogglerSkin
    20190308 03:26:32.299 INFO jivelite.applets – AppletManager.lua:318 Registering: LicenseManager
    20190308 03:26:32.300 INFO jivelite.applets – AppletManager.lua:318 Registering: LogSettings
    20190308 03:26:32.304 INFO jivelite.applets – AppletManager.lua:318 Registering: NowPlaying
    20190308 03:26:32.306 INFO jivelite.applets – AppletManager.lua:318 Registering: Quit
    20190308 03:26:32.313 INFO jivelite.applets – AppletManager.lua:318 Registering: ScreenSavers
    20190308 03:26:32.315 INFO jivelite.applets – AppletManager.lua:318 Registering: SelectPlayer
    20190308 03:26:32.322 INFO jivelite.applets – AppletManager.lua:318 Registering: SelectSkin
    20190308 03:26:32.327 INFO jivelite.applets – AppletManager.lua:318 Registering: SetupAppletInstaller
    20190308 03:26:32.330 INFO jivelite.applets – AppletManager.lua:318 Registering: SetupDateTime
    20190308 03:26:32.333 INFO jivelite.applets – AppletManager.lua:318 Registering: SetupLanguage
    20190308 03:26:32.336 INFO jivelite.applets – AppletManager.lua:318 Registering: SetupWallpaper
    20190308 03:26:32.339 INFO jivelite.applets – AppletManager.lua:318 Registering: SetupWelcome
    20190308 03:26:32.346 INFO jivelite.applets – AppletManager.lua:318 Registering: SlimBrowser
    20190308 03:26:32.377 INFO jivelite.applets – AppletManager.lua:318 Registering: SlimDiscovery
    20190308 03:26:32.384 INFO jivelite.applets – AppletManager.lua:318 Registering: SlimMenus
    20190308 03:26:32.391 INFO jivelite.applets – AppletManager.lua:318 Registering: WQVGAgridSkin
    20190308 03:26:32.394 INFO jivelite.applets – AppletManager.lua:318 Registering: WQVGAsmallSkin
    20190308 03:26:32.401 INFO applet.CustomClock – CustomClockMeta.lua:68 Using standard Now Playing screen
    20190308 03:26:32.403 ERROR jivelite.applets – AppletManager.lua:474 Error while loading applet LicenseManager:/root/triode-jivelite/share/jive/jive/AppletManager.lua:442: LicenseManager|…userpath/applets/LicenseManager/LicenseManagerApplet.lua:232: ‚then‘ expected near ‚!‘
    stack traceback:
    /root/triode-jivelite/share/jive/jive/AppletManager.lua:474: in function ‚_ploadApplet‘
    /root/triode-jivelite/share/jive/jive/AppletManager.lua:560: in function ‚loadApplet‘
    …e/userpath/applets/LicenseManager/LicenseManagerMeta.lua:46: in function ‚configureA
    20190308 03:26:32.416 INFO jivelite – JiveMain.lua:591 select skin: JogglerSkin
    20190308 03:26:32.546 INFO jivelite.applets – AppletManager.lua:709 store settings: SetupAppletInstaller
    20190308 03:26:32.643 INFO squeezebox.server – SlimServer.lua:752 connected raspberrypi
    20190308 03:26:32.657 INFO squeezebox.server – SlimServer.lua:764 self.mac being set to—->nil
    libpng warning: Interlace handling should be turned on when using png_read_image
    libpng warning: Interlace handling should be turned on when using png_read_image
    libpng warning: Interlace handling should be turned on when using png_read_image
    libpng warning: Interlace handling should be turned on when using png_read_image

    Notice the ERROR line: 20190308 03:26:32.403 ERROR jivelite.applets – AppletManager.lua:474 Error while loading applet LicenseManager:/root/triode-jivelite/share/jive/jive/AppletManager.lua:442: LicenseManager|…userpath/applets/LicenseManager/LicenseManagerApplet.lua:232: ‚then‘ expected near ‚!‘

    When I click on the Custom Clock entry I see the same behavior as in max2play: nothing happens. But in the SSH session I see:
    20190308 03:05:08.886 ERROR jivelite.applets – AppletManager.lua:474 Error while loading applet CustomClock:/root/triode-jivelite/share/jive/jive/AppletManager.lua:442: CustomClock|…elite/userpath/applets/CustomClock/CustomClockApplet.lua:347: ‚)‘ expected near ‚!‘
    stack traceback:
    /root/triode-jivelite/share/jive/jive/AppletManager.lua:474: in function ‚_ploadApplet‘
    /root/triode-jivelite/share/jive/jive/AppletManager.lua:560: in function ‚loadApplet‘
    /root/triode-jivelite/share/jive/jive/AppletMeta.lua:150: in function ‚callback‘
    /root/triode-j
    20190308 03:05:08.886 WARN jivelite.ui.draw – jiveL_dispatch_event:780 error in event function:
    …ivelite/userpath/applets/CustomClock/CustomClockMeta.lua:41: attempt to index local ‚applet‘ (a nil value)
    stack traceback:
    …ivelite/userpath/applets/CustomClock/CustomClockMeta.lua:41: in function ‚callback‘
    /root/triode-jivelite/share/jive/jive/ui/SimpleMenu.lua:189: in function ‚itemListener‘
    /root/triode-jivelite/share/jive/jive/ui/Menu.lua:154: in function ‚_eventHandler‘
    /root/triode-jivelite/share/jive/jive/ui/Menu.lua:1144: in function ‚ca

    Notice the ERROR line:
    20190308 03:05:08.886 ERROR jivelite.applets – AppletManager.lua:474 Error while loading applet CustomClock:/root/triode-jivelite/share/jive/jive/AppletManager.lua:442: CustomClock|…elite/userpath/applets/CustomClock/CustomClockApplet.lua:347: ‚)‘ expected near ‚!‘
    It’s the same error as above.

    Lines 347-350 in the CustomClockApplet.lua file are:
    if ((oldMode and self.mode != oldMode) or self.licensed~=licensed) and self.window then
    self.window:hide()
    self.window = nil
    end

    According to https://stackoverflow.com/questions/34713203/what-does-lua-operator-mean/34713230: the ~= is not equals. It is the equivalent in other languages of !=

    So the „!=“ entries in the CustomClockApplet.lua file are incorrect and should be „~=“.

    Sure enough when I change all the „!=“ to „~=“ the CustomClock applet works correctly!

    I stll have 2 problems: after changing all the „!=“ to „~=“ in the CustomClockApplet.lua file, there still are 2 other instances of the „!“ character in :
    function _token_of(c)
    local x,y = string.match(c,“^%s*([/!]?)%s*(%a+)%s*“)
    return (x or „“) .. (y or „“)
    end

    and:

    local html_tags = {
    [„br“] = ‚\n‘,
    [„/br“] = ‚\n‘,
    [„li“] = “,
    [„/li“] = “,
    [„ul“] = „“,
    [„/ul“] = „“,
    [„ol“] = „“,
    [„/ol“] = „“,
    [„img“] = “,
    [„/tr“] = “,
    [„pre“] = „“,
    [„/pre“] = „“,
    [„b“] = „*“,
    [„/b“] = „*“,
    [„i“] = „/“,
    [„/i“] = „/“,
    [„big“] = „“,
    [„/big“] = „“,
    [„small“] = „“,
    [„/small“] = „“,
    [„strong“] = „*“,
    [„/strong“] = „*“,
    [„em“] = „/“,
    [„/em“] = „/“,
    [„u“] = „“,
    [„/u“] = „“,
    [„div“] = „“,
    [„/div“] = „“,
    [„html“] = „“,
    [„/html“] = „“,
    [„head“] = „“,
    [„/head“] = „“,
    [„body“] = „“,
    [„/body“] = „“,
    [„p“] = „“,
    [„/p“] = „“,
    [„a“] = „“,
    [„/a“] = „“,
    [„hr“] = „\n“ .. string.rep(„-„,44) .. „\n“,
    [„font“] = „“,
    [„/font“] = „“,
    [„!doctype“] = „“,
    [„void“] = „“,
    [„/void“] = „“,
    [„comment“] = „“,
    [„/comment“] = „“,
    [„style“] = „“,
    [„/style“] = „“,
    [„meta“] = „“,
    [„tr“] = „“,
    [„td“] = „\t“,
    [„/td“] = „“,
    [„table“] = „“,
    [„/table“] =““,
    [„th“] = „“,
    [„/th“] = „“,
    }

    I don’t know if one of both of these should be changed as well.

    The other problem is that if I install the CustomClock app in Jivelite, then fix the „!=“ so that it runs correctly, then uninstall and reinstall it again, the CustomClock app is copied back with the incorrect „!=“. The file is coming from http://superdatetimewu.sourceforge.net/CustomClock_JL_1.01.004.zip.

    20190308 04:18:54.604 INFO applet.SetupAppletInstaller – SetupAppletInstallerApplet.lua:435 downloading: http://superdatetimewu.sourceforge.net/CustomClock_JL_1.01.004.zip to: /root/.jivelite/userpath/applets/CustomClock/ sha1: c4f6d3d143bc4876e843d3c1604ca469275b1cc7
    20190308 04:18:55.015 INFO applet.SetupAppletInstaller – SetupAppletInstallerApplet.lua:462 sha1 verified
    20190308 04:18:55.259 INFO applet.SetupAppletInstaller – SetupAppletInstallerApplet.lua:534 extracting file: /root/.jivelite/userpath/applets/CustomClock/strings.txt
    20190308 04:18:55.260 INFO applet.SetupAppletInstaller – SetupAppletInstallerApplet.lua:534 extracting file: /root/.jivelite/userpath/applets/CustomClock/CustomClockApplet.lua
    20190308 04:18:55.375 INFO applet.SetupAppletInstaller – SetupAppletInstallerApplet.lua:534 extracting file: /root/.jivelite/userpath/applets/CustomClock/CustomClockMeta.lua
    20190308 04:18:55.376 INFO applet.SetupAppletInstaller – SetupAppletInstallerApplet.lua:534 extracting file: /root/.jivelite/userpath/applets/CustomClock/CustomSpectrumMeter.lua
    20190308 04:18:55.377 INFO applet.SetupAppletInstaller – SetupAppletInstallerApplet.lua:534 extracting file: /root/.jivelite/userpath/applets/CustomClock/CustomVUMeter.lua
    20190308 04:18:55.378 INFO jivelite.applets – AppletManager.lua:709 store settings: SetupAppletInstaller

    I need to into piCorePlayer to see how it handles the „!=“ and why this isn’t a problem there.

    Frank

    Heiner premium
    12. März 2019 at 17:33 #44754

    Hi Frank,

    Thank you for the detailed report.
    We will try to recreate the issue and see if your fix could be applied generally, should there be a need.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.

Register here