TeamViewer Add-On: Datalogic is not working properly on Memor11 Android 13

Goodafternoon,

I am having difficulties using Teamviewer on 2 Memor11 devices which run on Android 13. The TeamViewer QuickSupport app itself and the Datalogic Add-on are installed on the devices without issues. After entering the ID from one of the devices in TeamViewer on my laptop it is possible to establish a live connection.

After this TeamViewer on the laptop side is very limited in its control. For example one left mouse click on an app to open it seems to register as if you are keeping pressing on it to see the quick options for the app.

This seems to only affect Memor11 with the latest available Android version. Establishing a TeamViewer connection on a Memor10 device works allows full control without issues.

When I check the dashboard in TeamViewer on the Laptop I see that the CPU is at 100% with only the TeamViewer QuickSupport app active.

When looking for the Datalogic add-on in the playstore I see that the minimum Android version is 5.1

Is this something that Datalogic will look into, or is this an issue that TeamViewer will have to address?

Thanks in advance,
Lorenzo

Hello @Lorenzo_Buurman,

We had already identified the issue with TeamViewer on Android 13+ and are working directly with TeamViewer to address the issue.
You should see a new TeamViewer Datalogic Add-On in the coming weeks that will resolve the issue.

I am not sure why your CPU is running at 100%, that is not going to be caused by the Datalogic Mobile device.
As far as the minimum Android version being 5.1, the lower number, the better supported the app is. The lower this number the more devices are going to support it, so it being this low is a good thing.

Drew Hugentobler
L3 Mobile Computer Specialist Support Engineer

3 Likes

Hello @Drew_Hugentobler,

Thank you for looking in to this. I just installed the updated version and it works again.

2 Likes

We’re pleased to inform that on June 17, 2025 TeamViewer released a new version of his “Add-on: Datalogic” that solved the issue with Android 13+ .

Simone Callegari
L3 Mobile Computer Specialist Support Engineer

1 Like