Motorola K1: Resume to remuco-client fail with IO error

[GoogleCodeExporter]

What is your environment?
* OS: Gentoo Linux
* Remuco version: 0.9.5
* Client device: Motorola K1 (new special client from hg)
* Player: remuco-mpd

What steps will reproduce the problem?
1. Start remuco client on Motorola K1 and connect to remuco-server
2. Let remuco-client go to the background (e.g. by closing the cover)
3. Resume to remuco-client

What is the expected behavior? What happens instead?
I can resume and control the remuco server.
But I get an "IO Error while sending data (write error: -1: errno=-1). 
Reconnect? 
And reconnect does not work: "IO Error while setting up the connection 
(errno=-1) 
(Restart of remuco-client does not work, too, with same message)
Even on exit remuco-client, the bluetooth connection will not be disconnect. 
I have to disable bluetooth in the mobile phone settings and enable it again. 
Sometimes I have to restart the phone. Then I can reconnect to the server.

Additional information:

Original issue reported on code.google.com by jbuec...@gmail.com on 11 Sep 2011 at 3:11

[GoogleCodeExporter]

Hm, looks like an issue in the K1's JSR-82 (Java-Bluetooth) implementation. 
Unfortunately I don't know of a way to work around this. AFAIK within Java it 
is not possible to reset or restart Bluetooth.

You say there's also no Bluetooth disconnect when exiting the client. In any 
case or only when you suspend/resume the client before?

Original comment by obensonne@googlemail.com on 11 Sep 2011 at 7:02

• Changed state: Chatting
• Added labels: Bluetooth, Component-MIDP, Device-Motorola-K1

[GoogleCodeExporter]

Original comment by obensonne@googlemail.com on 11 Sep 2011 at 7:03

• Added labels: Device-Motorola-KRZR-K1
• Removed labels: Device-Motorola-K1

[GoogleCodeExporter]

>You say there's also no Bluetooth disconnect when exiting the client. 
>In any case or only when you suspend/resume the client before?

The usual exit works. My described case was after suspend/resume.

Is there a forum or IRC or something to discuss about thinks or questions 
instead of this bugzilla?

Original comment by jbuec...@gmail.com on 11 Sep 2011 at 9:28

[GoogleCodeExporter]

Found a new workaround that could be interesting:
Reproduced the problem as described above. But now I did restart the remuco mpd 
adapter (and I do not restart bluetooth on the phone as described above).
After that I can establish a new connection (between player adapter and client, 
the bluetooth connection was established the hole time).

Original comment by jbuec...@gmail.com on 9 Apr 2012 at 4:32