This repository has been archived by the owner on Jun 25, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Touchscreen not responding #6
Comments
This is... weird. Did you try to touch everywhere on the screen to see if it was really unresponsive ? The top-right menu is quite hard to get, you need to touch at the corner of the screen to open it. |
I did tap all over - does the cursor move when you tap or is there any other indication? I didn't see any indication that it was responding whatsoever. |
Yeah the touchscreen moves the cursor when you touch it |
In that case, definitely not working because cursor never moved :(
In any case I'm not terribly worried about it, Lakka sounds more
interesting to me anyway, so I'll just wait to see if that works for me ^^
Thank you again for all your work making this possible :)
…On Sat, May 12, 2018 at 5:09 PM, Nathan S. ***@***.***> wrote:
Yeah the touchscreen moves the cursor when you touch it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AULFk-vShMeTUEctrATqaUx4wXteP69Gks5tx12DgaJpZM4T5Qab>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Heya, appreciate the work you've done man, having just one issue as of now.
Cannot get touchscreen to respond. I have tried multiple flashes of the card, multiple boots, etc. to no avail.
Switch is on 4.0.1 FWIW.
I know the cursor is supposed to be unresponsive.
As I understand tapping the top right is supposed to drop down a menu to connect to WiFi among other things however I cannot get them to respond. I know also the touchscreen is picky in Linux so I tapped around quite a few times in the general area of the top right to try and get it to come up and simply could not. I know it's running and now frozen as the volume buttons do bring up the dummy volume indicator.
Ideas my good sir?
The text was updated successfully, but these errors were encountered: