Unable to connect (timeout while waiting for hello) on Samsung Delphi (B3410)

[GoogleCodeExporter]

What is your environment?
* OS: Linux
* Remuco version: 0.9.2
* Client device: Samsung Delphi (B3410)
* Player: mpd

What steps will reproduce the problem?
I'm trying to connect with my phone .

What is the expected behavior? What happens instead?

Phone says "Timeout wihle waiting fo hello message"

In the phone logs stand:
[CN] not enough data for hello msg (need 9B, only -1B avilable)

But computer says that:
2010-05-29 00:04:20,925 [  DEBUG] [     net.py  425] connection request
accepted
2010-05-29 00:04:20,926 [  DEBUG] [     net.py  115] send 'hello' to
('C8:7E:75:E7:6F:4E', 8)
2010-05-29 00:04:20,926 [  DEBUG] [     net.py  265] try to send 9 bytes to
('C8:7E:75:E7:6F:4E', 8)
2010-05-29 00:04:20,927 [  DEBUG] [     net.py  274] sent 9 bytes
2010-05-29 00:04:23,283 [  ERROR] [     net.py  248] connection to client
('C8:7E:75:E7:6F:4E', 8) broken
2010-05-29 00:04:23,283 [  DEBUG] [     net.py  348] disconnect
('C8:7E:75:E7:6F:4E', 8)

Additional information:

Original issue reported on code.google.com by mitrandi...@gmail.com on 28 May 2010 at 10:04

[GoogleCodeExporter]

Not really a bug, this is an "expected" error.

Possible reasons:
- weak connection between phone and computer (BT/WiFi - what do you use?)
- the log says 9 bytes sent, but if they really travel over the air actually is 
not 
known .. the tool hcidump might help here to analyze this
- security restrictions on the phone (though unlikely, as the connection at 
least has 
been initialized)

Sorry, I cannot give you more precise hints. If you manage to fix it, please 
let us 
know how!

Oben

Original comment by obensonne@googlemail.com on 4 Jun 2010 at 6:53

• Changed state: Chatting
• Added labels: Component-Client, Device-Samsung-Delphi, Type-Support
• Removed labels: Type-Bug

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm using bluetooth - connection is OK: I can transfer files and do other things
without any problem.
I'm attaching the hcidump (if anybody can understand it^^)

Original comment by mitrandi...@gmail.com on 5 Jun 2010 at 11:08

Attachments:

• hcilog

[GoogleCodeExporter]

Well, I don't speak hcidump too, but you have a motivation to learn it ;)

Anyway, the problem is not inside Remuco. Looks like an unlucky combination of 
phone, 
Bluetooth device and ... whatever. I'm afraid I cannot help here much.

Just a guess: Have you tried using an authenticated Bluetooth connection (you 
can set 
this in the client when editing or creating  Bluetooth connection)?

Original comment by obensonne@googlemail.com on 5 Jun 2010 at 8:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hello,

If only remuco-vlc is started, the phone don't display VLC.
But, if I launch remuco-mplayer in parallel, the phone lists the 2 media 
players, I can select one but "Timeout wihle waiting fo hello message" is 
displayed, for both.

I'm disappointed :-(

I've used all option, but none works.
An idea ?

Bye
Gabriel

Original comment by gabriel....@gmail.com on 7 Jul 2010 at 4:55

[GoogleCodeExporter]

Note that VLC is only acive/listed on the phone if VLC itself is running. 
Otherwise remuco-vlc is running and watching for VLC to get started but it is 
not active.

I can think of 2 possible reasons why this fails:

1) The phone's Bluetooth is unbelievable slow (at least when setting up a 
connection). You could increase the timeout in the client source at 
http://code.google.com/p/remuco/source/browse/client/common/src/remuco/client/co
mmon/io/Connection.java#90 and then build your own client (see BleedingEdge and 
ClientCustomization).

2) The phone's Java implementation is a mess and some IO methods don't work as 
expected. To check/fix this you need to build your own client too. In the 
client source comment out the lines 
http://code.google.com/p/remuco/source/browse/client/common/src/remuco/client/co
mmon/io/Connection.java#501 to 
http://code.google.com/p/remuco/source/browse/client/common/src/remuco/client/co
mmon/io/Connection.java#527 (comment out: prefix lines with '//'). Build a 
custom client as mentioned above.

Maybe this helps.

Oben

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

[GoogleCodeExporter]

I observed the same error message as the TS: "Timeout while waiting for the 
hello message". Changing the timeout and commenting out the hello response (as 
per comment 7) did not resolve the error. However, I managed to get rid of it 
by manually setting the bluetooth channel in ~/.config/remuco/remuco.cfg and on 
the client. After this it works like a charm!

Martijn

Remuco version: 0.9.3
Client device: Nokia 6300 (7.21)
Player: Amarok

Original comment by psike...@gmail.com on 7 Aug 2010 at 6:34

[GoogleCodeExporter]

Thanks for documenting your work around. Which channel number did you use?

Original comment by obensonne@googlemail.com on 10 Aug 2010 at 1:09

[GoogleCodeExporter]

The same thing with my Nokia 5700. After I have set bluetooth channel manually 
(I have chosen channel 3) everything works. I suppose it should be mentioned in 
the FAQ.

Original comment by ivparamo...@gmail.com on 4 Sep 2010 at 1:33

[GoogleCodeExporter]

Added a note in the FAQ. Closing this issue. Open a new one, if you still 
experience this problem though you've tried manual Bluetooth channels.

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

• Changed state: Done
• Added labels: Bluetooth

[GoogleCodeExporter]

Original comment by obensonne@googlemail.com on 8 Mar 2011 at 6:38

• Added labels: Component-MIDP
• Removed labels: Component-Client