SOTI Pulse Logo

Query about android updates

MJ
María José
Daimler AG
Hello everybody,

I wanted to make the following query about the Android update system through SOTI.

We are implementing a system, in which, during several days of the week, the update file would be copied to the various terminals, and on a different day the update would be installed.

The problem is, that during the tests we had a mishap, according to the logs of the SOTI rule that is responsible for copying the files to the terminals, this file had been copied correctly in all the terminals, but on the day of execution, We checked that only a certain number of them had been updated, we checked the terminals and to our surprise, they did not have the update file copied but in the rule logs it appeared the opposite.

At this point, I thought about using an .xml file to create a custom data, so that it would be downloaded together with the update file, but when redirecting the custom data to the xml information, it did not detect it and in SOTI The field does not appear, the name of the custom data does appear but without information.

Has something similar happened to someone else?

What update systems do you have implemented for android terminals?

Do you have any ideas or suggestions about how I could solve the custom data problem, or any improvement for the update system?

My SOTI version is: 14.1.5.1284
 and the terminals are mostly TC52 and WT6000.

Thank you very much to all.
soti android android-enterprise firmware-update
4 years ago
Android
ANSWERS
MD
Matt Dermody Diamond Contributor
4 years ago

For Zebra Android devices I leverage File Sync Rules to deliver the .ZIP files and then a Post-Sync script to execute the install_system_update script to execute the update. In some cases I have to generate MX XML and then use mxconfig to execute the .ZIP depending on the scenario. Including the Post-Sync script as part of the same File Sync rule provides enforcement that the file is there before the file is run. 

MJ
María José
4 years ago

Hi, thanks for the anwser.

But one question, how you can know that the file is in the device?

MD
Matt Dermody Diamond Contributor
4 years ago

The File Sync Rule is taking care of that since the Post-Sync script is executed only AFTER the sync has completed. 

MJ
María José
4 years ago

But, how you can verify if the actualization file is downloaded in the terminal?

MD
Matt Dermody Diamond Contributor
4 years ago

You don't have to verify it because the Post-Sync Script will only execute after the sync of the file is completed. The script will not run until after the file is there. 

MB
Marcus Breitenthaler
4 years ago

Hi,

the solution for us was to Downlad the Update Packages from an Internal Cloud Server.

It is faster available from the Loacations over the world, no longer network routing to one Server and more.

I have created the Steps in Stage now and have Exported the XML File.

This XML File is in an Package in MobiControl and is arroubd 2MB Large.

With a Profile and there i have selectet with filter when and how it should be executed.

When the Package goes inavtive the XMl file will be executed at the Device with an intent command and starts the Download of the Update file and installs it.

That works verry well and it is a good solution for us.

MJ
María José
4 years ago

Ok, i understan now, but its a difference between our implemented systems, we make the copy of the files one day, and another day at an exactly hour, we make the instalation.

MB
Marcus Breitenthaler
4 years ago
MJ
María José
4 years ago

But we dont use profile to the deployment of the update, we have created several virtual groups, and then, we select a week for each group to download the files, and other week to apply the update and we manage all with the schedules of the rules, we have one rule to copy and another rule to copy the xml wich execute the update.

Similar Discussions