Samsung B2100 connection closed.

[GoogleCodeExporter]

* OS:Linux
* Player: MPD
Phone: Samsung B2100

The phone client connects and immediately disconnects, on the phone it says 
"connection closed by the other side" 
in the remuco log it says
 "2010-07-07 17:15:57,068 [  ERROR] [     net.py  260] connection to client ('00:26:5D:B2:A4:CB', 3) broken"

I have given it permissions on the phone...

Original issue reported on code.google.com by jckeert...@gmail.com on 7 Jul 2010 at 11:49

[GoogleCodeExporter]

Looking at the remuco log (using DEBUG log level), does it report that the 
hello message has been sent successfully?

Original comment by obensonne@googlemail.com on 8 Jul 2010 at 7:48

• Changed state: Chatting

[GoogleCodeExporter]

Here is the entire log..: 
2010-07-09 03:59:24,526 [  DEBUG] [     net.py  439] connection request from 
bluetooth client
2010-07-09 03:59:24,527 [  DEBUG] [     net.py  441] connection request accepted
2010-07-09 03:59:24,527 [  DEBUG] [     net.py  117] send 'hello' to 
('00:26:5D:B2:A4:CB', 1)
2010-07-09 03:59:24,527 [  DEBUG] [     net.py  277] try to send 9 bytes to 
('00:26:5D:B2:A4:CB', 1)
2010-07-09 03:59:24,527 [  DEBUG] [     net.py  286] sent 9 bytes
2010-07-09 03:59:25,223 [  DEBUG] [     net.py  167] data from client 
('00:26:5D:B2:A4:CB', 1) available
2010-07-09 03:59:25,223 [  DEBUG] [     net.py  138] try to receive 6 bytes
2010-07-09 03:59:25,224 [  DEBUG] [     net.py  151] received 1 bytes
2010-07-09 03:59:25,225 [  DEBUG] [     net.py  167] data from client 
('00:26:5D:B2:A4:CB', 1) available
2010-07-09 03:59:25,225 [  DEBUG] [     net.py  138] try to receive 5 bytes
2010-07-09 03:59:25,225 [  DEBUG] [     net.py  151] received 1 bytes
2010-07-09 03:59:25,226 [  DEBUG] [     net.py  167] data from client 
('00:26:5D:B2:A4:CB', 1) available
2010-07-09 03:59:25,226 [  DEBUG] [     net.py  138] try to receive 4 bytes
2010-07-09 03:59:25,226 [  DEBUG] [     net.py  151] received 1 bytes
2010-07-09 03:59:25,227 [  DEBUG] [     net.py  167] data from client 
('00:26:5D:B2:A4:CB', 1) available
2010-07-09 03:59:25,227 [  DEBUG] [     net.py  138] try to receive 3 bytes
2010-07-09 03:59:25,227 [  DEBUG] [     net.py  151] received 1 bytes
2010-07-09 03:59:25,228 [  DEBUG] [     net.py  167] data from client 
('00:26:5D:B2:A4:CB', 1) available
2010-07-09 03:59:25,228 [  DEBUG] [     net.py  138] try to receive 2 bytes
2010-07-09 03:59:25,228 [  DEBUG] [     net.py  151] received 1 bytes
2010-07-09 03:59:25,229 [  DEBUG] [     net.py  167] data from client 
('00:26:5D:B2:A4:CB', 1) available
2010-07-09 03:59:25,229 [  DEBUG] [     net.py  138] try to receive 1 bytes
2010-07-09 03:59:25,229 [  DEBUG] [     net.py  151] received 1 bytes
2010-07-09 03:59:25,230 [  DEBUG] [     net.py  195] incoming msg: 120, 86B
2010-07-09 03:59:25,231 [  DEBUG] [     net.py  167] data from client 
('00:26:5D:B2:A4:CB', 1) available
2010-07-09 03:59:25,231 [  DEBUG] [     net.py  138] try to receive 86 bytes
2010-07-09 03:59:25,231 [  DEBUG] [     net.py  151] received 86 bytes
2010-07-09 03:59:25,231 [  DEBUG] [     net.py  216] incoming msg 
2010-07-09 03:59:25,232 [  DEBUG] [     net.py  234] received client info from 
('00:26:5D:B2:A4:CB', 1)
2010-07-09 03:59:25,232 [  DEBUG] [     net.py  246] sending player info to 
('00:26:5D:B2:A4:CB', 1)
2010-07-09 03:59:25,232 [  DEBUG] [     net.py  277] try to send 117 bytes to 
('00:26:5D:B2:A4:CB', 1)
2010-07-09 03:59:25,232 [  DEBUG] [     net.py  286] sent 117 bytes
2010-07-09 03:59:25,379 [  ERROR] [     net.py  260] connection to client 
('00:26:5D:B2:A4:CB', 1) broken
2010-07-09 03:59:25,379 [  DEBUG] [     net.py  364] disconnect 
('00:26:5D:B2:A4:CB', 1)

Original comment by jckeert...@gmail.com on 8 Jul 2010 at 10:30

