gnome-phone-manager doesn't connect to phone

[Ali Sabil]

Binary package hint: gnome-phone-manager

Hi,

I tried to use gnome-phone-manager to connect to my phone using bluetooth, actually when I run gnome-phone-manager and try to connect, I get a message on my phone asking me for confirmation, after granting the access, gnome-phone-manager just say that the connection failed.

Everything else is working perfectly, I can send and receive files using nautilus-sendto, and Bluetooth File Sharing.

Thank you for your help,

--
Ali

[tayirvadai (tayirvadai-vikram)]

similar thing happened to me still waiting for a solution.
i use Sony ericsson w810i.

i tried to connect it through wammu,kmoblietools,multisync&gnokii but failed. :(

wammu says gnome-bluetooth is not present so cannot scan bluetooth. but i was able to send and receive photos via blue tooth using gnome-obex.Also infrared port was present in ttys2 even after changing that in settings i was not able to connect.

kmobiletools is not showing the rfcomm0 device when my dmesg | grep -i blue shows the following
-------------
[17179597.800000] Bluetooth: Core ver 2.8
[17179597.800000] Bluetooth: HCI device and connection manager initialized
[17179597.800000] Bluetooth: HCI socket layer initialized
[17179597.836000] Bluetooth: HCI USB driver ver 2.9
[17179641.664000] Bluetooth: L2CAP ver 2.8
[17179641.664000] Bluetooth: L2CAP socket layer initialized
[17179641.752000] Bluetooth: HIDP (Human Interface Emulation) ver 1.1-mh1
[17179641.764000] Bluetooth: RFCOMM socket layer initialized
[17179641.764000] Bluetooth: RFCOMM TTY layer initialized
[17179641.764000] Bluetooth: RFCOMM ver 1.7
--------------
gnokki hangs up.

multisync also hangs up.

[Mila Kuchta (kuchta)]

Same as here. I can receive files via gnome-obex, send files via nautilus-sendto but gnome-phone-manager is not able to connect to my phone and bluetooth discovery shows me some cachced records. hcitool scan works fine.

[Olivier Anh (twen)]

Hello,

I confirm this bug, gnome-phone-manager doesn't seem to connect when used with Edgy. It was running fine with Hoary, but can't remember with Dapper.

$ gnome-phone-manager
** Message: New connection device is 00:00:00:00:00:00
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
conn_complete: status 0x00
** Message: Failed connection to device on 00:00:00:00:00:00
** Message: Exiting connect thread

The Device IP is the correct one (I just removed the true IP). The phone indicates a data transmission is occuring when gnome-phone-manager is running. My phone is a Sony Ericsson T630.

However :

- Mutisync is fully functional : I can sync to/from evolution and backup

- gnome-obex-server is running fine also, I can send datas to my phone.

[canatella (dam-cosinux)]

The problem is in libgnokii3. Recompiling and installing libgnokii 0.6.14 from feisty solved the problem for me.

[Littleiffel (thierry-nicola)]

I still have the problem that gnome-phone-manager tries to connect to the phone. I get a message on the phone for granting access to the phone's data to my laptop, but nothing happens.

I have a Sony Ericsson w810i. And I reinstalled the package libgnokii3 through aptitude, but problem remains.

Canatella: How did you install the libgnokii3?

[Áron Sisak (asisak)]

Please confirm if the bug is still present in Feisty or Gutsy.
On the other hand if the bug is in fact in libgnokii3, we should modify the source package.

[tyler (tyler-chickn)]

I'm on Gutsy, I'm confirming this problem as well. (Sony Eric. w810i)

** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
conn_complete: status 0x00

** (gnome-phone-manager:8573): WARNING **: gn_gsm_initialise: Command timed out.
** Message: Failed connection to device on 00:18:13:0B:63:0A
** Message: Exiting connect thread

[Emmet Hikory (persia)]

There's actually lots of bugs represented here. The primary issue is that gnome-phone-manager has a truly poor UI when gnokii doesn't support the hardware, in that everything apparently works, but it always fails to connect (which is sometimes a regression). As this is only exposed when gnokii doesn't support hardware, this bug report tends to collect reports for each type of phone that gnokii doesn't support.

For those encountering this issue, the workaround is to get gnokii support for your phone, one way to help with that is to test your phone with gnokii directly, and report a bug against gnokii with your phone details if it doesn't work.

If anyone can reproduce this with a phone that gnokii does support, or can determine an appropriate hook in gnome-phone-manager to detect that the phone is present, but not supported, please comment in detail here to help move towards a final solution.

[Antonis Kaladis (nw-raptor)]

k800 via bluetooth on my gutsy laptop:

WARNING **: gn_gsm_initialise: Command timed out.
and then fails.

if i remember correctly i never got it to work on previous versions of ubuntu either...

[zietbukuel (zietbukuel)]

I also have this problem in Gutsy, I'm using a SE W610i. This is the output.

** Message: bdaddr 00:1C:A4:F9:CC:59
** Message: New connection device is 00:1C:A4:F9:CC:59 (changed)
** Message: New connection device is 00:1C:A4:F9:CC:59 (not changed)
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
conn_complete: status 0x00

** (gnome-phone-manager:5936): WARNING **: gn_gsm_initialise: Command timed out.
** Message: Failed connection to device on 00:1C:A4:F9:CC:59
** Message: Exiting connect thread
** Message: Auto-retrying the connection
** Message: New connection device is 00:1C:A4:F9:CC:59 (not changed)
** Message: New connection device is 00:1C:A4:F9:CC:59 (not changed)
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
conn_complete: status 0x00

[Davidiam (hectorjerezano)]

I also have Gusty my phone is a sony w810
I found a workaround ;

Following the Configuring the rfcomm device is this link https://help.ubuntu.com/community/BluetoothDialup.

1.-sdptool browse 00:18:13:04:9A:C3, I get this and other services=

Browsing 00:18:13:04:9A:C3 ...
Service Description: Sony Ericsson W810
Service RecHandle: 0x10000
Service Class ID List:
  "PnP Information" (0x1200)

Service Name: OBEX SyncML Client
Service RecHandle: 0x10001
Service Class ID List:
  UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
  "OBEX" (0x0008)

Service Name: Dial-up Networking
Service RecHandle: 0x10002
Service Class ID List:
  "Dialup Networking" (0x1103)
  "Generic Networking" (0x1201)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 2
Profile Descriptor List:
  "Dialup Networking" (0x1103)
    Version: 0x0100

Service Name: Serial Port
Service RecHandle: 0x10003
Service Class ID List:
  "Serial Port" (0x1101)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 3

Service Name: HF Voice Gateway
Service RecHandle: 0x10004
Service Class ID List:
  "Handfree Audio Gateway" (0x111f)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 4
Profile Descriptor List:
  "Handsfree" (0x111e)
    Version: 0x0101

Service Name: HS Voice Gateway
Service RecHandle: 0x10005
Service Class ID List:
  "Headset Audio Gateway" (0x1112)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 5
Profile Descriptor List:
  "Headset" (0x1108)
    Version: 0x0100

Service Name: OBEX Object Push
Service RecHandle: 0x10006
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 6
  "OBEX" (0x0008)
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100

Service Name: OBEX File Transfer
Service RecHandle: 0x10007
Service Class ID List:
  "OBEX File Transfer" (0x1106)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 7
  "OBEX" (0x0008)
Profile Descriptor List:
  "OBEX File Transfer" (0x1106)
    Version: 0x0100

Service Name: OBEX IrMC Sync Server
Service RecHandle: 0x10008
Service Class ID List:
  "IrMC Sync" (0x1104)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 8
  "OBEX" (0x0008)
Profile Descriptor List:
  "IrMC Sync" (0x1104)
    Version: 0x0100

Service Name: NAP service
Service Description: NAP description
Service RecHandle: 0x10009
Service Class ID List:
  "Network Access Point" (0x1116)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 15
  "BNEP" (0x000f)
    Version: 0x0100
    SEQ8: 0 6
Language Base Attr List:
  code_ISO639: 0x656e
  encoding: 0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Network Access Point" (0x1116)
    Version: 0x0100

Service Name: Mouse & Keyboard
Service Description: Remote Control
Service Provider: Sony Ericsson
Service RecHandle: 0x1000a
Service Class ID List:
  "Human Interface Device" (0x1124)
Protocol Descriptor List:
  "L2CAP" (0x0100)
...

[Connor Imes (ckimes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Connor Imes (ckimes)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!