[CD Cursor] Fix invalid displayId set when topology is not yet set
The issue here was that both currentCursor and topology has invalid displayId, but input devices have been set.. Which caused [Cursor|Touchpad]InputMapper to not get notified on DISPLAY_INFO reconfiguration, and rejecting all motion events. Bug: 399893492 Bug: 396568321 Test: Manually verified with attached cursor on reboot Flag: com.android.input.flags.connected_displays_associated_display_cursor_bugfix Change-Id: I016c646acdf6bd7b0fdb2840c852b825ccad9e1b
Loading
Please register or sign in to comment