I have just got Bluetooth working on my Thinkpad (Debian Testing/Squeeze) and it will pair with my Android 'phone but the signal keeps fluctuating. The link quality between 100% and -1%, the strength between 58% and -1 and it does this at around 2-5 second intervals.
It does it even when the 'phone is next to the laptop. Can anyone suggest a reason for this?
Barry Samuels asked:
I have just got Bluetooth working on my Thinkpad (Debian Testing/Squeeze) and it will pair with my Android 'phone but the signal keeps fluctuating. The link quality between 100% and -1%, the strength between 58% and -1 and it does this at around 2-5 second intervals.
It does it even when the 'phone is next to the laptop. Can anyone suggest a reason for this?
No idea if they're any good, but I can suggest two:
1. interference from another badly-behaved Bluetooth device nearby;
2. some incompatibility between the implementations.
I think there's something you can install on a Debian system to dump the bluetooth traffic in copious detail, but I don't remember its name. Then you can try to compare an example working session with what your devices are doing.
Is performance actually impacted? What's reporting the link quality? Could it be a buggy reporting routine? (Wasn't the iphone's signal strength partly a buggy reporting routing?)
Hope that helps,
On 21/11/10 13:54:36, MJ Ray wrote:
Barry Samuels asked:
I have just got Bluetooth working on my Thinkpad (Debian Testing/Squeeze) and it will pair with my Android 'phone but the signal keeps fluctuating. The link quality between 100% and -1%, the strength between 58% and -1 and it does this at around 2-5 second intervals.
It does it even when the 'phone is next to the laptop. Can anyone suggest a reason for this?
No idea if they're any good, but I can suggest two:
interference from another badly-behaved Bluetooth device nearby;
some incompatibility between the implementations.
I think there's something you can install on a Debian system to dump the bluetooth traffic in copious detail, but I don't remember its name. Then you can try to compare an example working session with what your devices are doing.
Is performance actually impacted? What's reporting the link quality? Could it be a buggy reporting routine? (Wasn't the iphone's signal strength partly a buggy reporting routing?)
Hope that helps,
MJ Ray (slef), member of www.software.coop, a for-more-than-profit co- op. Webmaster, Debian Developer, Past Koha RM, statistician, former lecturer.
Thanks for offering those suggestions.
1. There is, as far as I'm aware, no other Bluetooth devices in range.
2. Signal details are being reported by Blueman-Manager. I have tried it with the version of Windows XP that came with the laptop and I can connect to the 'phone and send a file to it. During this process a window pops up on the 'phone asking if I want to recieve the file. I get no such response when using Debian/Blueman so I assume the 'phone isn't recieving a request it can understand or not recieving the request at all.
As far as performance being impacted as I can't do anything with it yet there is no performance. :-)) To avoid any misunderstanding - it's an Android 'phone not an iPhone.
Barry Samuels wrote: [...]
- Signal details are being reported by Blueman-Manager. I have tried it
with the version of Windows XP that came with the laptop and I can connect to the 'phone and send a file to it. During this process a window pops up on the 'phone asking if I want to recieve the file. I get no such response when using Debian/Blueman so I assume the 'phone isn't recieving a request it can understand or not recieving the request at all.
As far as performance being impacted as I can't do anything with it yet there is no performance. :-)) To avoid any misunderstanding - it's an Android 'phone not an iPhone.
Surely both Android and Debian should have good debugging tools available. Off-list, someone suggested I might have been thinking of bluez-hcidump for debian: http://packages.debian.org/bluez-hcidump
I don't know Android enough to suggest a tool for that.
I had a problem with the Bluetooth/Gnome things being broken in the default installation of a recent version of Debian, but an upgrade had them working until I changed phone recently, so make sure you're current.
Other than my session-watching idea, maybe someone else has tips.
Hope that helps,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
MJ Ray wrote:
Barry Samuels wrote: [...]
- Signal details are being reported by Blueman-Manager. I have tried it
with the version of Windows XP that came with the laptop and I can connect to the 'phone and send a file to it. During this process a window pops up on the 'phone asking if I want to recieve the file. I get no such response when using Debian/Blueman so I assume the 'phone isn't recieving a request it can understand or not recieving the request at all.
As far as performance being impacted as I can't do anything with it yet there is no performance. :-)) To avoid any misunderstanding - it's an Android 'phone not an iPhone.
Surely both Android and Debian should have good debugging tools available. Off-list, someone suggested I might have been thinking of bluez-hcidump for debian: http://packages.debian.org/bluez-hcidump
I don't know Android enough to suggest a tool for that.
One could install the Android SDK and then use "[installdir]/android-sdk/tools/adb logcat" to get an extensively verbose dump of everything the device is up to. As it happens, BlueTooth seems particularly verbose: here's a few lines from several hundred lines of debugging generated by turning BT on:
<snip> D/BTL_IFC ( 96): BTL_IFC_CtrlSend: BTL_IFC_CtrlSend I/BTL_IFC ( 96): send_ctrl_msg: [BTL_IFC CTRL] send BTLIF_PBS_ENABLE (PBS) 0 pbytes (hdl 161) D/BluetoothServiceManager( 96): ***startService(): Done starting service: bluetooth_pbs*** I/GKI_LINUX(26082): GKI_sched_lock I/GKI_LINUX(26082): GKI_sched_unlock I/BTL-IFS (26082): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_PBS_ENABLE_EVT (PBS) 0 pbytes (hdl 18) I/BTL_IFC ( 96): btl_ifc_ctrl_rx: [BTL_IFC CTRL] recv BTLIF_PBS_ENABLE_EVT (PBS) 2 pbytes (hdl 161) D/com_broadcom_bt_service_pbap_PBAPService.cpp( 96): #### handlePbapEvent 0xad3f324a #### D/com_broadcom_bt_service_pbap_PBAPService.cpp( 96): ### PBAP Opend #### I/BluetoothPBAPService( 96): onPbapEnabled D/com_broadcom_bt_service_pbap_PBAPService.cpp( 96): ### PBAP Opend #### I/BluetoothPBAPService( 96): onPbapConnected I/BTL-IFS (26082): main_server_thread: [CTRL] Client connected (19) I/BTL_IFC_WRP( 194): wrp_sock_connect: Connected. (67) I/BTL_IFC ( 194): send_ctrl_msg: [BTL_IFC CTRL] send BTLIF_REGISTER_SUBSYS_REQ (SCO) 0 pbytes (hdl 67) I/BTL-IFS (26082): attach_client: ######## Attached client subsystem SCO (19) ######## D/BTL-IFS (26082): send_registration_rsp: send_registration_rsp [0] I/BTL-IFS (26082): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_REGISTER_SUBSYS_RSP (CTRL) 2 pbytes (hdl 19) D/BTL_IFC ( 194): BTL_IFC_RegisterSubSystem: add new ctrl fd to active set </snip>
If you're going to get any useful clues, this is probably where to find them :-)
Cheers, Simon
- -- - --------------------------------------------------------------------- Simon Ransome http://nosher.net
Photography RSS feed - http://nosher.net/images/images.rss
On 22/11/10 11:31:54, simon ransome wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
MJ Ray wrote:
Barry Samuels wrote: [...]
- Signal details are being reported by Blueman-Manager. I have tried
it with the version of Windows XP that came with the laptop and I can connect to the 'phone and send a file to it. During this process a window pops up on the 'phone asking if I want to recieve the file. I get no such response when using Debian/Blueman so I assume the 'phone isn't recieving a request it can understand or not recieving the request at all.
As far as performance being impacted as I can't do anything with it yet there is no performance. :-)) To avoid any misunderstanding -
it's an Android 'phone not an iPhone.
Surely both Android and Debian should have good debugging tools available. Off-list, someone suggested I might have been thinking of bluez-hcidump for debian: http://packages.debian.org/bluez-hcidump
I don't know Android enough to suggest a tool for that.
One could install the Android SDK and then use "[installdir]/android-sdk/tools/adb logcat" to get an extensively verbose dump of everything the device is up to. As it happens, BlueTooth seems particularly verbose: here's a few lines from several hundred lines of debugging generated by turning BT on:
</snip>
If you're going to get any useful clues, this is probably where to find them :-)
Cheers, Simon
Installing the Android SDK seems a little extreme. :-))
I think I'll give up on this for the time being. I was trying to do it simply because my 'phone and laptop both have Bluetooth support and I thought that it might be useful but I don't have a need for it.
Thanks to both of you for your suggestions.