Comment 26 for bug 1500242

Hi,

We will try to resolve this issue, hopefully, in the coming days/weeks or get
closer to understanding the root cause. However before we start I would like you
to retest again because we have made a significant change recently with updating
the BlueZ version to 5.37 as well as we might have a fix for the Audi issue
already. If you could be so kind to give it a spin and report back on what is
happening that would be awesome.

Prerequisities:

1. Update the phone

The latest rc-proposed would be a good choice as we are pushing good stuff into
it. Make sure that the phone runs bluez 5.37 by executing:

$ dpkg -l bluez

2. Install the silo with the possible Audi fix (see comments below)

I saw that you were able to install to rc-proposed on your own therefore I
suggest trying the silo too. However if you feel uncertain about this just skip
it as eventually whatever is in silos finds it's way to rc-proposed quite fast.

In order to install a silo you need to install phablet-tools package on your
Ubuntu running computer. The PPA is here:
https://launchpad.net/~phablet-team/+archive/ubuntu/tools

Installing a silo is done by executing command

$ citrain device-upgrade <silo-number> <pin-code>

where the silo-number indicates the silo which you would like to install and the
pin code indicates the four-digit code that you use to unlock the phone [it
happens to be the user password too]. So for this silo you need to run:

$ citrain device-upgrade 67 <your-pin>

The citrain tool will install everything for you and reboot the phone.

Testing:

I would like you to try these scenarios again with both Audi and Jabra. If you
observe that if still is buggy then please capture the logas as you did
previously.

Let me know if there is anything that I could clarify more regarding updating
and such.

Thanks,
Konrad