Skip to main content

Troubleshooting

Overview​

When Datalogic Launcher runs, it locks down the device by allowing only permitted packages to be accessed. If not configured properly, this can result in degraded/partial functionality within an application that relies on functionality outside itself. The information provided here is intended to help in configuring the launcher to allow the required functionality.

Allowed APKs​

Datalogic Launcher allows access to a package if it is referenced by one of the following configuration settings:

  • Allowed Apps: Allow any app displayed on the Home Screen. If any URLs are listed, this includes the default browser (configured at startup).
  • Allow apps to launch other apps: If enabled, allows all installed apps (a package with an activity with a filter of CATEGORY_LAUNCHER).
  • Built-in packages: Certain system-level packages are always allowed.
  • Allowed Packages: Allow any package included in this list.

How To Restore Functionality​

If applications launched from the Home Screen are missing functionality, try the following steps to inform the launcher which packages should be allowed:

  1. Try selecting Allow apps to launcher other apps:

    If you suspect that the missing feature is from another app, try enabling this checkbox. If this works, then you are finished. Optionally, you could try the next suggestion to isolate the specific package you need to allow.

  2. Discover the name of the blocked package:

    1. Examine the Logcat output from the device. (See Datalogic Logger for how to collect this without using ADB)

    2. Look in the Logcat output for an Error message similar to this example:

      Attempted Lock Task Mode violation r=ActivityRecord{fc8585a u0 com.google.android.calculator/com.android.calculator2.Calculator}

      The above example was generated by trying to launch the Calculator app when it was not allowed. The package name for the Calculator app is com.google.android.calculator.

    3. Add the package name to the list within Allowed Packages.

    4. Repeat these steps for additional packages listed as errors in Logcat.