Turns out I’m not crazy after all (but neither of us are either presumably :-D). After digging long and well, i found out that the rPI Display 2 has this “disconnect” between its screen-rotation and its touch-rotation. In older rPI OS versions, they where combined in the settings.
When i booted up my latest&greatest OS version and after rotating the screen, i noticed that the touch was all over the place (e.g. touching the main dropdown menu to the left actually triggered the date-widget on the right) and no setting (as per above) would change that.
Apparently, in the “screen configuration” application, there are 2 separate steps needed to rotate them all:
both needs to be set. I assume this is how they are “lumped together”.
When i did both of them, of course touch will work flawlessly with rPI OS. Question now becomes what this “Goodix…” setting actually alters and if this can be altered correspondingly under Zynthian?
I understand that something called “XWayland” is what controls touch in later OSes. Would this be something that can be supported also under Zynthian?
and i followed his advice. And sure, now everything works just fine Display, touch, everything
Only problem for me is that everything is upside down. So why don’t i just flip the physical display and be content? Its the small fact that this display have a stand that screws on from the opposite side and while i tried to be “sneaky” and just try to rotate parts of the casing, i can’t really do that either as the lcd flat cable is too short and would collide with the USB ports
Any tricks to take every thing screen related and just make a 180 of it all?
Works stocastically it seems. Some reboots, all touch-points works fine. Other reboots, i have no touch working at all.
trying the “inverse” option and the same scenario plays out (works sometimes, won’t work sometimes) with the caveat that everything touch is now 180 degrees inverted.
Luckily, i can still run a mouse to control it, but its a bit weird.
Runs 100% on BookWorm. But i did notice (as i wrote above) that one has to re-orientate both the screen itself and the touch in separate steps (and i figure the same is needed here somehow)
I looked around and i found your post tunagenes and it seems you have struggled with basically the same thing as me :).
I truly appreciate your input on this. Thank you.
I have commented below and i start to think that somewhere there is some race-condition going on. Thats the only way i can explain it logically (but, who knows…)
Thx LFO. I believe the users in that thread uses HDMI displays and i’m not sure how that would translate to this DSI variant.
However, it sort of brings up this idea that it might be (?) some kind of race-condition happening. when i configure the display in BookWork, i have to rotate the screen and the touch separately. Perhaps touch needs to somehow always be “rotated” after the screen, not vice versa.
and it workd after the first reboot. then i could reboot again (using the zynthian UI) and when it was up again, nothing touch-related worked once again
Ghosts in the machine
edit. altering lcd_rotate to 1, rebooting and then restoring it to 2 once again (same as screen-shot above) and it works again after reboot.
Rebooting it again with these settings and touch is not working at all.
Rebooting a third time (same settings) and touch fully works again (incl. bold press right/top corner to bring up ui-buttons)
Rebooting a fourth time (same settings) it works again fully
Powering off fully, then on again and all works
Rebooting a final time and nothing works (no touch).
I might be completely wrong but it kind of feels like some race condition here.
had to reboot 3 more times (first two, no touch. Third time, touch is back again. Same setting. Weird)
@riban and @jofemodo is this something that would qualify as a bug? If so, i would be very glad to assist you in providing logs, etc. Just let me know
My screen is a 7” DSI (this model) and I had new hope after reading the linked thread. Even though the connection type is different, their issue about touch scaling described in the first post is exactly my problem.
My screen works flawlessly in Bookworm OS but in Zynthian I’ve not been able to overcome the issue despite repeated tinkering with config files.
I think in another screen problem thread Riban said to raise an issue but that it can be hard for devs to test without hardware in hand.
Indeed! I can work on software fixes for functional requirements, and non-functional requirements for official hardware. It is far more challenging to help with hardware that is not in the lab, beyond suggestions from experience. Custom builds are very much community supported. If someone choses to deviate from previously tested and proven hardware then they are in the great unknow wilderness of the adventurer-explorer. Best of luck but you may have to furrow your own path.
I don’t know in what order things may load (e.g. if touch can potentially load before the LCD and therefore fail to “attach” itself properly, etc) which is why i asked. But as it is now, it actually works quite nicely 8/10 times and thats quite good enough imho. I will dig into this issue some more (and i know there are other adventurers out there in the forum threads with a similar situation) so maybe something will turn up.
Ok, 30+ reboots later and it just works perfectly fine. Glitch in the matrix? Who knows. Now it behaves
But i wanted to ask a (probably silly) question. I notice that the “lanes” here are quite wide and that i need to press the arrow keys to scroll through them. Is there any way to make them more narrow in order to fit as many as possible onto the screen at once, without having to scroll?
Look into the chains (X, columns) and launchers (y, rows) settings in Admin. Specifically, the chains number controls the width of the chain strips in the Mixer view. I suggest you raise their number to 10 or 12.
Display, touch, everything
