- 15 Dec, 2015 3 commits
-
-
Casey Dahlin authored
Test: AIDL integration tests pass Bug: 25969194 Change-Id: Ib7023c8e02af49e08c9921f1d097e5967c1d378e Signed-off-by:
Casey Dahlin <sadmac@google.com>
-
Casey Dahlin authored
-
Casey Dahlin authored
Change-Id: I5dfaca405f0f866e697d5ae546ead8a8eb6de7ca Test: make checkbuild succeeds Bug: 25868260 Signed-off-by:
Casey Dahlin <sadmac@google.com>
-
- 14 Dec, 2015 4 commits
-
-
Felipe Leme authored
-
Felipe Leme authored
Changes required: - Explicity casting function pointers. - Moving variables initialization before 'goto' statements. - Changing string references from 'char *' to 'const char *'. - Using 'extern "C"' so device-dependent implementation of 'dumpstate_board()' can be written in C or C++. BUG: 25563823 Change-Id: Ibeb70fd23e64e9b530736b554a372cb232fe1a44
-
Greg Hackmann authored
-
Mark Salyzyn authored
-
- 11 Dec, 2015 5 commits
-
-
Mark Salyzyn authored
Bug: 26029733 Change-Id: I2e5b44d642bbac7f62f63388dd8a3123f2abeafe
-
Mark Salyzyn authored
-
Mark Salyzyn authored
aosp is in C, internal is C++, struct must be explicit Bug: 24200279 Change-Id: I1c9d8156a86db6de73ee5b70063e63b38170b052
-
Mark Salyzyn authored
-
Mark Salyzyn authored
Extended csd EXT_CSD_REV, PRE_EOL_INFO, DEVICE_LIFE_TIME_EST_TYP_A, and DEVICE_LIFE_TIME_EST_TYP_B fields printed if available. Allow dumpstate access to /sys/kernel/debug/mmc0/mmc0:0001/ext_csd. Bug: 24200279 Change-Id: I310bdcf546a9307cf927f109359ad5a6d24b70f8
-
- 10 Dec, 2015 1 commit
-
-
Colin Cross authored
-
- 09 Dec, 2015 3 commits
-
-
Christopher Wiley authored
-
Christopher Wiley authored
Add another factory method that takes a message and service specific error code. Bug: 25800533 Test: system/tools/aidl integration tests pass Change-Id: I592cb7def0538576965d14c200ab58548b3bef32
-
Colin Cross authored
The realloc case in continueWrite should not increment the counter, the pointer passed to realloc is guaranteed to be non-NULL so the total number of allocations will not have changed. When realloc is called in restartWrite mData has not been checked against NULL, increment the counter if it was NULL. Bug: 26086286 Change-Id: I4c8af450cca1868b91793c0c5f0d8c4b4b5badbe
-
- 08 Dec, 2015 2 commits
-
-
Dan Stoza authored
- 07 Dec, 2015 3 commits
-
-
Dimitry Ivanov authored
am: 18ff6557 * commit '18ff6557': Replace libGLESv3 symlink with shared library
-
Dimitry Ivanov authored
-
Christian Poetzsch authored
In a4650a50 the concept of a maximum frame number allowance for the consumer was introduced. A call to acquireBuffers will only return buffers when their frame number is less-than-or-equal-to this maximum frame number. When SurfaceFlinger is the consumer, this maximum frame number is calculated in the onFrameAvailable/onFrameReplaced callbacks. These callbacks are called when a new buffer is dequeued by the application. The problem is that these callbacks are called _after_ the fence wait which is used to throttle the frame production of client apps. When the previous frame needs a long time to draw, those waits can potentially be a long time. As a result SurfaceFlinger won't do any composition with the new frame until the wait is over. Normally this isn't a big problem because there is a queue of buffers for SurfaceFlinger to work with. However, this changes massively when a client app is using a swap interval of zero. In this case, a new frame will instantly replace the previous queued frame. However, SurfaceFlinger doesn't know this until the onFrameReplaced callback gets called - which is delayed by the fence wait. If the timing is bad, SurfaceFlinger never gets a chance to pick up a new frame to do the composition with. We see this behaviour on our TC development system (slow GPU) with legacy on-screen benchmarks. Such apps are using a swap interval of zero and sometimes frames don't get updated for several seconds. This behaviour can be also seen on a Nexus5, although it isn't as obvious as on our TC. The fix in this cl is to move the EGL throttling to the end of the queueBuffers function. This ensures that if a frame gets replaced in the queue, all consumers who installed the callbacks, get called in a timely fashion. Change-Id: I36e9ecda162150f41e97d4fb7437963a3d86b371 Signed-off-by:
Christian Poetzsch <christian.potzsch@imgtec.com>
-
- 05 Dec, 2015 8 commits
-
-
Bart Sears authored
am: 3f46d82d * commit '3f46d82d': Revert "libbinder: Don't redefine B_PACK_CHARS"
-
Bart Sears authored
-
Bart Sears authored
This reverts commit 3eab1b40. Change-Id: Iedc99961c6014029722f814e621970c1732f9092
-
Elliott Hughes authored
am: f31cf3ab * commit 'f31cf3ab': Track rename from base/ to android-base/.
-
Elliott Hughes authored
-
Christopher Wiley authored
am: 7166e782 * commit '7166e782': libbinder: Don't redefine B_PACK_CHARS
-
Christopher Wiley authored
-
Christopher Wiley authored
This macro is defined in linux/binder.h which is *sometimes* included before binder/IBinder.h depending on codepath. Bug: 25868260 Test: Compiles Change-Id: Ied1e6658936668c16cbdacab3a3205107c907655
-
- 04 Dec, 2015 1 commit
-
-
Elliott Hughes authored
Change-Id: I62c18891ffe319d20ff084f5ca2aa0c038c23cd3
-
- 03 Dec, 2015 3 commits
-
-
Christopher Wiley authored
am: 823fa55a * commit '823fa55a': libbinder: Handle transaction failures correctly
-
Christopher Wiley authored
-
Christopher Wiley authored
Java code expects status_t != OK to be caught at the JNI level in android_util_Binder.cpp (see signalExceptionForError). We were incorrectly mapping this kind of failure to a special exception type and writing that exception type to parcels. Instead, refuse to write EX_TRANSACTION_FAILED to a parcel and return the status value instead. While here, remove non-trivial constructors to push authors toward the more explicit factory methods. Remove getException() and push authors toward using the simpler getter methods. Fix minor camelCase issues. Bug: 25615695 Test: system/tools/aidl integration tests still pass Change-Id: I7cad3ac8ae8300b5ac0b466606f4934d01e503c5
-
- 02 Dec, 2015 3 commits
-
-
Dan Stoza authored
Merge "bug#460672 framebuffer surface can't keep triple buffer if define NUM_FRAMEBUFFER_SURFACE_BUFFERS := 3"
-
james.zhang authored
bug#460672 framebuffer surface can't keep triple buffer if define NUM_FRAMEBUFFER_SURFACE_BUFFERS := 3 [root cause ] framebuffer surface is in the same process of surface flinger [changes ] call IGraphicBufferProducer::allocateBuffers on producer inside the DisplayDevice constructor to force-allocate all three buffers. [side effects] none [self test ]<tshark, enter and exit mainmenu>: ok [reviewers ] zhongjun.chen [change_type ] AOB --> google_original [tag_product ] common Change-Id: Ideb75d3aa1ed23b2fa4d263a120ea3ca39d01361
- 30 Nov, 2015 3 commits
-
-
Martijn Coenen authored
am: 83a98b10 * commit '83a98b10': Atrace: support streaming data to stdout.
-
Martijn Coenen authored
-
Martijn Coenen authored
Change-Id: I8534a9c69f25ecdd82230a5d8b4b8d1c4d58439e
-
- 23 Nov, 2015 1 commit
-
-
Casey Dahlin authored
am: 8f237272 * commit '8f237272': Add support for file descriptors and vectors thereof
-