Project-1CE/frameworks_base - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2019-11-25	[DisplayEventDispatcher] Kick DisplayEventDispatcher out of libandroidfw.	Alec Mouri
	DisplayEventDispatcher will live in libgui for now, as a shim over DisplayEventReceiver. This is so that we can keep libgui out of the UI-renderer module while we can work on stabilizing the interface with libandroidfw for asset management required by graphics classes. It also doesn't make much sense to have display-event functionality in a separate grab-bag library, especially when there's two users, and there is potentially an opportunity to somehow merge with DisplayEventReceiver to simplify code a bit. Change-Id: Ife0f9c8ad2053437087fdbf0618b892928ce6864 Bug: 142760698 Test: builds
2019-06-07	DisplayEventDispatcher: use eConfigChangedDispatch	Ady Abraham
	In order to get DISPLAY_EVENT_CONFIG_CHANGED, eConfigChangedDispatch needs to be used when creating DisplayEventDispatcher. Bug: 131688378 Test: adb shell /data/nativetest64/libsurfaceflinger_unittest/libsurfaceflinger_unittest Test: trigger config change and observe logcat Change-Id: I0de8037ee5b024b7d9729750f582be919087be41
2019-02-22	DisplayEventDispatcher: add DISPLAY_EVENT_CONFIG_CHANGED	Ady Abraham
	Add a new event for display configuration change. This event will be sent by SF anytime it changes the display config. Test: Generate DISPLAY_EVENT_CONFIG_CHANGED and observe the log Bug: 122905403 Change-Id: Ifa473a34d7b313501e5e4e8a67186fb82754fdcd
2019-02-04	Generalize physical display management	Dominik Laskowski
	This CL enables the framework to manage an arbitrary number of physical displays. It also surfaces physical display IDs, which are stable across reboots and encode (model, port) information that will be propagated further up in a follow-up CL. Bug: 116025192 Test: Boot with more than two displays Test: Hotplug works with any number of displays Test: Verify stable display IDs with "dumpsys display" Change-Id: Idb2eaff66b2e0873be6ad27d337ff18b730d1331
2017-06-08	Properly run window animations at vsync-sf (1/2)	Jorim Jaggi
	- Add new Choreographer instance that runs on vsync-sf - Use this new Choreographer for WindowAnimator, and remove all the hacks around it Test: Open apps and close apps, notice no stutter Test: Screen zoom animations Test: go/wm-smoke Bug: 36631902 Change-Id: I988ae25645effc3ac20efa7cb9b68f23444da0d0
2016-01-22	ALOGE is not ALOGV	John Reck
	Change-Id: I973cd7ce28bed38934aab0818e581a948a12cb42
2016-01-21	Add choreographer API to the NDK.	Michael Wright
	Change-Id: Icb8cffd3cd3bd06814466be72db3e26f6a62cbc6