| Commit message (Collapse) | Author | Files | Lines |
|
We need these variables to enable blanking on devices which do not
support ioctl. The code depends on these variables, but we are not
exporting it.
|
|
Use LOCAL_REQUIRED_MODULES for Pie and up and
LOCAL_ADDITIONAL_DEPENDENCIES for Oreo and down.
Change-Id: I5365e782f98f3bbf4bf246be22c8f573824b65ee
|
|
Change-Id: I15f888d58c01de00920dc5c56148d363f4dd79b8
|
|
gr_clip was not calculating the correct values after the rotation
patch. Since gr_clip width and height instead of taking a second
pair of x,y coordinates, we cannot depend as much on the
ROTATION_X_DISP and ROTATION_Y_DISP macros. The simplest solution
was to call scissor with direct values in most cases.
Change-Id: I25f9d575ec6ddc430fca4555f29c8334441fc95d
|
|
* The existence of TW_ROTATION that implements this feature at the
level of calls to libpixelflinger API closely mirrors the existence of
ro.sf.hwrotation for surfaceflinger in LineageOS.
* A brute-force approach was previously attempted via the
BOARD_HAS_FLIPPED_SCREEN makefile flag. That code iterated over the
active display surface in a double-buffered setup, and performed a
"smart" memcpy from the UI drawing surface (gr_draw) onto the display
surface. The problem was that, without heavy loop optimizations, that
code could have never scaled for 90 and 270 degree rotation.
I tried and you could literally see the for loop with the naked eye
while the display surface was updating.
* That code is now gone, but support for BOARD_HAS_FLIPPED_SCREEN := true
is still there (now means TW_ROTATION := 180).
* This patch relies on the assumption that it is impossibly difficult
and non-portable to rotate whole framebuffer display surfaces, in a
way that is not dependent upon the graphics backend (adf, fbdev, drm,
overlay etc). Therefore, it identifies the rendering primitives that
the TWRP graphics stack exposes to the GUI application above, and
implements hwrotation inside each of those calls instead:
- gr_line(), gr_fill() - 2D geometric shapes (lines, rectangles)
- gr_blit() - graphical image resources
- gr_ttf_textExWH() - font rendering
- gr_fb_width(), gr_fb_height() - framebuffer resolution
* The gist is to keep the backend and framebuffer (dimensions, row size
etc) unchanged (because making changes there is asking for trouble),
but present an altogether different reality to the calling API,
according to the compile-time constant TW_ROTATION.
* All (x, y) API coordinates and shapes are transformed before being
actually rendered as (x_disp, y_disp) display coordinates.
* With TW_ROTATION := 90 or 270 you can turn a landscape device into
a portrait one, because the GUI is fooled by the reversed dimensions
reported by gr_fb_width() and gr_fb_height() and renders the UI as
for a different device.
* For blit and text rendering operations, figuring out the transformed
coordinates in display space is not enough, as the surfaces that are
to be rendered have to be rotated themselves. This is handled by
allocating an intermediary rotated surface on each rendering
operation (not ideal), so the code with the intermediary surface
is compiled out for the TW_ROTATION := 0 case.
* This is still not as bad as rotating the whole framebuffer though, and
on a msm8976 device the performance hit is not even noticeable (for
software rendering).
* Currently there is no attempt to make a connection between the
TW_ROTATION and the { RECOVERY_TOUCHSCREEN_SWAP_XY,
RECOVERY_TOUCHSCREEN_FLIP_X, RECOVERY_TOUCHSCREEN_FLIP_Y } settings.
Change-Id: Ic8966ad5360c8a499649fdb16e242286640fd992
Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
|
|
Change-Id: Ibd2f67391ce6d7774498839829e0de9391508781
|
|
Change-Id: Ia5cfb747f300557ebd719538244655c8b792c407
|
|
Fix rules for adf graphics to detect their presence when ninja
make files are used.
Change pixelflinger graphics mode so that colors display properly
on the Pixel 3
Change-Id: Ie7181be6c5e1e9a007b58fd798b2cef787ce4a01
|
|
external/libdrm was fully converted to Android.bp on Pie, causing
the wildcard to match nothing, even though libdrm is present in
the build tree. Change it to cover both build files.
Change-Id: I4b092b29ac021cc1aa3bcf7346b225b79fd99f4b
|
|
Change-Id: I7e847e76932a6ceea3e669e8b8b9ec35e5ef9d9d
|
|
This type of vibrator is found on newer kernel versions (4.9+) and
registers with LED class framework (located at /sys/class/leds/vibrator).
Change-Id: I85e93fdac17b3f4b6f2ae689bbbd490806b5c29b
|
|
Respect TARGET_RECOVERY_PIXEL_FORMAT config in screenshot, graphics.
This fixes other wrong theme color in minuitwrp on Xiaomi MIX 2S.
Change-Id: Ieb8480c411e2f0c72cc50ffca66943ab025e2b7e
|
|
See https://github.com/omnirom/android_bootable_recovery/issues/219
This reverts commit 34ad728823b186f93016387f39388cdbde35b3ed.
Change-Id: Ia659b49af8206ba74b098aa721099a180762bab5
|
|
if we try and flip pages too quickly, the kernel returns -EBUSY.
Use drmHandleEvent to wait for any previous flip to complete
before attempting a new one.
Change-Id: If3def889c0c89d7cfb8b7f13c4dae6d4b12760f9
|
|
draw performance is significantly slower when drawing directly to the
mmaped buffer. Instead, draw to a userspace buffer and memcpy()
to the mmaped buffer on page flip.
Change-Id: Ibf2cd4be4f5437b445e68c572ff76ad72d506b15
|
|
GGL_PIXEL_FORMAT_RGBA8888 seems to work in this instance.
Change-Id: I88fb3e53332f47952036ef6e617b3ea7d0b639a9
|
|
Change-Id: I58d7aa61cdb5c954e0726644fdc25c58eed8e544
|
|
Change-Id: Iaebc613a25a727a91205d2f361e9d7719036d88d
|
|
Change-Id: If3173ddbfaccb95cc48636240ee3a918dac1e23f
|
|
RECOVERY_GRAPHICS_FORCE_SINGLE_BUFFER := true
Change-Id: Id5144ea772c3b7ae382b064c41c23acdd0decb84
|
|
Includes some minor code clean up. Also we are now outputting the
name of the first mouse device that we encounter to make it easier
to identify which device(s) may need to be blacklisted.
Change-Id: I515baf92967390edd224728f3a7092239138e6b8
|
|
Change-Id: Ib114dcc7b48219142602a2fbc256e2a0258b26e0
|
|
Changes to fb_var_screeninfo can cause changes to
fb_fix_screeninfo. So, write back the force changes before fi is
read.
Change-Id: I721a960fa401ac5203ffc90bd3bfa2d7d0cfb292
|
|
This is required for a number of devices, particularly now that custom
graphics support is deprecated.
This change is required to officially support TWRP on the Huawei Plank
(aka the Honor 7).
Change-Id: Ie16ec557c75654c9c9e7a2877aee3339fc214d05
|
|
On some devices TWRP tries to access the framebuffer before all
device nodes have been created. Retry opening instead of crashing later.
Change-Id: I189a8fe80a8906b46fb6cece53c0bf83c00c0e09
|
|
Fix: use row_bytes instead of xres (should help on Shield tablet)
Speed: Moving the calculations out of the inner loop
Change-Id: Ie43ae5e94ae88822360900c7b4d852b7aab4379b
|
|
* Required for devices like Sony Huashan (dual backlighting paths)
Change-Id: I0f84623431aec91fafee6617c1d4c542e4566caf
|
|
Builder using a custom theme may have need for this. Add a flag to
easily enable jpg support.
Change-Id: Ica74f8cb1312d3193105f2201a5cf8073e2edc82
|
|
While not all of these old build flags are active or implemented
yet (and they may not ever be implemeted until we find a device
that needs them), we need to make sure that the old build flags
are only applied when actually needed. Since there are a lot of
device trees that probably won't get updated due to lack of device
maintainers, we will rename the build flags and fix up devices on
a case by case basis.
Also added some pixel format related build flags to the make file
from AOSP so that AOSP devices should work in TWRP without
additional build flags.
Change-Id: I11ab475297d02b6aeffe89404fe50b4799a36be3
|
|
Change-Id: Ide3510d2efc1c1b39c756691776938e42424b61d
|
|
The driver already has the capability to do so.
It needs only to be flagged, if required.
Change-Id: I1d81b00a7499e493d1dbba0a440b45fc1202f7c1
|
|
Change-Id: Iebb5763277eec83fd6db4fdca8b7ecfd3c78dc6b
|
|
Change-Id: I436bab6ef679168d3625d8e1837917077cf89908
|
|
Chances are there are not many themes in widespread use that are
using jpeg images, but this will be easy to revert back or even
just temporarily modify if we need jpeg support in a pinch.
Change-Id: If17b05ce3ebccce724fd74b26ed8ea91b287c3cf
|
|
Note: events.cpp is still old code renamed to cpp to make it
easier to call functions like gr_fb_width().
I had to modify AOSP fbdev code to provide a separate memory
surface for drawing to as drawing directly to the framebuffer
resulted in rendering taking about 5 times longer.
I also modified AOSP adf code to provide a separate memory surface
for drawing for the same performance reasons. The Nexus 9 supports
adf graphics.
Overlay graphics work on at least one device. Overlay provides a
separate memory buffer already so performance is good.
I do not have a drm device yet that I know of. I made some attempt
to update the drm code to determine the correct pixel format based
on the drm graphics format, but what is available in pixel flinger
and what is available in drm do not line up all that well. Reports
are that the Pixel C is using drm graphics, but performance is
slow, likely due to the use of a mmap instead of a memory buffyer.
Change-Id: Ibd45bccca6ac2cb826037aa9b2aa5065cf683eed
|
|
Change-Id: I40131f330e902afab033e810761bf98c07bbd03d
|
|
Change-Id: Iacd4bb78f551b51d092ecde09521b5541e7dadcd
|
|
This patch set removes support in TWRP for the old .dat file
format as well as support for the AOSP style fonts in header
files. We need TTF for scaling.
Note that the old AOSP style header font is still supported in
minui which is not used by TWRP.
Change-Id: I6124a3333d479f1fc668138f7e32c4be9b519552
|
|
Change-Id: Ia15d49e51cad5bc8a3291975e1ff515a2b1c419c
|
|
Fixes touch on Oppo R7 Plus
Oppo R7 Plus, when recovery is flashed and booted from the actual
recovery partition, the digitizer sends some extra touch data for
up to 10 different touch slots even if no actual touch is present
for those slots (ABS_MT_SLOT). This patch allows TWRP to handle
touch data properly for this device and maybe others.
Change-Id: I8f9171b605566788b674b3d4d96bd9f2f65736c2
|
|
Some devices don't support double buffering, so add
the flag TW_DISABLE_DOUBLE_BUFFERING to disable it
Change-Id: Ia9c233fa229ae9c221a6c6f219b216d1753052f4
|
|
Change-Id: I48a5b25a227afb8637fcce7e4a1e2fc6bcc56b03
|
|
when "gr_mem_surface.format = GGL_PIXEL_FORMAT_RGBA_8888", "gl->recti" will be crash.
this is a simple fix.
Change-Id: I39da7298286f34cdf7eae98f6b082c36695b222e
|
|
Change-Id: Ida48b7ff119030312836aa109072ac4de7c5b9d6
|
|
Change-Id: I0beb3b349efd4f08491c92bb51c12caf3653cb73
Signed-off-by: ramsudharsan <ramsudharsanm@gmail.com>
|
|
Use TW_NEW_ION_HEAP := true to use it
Change-Id: I2ad105fa6d122b460ed4b5dc78563077b7904567
|
|
Change-Id: I63eb29d7a39956d92cb5da81c5cb4405930d43ae
|
|
* Fixes for example 'j' in Roboto-Regular
Change-Id: I0cf778c99f391900e164be743165cf8aad891020
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
|
|
Change-Id: I2691e2ee4b272e7425d318b05404360598e2ea92
|
|
Also add a short while loop to wait for fb0 to be created as was
needed on the x86-64 target for the Android emulator.
Change-Id: Ib1b87bea028ac3eac0541283334a0157cdfbce11
|
|
This will significantly reduce theme maintainence and should be a
lot more sustainable over time. Eliminate most themes leaving only
5 remaining in 3 categores:
* watch_mdpi: 320x320
* portrait_mdpi: 480x800
* portrait_hdpi: 1080x1920
* landscape_mdpi: 800x480
* landscape_hdpi: 1920x1200
Add handling to map the old DEVICE RESOLUTION to the new TW_THEME
build flag. New devices should specify a theme using the new
TW_THEME build flag using one of the 5 values from the list above.
Long term we will eliminate the use of the DEVICE_RESOLUTION flag
in favor of the new flag.
Change the way sliders render so that they completely follow the
placement="5". This will probably break some custom themes but is
necessary so that we can retain the aspect ratio on slider images
and still have them rendered at the center of the screen.
Add code to the console slideout button so that it can be centered.
Centering the slideout button allows us to keep the button at the
center of the screen when retaining aspect ratios on the image.
Add more retain aspect ratios for home, back, slideout, folder,
file, and lock screen images.
Change the way we build the top bar in TWRP. It is now mostly
drawn using fill objects and the TWRP logo is a separate image so
that we can retain its aspect ratio during scaling. Thanks to Mark
Norelus for providing the TWRP logo.
Change-Id: I801a7b3163cad9ef353461f4c327690a9ccbb3aa
|
|
Change-Id: Ib100ccf3c8f6c622beb40b37ba3f61aad69d7d93
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
|
|
Change-Id: I63c8dcfa276bbeb550ca051a3a1a0646a2d07dc6
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
|
|
gui: fix terminal command unusual line breaks and missing characters at the end of a read buf.
Change-Id: I8d3d740b6066b1594c5148b2012f0e7bcbecc22b
|
|
Change-Id: I6e063fba8d58c8c53da6bca6292c84e3392aee50
|
|
If the <header> element doesn't exist, the header is not drawn.
- minuitwrp: add function for clipping all drawing to a rectangle
...and another one to cancel it.
Change-Id: If0f688a5debee6ebd9c457999fe571705a42c5cc
|
|
This fixes missing images after reloading the material theme 3 times.
Change-Id: I9af2a76b16e465fd2218e5f479c36a294590fa62
|
|
Change-Id: I36eb1d5e4f6908bad5ebb1fec692d8510529a14c
|
|
With this patch set, if needed, we scale the images during early
boot. TTF support is needed to properly scale the font. No font
scaling is done on the old style fixed width font used in the
console.
Special thanks to _that for figuring out the scaling and blending
function calls to make this possible.
Change-Id: If2f79bef16d6db2e1298bfc3d00c9bcca2bee37a
|
|
- add a timeout to ev_get
- set timeout to 1 second when idle
- delay timeout for 15 frames to keep animation objects working
- stop kinetic scrolling immediately at end of list
Change-Id: I77138055c464b65b71e296f9c7ef63ea06809bc1
|
|
- Process multiple input events per frame even if rendering takes longer
than 33 ms. Limit minimum frames per second to 2 instead, allowing us
to catch up with the input events. The lag was especially visible when
using the mouse.
- Move blankTimer calls to the main input function so that moving
the mouse also unblanks.
- Fix a compile error with event logging.
Change-Id: If9e0360f5cc0562c4356611afc61b6d583fb1ec4
|
|
This also makes the hardwarekeyboard.cpp file that I created for
the Asus Transformer tablets with a keyboard dock the default
hardware keyboard handler. USB keyboards should work properly now
if present for keyboard input.
Change-Id: I724606e91ffe2a55265a9d1cb1ec714de244d38b
|
|
Change-Id: I3efc10e2c9759a358ded5b46f6125958e6d6bd66
|
|
AOSP and other ROM trees now do a rm -rf of the res folder during
the ramdisk creation process that removes the TWRP resources.
Using /twres instead of /res works around this issue making TWRP
more compatible with AOSP and other build trees.
Change-Id: I0d4c7e06ca381ac5aa0069b6f2b8c47f7dec49e7
|
|
This fixes touch on the a11 when fastboot booting the image. We
are also adding event logging for ABS_MT_POSITION data which we
should have been logging before but for some reason we did not.
Change-Id: I1b38c31c716efdcbe48db4faa5d0cef97c91c58e
|
|
Change-Id: I39fe4de8919e59dd75e8cb535fa0648948035c26
|
|
Change-Id: I7eebc474c025eda534adb04d061795623ebecdda
|
|
need to define custom theme(include custom ttf files)
in device tree :
TW_CUSTOM_THEME := device/xxxx/yyyy/recovery/res
For example:
https://github.com/twrp/android_device_xiaomi_armani
Change-Id: I6bebdfbdd75c99bfe216a8c0789af63c6fe4b9de
|
|
This is mostly kang from AOSP resources.c for loading png files
into RAM, but for ease of compatibility we retained the older
gr_surface data types throughout and ensured that we retain
support for alpha blended png files.
Change-Id: Ieea552173d3bfe885460407be73088bbad75663f
|
|
-Remove dosfstools for arm64 until we can make it compile
-Fix TW_USE_TOOLBOX flag to work again
-Fix symlinking and handling of sh when using mksh
-Fix legacy properties to find futex_wake function
-Fix libcrecovery to not use bsd_signal anymore
-Fix rules for building with regards to libcrecovery
-Update toolbox_recovery rules to compile tools in lollipop
-Fix a few compile errors specific to arm64
Testers report that TWRP does not boot on Nexus 9 and we fail to
get a shell for adb shell. At least it compiles without errors.
Change-Id: I286be8628defb60cc527b8a548c0bdfcb0ebb574
|
|
We will have to update the zip handling later. Now at least TWRP
boots up to the GUI.
Change-Id: I4182896eb095cab52fb0f1c9c20b6605e35677b9
|
|
Implement some needed updates to libminui to make it compile for
healthd. Note that res_create_multi_display_surface is not fully
implemented so healthd may still have issues with displaying some
graphics. Will update later when we are able to test these changes.
Change-Id: Ic1095a998f5dfe7e36a08384c86da28e0524a03f
|
|
This reverts commit a27d02fab9d6feb793cdcd6146f2655658f36f2b.
Change-Id: I62d143044749f101cd70fef048057f896e46c208
|
|
Odds are this is horribly broken, but we are not able to work on
it just yet.
Change-Id: I8cd12a6dba7957b1ccc1275b8d72c24797856db0
|
|
* Keeps original font system in place
* Uses the same API as original font system:
- You can render only one line at a time
- You can only use one font and color for one gr_text* call
* Caches all rendered text, with a string cache limited to 400
entries, then it trucates to 250, which results in memory
usage hovering around 5-10MB
Change-Id: I36107b9dcd8d57bae4486fce8b8f64e49ef3d906
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
|
|
Enable TWRP to reside alongside other recoveries with the naming
convention: bootable/recovery(-flag). If TWRP resides at
bootable/recovery and a device does not specify RECOVERY_VARIANT, then
it will build like normal. If TWRP resides at bootable/recovery-twrp,
then its makefiles will only be parsed if a device specifies
'RECOVERY_VARIANT := twrp'. This prevents TWRP specific makefile
warnings/errors (notably, missing DEVICE_RESOLUTION) when another
recovery is being built.
Change-Id: I8f02fffcd79c309c7123b9428eedc69af02e126e
|
|
Change-Id: Idf41990258361e612635980700fd694b11c1c625
|
|
Usage:
TW_INPUT_BLACKLIST := accelerometer
TW_INPUT_BLACKLIST := "accelerometer\x0agyroscope"
This can be used to fix touch input on devices where an input
device is breaking touch processing in TWRP.
We are using new line chars to separate multiple devices and in
the make file you specify the new line character with \x0a which
is the hex code in ASCII for a new line.
The new line character might be a bit of a pain to use as a
delimeter, but it is highly unlikely that an OEM will ever name
an input device with a new line character in the name.
Change-Id: I255136b7a686909a23e649918c661843153c2853
|
|
If on the default settings the screen will only kick in to action
AFTER it has gone to sleep once and has been woken up again with a
key press, this will be needed to set to 'true' in the
BoardConfig.mk
The code was already there, Dees_Troy and I thought it would be
nice to make it a switch to control at compile time.
Change-Id: I5116a27afe9cba57122761c192ea3ee153d98162
|
|
Change-Id: I6efaeb1c508c06513ac9ace7aa72a2eefa0cb1bb
|
|
This prevents a crash in TWRP when trying to blank
the screen on devices that are using overlay graphics.
Change-Id: I155868616ffa1b211e97be97e4abe8b03dad7ca0
|
|
* Like in android - press power+volume down, screenshots are saved
in /sdcard/Pictures/Screenshots (if /sdcard is mounted) or /tmp
Change-Id: Iaefa15b11a1d5fdfac57d77388db1621f378a8d4
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
|
|
* use a whitelist for the input device to listen on, every other will be ignored
Change-Id: I1296a45ec3d5ca0bca2a9e2601b0710e2c030fde
|
|
Since target_has_overlay() was not ifdefed with MSM_BSP,
it would return true on some devices even if MSM_BSP was unset,
breaking LPM and some other minui functions.
Change-Id: Ic6b524fa0b5e36fc9ffe67d53e2bf33e9d4fd2d3
|
|
This is by no means comprehensive, but is quite a bit better already.
Change-Id: Ibc8654a5dfb0eec39cbd0b64bdb52bb4fbfe2f7e
|
|
Fix path in minuitwrp for includes
Change-Id: I9e9e5f67e8574cdcbc6f8873ceeb56eab71143ed
|
|
Change-Id: I9dfa7de40229f00412d63fc9c1eb3a809a6eb2e6
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
|
|
Change-Id: Ic1ef3f6a4e9c74efb07d8a0103543d124567f0d4
|
|
Change-Id: Ia75c34ab1a45b7c8802c902906198517aa3437d5
|
|
Change-Id: Ibcf89952ee1391350c715f1ec82cf0cdb9b0ca7d
|
|
* Some touchscreens have REL_* events
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
Change-Id: I332637ff58324895896ad09bf4ac08a2f127e49f
|
|
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
Change-Id: I66d6db7b3ed9cca50b469d125b36224332e06913
|
|
* The difference isn't as big as there are not many big non-transparent
bitmaps in TWRP, on install screen on flo it is about 5-10ms better.
Only place where the difference is noticable is keyboard, which is
pretty big non-transparent bitmap, where it speeds up the render
by ~40ms on flo.
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
Change-Id: I4c51ef957ae2a1829ada4eb566e9964f708efcf0
|
|
Change-Id: I15d723f73c0b0bb4a40645d1c3f4c1c616f36998
|
|
* This makes the rendering several times faster, because the giant
rectangle used as background no longer uses expensive blending
calculations, and there are also many other big rectangles which
don't need it (fileselector, ...).
* Results on hammerhead:
- WITHOUT the patch - scrolling in fileselector on install page:
I:render 67 ms, flip 6 ms, total 73 ms
I:render 82 ms, flip 6 ms, total 88 ms
I:render 81 ms, flip 6 ms, total 87 ms
I:render 80 ms, flip 5 ms, total 85 ms
- WITH the patch - scrolling in fileselector on install page:
I:render 32 ms, flip 6 ms, total 38 ms
I:render 16 ms, flip 6 ms, total 22 ms
I:render 16 ms, flip 7 ms, total 23 ms
I:render 18 ms, flip 3 ms, total 21 ms
I:render 18 ms, flip 2 ms, total 20 ms
* On flo, the results are even more noticable - 160ms -> 40ms
Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
Change-Id: I5685763ba21745d7cd93133adf5f0bcb4c9a581f
|
|
On n8013 at least, this event is sometimes/often sent on touch start which
causes touches to be randomly rejected and throws you back to the start screen.
Touch releases still work fine for me, since it sends ABS_MT_TRACKING_ID == -1
for that purpose.
Adds a flag TW_IGNORE_MAJOR_AXIS_0 to configure this behavior.
Change-Id: I14bb036a2c2d4ee676b642c3ab297c55bb6c2084
|
|
- libmincrypt renamed to libmincrypttwrp that is an static library
- libjpegtwrp does not exist
- libfs_mgrtwrp is for JB decryption methods
This fixes making full builds when TW_INCLUDE_CRYPTO_SAMSUNG := true and TW_INCLUDE_CRYPTO := true are set.
Somehow typing make recoveryimage doesnt push the mentioned issue.
Change-Id: I7cad5db4f51152a1a8209e619b188ca88d7c74d1
|
|
This reverts commit 70e1129612765b14e5aace0155d4683c91cde951.
No longer needed after http://review.teamw.in/#/c/655/
|
|
Change-Id: Id5ce607a181110118ebc647fc07d387a7a3dc660
|
|
|
|
|
|
Change-Id: I93391596eece6b08ecf2e54f443e9821573cb871
|
|
Change-Id: I3e2a67979c60a8e9f37f46f4fb0b0682c56ec95b
|
|
|
|
|
|
Improves license compatibility between GPL and Apache
Change-Id: I2b165aa575bb6213af6b07936f99610c113443f0
|
|
2 second predim code courtesy of bigbiff
Change-Id: I052ac422f78dc82c05f58c188587534b800b935a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pull in most TWRP sources
Stub out partition management code
Make it compile -- probably will not boot
Kind of a mess but have to start somewhere
|