-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android 8.1 #199
Open
scarlet-glass
wants to merge
2,836
commits into
android-8.0
Choose a base branch
from
android-8.1
base: android-8.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Android 8.1 #199
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
…ses." am: d6fb1c6 Change-Id: I9b012c3096563e3c0187f644ed4fa930e785c502
…elease-4140700 snap-temp-L81200000078275553 Change-Id: I851cac137eb5838acd8d89f91b6664d2250e9910
Bug: http://b/37560614 Test: builds even after removing system/core/include/ziparchive Change-Id: Ib7ed45cafe83d24ed55aac28b4f41a073c371bc2
am: f9fe6a7 Change-Id: Iface325955657b6c8f72d19fbbe7b8e475a15fbb
am: 78ff083 Change-Id: I57e2b9a4e42e3e32e5f3d4ca550ea59898abbff1
WearRecoveryUI::draw_progress_locked() has declaration only, where the definition was deleted in commit 5e7cfb9. WearRecoveryUI::ClearText() is a duplicates of ScreenRecoveryUI::ClearText(). Test: Build swordfish recovery image. 'Run graphics test' and 'View recovery logs'. Change-Id: Ib66955d1d496f04359b4d6487160218e8f954478
am: f722fcf Change-Id: I621c528b73da0fade1473235ce2710cbd8d9bc95
am: c9e4118 Change-Id: Ib7ed03df1c1f23d4419cb932495f26f15006e3be
…elease-4144771 snap-temp-L10300000078657232 Change-Id: If037aa310a32dd1e7a448387a20d1e83ee3e960e
We're not actually following the gaps as in the comments. For example, Nexus 6P is supposed to use 220dp and 194dp gaps (top and bottom respectively), but the actual numbers are 185dp and 194dp. Because the animation icon and text sizes don't match the ones claimed (animation: expected 200dp or 700px, actual 800px; text: claimed 14sp, actual 76px). The top gap changes (shrinks) as we compute the baselines bottom-up. This CL switches to using computed gaps: the major UI elements always stay vertically centered, with identical top and bottom gaps. Bug: 63093285 Test: 'Run graphics test' on angler/volantis/fugu/ryu. Change-Id: I3cadbb34f728cf034afa47ac02a6deba8cb6b4e7
We're not actually following the gaps as in the comments. For example, Nexus 6P is supposed to use 220dp and 194dp gaps (top and bottom respectively), but the actual numbers are 185dp and 194dp. Because the animation icon and text sizes don't match the ones claimed (animation: expected 200dp or 700px, actual 800px; text: claimed 14sp, actual 76px). The top gap changes (shrinks) as we compute the baselines bottom-up. This CL switches to using computed gaps: the major UI elements always stay vertically centered, with identical top and bottom gaps. Bug: 63093285 Test: 'Run graphics test' on angler/volantis/fugu/ryu. Change-Id: I3cadbb34f728cf034afa47ac02a6deba8cb6b4e7 (cherry picked from commit 3250f72)
am: 344778c Change-Id: If58672e390c4794bc93946e6a090da88a7acc90a
am: 1783254 Change-Id: I022f5b36f750a6ee2640974ec8b2eb9bd1d504b9
am: f95e686 -s ours Change-Id: Iaa00625c3820ca4a88e1fe3dd0ef38dc03561a66
am: b649cad Change-Id: I28c43e6f673457b8765afd965762c09cd662e5b2
Move away from taking int* for the Y-offset. Change it to int and return the offset instead. Test: Check the recovery menu and 'Wipe data' menu. Change-Id: Ib15e070a0d576a0f8f66f35605cb8479e7071f26
My Nextbit Robin Android 7.1.1 want updates Android 8.1 |
GGL_PIXEL_FORMAT_RGBA8888 seems to work in this instance. Change-Id: I88fb3e53332f47952036ef6e617b3ea7d0b639a9
draw performance is significantly slower when drawing directly to the mmaped buffer. Instead, draw to a userspace buffer and memcpy() to the mmaped buffer on page flip. Change-Id: Ibf2cd4be4f5437b445e68c572ff76ad72d506b15
if we try and flip pages too quickly, the kernel returns -EBUSY. Use drmHandleEvent to wait for any previous flip to complete before attempting a new one. Change-Id: If3def889c0c89d7cfb8b7f13c4dae6d4b12760f9
Decrypting userdata is not needed when installing zips if we have a map of blocks to read, so skip the decryption. This allows to install zips with no user interaction and, more importantly, it allows to install zips on devices where TWRP can't properly decrypt userdata. Remove also the unneeded Mount_All_Storage() call, Install_Command() already mounts the needed partition. Change-Id: I91c69f84ecc2fe41c9567c40649e501af1cfb64a
For example on my device, the LG V20 (US996), the default time comes back as 2016 which doesn't trigger the fixup code. The actual time I picked was pretty arbitrary, but close to the current date, since we're checking if said date/time is reasonably accurate without the fixup code. Change-Id: I01db64777d7d0c5ce0710445cf88858d89656ac0
For devices with the Qualcomm RTC fix whose clocks need further tuning such as the LG V20 whose ats files produces the correct time except 46 years in the future. Takes adjustment in seconds and adjusts after reading the the ats file. Boardconfig.mk TW_CLOCK_OFFSET := -1451606400 Change-Id: I0b2d35dd0026ed18a7bbebf683517f7c0eaa53ff
* Separate stdout and stderr buffers: vdc's return codes get sent to stdout, but the possible presence of other error messages in the output buffer will cause a valid return from vdc not to be parsed properly, and subsequent decryption to fail due to "misunderstood" return code. eg on the U11+ (htc_ocm) libc will generate an error to stderr due to a missing property area resulting a proper connection to vold being incorrectly parsed, and breaking decryption. * Improve logging. Change-Id: I57987ebe4ee6754a78e79ca177506098f8301f8f
* Allow custom definition of strace path with TW_ flags. * `TW_CRYPTO_SYSTEM_VOLD_DEBUG := true` will use default path: /sbin/strace. * `TW_CRYPTO_SYSTEM_VOLD_DEBUG := /system/xbin/strace` will use the provided `/system/xbin/strace` path. Change-Id: I5e12a10176d17a4f26487de0976a776d48c4142e Signed-off-by: nailyk-fr <nailyk_git@nailyk.fr>
Enable a property when mounting partitions required for decryption, and disable when they are unmounted. This helps init scripts to react to such an event appropriately, for example by starting services critical for decryption that reside on said partitions. Change-Id: Ib6fa1e5c903d9c800fb145d582ced6cc7e0ab5b9
Add debug capability. Fix backup of images after tarred partitions with too much padding Add more md5 logging. Skip digest check if selected. Change ADB Backup version to 3 for new fixes to image padding. Change-Id: I0f76c0733c523717e4797d1a14c3ae47d046fc8c
It seems that old Scrypt-config.mk is unaware of arm64 architecture. In fact, crypto_scrypt-neon.c can be compiled into arm64 as well. This CL adds an arch section for arm64. Bug: 65425184 Test: adb shell /data/nativetest64/scrypt_test/scrypt_test Change-Id: Ib451de642c7cc4548bfdc0879781981654b21b8f Merged-In: If40a30378b8038324aad44071107130d7722e28d
This reverts commit 53c38b1. Change-Id: Id998923948fb51ef5640c8be8884801c4f8d90e3
This reverts commit 63d786c. These functions will be used for third party OTA zips, so keep them. Change-Id: I24b67ba4c86f8f86d0a41429a395fece1a383efd
See https://github.com/omnirom/android_bootable_recovery/issues/219 This reverts commit 34ad728. Change-Id: Ia659b49af8206ba74b098aa721099a180762bab5
Change-Id: I402be0241ba998ad7530f5226f205581dc33e538
Change-Id: Id3d2b15d6c0dad346282e59eb2f173da2776a905
Change-Id: I2ca7580bbde5a8903b9ba5c1513ddba887e8d49e
Thanks to David Viteri for this one. Signed-off-by: Humberto Borba <humberos@omnirom.org> Change-Id: I566179921ba1cdb3b79836eff2b78cd6289eff94
Change-Id: I17dcb8a2d77519799292d1c0fb5d94de21d7e6cb
Change-Id: Ica0c4033bc7148b1313b1671e91c5b92b09064c6
all (well I just checked LOS, aoscp and aicp) ROM scripts use "md5sum" as extension but TWRP checks only for the extension "md5". This change will also expects md5sum as the default digest extension and only if not found falling back to md5. Change-Id: Ia1dd072d77d53ed6c6ff13c6db730abdcdb56bb3
Change-Id: I8f92c19f9e947da29dc25f3b88f69413a13af64d
Change-Id: Ifea3aca26e8664416ec1b161d2b102a0592fc9c1 Signed-off-by: David Viteri <davidteri91@gmail.com>
csather79
approved these changes
Jul 14, 2019
csather79
approved these changes
Jul 14, 2019
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.
update 8.1