882b0a59d8
Stop using system properties to publish information about the key character map path. Instead, we can retrieve it on demand by asking the window manager. It was possible to exhaust the supply of system properties when repeatedly adding and removing input devices. Bug: 5532806 Change-Id: Idd361a24ad7db2edc185c8546db7fb05f9c28669 |
||
|---|---|---|
| .. | ||
| egl | ||
| android_native_buffer.h | ||
| DisplayInfo.h | ||
| EGLNativeSurface.h | ||
| EGLUtils.h | ||
| FramebufferNativeWindow.h | ||
| GraphicBuffer.h | ||
| GraphicBufferAllocator.h | ||
| GraphicBufferMapper.h | ||
| GraphicLog.h | ||
| Input.h | ||
| InputTransport.h | ||
| Keyboard.h | ||
| KeyCharacterMap.h | ||
| KeycodeLabels.h | ||
| KeyLayoutMap.h | ||
| PixelFormat.h | ||
| Point.h | ||
| PowerManager.h | ||
| Rect.h | ||
| Region.h | ||
| VirtualKeyMap.h | ||