I'm using bluez-libs-2.7 and bluez-utils-2.7 to develop a GPS system that communicates via bluetooth. I use the RFCOMM and the connection and disconnection works fine but the transmission gets stalled in about ten minutes. Both sides indicate that they are still connected, but in the GPS side, the process that writes in the rfcomm device (/dev/bluetooth/rfcomm/0) stops on a blocking write call:

write(fdbluetooth,s,strlen(s));

I open the rfcomm device this way:

fdbluetooth= open("/dev/bluetooth/rfcomm/0",O_RDWR | O_NOCTTY);

That write call works fine for a while until the communication gets stalled.

Is a bad implementation of the process that writes in the rfcomm device?

Is that issue solved in the 2.8 version of bluez?

Carlos AM
Naxus Conectividad Móvil