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

Issue 631853 link

Starred by 4 users
Status: WontFix
Owner:
khorimoto@chromium.org
Closed: Jan 2017
Cc:
r...@chromium.org
█ tkonch...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature

Blocking:
issue 607358



Sign in to add a comment

No support for BLE uWeave protocol server on ChromeOS

Project Member Reported by jingxuy@google.com, Jul 27 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36

Steps to reproduce the problem:
1. The server doesn't exist yet.

What is the expected behavior?

What went wrong?
Currently there is no BLE server on ChromeOS that follows the uWeave protocol.

Did this work before? N/A 

Chrome version: 51.0.2704.84  Channel: n/a
OS Version: 
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by tkonch...@chromium.org, Jul 27 2016

Cc: tkonch...@chromium.org
Labels: M-54
Status: Untriaged (was: Unconfirmed)
Confirming the issue as this seems to be a feature request
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 27 2016

Labels: Hotlist-Google

Comment 3 by ranjitkan@chromium.org, Aug 12 2016

Components: Internals>Network

Comment 4 by mmenke@chromium.org, Aug 19 2016

Components: -Internals>Network OS>Systems>Bluetooth
I...guess this is a bluetooth thing?

Comment 5 by kathrelk...@chromium.org, Aug 19 2016

Cc: r...@chromium.org
Components: -OS>Systems>Bluetooth IO>Bluetooth

Comment 6 by r...@chromium.org, Aug 19 2016

Owner: khorimoto@chromium.org
Status: Assigned (was: Untriaged)

Comment 7 by st...@chromium.org, Aug 24 2016

Cc: st...@chromium.org

Comment 8 by st...@chromium.org, Aug 24 2016

Cc: -r...@chromium.org

Comment 9 by scheib@chromium.org, Oct 20 2016

Blocking: 607358

Comment 10 by khorimoto@chromium.org, Jan 9 2017

Status: WontFix (was: Assigned)
Not necessary as the CrOS tether code will use the BLE central role.

Comment 11 by st...@chromium.org, Mar 3 2017

Cc: r...@chromium.org

Comment 12 by st...@chromium.org, Mar 3 2017

Cc: -st...@chromium.org
►

Sign in to add a comment