OTA Update Immediately Shows “Update in Progress”, Even Without User Action

Technical Support
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Understanding Torizon OTA Update Behavior

Your issue with OTA updates transitioning to “Update in Progress” before user acceptance is a known challenge with the default Torizon OTA implementation. Let me address your questions based on the available information:

1. Expected Behavior vs. Bug

This behavior appears to be the default implementation of Torizon Remote Updates (1). The system uses Aktualizr, which polls the server for updates every 5 minutes and applies them automatically when available (1)(2). This automatic behavior is by design for seamless OTA functionality.

2. Customizing Update Behavior for User Approval

Based on the community discussion, there are approaches to implement user approval workflows (2):

  • Using flock command: You can block updates using the flock command to prevent automatic application until user confirmation (2)
  • Custom notification mechanism: Implement a system to notify your application when updates are available, allowing you to present the choice to users (2)
  • User confirmation workflow: Only proceed with updates after explicit user acceptance (2)

The flock approach is considered safe even after reboots and can effectively maintain update blocking until you explicitly allow them (2).

3. Update Cancellation Limitations

Regarding update cancellation, the API documentation shows that updates can only be cancelled when they are in “Pending” status (3). Once a device has received its update instructions, the update can no longer be cancelled from the server side (3).

Recommended Approach

To achieve your desired workflow:

  1. Implement update blocking: Use flock to prevent automatic updates
  2. Create notification system: Set up a mechanism to notify your application when updates are available
  3. User interaction handling: Present update options to users and only release the flock upon user acceptance
  4. Configuration files: Investigate .toml configuration files for Aktualizr customization (2)

This approach ensures updates remain in a controllable state until user approval, maintaining your ability to cancel or replace updates as needed.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.