No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Hi, our devices seem not be able to update the android mobicontrol agent (yes, i activated Agent-Upgrade and send agent upgrade). We got the information that an upgrade is not possible because the actual agent is still compatible. I mean, i know it, because it's running!?! -.- Now i tried the following way: 1. send the apk to the device filesystem 2. send script: install /mnt/sdcard/GoogleMobiControl1400_1579.apk 3. A prompt is shown on the device, which has to be confirmed with OK. 4. Update success Is it possible to do this without user prompt?
Hey Guys, I have a very specific Updateproblem with Zebra Devices. Anyway, hopefully someone can help me or got the same issue in the past. We try to Update our Zebra TC20 from OS 04.14.30 Lifeguard 4 to Lifeguard 13. If I do this with adb sideload and a USB Cable everything works fine. We also done a few Updates remotely with Soti-Command Install_system_update and also with Zebra MX OS Update (http://techdocs.zebra.com/stagenow/3-4/csp/power/) This also worked fine on ~ 100 Devices. But now we get an Error on most of our devices. We got captured this Errormessage: Firstival we thought the OS Update File was not downloaded completly. So we done a few Tests but the Update File has the same size and MDM5-Sum. We also tested to copy the Update-File with Soti Remote Control with the same issue So for us it seems to be some local issue of the Device. Does anyone know if there is any cache limit or something else who could deny our OS Update??? Or is there any chance to force a "clean boot" which resets all the cache of the device? If we try to apply the Update on a fresh installed Device everything works fine. Also a Factory Reset can be applied by every device (same way like the Lifeguard Update) We also checked the File-Permission of the Update-File but it's always -rw-rw---- on working and non working devices. Further we tried to copy the File to /data/tmp/public with the same result. In any Case the Update-File has always the same Size :-( Could there be any File-Lock on the Update-File or has anyone an Idea how we can log this process to find out what happens in this situation? Many thanks so far.
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.
