New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 689656 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
█ aelias@chromium.org
amaralp@chromium.org
█ asimjour@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Bluetooth mouse on specific AndroidN devices fire no mouse events

Project Member Reported by mustaq@chromium.org, Feb 7 2017 
0. Attach a Bluetooth mouse to a Pixel C with Android N.
1. Go to any scrollable page, e.g. http://output.jsbin.com/xolehat
2. Click and drag with mouse.

Actual outcome:
The mouse acts like a touch, e.g. mouse-drag scrolls the page. Also fires touch events.

Expected:
On ToT this shouldn't happen as MotionEvents with TOOL_TYPE_MOUSE are routed as mouse event in ContentViewCore.onTouchEvent.

Oddly enough, wired mouse works just as expected.

Comment 1 by mustaq@chromium.org, Feb 7 2017 

The exact same thing happens on Pixel phone with Android N:
- Bluetooth mouse: fires touch events.
- wired mouse: WAI.

Comment 2 by mustaq@chromium.org, Feb 7 2017 

Looks like a Pixel-specific problem.

Tested two non-Pixel phones (MotoZ and Nexus5X): each behaves as expected for wired & bluetooth mice.

Comment 3 by mustaq@chromium.org, Feb 7 2017

Cc: asimjour@chromium.org
Summary: Bluetooth mouse on Pixel AndroidN fires no mouse events (was: Bluetooth mouse on Pixel C Android N fires no mouse events)
cc-ing Amir who knows about some driver-level touch-emulation hack for bluetooth mouse in CrOS. Any chance Pixel has done a similar thing?

Comment 4 by mustaq@chromium.org, Mar 1 2017

Blocking: -675339
This device-specific problem shouldn't block our general Android fix.

Comment 5 by mustaq@chromium.org, Jan 22 2018

Summary: Bluetooth mouse on specific AndroidN devices fire no mouse events (was: Bluetooth mouse on Pixel AndroidN fires no mouse events)
The problem also reproduces in Samsung Galaxy Note5 (Android O).
Project Member

Comment 6 by sheriffbot@chromium.org, Yesterday (34 hours ago)

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment