Cannot connect tether vie bluetooth (phone not discovered)

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Start the tether application in bluetooth mode
2. Try to join PAN from the computer
3. The phone is not detected as PAN-aware (bluetooth profile missing)

What is the expected output? What do you see instead?
Windows should fine the phone, detect it as PAN-capable and try to connect

What version of the product are you using? On what operating system?
HTC Hero with android-wifi-tether 1.52
Windows XP with stock MS drivers and another one with Broadcom drivers

Please provide any additional information below.
Both computers do not detect the Hero as PAN device. They see it, pair with 
it but cannot see its PAN profile.

Wifi tethering works just fine.

Original issue reported on code.google.com by los...@gmail.com on 27 Aug 2009 at 5:53

GoogleCodeExporter commented 9 years ago

Have you tried to start tethering _before_ pairing the devices?

Original comment by harald....@gmail.com on 28 Aug 2009 at 5:01

GoogleCodeExporter commented 9 years ago

Yes, i tried that as well but it didnt help!

Original comment by los...@gmail.com on 28 Aug 2009 at 5:08

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Notice the same behaviour with my Hero when trying on a Mac. No configurable 
services
is found, this is with stock ROM.

Original comment by jimmy.shimizu on 31 Aug 2009 at 4:58

GoogleCodeExporter commented 9 years ago

Same here. Tethering starts, I pair the device but no network services are 
found on
the device.

Original comment by robson...@gmail.com on 13 Sep 2009 at 12:40

GoogleCodeExporter commented 9 years ago

I am having the same problem.

I start _tethering_ in Bluetooth mode on the Hero.
I go through the process of pairing the PC with the Phone.
I am offered 2 "discovered" services by the Belkin/Broadcom software from my 
Hero: 
"ActiveSync" and "Voice Gateway".

I can add that:
I am using a Hero with the latest HTC ROM (2.73.405.5) as released on 11 Sept. 
2009
I followed the unlockr procedure for rooting the phone (cm-hero-recovery.img 
installed using flashrec-20090815.apk). This was performed post installation of 
the 
lastest HTC ROM and confirmed as working through the use of of the "TA Utility".

PC / Bluetooth details:
Windows XP 32bit with ServicePack 3

Belkin F8T012 USB Bluetooth 2.0 Adaptor using Broadcom drivers version 
5.1.0.1700 
(the latest available from Belkin UK support)

Original comment by john.mar...@gmail.com on 17 Sep 2009 at 4:56

GoogleCodeExporter commented 9 years ago

Same here using Modaco ROM 2.9 on a HTC Hero. 

I am using Linux with up to date bluez and hcitools and everything.

Output of services (sdptool browse MAC):

Browsing 00:23:D4:2C:45:A8 ...
Service Name: Voice gateway
Service RecHandle: 0x10000
Service Class ID List:
  "Handsfree Audio Gateway" (0x111f)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Handsfree" (0x111e)
    Version: 0x0105

Service Name: Voice gateway
Service RecHandle: 0x10001
Service Class ID List:
  "Headset Audio Gateway" (0x1112)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 2
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100

Service Name: Audio Source
Service Provider: Extended Systems
Service RecHandle: 0x10002
Service Class ID List:
  "Audio Source" (0x110a)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 25
  "AVDTP" (0x0019)
    uint16: 0x100
Profile Descriptor List:
  "Advanced Audio" (0x110d)
    Version: 0x0100

Service Name: AVRCP TG
Service RecHandle: 0x10003
Service Class ID List:
  "AV Remote Target" (0x110c)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 23
  "AVCTP" (0x0017)
    uint16: 0x100
Profile Descriptor List:
  "AV Remote" (0x110e)
    Version: 0x0100

Output of hcidump while trying to connect pand:

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
< ACL data: handle 11 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
> ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Info rsp: type 2 result 1
      Not supported
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 15 scid 0x0040
> HCI Event: Remote Name Req Complete (0x07) plen 255
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0f00 scid 0x0040 result 2 status 0
      Connection refused - PSM not supported

Notice the "PSM not supported". I have read elsewhere that this means that the 
service is not running on the remote side.

Kind regards

Florian

Original comment by dot...@gmail.com on 10 Nov 2009 at 10:48

GoogleCodeExporter commented 9 years ago

I update your app to 1.60 for my htc hero, no change. It still wont work

Original comment by dot...@gmail.com on 11 Nov 2009 at 12:01

GoogleCodeExporter commented 9 years ago

I tried to start the "pand" manually on the phone while logged in via "adb 
shell" and
with activated bluetooth:

# su -c "/data/data/android.tether/bin/pand --listen --role NAP --devup
/data/data/android.tether/bin/blue-up.sh -n"
pand[2687]: Bluetooth PAN daemon version 3.36
pand[2687]: Failed to connect to the local SDP server. Connection refused(111)

Original comment by dot...@gmail.com on 11 Nov 2009 at 8:21

GoogleCodeExporter commented 9 years ago

Almost identical as #10, can't find bluetooth PAN from any of my PCs. 
Reinstalled and
rebootet, nu luck. From console I ran the above commands, but instead got:

