Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I41d34c587e13dc69f9dfe253f88b08a6a6c127c7
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Ie0f93184e2d531e523fa029e7fb354d06fa1b199
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Icde2664f6b4d13a40d38bfe0a1ad51214506457f
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I7c460571c761166c1c3ed8a6d3ff1461ece96a9f
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I381f16450d501059c8ca07a6ece058bd476003bb
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Id42ee657b863d89294c4d6f77c4823e7ba463bc6
|
|
Process of tombstoned have changed the generation flow for
tombstone, and dropbox could not be notified when generating new
tombstone file any more, so dropbox could not copy and compress
tombstone file to /data/system/dropbox. We need to modify
observer events from CLOSE_WRITE to CREATE, and it could
work normally.
Bug: http://b/111608961
Test: 1 After tombstone is triggered, we could see the tombstone
file in the data/system/dropbox directory.
Signed-off-by: Haoran Li <lihaoran5@huawei.com>
Change-Id: I9d6a31773e4a58658ffab214b1e337f27e9f3ae6
(cherry picked from commit fe8d2c9a8c86bc842871129600ad9fbbb9b60ab3)
|
|
|
|
|
|
|
|
|
|
Tip appears the 1st time - when user swipe up from home for 3 times & never gone into overview from app.
Tip appears the 2nd time - if user "X" or ignores the 1st tip, we show it again after user opens 5 apps.
Tip appears the 3rd time - if user "X" or ignores the 2nd tip, we show it again after user opens 40 apps. (before it was 10 apps)
Tip never appears again - if user "X" or ignore the 3rd tip.
Change-Id: I8077be8ef9ae3a45d8a6ae131cec8dc10a614bc1
Fixes: 111413686
Test: manual test
|
|
pi-dev
|
|
Test: Settings no longer in memory
Bug: 110985973
Change-Id: I80570ad52cd986083d735c1b6c0d8b34d7feb58f
|
|
|
|
into pi-dev
|
|
A change in the logic of QuickStatusBarHeader#updateResources
mistakenly used quick_qs_offset_height for the total height of the qqs
panel instead of quick_qs_total_height. This caused the quick-quick
settings panel to be too short on devices which don't have a large
notch.
Test: visual, on device without a notch
Change-Id: I0deed2560328501e547b04239133e350cdac4ff6
Fixes: 111554577
|
|
|
|
|
|
Such that it gets executed after setSurface, in order that
mReqUsage has the correct flags set.
Test: Take trace, ensure that allocateBuffers actually allocates
in the right format/usage by ensuring that dequeueBuffer doesn't
trash them immediately again.
Bug: 111517695
Change-Id: I94b402d7b29d565155a77a2d09106246261712d2
|
|
On a fresh device, the home intent resovles to SetupWizard. After
setup is complete, it will resolve to the regular home app. In
order to accomodate for that, repin home app once user setup is
complete.
Test: Wipe device, complete SUW, inspect pinner
Bug: 111132016
Change-Id: I904ecd2fed26bc1a3baf45c1b54da5fc6352d773
|
|
Test: make ds-docs
Bug: 110268338
Change-Id: Ifaa4096d075500f1c7a53b1eec9e1944ed2ddda6
|
|
Fix TextureView.getBitmap to capture content only from the layer.
Bug: 111401911
Test: A new test TextureViewTest.testTransformScale is passing
Change-Id: I2b9cee17fc48de7b12ed03d5b4f173ce5445dbfe
|
|
|
|
Bug: 77808145
Test: Tried to install corrupt APK prior to the change, install failed
Test: Tried to install corrupt APK after the change, install succeeded
Test: atest CtsAppSecurityHostTestCases:CorruptApkTests
Change-Id: I19a69e52a17c1080beaf2cc575c32f564b1033a3
|
|
oc-dev am: e43837e258 am: dccb62bcca
am: 64cb4be887
Change-Id: Id7d4599c5d7d7c803e86afa88be582773c80741f
|
|
oc-dev am: e43837e258
am: dccb62bcca
Change-Id: I9e6762b25f001e31da7df0bb25984856989b9fd9
|
|
|
|
am: e43837e258
Change-Id: Ib0ef741f0188ff3e6edc52e20eae997e9dba56e4
|
|
* changes:
[automerger] Fix TrackInfo parcel write am: 0d2dc943dc am: 00b57fc9b7 am: 1bce1217ca am: 47c831e675 am: d6143e9307
[automerger] Fix TrackInfo parcel write am: 0d2dc943dc am: 00b57fc9b7 am: 1bce1217ca am: 47c831e675
[automerger] Fix TrackInfo parcel write am: 0d2dc943dc am: 00b57fc9b7 am: 1bce1217ca
[automerger] Fix TrackInfo parcel write am: 0d2dc943dc am: 00b57fc9b7
[automerger] Fix TrackInfo parcel write am: 0d2dc943dc
Fix TrackInfo parcel write
|
|
|
|
|
|
Codegen doc update + CameraDevice manual update about EXTERNAL
hardware level.
Test: check offline-sdk-docs output
Bug: 77861412
Change-Id: I70c87a176cf873cf8bec2037f973a94fe99aef2e
|
|
|
|
|
|
|
|
into oc-dev am: 8f1c70e49b am: d1f53d13a9 -s ours
am: 213af1a79e -s ours
Change-Id: If0154030422d4ddd2b4383f9e107125d67f7b409
|
|
into oc-dev am: 8f1c70e49b
am: d1f53d13a9 -s ours
Change-Id: I293fc38d50e75b0b021dff6af045ac8a2aa6927f
|
|
am: 8f1c70e49b
Change-Id: Ic103dfa909ca4567a815b16f0794baf74c1cf068
|
|
into oc-mr1-dev
am: 1e5152b539 -s ours
Change-Id: I2ada9a973b1728122a2beb5f47d105af4507c742
|
|
|
|
|
|
Keeping the code in memory of the currently set home app is
important for latency as we don't have any kind of starting
window/splash screen when pressing the home app to hide any latency.
Memory impact:
Pinning dex/vdex:
In practical scenarios, this should be < 500kb.
The home app is usually profile-speed compiled, for which the
resulting dex/vdex files are about 2 mb. However, during regular
use, at least 1.5 MB of it is referenced in memory. This makes
sense: By definition profile-speed only compiles the things that
is usually frequently executed during regular execution.
Pinning apk:
With Launcher 3 in practical scenarios this should be about 3.7 MB,
as the APK is about 5.7 MB but 2 MB are usually referenced in any
case.
Bug: 111132016
Bug: 78585335
Test: Inspect "adb shell dumpsys pinner" after boot.
Test: Check for pinned files after updating camera/home.
Test: Check for pinned files after user switch with different
default apps.
Test: Check for pinned files after bg-dexopt.
Test: Check for pinned files after bg-dexopt + kill pid.
Change-Id: I6cdbc06d089efeb1c72a51216879ba0573502009
Merged-In: I6cdbc06d089efeb1c72a51216879ba0573502009
|