GNOME Bugzilla – Bug 622545
Can't set up bluetooth DUN connection through Android's PDA Net
Last modified: 2010-10-14 04:21:12 UTC
I'm running Fedora 13. I've used bluetooth DUN with a Nokia and Sony Ericsson devices successfully, but when trying to setup a DUN connection to a Motorola Milestone Android devices running PDA Net ( http://www.junefabrics.com/android/index.php ) I get an error message: "Error: timed out detecting phone details." The process is: 1. Install PDA net free edition version 2.42 on Android device and launch it. 2. Select "Enable Bluetooth DUN" from the PDA Net menu. 3. Approve the Android bluetooth visiblity confirmation dialog 4. Right click bluetooth icon on GNOME panel and select "Set up a new device". 5. Select the Android device from the list and complete the pairing. 6. When the "Setup completed" dialog comes up on the computer, check "Access the internet using your mobile phone". The dialog will now show an animation and a label "detecting phone configuration". The PDA Net screen now says "PdaNet is connected!" and shows info data "Bytes: 0/0" and "Activities: 0/0". These do not change. The messages log shows something like this: Jun 24 02:17:23 sepiroth bluetoothd[19445]: link_key_request (sba=00:1C:26:D9:47:ED, dba=D8:54:3A:27:AE:01) After a while, the GNOME bluetooth dialog stops the animation and shows the message "Error: timed out detecting phone details." and unchecks the "Access the internet...". The PDA Net screen returns to the "standby mode". The messages log then shows something like this: Jun 24 02:18:08 sepiroth dbus: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.235" (uid=0 pid=19444 comm="/usr/sbin/bluetoothd) interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.280" (uid=16777216 pid=23948 comm="bluetooth-wizard)) If I then close the GNOME bluetooth setup dialog, DUN access through the android device is not enabled.
The dbus error is a Bluez error. To debug, could you: 1) remove the device via the Bluetooth icon in your panel to delete the pairing 2) in a terminal as root, run "modem-manager --debug" 3) re-pair the device, and check the "Dialup Networking" box 4) grab the modem-manager output and paste it into this bug Also, what version of modem-manager do you have installed?
I'm running Fedora 13, and I had to do the following to get modem-manager in debug mode: $ su - # service NetworkManager stop # killall modem-manager # modem-manager --debug & # service NetworkManager start After that, when I try to pair my phone and set DUN, I get this from modem manager: ---8<--- ** Message: Loaded plugin Generic ** Message: Loaded plugin Novatel ** Message: Loaded plugin Option ** Message: Loaded plugin Longcheer ** Message: Loaded plugin Sierra ** Message: Loaded plugin ZTE ** Message: Loaded plugin Nokia ** Message: Loaded plugin AnyData ** Message: Loaded plugin Option High-Speed ** Message: Loaded plugin Gobi ** Message: Loaded plugin Ericsson MBM ** Message: Loaded plugin MotoC ** Message: Loaded plugin Huawei ** (modem-manager:3114): DEBUG: (tty/ttyS1): port's parent platform driver is not whitelisted ** (modem-manager:3114): DEBUG: (tty/ttyS2): port's parent platform driver is not whitelisted ** (modem-manager:3114): DEBUG: (tty/ttyS3): port's parent platform driver is not whitelisted ** (modem-manager:3114): DEBUG: (tty/ttyS0): could not get port's parent device ** (modem-manager:3114): DEBUG: (net/pan0): could not get port's parent device ** (modem-manager:3114): DEBUG: (net/vboxnet0): could not get port's parent device ** (modem-manager:3114): DEBUG: (tty/rfcomm0): could not get port's parent device ** Message: (rfcomm0) opening serial device... ** (modem-manager:3114): DEBUG: <1277632317.132649> (rfcomm0) device open count is 1 (open) ** (modem-manager:3114): DEBUG: (rfcomm0): probe requested by plugin 'Generic' ** (modem-manager:3114): DEBUG: <1277632317.231990> (rfcomm0): --> 'AT+GCAP<CR>' ** (modem-manager:3114): DEBUG: <1277632321.178489> (rfcomm0): --> 'AT+GCAP<CR>' ** (modem-manager:3114): DEBUG: <1277632325.180343> (rfcomm0): --> 'AT+GCAP<CR>' ** (modem-manager:3114): DEBUG: <1277632329.180242> (rfcomm0) device open count is 0 (close) ** Message: (rfcomm0) closing serial device... ** Message: (rfcomm0) opening serial device... ** (modem-manager:3114): DEBUG: <1277632329.181366> (rfcomm0) device open count is 1 (open) ** (modem-manager:3114): DEBUG: <1277632329.181483> (rfcomm0): --> 00 78 f0 7e ** (modem-manager:3114): DEBUG: <1277632332.180153> (rfcomm0): --> 00 78 f0 7e ** (modem-manager:3114): DEBUG: <1277632335.182915> (rfcomm0) device open count is 0 (close) ** Message: (rfcomm0) closing serial device... ** (modem-manager:3114): DEBUG: (tty/rfcomm0): could not get port's parent device ** (modem-manager:3114): DEBUG: (tty/rfcomm0): could not get port's parent device ** (modem-manager:3114): DEBUG: (tty/rfcomm0): could not get port's parent device ** (modem-manager:3114): DEBUG: (tty/rfcomm0): could not get port's parent device ** (modem-manager:3114): DEBUG: (tty/rfcomm0): could not get port's parent device ** (modem-manager:3114): DEBUG: (tty/rfcomm0): could not get port's parent device ** (modem-manager:3114): DEBUG: (tty/rfcomm0): could not get port's parent device ---8<--- The two dumps with interesting data are from the first time I check the "DUN" checkbox. After the timeout, if I check it again the UI behaves exactly the same, but the log only shows "could not get port's parent device" messages. Also, while this is going on (and PDA Net shows that someone is connecting), 'rfcomm -a' shows: ---8<--- rfcomm0: 00:1C:26:D9:47:ED -> D8:54:3A:27:AE:01 channel 3 connected [reuse-dlc tty-attached] ---8<---
Also, as per the suggestion in RedHat Bug https://bugzilla.redhat.com/show_bug.cgi?id=600137 (which seems to be the same thing), here is the relevant output from .xsession-errors: ---8<--- ** Message: has_config_widget D8:54:3A:27:AE:01 DialupNetworking ** Message: has_config_widget D8:54:3A:27:AE:01 OBEXObjectPush ** Message: has_config_widget D8:54:3A:27:AE:01 AudioSource ** Message: has_config_widget D8:54:3A:27:AE:01 A/V_RemoteControlTarget ** Message: has_config_widget D8:54:3A:27:AE:01 Headset_-_AG ** Message: has_config_widget D8:54:3A:27:AE:01 HandsfreeAudioGateway ** Message: has_config_widget D8:54:3A:27:AE:01 Phonebook_Access_-_PSE ** Message: has_config_widget D8:54:3A:27:AE:01 DialupNetworking ** Message: has_config_widget D8:54:3A:27:AE:01 OBEXObjectPush ** Message: has_config_widget D8:54:3A:27:AE:01 AudioSource ** Message: has_config_widget D8:54:3A:27:AE:01 A/V_RemoteControlTarget ** Message: has_config_widget D8:54:3A:27:AE:01 Headset_-_AG ** Message: has_config_widget D8:54:3A:27:AE:01 HandsfreeAudioGateway ** Message: has_config_widget D8:54:3A:27:AE:01 Phonebook_Access_-_PSE ** Message: Default Bluetooth adapter is powered ** Message: dun_start: starting DUN device discovery... ** Message: dun_start: calling Connect... ** Message: dun_start: finished ** Message: dun_connect_cb: processing Connect reply ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0' ** Message: dun_connect_cb: finished ** (bluetooth-wizard:4214): WARNING **: dun_timeout_cb: Error: timed out detecting phone details. ** (nm-applet:2296): WARNING **: _nm_object_get_property: Error getting 'Default' for /org/freedesktop/NetworkManager/ActiveConnection/4: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ** Message: dun_start: starting DUN device discovery... ** Message: dun_start: calling Connect... ** (bluetooth-wizard:4214): CRITICAL **: dbus_g_proxy_add_signal: assertion `g_datalist_id_get_data (&priv->signal_signatures, q) == NULL' failed ** Message: dun_start: finished ** Message: dun_connect_cb: processing Connect reply ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0' ** Message: dun_connect_cb: finished ** (nm-applet:2296): WARNING **: _nm_object_get_property: Error getting 'Default' for /org/freedesktop/NetworkManager/ActiveConnection/5: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (bluetooth-wizard:4214): WARNING **: dun_timeout_cb: Error: timed out detecting phone details. ** Message: dun_start: starting DUN device discovery... ** Message: dun_start: calling Connect... ** (bluetooth-wizard:4214): CRITICAL **: dbus_g_proxy_add_signal: assertion `g_datalist_id_get_data (&priv->signal_signatures, q) == NULL' failed ** Message: dun_start: finished ** Message: dun_connect_cb: processing Connect reply ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0' ** Message: dun_connect_cb: finished ** (bluetooth-wizard:4214): WARNING **: dun_timeout_cb: Error: timed out detecting phone details. ** Message: dun_start: starting DUN device discovery... ** Message: dun_start: calling Connect... ** (bluetooth-wizard:4214): CRITICAL **: dbus_g_proxy_add_signal: assertion `g_datalist_id_get_data (&priv->signal_signatures, q) == NULL' failed ** Message: dun_start: finished ** Message: dun_connect_cb: processing Connect reply ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0' ** Message: dun_connect_cb: finished [4742:4742:1365408318:ERROR:chrome/browser/renderer_host/render_sandbox_host_linux.cc(385)] sendmsg: Connection refused ** (bluetooth-wizard:4214): WARNING **: dun_timeout_cb: Error: timed out detecting phone details. ** (nm-applet:2296): WARNING **: _nm_object_get_property: Error getting 'Default' for /org/freedesktop/NetworkManager/ActiveConnection/6: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ---8<---
So basically it seems that the phone is just not responding to DUN requests. The last thing we can try is talking to the phone directly with minicom to see what's going on. 1) mv /usr/sbin/modem-manager / (just to get it out of the way) 2) sdptool browse <phone bt addr> 3) look for the Dialup Networking record and remember the channel # 4) rfcomm connect hci0 <phone bt addr> <channel #> 5) put this into /etc/minirc.dfl: pu port /dev/rfcomm0 pu minit pu mreset 6) su - (yes, actual su) 7) minicom 8) type AT+GCAP and hit return to see if the phone responds this basically simulates what modem-manager and the bluetooth plugin are doing.
any news with this oded?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!