We have moved to a new Sailfish OS Forum. Please start new discussions there.
16

[Bug 2.0.4] Outgoing call hangs on carkit

Tracked by Jolla (In release)

asked 2016-10-07 21:27:10 +0300

hoschi gravatar image

updated 2016-10-18 12:44:04 +0300

Hello! Since 2.0.4 an outgoing call on my carkit doesn't indicate ringing via the loudspeaker, the display indicates still calling even after connection is picked up and the loudspeaker doesn't turn on after the call is picked up. Roundabout one minute after the call is picked up by the called party, the call is shown as established and the loudspeaker (of the car) is turned on.
The other party can here me as soon as they pick up, I cannot recognize that. Therefore they hear me for one minute, while I'm still waiting for one minute.

I think this is a major regression. My carkit is a Fiscon in an Audi A4 (2008) and worked flawlessly till 2.0.4. I suspect the bluetooth audio improvements. It is embarassing that others can here me for one minute, while I'm not. My local pizza-service is hopefully not to angry on me, I called them three times till I figured what's ongoing.

Step by step description:

  1. Initiate call via bluetooth-integration of the car
  2. Call is shown as ringing on the car-display -> Regression, no ringing sound
  3. Call is now picked-up/accepted by called party after some random time
  4. Car-Display indicates still ringing, microphone is turned on but not the loudspeaker -> Regression, not indication of accepted call, other party can here me while I'm not
  5. Around one minute later the call is shown accepted on the car display

// edit
Possible fixes included in 2.04.14. These are new, the others where previously part of 2.04.13:

  • Binaries removed : bluez-gstreamer
  • [packaging] Point upstream submodule to Mer project mirror.
  • [bluez] Send reply when using agent to initiate voicecall.
edit retag flag offensive close delete

Comments

My car kit Nokia CK-100 also worked flawlessly before 2.0.4, but now I can no longer transfer the call away from car kit when exiting the car - headphones button in call app does nothing and audio remains in kit until bluetooth timeouts in a minute or so.

twi42 ( 2016-10-08 11:25:06 +0300 )edit
1

Hei,

I can confirm this last one with my 2010 Toyota Prius.

I cannot transfer the call between the car and the phone. I would also add that I even cannot initiate a call from the carkit. Half a ring and the connection is dropped with a message on the carkit to check the phone. I can, however; start a call from the phone while connected to the car.

LVPVS over.

LVPVS ( 2016-10-08 22:58:35 +0300 )edit

I have a plantronics WK 742 and it worked flawlessly until the update yesterday. Now the audio is on the phone despite the fact that the headset is connected. Then I renewed the pairing and rebooted the phone. On bootup, the phone asked about whether it should activate the HPF connection. Now I can listen to music, but the audio stream is seriously broken and gets very choppy from time to time. When calling, the phone defaults still to the internal speaker. Tapping the headset now transfers, but also with very choppy sound. I have also a Jabra headset that supports HSP, A2DP, AVRCP, HFP, DID and that works flawlessly. So IMHO, something went wrong on the HPF profile. Both setups worked flawlessly before the upgrade to 2.0.4.13 Fiskarsinjoki

Flight406 ( 2016-10-10 13:56:49 +0300 )edit

sorry, this isn't an answer, I pushed the wrong button

Flight406 ( 2016-10-10 13:57:34 +0300 )edit

Thanks, even if it doesn't is an answer we collect information for the developers. Sounds similiar to my exerience, but my testing is limited (I need vicitim for calling...).

hoschi ( 2016-10-10 14:05:55 +0300 )edit

2 Answers

Sort by » oldest newest most voted
2

answered 2016-10-20 08:43:15 +0300

jovirkku gravatar image

This issue should be fixed in 2.0.4.14. Please test in your car.

edit flag offensive delete publish link more

Comments

I have tested this today calling (and being called) and everything seems to work. Thank you!
By the way, if I'm called in the car my car's loudspeaker plays it's regular built-in ringtone and now also my phone rings with it's jolla-ringtone (+vibration). I don't think this is a bad behaviour, because Sailfish cannot transfer it's ringtone to a carkit (as for now).

hoschi ( 2016-10-20 20:48:11 +0300 )edit

I can confirm that latest (2.0.4.14) update works again in my car (on a dension bt lite) with Jolla C. I had to update firmware on the carkit device and after pairing the connection type was headset - I manually changed in the settings to 'car kit'.

kapcsandi ( 2016-10-23 19:15:35 +0300 )edit

Can confirm issue is resolved with my Original Jolla

GD ( 2016-10-24 08:11:02 +0300 )edit

Kia Sportage SL (3): carkit looks broken with update from 2.0.2 to 2.0.4.14. Audio system hangs up, loudspeakers and microphone do not work during phone call.I kindly ask to revert those improvements in Bluetooth subsystem. Now it's just unsafe to use the phone in a car - it behaves unexpectedly all the time :( It was good enough in 2.0.2.

Valerij ( 2016-10-25 23:25:45 +0300 )edit

Probably another problem? Does it work if you are the called party? It always worked for me, if I received the call.

hoschi ( 2016-10-26 00:11:43 +0300 )edit
1

answered 2016-10-27 15:03:14 +0300

jovirkku gravatar image

The fix for this issue was delivered in update 2.0.4.14.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
4 followers

Stats

Asked: 2016-10-07 21:27:10 +0300

Seen: 714 times

Last updated: Oct 27 '16