summaryrefslogtreecommitdiffstats
path: root/minuitwrp/events.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Update minuitwrp graphics in line with latest minuiEthan Yonker2016-01-271-792/+0
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* Merge up to AOSP marshmallow-releaseEthan Yonker2015-10-091-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/+10
| | | | | | | | | | | | 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
* Ingore touch events for 0,0Ethan Yonker2015-03-191-0/+6
| | | | Change-Id: I63eb29d7a39956d92cb5da81c5cb4405930d43ae
* gui: avoid high CPU usage while waiting for inputthat2015-02-091-2/+2
| | | | | | | | | - 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
* gui: fix lag (and event logging)that2015-02-011-1/+2
| | | | | | | | | | | | | | - 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
* Move input handling into the main threadEthan Yonker2015-01-301-26/+22
| | | | | | | | | 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
* Add TW_IGNORE_MT_POSITION_0 touch flagEthan Yonker2014-12-291-0/+12
| | | | | | | | 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
* Fix derpEthan Yonker2014-08-141-1/+1
| | | | Change-Id: Idf41990258361e612635980700fd694b11c1c625
* Allow blacklisting input devices by build flagEthan Yonker2014-08-141-1/+16
| | | | | | | | | | | | | | | | | | | 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
* minuitwrp: use a whitelist for the input device instead of a hardcoded ignore listFlemmard2014-06-301-0/+7
| | | | | | * use a whitelist for the input device to listen on, every other will be ignored Change-Id: I1296a45ec3d5ca0bca2a9e2601b0710e2c030fde
* Whitespace and minor code cleanupMatt Mower2014-06-041-3/+3
| | | | | | This is by no means comprehensive, but is quite a bit better already. Change-Id: Ibc8654a5dfb0eec39cbd0b64bdb52bb4fbfe2f7e
* Add support for actions triggered by key combinationVojtech Bocek2014-04-161-1/+8
| | | | | Change-Id: I9dfa7de40229f00412d63fc9c1eb3a809a6eb2e6 Signed-off-by: Vojtech Bocek <vbocek@gmail.com>
* Support Qualcomm overlay graphics in recoveryEthan Yonker2014-04-011-1/+1
| | | | Change-Id: Ia75c34ab1a45b7c8802c902906198517aa3437d5
* Look also for buttons when checking if input device is mouseVojtech Bocek2014-02-201-3/+12
| | | | | | | | * Some touchscreens have REL_* events Signed-off-by: Vojtech Bocek <vbocek@gmail.com> Change-Id: I332637ff58324895896ad09bf4ac08a2f127e49f
* Implement mouse cursorVojtech Bocek2014-02-071-8/+70
| | | | | | Signed-off-by: Vojtech Bocek <vbocek@gmail.com> Change-Id: I66d6db7b3ed9cca50b469d125b36224332e06913
* Add haptic feedbackSamer Diab (S.a.M.e.R_d)2014-02-061-0/+2
| | | | Change-Id: I15d723f73c0b0bb4a40645d1c3f4c1c616f36998
* Don't interpret ABS_MT_TOUCH_MAJOR == 0 as touch releaseIbrahim Awwal2014-01-041-0/+2
| | | | | | | | | | | | 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
* Revert "Fix touch not working due to gr_fb_width returning 0 in some cases"Dees_Troy2013-08-241-15/+16
| | | | | This reverts commit 70e1129612765b14e5aace0155d4683c91cde951. No longer needed after http://review.teamw.in/#/c/655/
* Fix touch not working due to gr_fb_width returning 0 in some casesDees_Troy2013-08-111-16/+15
| | | | Change-Id: Id5ce607a181110118ebc647fc07d387a7a3dc660
* Remove unneeded touch code changesDees_Troy2013-07-081-15/+0
|
* Fix touch on some Samsung devicesDees_Troy2013-07-011-11/+41
| | | | Change-Id: I3e2a67979c60a8e9f37f46f4fb0b0682c56ec95b
* Allow for more input devicesDees_Troy2013-05-031-1/+1
|
* Move all AOSP code out of recovery binaryDees_Troy2013-04-041-25/+25
| | | | | | Improves license compatibility between GPL and Apache Change-Id: I2b165aa575bb6213af6b07936f99610c113443f0
* Ignore bma150 in event handlerDees_Troy2012-12-111-1/+1
|
* Fix compiler warningsDees_Troy2012-09-281-0/+6
|
* TWRP-ify AOSP codeDees_Troy2012-09-051-0/+640
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-11-13 08:09:55 +0100