自 2025 年 3 月 27 日起,我們建議您使用 android-latest-release
而非 aosp-main
建構及貢獻 AOSP。詳情請參閱「Android 開放原始碼計畫變更」。
裝置排程
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
裝置排程模組包含邏輯,可偵測裝置是否處於閒置狀態,並可在未干擾使用者的情況下重新啟動。
這個模組會向安裝程式提供可靠的信號,指出何時可重新啟動,進而提升軟體更新的採用率。可靠的重新啟動就緒信號可讓安裝程式重新啟動裝置以套用更新,並確保使用者不會因更新而中斷。
自動重新啟動未使用的裝置,可加快更新速度,不必等待裝置自然重新啟動。縮短更新所需的時間,使用者就能更快收到重大修正,進而改善裝置的整體健康狀態。較快的採用率也能讓您更快發現回歸現象。
由於判斷裝置是否可重新啟動時需要考量多項條件,因此這項邏輯可更新。這些條件可能會隨著時間而變更,因此能夠更新這個邏輯,可確保重新啟動就緒信號保持有效。
模組邊界
在 Android 12 中,這個模組會包含下列新目錄中的程式碼:
packages/modules/Scheduling
裝置排程模組 (com.android.scheduling
) 會以 APEX 套件形式提供。
模組包含兩個 JAR 檔案:
依附元件
這個模組沒有外部依附元件。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-27 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-27 (世界標準時間)。"],[],[],null,["# Device Scheduling\n\nThe Device Scheduling module contains logic that detects whether or not the\ndevice is in an idle state, and may be rebooted without user disruption.\n\nThis module improves the uptake rate of software updates by\nproviding a reliable signal of reboot readiness to installers. A reliable reboot\nreadiness signal enables installers to reboot the device to apply an update,\nwith the knowledge that the user hasn't been disrupted by the update.\n\nAutomatically rebooting devices in an unused state allows for faster updates,\ncompared to waiting for the device to be organically rebooted. By reducing the\ntime taken for an update to be applied, users receive critical fixes quicker\nwhich improves the overall health of their device. A quicker uptake rate\nalso enables regressions to be found sooner.\n\nThis logic is updatable since determining the reboot readiness of a device\ninvolves the consideration of multiple criteria. These criteria may evolve over\ntime, so being able to update this logic ensures that the reboot readiness\nsignal remains valid.\n\nModule boundary\n---------------\n\nIn Android 12, this module contains code in the\nfollowing new directory:\n\n- `packages/modules/Scheduling`\n\nPackage format\n--------------\n\nThe Device Scheduling module (`com.android.scheduling`) ships as an APEX\npackage.\n\nThe module contains two JAR files:\n\n- `framework-scheduling.jar:` Contains the API surface that an installer\n interacts with. This is a part of the `bootclasspath`.\n\n- `service-scheduling.jar`: Contains a new system service,\n `RebootReadinessManagerService`. Loaded by the system server process.\n\nDependencies\n------------\n\nThis module has no external dependencies."]]