I am using Debian (Mixed/Unstable) and I have a Nano Tiny Bluetooth adapter
that uses an Accel Semiconductor microchip. The mobile phone is visible to
the computer, but I cannot see the computer from the mobile phone. How do I
make the computer visible to my mobile phone?
I have enabled both pscan and iscan as follows:
hciconfig hci0 piscan
The hciconfig tool reveals the following configuration:
hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING PSCAN ISCAN
RX bytes:2273 acl:0 sco:0 events:59 errors:0
TX bytes:479 acl:0 sco:0 commands:45 errors:0
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'Accel-OB2'
Class: 0x4a0100
Service Classes: Networking, Capturing, Telephony
Device Class: Computer, Uncategorized
HCI Version: 2.0 (0x3) Revision: 0x44
LMP Version: 2.0 (0x3) Subversion: 0x3
Manufacturer: Cambridge Silicon Radio (10)
Does anyone know what the class codes are? Should I change the class code
in the /etc/bluetooth/main.conf configuration file?
Mark.
--- On Sat, 25/6/11, Peter Hurley <[email protected]> wrote:
> The typical way to debug bluetooth issues is:
> 1. add debug flag "-d" to bluetoothd command line and then
> review system log
There is some strange stuff going on:
Jun 25 19:48:27 venus udevd[25268]: failed to execute '/usr/local/sbin/bluetoothd' '/usr/local/sbin/bluetoothd --udev': No such file or directory
bluetoothd is in /usr/sbin not /usr/local/sbin. I don't know how to switch that.
Jun 25 19:48:41 venus bluetoothd[916]: input-headset driver probe failed for device 00:1F:CC:C2:E4:86
I don't know what that is. I don't have a bluetooth headset. That is the address of my mobile phone.
Mark.
--- On Sat, 25/6/11, Peter Hurley <[email protected]> wrote:
> From: Peter Hurley <[email protected]>
> Subject: Re: How do I make the computer visible to the mobile phone?
> To: "[email protected]" <[email protected]>
> Cc: "[email protected]" <[email protected]>
> Date: Saturday, 25 June, 2011, 17:27
> On Sat, 2011-06-25 at 08:44 -0400,
> Mark Hobley wrote:
> > I am using Debian (Mixed/Unstable) and I have a Nano
> Tiny Bluetooth adapter
> > that uses an Accel Semiconductor microchip. The mobile
> phone is visible to
> > the computer, but I cannot see the computer from the
> mobile phone. How do I
> > make the computer visible to my mobile phone?
>
> ??? sudo hciconfig hci0 piscan
>
> Should work.
>
> Did you resolve your earlier problem with timeouts?
> http://marc.info/?l=linux-bluetooth&m=130877416213307&w=2
>
> In a terminal:
> ??? hcitool scan
> should print out the BD_ADDR of the phone
> ??? bluez-simple-agent hci0 BD_ADDR
> should pair.
> What happens?
>
> The typical way to debug bluetooth issues is:
> 1. add debug flag "-d" to bluetoothd command line and then
> review system
> log
> 2. run hcidump while performing operation that's not
> working
> ??? sudo hcidump -tVX > filename
> ???-or-
> ??? sudo hcidump -t --save-dump=filename
> ??? hcidump -tVXr filename
> Post the dump and let someone look at it.
>
> >? ? ? ???Class: 0x4a0100
> >? ? ? ???Service Classes:
> Networking, Capturing, Telephony
> >? ? ? ???Device Class:
> Computer, Uncategorized
>
> These look ok to me.
>
> > Does anyone know what the class codes are?
>
> Class_of_device is defined here:
> https://www.bluetooth.org/Technical/AssignedNumbers/baseband.htm
>
> > Should I change the class code
> > in the /etc/bluetooth/main.conf configuration file?
>
> No.
>
--- On Sat, 25/6/11, Peter Hurley <[email protected]> wrote:
> Did you resolve your earlier problem with timeouts?
> http://marc.info/?l=linux-bluetooth&m=130877416213307&w=2
No. I still get that error. However, once in a blue moon, my mobile phone does becomes visibile and the timeout does not occur. I then try to take advantage of this uptime, and I get stung by the invisible computer problem. I am trying to solve both issues.
Mark.
T24gU2F0LCAyMDExLTA2LTI1IGF0IDA4OjQ0IC0wNDAwLCBNYXJrIEhvYmxleSB3cm90ZToNCj4g
SSBhbSB1c2luZyBEZWJpYW4gKE1peGVkL1Vuc3RhYmxlKSBhbmQgSSBoYXZlIGEgTmFubyBUaW55
IEJsdWV0b290aCBhZGFwdGVyDQo+IHRoYXQgdXNlcyBhbiBBY2NlbCBTZW1pY29uZHVjdG9yIG1p
Y3JvY2hpcC4gVGhlIG1vYmlsZSBwaG9uZSBpcyB2aXNpYmxlIHRvDQo+IHRoZSBjb21wdXRlciwg
YnV0IEkgY2Fubm90IHNlZSB0aGUgY29tcHV0ZXIgZnJvbSB0aGUgbW9iaWxlIHBob25lLiBIb3cg
ZG8gSQ0KPiBtYWtlIHRoZSBjb21wdXRlciB2aXNpYmxlIHRvIG15IG1vYmlsZSBwaG9uZT8NCg0K
CXN1ZG8gaGNpY29uZmlnIGhjaTAgcGlzY2FuDQoNClNob3VsZCB3b3JrLg0KDQpEaWQgeW91IHJl
c29sdmUgeW91ciBlYXJsaWVyIHByb2JsZW0gd2l0aCB0aW1lb3V0cz8NCmh0dHA6Ly9tYXJjLmlu
Zm8vP2w9bGludXgtYmx1ZXRvb3RoJm09MTMwODc3NDE2MjEzMzA3Jnc9Mg0KDQpJbiBhIHRlcm1p
bmFsOg0KCWhjaXRvb2wgc2Nhbg0Kc2hvdWxkIHByaW50IG91dCB0aGUgQkRfQUREUiBvZiB0aGUg
cGhvbmUNCglibHVlei1zaW1wbGUtYWdlbnQgaGNpMCBCRF9BRERSDQpzaG91bGQgcGFpci4NCldo
YXQgaGFwcGVucz8NCg0KVGhlIHR5cGljYWwgd2F5IHRvIGRlYnVnIGJsdWV0b290aCBpc3N1ZXMg
aXM6DQoxLiBhZGQgZGVidWcgZmxhZyAiLWQiIHRvIGJsdWV0b290aGQgY29tbWFuZCBsaW5lIGFu
ZCB0aGVuIHJldmlldyBzeXN0ZW0NCmxvZw0KMi4gcnVuIGhjaWR1bXAgd2hpbGUgcGVyZm9ybWlu
ZyBvcGVyYXRpb24gdGhhdCdzIG5vdCB3b3JraW5nDQoJc3VkbyBoY2lkdW1wIC10VlggPiBmaWxl
bmFtZQ0KICAgLW9yLQ0KCXN1ZG8gaGNpZHVtcCAtdCAtLXNhdmUtZHVtcD1maWxlbmFtZQ0KCWhj
aWR1bXAgLXRWWHIgZmlsZW5hbWUNClBvc3QgdGhlIGR1bXAgYW5kIGxldCBzb21lb25lIGxvb2sg
YXQgaXQuDQoNCj4gICAgICAgICBDbGFzczogMHg0YTAxMDANCj4gICAgICAgICBTZXJ2aWNlIENs
YXNzZXM6IE5ldHdvcmtpbmcsIENhcHR1cmluZywgVGVsZXBob255DQo+ICAgICAgICAgRGV2aWNl
IENsYXNzOiBDb21wdXRlciwgVW5jYXRlZ29yaXplZA0KDQpUaGVzZSBsb29rIG9rIHRvIG1lLg0K
DQo+IERvZXMgYW55b25lIGtub3cgd2hhdCB0aGUgY2xhc3MgY29kZXMgYXJlPyANCg0KQ2xhc3Nf
b2ZfZGV2aWNlIGlzIGRlZmluZWQgaGVyZToNCmh0dHBzOi8vd3d3LmJsdWV0b290aC5vcmcvVGVj
aG5pY2FsL0Fzc2lnbmVkTnVtYmVycy9iYXNlYmFuZC5odG0NCg0KPiBTaG91bGQgSSBjaGFuZ2Ug
dGhlIGNsYXNzIGNvZGUgDQo+IGluIHRoZSAvZXRjL2JsdWV0b290aC9tYWluLmNvbmYgY29uZmln
dXJhdGlvbiBmaWxlPw0KDQpOby4NCg==