Bluetooth not working on Acer W500 tablet

[Stuart Metcalfe]

On Ubuntu Natty, the bluetooth menu appears in the panel and reports "Bluetooth: On" but the icon is greyed-out and when I open the preferences dialog, I am only given the option to "Turn on bluetooth" with a large button. Clicking the button doesn't do anything.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Mon Jun 27 14:32:37 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterestingModules: sco bnep l2cap btusb bluetooth
MachineType: acer ICONIA Tab W500
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=3452344d-9b10-42f2-8c88-21e56287eb35 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2011
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: WT1
dmi.board.vendor: acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd04/14/2011:svnacer:pnICONIATabW500:pvrV1.08:rvnacer:rnWT1:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: ICONIA Tab W500
dmi.product.version: V1.08
dmi.sys.vendor: acer
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
  DOWN
  RX bytes:0 acl:0 sco:0 events:0 errors:0
  TX bytes:3 acl:0 sco:0 commands:1 errors:0

[goniomdq (jose-goni)]

Same problem here on a Toshiba Satellite Pro S200.
Restarting the bluetooth service fixes it (sudo service bluetooth restart)
Ubuntu Natty fresh install. BT was working in 10.10
$ lsusb
Bus 006 Device 003: ID 0930:0508 Toshiba Corp. Integrated Bluetooth HCI
$ uname -r
2.6.38-8-generic

[Stuart Metcalfe (stuartmetcalfe)]

Restarting the service doesn't solve the problem for me. I should also note that a separate USB bluetooth dongle I have works as expected when plugged in.

[madbiologist (me-again)]

@ goniomdq - As you have different hardware to the original bug reporter, you should file a new bug.

@ Stuart Metcalfe - Does this problem still occur on Ubuntu 12.04 "Precise Pangolin"?

[Stuart Metcalfe (stuartmetcalfe)]

@madbiologist: Sorry, I sold the tablet so can't confirm 12.04 behaviour

[Tuomas Jormola (tjormola)]

Nope, not fixed in 12.04. I'm trying to attach new apport files..

[Tuomas Jormola (tjormola)]

ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
InterestingModules: btusb bnep rfcomm bluetooth
MachineType: acer ICONIA Tab W500
NonfreeKernelModules: fglrx
Package: bluez 4.98-2ubuntu7
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
 LC_CTYPE=fi_FI.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=/dev/mapper/vg--sys-lv--root ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Tags: precise
Uname: Linux 3.2.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/08/2011
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: WT1
dmi.board.vendor: acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.13:bd07/08/2011:svnacer:pnICONIATabW500:pvrV1.13:rvnacer:rnWT1:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: ICONIA Tab W500
dmi.product.version: V1.13
dmi.sys.vendor: acer
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
  DOWN
  RX bytes:0 acl:0 sco:0 events:0 errors:0
  TX bytes:6 acl:0 sco:0 commands:2 errors:0

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Tuomas Jormola (tjormola)]

apport information

[Zhang Weiwu (zhangweiwu)]

I can confirm it still doesn't work for me on 12.10 (64-bit). The behavior:

bluetooth icon is shown, with a right-click menu option to turn it off, which should mean it is on.

To add a bluetooth device, clicking "Bluetooth setting" on the notification icon right-click menu results nothing - no new window.

Go to gnome control panel and access bluetooth setting from there. The window shows bluetooth is on. Click "+" to add a new device, it scans for half an hour not being able to find any device (another computer next to it can find 3+ devices). If turn local computer visible, other computers cannot see it.

restarting "bluetooth" service does not help (no change in behaviour).

[Scott (skreuser)]

I have it working in 12.04 with an external adapter. I have a USB hub. I bought a Logitech Wireless keyboard, it included a USB bluetooth adapter. I plugged it in to the USB hub and the keyboard works, I had a mouse working as well. So it seems the bluetooth in the A500 does not work but a workaround is availabke if you use a USB-bluetooth adapter.

[Scott (skreuser)]

P.S. I wanted to add you do not need the USB HUB. Just plugging in the adapter to any of the two available USB ports works as well.

[Mathieu Trudel-Lapierre (cyphermox)]

Looks like bluez has issues talking to the hci0 device that is detected.

Could someone having this bug please report it upstream? See http://www.bluez.org/development/lists/ ; it's a matter of sending an email to the bluetooth mailing list to let the developers know about the issue, and including at the very least /var/log/syslog from a clean boot, and after an attempt at enabling the device and/or scanning for neighboring bluetooth devices.

[Audun Gangsto (feitingen)]

Wrong driver for some, if lsusb -v -d 0cf3:3005 reports something, this will fix it:
http://<email address hidden>/msg19076.html
For me this patch is not working because I have a different bluetooth chip.
Can you guys post lsusb so we can confirm which chip you have?

[Jonathan Ferreira (j0n4tfds)]

I have the same chip that the patch fixes, I made an test trying connect on my cellphone and it's worked so far.
The response to command "lsusb -v -d 0cf3:3005" is a bit long, so I put in the attachment.

[Launchpad Janitor (janitor)]

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

[Ｖ字龍(Vdragon) (vdragon)]

AR3011 Bluetooth chip(set) should be supported after Linux kernel 3.4 and later(and supported via installing linux-firmware package), reopen this bug if you find problem persists.