[GoogleCodeExporter]

I don't think this is a problem inside Remuco. The error messages on the client 
and in the log you've posted simply catch IO errors from lower levels. That 
means the connections seems to get cut by your computer's Bluetooth stack, for 
whatever reason. If you have a chance to, you should try to use another 
Bluetooth dongle or another computer.

Original comment by obensonne@googlemail.com on 28 Jul 2010 at 7:38

• Added labels: Bluetooth, Device-Samsung-B2100

[GoogleCodeExporter]

I have the very same problem with a Samsung S3100/Ubuntu so that it may be 
something related to samsung rather than to the dongle

Original comment by jtl...@gmail.com on 4 Sep 2010 at 1:56

[GoogleCodeExporter]

Issue 102 is about another strange IO error. There users reported they could 
fix this problem by setting a fixed Bluetooth on your computer and on your 
phone (the Bluetooth section in the FAQ gives hints how to manually set 
Bluetooth channels: 
http://code.google.com/p/remuco/wiki/FAQ#Service_search_fails).

I guess some phones expect specific services at specific Bluetooth channels and 
they cut the connection in case there is unexpected service (like Remuco, which 
takes the first free channel number).

Please give some feedback in case the fixed channel workaround helps.

Original comment by obensonne@googlemail.com on 4 Sep 2010 at 10:02

[GoogleCodeExporter]

I fixed to a channel and i get this:
10-09-05 04:10:27,521 [  DEBUG] [     net.py  167] data from client 
('00:26:5D:B2:A4:CB', 1) available
2010-09-05 04:10:27,521 [  DEBUG] [     net.py  138] try to receive 86 bytes
2010-09-05 04:10:27,521 [  DEBUG] [     net.py  151] received 86 bytes
2010-09-05 04:10:27,521 [  DEBUG] [     net.py  216] incoming msg 
2010-09-05 04:10:27,521 [  DEBUG] [     net.py  234] received client info from 
('00:26:5D:B2:A4:CB', 1)
2010-09-05 04:10:27,521 [  DEBUG] [     net.py  246] sending player info to 
('00:26:5D:B2:A4:CB', 1)
2010-09-05 04:10:27,522 [  DEBUG] [     net.py  277] try to send 265 bytes to 
('00:26:5D:B2:A4:CB', 1)
2010-09-05 04:10:27,522 [  DEBUG] [     net.py  286] sent 265 bytes
2010-09-05 04:10:27,732 [  ERROR] [     net.py  260] connection to client 
('00:26:5D:B2:A4:CB', 1) broken
2010-09-05 04:10:27,732 [  DEBUG] [     net.py  364] disconnect 
('00:26:5D:B2:A4:CB', 1)

Maybe the phone does not allow 265 byte transmissions or maybe its too slow to 
accept it and remuco thinks the connection is broken?

Original comment by jckeert...@gmail.com on 4 Sep 2010 at 10:42

[GoogleCodeExporter]

2010-09-05 04:17:57,389 [  DEBUG] [     net.py  286] sent 9 bytes

Maybe our phones can accept only small quantities of data at a time? Maybe an 
option to set how much data at a time will help?

PS: I have no idea how remuco or bluetooth works, so forgive me if my guesses 
are insane :P

Original comment by jckeert...@gmail.com on 4 Sep 2010 at 10:49

[GoogleCodeExporter]

Hi,

I tried with several different values for the channel but it didn't help much. 
I tried 7,8 and 10. For 7 and 8, the error was the very same as before but the 
8th channel is marked in the phone as "serial", this is why i tried it!

For the 10th, it was not even able to send the hello message.

I found something that maybe interesting in the phone log: 

[BUG] unexpected value: null
 right after the connexion sock info and before
[CN] going down

btw, can you remind me where the log on the computer is please? thanks

Original comment by jtl...@gmail.com on 5 Sep 2010 at 11:02

[GoogleCodeExporter]

The line 

[BUG] unexpected value: null

is not linked to any connection related stuff and it is not a critical problem.

On the computer you'll find the log in ~/.cache/remuco

Original comment by obensonne@googlemail.com on 2 Oct 2010 at 8:54

[GoogleCodeExporter]

After a little fighting on Arch to get Remuco installed on Arch, I came across 
this problem when I try to connect with my Samsung SGH-G600 (could it be a 
Samsung-only issue?)

DEBUG log attached.

Original comment by xyem...@googlemail.com on 19 Oct 2010 at 1:57

Attachments:

• mpd.log

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I guess it's a problem on samsung's side :( thank you for making remuco =)

Original comment by jckeert...@gmail.com on 26 Nov 2010 at 9:28

[GoogleCodeExporter]

Original comment by obensonne@googlemail.com on 8 Dec 2010 at 8:41

• Changed state: Chatting

[GoogleCodeExporter]

Closing. I'm afraid I can't help here since it appears to be a device specific 
issue.

Original comment by obensonne@googlemail.com on 19 Jul 2011 at 8:14

• Changed state: Invalid