Problems with notifications & clones running in the background

If notifications do not work in cloned apps, especially when the cloned app is in the background, it could be because some Android devices use overly aggressive memory management, freeing up as much RAM memory as possible by killing app processes very soon after an app moves to background. This may also affect persistent app services used for delivering new message notifications.

Similarly, if App Cloner fails to communicate with the cloned app, e.g. when using features such as New identity, Layout inspector or Preferences editor, when exporting or importing app data or when sending updated clone settings to the clone, it may be because the Android system does not allow the cloned app to start or run in the background.

To fix this, try excluding the cloned app from the battery optimizations in the Android system settings. Under the Installed clones tab open the app’s context menu and select Show app info > App battery usage and then select Unrestricted.

Using the Launching option Request ignore battery optimizations you can create clones that will automatically prompt to be added to the battery optimization whitelist.

If you already have many clones installed, this solution may be impractical. If you have ADB access, you can use the following ADB command to add an app to the battery optimization whitelist, where <packageName> is the cloned app’s package name:

adb shell dumpsys deviceidle whitelist +<packageName>

Make sure to include the plus symbol (+) before the package name without any separating space. To remove an app from the battery optimization whitelist, run the same command but use a minus symbol (-) instead:

adb shell dumpsys deviceidle whitelist -<packageName>

You can check if your cloned apps are added to the battery optimization whitelist using:

adb shell dumpsys deviceidle whitelist

You can also try using the Persistent app option to keep the app alive even when in the background. You should remember that persisting apps may reduce the available RAM memory, especially when creating many clones, which might have a negative impact on other apps or system performance in general. Creating a dummy accessibility service and enabling this accessibility service once the clone is installed is the only guaranteed method that the Android system will keep your app running at all times.

If media player notifications with action buttons such as play / pause, next or previous track do not work for cloned apps, try cloning the app using the Manifest cloning mode, which can be found under Cloning options. Note that this workaround does not work with all cloned apps, e.g. Spotify.

Sometimes, however, notifications simply don’t work in clone apps, as in the case with Skype. This may be because of the internal method used to deliver notifications from the server-side components to the app, which may break for modified app certificates or package names (which is often used as an app’s unique identifier).