Quote from tass_co on 16/12/2025, 05:12

Thank you for the update.

I have repeated the diagnostic process multiple times and followed all steps exactly.
However, the DebugView.log file is not being generated on my system at all,
which is why it is missing from the log folder.

Additional checks as requested:

– When the spacedesk Driver is turned OFF in the Driver Console, the stuttering
does NOT occur. Windows works smoothly.
– As soon as the Driver is turned ON, system-wide stuttering starts immediately,
even without any viewer device connected.

While the Driver is ON, I checked Task Manager:
– No application is showing unusually high CPU or memory usage.
– The stuttering occurs even when overall CPU usage is low.

Additionally, since yesterday I have been turning OFF the spacedesk driver
whenever I watch videos (YouTube, local video files, etc.), because keeping
the driver ON causes noticeable stuttering during video playback on the PC.
With the driver turned OFF, video playback is smooth again.

This behavior started after updating to spacedesk Driver v2.2.12.
Earlier versions did not cause this issue.

Please let me know if there is an alternative way to capture DebugView logs
or if this could be a known issue with v2.2.12 preventing DebugView logging.
Thank you for your continued support and patience.

Quote from tass_co on 16/12/2025, 05:23

Quote from spacedesk Renz on 16/12/2025, 05:06

Hi @tass_co,
I’m not sure why, but the file named “Debugview.log” is still missing from the log folder. Please see imaged attached as reference. Can you try getting your logs again? Thanks also for your patience.

Also, please check this as this will help us determine what’s causing the issue on your end:

Quote from spacedesk Renz on 16/12/2025, 04:33

Can you also check if the stuttering issue is there when the spacedesk Driver is turned off from the Driver Console? If not, then while the Driver is turned on, open the Task Manager then check if there’s any application that’s using up a large amount of CPU, GPU, and/or memory.

 

To help illustrate the problem more clearly, I uploaded a YouTube video showing
the stuttering behavior. The video demonstrates that Windows stutters while the
spacedesk Driver is enabled and becomes smooth again as soon as the Driver is disabled.

Quote from spacedesk Renz on 16/12/2025, 06:01

Hi @tass_co,

Thanks for the detailed update and the video. If it’s possible, can you also send a video of the stuttering issue while no spacedesk viewer is connected to the PC? From the video, it seems that a viewer connects as indicated by the pending connection popup that appears after you turned on the Driver. Thanks again.

Quote from tass_co on 16/12/2025, 06:42

I performed further tests to isolate the issue and here are the results:

Viewer device tests:

– Xiaomi 12T Pro (Android 15)
Viewer APK: v2.132
→ Connected alone: NO stuttering at all.

– Samsung Galaxy Note 10.1 (GT-N8010, Android 4.1.2)
Viewer APK: v2.1.30 (Android 4.1+ compatible)
→ Connected alone: STUTTERING occurs.
→ Connected together with the Xiaomi 12T Pro: STUTTERING occurs.

So the stuttering is consistently triggered whenever the GT-N8010 (Android 4.1.2)
is connected, regardless of whether it is the only viewer or one of multiple viewers.
As soon as the GT-N8010 is disconnected, the stuttering immediately disappears.

This confirms that:
– The issue is NOT caused by the Xiaomi 12T Pro or newer Android versions.
– The issue is NOT caused by having multiple viewers alone.
– The issue is specifically related to the GT-N8010 (Android 4.1.2) interacting
with spacedesk Driver v2.2.12.

This suggests a compatibility or performance regression between the current
spacedesk Driver and older Android 4.1 devices, even when using an
Android 4.1+ compatible viewer APK (v2.1.30).

Please let me know if there are any recommended settings, legacy modes,
or older viewer/driver combinations known to work better with Android 4.1 devices.

Thank you for your continued support and patience.

Quote from tass_co on 16/12/2025, 07:35

Small update / correction after additional observation:

After longer usage, I noticed that when the Xiaomi 12T Pro (Android 15, Viewer v2.132)
is connected alone, there is also a very minor amount of stuttering.
However, it is barely noticeable and does not significantly affect normal usage.

