Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

charger: allow devices to skip the initial display blank

The theory behind the blank was that the kernel would not
re-initilize the display on boot (and leave it to whatever
the bootloader configured it to) until after the first
blank request.

On some devices, the bootloader does not turn the screen on,
but it's done by the kernel and thus. This makes the extra blank at
start unnecessary.

Bug: 7319529
Change-Id: I9ad9856186df6e9e23ebbe86e83b641423e16dcb
Signed-off-by: Dima Zavin <dima@android.com>
  • Loading branch information...
commit 209c7b0fad9604d1dde1b74d9f9d577b923469fd 1 parent bdec5ea
Dima Zavin authored
Showing with 6 additions and 0 deletions.
  1. +4 −0 charger/Android.mk
  2. +2 −0  charger/charger.c
View
4 charger/Android.mk
@@ -8,6 +8,10 @@ include $(CLEAR_VARS)
LOCAL_SRC_FILES := \
charger.c
+ifeq ($(strip $(BOARD_CHARGER_DISABLE_INIT_BLANK)),true)
+LOCAL_CFLAGS := -DCHARGER_DISABLE_INIT_BLANK
+endif
+
LOCAL_MODULE := charger
LOCAL_MODULE_TAGS := optional
LOCAL_FORCE_STATIC_EXECUTABLE := true
View
2  charger/charger.c
@@ -975,7 +975,9 @@ int main(int argc, char **argv)
ev_sync_key_state(set_key_callback, charger);
+#ifndef CHARGER_DISABLE_INIT_BLANK
gr_fb_blank(true);
+#endif
charger->next_screen_transition = now - 1;
charger->next_key_check = -1;
Please sign in to comment.
Something went wrong with that request. Please try again.