- 10 Jul, 2020 2 commits
-
-
Victor Khimenko authored
Bug: http://b/153609531 Test: m libbinder.native_bridge Change-Id: I3955d9b54aaea7a6b5b9bde81a336908a849cde6 Merged-In: I3955d9b54aaea7a6b5b9bde81a336908a849cde6
-
Victor Khimenko authored
Also make headers available for RenderScript. Bug: http://b/153609531 Test: m libarect.native_bridge Change-Id: Iee387d19d167d8b90f4bf3fae7869ea370025b9a Merged-In: Iee387d19d167d8b90f4bf3fae7869ea370025b9a
-
- 30 Jun, 2020 1 commit
-
-
Kevin DuBois authored
-
- 29 Jun, 2020 1 commit
-
-
Kevin DuBois authored
When an vsync timestamp is recorded that is anonmolous to the currently recorded timestamp ringbuffer, update the timebase for synthetic calculations. Test: 2 new unit tests Test: visual spot checking interactions on pixel4 device Test: uibench a/b anti-regression Test: dogfood with patch based one recent rvc build. Fixes: 159882858 Change-Id: Ie201cd593a54586d9b1f488c6d2ca44178d75cf1
-
- 27 Jun, 2020 1 commit
-
-
Vishnu Nair authored
[automerger skipped] Call Layer::getLayerDebugInfo from the main thread am: 927b3b12 -s ours am: bf6f3dec -s ours am: 1e4cccab -s ours am skip reason: Change-Id I04daedcb9a890083cc710bab30b295e14b9872ae with SHA-1 b123f47b is in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/11972490 Change-Id: I6dedd9fe0db79fdbb6b0438e826bb79f268c4f51
-
- 26 Jun, 2020 9 commits
-
-
Vishnu Nair authored
[automerger skipped] Call Layer::getLayerDebugInfo from the main thread am: 927b3b12 -s ours am: bf6f3dec -s ours am skip reason: Change-Id I04daedcb9a890083cc710bab30b295e14b9872ae with SHA-1 b123f47b is in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/11972490 Change-Id: I54d812d033e70db7c894d86478dbe9590d3c68bf
-
Vishnu Nair authored
am skip reason: Change-Id I04daedcb9a890083cc710bab30b295e14b9872ae with SHA-1 b123f47b is in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/11972490 Change-Id: I53cac8a7d2fc4efacab81cdee53cee592c59312c
-
Ady Abraham authored
-
Vishnu Nair authored
[automerger skipped] Merge "Call Layer::getLayerDebugInfo from the main thread" into qt-dev am: f3f2130e am: f403598e -s ours am skip reason: Change-Id I5537c53e8214e2785473839d71fd483d1a3219b6 with SHA-1 43bccf83 is in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/11973468 Change-Id: Ibb7ee588ffa7c168e6c6fb235214f1d70f465407
-
Vishnu Nair authored
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/11973468 Change-Id: I17c0038e40757656834779531635d315104cabc5
-
Vishnu Nair authored
-
Ady Abraham authored
When DisplayManager sets the DisplayConfigsSpecs with a policy that the appRequestRange is broader than the primaryRange, it means that an app can choose a refresh rate from the appRequestRange and not from the primaryRange only if that app explicitly specified a frame rate using setFrameRate API. However, to avoid cases where we switch the refresh rate back and forth from the two ranges, we are allowing only applications that their window is focused from WindowManager's perspective to select refresh rate out the primaryRange. This matches the behavior of an application that sets the preferredDisplayModeId. Bug: 144307188 Bug: 159940172 Test: adb shell /data/nativetest64/libsurfaceflinger_unittest/libsurfaceflinger_unittest Test: YouTube in PIP mode while device is restricted by primaryRange Change-Id: I26a9690210bb5771bd8aae2bff301031617f7c8f
-
Yiwei Zhang authored
Bug: 158431662 Test: enable the tracepoint on user build Change-Id: I0808d8fe6a8416534fbec5a273d668700f0f7129 Merged-In: I0808d8fe6a8416534fbec5a273d668700f0f7129
-
TreeHugger Robot authored
-
- 25 Jun, 2020 6 commits
-
-
Josh Gao authored
* changes: adbd_auth: return auth id when requesting a prompt. adbd_auth: improve logging.
-
Abhijeet Kaur authored
[automerger skipped] Copy Screenshot to fd if and only if user consent approved am: 90f82490 am: d1a1d648 -s ours am skip reason: Change-Id I0ede8bc8cf5333ea586218a37fd6456f782a50c7 with SHA-1 9ce94670 is in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/11950659 Change-Id: I363b2bd6b06ccf0a241f56ef75f0ec267dc4bd79
-
Abhijeet Kaur authored
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/11950659 Change-Id: I7e9e6f0ee94857d1846bf4dec63ecc211a068af3
-
TreeHugger Robot authored
-
Rob Carr authored
-
Josh Gao authored
There seems to be an additional underlying bug that causes the framework to send a spurious authentication denial, but this is still an improvement. Bug: http://b/159061108 Test: treehugger Change-Id: I7028292fbde157f02cc35c3a37ab5c49d68eaae6
-
- 24 Jun, 2020 4 commits
-
-
Josh Gao authored
When multiple auth requests come in (e.g. if someone connects over TCP and USB, or if we send a USB request, and then kill adb and try again), we need to know the ID assigned to the request to disambiguate. Bug: http://b/159061108 Test: manual Change-Id: I68cf2335c5958decf29e58ed9132735577a7e074
-
Josh Gao authored
Bug: http://b/159061108 Test: treehugger Change-Id: I4aa83e71ea99752dd819a5a5a9d7a050f49c1dae
-
Robert Carr authored
In the linked bug, there are traces documenting cases where the user observes jank while deferred transactions are in play. We can see several cases where the client gets stuck for a long time on dequeueBuffer. Around these times we can also see cases where latchBuffer aborts early due to the !allTransactionsSignaled condition. We expect all the transactions to be signalled at this point, because before handlePageFlip we expect to reach handleTransactionLocked, which should call notifyAvailableFrames, marking the sync points available based on the head frame number. However if we study the trace we also see there is an onMessageInvalidate, which contains a handlePageFlip but does NOT contain the handleTransaction before it which we would expect. However we know if onMessageInvalidate calls handlePageFlip (via handleMessageInvalidate) then it must have called handleMessageTransaction, as these two lines are right next to eachother. We can thus conclude that we see the problem because handleMessageTransaction didn't call handleTransaction due to runHandleTransaction evaluating to false. This makes sense in the context of recent changes. Previously deferred transactions would set the transaction flags continuously while they were pending, so the server would always perform transactions when waking up, and we wouldn't get in this condition. However, setting the transaction flags always triggers a wake up! But we don't actually want to wake up until the frame actually arrives, so first we tried setting the transaction flags without triggering a wake up. But we found this could prevent other people from triggering wakeups, so a recent CL modified it to set mForceTraversal instead. Intending to force that we call doTransaction from handleMessageInvalidate regardless of whether a new transaction has arrived (because we need to check if an old transaction is now ready). However, it didn't quite work because of this early abort due to runHandleTransaction. Bug: 159677043 Test: Existing tests pass Change-Id: I84f2a9cca2ebb3f59d30924efdb39c917f47111b
-
arthurhung authored
Currently, in order to detect occlusion input, all buffered layers would update input info into InputFlinger, so the window may contain null token, we should check if id is also identical to prevent get the wrong result Bug: 159349058 Test: Enable show tap, open bubble and watch logs. Change-Id: I8412812e9b100988ab380ad64366f2548e50d9e5
-
- 23 Jun, 2020 5 commits
-
-
Mady Mellor authored
This reverts commit 80d685ae. Reason for revert: seeing if maybe caused regression (b/159719013) Bug: 159719013 Bug: 159349058 Change-Id: Iac21f799822bab5c26b9753ed78617e0087810bf
-
Vishnu Nair authored
Fixes an issue where drawing state could be accessed from a binder thread. The function also mixed current state with drawing state incorrectly. The function now only retrieves drawing state. Bug: 150226608 Test: Steps in bug doesn't repro Test: atest sffakehwc_test Merged-In: I04daedcb9a890083cc710bab30b295e14b9872ae Change-Id: I04daedcb9a890083cc710bab30b295e14b9872ae
-
Vishnu Nair authored
Fixes an issue where drawing state could be accessed from a binder thread. The function also mixed current state with drawing state incorrectly. The function now only retrieves drawing state. Bug: 150226608 Test: Steps in bug doesn't repro Test: atest sffakehwc_test Merged-In: I5537c53e8214e2785473839d71fd483d1a3219b6 Change-Id: I04daedcb9a890083cc710bab30b295e14b9872ae
-
arthurhung authored
Currently, in order to detect occlusion input, all buffered layers would update input info into InputFlinger, so the window may contain null token, we should check if id is also identical to prevent get the wrong result. Bug: 159349058 Test: Enable show tap, open bubble and watch logs. Change-Id: Ia1841ba51bce00fc9901fdf7324e8e31d9737082
-
TreeHugger Robot authored
-
- 22 Jun, 2020 8 commits
-
-
Siarhei Vishniakou authored
The function getConnectionLocked can return null. We must check the result for null to prevent dereferencing null. Bug: 143459140 Test: none Change-Id: I43991ea2ac9e23b5d5fc198a0ac8622d83696d31
-
TreeHugger Robot authored
-
Yiwei Zhang authored
Bug: 159213110 Bug: 159505775 Test: atest libgui_test:SurfaceTest#DefaultMaxBufferCountSetAndUpdated Change-Id: Ia4f781e0715b3a4e55c598595746bc0d5c76e3ef
-
TreeHugger Robot authored
-
TreeHugger Robot authored
-
Abhijeet Kaur authored
Currently the dumpstate screenshot file is copied to the screenshot fd (provided by the API caller) even when user consent times out. Bug: 152944488 Test: BugreportManagerTest#normalflow_full Change-Id: I0ede8bc8cf5333ea586218a37fd6456f782a50c7 Merged-in: I0ede8bc8cf5333ea586218a37fd6456f782a50c7
-
TreeHugger Robot authored
-
Luke Huang authored
Make it up-to-date. Test: N/A Bug: 150371903 Change-Id: Ia1402a18d6d466ffbb0357127d7d45cf6c722550
-
- 19 Jun, 2020 3 commits
-
-
Brian Duddie authored
To maintain backwards compatibility, ensure that apps with target SDK set to P or lower get access to step count and detect sensors, regardless of their permission status. After a change was made to the app ops code in rvc-dev, this check resulted in compatibility breakage for some apps built with target SDK before Q. Fixes: 157638722 Test: confirm that a popular step counting app from the Play Store is able to receive step count events after the change (where it couldn't before) Change-Id: Idab0ec458221524997f68311f4c6b216c969cb61
-
Valerie Hau authored
Some clients of ASurfaceControl may not set callbacks. We do not want to call finalizePendingCallbacks in this case. Bug: 159231312 Test: build, boot, SurfaceFlinger_test, libsurfaceflinger_unittest Change-Id: I62dc270302a60274d8d1192d0e35ce3f48721e6c
-
TreeHugger Robot authored
-