Hi Luiz,

 >> I agree. Going to fix, and send a patch to BlueZ to add that label.
>
> While at it you might consider actually handling the Release because
> right now oFono doesn't react to either org.bluez disappearing nor
> adapter proxy being removed so if one of those events happen without
> calling RequestDisconnection oFono will keep the connection.
>

As long as BlueZ calls shutdown() on the socket, the resources will be 
cleaned up by the oFono HUP handler.

> Before anyone asks, there is another difference between Release and
> RequestDisconnection, the former should cause a forceful disconnect if
> connected while the latter should disconnect gracefully so bluetoothd
> will wait for the response so in theory Release can happen without
> RequestDisconnection being called before.
>

The only time BlueZ calls Release() today is when gracefully shutting 
down.  It calls shutdown() then anyway.

It might be argued that we should shut down the SCO server socket if 
BlueZ has called Release() on our profile.  Looking at the code, it 
looks like we only accept SCO connections when a given 
handsfree_audio_card matches a connection request.  So assuming the 
kernel has SCO defer setup handling, we should be okay with the current 
behavior.  Comments?

Regards,
-Denis