Issue metadata
Sign in to add a comment
|
Broadcom Bluetooth not working in Jerry |
||||||||||||||||||||||||
Issue descriptionVersion: 52.0.2727.0/8297.0.0 (Official Build) dev-channel Jerry OS: Chrome What steps will reproduce the problem? (1)Recover OS via USB>> go to Uber tray>> or go to settings>> check for Bluetooth Expected: Bluetooth option should be seen on Uber tray or Chrome://settings Actual: Instead no Bluetooth option is seen This is a Non-Regression issue as Bluetooth option is not seen in M49:49.0.2623.112/7834.70.0 (Official Build) stable-channel as well Note: Bluetooth settings is seen on the same version using M52: 52.0.2727.0/8297.0.0 (Official Build) dev-channel Spring, Peachpit, Blaze, Daisy, Quawks Issue is not applicable to Linux and Windows
,
May 10 2016
@Geeta or @Songuk : Could any one please confirm this issue as we don't have jerry device here. Thnaks,
,
May 11 2016
@ sandeepkumar.sunkari Is the issue same as the issue 597130 .
,
May 11 2016
I recovery installed jerry to 8297.0.0 build and Bluetooth was present in the Uber tray and as well as in the settings page
,
May 11 2016
@songsuk: This issue is different than issue 597130 , and Bluetooth settings is not there in Uber tray and in the settings page as well at our end, and it was not there in older versions too.
,
May 11 2016
Thanks sandeepkumar.sunkari. Able to reproduce the issue on CrOS 8308.0.0/ Chrome 52.0.2727.0 - Jerry-DVT
,
May 11 2016
,
May 11 2016
This appears to be a Broadcom controller issue. Jerry MP devices have Marvell, but there was some question over Marvell or Broadcom originally. Some of the early devices were made with Broadcom. We borrowed a DVT, confirmed that it has Broadcom, and saw this same bug. Our MP device has Marvell as it should and works fine. Can everyone who is able to reproduce this bug please confirm that their device has a Broadcom chip? Try running `ethtool -i wlan0` and see if you driver is listed as "brcmfmac". If you're not in dev mode, open file:///var/log/messages and search for "mwifiex". If you see that, you have a Marvell chip. If there are no Marvell boards with this problem, we can probably just call this WontFix.
,
May 11 2016
I dug up the original bug; duplicating this one into it. Please label your Broadcom machines that this is expected.
,
May 11 2016
oops, that's http://crosbug.com/44003, not chromium. Since Monorail won't let us Duplicate into partner bugs (see https://bugs.chromium.org/p/monorail/issues/detail?id=1164), closing as WontFix.
,
May 11 2016
third time's a charm: http://crosbug.com/p/44003 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sandeepk...@techmahindra.com
, May 10 2016