Environment
- Device: Datalogic [Memor 35 / 35x]
- Android version: [Android 15 / 3.16.008.20251216s]
- Management: Custom EMM / Device Policy Controller (Device Owner, fully-managed device)
- TeamViewer Host:
com.teamviewer.host.market — v15.79.177 (installed from Google Play, latest) - TeamViewer Datalogic add-on:
com.teamviewer.quicksupport.addon.datalogic_1 — v15.70.9132 (latest available on Google Play)
Problem
When a technician starts an unattended remote-control session to the device, the connection establishes (correct TeamViewer ID, session negotiates), but the technician's screen hangs indefinitely on "Connecting… Initializing display parameters" — the device screen never renders and no remote control is possible.
What we have already verified / ruled out
- Add-on is installed and has been granted all of its declared permissions via the Datalogic AppManager SDK, including the capture/injection permissions:
ACCESS_SURFACE_FLINGER, READ_FRAME_BUFFER, CAPTURE_VIDEO_OUTPUT, INJECT_EVENTS. - Host is installed and granted
SYSTEM_ALERT_WINDOW, SCHEDULE_EXACT_ALARM, MANAGE_EXTERNAL_STORAGE, etc. - Screen capture is NOT disabled by device policy —
adb shell dumpsys device_policy shows Screen capture disallowed users: [] (i.e. capture is allowed). - TeamViewer provisioning/assignment succeeds — the device obtains a rollout key, the MDM provisioning API returns SUCCESS, and it reports a valid TeamViewer ID.
- The failure is only in the display/screen-capture stage — connection and assignment are fine.
Suspected root cause
There is a version mismatch between TeamViewer Host and the Datalogic-specific add-on: Host is on 15.79.x while the newest Datalogic add-on published to Google Play is 15.70.9132. TeamViewer requires the OEM add-on to match the Host/QuickSupport version; a minor-version drift produces exactly this "Initializing display parameters" hang while everything else works.
The core problem for an enterprise deployment: Google Play only serves the latest version of each app. Host auto-updates to 15.79.x, but the Datalogic add-on has not been updated past 15.70.9132, so the two can never be aligned through Play — and we cannot downgrade Host to 15.70.x through the Play/managed-Play pipeline.
Questions for Datalogic / TeamViewer
- Is an exact Host ↔ Datalogic add-on version match required? What is the officially supported/compatible version pairing?
- When will an updated Datalogic add-on matching the current Host (15.79.x) be published to Google Play? The add-on appears to lag the mainline Host by several minor versions.
- In an EMM/managed Google Play deployment, what is the recommended way to keep Host and the Datalogic add-on in sync (e.g. version pinning, a distribution channel that ships them together)?
- Is there a known Android 15 issue with the Datalogic add-on's display/framebuffer capture on [device model]? (We've seen a related report — "TeamViewer QuickSupport / Datalogic Add-On not working properly on Memor 12, Android 15" — on Datalogic forum.)
Any guidance on the supported version pairing or an ETA for an updated add-on would be greatly appreciated, as this currently blocks unattended remote support on our Android 15 Datalogic fleet.
