init: Enable adsprpcd instead of starting #612
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes the issue of the first boot on forceencrypt taking down adsprpcd without starting it back up again. init : processing action (vold.decrypt=trigger_shutdown_framework) from (/init.rc:715) init : Service 'vendor.adsprpcd' (pid 592) received signal 9 See: https://android.googlesource.com/platform/system/core/+/refs/tags/android-9.0.0_r39/rootdir/init.rc#716 "class main" brings it in sync with cdsprpcd, which is also in that class. We can put it into "main" because the adsp and slpi devices will have been and remain booted already when the vold.decrypt=trigger_shutdown_framework prop triggers, no need to wait until "late_start" to start the adsprpcd service back up again. btw... TOLD YA! :)
|
🤦♂️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the issue of the first boot on
forceencrypttaking downadsprpcdwithout starting it back up again.See: https://android.googlesource.com/platform/system/core/+/refs/tags/android-9.0.0_r39/rootdir/init.rc#716
class mainbrings it in sync withcdsprpcd, which is also in that class.We can put it into
mainbecause the adsp and slpi devices will have been and remain booted already when thevold.decrypt=trigger_shutdown_frameworkprop triggers, no need to wait untillate_startto start theadsprpcdservice back up again.btw... TOLD YA! :)