In contrast, when the Samsung Galaxy Note 10.1 (GT-N8010, Android 4.1.2, Viewer v2.1.30)
is connected, the stuttering becomes clearly visible and system-wide,
making the issue much more severe.

So to clarify:
– Xiaomi 12T Pro connected alone → very minor / barely noticeable stuttering
– GT-N8010 connected alone → severe and obvious stuttering
– Both devices connected → severe stuttering (same as with GT-N8010 alone)

This indicates that the issue exists at a low level even with newer Android devices,
but it becomes significantly worse when an older Android 4.1 device is connected.

The problem still started after updating to spacedesk Driver v2.2.12.
Earlier versions did not show this behavior.

Quote from spacedesk Renz on 16/12/2025, 07:37

Hi @tass_co,

Thanks for drilling down the cause of the stutter on your end. For your information, starting with spacedesk Android app v2.1.31, support for devices with an Android version that’s lower than 5.0 has been removed due to an update to Google Play’s policy. Can you try changing the “Encoding Type” option on your Galaxy Note to “Hardware Encoding H264 (forced)” to see if this fixes the stutter? You can find it in the floating menu > Settings > Quality/Performance.

Quote from tass_co on 16/12/2025, 08:26

I already tested the suggested setting on the GT-N8010.

When switching the Encoding Type to “Hardware Encoding H264 (forced)”, the viewer immediately throws the following error (see attached screenshot):

“Hardware Decoder H264 ran into an error on decoding. Please consider switching from Hardware Encoding to Software Encoding.”

The session is then disconnected automatically.

This confirms that:

• The GT-N8010 (Android 4.1.2) cannot decode the H.264 stream using hardware decoding
• The issue is not just performance-related, but a hard decoder incompatibility
• Therefore, forcing hardware encoding is not a viable workaround on this device

As a result, the viewer must fall back to software decoding, which then causes the system-wide stuttering observed on the PC whenever this device is connected.

This further supports the conclusion that the stuttering is caused by a compatibility limitation between:

• spacedesk Driver v2.2.12
• and legacy Android 4.1 hardware decoders

Please let me know if there are any legacy/compatibility options on the driver side (e.g. older encoder profiles or reduced stream parameters) that could improve behavior with Android 4.1 devices.
Thank you.

Quote from tass_co on 16/12/2025, 08:41

I would like to clarify and correct the timeline, as this further confirms that the issue is a driver-side regression.

Previously, I was using spacedesk Windows Driver v2.1.0. (i guess)

Behavior with Driver v2.1.0:

• Samsung Galaxy Note 10.1 (GT-N8010, Android 4.1.2)
  → Connected alone: NO stuttering, system was smooth.
• Xiaomi 12T Pro (Android 15)
  → Added later as a second viewer: NO noticeable stuttering.
• Even with both viewers connected, the system behavior was acceptable and did not show the severe stuttering seen now.

After updating the Windows PC to spacedesk Driver v2.2.12:

• GT-N8010 alone → STUTTERING occurs
• GT-N8010 + Xiaomi 12T Pro → STUTTERING occurs
  Xiaomi 12T Pro → STUTTERING occurs​ (very little, almost imperceptible​)
•  
• As soon as the GT-N8010 is disconnected, the stuttering immediately disappears.

This clearly indicates that:

• The GT-N8010 was previously compatible and stable with Driver v2.1.0
• The issue started only after upgrading to Driver v2.2.12
• Therefore, this is a regression introduced in the newer driver, specifically affecting legacy Android 4.1 devices

Additionally, forcing “Hardware Encoding H264” on the GT-N8010 results in an immediate Hardware Decoder H264 error, confirming that the stream generated by the newer driver is no longer compatible with the device’s hardware decoder.

Please let me know if:

• Driver v2.1.0 (or another older version) is recommended for legacy Android devices, or
• There are any legacy/compatibility encoder options available in newer drivers to restore the previous behavior.

Thank you for your continued support and patience.