summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-11-07Don't change the framebuffer target until we render a new oneandroid-sdk-4.4.2_r1.0.1android-sdk-4.4.2_r1android-4.4.2_r2.0.1android-4.4.2_r2android-4.4.2_r1.0.1android-4.4.2_r1android-4.4.1_r1.0.1android-4.4.1_r1kitkat-mr1.1-releasekitkat-mr1-releaseJesse Hall
Continuing to send the last-rendered framebuffer to HWC on subsequent frames allows the HWC to read partially-composed regions that haven't changed, instead of re-composing from scratch. Bug: 11573910 Change-Id: I8829877d2a06001f1e1b3f168cbba71c7b217b2d
2013-11-07Merge "Provide virtual display output buffer to HWC in prepare" into klp-devJesse Hall
2013-11-06Merge "Don't use implementation-defined format with CPU consumers" into klp-devJesse Hall
2013-11-05Provide virtual display output buffer to HWC in prepareJesse Hall
We were already making sure the HWComposer class had the handle before prepare, but it wasn't passing the handle along to HWC as intended. Partial fix for bug: 11430248 Change-Id: I25f672c4fdfaa6a81fe0acb24d9ad05153ee17dc
2013-11-04Don't use implementation-defined format with CPU consumersJesse Hall
If the virtual display surface is being consumed by the CPU, it can't be allowed with HAL_PIXEL_FORMAT_IMPLEMENTATION_DEFINED since there is no way for the CPU consumer to find out what format gralloc chose. So for CPU-consumer surfaces, just use the BufferQueue's default format, which can be set by the consumer. A better but more invasive change would be to let the consumer require a certain format (or set of formats?), and disallow the producer from requesting a different format. Bug: 11479817 Change-Id: I5b20ee6ac1146550e8799b806e14661d279670c0
2013-11-04Merge "DispSync: remove delay when enabling vsync events" into klp-devJamie Gennis
2013-11-01DispSync: remove delay when enabling vsync eventsJamie Gennis
This change fixes a bug that caused an extra frame of latency when enabling vsync event callbacks in DispSync. The bug was related to the logic that prevents the two events from firing with very little time between them due to updates to the vsync model. Bug: 11479720 Change-Id: Ie7eaff9e92ffb7b7b6cb4d3d4402c96cbd29af7e
2013-10-30Merge "EGL: rename CallStack::dump into CallStack::log" into klp-devIgor Murashkin
2013-10-25EGL: rename CallStack::dump into CallStack::logIgor Murashkin
Bug: 11324229 Change-Id: Ibac1be182c336e7aa5ac098f08d18b3c188964b4
2013-10-25Merge "Bug fixes for SensorService" into klp-devAravind Akella
2013-10-25Bug fixes for SensorServiceAravind Akella
i) Emulate Flush for AOSP Fusion Sesnsors on newer HALs that support batching. ii) Early return if there are no events for the current SensorEventConnection. Bug: 11325707, 11376538 Change-Id: Idb856302463649a99d3d5d0c965bb06ba06b8e1d
2013-10-25Native counterpart of new power manager methodMarco Nelissen
Cherrypicked from master. b/9464621 Change-Id: I54c0ed50a57ac870da91db8589a73a2c792dbd8d
2013-10-25Fix handling of undefined TARGET_FORCE_HWC_FOR_VIRTUAL_DISPLAYSJesse Hall
related to b/8316155 - Implement HWComposer 1.3 w/ virtual display support Change-Id: I2dc8d65a74174aa833cc491264f97f1f2df49307
2013-10-23Merge "Add a boardconfig to force HWC composition of virtual displays" into ↵Jesse Hall
klp-dev
2013-10-23Merge "Use implementation-defined format when HWC writes to output buffer" ↵Jesse Hall
into klp-dev
2013-10-21Only consume touches up until the frame timeMichael Wright
When resampling is disabled, it's currently possible to consume touches after the current frame time. This breaks some guarantees and could cause unexpected behaviors. Change-Id: I99908a2cac2df9f795dd4a07188b4451213cf3e4
2013-10-18Wait for buffers to drainAndy McFadden
When a BufferQueue producer disconnects and reconnects, we retain the previously-queued buffers but empty the slots. This allows the number of queued buffers to grow without limit. The low-memory killer does not approve. Bug 11069934 Change-Id: Ia2eaa954c7a3904b54209a3701dba01689e204d8
2013-10-17Add a boardconfig to force HWC composition of virtual displaysNaseer Ahmed
When this boardconfig is defined, even when all virtual display composition is done by GLES, the HWC will be forced to copy from the GLES framebuffer to the output buffer. On some hardware this allows HWC to do format conversions that would otherwise have to be done by the consumer, with worse power and/or performance. Bug: 8316155 Change-Id: If980ecc589f138cef063eafa757f7f748196713e
2013-10-17Use implementation-defined format when HWC writes to output bufferJesse Hall
When GLES isn't writing to the output buffer directly, request an implementation-defined format with minimal usage flags, leaving the format choice up to gralloc. On some hardware this allows HWC to do format conversions during composition that would otherwise need to be done (with worse power and/or performance) by the consumer. Bug: 8316155 Change-Id: Iee6ee8404282036f9fd1833067cfe11dbadbf0bf
2013-10-16merge in klp-release (no-op)android-cts-4.4_r1kitkat-cts-devEd Heyl
2013-10-15merge in klp-release history after reset to klp-devThe Android Automerger
2013-10-15merge in klp-release history after reset to klp-devThe Android Automerger
2013-10-15SurfaceFlinger: give SF its own vsync phaseJamie Gennis
This change allows SurfaceFlinger to run at a different vsync phase offset from that used by external listeners. Bug: 11175503 Change-Id: I561c53a5659fa6dc1e3e4ae30340f3c1a6adceb4
2013-10-15SurfaceFlinger: Add EventControlThreadJamie Gennis
This change adds a new thread for calling HWComposer's eventControl asynchronously. The DispSync-based vsync approach ends up enabling and disabling HWComposer's vsync callbacks at arbitrary times, and some HWComposer implementations do not have these calls optimized. Bug: 11175503 Change-Id: I719be82bd200b391c61d40863b991c7b59acdfd6
2013-10-15Merge "Disable hardware vsync when blanking the screen" into klp-devJesse Hall
2013-10-15Merge "SensorService Flush API bug fix." into klp-devAravind Akella
2013-10-15merge in klp-release history after reset to klp-devThe Android Automerger
2013-10-14SensorService Flush API bug fix.Aravind Akella
SensorService is dead locking itself when flush is called on older devices which don't support batching. mConnectionLock is acquired twice. Change-Id: I5c25585bfb2b396df4b05826a9cba1da7997a3ee
2013-10-14Disable hardware vsync when blanking the screenJesse Hall
Bug: 11220224 Change-Id: I99d0a42e1a6bb0aaf89706f6d100e9ef2a5deaa4
2013-10-14Filter out vsync events from HWC with duplicate timestampsJesse Hall
Bug: 11220224 Change-Id: I4efe0b66ea8969bf0ec3c4fcb325d354c8a0c315
2013-10-13merge in klp-release history after reset to klp-devThe Android Automerger
2013-10-13Merge "Adding PackageManager feature strings for stepcounter and ↵Aravind Akella
stepdetector." into klp-dev
2013-10-13Adding PackageManager feature strings for stepcounter and stepdetector.Aravind Akella
Change-Id: I75ec21900fdc3ea80b61ec12c851a0c5ce9c44e8
2013-10-13Merge "DispSync: don't compensate for wakeup latency" into klp-devJesse Hall
2013-10-13merge in klp-release history after reset to klp-devThe Android Automerger
2013-10-11Merge "Use black for blackout layer" into klp-devAndy McFadden
2013-10-11Change API from flush(handle) to flush(). Call flush on all active sensors ↵Aravind Akella
in the given SensorEventConnection. Change-Id: I4ef2bec80406c517903ab9782dc9eaf3fa8b7f36
2013-10-11Use black for blackout layerAndy McFadden
SurfaceFlinger was rendering dark purple for secure content, which showed up when we took a screen shot for the orientation change animation. Use black instead. Bug 11157921 Change-Id: I3895e8168891d49dc5b84eed599bcd0a303bb70a
2013-10-10Eliminate latency when resampling is disabledMichael Wright
Since the latency was introduced to avoid egregious errors during resampling, remove it when we aren't resampling. Change-Id: Ia8e9a9afb1e16212fec81a8c9c661c598e1b0ebf
2013-10-11Merge "Eliminate latency when resampling is disabled" into klp-devDave Burke
2013-10-11Merge "Change API from flush(handle) to flush(). Call flush on all active ↵Aravind Akella
sensors in the given SensorEventConnection." into klp-dev
2013-10-10Eliminate latency when resampling is disabledMichael Wright
Since the latency was introduced to avoid egregious errors during resampling, remove it when we aren't resampling. Change-Id: Ia8e9a9afb1e16212fec81a8c9c661c598e1b0ebf
2013-10-10Merge "Wake up disp sync thread when setting display period" into klp-devJesse Hall
2013-10-10Wake up disp sync thread when setting display periodJesse Hall
Bug: 10624956 Change-Id: I272c15f319521bfbd1bb70451366c7dd84d60bf9
2013-10-10Fix blank / partial screenshotsAndy McFadden
The screen capture code wasn't waiting for the render to finish, so sometimes you'd see an empty or partial image. Bug 11131777 Change-Id: Ic64087322ce3bb15bb5f4fb1eb07579880fe6197
2013-10-09DispSync: don't compensate for wakeup latencyJamie Gennis
This change removes the wakeup latency compensation from the software-generated vsync events. Choreographer can't handle timestamps in the future, so don't aim for early wake-ups with the expectation that the actual wake-up will be late. Bug: 11153576
2013-10-09Change API from flush(handle) to flush(). Call flush on all active sensors ↵Aravind Akella
in the given SensorEventConnection. Change-Id: I4ef2bec80406c517903ab9782dc9eaf3fa8b7f36
2013-10-09Fix blank / partial screenshotsAndy McFadden
The screen capture code wasn't waiting for the render to finish, so sometimes you'd see an empty or partial image. Bug 11131777 Change-Id: Ic64087322ce3bb15bb5f4fb1eb07579880fe6197
2013-10-09merge in klp-release history after reset to klp-devThe Android Automerger
2013-10-08merge in KQS81MEd Heyl
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-12 21:53:51 +0000