[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

This bug was fixed in the package ubuntu-system-settings - 0.3+16.10.20160523-0ubuntu1 --- ubuntu-system-settings (0.3+16.10.20160523-0ubuntu1) yakkety; urgency=medium * Catch connection errors asynchronously -- Ken VanDine Mon, 23 May 2016 12:27:38

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: telephony-service (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth,

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: canonical-devices-system-image Milestone: ww08-2016 => 11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: ofono (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Branch linked: lp:~tiagosh/messaging-app/remove-gsettings ** Branch linked: lp:~tiagosh/telephony-service/default-sim-for-calls ** Branch linked: lp:~tiagosh/telepathy-ofono/use-accounts-service -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed => In Progress ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu.

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Branch linked: lp:~ken-vandine/ubuntu-system-settings/default_sim_as -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

If this will take a while, then would it be possible to have ofono default to a deterministic SIM for outbound calls as an interim workaround? Eg. sort them by some key and take the lowest one, or use the lowest numbered port or something. Then I could swap the SIM cards around (if needed) to get

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

Yes, this is still an issue. We agreed with Alfonso that ofono will use AccountsService to get the default sim card for calls. It needs some work on telephony-service and system-settings. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

We need to get to the bottom of this one guys. What is the latest status? Users are still reporting the issue even though we've moved to Bluez5, so there is a still an issue. ** Changed in: canonical-devices-system-image Milestone: backlog => ww08-2016 ** Changed in: telephony-service

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

Today I found out that outgoing calls on the bluetooth enabled Toyota Touch system went out through sim2, although I have selected sim1 as the default for outgoing calls. $ system-image-cli --info current build number: 29 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

@Uranicus Thanks for the heads-up re: battery status. The plugin that handles battery status currently doesn't properly handle dual-SIM. It's on our list to resolve before OTA9 is released. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

Knowing that this bug is in progress, I want to share an interesting finding (at least for me). I am on rc-proposed (with bluez5, see details below). When SIM 1 is (randomly picked) used, the battery status is shown in the car display. When SIM 2 is used, the battery status shows 100% loading.

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: bluez (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0,

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu.

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: canonical-devices-system-image Milestone: None => backlog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Tags added: after-bluez5 bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: telephony-service (Ubuntu RTM) Status: Confirmed = Triaged ** Changed in: telephony-service (Ubuntu) Status: Confirmed = Triaged ** Changed in: ofono (Ubuntu) Status: Confirmed = Triaged ** Changed in: bluez (Ubuntu) Status: Confirmed = Triaged --

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

** Changed in: bluez (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

I agree, lets fix this when we move to bluez5, so I propose to defer this bug until then. ** Changed in: canonical-devices-system-image Milestone: ww34-2015 = None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu.

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

As a matter of fact I will also add that the slot chosen to start a call is kind of random and can change after a reboot. It would be possible to fix it in the code as a quick work around to have as a minimum a deterministic behaviour. -- You received this bug notification because you are a

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

Some research shows that audio/telephony-ofono.c in BlueZ 4 source tree only accounts for one modem in the system. Currently there is no way to specify a preferred modem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu.

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

Actually, the call is started by a Dial DBus call to an ofono modem started from bluetoothd. Currently we are not using ofono's HFP implementation, but the BlueZ one. This will change when we move from BlueZ 4 to BlueZ 5. But for the moment the one which chooses the modem to use is BlueZ. ** Also