Any reason for the non-standard placement in a subfolder? Have you successfully leveraged a .UPL update file outside of SOTI (eg. through StageNow?) I'm thinking you might have to use the mxconfig script on a StageNow XML that processes the .UPL file rather than using install_system_update on the .ZIP as you would traditionally handle an OS Update for a Zebra Android device.
I personally would rather decouple the multiple firmware updates (BSP + LG) into separate Profiles or File Sync Rules rather than trying to couple them together. You'll end up with multiple reboots into Recovery Mode but you'll avoid unnecessarily sending down a FPU just to get an LG version updated.
I've given this some more thought and am now assuming that you're trying to work around the fact that the Helios (SD660) platform devices like the TC52 and TC77 have a new version of Recovery Mode that has sub-menus asking for Upgrade/Downgrade as well as another prompt for Diff vs. Full update and that new Recovery Mode doesnt cooperate properly with the install_system_update script that could be traditionally used with Zebra Android devices. If that is the case I would suggest going down the StageNow route to generate an XML file for processing the update (as a .ZIP or .UPL) and then use the mxconfig script for kicking off that XML. It appears that there is an Intent that can also be leveraged, although I think this is more intended for the EMM providers like SOTI to integrate with their scripting. I would imagine that we would see a newer version of install_system_update at some point that works with this next generation platform of devices from Zebra.
Info on handling multiple updates with a UPL file:
An according to this link you may want to use /data/tmp/public/Patches for the path in the UPL file.
Thanks for the information. I will have to take some time and try to digest it after I get some sleep.
First let me say I am pretty new to Android management and AEDO is pretty new to most of us along with waiting for SOTI to catch up with Google (though I can't upgrade my systems at the rate that they do, so trying to pick and choose when to do upgrades).
One of the reasons that I was looking to use a folder really has to do with trying to figure out a way to do file management since when an upgrade or patch is installed the file is remains after the process, thus at some point it will need to be cleaned up. I am starting to get too much crap in the root of the SDCARD.
Zebra was who mentioned using the UPL file for multiple updates, but of course didn't provide me with any documentation. I am far from being a StageNow expert and would prefer to keep as much in the EMM vs. the OEM tool. I do realize that there are things that StageNow needs to be used for some things (not like Zebra's documentation of StageNow is that great either).
The issue with doing multiple updates vs. single updates would be the ability to recognize the state of the device in order to be able to apply the updates in order. I have tried using Custom Data to recognize when a particular patch has been downloaded by a file sync rule, but I am finding the reliability of Custom Data updating to be less than stellar. The OEM Version does not always work as Zebra just gave us a hotfix for MX and the OEM Version didn't change and there doesn't appear to be a way to mine the MX version.
As I state at the beginning, I am still trying to learn what works which is one of the reasons I have been posted a lot of questions lately. I appreciate your feedback.
I'm not sure I would agree with you about the lack of documentation. StageNow and MX are incredibly well documented.
Here is also the same link I already provided thoroughly documenting UPL based OSUpdates, even with instructions specific to SOTI. What more documentation on the process could you need?
As for catching up on AEDO support, can you provide any specific examples of where SOTI is falling short? I wouldn't trust any other EMM vendor with AEDO for COSU right now, especially on Zebra Android devices. I'd be very curious to hear any concrete examples you have of missing AEDO feature that you need to take advantage of. NFC, DPC, QR, ZTE, AND StageNow based AEDO enrollment are all supported. Managed Google Play and Managed Configs are supported, OEMConfig is coming but reliant on the manufacturers actually publicly publishing their OEMConfig applications to Google Play, AEDO Kiosk mode is supported along with the legacy launcher. What is missing, COPE?
I'm also surprised your vendor has not been more helpful throughout this process for you. This is expertise that they should certainly have if they are reselling Zebra devices and should be able to provide guidance on.