summaryrefslogtreecommitdiffstats
path: root/recovery_utils (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Update health AIDL HAL to V2Jack Wu2022-12-241-2/+2
| | | | | | | Bug: 251425963 Test: Build Change-Id: I471f8fb9c7eb1044ea0b920d55728613188bfbdf Signed-off-by: Jack Wu <wjack@google.com>
* Enable ProjectID by default.Shikha Malhotra2022-03-171-11/+8
| | | | | | | | | This is in conjunction with enabling the project id for internal directories. The check whether project ids should be used or not, is done in installd process. If they cannot be used, then the installd process falls back to previous approaches. Bug: b/215154615 Test: atest installd/StorageHostTest Test: atest installd/installd_service_test.cpp Change-Id: I9a45a14cf10c040f7ce84f78c5e9c8ce60c17958
* Merge "GetBatteryInfo() also reads AIDL health HAL."Yifan Hong2021-12-072-28/+57
|\
| * GetBatteryInfo() also reads AIDL health HAL.Yifan Hong2021-12-072-28/+57
| | | | | | | | | | | | | | Test: call GetBatteryInfo manually with and without AIDL health HAL Bug: 170338625 Bug: 177269435 Change-Id: I123739e5bc372d5198fd711f592ceac04d46ab28
* | Use metadata_key_dir instead of metadata_encryptionJaegeuk Kim2021-12-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Eric pointed that metadata_key_dir is what specifies that metadata encryption is enabled, whereas metadata_encryption is the metadata encryption options, which don't have to be specified if the default options are sufficient. Bug: 208161227 Fixes: 80a1d8e34116 ("Avoid to format raw disk if metadata encryption is enabled") Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Jaegeuk Kim <jaegeuk@google.com> Change-Id: I390450ba49c528b1f465c247d32174d36c7937a2
* | Avoid to format raw disk if metadata encryption is enabledJaegeuk Kim2021-12-021-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current flow is 1. factory reset formatted raw disk. 2. next boot tries to convert it to metadata encryption 2.a mount sda27 2.b umount sda27 2.c encrypt_inplace() 2.d fsck on dm-x 2.e mount dm-x The #2 flow is unnecessary, if we know the disk will be encrypted. And, that gives a change of the failure when unmounting the raw disk by starting some file operations on /data. That can cause the entire encryption failure. Bug: 208161227 Signed-off-by: Jaegeuk Kim <jaegeuk@google.com> Change-Id: Iaedfeb74bb6abb667efee6dcadf8d66272466ee0
* | recovery_utils: remove FDE supportEric Biggers2021-11-101-17/+3
|/ | | | | | | | | | | | | | Support for FDE is being removed from Android, having been replaced by FBE. This CL removes the FDE-specific code from recovery_utils: - Remove the code that wiped FstabEntry::key_loc if it is a block device, since key_loc was only used by FDE. - Remove support for reserving a crypto footer when formatting volumes, since crypto footers were only used by FDE. Bug: 191796797 Change-Id: I90b1e4cacd2f3e5cce77a82a0af744fcc7da9400
* [LSC] Add LOCAL_LICENSE_KINDS to bootable/recoveryBob Badour2021-02-141-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added SPDX-license-identifier-Apache-2.0 to: applypatch/Android.bp bootloader_message/Android.bp edify/Android.bp fuse_sideload/Android.bp install/Android.bp minadbd/Android.bp minui/Android.bp otautil/Android.bp recovery_ui/Android.bp recovery_utils/Android.bp tests/Android.bp tools/image_generator/Android.bp tools/recovery_l10n/Android.bp uncrypt/Android.bp update_verifier/Android.bp updater/Android.bp updater/Android.mk updater_sample/Android.bp updater_sample/tests/Android.bp Added SPDX-license-identifier-Apache-2.0 SPDX-license-identifier-MIT SPDX-license-identifier-OFL to: Android.bp Android.mk Bug: 68860345 Bug: 151177513 Bug: 151953481 Test: m all Exempt-From-Owner-Approval: janitorial work Change-Id: I3da761b525452838977297f773974000d4de7bd6
* Rename external storage properties.Martijn Coenen2020-04-151-2/+2
| | | | | | | | | According to property naming guidelines. Bug: 152170470 Bug: 153525566 Test: N/A Change-Id: I64c6d8ca49fbd72f923a8794df0929bd500dd8e9
* Support F2FS compressionJaegeuk Kim2020-04-031-0/+6
| | | | | | Bug: 134580167 Change-Id: I13e481b14c1ba2f05c31ed0391a8ef29845933c9 Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
* recovery: add a way to enable metadata_csum for ext4Jaegeuk Kim2020-02-121-0/+9
| | | | | | | | Requires to add "metadata_csum" in fsmgr_flag of fstab. Bug: 149039306 Change-Id: I2b95dcaaf2ba224135ad51f117b7b01bbf342b7e Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
* Set Casefold and PrjQuotas in Factory ResetDaniel Rosenberg2020-01-251-1/+26
| | | | | | | | | | | | | | This sets up devices to have casefolding and project quotas if they have enabled the relevant product properties. For ext4, we must set wide inodes at makefs time, but other things are enabled by fs_mgr with tune2fs at boot time. Bug: 138321217 Bug: 138322712 Test: Enable on a device. Reformat from recovery. Check that /data has the expected values using tune2fs/f2fs.fsck Change-Id: If706a3cad591f311eb904df4deca531d0b3fe0c4
* [bootable][recovery] fix -Wreorder-init-listNick Desaulniers2019-10-111-1/+5
| | | | | | | | | | C++20 will require members in a designated initializer to be in order unlike C99. Bug: 139945549 Test: mm Change-Id: I6f8d658448f7e5dd980bf95b890b15cb0aab7407 Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
* minadbd: Return battery level via getprop.Tao Bao2019-10-051-0/+1
| | | | | | | | | | | | | `adb rescue getprop rescue.battery_level` returns the current battery level. Bug: 134560109 Test: Build and boot into rescue mode. Test: `adb rescue getprop ro.build.fingerprint` Test: `adb rescue getprop rescue.battery_level` Test: `adb rescue getprop` to dump all the properties. Test: Run recovery_unit_test. Change-Id: I78a9e8ab9783ffc8532cb93e6a64fb2157c19bd5
* recovery_utils: Use libvoid_headers.Tao Bao2019-10-031-4/+5
| | | | | Test: mmm bootable/recovery Change-Id: I2ad7620d0f967cb018a415358379c34804e232c5
* Refactor battery info querying functions into librecovery_utils.Tao Bao2019-10-033-15/+150
| | | | | | Bug: 134560109 Test: Run recovery_unit_test. Change-Id: Ibbcdcfd507fa23657ee7ff677208b0003ec382ba
* otautil: Factor out the utils that're private to recovery.Tao Bao2019-10-029-0/+1043
A number of utility functions are intended for serving recovery's own use. Exposing them via libotautil (which is a static lib) would pass the dependencies onto libotautil's users (e.g. recovery image, updater, host simulator, device-specific recovery UI/updater extensions etc). This CL finds a new home for the utils that are private to recovery. Test: mmma bootable/recovery Change-Id: I575e97ad099b85fe1c1c8c7c9458a5a43d4e11e1
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 16:12:55 +0200