| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
This is causing recovery to skip real input devices on some
samsung phones where sensors are registered as input devices.
So there more then 16 of them. (ex. ks01lte)
And EV_REL input devices already disabled in recovery ui.cpp if
BOARD_RECOVERY_NEEDS_REL_INPUT is not set. So do same here not to exceed
the limit of MAX_DEVICES
Change-Id: If3d6e29d00229278a8ef3dfa445393c9f3d5f361
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are devices with RGBA_8888 pixel format.
There are also recoveries like TWRP that have
alpha support and hence for a RGBA device, I expect
to be able to set TARGET_RECOVERY_PIXEL_FORMAT = RGBA_8888
It should be supported on BoardConfig to set the
correct PixelFormat for a device.
Although recovery does not have alpha, so it can
consider RGBA devices as RGBX, but it could do so
in future.
Change-Id: Id1f3b2fbfc8ad4cf0422614580e420196614f792
Signed-off-by: Arnav Gupta <championswimmer@gmail.com>
|
|
|
|
|
|
| |
Needed for newer hisilicon boards
Change-Id: I9a5d640b1168de518885b89f63499c6f31958b75
|
|
|
|
|
|
| |
And a few trival fixes to suppress warnings.
Change-Id: I38734b5f4434643e85feab25f4807b46a45d8d65
|
|
|
|
|
|
|
| |
Bug: 22231636
Change-Id: I103c8e906b7dd9862b7bb89d8642268e9a3006b4
Signed-off-by: Stéphane Marchesin <marcheu@chromium.org>
|
|
|
|
| |
Change-Id: I59e08a304ae514a3fdb6fab58721f11670bc1b01
|
|
|
|
|
|
|
| |
This lets us recognize whether we have up/down/power, say, and tailor
the UI accordingly.
Change-Id: If94e454f14243b59d2f473ac9a436bd60591da01
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously most devices would lose the character before a line wrap.
The log's text rendering was starting at offset 4 but none of the
arithmetic was taking this into account. It just happened to work
on the Nexus 9's 1536-pixel wide display (1536/18=85.3) but not on
a device such as the Nexus 5 (1080/18=60).
The only active part of this change is the change from 4 to 0 in the
gr_text call. The rest is just a few bits of trivial cleanup while I
was working out what was going on.
Change-Id: I9279ae323c77bc8b6ea87dc0fe009aaaec6bfa0e
|
|
|
|
|
|
|
| |
The zlib include was not required. libpng is now handled by referencing
the libpng static library
Change-Id: Ie4e0abad3fff5b763eba363d3d0fa96128ff49bc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[Problem]
Droid and animation color in recovery mode are incorrect
[Modify]
- Add support for flipping (zero copy) with RECOVERY_ABGR.
- Decodes PNG files to BGRA directly, and other fills, text and alpha blending are also done directly in BGRA (i.e. blits can still bypass conversion)
- Remove the BGRA workaround added previous for single buffer mode (f766396)
Bug:19216535
Change-Id: Ie864419fc6da776ff58b2d02e130f203c194500f
Signed-off-by: Tony Kuo <tony.kuo@mediatek.com>
|
|
|
|
|
|
|
| |
Allow factory test images to use minui functionaltiy
by making use of libminui dynamic library.
Change-Id: I63e77420d5addbcc6eebeedc213f629085766b4c
|
|
|
|
|
| |
Change-Id: I1ad97b5b62bddbcb1104fa0b4e54415b793a4194
Signed-off-by: Greg Hackmann <ghackmann@google.com>
|
|
|
|
|
|
|
| |
Isolate the code that interacts with fbdev, in preparation for adding
a new backend.
Change-Id: I19105e9da1ca6408cebc110f7e2bb5abfb481ee9
|
|
|
|
|
|
|
|
|
|
|
| |
If your screen is a TV, it may not actually be displaying the edges of
the framebuffer. Allow specifying an overscan percentage, and move
each edge of the framebuffer in by that percent of the width/height.
(The gr_* layer just lies to the caller about the size of the
framebuffer, telling the caller it's smaller than it really is, and
offsets all drawing commands to match.)
Change-Id: I11bb2feb39ae522bd3e957a14ebdecf3609e0fdc
|
|
|
|
| |
Change-Id: I0bf22c87c51a34ee4a839c4966277fad8150bd59
|
|
|
|
| |
Change-Id: Ifee94ac08028e62a40241a089ac7c36346fea3a3
|
|
|
|
|
|
|
| |
Add "RECOVERY_24_BIT := true" to the device's BoardConfig.mk to use
24-bit framebuffers in the recovery ui.
Change-Id: Iaede138bf7870becf237f12f1c0e49c9ff82d007
|
| |
|
| |
|
|
|