diff options
| author | Dianne Hackborn <hackbod@google.com> | 2011-09-21 10:55:12 -0700 |
|---|---|---|
| committer | Dianne Hackborn <hackbod@google.com> | 2011-09-21 13:15:02 -0700 |
| commit | beae3bd6d34472d27ac5698f8d9bcbc12d0cf4f0 (patch) | |
| tree | cc0e7eeb8aa6d53c11412a31bb506e6d5fb274f1 /core/java/android/widget/TextView.java | |
| parent | a80599f5be394edd9f3918ba03c490850a1d9e7f (diff) | |
| download | frameworks_base-beae3bd6d34472d27ac5698f8d9bcbc12d0cf4f0.zip frameworks_base-beae3bd6d34472d27ac5698f8d9bcbc12d0cf4f0.tar.gz frameworks_base-beae3bd6d34472d27ac5698f8d9bcbc12d0cf4f0.tar.bz2 | |
Improvements to power manager turning on screen.
The keyguard/window manager recently got a facility to report when it is
okay to turn the screen on, when it knows the lock screen is displayed.
The power manager was using this wrong, just using it to drive the
flags given to the input system. Duh.
This change now uses the information to determine when to turn the screen
brightness up from 0. For an OLED screen, this is the time when the
user can actually see anything on the screen.
For LCD screens this may not be optimal, because the LCD may start running
before its backlight is turned on, so if you look carefully you may see
stuff before it is lit up. On the other hand, it is good to turn on the
display as early as possible (before waiting for the keyguard) because it
can take a little bit of time to get that and the touch screen going. By
only waiting on the display brightness, we allow turning on the screen
in the kernel to proceed in parallel with ensuring the keyguard is displayed.
Change-Id: I7ee4ce19fd4efd5b51872b855af6263f53cd6c30
Diffstat (limited to 'core/java/android/widget/TextView.java')
0 files changed, 0 insertions, 0 deletions