PiCorePlayer on pi zero 2 - possible touch improvements?

[andre1210]

Hi, I'm new to piCorePlayer.
I installed shortly piCoreplayer 8.1.0 fresh on a raspberry 4b with jivelite grid skin on an waveshare 7" LCD (H) 1024*600 resolution and hifiberry dac+
LMS is running on a different pi4.
Everything works fine. The touch is verry accurate. Response is quick.

After that I switched the configuration to a Pi zero 2w, instead of hifiberry dac+ I'm using a hifiberry dac (zero), but the same display.
Now everything is working too, but with one difference / problem:
Every 2-3 touch on the display opens a context menu. The response is sometimes quick and sometimes a bit delayed.
The cpu load (htop) shows continuously a load <= 0.1
What can be the cause? Is it possible to configure timings of the touch?
The response is not the problem, but the opening of the context menu instead of entering the menu.

Additional info for the touch device:
N: Name="STMicroelectronics 7H Custom Human interface Touchscreen"

thank you
regards
Andre

[paul-]

Have you ran any of the test programs that come with the ts library. (You have to stop jivelite to run them)

There are several different things you can change in the config file (ts.conf)

Take a look https://github.com/libts/tslib

Please note, if you change ts.conf, that file is not in the default backup set for pCP. you will need to add that file to /opt/.filetool.lst

[andre1210]

I used ts_calibrate for calibration. I observed that sometimes I had to touch twice until accepted.
With ts_test_mt I could see that the calibration was very good. With ts_test every touch was accepted.

In the jevelite menu it feels that the systems hangs sometimes for 0.5 - 1 seconds.
If a touch is done in that time, it seems that the touch is seen as "long" touch and the context menu opens.

I don't know with which parameter I should start changing for this issue.

[paul-]

It depends on what is causing it.

My guess is a sensitivity or touch threshold issue. Running the ts_test program should show you the touch data and then you have to decide.

[Greg Erskine]

My guess would be a hardware issue.

• a dirty screen
• insufficient power
• cable needs reseating
• protective plastic needs removing

[bpa]

Capacitive screen rely on moisture in the skin. Some screens have difficulty with people with dry/cold skin also often older people.

Check if this the problem by using as stylus (or gloves with special tips), wetting your finger, use moisturising cream, get hands warm etc.

[andre1210]

I has nothing to do with the touch itself (clean, no moisture, enough power - I also connected an additional power supply to the screen)
If I connect the screen to the pi 4 with picoreplayer, there is no issue.
Back to the zero 2, every second touch is considered as long click.
It feels like a timing issue due to the lower performance of the zero 2.

[andre1210]

The results of ts_test are accurate.
value 255 on touch and immediately 0 on release.
On which level is decided if it's a short or a long click? Is it done in jivelite?

[paul-]

That would be in jivelite.

One thing to remember is that jivelite has to load information from your LMS server. Its possible that delays in touch response are coming from jivelite waiting for information from LMS.

[andre1210]

LMS is running on a separate pi 4 with not much load and connected via lan.
The picoreplayers (zero and pi 4) are both wifi connected.
I do not think that the LMS is the root cause.

But another thought - can I configure jivelite to disable long presses?
I do not need the context menu.