Module Activation Scope

Module Activation Scope

Since EdXposed API 92, we implemented the module activation scope. (Refer to Introduction of Modules Activation Scope (Chinese))

Users can now choose which applications the module can work on, but they don't know which should be selected. Although we don't force the use of this feature, it is still very important to declare the list of its scope for a good user experience.

Example usage

If a module wants to hook package com.example.a and com.example.b, in AndroidManifest.xml, a meta-data named xposedscope should be defined as:

<meta-data android:name="xposedscope" android:resource="@array/example_scope" />

And in array.xml, a string array named example_scope (this name could be arbitrarily changed) should be defined as:

<string-array name="example_scope" >
    <item>com.example.a</item>
    <item>com.example.b</item>
</string-array>

Advantage

By defining such a meta-data, the list of applications in the array will be displayed to the user when the scope of the module is set in the manager.