Bluetooth is not working

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Activate Bluetooth
2. Search
3. Associate 

What is the expected output? What do you see instead?
long wait for associate

What version of the boot.img and system.img are you using?
boot.img v1.1
systemv2.img

Can you provide logcat output during that error?

Please provide any additional information below.
work fine with official LG roms

Original issue reported on code.google.com by cioeri@gmail.com on 27 Jul 2010 at 8:32

[GoogleCodeExporter]

I also trying hard for bluetooth, and for the moment bluetooth is unable to 
activate.

I managed to have some progress ins console mode : in fact BTLD and hcid are 
not started after boot.

unhappilly, if i start manually BTLD and after hcid, the android system seems 
not to be aware of this, I dont know haow to restart properly a service in 
android from console.

but at leat, when i start manually BTLD, it doesnt crashes as it does at boot 
time and the HCID can connect ton the bluetooth adapter.

Original comment by julien.b...@gmail.com on 30 Jul 2010 at 8:25

[GoogleCodeExporter]

We certainly need a volunteer to fix bluetooth, because I do not own any 
devices.
First step would be to make it work (=recognize other devices, maybe pairing 
and so on) from shell by using the deamons from the korean-v10t rom.

Original comment by polyth...@gmail.com on 21 Aug 2010 at 7:18

• Changed state: NeedVolunteer

[GoogleCodeExporter]

Issue 47 has been merged into this issue.

Original comment by polyth...@gmail.com on 21 Aug 2010 at 7:38

[GoogleCodeExporter]

I have some bluetooth devices.
What to do?

Original comment by andre%ma...@gtempaccount.com on 23 Aug 2010 at 9:38

[GoogleCodeExporter]

I have some prior experience with bluetooth command line utilities in linux, 
but I can't seem to get this running (system 4.1).

This command should list all services on all discoverable bluetooth devices in 
range: sdptool browse

This command should list all local bluetooth hardware addresses: hcitool dev

This command should be pretty self explanatory: l2ping $bdaddr

I cannot get any of the above to work. It's almost as if a driver or firmware 
wasn't loaded. Still, I do get this in the kernel log:

<5>[34269.451511] init: starting 'btld'
<7>[34270.048350] +++bluetooth_toggle_radio+++(1)(1)(0)(2)
<7>[34270.048856] bluetooth_power(1)
<7>[34270.049936] on_off: 1
<7>[34270.051588] *****wait for regulator turned-on, 150ms*****
<7>[34270.445676] +++bluetooth_toggle_radio+++(1)(1)(0)(2)
<7>[34270.446190] RFKILL_STATE_UNBLOCKED
<7>[34270.446651] hsuart_power 1<6>init: event { 'change', 
'/devices/platform/bt_power.0/rfkill/rfkill0', 'rfkill', '', -1, -1 }
<5>[34271.959230] init: starting 'hcid'
<6>[34271.963093] init: Created socket '/dev/socket/dbus_bluetooth' with mode 
'660', user '1002', group '1002'
<6>[34271.964670] init: Created socket '/dev/socket/bluetooth' with mode '660', 
user '1002', group '1002'

I'll have to compare files between 1.5 and 2.1 to get any further...

Original comment by h.n.erik...@gmail.com on 23 Aug 2010 at 2:04

[GoogleCodeExporter]

Are there any news?
For me it's necassary that bluetooth is working, because I need it for my 
handsfree in my car at work. So I cannot upgrade to 2.1

Original comment by andre%ma...@gtempaccount.com on 15 Sep 2010 at 9:08

[GoogleCodeExporter]

Issue 92 has been merged into this issue.

Original comment by polyth...@gmail.com on 17 Sep 2010 at 8:40

[GoogleCodeExporter]

I'm not that familiar with bluetooth, and I do not own any bluetooth devices. I 
can not help with the bluetooth issues directly, but if anyone is at it, please 
post to the mailinglist.
We can also help there with problems like starting services during boot or 
enableing more debugging output in the kernel and so on.

Original comment by polyth...@gmail.com on 17 Sep 2010 at 8:45

• Changed title: Bluetooth is not working

[GoogleCodeExporter]

Original comment by polyth...@gmail.com on 20 Sep 2010 at 8:21

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Can't build from source to gain hcid & hcitools in image.
There is no this files in 4.4\1.7 too.
Any ideas?

Original comment by Fedo...@gmail.com on 23 Sep 2010 at 9:53

[GoogleCodeExporter]

This could be a usefull link. Hopefully

http://pdk.android.com/online-pdk/guide/bluetooth.html

Original comment by andre%ma...@gtempaccount.com on 23 Sep 2010 at 10:54

[GoogleCodeExporter]

