Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Touchpad does not work when using SlimPort #301

Open
3arn0wl opened this issue Oct 17, 2017 · 26 comments

Comments

Projects
None yet
@3arn0wl
Copy link

commented Oct 17, 2017

  • Device: Nexus 5 - Hammerhead
  • Channel: stable
  • Build: OTA-2

Steps to reproduce

Connect the device to a screen using a SlimPort adapter.

Expected behaviour

The devices screen turns into a touchpad and a cursor shows up on the screen it's connected to.

Actual behaviour

Touch-pad does not work, no cursor shows up.

@samzanemesis

This comment has been minimized.

Copy link

commented Oct 18, 2017

I would like to add to this issue, the real bug is that the screen can't be used as a touchpad, a bluetooth mouse works fine

Seems touchscreen works, as the indicator to use the screen as a touchpad fades away when you swipe it, but there is no activity on the mains creen

I'm with a Hammerhead on devel

@NeoTheThird NeoTheThird changed the title No pointer or mouse activity when using SlimPort Touchpad does not work when using SlimPort Oct 19, 2017

@NeoTheThird

This comment has been minimized.

Copy link
Member

commented Oct 19, 2017

Thanks @samzanemesis, i updated the report. Can someone reproduce and confirm this?

@scastren

This comment has been minimized.

Copy link

commented Oct 19, 2017

This happened to me as well. I flashed my Nexus 5 right after the first version of UT of UBports was released. When I tested my N5 with SlimPort adapter (which work nicely with the UT version from Canonical) there was no mouse activity when touching the screen of the phone.

@mauricioduarte01

This comment has been minimized.

Copy link

commented Nov 19, 2017

Hi,
I can reconfirm this. I though this was fixed or something like that because I was seeing some users in the UBports Telegram SG talking about this, but as soon I tried connect my N5 via Slimport to my TV, the device screen just fade out and nothing else happens, I can just use the screen keyboard to unblock the session and thats it. No Touchpad support. Just a white screen. If this was working well with UT from canonical I think this should reviewed because having to use a bluetooth mouse/keyboard to enable the mouse pointer its a huge deal.

@SwizzleMaster

This comment has been minimized.

Copy link

commented Feb 6, 2018

I have the same issue on a fresh hammerhead installation, OTA3 ( I tried both stable and dev channel ) + slimport cable

@ezickler

This comment has been minimized.

Copy link

commented Mar 15, 2018

Same here

@NeoTheThird NeoTheThird added bug and removed needs confirmation labels Mar 15, 2018

@ruedigerkupper

This comment has been minimized.

Copy link

commented Mar 18, 2018

Confirmed.

@simoxxx

This comment has been minimized.

Copy link

commented Mar 19, 2018

I can confirm this bug on xenial too.
(on nexus 4 this feature works fine on both releases vivid and xenial)

@pom3ranc86

This comment has been minimized.

Copy link

commented Apr 20, 2018

Confirmed.

@abkro

This comment has been minimized.

Copy link

commented Jun 6, 2018

Confirmed on Nexus 5 hammerhead running Xenial r415. @NeoTheThird do you need logs or something? I could post them...

@NeoTheThird

This comment has been minimized.

Copy link
Member

commented Jun 9, 2018

@abkro Not sure if it will log something, but dmesg and logcat never hurt.

@abkro

This comment has been minimized.

Copy link

commented Jun 9, 2018

OK. Just confirmed that there's no change on r419. I'll update here and post the logs within a couple of hours. I'll just edit this comment and paste them in here.

@abkro

This comment has been minimized.

Copy link

commented Jun 9, 2018

@NeoTheThird I connected my Nexus 5 now running r419 today. Same problem, no change. Here are the logs.

UTdmesg.txt
UTlogcat.txt

@samzanemesis

This comment has been minimized.

Copy link

commented Sep 15, 2018

Works in Xenial, please close this issue 👍 @UniversalSuperBox

@UniversalSuperBox

This comment has been minimized.

Copy link
Member

commented Sep 16, 2018

I'm not able to confirm that. Still doesn't work for me with data from before the latest updates. Did you flash with wipe @samzanemesis?

@nfsprodriver

This comment has been minimized.

Copy link
Member

commented Sep 16, 2018

Also can confirm that. Seems to be fixed with the today's scaling fix.

@3arn0wl

This comment has been minimized.

Copy link
Author

commented Sep 16, 2018

It's not working for me yet either - Hammerhead.16:04.dev

@nfsprodriver

This comment has been minimized.

Copy link
Member

commented Sep 16, 2018

Have you updated your system via apt?

@MK1973

This comment has been minimized.

Copy link

commented Sep 17, 2018

Confirm the screen does not work as a touchpad.

I can insert my passcode from the touchscreen keyboard that appears pressing the power button or volume, but than there is no any pointer to interact with.

device: N5
channel: devel, update version 594
OS: Xenial 16.04

@3arn0wl

This comment has been minimized.

Copy link
Author

commented Sep 17, 2018

"Have you updated your system via apt?"

I got the automatic update, and I have installed the latest dev image this morning.
I have just tried it again on two monitors, and it doesn't appear to be working.

@APokorny

This comment has been minimized.

Copy link

commented Nov 4, 2018

We would need unity8 logs (home/phablet/.cache/upstart/unity8.log of while the slim port is attached.
Additionally /var/log/lightdm/unity-system-compositor.log would help.

For the touchpad simulation unity8 crates a userspace input device via /dev/uinput and turns it into a mouse.
If that succeeds usc should tell us about the new device. And we should see error traces otherwise in unity8.log

Also you could login to the device via ssh while the slimport adapter is plugged in and look for the simulated device in /dev/input/

@SwizzleMaster

This comment has been minimized.

Copy link

commented Nov 4, 2018

We would need unity8 logs (home/phablet/.cache/upstart/unity8.log of while the slim port is attached.
Additionally /var/log/lightdm/unity-system-compositor.log would help.

Logs; as requested.

unity8.log
unity-system-compositor.log

@APokorny

This comment has been minimized.

Copy link

commented Nov 5, 2018

Hmm I dont see "Virtual uinput mouse device created". And no traces of another input devices being opened.

@SwizzleMaster

This comment has been minimized.

Copy link

commented Nov 11, 2018

Hmm I dont see "Virtual uinput mouse device created". And no traces of another input devices being opened

ok. i retried it... check near the [2018-11-11 17:52:50] timestamp

i also ran " ls /dev/u* " to check if the uinput device is present. it's there.
ls_dev_u*.log
unity8.log
unity-system-compositor.log

@mauricioduarte01

This comment has been minimized.

Copy link

commented Jun 28, 2019

Tried edge today and I noticed a new interface and even a first time tutorial about how to use the touchpad. I notice that you can control the pointer but the touch area is not centered. I think now is a good time to review this issue because this feature is finally almost there. @MK1973

@3arn0wl

This comment has been minimized.

Copy link
Author

commented Jul 3, 2019

Being able to control the pointer with the phone as a touchpad is clear development! I wonder if the centering issue is a difficult one to sort out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.