Device locking

All clones are device-locked by default. This means if you create a clone on one device, it cannot be used on another device. This is to prevent distribution and abuse of clones. This also happens when using the premium version of App Cloner.

The simplest way to get the clone working on another device is to install App Cloner on the other device itself and create a new clone locally. You can always export and import the clone settings used for a particular app.

However, if you want to create a clone for a specific target device, e.g. a friend or family member, then please use the Device lock option, which you can find under Launching options, pasting the correct target device identifier into the dialog. The device identifier is shown in a dialog when trying to open the clone on another device. On smaller devices you may need to scroll down inside the dialog to see the device identifier.

On Android 8.0 or higher do not use the Device ID shown under App Cloner Settings > Device info. Starting with Android 8.0 each app gets its own device identifier, so to find the correct device identifier you must first launch the clone without the Device lock option enabled.

You can also use the Device lock option to paste multiple, comma-separated identifiers, which allows a single clone to run on multiple devices.

The Huge donation or Giant donation removes device locking, so you can create clones that run on all devices. However, you are not allowed to distribute clones outside of your company, unless they are your own apps or you are the copyright holder. Please see the App Cloner Terms of Use at https://appcloner.app/terms/.

Please note that the In-app live chat option always enforces device locking, even if you’ve made the huge or giant donation . This is because the live chat feature incurs server and hosting costs. Each live chat user should use their own licensed copy of App Cloner.

Secret dialer code

This is the Secret dialer code launching option. A dialer coder is a series of digits prefixed by *#*# and followed by #*#* that you enter into your phone dialer and which can trigger a certain action or, in this case, launch a cloned app.

See also: https://github.com/ukanth/afwall/wiki/Phone-codes-secrets

Unfortunately this isn’t supported by all devices. For example, it doesn’t work on Samsung devices. This option only makes sense if you also remove the app’s launcher icon, so that the cloned app can only be launched via the secret dialer code.

Fake calculator

The Fake Calculator privacy option shows a simple but fully functional calculator app when launching the clone. If you enter the correct code it will unlock the real app. Obviously, it makes sense to also change the app’s name and icon to something resembling a calculator app 🙂

Background optimization options

You will only see the Anti-memory thrashing option on Android 6.0 or earlier since Android 7.0+ already implements these changes.

Any app may declare the following event receivers in its manifest:

  • Connectivity change events, which are triggered whenever your network connectivity changes, e.g. when you switch from mobile data to Wi-Fi and vice versa or you toggle your Wi-Fi or mobile data connection.
  • New picture / video events, which are triggered whenever you take a new picture using your camera app or record a video.

Whenever these two events are triggered, Android will start the app in the background in order to execute the code to handle these events. This requires the entire app to be loaded into the phone’s memory even though the app is never displayed. If the app is large this may cause other recently used apps to be unloaded from memory, which negatively affects multi-tasking. It may also make your phone feel sluggish because when an app’s process is loaded into memory it usually executes a number of initialization functions.

It’s also a privacy concern. Why should an app’s background task be started whenever you take a picture? Why does the app need to know you just shot a photo?

The Anti-memory thrashing option allows you to disable these events for the cloned app.