diff options
| author | Jesse Hall <jessehall@google.com> | 2012-11-08 11:55:14 -0800 |
|---|---|---|
| committer | Jesse Hall <jessehall@google.com> | 2012-11-14 22:55:09 -0800 |
| commit | e244db42da1cb07f53a1fc921b45d498000b56e8 (patch) | |
| tree | c9ccda894698e5fd14396d95d8dc02736ffcdb20 /docs/html/sdk/api_diff/11/changes | |
| parent | 5756c30096f98ed59230a86350537f726276dad5 (diff) | |
Handle hotplug events as described instead of rescanning
Hotplug events say which display they're for and whether the display
was connected or disconnected. Before, this info was ignored, and the
event just triggered a rescan of all displays. If a display was
disconnected and then reconnected quickly, the rescan would treat this
as a no-op or a device property change and wouldn't turn the display
on.
Now the display manager attempts to update its state with the change
the event describes. So a quick disconnect/connect cycle will cause
the display to be turned on since the display manager will have
updated its internal state to reflect the disconnect event, and will
treat the connect event as a new display rather than a device property
change.
Bug: 7491120
Change-Id: If16268fbd0708683f6401ea72fbee9fb2c3c8d19
Diffstat (limited to 'docs/html/sdk/api_diff/11/changes')
0 files changed, 0 insertions, 0 deletions