- 20 Mar, 2014 2 commits
-
-
Marco Nelissen authored
* commit '1f70863d': Add support for writing byte arrays to parcels
-
Marco Nelissen authored
* commit '37b44969': Add support for writing byte arrays to parcels
-
- 17 Mar, 2014 1 commit
-
-
Marco Nelissen authored
b/13418320 Cherrypicked from f0190bff https://googleplex-android-review.git.corp.google.com/#/c/433320/ Change-Id: I2285df9e9d3dc8a6a54055b13b352b81660bf45d
-
- 11 Mar, 2013 1 commit
-
-
Jean-Baptiste Queru authored
-
- 06 Nov, 2012 2 commits
-
-
The Android Automerger authored
-
Mathias Agopian authored
If we switched from HWC to GLES but the dirty region was empty (could happen if the dirty region is outside of the screen for instance), we need to force a full screen composition. In this change we ignore the dirty region for the purpose of rejecting the whole update and we rely on the fact that it will later be expanded to the whole screen. This was the least risky fix. Bug: 7467760, 7452931 Change-Id: I2132f2f963b00a3ce7150adadb107b0367b3862e
-
- 30 Oct, 2012 1 commit
-
-
The Android Automerger authored
-
- 29 Oct, 2012 1 commit
-
-
Colin Cross authored
Dump /d/extfrag/unusable_index in bugreports. It shows the percentage of memory in each zone that is not available for allocations for each order. Change-Id: I2af6680cb609887ea7b3d6107d1aa88bd0206b52
-
- 26 Oct, 2012 1 commit
-
-
Mathias Agopian authored
we perform external display clipping only on the GL side (ie: not done on the h/w composer side, which is harder and would be too risky). in practice this means that WFD will be clipped properly, while HDMI *may* or may not depending on how hwc is used. Bug: 7149437 Change-Id: I92d4d04220db72b6ffb134c7fa7a93af569723a5
-
- 25 Oct, 2012 3 commits
-
-
The Android Automerger authored
-
Mathias Agopian authored
we perform external display clipping only on the GL side (ie: not done on the h/w composer side, which is harder and would be too risky). in practice this means that WFD will be clipped properly, while HDMI *may* or may not depending on how hwc is used. Bug: 7149437 Change-Id: I92d4d04220db72b6ffb134c7fa7a93af569723a5
-
Dave Burke authored
This reverts commit 225c66a4 Change-Id: If31a04b81052cbc7dd7bf237c07107c33066d03d
-
- 22 Oct, 2012 4 commits
-
-
The Android Automerger authored
-
Mathias Agopian authored
a misbehaving or malicious client could cause SF to crash by providing a "fake" IInterface. we now check the IInterface we get is our own and local. Bug: 7278879 Change-Id: Ia19d05902d4b2385c5a16416148378d4998833fd
-
Jamie Gennis authored
-
Jamie Gennis authored
This change adds support for displays that are not allowed to display surfaces with the eSecure flag set. All non-virtual displays are considered secure, while virtual displays have their secure-ness specified at creation time. Bug: 7368436 Change-Id: I81ad535d2d1e5a7ff78269017e85b111f0098500
-
- 21 Oct, 2012 1 commit
-
-
The Android Automerger authored
-
- 19 Oct, 2012 3 commits
-
-
Andy McFadden authored
The code that reserves display IDs was only run when a hardware composer was present. The eventControl() function, which handles enabling of vsync, was ignoring the request because the primary display didn't appear in its set of allocated IDs. This moves reservation of IDs for built-in displays outside the HWC-only block. Also, added a couple of warnings in eventControl(). Bug 7376568 Change-Id: I185ccdf817a25499b5c2668f8f6d594afb8c1568
-
The Android Automerger authored
-
Romain Guy authored
-
- 18 Oct, 2012 2 commits
-
-
Romain Guy authored
The shell property debug.egl.trace can now be set to: 0 disables tracing 1 logs all GL calls error checks glGetError after every GL call, logs a stack trace on error systrace logs each GL call to systrace Change-Id: I34a2a2d4e19c373fd9eaa1b0cd93e67c87378996
-
The Android Automerger authored
-
- 17 Oct, 2012 4 commits
-
-
The Android Automerger authored
-
Jamie Gennis authored
This change changes the animation transaction timeout from 500us to 5s. Bug: 7362633 Change-Id: I9bed8e74f726dae2daa398afc29babcea00d5b04
-
Jamie Gennis authored
-
The Android Automerger authored
-
- 16 Oct, 2012 8 commits
-
-
Romain Guy authored
-
The Android Automerger authored
-
Mathias Agopian authored
we were holding a reference (ie: pointer) to a sp<DisplayDevice> while processing the message. Meanwhile the object itself could go away and we would end up accessing a dead object. the root cause of the problem is that we are accessing mDisplays[] in a few places outside of the main thread. Bug: 7352770 Change-Id: I89e35dd85fb30e9a6383eca9a0bbc7028363876c
-
Jamie Gennis authored
-
Romain Guy authored
Change-Id: I2613aa32c29eddc52a00090656c1bd11f9f5732b
-
Jamie Gennis authored
This change adds a transaction flag for WindowManager to indicate that a transaction is being used to animate windows around the screen. SurfaceFlinger will not allow more than one of these transactions to be outstanding at a time to prevent the animation "frames" from being dropped. Bug: 7353840 Change-Id: I6488a6e0e1ed13d27356d2203c9dc766dc6b1759
-
Romain Guy authored
-
Romain Guy authored
Change-Id: I53ac91a9ce07b5dd5f2ee0e3cc5b65b6402f9229
-
- 15 Oct, 2012 1 commit
-
-
Jesse Hall authored
The screenshot is a GL_RGB texture, and the GL_REPLACE texture env mode uses vertex alpha for GL_RGB textures instead of alpha=1.0. Bug: 7340077 Change-Id: I6fbb907023e48f9c422b15a33da79757d6726840
-
- 13 Oct, 2012 2 commits
-
-
The Android Automerger authored
-
Kenny Root authored
-
- 12 Oct, 2012 3 commits
-
-
The Android Automerger authored
-
Jamie Gennis authored
-
Jamie Gennis authored
Bug: 7283132 Change-Id: I38116f39fc18212f2daab94bbfc3daaf89439fc4
-