A1601 RECOVERY #215
Open
A1601 RECOVERY #215
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: d1fa3c2 Change-Id: Ib7e71dd067f73367b3461de613e63e476ad8f1de
am: 8f7547e -s ours Change-Id: Ie480acb2efab18ec32c4964914457aac4f34e74e
am: 855eaff -s ours Change-Id: I25a554cd60a9e08d954180792c2b3d0931fe2400
am: 2abdb8d Change-Id: I0b2f63adc3b06b4ee72093821f31d76e6ccc82ef
am: 9893852 Change-Id: I0bec043db9e23cb7c47ed2929b906e42561eacef
Get rid of pixel offset variables, and use makefile variables in BoardConfigs. Bug: 37779982 Test: Verified vr ui has same behavior. Change-Id: Ifbf44e27d7101aedbe3c0e6db4b8181d56efadfd (cherry picked from commit 81a8e4c)
am: 20d40ce Change-Id: I83efb71cf8d36be932660645a36191be0f12ddc7
am: 674851d Change-Id: Ie94f4e605713dc9bb4a4e312edadc1e8120d860d
All cosmetic changes about indentation reformatting in this CL. Test: mmma bootable/recovery Change-Id: I4539e6244697d1f356b7eb10b961b52d7db561f7
Test: mmma bootable/recovery Change-Id: I66e328614423488a4027d7878f4569fbf3a3721e
* Use project pathmap when available for LOCAL_C_INCLUDES Change-Id: Iddc7cc8509d966307c4a490c9d6c15d761dbb3b4
…elease-4133428 snap-temp-L95800000077479875 Change-Id: Icd576b05deb207c83c312ad2b51437bd92264348
The install logging currently assumes that the build number is a 32-bit
integer and prints an error when that doesn't hold true. However, that's
only a convention used by Google builds.
From build/core/version_defaults.mk:
ifeq "" "$(BUILD_NUMBER)"
# BUILD_NUMBER should be set to the source control value that
# represents the current state of the source code. E.g., a
# perforce changelist number or a git hash. Can be an arbitrary string
# (to allow for source control that uses something other than numbers),
# but must be a single word and a valid file name.
#
# If no BUILD_NUMBER is set, create a useful "I am an engineering build
# from this date/time" value. Make it start with a non-digit so that
# anyone trying to parse it as an integer will probably get "0".
BUILD_NUMBER := eng.$(shell echo $${USER:0:6}).$(shell $(DATE) +%Y%m%d.%H%M%S)
endif
Change-Id: I8e7cec0618783f69545ba76d0dce2bbc1681784c
am: 30afdee Change-Id: Ibe47feaf6d00838db24b76a51e2418772f329e0d
am: 170aa1c Change-Id: Ia11eec1dc9c1b484f7f5cd67ff1792b5c3423a26
Execute mke2fs to create empty ext4 filesystem. Execute e2fsdroid to add files to filesystem. Test: enter recovery mode and wipe data Bug: 35219933 Change-Id: I10a9f4c1f4754ad864b2df45b1f879180ab33876 Merged-In: I10a9f4c1f4754ad864b2df45b1f879180ab33876
…elease-4136929 snap-temp-L91700000077883673 Change-Id: I14571553dae47515fe9fc4ec2dc02b62e8a1fbdc
am: 8e7db8f Change-Id: I81e0e1e088da045f217aff957c7c5730d09cabbe
am: 076aba3 Change-Id: I6a16dab86d41026f7a2501a3ee7601ae97c5dd72
Change-Id: I91b7e674cd74d9069ee0ae3e70dbfd4a6a051756
Change-Id: I9a6c5a1384bed7f0169d9af94ff8cb22913ff8e4
Support decrypting Pixel 1 devices using secdis method with the
gatekeeper instead of weaver.
Add a bit of a dirty workaround to a permissions issue that the
keystore presents because the keystore checks the uid of the
calling process and refuses to let the root user add authorization
tokens. We write the auth token to a file and start a separate
service that runs under the system user. The service reads the
token from the file and adds it to the keystore. You must define
this service in your init.recovery.{hardware}.rc file:
service keystore_auth /sbin/keystore_auth
disabled
oneshot
user system
group root
seclabel u:r:recovery:s0
TWRP will run this service when needed.
Change-Id: I0ff48d3355f03dc0be8e75cddb8b484bdef98772
Change-Id: I58d7aa61cdb5c954e0726644fdc25c58eed8e544
ZipUtil was deprecated at android-8.1 but it has been still used by zipwrap. So this patch fixes the missed header file at new android version. Signed-off-by: Humberto Borba <humberos@gmail.com> Change-Id: I60bf67292021f3b63fb1ee2b8774303d9300fa12
* /persist can be mounted early while TWRP is parsing the fstab so as soon as the partition is parsed, mount and adjust the time accordingly. * Store a backup settings file on /persist. Having a 2nd copy of the settings file in the /persist partition allows for early reading of the file and adjust timezone and brightness to user preference while still on TWRP splash. * Add the qcom ats time offset in TWRP settings file and use it if no better ats file is found. This will also allow devices with a persist partition, but no ats files in it, to adjust the time offset during early boot. * Use /persist/time/ as Qualcomm time fix source, based on Xuefer <xuefer@gmail.com> patch: https://gerrit.omnirom.org/c/27265/ https://gerrit.omnirom.org/c/24384/ Change-Id: I6c21538eec58d87edfb639d9ce3871f33b886c1d
…e a translated string is too long to fit in button." into android-8.1
…ll other translations" into android-8.1
…example where a string is to long to be displayed in the button (overlapping / cut-offs)." into android-8.1
Change-Id: I5b4ad0e2b1c5c6d886b8355c167ef9e137d1c349
Change-Id: I3ea752697cc7f085541d961a6185194badb99015
Change-Id: Ib3a188f867330013069b7d443bcbad5dc3bc1e90
Change-Id: Iad82fa5d90ce7f3e4b1cf5cd5c6d6fef644f6762
* Assume a user knows what they are flashing and skip the check of whether or not the build they are flashing is older than the TWRP image they are using (which really isn't at all relevant to the ROM's build date anyway). Change-Id: I74ca5a6dc604268bf38f85ec1861f3eaafd9bf06
update_engine_sideload reads /etc/recovery.fstab during its install process and the twrp.fstab format may not be appropriate for what fs_mgr expects. Change-Id: I059ef22c0e862e60a3bffe5259f70c714fe33ec6
Change-Id: Ib15052832c2b25465b8a1d5c30d4659653b99f09
Change-Id: If07b7655265c94ad6b7ffa06629252749b5616e9
Fix toybox build at android 8.1. PS: xzcat support removed Signed-off-by: Humberto Borba <humberos@gmail.com> Change-Id: I185231bacf24db073f66eb57a146d7d1b64ffc2a
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