Telephonny service, modem not set

Description

When trying to connect a phone through bluetooth and make a call with phone application i got this error from agl-service-telephony:

 

ERROR: [API telephony] default modem not set

 

See the log of agl-service-telephony

Environment

None

Attachments

1
  • 17 Dec 2018, 10:45 PM

Activity

Thierry Bultel 
January 29, 2019 at 2:06 PM

Thierry Bultel 
December 18, 2018 at 9:05 AM

Matt,

you might be right, indeed.

Since this version of bluealsa uses RFCOMM for handling HFP directly, it might conflict with Ofono.

But it must be checked to be sure. Merging my 2 changes in the metas is enough for the test (bu it will break the bluetooth audio until the changes in hal-generic and softmixer are merged as well)

Matt Ranostay 
December 18, 2018 at 1:10 AM

I can also confirm if you disable bluealsa it works everytime, so something needs to be changed.

Matt Ranostay 
December 17, 2018 at 11:12 PM
(edited)

Pretty sure you need this changed merged https://gerrit.automotivelinux.org/gerrit/#/c/18723/

Clément Bénier 
December 17, 2018 at 10:43 PM
(edited)

I reopen it because it is quite unstable, when reboot, or when connect a new phone, modem is not set anymore,

 

on last master m3 with a bluetooth dongle:

  • first case

    • pair your phone

    • make a call it does not work

    • log: "modem not set"

  • seconde case

    • reboot m3

    • make a call, it does not call

    • log: "default modem not set"

  • for fixing it in both cases

    • uncheck then check call audio

    • restart agl service telephony

 

I attached you a telephony service log named 'telephonyreboot.log' where the procedure is:

  • phone is paired

  • reboot

  • launch phone app

  • try to make a call, it didn't

  • uncheck/check 'call audio' on phone

  • try to make a call, it didn't

  • restart agl telephony service

  • make a call, it does work

 

 

 

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Affects versions

Priority

Created December 7, 2018 at 4:48 PM
Updated February 12, 2019 at 1:44 AM
Resolved January 29, 2019 at 2:07 PM

Flag notifications