Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

History CapaInstaller Android Support

CapaInstaller uses an app as an agent for Android units.

  • The agent version was used until CapaInstaller release 5.7.100, then it was substituted with a new agent having the same functionality and other improvements.
  • The new agent is versioned 2.x.x.

Android History

In general Android has been a very open platform allowing apps to do a lot of stuff. Later Android releases have restricted applications much more and introduced newer device policy management concepts (Device Administrator / Device Owner / Profile Owner).

Previously an app could drain the battery quite fast if it wasn’t optimized. In newer Android versions from Android 6 and upwards, this has been optimized so apps are being “battery optimized”.

Battery optimization is being more and more restrictive, over the newer Android versions. Battery optimizations are firstly controlled by an individual app setting. The new CapaInstaller Agent prompts the user for preventing battery optimization. But even if the app is not battery optimized it will still be optimized and especially from Android 8 this they have further increased the battery optimizations. For further and deep technical explanations see:

In general, it can be given that these factors apply for determining whether an app should be optimized:

  • Battery optimization disabled for the app
  • Android version
  • App usage by the user
  • Priority push messages received
  • Privileged apps
  • Vendor-specific optimizations

In general, the CapaInstaller Agent will fulfill most of these factors except the user interaction part (The CapaInstaller agent is rarely clicked by the end-user), some may even have blacklisted the CapaInstaller Agent so the end-user will be unable to launch the app.

Vendor-specific optimizations

Several Android vendors (Samsung, Huawei, Motorola, etc..) have made their own “smart” battery optimizations. Some of these must be disabled manually.

What to do

In general, the CapaInstaller agent shall be at least 2.1.5 and it must be installed/configured to not allow battery optimization for the CapaInstaller agent (agent is prompting the user).

For Android versions above Android 8, the agent should be upgraded to version 2.2.x or newer in order to work with reoccurring callbacks to the CapaInstaller backend servers.

What shall we do with old agents, not responding?

If you have some agents which haven’t communicated with CapaInstaller for a long time, we recommend the following approach:

  1. Determine if this device is still in actual use? (Device is erased and sold, device obsolete and dropped in a drawer, the user is on absent, etc…..)
  2. Will this device be faced out within a few months anyway, then we can just ignore it.
  3. Ask the user of the device to open the CapaInstaller Agent. Just by opening the agent it will probably try to call home.
  4. If the device doesn’t call home even though the app is started you can on agents 1.x.x press the burger menu and select “Call home” and on agent 2.x.x click profiles tab and click the refresh symbol.
  5. Finally, it will be good to update the CapaInstaller agent to version 2.2.x or newer.
  • No labels