Android 10.0 #296
Open
Android 10.0 #296
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
am: d4f2831 Change-Id: I737fdd08ceea35db4158532cfa3a8a01fe5dbba7
Also clean up a few variable names. Test: Boot into recovery. Check key inputs. Change-Id: I058475ac22f3db8523bd8aa30ccb61be1ef45559
am: aefc9e3 Change-Id: I2bdfb43f7d161de8cda635a48547db15ce05438c
am: ea37122 Change-Id: I1b213b5c60621e47e63520659b81954b864ec960
am: fc7a0dc Change-Id: I0cddcea8559d8aa90db80be4a5f3ef5d667ad139
am: 7b8303f Change-Id: Ibf7bb5aec11fe3f236a15b2e30db43d09dc60e31
The wipe package used to open the zip file directly from the content string. Switch to use the interface from the new package class instead. Bug: 127071893 Test: unit tests pass Change-Id: I990e7f00c5148710722d17140bab2e343eea3b6b
am: 2a33682 Change-Id: I443b7120d47083bdc31412bc2d49dd61be4ba848
am: 682cd4f Change-Id: I2f85ee25631805263032e67ec35511b28c06640d
We have already switched to the protobuf format for new builds, and the downgrade packages will require a data wipe. So it should be safe to drop the support for text format. This also helps to save the issue when users sideload a package with a pending OTA, because the new CareMap contains the fingerprint of the intended build. Bug: 128536706 Test: unit tests pass, run update_verifier with legacy CareMap Change-Id: I1c4d0e54ec591f16cc0a65dac76767725ff9e7c4
We have already switched to the protobuf format for new builds, and the downgrade packages will require a data wipe. So it should be safe to drop the support for text format. This also helps to save the issue when users sideload a package with a pending OTA, because the new CareMap contains the fingerprint of the intended build. Bug: 128536706 Test: unit tests pass, run update_verifier with legacy CareMap Change-Id: I1c4d0e54ec591f16cc0a65dac76767725ff9e7c4 (cherry picked from commit aaa6103)
<stdint.h> for uint8_t; <stdlib.h> for free(3); <thread> for std::thread. Test: mmma -j bootable/recovery Test: Run unit tests on crosshatch. Change-Id: Id99b29b3d514f4e453983599c8b1aa6b0fab4ef8
am: 05f9a8e Change-Id: Icd531dd8a88a4c49c288edf5449e93e81ddde203
am: 6105a6f Change-Id: Ic511d7e2b7043905e3025493e7ad0cdb3fb05d62
…eMap" am: 2e6fbfc Change-Id: If9cd6ba2cf97395d05575eeb842176bc6ab1e5bf
Without this, installing the twrp app as system app leads to
reboot loops into recovery with log messages like:
java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {me.twrp.twrpapp: android.permission.READ_PRECISE_PHONE_STATE, me.twrp.twrpapp: android.permission.BATTERY_STATS, me.twrp.twrpapp: android.permission.PACKAGE_USAGE_STATS}
Change-Id: I6156323ea0d23512b0d7eefbd03aa627f3002ae8
(cherry picked from commit 86a4370)
when unmounting system /system_root/system is symlinked to /system on devices built with BOARD_BUILD_SYSTEM_ROOT_IMAGE Some ZIPs don't play well with a symlink when trying to mount to /system. Change-Id: Ifb0a105ddc0337353a7e1ac234c9f1e5b387e992 (cherry picked from commit 589daae)
Change-Id: I3762fb3e2c3ffb4cbdc6d93ce424cacc7e0ef418 (cherry picked from commit e0e4340)
Change-Id: I465eb02bfeb1feeb087458955241c1456b0ef496
* these type of vibrators are present in newer devices based on board sm8150 & above. Like Oneplus 7 series, Redmi K20 Pro, etc. * to enable it add TW_SUPPORT_INPUT_1_2_HAPTICS := true in Boardconfig.mk * you will need to add the vendor vibrator service to init and run it in your device tree Change-Id: I0fe6612def149e70808ca41829b6f7ba0b23cd62 Signed-off-by: Mohd Faraz <androiabledroid@gmail.com> (cherry picked from commit 909daa9)
Change-Id: I18bffa454ad64d70c5efedbf174887571e95b734
We are now requiring fstab v2 for android-10+ trees. You can specify twrp flags using /etc/twrp.flags to label and annotate partitions. This patchset uses fs_mgr to load the super partition and build device mapper blocks off vendor and system depending on the slot in use. These are mapped to partitions in TWRP and allowed to be mounted read-only. The super partition is also mapped into a TWRP partition in order to backup the entire partition. You cannot backup individual device mapper blocks due to the device can only be read-only. Therefore you cannot write back to the device mapper. Change-Id: Icc1d895dcf96ad5ba03989c9bf759419d83673a3
This patch uses the loop device to mount files under /sbin/ from /system/apex in order for the device to use libraries or other files store inside these files. Each apex file is mounted over a loop device into a directory correpsonding to the apex filename under /sbin/. Once apex mounting is completed, TWRP will set a property twrp.apex.loaded to true so that init can use them as a LD_LIBARY_PATH source. Change-Id: I69f14a969123ac9cf1afc85b6cf76836cb092fb2 Change-Id: Ica6a7d8e479bcaec8bec4483b5e8d2b45ee105fb
* Needed for the LG V30, G7, V35, V40 * Use TW_HAPTICS_TSPDRV in your BoardConfig.mk to enable it. Change-Id: I0970ed5c046e851f7e6f562283523c7214c8d2b5 (cherry picked from commit 314cbd5)
Change-Id: Iefa73425fc13f41f5a267cce0c5d4047edc25e9e (cherry picked from commit 186eb70)
* since commit: TeamWin@a2bd7b7 after factory reset /data/recovery doesn't recreates in A-only devices. * so fixes issue flashing newer roms need access to /data/recovery Signed-off-by: Mohd Faraz <androiabledroid@gmail.com> Change-Id: I02cb67f7161571b1aa02784049231d42872a3587 Signed-off-by: Mohd Faraz <androiabledroid@gmail.com> (cherry picked from commit bcbe94e)
Building with TW_OEM_BUILD results in errors during compilation: error: unused label 'error' [-Werror,-Wunused-label] error: unused parameter 'allow_commands' [-Werror,-Wunused-parameter] These changes are required to allow compilation to complete. Change-Id: Iddc5bf1b90120de19a472c48b21d3531b758cacf (cherry picked from commit 0cd6be9)
For example now in Install menu we are seeing all files with .zip extension, after this commit we can see also files with .ZIP extension. Just add the extension between ";" separator. Change-Id: I6ddd2a812a182570af3d76711b1e3e13740a466b (cherry picked from commit 2702094)
- Should not be determined by whether support exists in TWRP - Set to 0 by default if FBE is not detected This also prevents the wrappedkey check from running on FDE devices Change-Id: I85d1952facdfafdaa1571fc1b11d4b4b7d9ba48e (cherry picked from commit cf0dffc)
This function will automatically decrypt .ozip file in a .zip and it will save the .zip in the same folder of the .ozip and with the same name. After the decryption, the flash will start. To enable this function you have to set a Boardconfig flag with the decryption key like i did here: mauronofrio/android_device_realme_RMX1901@a30625f Original projects: https://github.com/sabpprook/ozip2zip https://github.com/bkerler/oppo_ozip_decrypt Change-Id: Ic93243a565008c442bcf2992069b2801532ac7c1 (cherry picked from commit 0ff5984)
Some of the partitions will not be unmount automatically. They shouldn't
be mounted by default.
Bugs:
DM_DEV_REMOVE failed for [product]: Device or resource busy
Cannot unmap product before removing group qti_dynamic_partitions.
script aborted: assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))error: 25
Updater process ended with ERROR: 7
Change-Id: I7cbd5c29456ca2731b94a69bbf9ad77058cef09c
Bugs: E:Cannot restore super -- mounted read only. Change-Id: I07891b3f45a8601c1cafa45f9dd2a7a94482ac06
fscrypt aosp doc: https://source.android.com/security/encryption/file-based kernel fscrypt doc: https://www.kernel.org/doc/html/v4.18/filesystems/fscrypt.html This commit implements the ability for TWRP to use fscrypt to decrypt files on the fscrypt implementation. It has been implemented mostly in a new successor library to e4crypt called libtwrpfscrypt. Most of the code was ported from AOSP vold. Notable updates include: - updated policy storage by libtar - lookup of fbe policies by libtwrpfscrypt - threaded keystore operations Big thanks to Dees_Troy for the initial trailblazing of encryption in TWRP. Change-Id: I69cd2eba3693a9914e00213d4943229635d0cdae
Change-Id: I6348511087aca6fc722dc48677794e0d8b4a63fa
Commit imported from: https: //github.com/LineageOS/android_system_vold/commit/ce024f07c23d0649635a336fff389332b9806f48 Change-Id: I924a9fcbac7d790609fbafcf8c12654fdb267e32
Importing is_wrapped_key_supported_common from android-9.0 branch Change-Id: I7a13b40e365a984a90a661e6c2c71cfa5b725a11
Importing this commit: mauronofrio@f999d65 Change-Id: If73dc534ddf6c8b96ce2789789f25ce432428aa5
Importing of this commit: LineageOS/android_system_vold@944c48d Change-Id: I048a6c2aeff2591135f47223a99af5ddd215703c
Change-Id: Ia3c266bb32e31354375b633c4801e486f664539a
Change-Id: I0bb9d4ceab83feff19571004f7dccd360ddceac0
This setting in the board will help if it takes longer for the touchscreen driver to initialize. Use TW_DELAY_TOUCH_INIT_MS := nnnn where nnnn is in MS. Change-Id: I0a5c602edfe1214d64adadc980921a7bc0aa2bc5 (cherry picked from commit c6e2cfe)
Change-Id: Ica7dfbfd46c06618240fb06fce9c4b31103ec506
This patchset is now exlcuding /data/cache from backup, and removing it from the wipe exclusion list to prevent errors on restore and wiping /data. This patchset changes the directory from /data/cache to /data/recovery for TWRP to store logs and other file information. This will help with AB devices that don't want recovery to mess with /data/cache. This patchset will make ORS use /data/cache for AB devices. Remove policy code because we don't need to set a policy for the recovery directory. Change-Id: I1d140276314fd34804a72297d6e25a52e58210a0
* missed in TeamWin@3754fab Change-Id: I8fc3719e7f98c3d9b5fd96a9820b84773d4f5d7d Signed-off-by: Mohd Faraz <androiabledroid@gmail.com> (cherry picked from commit 25371a7)
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.
WE DO NOT MERGE PULL REQUESTS SUBMITTED HERE
You will need to submit it through OmniRom Gerrit
For changes to device trees, use TWRP Gerrit
This guide explani how to use Gerrit code review