kennyliveforever wrote:
> ... but after reboot with Jivelite autostart touch doesn't work again.
I haven't upgraded my pCP+Waveshare beyond v3.5, but 'this post'
(https://forums.slimdevices.com/showthread.php?107366-picoreplayer-3-11-waveshare-3-5-TFT-jivelite-Raspberry-Pi-2B&p=911762&viewfull=
pavowren wrote:
> 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.
CraziFuzzy wrote:
> The 4 inch 320x480 touchscreens appear to be the perfect size to allow
> some of the stainless bezel to remain - my question is that I have not
> really seen any definitive answer whether JiveLite displays properly on
> a portrait and/or low resolution screen.
The screen res
pavowren wrote:
> however touch is "off" ...
Also have a look earlier in this thread (start around 'here'
(https://forums.slimdevices.com/showthread.php?108852-Announce-piCorePlayer-3-5-0&p=913389&viewfull=1#post913389)).
See what out put you get for ts_print – if you don't see the zero
at the
Solved for pCP 3.5.0 + Waveshare 35B!
Comparing the ts.conf file between pCP 3.22 and 3.5.0, it seems to have
lost a few lines. This works for me:
Code:
$ cat /usr/local/etc/ts.conf
module_raw input
module pthres pmin=1
module variance delta=30
module dejitter del
TheChrisP wrote:
> Out of curiosity, what are the result you get when doing a ts_print and
> a ts_print raw ? Especially the data you get when you release the
> touchscreen ?
I didn't get as far as looking into tslib, nor using any of the other
ts_ utilities (I didn't know they were there ...). I
