deskreen VS input-leap

Or if you are an experienced user of your operating system, you can find solutions on how to create a virtual display without a need for Virtual Display Adapter in the following link: https://github.com/pavlobu/deskreen/discussions/86

Use a vnc client on your android device and setup a virtual monitor on your desktop that is really a vnc server.

I know how to do that with Sway and swayvnc on wayland, as well as with xorg.

https://superuser.com/questions/1434779/using-a-tablet-as-a-...

https://www.reddit.com/r/swaywm/comments/k1zl41/thank_you_de...

This is particularly helpful to people using asahi linux and wanting to connect an external monitor. That can be done with something as simple as a raspberry pi.

EDIT: apparently this project help achieving the same thing on different OS but using webRTC and a browser:

https://github.com/pavlobu/deskreen

Screen sharing apps are good for this. You can access your pc from your phones browser and local pc IP. https://github.com/pavlobu/deskreen is free one i use.

No it is not necessary. The screen mirroring and sharing single application window functionality of Deskreen are working without any need for Virtual Display Adapter. The Virtual Display Plug is needed only if you want to extend your computer desktop to have a full secondary screen experience with Deskreen. Or if you are an experienced user of your operating system, you can find solutions on how to create a virtual display without a need for Virtual Display Adapter in the following link: https://github.com/pavlobu/deskreen/discussions/86

Generic X: https://github.com/pavlobu/deskreen/issues/42

I use Deskreen with Windows, it has a Linux version that probably works similarly. I think it leverages browser streaming tech.

https://deskreen.com/

Easiest way to get it working is with a dummy plug, but maybe there's more options on Linux to fake a display in software.

There is an actively developed fork https://github.com/input-leap/input-leap, however that fork is still undergoing heavy development and recommends sticking with Barrier until they're able to release v3.0.0 which they expect rather soon.

barrier is basically a dead project now. The active members of the project forked it and are going to release when ready but

https://github.com/input-leap/input-leap

Keep an eye on that for anything new

There's a new fork of barrier called input leap (not to be confused with the leap motion), https://github.com/input-leap/input-leap with work on getting Wayland support in shape. Not sure how far the support is atm, but the gnome 45 release notes mentioned "Wayland support for Input Leap" (https://release.gnome.org/45/)

Wayland tracker issue, https://github.com/input-leap/input-leap/issues/109

I wonder if I would be better off just buying a LG monitor without the Smart KVM, and instead using Barrier (or, Input Leap, which seems to be maintained actively compared to Barrier https://github.com/input-leap/input-leap)

Could also be worth mentioning that Barrier is basically unmaintained at this point so you'll probably never get Wayland support there. The maintainers (apparently the owner of the debauchee/barrier dropped off the face of the earth) of Barrier forked it and migrated to input-leap (issue with details if interested) which is where all development is presently, although they haven't made a release yet.

I'm already using waynergy with input-leap as my main way to control the laptop when it is docked. It is amazing.