Hi everyone,
One of our customers is facing this error message on a Memor12:
What could be the cause and how can we solve it?
Kind regards,
Filip
2 Likes
Hi Filip,
This problem is caused by a change in the Android SDK that our SDK extension did not fully accommodate. It is caused when the terminal connects to either a Wi-Fi network or a cellular mobile network and updates Android components via Play Store. Once this update happens, the terminal switches from implementing Local Share to implementing Quick Share. In some cases this error will not display immediately after the update, but in some cases it does. It will always display after the terminal reboots. This problem currently affects Memor 12/17, Memor 30/30X, and Memor 35/35X.
Aside from the very big red notification, we haven’t found any actual problems that result from this error.
Our developers have isolated the root cause and have checked a fix into source control. This fix is planned to be rolled out in the next maintenance release. We’re working on publishing a workaround, and when it is ready I’ll post it here for you. More on that later…
Thank you for your patience,
Scott
Mobile Computers Specialist Support Engineer, Datalogic
4 Likes
Any news on this issue here?
Hello @Arian_Zuta ,
As Scott explained earlier, this error is caused by an automatic Android SDK update that Google Play Services pushes when the device connects to a network. This update affects all firmware versions and unexpectedly changes a system setting that our Configuration Manager doesn’t recognize, resulting in the conflict.
The problem is purely cosmetic - despite the alarming red notification, it does not cause the device to malfunction, it is just an annoying alert.
Current Available Solution:
To immediately address the issue, we have released Espresso package version v1.19.001 for both Memor1X-Memor3X devices, which includes an updated DL System Service component that fixes the Configuration Manager error.
Remark: The new Espresso requires software component made available starting from firmware v1.19.005, then Devices must be updated to v1.19.005 before applying the Espresso.
Download Links:
- Memor 12-17: Memor 12-17 - Android - Firmware - Products - Datalogic Developer Portal
- Memor 30-35: Memor 30-35 - Android - Firmware - Products - Datalogic Developer Portal
Permanent Solution:
The next firmware release, scheduled for June, will natively include the updated DL System Service component that permanently resolves this error.
We recommend installing the Espresso v1.19.001 on fw v1.19.005 as a temporary fix until the permanent solution is available.
Best regards,
Simone Callegari
L3 Specialist SW Engineer - Datalogic Mobile Products