MiPad4/android_device_xiaomi_sdm660-common
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
android_device_xiaomi_sdm66.../sepolicy/private/file_contexts

12 lines
513 B
Text
Raw Normal View History

sdm660-common: create and symlink a dummy /metadata/apex Google moved apex sessions directory from /data/apex/sessions to /metadata/apex/sessions after commit: "Move apex sessions directory to /metadata" https://android.googlesource.com/platform/system/apex/+/36cf4bbac6108898a531aacc102dcc489d791b37 Devices with a mounted metadata partition will have the needed directories set up by system/core/rootdir/init.rc. Xiaomi devices on sm6125 do not have a metadata partition out of the box, so things like "Google Play system update" will fail to install the update. Therefore, create a dummy directory under /data/vendor/metadata_apex and symlink it to /metadata/apex. The reason why the old /data/apex/sessions directory is not used for the symlink is that apexd will call migrateSessionsDirIfNeeded() to recursively copy things from the old directory to the new one. Creating the symlink from /data/apex/sessions may result in unintended behaviors. Signed-off-by: OdSazib <odsazib@gmail.com>
2021-02-09 00:04:23 -05:00
# Apex Metadata
sdm660-common: apex: Symlink metadata to existing sessions * Better we do this instead of creating extra dir
2021-02-16 06:44:40 -05:00
/data/apex/sessions(/.*)? u:object_r:apex_metadata_file:s0
/data/apex/active(/.*)? u:object_r:apex_metadata_file:s0
/data/apex/backup(/.*)? u:object_r:apex_metadata_file:s0
/data/apex/hashtree(/.*)? u:object_r:apex_metadata_file:s0
sdm660-common: create and symlink a dummy /metadata/apex Google moved apex sessions directory from /data/apex/sessions to /metadata/apex/sessions after commit: "Move apex sessions directory to /metadata" https://android.googlesource.com/platform/system/apex/+/36cf4bbac6108898a531aacc102dcc489d791b37 Devices with a mounted metadata partition will have the needed directories set up by system/core/rootdir/init.rc. Xiaomi devices on sm6125 do not have a metadata partition out of the box, so things like "Google Play system update" will fail to install the update. Therefore, create a dummy directory under /data/vendor/metadata_apex and symlink it to /metadata/apex. The reason why the old /data/apex/sessions directory is not used for the symlink is that apexd will call migrateSessionsDirIfNeeded() to recursively copy things from the old directory to the new one. Creating the symlink from /data/apex/sessions may result in unintended behaviors. Signed-off-by: OdSazib <odsazib@gmail.com>
2021-02-09 00:04:23 -05:00
sdm660-common: Use stock poweroff charging animation * It's best animation out there with battery level This reverts commit 9271fec5a44dccf04bdbdf4b6f7d04d58f8362d6. Signed-off-by: OdSazib <odsazib@gmail.com>
2020-12-05 03:45:08 -05:00
# Executables
sdm660-common: create and symlink a dummy /metadata/apex Google moved apex sessions directory from /data/apex/sessions to /metadata/apex/sessions after commit: "Move apex sessions directory to /metadata" https://android.googlesource.com/platform/system/apex/+/36cf4bbac6108898a531aacc102dcc489d791b37 Devices with a mounted metadata partition will have the needed directories set up by system/core/rootdir/init.rc. Xiaomi devices on sm6125 do not have a metadata partition out of the box, so things like "Google Play system update" will fail to install the update. Therefore, create a dummy directory under /data/vendor/metadata_apex and symlink it to /metadata/apex. The reason why the old /data/apex/sessions directory is not used for the symlink is that apexd will call migrateSessionsDirIfNeeded() to recursively copy things from the old directory to the new one. Creating the symlink from /data/apex/sessions may result in unintended behaviors. Signed-off-by: OdSazib <odsazib@gmail.com>
2021-02-09 00:04:23 -05:00
/system/bin/chargeonlymode u:object_r:charger_exec:s0
sdm660-common: sepolicy: Allow ota updater to access package file
2021-01-26 21:42:10 -05:00
# OTA packages
sdm660-common: create and symlink a dummy /metadata/apex Google moved apex sessions directory from /data/apex/sessions to /metadata/apex/sessions after commit: "Move apex sessions directory to /metadata" https://android.googlesource.com/platform/system/apex/+/36cf4bbac6108898a531aacc102dcc489d791b37 Devices with a mounted metadata partition will have the needed directories set up by system/core/rootdir/init.rc. Xiaomi devices on sm6125 do not have a metadata partition out of the box, so things like "Google Play system update" will fail to install the update. Therefore, create a dummy directory under /data/vendor/metadata_apex and symlink it to /metadata/apex. The reason why the old /data/apex/sessions directory is not used for the symlink is that apexd will call migrateSessionsDirIfNeeded() to recursively copy things from the old directory to the new one. Creating the symlink from /data/apex/sessions may result in unintended behaviors. Signed-off-by: OdSazib <odsazib@gmail.com>
2021-02-09 00:04:23 -05:00
/data/awaken_updates(/.*)? u:object_r:ota_package_file:s0
Reference in a new issue Copy permalink