Omprakash Dhyade 9e3751980f surfaceflinger: Use only one EventThread when phase offsets are same. ... SurfaceFlinger uses two event-threads to support phase-offsets for application and SurfaceFlinger itself. Extra thread may cause scheduling issues and wake-up latency for either SurfaceFlinger or Application, depending on scheduling, even when running at higher priority as these threads have low-load and qualify for task-packing. Use single event-thread when phase offsets are same. Debug runtime service call behavior change when same phase-offset: 1018 (set phase offset for Application): will change both Application and SurfaceFlinger phase offsets. 1019 (set phase offset for SurfaceFlinger): Will be a no-op. Change-Id: I2514b4ff6249e9bce3eb19f60b1dfe0de12b86d9		2016-02-29 09:37:36 +00:00
build	native: Restore VM memory overrides	2015-10-12 23:36:09 -07:00
cmds	Themes: Reference app resource when compiling theme [1/2]	2016-01-20 13:32:23 -08:00
data/etc	native: add ambient temperature & relative humidity sensor features	2015-11-04 12:28:21 -08:00
docs	framework/native/docs: remove doc footer for jd output	2015-05-27 10:13:35 -07:00
include	Revert "Revert "gui: only support tertiary display if QTI_BSP is defined""	2016-01-09 17:50:43 -08:00
libs	binder: MemoryHeapIon: Fix size_t vs integer formatting mismatch	2016-02-20 03:10:19 +01:00
opengl	Android 6.0.1 release 3	2015-12-07 17:07:16 -08:00
services	surfaceflinger: Use only one EventThread when phase offsets are same.	2016-02-29 09:37:36 +00:00
MODULE_LICENSE_APACHE2	auto import from //depot/cupcake/@135843	2009-03-03 19:31:44 -08:00
NOTICE	resolved conflicts for merge of adee6b35 to honeycomb-plus-aosp	2011-01-17 14:17:12 -08:00