Share via

Android - Remote Desktop - decode barcode

Kasa Fr 0 Reputation points
2025-04-10T12:08:11.7533333+00:00

Hello,

For remote connection to the server where we have the information system, we use a Zebra TC8300 device with a barcode scanner with Android 13 OS. We use the Remote Desktop application (v8.1.82.445). We need to install a new server with Windows Server 2022 Datacenter OS. The previous server had OS Windows Server 2019 Datacenter.

We are having a problem with the display rendering, if we lose internet connection and reconnect. I believe this is an issue with an older version of the RD application. So I installed a new version of RD (v11.0.0.10) on the Zebra device. If I now connect to the server via the new version of RD, the problem with rendering the display is resolved, but we now have a new problem with decoding invisible characters from the barcode. Instead of "0108593540507600112504041730040310240002", the characters "ççççççççççççççççççççççççççççççççççççççç" are displayed.

I've tried connecting to the new server from an older RD application and the decoding of the invisible characters from the barcode is good. So I tried to connect to the previous server from the new RD application and the decoding of the invisible characters from the barcode is bad.

Now I think the problem is in the new version of the RD application, somewhere there is a difference, but where?

I tried to install another application as Parallel Client and the same problem with decoding invisible characters from barcode...

We use US language and keyboard on Zebra device and US keyboard on server.

Could the problem be in the keyboard emulation? But what do I need to set up?

Thank you all for any reply.

Frantisek

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Domic Vo 10 Reputation points Independent Advisor
    2025-08-10T06:34:56.4266667+00:00

    Dear Kasa Fr,

    Thank you for your detailed explanation regarding the barcode decoding issue you're experiencing with the Zebra TC8300 device and the Remote Desktop application.

    You've done an excellent job isolating the behavior across different RD client versions and server OS combinations. Based on your findings:

    RD v8.1.82.445: Correct barcode decoding, but display rendering issues after reconnect.

    RD v11.0.0.10: Display rendering resolved, but barcode data is misinterpreted (e.g., showing "çççç..." instead of expected numeric string).

    Parallel Client: Same decoding issue as RD v11.

    Consistent US language and keyboard settings on both device and server.

    Preliminary Assessment

    The issue appears to stem from how the newer RD client version handles keyboard input and character encoding, particularly for non-printable or control characters often embedded in barcode data.

    Here are some likely contributing factors:

    Keyboard Emulation Differences

    Newer RD clients may use different input methods (e.g., Unicode vs. scancode translation), which can affect how barcode data is interpreted.

    Character Encoding Mismatch

      If the RD client or server interprets the input stream using a different code page or encoding standard, invisible characters may be misrepresented.

  
  **Input Method Editor (IME) or Locale Settings**

  
     Even with US keyboard layouts, subtle differences in input method handling between Android and Windows can cause decoding anomalies.
B) **Recommended Steps**

To help resolve the issue, we suggest the following:

1. **Test with Keyboard Emulation Settings on Zebra Device**

   - Check if the barcode scanner app or device settings allow switching between **keyboard wedge**, **HID**, or **direct input** modes. Try toggling these to see if decoding improves.
   
1. **Force Legacy Keyboard Mode in RD Client (if available)**

   - Some RD clients offer settings to use legacy input translation. Explore RD v11 settings for any keyboard/input compatibility options.
   
1. **Verify Code Page on Windows Server**

   - Ensure the server is using **code page 437 or 1252 (US English)** for console and RDP sessions. You can check this via chcp command in Command Prompt.
   
1. **Use Diagnostic Logging on Zebra Device**

   - Enable input logging to capture raw barcode data before it reaches the RD session. This can help confirm whether the issue originates on the device or during transmission.
   
1. **Try Alternative RD Clients with Input Customization**

   - If RD v11 lacks flexibility, consider testing with clients like **RD Client by Devolutions** or **Splashtop**, which may offer more granular input control.

    I hope this helps,

    Domic Vo

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.