Translations:Обновление клиентского приложения через флеш-карту/1/en
Situation Description
The key reasons for using this functionality are the ability to add custom certificates during APK file compilation and update the client application without rebooting the device. An additional option is the ability to reinstall the client application if the current one was installed incorrectly or is experiencing issues. This feature will be useful for users and SmartPlayer technical support specialists.
Action Algorithm
This section describes the steps to update the client application from a flash drive:
- take a flash drive and create a folder named "SmartPlayer" on it;
- upload the SmartPlayer client app APK file to it;
- connect the flash drive to the device;
- the device will automatically check and read the information and contents of the flash drive;
- the user will start the installation of the new version of the application;

;
- wait for the installation to complete;
- launch and use the device as intended.
Subtleties and Functional Details
When updating the client application via flash drive, certain rules must be followed to ensure stable and correct operation. These are:
- during installation from the flash drive, the distribution file is automatically copied to the device’s memory. Therefore, it's essential to ensure the device has enough free space in local storage to accommodate the file;
- when preparing the flash drive with the client app, create a folder named "SmartPlayer" and place the APK file inside. The expected path would look like: "/SmartPlayer/update.apk". If a corrupted or incorrect file is placed, the device will show an error and stop the process.

- the update will only proceed if the APK on the flash drive has the same or higher version than the one installed. If the version on the flash drive is lower, the device will show an error stating that downgrading is not possible.

- some devices have root access or an SDK (developer tools system) that allows "silent" installation (automatic installation with default parameters). In such cases, the user will see a screen with three buttons: “close”, “open file”, “install”.

In this case, the buttons perform the following actions:
- close — closes the installer window;
- install — launches silent installation on the device;
- open file — opens the system installer with the file selection and confirmation dialog.

If no SDK or root access is present, the interface changes and silent installation becomes unavailable. The user will now see only two buttons: “close” and “install”. In this case, the **install** button functions identically to the previously described **open file** behavior.

Additional Information
If this article does not help you use the functionality as intended, or if questions remain after reading, you can ask them in the **Discussions** section at the top of the page.

More details can also be found on the page How users interact with the “Discussions” section