[Pre15] Touchscreen out of calibration

opencardev / crankshaft

Crankshaft: A turnkey GNU/Linux solution that transforms a Raspberry Pi to an Android Auto head unit.

http://getcrankshaft.com

GNU General Public License v3.0

2.15k stars 261 forks source link

[Pre15] Touchscreen out of calibration #274

Closed smartroad closed 5 years ago

smartroad commented 5 years ago

Really weired problem with offical screen touchpanel when I run CS in normal mode. When I press on the screen the touch doesn't line up with the input the Pi gets. See video:

https://youtu.be/PRjpbbtpgqE

When I boot into debug mode, the touch input is fine and correct.

What phone do you have? Nokia 8
What OS version? 8.1.0
What crankshaft version? Pre15
Steps to reproduce the bug, if you're planning to report a bug. Please indicate whether the bug is always repoducible. I was just trying to use the unit normally. Always seems to happen in normal mode but not in debug (using a USB stick with "DEBUG_ENABLE" file on it.

hawkeyexp commented 5 years ago

Not noticed until now but will check it.

smartroad commented 5 years ago

I was using the screen in the car and oddly, even having the debug option on, the same effect was happening. One other thing that I forgot to mention, this only seems to happen in the AA interface. In the settings menu everything seems to be right and responds correctly.

Just rolled back to NG14 and the input seems fine, I can report back tomorrow once I have it in the car again.

ghost commented 5 years ago

I've had the same issue. Thought it was an issue with my unofficial screen though

dinapappor commented 5 years ago

I had this too. But disconnecting the phone and tapping ok on the warning dialogue fixes it for me.

hawkeyexp commented 5 years ago

Seems to be solved now in current state i'm working on. Crazy behaviour.

HoLy1337 commented 5 years ago

Same here, a bug fix before Christmas would be very lovely!

Have to drive a lot

hawkeyexp commented 5 years ago

A fix before christmas is sure :-)

smartroad commented 5 years ago

Thanks hawkeyexp!! Was wondering, what was the issue?

hawkeyexp commented 5 years ago

Seems like the forced focus from the warning dialog caused it.