Arcadia x86 updates 250305#4
Open
electrikjesus wants to merge 9 commits intoBlissRoms-x86:arcadia-x86from
Open
Arcadia x86 updates 250305#4electrikjesus wants to merge 9 commits intoBlissRoms-x86:arcadia-x86from
electrikjesus wants to merge 9 commits intoBlissRoms-x86:arcadia-x86from
Conversation
Allows overriding AMOTION_EVENT_BUTTON_SECONDARY with AMOTION_EVENT_BUTTON_BACK, using a property trigger. This will work with the ro.boot.force.right_mouse_as_back (true/false) property, or the androidboot.force.right_mouse_as_back (true/false) kernel cmdline option.
This requires a commit in frameworks/base to be removed: 5bc2c3d520e958493c9b4d5624457403267c9689 We can use ro.boot.force.win_as_home=1 or androidboot.force.win_as_home=1 to trigger the legacy behavior of Win hey being HOME action
The inputflinger can not handle multi USB mouse for multi display use case. An attempt was made to append the input-port-associations.xml configuration file to vendor/etc/ with official documentation, but can not handle multi USB mouse for multi display use case. The reason is that USB mouse can be multiple, and the associated diaplay ID can be multiple,but PointerController is singleton unique and only one viewport and one display id are saved in PointerController So in the case of multiple USB mouse, although the associated display id is saved in each USB mouse, the target display id and the target viewport are judged according to the viewport and display id saved in PointerController,so only one USB mouse can be mapped to one display other USB mouse can't be mapped to display. So need to remove the code that determines the display id based on the controller,and set an associated display id for each CursorInputMapper. Correct the viewport saved in PointerController based on the associated viewport before handling mouse events. Bug: None Test: atest inputflinger_tests Change-Id: I907d0e7675df02c1edb42060a3e8fe535feac137
…screen. Tips: Must setprop sys.mouse.presentation 1 Depend on commit:frameworks/base(60d9f87,"Multi-display:support mouse...") Source: TinkerBoard2-Android/frameworks-native@d3f542f Change-Id: I421eadd92ff82c2bc402858ee67fc10597d75ce0
Remember Y position and swap minX/maxX when switching. This gives us a more natural cursor movement when switching displays Requires: frameworks/native: multi-display:inputflinger service support mouse display on external screen
…h gesture Bring over changes from CursorInputMapper for mouse presentation so that we can also use it with the touchpad. Requires using 2-finger swipe gesture to switch to the next display once the pointer reaches the edge of the display.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.