Now requires permission if targeting P. Note that this is a separate permission from the existing one that is required for instant apps to use foreground services. The reason for this is that their semantics are different (the instant apps permission is associated with an app op for control over what the app is allowed, while the regular app permission is just a normal permission that is always granted and only there for auditing of apps), and there are probably going to be cases where a developer will want to use a foreground service in the full version of their app but not as an instant app. Bug: 72116995 Test: atest CtsAppTestCases Change-Id: If5a79e7ed5ab9e0edc77410315eb4d2df8ac850b
31 lines
1.3 KiB
XML
31 lines
1.3 KiB
XML
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
|
package="com.android.frameworkperf">
|
|
<uses-permission android:name="android.permission.FOREGROUND_SERVICE"/>
|
|
<uses-permission android:name="android.permission.WAKE_LOCK" />
|
|
<uses-sdk android:minSdkVersion="5" />
|
|
|
|
<application android:hardwareAccelerated="false">
|
|
<uses-library android:name="android.test.runner" />
|
|
<activity android:name="FrameworkPerfActivity" android:label="Framework Perf">
|
|
<intent-filter>
|
|
<action android:name="android.intent.action.MAIN" />
|
|
<category android:name="android.intent.category.DEFAULT" />
|
|
<category android:name="android.intent.category.LAUNCHER" />
|
|
</intent-filter>
|
|
</activity>
|
|
<service android:name="SchedulerService">
|
|
</service>
|
|
<service android:name="TestService" android:process=":test">
|
|
</service>
|
|
<service android:name="LocalTestService">
|
|
</service>
|
|
<receiver android:name="Receiver" android:exported="true">
|
|
</receiver>
|
|
</application>
|
|
|
|
<instrumentation android:name="android.test.InstrumentationTestRunner"
|
|
android:targetPackage="com.android.frameworkperf"
|
|
android:label="Framework Perf Runner"
|
|
/>
|
|
</manifest>
|