Home of the Squeezebox™ & Transporter® network music players.
Page 98 of 161 FirstFirst ... 488896979899100108148 ... LastLast
Results 971 to 980 of 1601
  1. #971
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    3,036
    That device likely emulates a usb keyboard. The link in your post is broken.
    If that is the case then jivelite will read the keypresses from the inputX device automatically.

    You can check by running this command from an ssh connection to pcp and see if you have any keyboards listed. Here's mine as an example.

    Code:
    dmesg | grep input
    
    [    3.494242] input: Smart Smart Wireless Device as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:25A7:0701.0001/input/input0
    [    3.564421] hid-generic 0003:25A7:0701.0001: input,hidraw0: USB HID v1.01 Keyboard [Smart Smart Wireless Device] on usb-20980000.usb-1.5/input0
    [    3.583361] input: Smart Smart Wireless Device as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.5/1-1.5:1.1/0003:25A7:0701.0002/input/input1
    [    3.584142] hid-generic 0003:25A7:0701.0002: input,hidraw1: USB HID v1.01 Mouse [Smart Smart Wireless Device] on usb-20980000.usb-1.5/input1
    [    3.607729] input: Smart Smart Wireless Device as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.5/1-1.5:1.2/0003:25A7:0701.0003/input/input2
    [    3.678659] hid-generic 0003:25A7:0701.0003: input,hiddev96,hidraw2: USB HID v1.01 Device [Smart Smart Wireless Device] on usb-20980000.usb-1.5/input2
    [   24.937267] input: FT5406 memory based driver as /devices/virtual/input/input3
    [   70.361731] input: lircd-uinput as /devices/virtual/input/input4
    If it does, then you need to determine the keycodes the keys send using evtest and change InputToActionMap.lua accordingly.

    Start with event0 if you have no other keyboard devices connected. evtest first lists all the keys that your device supports.

    First download and install evtest
    Code:
    ceo
    
    wget http://ralph-irving.users.sourceforge.net/pico/evtest.tcz.md5.txt
    
    wget http://ralph-irving.users.sourceforge.net/pico/evtest.tcz
    
    md5sum -c evtest.tcz.md5.txt
    evtest.tcz: OK
    
    tce-load -i evtest
    evtest.tcz: OK
    Then run evtest as root

    Code:
    sudo evtest
    
    No device specified, trying to scan all of /dev/input/event*
    Available devices:
    /dev/input/event0:	Smart Smart Wireless Device
    /dev/input/event1:	Smart Smart Wireless Device
    /dev/input/event2:	Smart Smart Wireless Device
    /dev/input/event3:	FT5406 memory based driver
    /dev/input/event4:	lircd-uinput
    Select the device event number [0-4]: 0
    Input driver version is 1.0.1
    Input device ID: bus 0x3 vendor 0x25a7 product 0x701 version 0x101
    Input device name: "Smart Smart Wireless Device"
    Supported events:
      Event type 0 (EV_SYN)
      Event type 1 (EV_KEY)
        Event code 1 (KEY_ESC)
        Event code 2 (KEY_1)
        Event code 3 (KEY_2)
        Event code 4 (KEY_3)
        Event code 5 (KEY_4)
        Event code 6 (KEY_5)
        Event code 7 (KEY_6)
        Event code 8 (KEY_7)
        Event code 9 (KEY_8)
        Event code 10 (KEY_9)
        Event code 11 (KEY_0)
        Event code 12 (KEY_MINUS)
        Event code 13 (KEY_EQUAL)
        Event code 14 (KEY_BACKSPACE)
        Event code 15 (KEY_TAB)
        Event code 16 (KEY_Q)
        Event code 17 (KEY_W)
        Event code 18 (KEY_E)
        Event code 19 (KEY_R)
        Event code 20 (KEY_T)
        Event code 21 (KEY_Y)
        Event code 22 (KEY_U)
        Event code 23 (KEY_I)
        Event code 24 (KEY_O)
        Event code 25 (KEY_P)
        Event code 26 (KEY_LEFTBRACE)
        Event code 27 (KEY_RIGHTBRACE)
        Event code 28 (KEY_ENTER)
        Event code 29 (KEY_LEFTCTRL)
        Event code 30 (KEY_A)
        Event code 31 (KEY_S)
        Event code 32 (KEY_D)
        Event code 33 (KEY_F)
        Event code 34 (KEY_G)
        Event code 35 (KEY_H)
        Event code 36 (KEY_J)
        Event code 37 (KEY_K)
        Event code 38 (KEY_L)
        Event code 39 (KEY_SEMICOLON)
        Event code 40 (KEY_APOSTROPHE)
        Event code 41 (KEY_GRAVE)
        Event code 42 (KEY_LEFTSHIFT)
        Event code 43 (KEY_BACKSLASH)
        Event code 44 (KEY_Z)
        Event code 45 (KEY_X)
        Event code 46 (KEY_C)
        Event code 47 (KEY_V)
        Event code 48 (KEY_B)
        Event code 49 (KEY_N)
        Event code 50 (KEY_M)
        Event code 51 (KEY_COMMA)
        Event code 52 (KEY_DOT)
        Event code 53 (KEY_SLASH)
        Event code 54 (KEY_RIGHTSHIFT)
        Event code 55 (KEY_KPASTERISK)
        Event code 56 (KEY_LEFTALT)
        Event code 57 (KEY_SPACE)
        Event code 58 (KEY_CAPSLOCK)
        Event code 59 (KEY_F1)
        Event code 60 (KEY_F2)
        Event code 61 (KEY_F3)
        Event code 62 (KEY_F4)
        Event code 63 (KEY_F5)
        Event code 64 (KEY_F6)
        Event code 65 (KEY_F7)
        Event code 66 (KEY_F8)
        Event code 67 (KEY_F9)
        Event code 68 (KEY_F10)
        Event code 69 (KEY_NUMLOCK)
        Event code 70 (KEY_SCROLLLOCK)
        Event code 71 (KEY_KP7)
        Event code 72 (KEY_KP8)
        Event code 73 (KEY_KP9)
        Event code 74 (KEY_KPMINUS)
        Event code 75 (KEY_KP4)
        Event code 76 (KEY_KP5)
        Event code 77 (KEY_KP6)
        Event code 78 (KEY_KPPLUS)
        Event code 79 (KEY_KP1)
        Event code 80 (KEY_KP2)
        Event code 81 (KEY_KP3)
        Event code 82 (KEY_KP0)
        Event code 83 (KEY_KPDOT)
        Event code 86 (KEY_102ND)
        Event code 87 (KEY_F11)
        Event code 88 (KEY_F12)
        Event code 96 (KEY_KPENTER)
        Event code 97 (KEY_RIGHTCTRL)
        Event code 98 (KEY_KPSLASH)
        Event code 99 (KEY_SYSRQ)
        Event code 100 (KEY_RIGHTALT)
        Event code 102 (KEY_HOME)
        Event code 103 (KEY_UP)
        Event code 104 (KEY_PAGEUP)
        Event code 105 (KEY_LEFT)
        Event code 106 (KEY_RIGHT)
        Event code 107 (KEY_END)
        Event code 108 (KEY_DOWN)
        Event code 109 (KEY_PAGEDOWN)
        Event code 110 (KEY_INSERT)
        Event code 111 (KEY_DELETE)
        Event code 119 (KEY_PAUSE)
        Event code 125 (KEY_LEFTMETA)
        Event code 126 (KEY_RIGHTMETA)
        Event code 127 (KEY_COMPOSE)
      Event type 4 (EV_MSC)
        Event code 4 (MSC_SCAN)
      Event type 17 (EV_LED)
        Event code 0 (LED_NUML) state 0
        Event code 1 (LED_CAPSL) state 0
        Event code 2 (LED_SCROLLL) state 0
        Event code 3 (LED_COMPOSE) state 0
        Event code 4 (LED_KANA) state 0
    Key repeat handling:
      Repeat type 20 (EV_REP)
        Repeat code 0 (REP_DELAY)
          Value    250
        Repeat code 1 (REP_PERIOD)
          Value     33
    Properties:
    Testing ... (interrupt to exit)
    Event: time 1554897601.288897, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028
    Event: time 1554897601.288897, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
    Event: time 1554897601.288897, -------------- SYN_REPORT ------------
    Event: time 1554897601.428877, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028
    Event: time 1554897601.428877, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
    Event: time 1554897601.428877, -------------- SYN_REPORT ------------
    Event: time 1554897604.016909, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70029
    Event: time 1554897604.016909, type 1 (EV_KEY), code 1 (KEY_ESC), value 1
    Event: time 1554897604.016909, -------------- SYN_REPORT ------------
    Event: time 1554897604.132926, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70029
    Event: time 1554897604.132926, type 1 (EV_KEY), code 1 (KEY_ESC), value 0
    Event: time 1554897604.132926, -------------- SYN_REPORT ------------
    Event: time 1554897892.021775, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70009
    Event: time 1554897892.021775, type 1 (EV_KEY), code 33 (KEY_F), value 1
    Event: time 1554897892.021775, -------------- SYN_REPORT ------------
    Event: time 1554897892.117800, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70009
    Event: time 1554897892.117800, type 1 (EV_KEY), code 33 (KEY_F), value 0
    Event: time 1554897892.117800, -------------- SYN_REPORT ------------
    Event: time 1554897896.441642, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7000b
    Event: time 1554897896.441642, type 1 (EV_KEY), code 35 (KEY_H), value 1
    Event: time 1554897896.441642, -------------- SYN_REPORT ------------
    Event: time 1554897896.593674, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7000b
    Event: time 1554897896.593674, type 1 (EV_KEY), code 35 (KEY_H), value 0
    Event: time 1554897896.593674, -------------- SYN_REPORT ------------
    This post describes how to modify the InputToActionMap.lua
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 2-UE Radio
    Squeezebox client builds donations always appreciated.

  2. #972
    Senior Member JadeMonkee's Avatar
    Join Date
    Oct 2008
    Location
    Somerset, UK
    Posts
    217
    Quote Originally Posted by ralphy View Post
    That device likely emulates a usb keyboard. The link in your post is broken.
    I've updated the link now, thanks.

    Quote Originally Posted by ralphy View Post
    If that is the case then jivelite will read the keypresses from the inputX device automatically.
    Indeed, I can confirm that Jivelite responds to keypresses (just not all of them - I have found out that it sends media key signals for play/pause, which Jivelite doesn't react to).

    Are the codes contained in the OSMC lircd.conf file the ones I need? Or will evtest return different codes?

    The codes from my modified config are:

    Code:
     begin codes
              KEY_N                    0x0F # home/now playing
              KEY_T                    0x10 # i (current track info)
              KEY_UP                   0x11 # up
              KEY_DOWN                 0x13 # down
              KEY_LEFT                 0x15 # left
              KEY_RIGHT                0x12 # right
              KEY_ENTER                0x14 # OK
              KEY_ESC                  0x16 # back
              KEY_RIGHTBRACE           0x17 # menu (go playlist)
              KEY_C                    0x18 # play/pause
              KEY_G                    0x19 # stop (think of something better)
              KEY_Z                    0x1A # rwd (jump rewind)
              KEY_B                    0x1B # ffwd (jump forward)
              #KEY_VOLUMEUP             0x1B # for newer OSMC remote
              #KEY_VOLUMEDOWN           0x1A # for newer OSMC remote
          end codes
    I'll have a go at re-mapping the keys later today. Thanks for your help.
    Active: 1x Transporter | 1x Classic | 2 x Receiver | 2x Raspberry Pi (1x 2B, 1x 3B) w/ piCorePlayer, Jivelite, 7" touch screen (controlling 2x Receivers) | OrangeSqueeze as Android controller
    Deprecated: 1x Classic | 2x Boom| 2x Receiver | 2x Controllers (aka the dark and terrible things that shall not be used again)
    LMS v8.1.1 running as a Docker in Unraid on a HP MicroServer gen8
    5916 albums with 47950 songs by 11001 artists - and always growing

  3. #973
    Senior Member JadeMonkee's Avatar
    Join Date
    Oct 2008
    Location
    Somerset, UK
    Posts
    217
    Ok I'm trying it out now, but am a bit confused to how I know which value from evtest to put into InputToActionMap.lua

    evtest returned the following (my remote appears as two devices, so here it is for both event1 and event2):
    event1:
    Code:
    Event: time 1554903250.115956, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004a
    Event: time 1554903250.115956, type 1 (EV_KEY), code 102 (KEY_HOME), value 1
    Event: time 1554903250.115956, -------------- SYN_REPORT ------------
    Event: time 1554903250.131933, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004a
    Event: time 1554903250.131933, type 1 (EV_KEY), code 102 (KEY_HOME), value 0
    Event: time 1554903250.131933, -------------- SYN_REPORT ------------
    Event: time 1554903253.515961, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70052
    Event: time 1554903253.515961, type 1 (EV_KEY), code 103 (KEY_UP), value 1
    Event: time 1554903253.515961, -------------- SYN_REPORT ------------
    Event: time 1554903253.532053, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70052
    Event: time 1554903253.532053, type 1 (EV_KEY), code 103 (KEY_UP), value 0
    Event: time 1554903253.532053, -------------- SYN_REPORT ------------
    Event: time 1554903254.467968, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70051
    Event: time 1554903254.467968, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
    Event: time 1554903254.467968, -------------- SYN_REPORT ------------
    Event: time 1554903254.524039, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70051
    Event: time 1554903254.524039, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
    Event: time 1554903254.524039, -------------- SYN_REPORT ------------
    Event: time 1554903255.387954, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70050
    Event: time 1554903255.387954, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
    Event: time 1554903255.387954, -------------- SYN_REPORT ------------
    Event: time 1554903255.411928, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70050
    Event: time 1554903255.411928, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
    Event: time 1554903255.411928, -------------- SYN_REPORT ------------
    Event: time 1554903256.307955, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004f
    Event: time 1554903256.307955, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
    Event: time 1554903256.307955, -------------- SYN_REPORT ------------
    Event: time 1554903256.339945, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004f
    Event: time 1554903256.339945, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
    Event: time 1554903256.339945, -------------- SYN_REPORT ------------
    Event: time 1554903258.899956, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028
    Event: time 1554903258.899956, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
    Event: time 1554903258.899956, -------------- SYN_REPORT ------------
    Event: time 1554903258.923932, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028
    Event: time 1554903258.923932, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
    Event: time 1554903258.923932, -------------- SYN_REPORT ------------
    And for event2:
    Code:
    Event: time 1554903383.515952, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0060
    Event: time 1554903383.515952, type 1 (EV_KEY), code 358 (KEY_INFO), value 1
    Event: time 1554903383.515952, -------------- SYN_REPORT ------------
    Event: time 1554903383.547939, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0060
    Event: time 1554903383.547939, type 1 (EV_KEY), code 358 (KEY_INFO), value 0
    Event: time 1554903383.547939, -------------- SYN_REPORT ------------
    Event: time 1554903391.227953, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0224
    Event: time 1554903391.227953, type 1 (EV_KEY), code 158 (KEY_BACK), value 1
    Event: time 1554903391.227953, -------------- SYN_REPORT ------------
    Event: time 1554903391.243945, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0224
    Event: time 1554903391.243945, type 1 (EV_KEY), code 158 (KEY_BACK), value 0
    Event: time 1554903391.243945, -------------- SYN_REPORT ------------
    Event: time 1554903392.187953, type 4 (EV_MSC), code 4 (MSC_SCAN), value 10084
    Event: time 1554903392.187953, type 1 (EV_KEY), code 438 (KEY_CONTEXT_MENU), value 1
    Event: time 1554903392.187953, -------------- SYN_REPORT ------------
    Event: time 1554903392.203934, type 4 (EV_MSC), code 4 (MSC_SCAN), value 10084
    Event: time 1554903392.203934, type 1 (EV_KEY), code 438 (KEY_CONTEXT_MENU), value 0
    Event: time 1554903392.203934, -------------- SYN_REPORT ------------
    Event: time 1554903393.163952, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00cd
    Event: time 1554903393.163952, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
    Event: time 1554903393.163952, -------------- SYN_REPORT ------------
    Event: time 1554903393.179934, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00cd
    Event: time 1554903393.179934, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
    Event: time 1554903393.179934, -------------- SYN_REPORT ------------
    Event: time 1554903393.883952, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0226
    Event: time 1554903393.883952, type 1 (EV_KEY), code 128 (KEY_STOP), value 1
    Event: time 1554903393.883952, -------------- SYN_REPORT ------------
    Event: time 1554903393.899933, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0226
    Event: time 1554903393.899933, type 1 (EV_KEY), code 128 (KEY_STOP), value 0
    Event: time 1554903393.899933, -------------- SYN_REPORT ------------
    Event: time 1554903394.555946, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00b4
    Event: time 1554903394.555946, type 1 (EV_KEY), code 168 (KEY_REWIND), value 1
    Event: time 1554903394.555946, -------------- SYN_REPORT ------------
    Event: time 1554903394.571935, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00b4
    Event: time 1554903394.571935, type 1 (EV_KEY), code 168 (KEY_REWIND), value 0
    Event: time 1554903394.571935, -------------- SYN_REPORT ------------
    Event: time 1554903395.243945, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00b3
    Event: time 1554903395.243945, type 1 (EV_KEY), code 208 (KEY_FASTFORWARD), value 1
    Event: time 1554903395.243945, -------------- SYN_REPORT ------------
    Event: time 1554903395.259933, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00b3
    Event: time 1554903395.259933, type 1 (EV_KEY), code 208 (KEY_FASTFORWARD), value 0
    Event: time 1554903395.259933, -------------- SYN_REPORT ------------
    So, in InputToActionMap.lua, do I change the values under 'keyActionMappings', putting in the 'KEY_FASTFORWARD' (for example) values?
    Or do I have to translate the key press codes (eg for KEY_FASTFORWARD code 208? or value c00b3?) to a keyboard equivalent and modify the section under 'charActionMappings' ?

    Sorry for my noobness!
    Active: 1x Transporter | 1x Classic | 2 x Receiver | 2x Raspberry Pi (1x 2B, 1x 3B) w/ piCorePlayer, Jivelite, 7" touch screen (controlling 2x Receivers) | OrangeSqueeze as Android controller
    Deprecated: 1x Classic | 2x Boom| 2x Receiver | 2x Controllers (aka the dark and terrible things that shall not be used again)
    LMS v8.1.1 running as a Docker in Unraid on a HP MicroServer gen8
    5916 albums with 47950 songs by 11001 artists - and always growing

  4. #974
    Senior Member JadeMonkee's Avatar
    Join Date
    Oct 2008
    Location
    Somerset, UK
    Posts
    217
    Ok I thought I'd have a go at it, but I haven't had much luck.
    I started by doing the following (as per this post https://forums.slimdevices.com/showt...l=1#post883651):
    Code:
    sudo mkdir /home/tc/.jivelite/userpath/jive/
    sudo cp -L /opt/jivelite/share/jive/jive/InputToActionMap.lua /home/tc/.jivelite/userpath/jive/InputToActionMap.lua
    cd /home/tc/.jivelite/userpath/jive/
    sudo vi InputToActionMap.lua
    Then added below the existing entries in:
    keyActionMappings = {}
    keyActionMappings.press = {
    (but before the final closing bracket)
    Code:
    --BEGIN my OSMC Remote mappings. I've commented out existing maps
    --event1 keys
        --[KEY_HOME] = 
        --[KEY_UP] = 
        --[KEY_DOWN] = 
        --[KEY_LEFT] = 
        --[KEY_RIGHT] = 
        --[KEY_ENTER] = 
    --event2 keys
        [KEY_INFO] = "go_current_track_info",
        --[KEY_BACK] = 
        [KEY_CONTEXT_MENU] = "volume_up",
        [KEY_PLAYPAUSE] = "pause",
        [KEY_STOP] = "volume_down",
        [KEY_REWIND] = "jump_rew",
        [KEY_FASTFORWARD] = "jump_fwd",
    --END my OSMC Remote mappings
    Backed up my changes via the web menu and rebooted.
    But Jivelite doesn't even start.
    As soon as I RE-copy a fresh version of /opt/jivelite/share/jive/jive/InputToActionMap.lua into /home/tc/.jivelite/userpath/jive/InputToActionMap.lua Jivelite immediately starts.

    What have I done wrong?

    Thanks for your help - and sorry for taking up so much of your time!
    Active: 1x Transporter | 1x Classic | 2 x Receiver | 2x Raspberry Pi (1x 2B, 1x 3B) w/ piCorePlayer, Jivelite, 7" touch screen (controlling 2x Receivers) | OrangeSqueeze as Android controller
    Deprecated: 1x Classic | 2x Boom| 2x Receiver | 2x Controllers (aka the dark and terrible things that shall not be used again)
    LMS v8.1.1 running as a Docker in Unraid on a HP MicroServer gen8
    5916 albums with 47950 songs by 11001 artists - and always growing

  5. #975
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,233
    I've set up a Pi Zero W running pCP 4.1.0 to act solely as a 'Now Playing' display for my TV via HDMI - neither LMS nor Squeezelite is enabled on the Pi.

    It works well, but the image isn't filling my screen. The TV has a native resolution of 1920 x 1080, but when I select the HD skin with this resolution (or the HD Grid skin), Jivelite simply restarts.

    The biggest skin I can get to work is HD 1280 x 1024. At this resolution, the only 'Now Playing' view that's offered is 'Artwork and Text' (which is perfect, because it's not a touch screen, so I don't need the controls, but some other display views could be useful). The only wallpaper that's offered is 'Black', although if I activate the Joggler skin first then the selected wallpaper appears 'tiled' behind the HD 1280 x 1024 skin.

    So I'd appreciate advice on a few issues:
    1) Why does the HD 1920 x 1080 skin cause Jivelite to restart? Is this a known 'to do' on pCP, or a problem with my specific setup?
    2) Where should I put bigger wallpapers? On a conventional Jivelite installation I know that they go in...
    Code:
    /opt/jivelite/share/jive/applets/SetupWallpaper/wallpaper
    ...but in pCP that seems to be a symlink to...
    Code:
    /tmp/tcloop/pcp-jivelite/opt/jivelite/share/jive/applets/SetupWallpaper/wallpaper
    ...and that doesn't seem like it'll survive a reboot. And while I'm at it, what prefix is required for a wallpaper at this resolution?
    3) Is it a significant task for me to create additional 'Now Playing' views for this resolution?

  6. #976
    Senior Member Jeff07971's Avatar
    Join Date
    Aug 2011
    Location
    London, England
    Posts
    1,800
    Hi,

    You need to edit config.txt to allow the console to be 1920x1080

    Code:
    # uncomment to force a console size. By default it will be display's size minus
    # overscan.
    framebuffer_width=1920
    framebuffer_height=1080
    As to the wallpapers not surviving a reboot, are you backing up before rebooting ?

    Try "pcp ?" from the cli for options

    Jeff

    Want a webapp ? Get SqueezeLite-X ! https://forums.slimdevices.com/showt...l=1#post903953

  7. #977
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,233
    Thanks Jeff - will give those a try.

  8. #978
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,233
    Quote Originally Posted by Jeff07971 View Post
    Hi,

    You need to edit config.txt to allow the console to be 1920x1080
    Wait - where is that? I found /usr/local/sbin/config.cfg, but that code isn't present in that file. There's no sign of a config.txt that I can find.

  9. #979
    Senior Member Jeff07971's Avatar
    Join Date
    Aug 2011
    Location
    London, England
    Posts
    1,800
    Quote Originally Posted by chill View Post
    Wait - where is that? I found /usr/local/sbin/config.cfg, but that code isn't present in that file. There's no sign of a config.txt that I can find.
    Name:  2019-04-13 11_36_58-Window.jpg
Views: 542
Size:  10.9 KB



    Don't forget to backup !

    Want a webapp ? Get SqueezeLite-X ! https://forums.slimdevices.com/showt...l=1#post903953

  10. #980
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,233
    Got it - in the root of the SD card. So now the display fills the screen - thank you.

    Will investigate wallpapers and Now Playing views later.

    EDIT: Posts crossed. I found it by putting the SD card into the laptop's card reader.

Tags for this Thread

Posting Permissions

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