Home of the Squeezebox™ & Transporter® network music players.
Page 14 of 14 FirstFirst ... 4121314
Results 131 to 139 of 139
  1. #131
    Junior Member
    Join Date
    Feb 2016
    Location
    France
    Posts
    18
    Quote Originally Posted by pavowren View Post
    after all that, touch is still off. wow.. should this be this hard?
    It's not for the impatient, certainly! It took me several weeks before all the pieces slotted into place, first with pCP 3.12 and then again on upgrading to pCP 3.5.0.

    Have you checked that pointercal and ts.conf are actually being restored on restart? What do you see in the output of ts_print?

    I understand that yours is an HDMI-connected screen, which quite possibly has completely different issues to the GPIO-connected devices.
    --
    Nick.

  2. #132
    Quote Originally Posted by Greg Erskine View Post
    hi pavowren,

    FYI, piCorePlayer supports the Official 7" Raspberry Pi Foundation screen. We made that decision assuming the majority of users would use the screen designed specifically for the Raspberry Pi.

    As you are finding out, there are probably a hundred screens with many different specs.

    You need to also consider the resolution of the available jivelite skins. The 800 x 600 resolution skins get more development as they are compatible with the Official 7" RPi screen. There has been efforts for jivelite to support additional resolutions but typically, resolutions that meet the Official 7" RPi screen or the original Squeezebox resolutions get greater attention.

    regards
    Greg
    hello greg, i hear what you are saying about the many resolutions and display sizes.
    and why the most common gets the attention of volunteer developer(s) and appreciate their efforts.
    but i guess i do not understand the complexity of handling the input; i mean it almost works!
    screen looks great via config.txt settings.
    ts_calibrate works but not quite.
    i'm just curious which module is specific to 7" 800x600 and the difficulty of making it "generic".

    well, i will be getting a 7" 1024x600 shortly, so i will see how it behaves as 800x600 device.
    curious george here
    pavo

  3. #133
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    1,505
    The jivelite skins are resolution dependent.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  4. #134
    Quote Originally Posted by paul- View Post
    The jivelite skins are resolution dependent.
    yeah sure that's the visual thing, not pointer accuracy.
    on max2play (which runs x), jivelite has no issues with touch accuracy.
    change to a whacky skin, the screen visually is off but the touch accuracy still remains.

    so i can only conclude there is an issue with tslib which i assume jivelite depends on.
    why is it verboten to install x on pCP?
    is x that fat?

    as you might have guessed, i really like and want to stick with pCP as long as i can...
    if only i can get this touch to work properly.

  5. #135
    Junior Member
    Join Date
    Aug 2010
    Location
    Copenhagen, Denmark
    Posts
    8

    3.5" Joy-IT screen, need help

    Hi,

    I just bought this 3.5" touch screen for my PcP 4.0 running on RPi 2B+ with LMS and USB disk.
    However the installation instructions for this screen are written for Raspbian OS.
    I have followed the guide written by bynowhinjing, but of course Jivelite doesn't work on this TFT. In fact I get the white screen only.
    In the Joy-IT instructions you need to edit two files, which are not present in PcP:
    /usr/share/X11/xorg.conf.d/99-fbturbo.conf
    /usr/share/X11/xorg.conf.d/99-calibration.conf
    I have created these two files in /mnt/mmcblk0p2/tce/ but I don't know how to include them. My Linux skills are weak.

    This is how 99-calibration.conf should read, according to Joy-IT:
    Section "InputClass"
    Identifier "calibration"
    MatchProduct "ADS7846 Touchscreen"
    Option "Calibration" "160 3723 3896 181"
    Option "SwapAxes" "1"
    Option "TransformationMatrix" "1 0 0 0 -1 1 0 0 1"
    EndSection

    This is 99-fbturbo.conf:
    Section "Device"
    Identifier "Allwinner A10/A13 FBDEV"
    Driver "fbturbo"
    Option "fbdev" "/dev/fb1"
    Option "SwapbuffersWait" "true"
    EndSection

    Hoping to hear from someone who will guide me.
    I would really love to get this screen up and running :-)
    Thank you!

    Jan
    Last edited by Jan Madsen; 2018-11-10 at 12:10.

  6. #136
    Junior Member
    Join Date
    Aug 2010
    Location
    Copenhagen, Denmark
    Posts
    8
    If I try to load the modules manually in Putty I get error:

    module flexfb not found in modules.dep

    sudo modprobe flexfb width=320 height=480 regwidth=16 init=-1,0xb0,0x0,-1,0x11,-2,250,-1,0x3A,0x55,-1,0xC2,0x44,-1,0xC5,0x00,0x00,0x00,0x00,-1,0xE0,0x0F,0x1F,0x1C,0x0C,0x0F,0x08,0x48,0x98,0x3 7,0x0A,0x13,0x04,0x11,0x0D,0x00,-1,0xE1,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x3 7,0x06,0x10,0x03,0x24,0x20,0x00,-1,0xE2,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x3 7,0x06,0x10,0x03,0x24,0x20,0x00,-1,0x36,0x28,-1,0x11,-1,0x29,-3

    sudo modprobe fbtft_device name=flexfb rotate=90 speed=16000000 gpios=reset:25,dc:24 txbuflen=32768 fps=50


    I guess my screen is not Waveshare compatible.

  7. #137
    Senior Member
    Join Date
    Jan 2016
    Location
    Germany
    Posts
    119
    @ Jan Madsen

    Do you come from Germany? Then maybe we could talk by PM.

  8. #138
    Junior Member
    Join Date
    Aug 2010
    Location
    Copenhagen, Denmark
    Posts
    8
    I have now Jivelite up and running on my Joy-IT 3.5" TFT :-)
    I succeded with the new 4.1.0 release and following nowhinjing's guide.
    Modifications to be made in do_rebootstuff.sh was done in pcp_startup.sh instead.

    Without luck I tried many, many times making it work in previous PcP versions, from 3.21 to 4.0.0.
    Today when I did I nowhinjing's modifications I loaded the extensions prior to installing Jivelite.
    Before I used to begin with the Jivelite installation, then followed by loading the extensions.
    Perhaps this was the reason for success...?

    However, I'm buying another screen, probably with HDMI interface, since the touch of this Joy-IT works no more.
    I've probably damaged the thin cable to the touch screen.

    Thanks to @piPlayer for his help on PM.

    /Jan
    Last edited by Jan Madsen; 2018-11-28 at 10:09.

  9. #139
    Junior Member
    Join Date
    Aug 2010
    Location
    Copenhagen, Denmark
    Posts
    8
    Update:
    Bought another Joy-IT screen and all works now, including touch.
    Pictures of my (upgraded) build here:
    http://2bak.blogspot.com/2018/12/pic...ll-in-one.html

Posting Permissions

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