there is no suitable info there :(

Original comment by Fedo...@gmail.com on 23 Sep 2010 at 12:39

[GoogleCodeExporter]

If you want to build the bluetooth tools, edit 
vendor/openetna/openetna/BoardConfig.mk
and uncomment
BOARD_HAVE_BLUETOOTH := true.
There is a comment about audio problems, but I'm not sure if that's really the 
case. So feel free to try out.

Original comment by polyth...@gmail.com on 24 Sep 2010 at 8:32

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

thanks.
i have to begin to understand structure of project

Original comment by Fedo...@gmail.com on 24 Sep 2010 at 10:26

[GoogleCodeExporter]

i tried to accivated bluetooth in setting(wreless) and when i push the button 
on the screen notthing happens.. with the application blutooth file transfer i 
tried to trun the bluetooth on but the nitification for granting access to 
turning on blutooth is comming one after another and blutooth dont enable
(sorry because of my poor english)

Original comment by ali.fara...@gmail.com on 24 Sep 2010 at 1:32

[GoogleCodeExporter]

Get the bluetooth to work from shell.
To reproduce:
1. edit vendor/openetna/openetna/BoardConfig.mk and uncomment 
BOARD_HAVE_BLUETOOTH := true.
2. adb shell
3. echo 1 > /sys/class/rfkill/rfkill0/state
##hciattach /dev/ttyHS0 <there should be original firmware, at this time-any> 
115200
4. hciattach /dev/ttyHS0 any 115200
5. hciconfig hci0 up

scan & connection works fine, but only from shell, bluetoothd want to start.
~ # /system/bin/bluetoothd -n -d
bluetoothd[1532]: Bluetooth daemon 4.47
bluetoothd[1532]: Enabling debug information
bluetoothd[1532]: parsing main.conf
bluetoothd[1532]: discovto=120
bluetoothd[1532]: pairto=0
bluetoothd[1532]: pageto=8192
bluetoothd[1532]: name=%m
bluetoothd[1532]: class=0x40020C
bluetoothd[1532]: discov_interval=0
bluetoothd[1532]: deviceid=android:generic:1.5
bluetoothd[1532]: Starting SDP server
bluetoothd[1532]: opening L2CAP socket: Operation not permitted
bluetoothd[1532]: Server initialization failed
bluetoothd[1532]: Loading builtin plugins
bluetoothd[1532]: Loading plugins /system/lib/bluez-plugin
bluetoothd[1532]: Loading input plugin
bluetoothd[1532]: Loading audio plugin
bluetoothd[1532]: Unix socket created: 4
bluetoothd[1532]: audio.conf: Key file does not have key 'AutoConnect'
bluetoothd[1532]: audio.conf: Key file does not have group 'Headset'
bluetoothd[1532]: input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[1532]: adapter_ops_setup failed

Original comment by Fedo...@gmail.com on 27 Sep 2010 at 11:45

[GoogleCodeExporter]

no errors with audio. think it can be enabled in main branch.
But bluetoothd won't to start. No info in the internet.

Original comment by Fedo...@gmail.com on 27 Sep 2010 at 4:35

[GoogleCodeExporter]

@ FedosIS

Is it possible to share your build with us?

That would be great!
THX

Original comment by andre%ma...@gtempaccount.com on 28 Sep 2010 at 2:29

[GoogleCodeExporter]

all what U need is described in my post before.
foolowing that steps you get working hcitools, hciconfig & other shell tools, 
but bluetoothd still won't to work, so there is no bluetooth from phone 
interface

Original comment by Fedo...@gmail.com on 28 Sep 2010 at 8:07

[GoogleCodeExporter]

any fix on froyo?

Original comment by croxz3...@gmail.com on 1 Oct 2010 at 5:38

[GoogleCodeExporter]

no, cannot enable bluetooth in systemV6.0rc2 :(

Original comment by andreabe...@gmail.com on 1 Oct 2010 at 5:47

[GoogleCodeExporter]

not either in boot V2.1.1 and System V6-rc5
bluetooth doesnot became on:(

Original comment by ali.fara...@gmail.com on 4 Oct 2010 at 2:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Issue 180 has been merged into this issue.

Original comment by Tetsuo6...@gmail.com on 5 Oct 2010 at 9:13

[GoogleCodeExporter]

need help.
in new source cyanogenmod, after disabling ANDROID_PARANOID_NETWORK
and post 18 i got this
# bluetoothd -nd
Enabling debug information
parsing main.conf
discovto=120
pairto=0
pageto=8192
name=%m
class=0x40020C
discov_interval=0
deviceid=android:generic:1.5
default_link_policy=7
Starting SDP server
Unable to get the control socket for 'bluetooth'
Server initialization failed
Loading builtin plugins
Loading hciops plugin
Loading plugins /system/lib/bluez-plugin
Loading input plugin
Loading audio plugin
Unix socket created: 12
audio.conf: Key file does not have key 'AutoConnect'
audio.conf: Key file does not have group 'Headset'
input.conf: Key file does not have key 'IdleTimeout'
HCI dev 0 registered
child 1807 forked
btd_adapter_ref(0x105b8): ref=1
HCI dev 0 up
Starting security manager 0
Stopping Inquiry at adapter startup
a2dp_server_probe: path /org/bluez/1806/hci0

btd_adapter_ref(0x105b8): ref=2
audio_adapter_ref(0x10ac0): ref=1
audio.conf: Key file does not have key 'SBCSinks'
audio.conf: Key file does not have key 'MPEG12Sinks'
SEP 0xffb0 registered: type:0 codec:0 seid:1
Adding record with handle 0x10000
Record pattern UUID 00000019-0000-1000-8000-00805f9
Record pattern UUID 00000100-0000-1000-8000-00805f9
Record pattern UUID 00001002-0000-1000-8000-00805f9
Record pattern UUID 0000110a-0000-1000-8000-00805f9
Record pattern UUID 0000110d-0000-1000-8000-00805f9
avrcp_server_probe: path /org/bluez/1806/hci0

audio_adapter_ref(0x10ac0): ref=2
Adding record with handle 0x10001
Record pattern UUID 00000017-0000-1000-8000-00805f9
Record pattern UUID 00000100-0000-1000-8000-00805f9
Record pattern UUID 00001002-0000-1000-8000-00805f9
Record pattern UUID 0000110c-0000-1000-8000-00805f9
Record pattern UUID 0000110e-0000-1000-8000-00805f9
btd_adapter_ref(0x105b8): ref=3
Changing service classes to 0x08020c
Adapter /org/bluez/1806/hci0 has been enabled
Failed to open RFKILL control device
Entering main loop
Inquiry Failed with status 0x12
child 1807 exited

Need help.

Original comment by Fedo...@gmail.com on 5 Oct 2010 at 10:05

[GoogleCodeExporter]

Failed to open RFKILL control device
this is main trouble. google says nothing. adapter have been enabled.

Original comment by Fedo...@gmail.com on 5 Oct 2010 at 10:29

[GoogleCodeExporter]

try
strace bluetoothd -nd
This should give you some hint what is going on. Probably there is an 
permission problem with the rfkill device it wants to open.

Original comment by polyth...@gmail.com on 6 Oct 2010 at 6:45

[GoogleCodeExporter]

I don't think they are problematic:
http://forum.xda-developers.com/showthread.php?p=7730746

here the same log but bluetoothd works ok...
I've read rfkill API has changed in linux 2.6.31, and probably android is using 
the new api?

Original comment by saxand...@gmail.com on 9 Oct 2010 at 1:57

[GoogleCodeExporter]

@polytheus: my htc also wont run bluetoothd. However I compared startup traces 
using the very cool "droid explorer" and found my lg eve had this

ERROR/bluedroid(130): bt_enable: Timeout waiting for HCI device to come up
DEBUG/BluetoothService(130): Bluetooth state 11 -> 10

but my magic found and initialised the hci modem.

So if you start playing with hcitool, and googling on the error, its a very 
well documented error, although I havent seen a fix for it yet. It appears to 
be a firmware or modem driver issue, but that's as far as I got.

Original comment by philgillam@gmail.com on 15 Oct 2010 at 7:30

[GoogleCodeExporter]

Wow! Just now can to get BT working:
- turn from GUI
- pair from GUI
- send & receive files using Bluetooth File Transfer from Market.
so, U need the following steps to reproduce:
1. in source code edit vendor/openetna/openetna/BoardConfig.mk and uncomment 
BOARD_HAVE_BLUETOOTH := true. 
2. build from source
3. adb shell so next in the shell
4. hciattach /dev/ttyHS0 any 115200
5. bluetoothd
6. now U can try to enable bluetooth & search for devices
7. install BT File transfer to got OBEX push/pull functionality!

Original comment by Fedo...@gmail.com on 15 Oct 2010 at 9:13

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Correction for previous post.
Step to get BT working fine
1. Get the source code
2. change ANDROID_PARANOID_NETWORK in 
android-2.2/kernel/arch/arm/configs/openetna to n
3. in android-2.2/out/target/product/eve/root/init.rc r U need to change from 
original to this(so remove all services from dbus to installd - they are for BT)
service dbus /system/bin/dbus-daemon --system --nofork
    socket dbus stream 660 bluetooth bluetooth
    user root
    group root net_bt_admin

service installd /system/bin/installd
    socket installd stream 600 system system
 dbus-daemon should be run as root(may be it can run as bluetooth, but in my variant it's as described before)
4. build from source
5. flash to the phone
6. after boot do adb shell
7 echo 0 > /sys/class/rfkill/rfkill0/state (not needed at most cases)
8 hciattach /dev/ttyHS0 any 115200
9. bluetoothd
10. now U can try to enable bluetooth & search for devices
11. install BT File transfer to got OBEX push/pull functionality!
12. after reboot U need to repeat 7-8 step/

I know, that it's not to good, but U can get full BT functionality.
Root of the problem found, so i have to experimen with it.
Need help from volonteurs

Original comment by Fedo...@gmail.com on 15 Oct 2010 at 1:24

[GoogleCodeExporter]

to reduce typing i wrote script
#!/system/bin/sh
echo 0 > /sys/class/rfkill/rfkill0/state
/system/bin/hciattach /dev/ttyHS0 any 115200
/system/bin/bluetoothd
 & place it to /system/bin & chmod a+x it
so, after reboot from terminal i can just type BT or set shortcut from desktop

Original comment by Fedo...@gmail.com on 15 Oct 2010 at 1:43

[GoogleCodeExporter]

fix #1. dbus-daemon should be run as bluetooth, when it is run as root - wifi 
is broken

Original comment by Fedo...@gmail.com on 15 Oct 2010 at 2:31

[GoogleCodeExporter]

Great work FedosIS! You should clean it up and include steps 7-8-9 in 
init.rc... Then you can ask permission to commit to git or just attach the 
complete patch here :)

Original comment by saxand...@gmail.com on 15 Oct 2010 at 3:16

[GoogleCodeExporter]

but this steps in init.rc have not to work... i try this, but i will continue 
my investigations tomorrow. In my lg620 BT is already work)
I need this function & it will have to be working. It will be committed, soon 
later/
Also, i don't know how to ask permission to commit.

Original comment by Fedo...@gmail.com on 15 Oct 2010 at 3:23

[GoogleCodeExporter]

can someone include this in the next release? I've even dealt too little with 
it.

Original comment by fug....@gmail.com on 15 Oct 2010 at 4:10

[GoogleCodeExporter]

I have bluetooth running with protocols, so you don't need BT file transfer.

Simply don't remove everything in openetna file. just the bluetoothd service.

Also attach script for starting bluetoothd and hciattach. 

Also found out that xircom driver works BUT IT NOT SURE IT'S THE RIGHT ONE. 

The script has this driver.

USE ON YOUR OWN RISK!

Are trying to get it to work in init.rc.

Just flashed but the updates in init.rc don't follow to phone...

Any ideas?

// Figgelus

Original comment by figgelu...@gmail.com on 15 Oct 2010 at 10:25

Attachments:

• bluetooth

[GoogleCodeExporter]

Great work! I'm really happy you're making progress. With bluetooth working 
OpenEtna is going to be close to perfect! :) Thank you all!

Original comment by smald...@gmail.com on 15 Oct 2010 at 10:33

[GoogleCodeExporter]

Thanks, for your Great Work!

Original comment by croxz3...@gmail.com on 15 Oct 2010 at 11:10

[GoogleCodeExporter]

I simply created a file in /etc/init.d/ called 07bluetooth with same 
permissions as the other files in /etc/init.d/ with the following in it

#!/system/bin/sh 
/system/bin/hciattach /dev/ttyHS0 xircom 
/system/bin/bluetoothd 

I removed the rfkill, this way when the phone is rebooted it will remember the 
state BT was in when it was reset instead of always starting off.

This was 2.2/rc6

Original comment by philgillam@gmail.com on 16 Oct 2010 at 1:41

[GoogleCodeExporter]

First sorry my english. philgillam. ¿What steps did you? I cant create or move 
any file to /etc/init.d/, no permissions.

Original comment by d4rk...@gmail.com on 16 Oct 2010 at 1:52

[GoogleCodeExporter]

for those that have problem following steps.
1) download root explorer from market and allow it superuser permissions when 
it opens.
2) change directory to /etc/init.d and change filesystem from RO to RW
3) copy 3 lines from my post #46 to a new file called 07bluetooth, save file
4) check permissions of file are same as other files (owner, group, mode)
5) reboot phone

Original comment by philgillam@gmail.com on 16 Oct 2010 at 7:02

[GoogleCodeExporter]

it's working!!
Thank you.
Openetna is getting perfect.
It juste misses OpenGL, video reording and 5MP camera and it will be perfect.
After there will just be some ehaancement!

Original comment by kris10d...@gmail.com on 16 Oct 2010 at 10:08

[GoogleCodeExporter]

Great job! I think it's real fix of BT problem.
Thanks for figellus84.

Original comment by Fedo...@gmail.com on 16 Oct 2010 at 10:15