Home of the Squeezebox™ & Transporter® network music players.
Page 8 of 119 FirstFirst ... 6789101858108 ... LastLast
Results 71 to 80 of 1189
  1. #71
    Senior Member
    Join Date
    Feb 2015
    Posts
    196
    Quote Originally Posted by tomster View Post
    Hi guys!

    I just got my original RasPi 7" touch screen arriving in the mail today. After having it put all together and fired up with PiCorePlayer 1.21b I can find the touch input is not working. JiveLite would start up keeping me stuck on the "Choose Language" screen...
    Am I missing something or is the touch feature simply not yet supported?
    Thx for a quick reply.
    Regards,
    Tom
    Tom,

    The current version of piCorePlayer does not support the touch interface. Easiest thing to do is attach a USB mouse or keyboard to configure JiveLite. Then quit JiveLite using the [Quit] button on the home screen to save changes. This does not always work for me (changes does not survive a reboot), so to be sure I use piCorePlayer's web interface to backup the settings using the "[Backup] Backup your changes" button on the main page (for this button to be visible you have to select the beta tab at the bottom of the page).

    I use a FLIRC adapter in combination with an original Squeezebox remote to emulate a keyboard.

  2. #72
    Junior Member
    Join Date
    Oct 2015
    Posts
    24
    Kolossos,

    thank you for your reply. In the meantime I did exactly what you suggested. So now Jivelite would at least start into normal Display mode.
    FLIRC support will be added in the next days as those dongles arrived yesterday.

    For the complete user experience (the devices should act in each kids room as their players) I would really fancy the touch-thingy though.
    Let's see what Steen and Ralphy will come up with. At least Steen has got a genuine RasPi display I guess...
    Last edited by tomster; 2015-10-22 at 07:53.

  3. #73
    Senior Member sbp's Avatar
    Join Date
    Apr 2010
    Location
    Denmark
    Posts
    1,175
    Hi Tom

    Thank you for your mails regarding the touch screen. Maybe we should continue the discussion here, so we can help each other with the issues.

    The problems right now are:
    1. The calibration of the touch gesture and the Jivelite GUI is off. In the middle of the screen it seems accurate, however when we go closer to the frame (up/down/left and right) the distance increase.
    2. There is a mouse cursor when we use the touch function.

    Any other issues - please report them.

    Steen
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like piCorePlayer

  4. #74
    Junior Member
    Join Date
    Oct 2015
    Posts
    24
    Sure, no prob.

    I've been playing around a bit with config.txt and changed several boot options.
    When I set either
    Code:
    framebuffer_width=800
    framebuffer_height=480
    or
    Code:
    vga=800x480
    I get a full-screen Joggler-skin. But this only seems to have an effect on the screen layout not on the touch driver/ calibration/grid.
    Also the offset seems to be bigger the smaller the chosen resolution is...

  5. #75
    Junior Member
    Join Date
    Oct 2015
    Posts
    24
    Yep. The offset is significantly less compared to 800x480 when I set framebuffer to 1920x1080.
    Still off too much though...

  6. #76
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,473
    Quote Originally Posted by sbp View Post
    Hi Tom

    Thank you for your mails regarding the touch screen. Maybe we should continue the discussion here, so we can help each other with the issues.

    The problems right now are:
    1. The calibration of the touch gesture and the Jivelite GUI is off. In the middle of the screen it seems accurate, however when we go closer to the frame (up/down/left and right) the distance increase.
    2. There is a mouse cursor when we use the touch function.

    Any other issues - please report them.

    Steen
    I have the mouse pointer disabled on my latest test build.

    There is code in jivelite to unhide the mouse pointer when it detects movement and hide it after a timeout. As I didn't what to change the default behaviour, I check for an environment variable on startup and always disable the mouse pointer if it's defined.

    Now on to the calibration issue....
    Ralphy

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

  7. #77
    Senior Member sbp's Avatar
    Join Date
    Apr 2010
    Location
    Denmark
    Posts
    1,175
    Quote Originally Posted by ralphy View Post
    I have the mouse pointer disabled on my latest test build.

    There is code in jivelite to unhide the mouse pointer when it detects movement and hide it after a timeout. As I didn't what to change the default behaviour, I check for an environment variable on startup and always disable the mouse pointer if it's defined.
    Good - one issue solved


    Quote Originally Posted by ralphy View Post
    Now on to the calibration issue....
    Regarding the calibration issue.
    I started like Tom to use different sizes in the config.txt file. But was unable to find a setting that was perfect.
    I also have been reading and I googled a lot.
    This now led me to believe that we might need to make a tslib.tcz package in order to calibrate our touch screen.
    http://udoo.org/forum/threads/solved...mebuffer.1342/
    and
    https://github.com/notro/fbtft/wiki/Touchpanel
    http://elinux.org/Leapster_Explorer:...screen_Library

    Is that correct, or are there other options to calibrate the touch screen
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like piCorePlayer

  8. #78
    Junior Member
    Join Date
    Oct 2015
    Posts
    24
    I guess we have been reading the same pages ;-)

    tslib was also my come-up. Though that's only a shot in the dark.
    Maybe there's a tool to get the raw data of the touch inputs. This could help finding the correct coefficient for calibration...

  9. #79
    Senior Member sbp's Avatar
    Join Date
    Apr 2010
    Location
    Denmark
    Posts
    1,175
    Quote Originally Posted by tomster View Post
    I guess we have been reading the same pages ;-)

    tslib was also my come-up. Though that's only a shot in the dark.
    Maybe there's a tool to get the raw data of the touch inputs. This could help finding the correct coefficient for calibration...
    You Can install the evtest.tcz package, this Will show you the registeret events.
    However,. I did not manage to get any useful information.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like piCorePlayer

  10. #80
    Junior Member
    Join Date
    Oct 2015
    Posts
    24
    BTW, is there a way to also turn-off backlighting when the "blank" screen-saver is active?
    Doesn't make much sense to blank the screen and keep the backlighting on all the time, right?

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
  •