summaryrefslogtreecommitdiffstats
path: root/minuitwrp/Android.mk (follow)
Commit message (Collapse)AuthorAgeFilesLines
* minuitwrp: Include some missing variables related to screen blankingVineeth Pillai2020-01-021-0/+18
| | | | | | 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.
* Switch between dependencies and modulesEthan Yonker2019-05-241-1/+5
| | | | | | | Use LOCAL_REQUIRED_MODULES for Pie and up and LOCAL_ADDITIONAL_DEPENDENCIES for Oreo and down. Change-Id: I5365e782f98f3bbf4bf246be22c8f573824b65ee
* Fix build in 5.1 treeDees Troy2019-04-031-1/+1
| | | | Change-Id: I15f888d58c01de00920dc5c56148d363f4dd79b8
* TW_ROTATION: add flag to handle hardware-rotated display panelsVladimir Oltean2019-03-181-2/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* libminuitwrp updates for Pixel 3 devicesEthan Yonker2019-01-161-1/+1
| | | | | | | | | 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
* minuitwrp: Fix detection of libdrm on Pielambdadroid2019-01-161-1/+1
| | | | | | | | 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
* Use libdrm_platform for minuitwrp in 8.x treesEthan Yonker2018-01-041-1/+5
| | | | Change-Id: I58d7aa61cdb5c954e0726644fdc25c58eed8e544
* Update to AOSP 8.0 baseEthan Yonker2017-09-081-0/+3
| | | | Change-Id: I29fe722b4eb9718765327902779046840a01433e
* ifdef overlay graphicsEthan Yonker2017-01-211-1/+1
| | | | Change-Id: If3173ddbfaccb95cc48636240ee3a918dac1e23f
* Add build flag for forcing single buffer modeEthan Yonker2016-08-191-2/+2
| | | | | | RECOVERY_GRAPHICS_FORCE_SINGLE_BUFFER := true Change-Id: Id5144ea772c3b7ae382b064c41c23acdd0decb84
* Black screen patch for some HiSilicon devices (FBIOPAN_DISPLAY)Muhammad Fahad Baig2016-06-091-0/+3
| | | | Change-Id: Ib114dcc7b48219142602a2fbc256e2a0258b26e0
* Flag to enable jpg supportGreg Wallace2016-02-031-2/+8
| | | | | | | Builder using a custom theme may have need for this. Add a flag to easily enable jpg support. Change-Id: Ica74f8cb1312d3193105f2201a5cf8073e2edc82
* Change some graphics build flagsEthan Yonker2016-02-031-16/+32
| | | | | | | | | | | | | | | | 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
* Fix minuitwrp include mistakeGreg Wallace2016-01-291-2/+2
| | | | Change-Id: Iebb5763277eec83fd6db4fdca8b7ecfd3c78dc6b
* ifdef and comment out libjpegEthan Yonker2016-01-271-2/+4
| | | | | | | | 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
* Update minuitwrp graphics in line with latest minuiEthan Yonker2016-01-271-7/+37
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* Update rules for libpixelfinger_twrpEthan Yonker2015-11-071-1/+1
| | | | Change-Id: I40131f330e902afab033e810761bf98c07bbd03d
* Remove support for non-TTF fontsEthan Yonker2015-10-151-43/+8
| | | | | | | | | | | 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
* Add support for RGBA_8888 pixel formatKra1o52015-10-141-0/+3
| | | | Change-Id: Ia15d49e51cad5bc8a3291975e1ff515a2b1c419c
* Merge up to AOSP marshmallow-releaseEthan Yonker2015-10-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In order to maintain compatibility with older trees, we now have minadbd.old and minui.old. I had to use a TARGET_GLOBAL_CFLAG to handle ifdef issues in minui/minui.d because healthd includes minui/minui.h and there was no other alternative to make minui.h compatible with older trees without having to modify healthd rules which is outside of TWRP. Note that the new minui does not currently have support for qcom overlay graphics. Support for this graphics mode will likely be added in a later patch set. If you are building in a 6.0 tree and have a device that needs qcom overlay graphics, be warned, as off mode charging may not work properly. A dead battery in this case could potentially brick your device if it is unable to charge as healthd handles charging duties. Update rules for building toolbox and add rules for making toybox Use permissive.sh in init.rc which will follow symlinks so we do not have to worry about what binary is supplying the setenforce functionality (toolbox, toybox, or busybox). Fix a few warnings in the main recovery binary source code. Fix a few includes that were missing that prevented compiling in 6.0 Change-Id: Ia67aa2107d260883da5e365475a19bea538e8b97
* Add TW_IGNORE_ABS_MT_TRACKING_IDEthan Yonker2015-08-261-0/+4
| | | | | | | | | | | | 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
* Add flag to disable double bufferingKra1o52015-06-291-0/+4
| | | | | | | Some devices don't support double buffering, so add the flag TW_DISABLE_DOUBLE_BUFFERING to disable it Change-Id: Ia9c233fa229ae9c221a6c6f219b216d1753052f4
* Add option to use new heap_id_mask instead of old heap_maskKra1o52015-04-231-0/+4
| | | | | | Use TW_NEW_ION_HEAP := true to use it Change-Id: I2ad105fa6d122b460ed4b5dc78563077b7904567
* Reduce themes to 5 and rely on scalingEthan Yonker2015-03-131-13/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Use /twres instead of /res for theme resourcesDees Troy2015-01-221-0/+1
| | | | | | | | | 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
* Add TW_IGNORE_MT_POSITION_0 touch flagEthan Yonker2014-12-291-0/+4
| | | | | | | | 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
* Add support for custom kernel headersKra1o52014-12-171-1/+5
| | | | Change-Id: I39fe4de8919e59dd75e8cb535fa0648948035c26
* Revert "Make libminuitwrp compile"Dees Troy2014-11-061-1/+1
| | | | | | This reverts commit a27d02fab9d6feb793cdcd6146f2655658f36f2b. Change-Id: I62d143044749f101cd70fef048057f896e46c208
* Make libminuitwrp compileEthan Yonker2014-11-061-1/+1
| | | | | | | Odds are this is horribly broken, but we are not able to work on it just yet. Change-Id: I8cd12a6dba7957b1ccc1275b8d72c24797856db0
* Add support for TrueType fontsVojtech Bocek2014-10-141-2/+10
| | | | | | | | | | | | | * 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>
* Build block TWRP with RECOVERY_VARIANTMatt Mower2014-09-031-2/+2
| | | | | | | | | | | | | 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
* Allow blacklisting input devices by build flagEthan Yonker2014-08-141-0/+4
| | | | | | | | | | | | | | | | | | | 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
* TW_SCREEN_BLANK_ON_BOOT will jolt the screen/touch driver.xNUTx2014-08-101-0/+3
| | | | | | | | | | | | 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
* Set font based on resolution if not set alreadyEthan Yonker2014-08-071-0/+14
| | | | Change-Id: I6efaeb1c508c06513ac9ace7aa72a2eefa0cb1bb
* Implement "take a screenshot" featureVojtech Bocek2014-07-091-1/+1
| | | | | | | | * 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>
* minuitwrp: use a whitelist for the input device instead of a hardcoded ignore listFlemmard2014-06-301-0/+5
| | | | | | * use a whitelist for the input device to listen on, every other will be ignored Change-Id: I1296a45ec3d5ca0bca2a9e2601b0710e2c030fde
* Support Qualcomm overlay graphics in recoveryEthan Yonker2014-04-011-1/+23
| | | | Change-Id: Ia75c34ab1a45b7c8802c902906198517aa3437d5
* Don't interpret ABS_MT_TOUCH_MAJOR == 0 as touch releaseIbrahim Awwal2014-01-041-0/+4
| | | | | | | | | | | | 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
* crypto: Fix crypto dependencies for ICS/Samsung methodsOliverG962013-12-191-3/+0
| | | | | | | | | | | - 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
* Remove libjpegtwrp and use CM provided libjpegDees_Troy2013-08-111-4/+5
|
* Tweak libsDees_Troy2013-04-051-3/+2
|
* Move all AOSP code out of recovery binaryDees_Troy2013-04-041-6/+12
| | | | | | Improves license compatibility between GPL and Apache Change-Id: I2b165aa575bb6213af6b07936f99610c113443f0
* Add build flag for custom graphicsDees_Troy2013-01-151-1/+7
|
* TWRP-ify AOSP codeDees_Troy2012-09-051-0/+54
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-02 13:40:41 +0200