Skip to content

UScreen 1.2.3 — USB second monitor for Linux with S Pen support

Choose a tag to compare

@majmichu1 majmichu1 released this 16 Sep 01:51
· 25 commits to main since this release

Three fixes from this week's reports. Two are certain, one is a best effort until its reporter comes back.

The virtual monitor only exists while a tablet is attached

The EVDI helper used to run from the moment the daemon started, so the desktop
saw a connected (disabled) monitor at every boot whether a tablet was there or
not. KDE remembers layouts per output, so a layout once saved as "show only on
the UScreen screen" came straight back on the next login with nothing to show
it on — real screens black, no tablet in sight
(#12).

The helper now starts when a tablet becomes a screen and stops when it stops
being one, so the virtual monitor appears and disappears exactly like a cable.
Verified: daemon running with no tablet, no helper process, no DVI output
listed by KWin.

.deb: a failing evdi-dkms no longer breaks the rest of the install

Debian's evdi-dkms 1.14.8 does not build against kernels 6.14 and newer
(drm_driver.date is gone there). With uscreen depending on it, dpkg left
uscreen unconfigured too — no udev rule for /dev/uinput, no modprobe file
for the EVDI device — which produced a wall of unrelated-looking errors
(#13).

The package now recommends evdi-dkms instead, the helper's hint when no EVDI
device appears says what to actually check (it used to suggest a Makefile
target package installs do not have), and docs/installation.md has the
recipe for building the upstream module on such kernels.

App: a decoder that shows nothing gets restarted

A Galaxy Tab S10 FE+ on Android 16 rendered one frame and then nothing while
the host kept sending and the decoder kept accepting input
(#10). The old watchdog only
noticed a decoder that stopped taking frames. Now, four frames in and none
out for 1.5 s restarts the decoder and reconnects for a fresh keyframe; a
second stall in a row restarts it without the low-latency hints.

This is built from that report's log and is a recovery, not a root cause; the
issue stays open until the reporter says what the tablet does with 1.2.3.

Update both halves together. Files: .deb, .rpm, PKGBUILD archive,
portable tarball, uscreen.apk, SHA256SUMS.