| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Commit I4b56db78d13931fdd79580b801260bdfca0e9726 intended to constrain
the log to the lower quarter of the screen, but miscalculated the
respective limit value. Also make sure to display the log starting from
the last line.
Change-Id: I87fb2f311ff312faeca8777559d46c1569f6b95f
|
|
|
|
| |
Change-Id: Ib924fe17aef856963e69d4e3768ac37ac0362fd9
|
|
|
|
|
|
|
| |
When left uninitialized, wrong pointer to text may be passed from
draw_screen_locked to draw_menu_item, causing segfault in gr_text.
Change-Id: I932dd8c4d3d28afe82decc46f1f0af20586d88df
|
|
|
|
|
|
|
|
|
|
| |
* pstore filesystem is evolution of ram_console and contains
kmsg from previous boot (previously in /proc/last_kmsg).
* Lollipop init.rc does this. If device doesn't have
pstore fs, it will simply be ignored
Change-Id: Id3bf8763ccde54f87fde5cdf2db511649c376aa4
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
|
|\
| |
| |
| |
| |
| |
| | |
Ticket: RM-234
Android 6.0.1 release 30
Change-Id: I7c9e7094fc968a7a57cf0c7c4409f8a76cbe7863
|
| |
| |
| |
| |
| |
| | |
Bug: 26960931
Change-Id: Ieae45caccfb4728fcf514f0d920976585d8e6caf
(cherry picked from commit 4f2df162c6ab4a71ca86e4b38735b681729c353b)
|
| |
| |
| |
| | |
Change-Id: Id606cef249a7464037443de6265055803c290d82
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Ticket: CYNGNOS-2213
Android 6.0.1 release 24
Change-Id: If49bb48c41ce36a2fcd4b7dcc6393e1e2b3c27a1
|
| |\ \ |
|
| | |\ \
| | |/ /
| |/| | |
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Bug: 26960931
Change-Id: Ieae45caccfb4728fcf514f0d920976585d8e6caf
(cherry picked from commit 4f2df162c6ab4a71ca86e4b38735b681729c353b)
|
| | |
| | |
| | |
| | |
| | |
| | | |
* KEY_HOME is used in a lot of devices instead of KEY_HOMEPAGE
Change-Id: I18ec415b4d7e5e1f97a88640b820c64dbc8bb634
|
| | |
| | |
| | |
| | | |
Change-Id: I9fc0fa29299610865f622dc296bdadff59d74447
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
https://android.googlesource.com/platform/bootable/recovery into cm-13.0
Android 6.0.1 release 22
Change-Id: I9a9bddd7f1d8dfc8cb91f4fe8d57e2d3df41f6eb
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit e5879c3639789d61803605c12371a4f291e0b3cc.
The swap in page flip code is not needed any more.
New changes take care of ABGR and BGRA formats swapping bytes in
png and drawing routines
See commit fd778e3e406a7e83536ea66776996f032f24af64
Bug: 26243152
Change-Id: I313ee41bee2c143b4e5412515285a65ac394ec77
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | | |
am 710b6bb9: am ec4b58ad: (-s ours) am ec63d564: Track usage of Vector / SortedVector from libutils DO NOT MERGE
* commit '838768ca57d087025dbd31587ee895150bca9e10':
Track usage of Vector / SortedVector from libutils DO NOT MERGE
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When there are 20 entries (like 10 last_log* and 10 last_kmg* in "view
recovery logs"), there's no "Back" entry. Because the number of entries
(21) exceeds text_rows (20) in WearRecoveryUI::StartMenu(). Since we
have scrollable menu, having more entries than text_rows won't be an
issue.
Bug: 23752519
Change-Id: I12573d7a34852a1a3d130c9e88522cee737eb08f
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Every watch has a (mostly identical) copy of the wear_ui. Factor them
out into a single copy for easier maintenance. Device-specific settings
should be defined in recovery_ui.cpp that inherits WearRecoveryUI class.
Bug: 22451422
Change-Id: Id07efca37d1b1d330e6327506c7b73ccf6ae9241
|
| | |
| | |
| | |
| | |
| | |
| | | |
Use lseek64 to determine file/block sizes
Change-Id: I5ae7b11d6cb612c84cb4be29d0e3fe1493b8e844
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add a system bar (navigation bar) similar to the main Android system
with back and home buttons. This makes it easier for users to figure
out how to go back on devices that lack hardware buttons, and also
provides a quick way to get back to the main menu.
Note only buttons that do not have a hardware equivalent are shown, in
order to prevent redundancy and confusion.
Change-Id: I7538749978837571a8c250c3c8e54ac127b39d84
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes the crash when a user presses a hardware back button
instead of the on screen menu item.
OPO-521
Change-Id: I579d2720cdf7256a269358d037582121425d7c25
|
| | |
| | |
| | |
| | | |
Change-Id: I15d5dc734adba58ca4d44a5818c23115481e0470
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It turns out, file names starting with @ are on the cache
partition and we don't want to remount it overriding the
selinux context.
OPO-428
Change-Id: I661a590c3c70d75a1255b25debad3f2cbeee59e8
|
| | |
| | |
| | |
| | |
| | |
| | | |
OPO-489
Change-Id: I157116fdc7c85a42ce3c978b52f949e3cbc25b31
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Some devices may want to react in new and innovative ways to the
invocation of rainbow mode. Allow for this deep integration.
Change-Id: I088487e42b71ebfa80ca3976be328f0336ec0805
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Mount the partition that is storing the OTA with
an override so that recovery can read it.
Change-Id: Ib87f27d4ca95f1a44de0477198c1de00552c0a8a
|
| | |
| | |
| | |
| | |
| | |
| | | |
We need to re-use this to get read access to OTA files.
Change-Id: Iaab91150ff30422f25139372c5cd9076f1670bd3
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The touch UI takes 3 text lines per menu item, so minimize header text
to compensate.
Change-Id: I468f404e1a3de6ef9dee63301bb050b64f8de211
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Most headers in recovery aren't very useful and so have historically
not been shown in the touch UI. But certain headers, such as those
shown by yes_no(), should be shown.
Change-Id: I8536c528d3b4b4fd6d506ecef25378149b4e9746
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This would allow people who gain access to a pin-locked device
to remove the pin and gain access to media. This will still allow
wipes from Android to preserve media.
Change-Id: I73bc9d176297081a41c8d29fc77638d665442fe8
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Do not require recovery binary to make toybox symlinks. It is not
necessary and provokes a circular dependency warning from make.
* Do not declare toybox symlinks and bu_recovery as additional
dependencies when in one-shot mode. This allows incremental
rebuilding of the recovery binary.
Change-Id: I5ba815ebd4ce5981f8be316ec5ab77272ff565cc
|
| | |
| | |
| | |
| | | |
Change-Id: I76587c4fa234c5aab52882492da295e70029f522
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Introduce a menu stack for navigating sub-menus. The menu data
structure format is a bit messy, but necessary in order to provide
a string list for the ui.
* Create "advanced" sub-menu for rarely used and dangerous commands.
* Create "factory reset" sub-menu for various reset and wipe commands.
* Separate "wipe data" and "factory reset" items.
Change-Id: Ib9bc6967b98d022880cfe7fa8e324cd64b07d248
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
During the Android 6 rebase, the 'm' options was missed in the
getopt handler, breaking the ability to do a full wipe triggered
from inside of Android.
CYNGNOS-1817
Change-Id: Ic88006abd18cc83dd4a9d7917f34d6c6c8115538
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
During a rebase, a line was dropped that shouldn't have been.
CYNGNOS-1747
Change-Id: I9c9729ba11599baad267d3769685124b422033f8
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Android 6 re-introduced MCS/MLS SELinux contexts. Unforunately,
this broke our previous SELinux model for walking /data and unlinking
everything but media. Fix this by mounting /data with a temporary
SELinux context that works with the previous model.
Ticket: CYNGNOS-1747
Change-Id: Id87ad3bb357102c3a8bd7c1417183d788ef858a0
|
| | |
| | |
| | |
| | |
| | |
| | | |
* Crank it up when installing
Change-Id: I997d937901ff446834e6c479aaf629bee51de388
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Upstream recovery doesn't provide a menu for non ENG/UserDebug
builds.
OPO-321
Change-Id: I01b285a40287be4147d15a70b91ad17a3c93da68
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
dragon kernel is compressed via lz4 for boot speed and bootloader
support reasons and recent prebuilts happen to include the gzip header
sequence which is causing imgdiff to fail.
Detect a spurious gzip header and treat the section as a normal section.
Bug: 26133184
Change-Id: I369d7d576fd7d2c579c0780fc5c669a5b6ea0d3d
(cherry picked from commit 0f2f6a746af517afca9e5e089a4a17be0a9766d6)
Signed-off-by: David Riley <davidriley@google.com>
|
| | |
| | |
| | |
| | | |
Change-Id: I0e02ce2501cea8e7620fc3afe2d996ab98d32f60
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
https://android.googlesource.com/platform/bootable/recovery into cm-13.0
Android 6.0.1 release 3
|
| |\ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
am ec4b58ad: (-s ours) am ec63d564: Track usage of Vector / SortedVector from libutils DO NOT MERGE
* commit '15da523e5fe7dbdc3a8d49c809042bc760081920':
Track usage of Vector / SortedVector from libutils DO NOT MERGE
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
(-s ours) am ec63d564: Track usage of Vector / SortedVector from libutils DO NOT MERGE
* commit '3c7f655bf0382776617d3c98293e28d9967c9a96':
Track usage of Vector / SortedVector from libutils DO NOT MERGE
|
| | | |\
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Track usage of Vector / SortedVector from libutils DO NOT MERGE
* commit '0e804d542a2c151d254cad0d8581d9709a394a9a':
Track usage of Vector / SortedVector from libutils DO NOT MERGE
|
| | | | |\
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Vector / SortedVector from libutils DO NOT MERGE
* commit 'd396b9dbd99924f7c8687227b22220a87c85d9c7':
Track usage of Vector / SortedVector from libutils DO NOT MERGE
|
| | | | | |\
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
SortedVector from libutils DO NOT MERGE
* commit '710b6bb9d7d36ce16453850efc3112016a77e9ff':
Track usage of Vector / SortedVector from libutils DO NOT MERGE
|
| | | | | | |\
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
from libutils DO NOT MERGE
* commit 'ec4b58ad8a21b511bf6b136792bb924eb6e9e299':
Track usage of Vector / SortedVector from libutils DO NOT MERGE
|
| | | | | | | |\
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
* commit 'ec63d564a86ad5b30f75aa307b4bd271f6a96a56':
Track usage of Vector / SortedVector from libutils DO NOT MERGE
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
bug: 22953624
Change-Id: Ifcc17e39433ac91ca41da5d336fb3006dfbb65a8
|