Bluetooth control panel doesn't acknowledge it's running

Bluetooth is currently not working on Raring-Nexus7 , waiting on Broadcom patch, Refer to:

 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400

I'll add this to the known issues page for the Nexus7

------------------------------------

No devices found when starting up bluetooth,

u@u-laptop:~$ sudo bluetoothd -n
bluetoothd[1888]: Bluetooth daemon 4.101
bluetoothd[1888]: Starting SDP server
bluetoothd[1888]: DIS cannot start: GATT is disabled
bluetoothd[1888]: Failed to init deviceinfo plugin
bluetoothd[1888]: Failed to init proximity plugin
bluetoothd[1888]: Failed to init time plugin
bluetoothd[1888]: Failed to init alert plugin
bluetoothd[1888]: Failed to init thermometer plugin
bluetoothd[1888]: Failed to init gatt_example plugin

u@u-laptop:~$ hcitool dev
Devices:

Note that the fix in linux-image-3.1.10-8-nexus7_3.1.10-8.17 works only with Ubuntu 12.10 and not with 13.04.

Assigning bug to Jani, since we are sitting on kernel updates

Seems to work for me now.

Using the latest (just upgraded this morning) (3.1.10-9-nexus7 #25), I open the bluetooth settings window, change bluetooth to "on" and it still says "Bluetooth is disabled". Nexus7 hardware with 3G.

Bluetooth works fine for me now on latest update. Just tried out a bluetooth mouse.

did you reboot to get the new kernel active ? also please check if brcm-patchram-plus is installed ... (it should get pulled in by the latest ubuntu-defaults-nexus7 package)

Just now booted my nexus7, did "apt-get update; apt-get upgrade", then rebooted again. Still, when I open the bluetooth control panel and turn on bluetooth, just below it still says "Bluetooth is disabled". How do I verify the "brcm-patchram-plus"? I have ubuntu-defaults-nexus7 ver. 0.45 according to "dpkg -l", and here's "uname -a" output:
Linux rajnexus7 3.1.10-9-nexus7 #25-Ubuntu SMP PREEMPT Thu Jan 31 12:23:44 UTC 2013 armv7l armv7l armv7l GNU/Linux

oh, make sure you upgrade then, ubuntu-defaults-nexus7 0.45 is quite old, the dependency was added in 0.50 (and we are currently at 0.52)

also in a development release you should always apt-get "dist-upgrade" instead of just "upgrade", the former cares for package removals and additions while the latter will only upgrade whats possible without adding or removing packages.

Yes, that works. dist-upgrade was needed, followed by a reboot. Now it works fine! Thanks!