forked from miracle2k/android-autostarts
-
Notifications
You must be signed in to change notification settings - Fork 0
/
AndroidManifest.xml
39 lines (38 loc) · 1.88 KB
/
AndroidManifest.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.elsdoerfer.android.autostarts"
android:installLocation="auto"
android:versionCode="24"
android:versionName="1.7.7">
<application android:icon="@drawable/icon" android:label="@string/app_name">
<activity android:name=".ListActivity"
android:label="@string/app_name">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name=".HelpActivity"
android:theme="@android:style/Theme.Light" />
</application>
<!-- We generally won't get those permissions. WRITE_SECURE_SETTINGS is
protectionLevel "signatureOrSystem", and changing other component's
states is even only allowed with a system signature, which is why
we need to work around those limitations with root.
However, it's possible that we might get those permissions in some
cases, for example if a user installs us on the system, in which
case we can then skip the root hacks and do things properly.
-->
<uses-permission android:name="android.permission.WRITE_SETTINGS" />
<uses-permission android:name="android.permission.WRITE_SECURE_SETTINGS" />
<uses-permission android:name="android.permission.CHANGE_COMPONENT_ENABLED_STATE" />
<uses-permission android:name="android.permission.ACCESS_SUPERUSER" />
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true" />
<uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14" />
<uses-configuration />
<uses-feature />
</manifest>