pand[1160]: Bluetooth PAN daemon version 3.36
pand[1160]: Bind failed. Address already in use(98)

Original comment by erv...@gmail.com on 13 Nov 2009 at 10:04

GoogleCodeExporter commented 9 years ago

Finally (after trying for two days), I figured out what was wrong. Pairing the
service is only working if the devices are paired in advance. Other bluetooth
services are identified without doing this, but the PAN service requires 
pairing in
advance....

Original comment by erv...@gmail.com on 13 Nov 2009 at 10:18

GoogleCodeExporter commented 9 years ago

@ervjhb: Could you please describe your procedure in detail? This might help 
others.
Thank you!

Original comment by harald....@gmail.com on 14 Nov 2009 at 2:44

GoogleCodeExporter commented 9 years ago

@ervjhb: tried that too, but no luck. I don't get an "Address already in use" 
but an
"Connection refused" error on  a Modaco ROM 2.9 with my HTC Hero

Original comment by dot...@gmail.com on 16 Nov 2009 at 11:21

GoogleCodeExporter commented 9 years ago

I'm having this same issue with wireless tether on my EVO.  Tried Broadcom 
drivers, Bluesoleil drivers, and MS stock drivers, without success.  

PC is running Windows XP Pro x64 and Bluetooth adaptor is a TrendNet TBW-105UB. 

Currently using MS stock drivers.  PC will find and pair with phone with no 
problems, but does not see the PAN service.  When attempting to join a PAN, it 
searches and claims no devices can be found that support PAN.  

I've tried pairing before joining the PAN, pairing during joining the PAN, 
pairing initiated from the phone, pairing initiated from the PC, pairing while 
tethering is running, pairing while tethering is stopped, tethering while each 
device is discoverable, tethering while one or the other or both devices are 
not discoverable, and every combination of those I can think of, none of which 
allow the PC to see the PAN service.  

If anyone has a solution to this, please post it.  This issue has been driving 
me nuts!

Original comment by joel.t.k...@gmail.com on 16 Jan 2011 at 1:03

GoogleCodeExporter commented 9 years ago

With the XOOM requiring infrastructure mode for wifi having bluetooth tethering 
for the Hero has again become important. The wifi works great with my laptop, 
but I have now have the Xoom Wifi Only version and need bluetooth tethering 
desperately.

The Xoom Wifi only will pair but does not recognize the PAN.

Original comment by jeffjas...@gmail.com on 7 Apr 2011 at 2:17

GoogleCodeExporter commented 9 years ago

i've tried it on the t-mobile g2 running CM7.0.3 (i know, not officially 
supported) but found the pand daemon starts just fine using the above command. 
gives no errors after running the command, but hcidump outputs the following 
after two failed attempts (it's worth noting the connecting device is a 
playbook, which i understand may wholly be the issue):

HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> 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: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Read Remote Extended Features (0x23) plen 13
> ACL data: handle 12 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 12 flags 0x00 dlen 16
< ACL data: handle 12 flags 0x00 dlen 10
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 12 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x0038
< ACL data: handle 12 flags 0x00 dlen 16
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Command Status (0x0f) plen 4
> ACL data: handle 12 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1691
< ACL data: handle 12 flags 0x00 dlen 18
< ACL data: handle 12 flags 0x00 dlen 12
> HCI Event: Remote Name Req Complete (0x07) plen 255
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 12 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      MTU 672
> ACL data: handle 12 flags 0x02 dlen 28
    L2CAP(d): cid 0x0040 len 24 [psm 0]
< ACL data: handle 12 flags 0x00 dlen 14
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 12 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 12 flags 0x00 dlen 12
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> 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 Event: Max Slots Change (0x1b) plen 3
> HCI Event: Read Remote Extended Features (0x23) plen 13
> ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 11 flags 0x00 dlen 16
< ACL data: handle 11 flags 0x00 dlen 10
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Command Status (0x0f) plen 4
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x0038
< ACL data: handle 11 flags 0x00 dlen 16
> HCI Event: Remote Name Req Complete (0x07) plen 255
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1691
< ACL data: handle 11 flags 0x00 dlen 18
< ACL data: handle 11 flags 0x00 dlen 12
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      MTU 672
> ACL data: handle 11 flags 0x02 dlen 28
    L2CAP(d): cid 0x0040 len 24 [psm 0]
< ACL data: handle 11 flags 0x00 dlen 14
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 11 flags 0x00 dlen 12
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4

Original comment by netrac...@gmail.com on 27 May 2011 at 2:55

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Any ideas why device is not recognized as a PAN AP? I'm trying to connect a 
nokia bluetooth only phone to alcatel move (android 2.2)

Original comment by akostadi...@gmail.com on 11 Mar 2012 at 6:20

GoogleCodeExporter commented 9 years ago

Same issue here: pand is running, but pc dont discover as PAN. Galaxy S with 
2.3.6

Original comment by elso.and...@gmail.com on 13 Mar 2012 at 1:26

342156 / android-wifi-tether

Cannot connect tether vie bluetooth (phone not discovered) #140