On Thu, Feb 23, 2012 at 11:20 PM, Denis Kenzior <denkenz(a)gmail.com> wrote:
On 02/23/2012 06:49 PM, Mike wrote:
> I'm getting weird behaviour from an LG VX8360, connected via bluetooth
> HFP. When the phone connects, I see a CallAdded signal go out over
> dbus, despite there being no call on the phone itself. You can see
> the signal below. The LineIdentification held the actual phone number
> of the phone, but I replaced it with "xxxxxxxxxx". I also copied in
> the initial RFCOMM communication. It looks to me like this phone does
> not comply with the HFP spec in that it returns an answer to AT+CLCC
> when there is no phone call present (and at that, an index of 0). It
> also happens that the status is a 6, which does not appear to be a
> valid status in HFPv1.5. This just happens to map to the enum
> CALL_STATUS_DISCONNECTED, but I'm guessing this was merely
> coincidence. Since the state is broadcast as disconnected, I can
> simply ignore it in my GUI application. However, I'm wondering if
> this is something that is better handled in the ofono side?
Try the following patch.
I'm told the patch worked. I don't have direct access to this phone
to know exactly what that means, but the issue of incorrectly
reporting a phonecall the moment the phone connects is solved. I'm
still seeking an answer to whether or not actual phonecalls work.