对于应用何时可以使用前台服务,Android 14 制定了严格的规则。
此外,在 Android 14 中,我们还引入了一个新 API,用于指定作业必须是用户发起的数据传输作业。此 API 适用于需要由用户发起的持续时间较长的数据传输,例如从远程服务器下载文件。这些类型的任务应使用由用户发起的数据传输作业。
由用户发起的数据传输作业由用户启动。这些作业需要一个通知,会立即启动,并且可能在系统条件允许的情况下长时间运行。您可以同时运行多个由用户发起的数据传输作业。
必须在应用对用户可见的情况下(或在某个允许的条件下)安排由用户发起的作业。满足所有限制条件后,操作系统可以执行由用户发起的作业,具体取决于系统运行状况限制。系统还可以根据提供的估算载荷大小来确定作业的执行时长。
用户发起的数据传输作业的权限
由用户发起的数据传输作业需要具备以下新权限才能运行:RUN_USER_INITIATED_JOBS
。系统会自动授予此权限。如果您未在应用清单中声明此权限,系统会抛出 SecurityException
。
安排用户发起的数据传输作业的流程
如需运行用户发起的作业,请执行以下操作:
如果这是您第一次使用 JobScheduler 声明 API,请在清单中声明
JobService
和相关权限。此外,还要为数据传输定义JobService
的具体子类:<service android:name="com.example.app.CustomTransferService" android:permission="android.permission.BIND_JOB_SERVICE" android:exported="false"> ... </service>
class CustomTransferService : JobService() { ... }
在清单中声明
RUN_USER_INITIATED_JOBS
权限:<manifest ...> <uses-permission android:name="android.permission.RUN_USER_INITIATED_JOBS" /> <application ...> ... </application> </manifest>
构建
JobInfo
对象时,调用新的setUserInitiated()
方法。我们还建议您在创建作业时通过调用setEstimatedNetworkBytes()
提供载荷大小估算值:val networkRequestBuilder = NetworkRequest.Builder() .addCapability(NET_CAPABILITY_INTERNET) .addCapability(NET_CAPABILITY_NOT_METERED) // Add or remove capabilities based on your requirements .build() val jobInfo = JobInfo.Builder() // ... .setUserInitiated(true) .setRequiredNetwork(networkRequestBuilder.build()) .setEstimatedNetworkBytes(1024 * 1024 * 1024) // ... .build()
在应用可见或在允许的条件列表中,作业应在转移开始前调度:
val jobScheduler: JobScheduler = context.getSystemService(Context.JOB_SCHEDULER_SERVICE) as JobScheduler jobScheduler.schedule(jobInfo)
执行作业时,请确保对
JobService
对象调用setNotification()
。该值用于在任务管理器和状态栏通知区域中告知用户作业正在运行:class CustomTransferService : JobService() { override fun onStartJob(params: JobParameters?): Boolean { val notification = Notification.Builder(applicationContext, NOTIFICATION_CHANNEL_ID) .setContentTitle("My user-initiated data transfer job") .setSmallIcon(android.R.mipmap.myicon) .setContentText("Job is running") .build() setNotification(params, notification.id, notification, JobService.JOB_END_NOTIFICATION_POLICY_DETACH) // Do the job execution. } }
定期更新通知,让用户了解作业的状态和进度。如果您在安排作业之前无法确定传输大小,或者需要更新估算的传输大小,请在已知传输大小后使用新的 API
updateEstimatedNetworkBytes()
更新传输大小。执行完成后,调用
jobFinished()
以向系统表明作业已完成,或者应重新调度作业。
可以停止用户发起的数据传输作业
用户和系统都可以停止用户发起的传输作业。
由用户从任务管理器提供
The user can stop a user-initiated data transfer job that appears in the Task Manager.
At the moment that the user presses Stop, the system does the following:
- Terminates your app's process immediately, including all other jobs or foreground services running.
- Doesn't call
onStopJob()
for any running jobs. - Prevets user-visible jobs from being rescheduled.
For these reasons, it's recommended to provide controls in the notification posted for the job to allow gracefully stopping and rescheduling the job.
Note that, under special circumstances, the Stop button doesn't appear next to the job in the Task Manager, or the job isn't shown in the Task Manager at all.
由系统提供
Unlike regular jobs, user-initiated data transfer jobs are unaffected by App Standby Buckets quotas. However, the system still stops the job if any of the following conditions occur:
- A developer-defined constraint is no longer met.
- The system determines that the job has run for longer than necessary to complete the data transfer task.
- The system needs to prioritize system health and stop jobs due to increased thermal state.
- The app process is killed due to low device memory.
When the job is stopped by the system (not by the low-memory case), the system
calls onStopJob()
, and the system retries the job at a time that the system
deems to be optimal. Check that your app can persist data transfer state, even
if onStopJob()
isn't called, and that your app can restore this state when
onStartJob()
is called again.
允许安排用户发起的数据传输作业的条件
Apps can only start a user-initiated data transfer job if the app is in the visible window, or if the certain conditions are met. To determine when a user-initiated data transfer job can be scheduled, the system applies the same list of conditions that allow apps to start an activity from the background in special cases. Notably, this list of conditions are not the same as the set of exemptions for background-started foreground service restrictions.
The exceptions to the previous statement are the following:
- If an app can launch activities from the background, they can also launch user-initiated data transfer jobs from the background.
- If an app has an activity in the back stack of an existing task on the Recents screen, that alone doesn't allow a user-initiated data transfer job to run.
If the job is scheduled at some other time not listed in the allowed conditions
list, the job fails and returns a RESULT_FAILURE
error code.
适用于用户发起的数据传输作业的约束条件
To support jobs running at optimal points, Android offers the ability to assign constraints to each job type. These constraints are already available as of Android 13.
Note: The following table only compares the constraints that vary between each job type. See JobScheduler developer page or work constraints for all constraints.
The following table shows the different job types that support a given job constraint, as well as the set of job constraints that WorkManager supports. Use the search bar before the table to filter the table by the name of a job constraint method.
These are the constraints allowed with user-initiated data transfer jobs:
setBackoffCriteria(JobInfo.BACKOFF_POLICY_EXPONENTIAL)
setClipData()
setEstimatedNetworkBytes()
setMinimumNetworkChunkBytes()
setPersisted()
setNamespace()
setRequiredNetwork()
setRequiredNetworkType()
setRequiresBatteryNotLow()
setRequiresCharging()
setRequiresStorageNotLow()
测试
下面列出了有关如何手动测试应用作业的一些步骤:
- 如需获取作业 ID,请获取在构建作业时定义的值。
如需立即运行作业或重试已停止的作业,请在终端窗口中运行以下命令:
adb shell cmd jobscheduler run -f APP_PACKAGE_NAME JOB_ID
如需模拟系统强行停止作业(由于系统运行状况或超出配额条件),请在终端窗口中运行以下命令:
adb shell cmd jobscheduler timeout TEST_APP_PACKAGE TEST_JOB_ID