Issue metadata
Sign in to add a comment
|
ARC++ BTLE broken for edgar. |
||||||||||||||||||||||
Issue descriptionMoving from https://b.corp.google.com/issues/36095748 In short, Bluetooth LE is broken for Android apps running under ARC++. Full service discovery does not report back complete list of services, as verified with nRF Connect app. The BLE stack seems to be omitting UUID 0x1800, Generic Access, from services list. Apps that try to communicate with BLE devices flat out don't work as a result. UI language: en-US Version: 58.0.3029.6 dev Product Specific Data (whitelisted): CHROME VERSION: 58.0.3029.6 dev CHROMEOS_AUSERVER: <URL: 1> CHROMEOS_RELEASE_BOARD: edgar-signed-mp-v2keys CHROMEOS_RELEASE_DESCRIPTION: 9334.2.0 (Official Build) dev-channel edgar CHROMEOS_RELEASE_TRACK: dev-channel CHROMEOS_RELEASE_VERSION: 9334.2.0 ENTERPRISE_ENROLLED: Not managed expi: 3300110 3300132 3312841 3313324 3313326 3313362 3313401 hardware_class: EDGAR D25-A4C-S8I-A7K lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 006: ID 04f2:b567 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub routes: default via <IPv4: 10> dev wlan0 metric 1 <IPv4: 30>/24 dev wlan0 proto kernel scope link src <IPv4: 1>0 <IPv4: 11>/30 dev br0 proto kernel scope link src <IPv4: 13> Browser: Chrome 58.0.3029.6
,
Mar 11 2017
Re #1 , this seems to be regression because the fitbit app was working on minnie on M-57 9202.0.0 build and i updated it to M-58 9334.2.0 build, the app was not working.
,
Mar 11 2017
,
Mar 16 2017
Howdy, I'm the one who made the posts to the chromium-os-dev list and also submitted the feedback that this bug was generated from. Just to be clear, this only seems to affect apps running in ARC++. If I take the BLE Sphero, pair it with the laptop, and then run Sphero's SPRK Lightning Lab app for Chrome (https://chrome.google.com/webstore/detail/sprk-lightning-lab/hfiocchbmngcelgfdcfbepgoipapddlh?hl=en), that works just fine. This makes me think the problem is not with the core OS bluetooth subsystem, but rather with the ARC++ Bluetooth Bridge. However, I am not familiar with the code, so you all would know better than I. Just thought I'd clarify. Thanks.
,
Mar 27 2017
FYI, I recently tested a Fitbit Blaze in both BLE Scanner and nRF Connect, and unlike the Sphero, neither app showed any advertised services for the device. So something is going on other than just the Generic Access service coming up missing. Also, perhaps this bug should be re-titled?
,
Apr 3 2017
According to b/36072163, Fitbit is working correctly in Caroline 9334.28 Pramod, can you help looking at this with edgar?
,
Apr 3 2017
Look like ARC++ for edgar is not actually launched. Mark this as P3 for now
,
Apr 3 2017
As, i check on 9334.28.0 build, ARC++ is not enabled for edgar.
,
Apr 3 2017
Yes it's true that ARC++ is not enabled for Edgar by default. I forced its launch by using the --arc-availability flag. Other than BLE, ARC++ seems to work fine on this model. The policies for filing bugs against models that aren't yet supported for ARC++ (but which are on the roadmap) are not clear to me. Since Edgar will eventually be a supported model, is there any reason to not start hunting down this bug before that happens, so that when ARC++ is finally enabled, the bug does not exist for everyone who is using it?
,
Apr 3 2017
> Is there any reason to not start hunting down this bug before that happens, so that when ARC++ is finally enabled, the bug does not exist for everyone who is using it? Android N ARC++ code is branched from M for a while and the code is quite different now. There are test team that test ARC++ M branch for supported mode to make sure that it work. But for feature development, we want to add a new code in N or future release branch only to avoid duplication work. I will mark this as WontFix as it is bug unreleased platform.
,
Apr 3 2017
I see, thanks; that makes sense. So it sounds like we need to wait for N to appear on Edgar dev or canary branch and then re-test to see if issue is gone after that. Any idea when N might show up on remaining models that still don't have it?
,
Apr 3 2017
> Any idea when N might show up on remaining models that still don't have it? Sorry, no idea about that. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pbath...@chromium.org
, Mar 11 2017