Bluetooth hcitool cc connection drop problem

[crazytrain1978]

Hi Hoping for some help with my problem please

I am having a lot of difficulty pairing with other devices (testing with my phone atm)

I have set my bluetooth pin in /var/lib and in /var/lib/bluetooth in a directory named my MAC inside a file called pincodes which contains my MAC and a space and then the pin hcitool cc connection drop problem

Everything seems ok, i can scan and inquire devices and can even pair from the phone to bt4 when using a simple-agent pin agent which i found here Arch Linux Forums / Pairing bluetooth devices
hcito
but when i try and do a simple hcitool cc MACADDRESS
connection it seems to succeed for a second then drop the connection

and i can see this if i do hcitool con and also by the disconnect in the hcidump log at the end of the thread

straight after i do the hcitool cc command it will give me

>Connections:
> < ACL MACADDRESS handle 11 state 1 lm MASTER

and then if i run the same command 2 secs later the con is gone


New Info for Post Edit: I have also now tried a different bluetooth device and had the exact same issue and results, so that should rule out the device and its compatibility with backtrack as the problem.. presumably?...

Not sure if its related but the command
sdptool -i hci0 records --raw MACADDRESS

keeps giving me
>Failed to connect to SDP server on MACADDRESS Invalid argument


This is what my main.conf looks like

[General]

# List of plugins that should not be loaded on bluetoothd startup
#DisablePlugins = network,input

# Default adaper name
# %h - substituted for hostname
# %d - substituted for adapter id
Name = Pass_Is_1234

# Default device class. Only the major and minor device class bits are
# considered.
Class = 0x0a210c

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
PairableTimeout = 0

# Use some other page timeout than the controller default one
# which is 16384 (10 seconds).
PageTimeout = 8192

# Discover scheduler interval used in Adapter.DiscoverDevices
# The value is in seconds. Defaults is 0 to use controller scheduler.
DiscoverSchedulerInterval = 0

# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true

# Remember the previously stored Powered state when initializing adapters
RememberPowered = true

# Use vendor, product and version information for DID profile support.
# The values are separated by ":" and VID, PID and version.
#DeviceID = 1234:5678:abcd

# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to true.
ReverseServiceDiscovery = true



HCIDUMP log of the hcitool cc connection attempt

>HCI sniffer - Bluetooth packet analyzer ver 1.42
>device: hci0 snap_len: 1028 filter: 0xffffffff
>< HCI Command: Create Connection (0x01|0x0005) plen 13
>> HCI Event: Command Status (0x0f) plen 4
>> HCI Event: Connect Complete (0x03) plen 11
>< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
>> HCI Event: Command Status (0x0f) plen 4
>> HCI Event: Read Remote Supported Features (0x0b) plen 11
>< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
>> HCI Event: Command Status (0x0f) plen 4
>< HCI Command: Remote Name Request (0x01|0x0019) plen 10
>> HCI Event: Command Status (0x0f) plen 4
>> HCI Event: Max Slots Change (0x1b) plen 3
>> HCI Event: Read Remote Extended Features (0x23) plen 13
>> HCI Event: Remote Name Req Complete (0x07) plen 255
>< HCI Command: Disconnect (0x01|0x0006) plen 3
>> HCI Event: Command Status (0x0f) plen 4
>> HCI Event: Disconn Complete (0x05) plen 4




Has anyone else had any similar problems to this? i have tried looking in dmesg and /var/logs/syslog and cant see any errors occurring (not even sure if they would be found here to be honest)