work around slight issue on Sensation device and Shooter, by using xres_virtual instead of xres to get the 4 extra bits needed. based of original changes from toastcfh and modified to not be hard coded 32 bit and work with 16 bit as well.
Change-Id: I15850a0969050598ffc14279b8b50c6fcb4682f7
ZTE Blade is an example of this type of devices.
The original patch comes from Sebastian404 -> http://goo.gl/QC37W
Change-Id: Idffd97adf7da8a352617342bb6ff2161e6eac3a5
This, for example, is for an LDPI device:
BOARD_RECOVERY_FONT_INCLUDE_HEADER := ../../device/geeksphone/one/font_7x16.h
BOARD_RECOVERY_FONT_WIDTH := 7
BOARD_RECOVERY_FONT_HEIGHT := 16
Change-Id: I71d2f420b9668b5767c9b0b5d90e3e523c56e873
Make ui_init() clear the framebuffer memory it maps in so the user
isn't treated to a visible flash of random bits on recovery startup.
Call ui_set_background() (to show the installing icon) right after
ui_init() to display something while device_recovery_start() is
working (which can take a second or two on some devices).
Bug: 3145331
Change-Id: I11e7859fab5847370ea4f4932c3fb1558af26c5d
Instead of six separate images for the left end, right end, and tiled
center portion of the full and empty progress bars, just use two
images: a full bar and an empty bar. Draw the left side of the full
bar and the right side of the empty one, moving the boundary rightward
to "fill" the bar. This makes recovery trivially smaller, and allows
fancier images to be used as progress bars.
Support paletted PNG images as resources.
Take some device-specific details of the recovery UI (eg, what keys to
press to bring up the interface and perform actions, exact text of the
menu, etc.) and split them out into separate C functions. Arrange to
take implementations of those functions from the appropriate vendor
directory at build time. Provide a default implementation in case no
vendor-specific one is available.
