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

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-06-13 23:32:53 +0200

Bluetooth problems w/ standard Renault carkit + workaround [1.0.7.16]

Hello there,

As I've mentioned in a comment to a similar issue (after update: carkit (bluetooth) not working) the last update completely broke the Bluetooth connection between my carkit and my Jolla.

The issue is mainly reflected in inability to pair after the update and it is a regression as it worked perfectly before. When you go on your carkit to Settings / Bluetooth settings and select a slot you want to use with your Jolla, you are given two options for pairing: 'Pair with a phone' and 'Pair with an audio device' (or something along those lines, didn't write down the exact wording).

If you go for 'Pair with a phone', the carkit generates a new temporary pin and asks you to start the pairing process from your Jolla and to enter the displayed PIN. As soon as you initiate pairing on Jolla, before you even get the chance to enter the PIN, the carkit breaks the connection with 'Connection has failed...' message. You may continue the 'pairing' process on your Jolla but your device won't be listed on the carkit and if you attempt to do another pairing you'll get a different pin making the pairing impossible to establish.

If you go for 'Pair with an audio device' the carkit will ask you to start the pairing process from Jolla and as soon as you do that it will switch to a PIN entry screen where you are supposed to enter the PIN you've set on your Jolla, but in the mean time your Jolla will be displaying 'Connecting...' circle without giving you the chance to enter the PIN. If you cancel the process on your carkit (or enter any bogus PIN), the carkit will again display 'Connection has failed...' but your Jolla will switch to PIN entry just as in the above case, making it again impossible to pair.

The carkit in question is the standard Bluetooth Radio/Sat kit (identified as My_Radiosat) that comes with Renault Megane/Laguna (and possibly newer Clios as well) since 2009, and mine has a software version: 91.14, if that's of any help to somebody trying to figure out what the issue exactly is. If the dev team is willing to look into this issue I can provide any logs needed.

In addition (perhaps an unrelated issue but it only happened while I was trying the above scenarios), during this process, the Jolla will arbitrary decide to shut down itself in a particularly curious manner - it will shut down, then run in the charging mode (displays the USB cable on the screen) as if it was turned off and then plugged into a charger - but it wasn't. It wasn't connected to anything. Holding the power key will turn it on again as if nothing has happened (except all the previously open apps will, obviously, be closed). This happened to me several times on my previous attempts at pairing - today it didn't occur, perhaps it has to do something with connman as I'm now running the connman 1.23 hotfix?

Any help or guides with the issue is appreciated as, from what I've gathered, it's not only the standard Renault carkit that is experiencing Bluetooth (pairing) issues after the last update?

I'll leave this as an issue/question in hope we'll get an official solution to the described problem, and I'll post what you can try as a workaround given that I somehow managed to get them to pair today.

Bluetooth problems w/ standard Renault carkit + workaround [1.0.7.16]

Hello there,

As I've mentioned in a comment to a similar issue (after update: carkit (bluetooth) not working) the last update completely broke the Bluetooth connection between my carkit and my Jolla.

The issue is mainly reflected in inability to pair after the update and it is a regression as it worked perfectly before. When you go on your carkit to Settings / Bluetooth settings and select a slot you want to use with your Jolla, you are given two options for pairing: 'Pair with a phone' and 'Pair with an audio device' (or something along those lines, didn't write down the exact wording).

If you go for 'Pair with a phone', the carkit generates a new temporary pin PIN and asks you to start the pairing process from your Jolla Jolla, and to enter the displayed PIN. PIN there. As soon as you initiate pairing on Jolla, before you even get the chance to enter the PIN, the carkit breaks the connection with 'Connection has failed...' message. You may continue the 'pairing' pairing process on your Jolla but your device won't be listed on the carkit and if you attempt to do another pairing you'll get a different pin PIN making the pairing impossible to establish.

If you go for 'Pair with an audio device' the carkit will ask you to start the pairing process from Jolla and as soon as you do that it will switch to a PIN entry screen where you are supposed to enter the PIN you've set on your Jolla, but in the mean time your Jolla will be displaying 'Connecting...' circle without giving you the chance to enter the PIN. If you cancel the process on your carkit (or enter any bogus PIN), the carkit will again display 'Connection has failed...' but your Jolla will switch to PIN entry just as in the above case, making it again impossible to pair.

The carkit in question is the standard Bluetooth Radio/Sat Radiosat kit (identified as My_Radiosat) (Radiosat Classic Bluetooth, Radiosat 3D Sound by Arkamys® Bluetooth or Bose® Sound System) that comes with Renault Megane/Laguna Scenic/Megane/Laguna (and possibly newer Clios as well) since 2009, 2009 - and mine has a software version: 91.14, if that's of any help to somebody trying to figure out what the issue exactly is. The same issue probably affects other Renault carkits (R-Link, R-Plug & Radio+, MediaNAV and Carminat TomTom as they all use the same Bluetooth module). If the dev team is willing to look into this issue I can provide any logs needed.

In addition (perhaps an unrelated issue but it only happened while I was trying the above scenarios), during this process, the Jolla will arbitrary decide to shut down itself in a particularly curious manner - it will shut down, then run in the charging mode (displays the USB cable on the screen) as if it was turned off and then plugged into a charger - but it wasn't. It wasn't connected to anything. Holding the power key will turn it on again as if nothing has happened (except all the previously open apps will, obviously, be closed). This happened to me several times on my previous attempts at pairing - today it didn't occur, perhaps it has to do something with connman as I'm now running the connman 1.23 hotfix?

Any help or guides with the issue is appreciated as, from what I've gathered, it's not only the standard Renault carkit that is experiencing Bluetooth (pairing) issues after the last update?

I'll leave this as an issue/question in hope we'll get an official solution to the described problem, and I'll post what you can try as a workaround given that I somehow managed to get them to pair today.

Bluetooth problems w/ standard Renault carkit + workaround [1.0.7.16]

Hello there,

As I've mentioned in a comment to a similar issue (after update: carkit (bluetooth) not working) the last update completely broke the Bluetooth connection between my carkit and my Jolla.

The issue is mainly reflected in inability to pair after the update and it is a regression as it worked perfectly before. When you go on your carkit to Settings / Bluetooth settings and select a slot you want to use with your Jolla, you are given two options for pairing: 'Pair phone' and 'Pair audio device' (or something along those lines, didn't write down the exact wording).

If you go for 'Pair phone', the carkit generates a new temporary PIN and asks you to start the pairing process from your Jolla, and to enter the displayed PIN there. As soon as you initiate pairing on Jolla, before you even get the chance to enter the PIN, the carkit breaks the connection with 'Connection has failed...' message. You may continue the pairing process on your Jolla but your device won't be listed on the carkit and if you attempt to do another pairing you'll get a different PIN making the pairing impossible to establish.

If you go for 'Pair audio device' the carkit will ask you to start the pairing process from Jolla and as soon as you do that it will switch to a PIN entry screen where you are supposed to enter the PIN you've set on your Jolla, but in the mean time your Jolla will be displaying 'Connecting...' circle without giving you the chance to enter the PIN. If you cancel the process on your carkit (or enter any bogus PIN), the carkit will again display 'Connection has failed...' but your Jolla will switch to PIN entry just as in the above case, making it again impossible to pair.

The carkit in question is the standard Bluetooth Radiosat kit (Radiosat Classic Bluetooth, Radiosat 3D Sound by Arkamys® Bluetooth or Bose® Sound System) that comes with Renault Scenic/Megane/Laguna (and possibly newer Clios as well) since 2009 - and mine has a software version: 91.14, if that's of any help to somebody trying to figure out what the issue exactly is. The same issue probably affects other Renault carkits (R-Link, R-Plug & Radio+, MediaNAV and Carminat TomTom TomTom) as they all use the same Bluetooth module). module. If the dev team is willing to look into this issue I can provide any logs needed.

In addition (perhaps an unrelated issue but it only happened while I was trying the above scenarios), during this process, the Jolla will arbitrary decide to shut down itself in a particularly curious manner - it will shut down, then run in the charging mode (displays the USB cable on the screen) as if it was turned off and then plugged into a charger - but it wasn't. It wasn't connected to anything. Holding the power key will turn it on again as if nothing has happened (except all the previously open apps will, obviously, be closed). This happened to me several times on my previous attempts at pairing - today it didn't occur, perhaps it has to do something with connman as I'm now running the connman 1.23 hotfix?

Any help or guides with the issue is appreciated as, from what I've gathered, it's not only the standard Renault carkit that is experiencing Bluetooth (pairing) issues after the last update?

I'll leave this as an issue/question in hope we'll get an official solution to the described problem, and I'll post what you can try as a workaround given that I somehow managed to get them to pair today.

Bluetooth problems w/ standard Renault carkit + workaround [1.0.7.16]

Hello there,

As I've mentioned in a comment to a similar issue (after update: carkit (bluetooth) not working) the last update completely broke the Bluetooth connection between my carkit and my Jolla.

The issue is mainly reflected in inability to pair after the update and it is a regression as it worked perfectly before. When you go on your carkit to Settings 'Settings / Bluetooth settings connection' and select a slot you want to use with your Jolla, you are given two options for pairing: 'Pair phone' and 'Pair audio device' (or something along those lines, didn't write down the exact wording).

If you go for 'Pair phone', the carkit generates a new temporary PIN and asks you to start the pairing process from your Jolla, and to enter the displayed PIN there. As soon as you initiate pairing on Jolla, before you even get the chance to enter the PIN, the carkit breaks the connection with 'Connection has failed...' message. You may continue the pairing process on your Jolla but your device won't be listed on the carkit and if you attempt to do another pairing you'll get a different PIN making the pairing impossible to establish.

If you go for 'Pair audio device' the carkit will ask you to start the pairing process from Jolla and as soon as you do that it will switch to a PIN entry screen where you are supposed to enter the PIN you've set on your Jolla, but in the mean time your Jolla will be displaying 'Connecting...' circle without giving you the chance to enter the PIN. If you cancel the process on your carkit (or enter any bogus PIN), the carkit will again display 'Connection has failed...' but your Jolla will switch to PIN entry just as in the above case, making it again impossible to pair.

The carkit in question is the standard Bluetooth Radiosat kit (Radiosat Classic Bluetooth, Radiosat 3D Sound by Arkamys® Bluetooth or Bose® Sound System) that comes with Renault Scenic/Megane/Laguna (and possibly newer Clios as well) since 2009 - and mine has a software version: 91.14, if that's of any help to somebody trying to figure out what the issue exactly is. The same issue probably affects other Renault carkits (R-Link, R-Plug & Radio+, MediaNAV and Carminat TomTom) as they all use the same Bluetooth module. If the dev team is willing to look into this issue I can provide any logs needed.

In addition (perhaps an unrelated issue but it only happened while I was trying the above scenarios), during this process, the Jolla will arbitrary decide to shut down itself in a particularly curious manner - it will shut down, then run in the charging mode (displays the USB cable on the screen) as if it was turned off and then plugged into a charger - but it wasn't. It wasn't connected to anything. Holding the power key will turn it on again as if nothing has happened (except all the previously open apps will, obviously, be closed). This happened to me several times on my previous attempts at pairing - today it didn't occur, perhaps it has to do something with connman as I'm now running the connman 1.23 hotfix?

Any help or guides with the issue is appreciated as, from what I've gathered, it's not only the standard Renault carkit that is experiencing Bluetooth (pairing) issues after the last update?

I'll leave this as an issue/question in hope we'll get an official solution to the described problem, and I'll post what you can try as a workaround given that I somehow managed to get them to pair today.

Bluetooth problems w/ standard Renault carkit + workaround [1.0.7.16]

Hello there,

As I've mentioned in a comment to a similar issue (after update: carkit (bluetooth) not working) the last update completely broke the Bluetooth connection between my carkit and my Jolla.

The issue is mainly reflected in inability to pair after the update and it is a regression as it worked perfectly before. When you go on your carkit to 'Settings / Bluetooth connection' and select a slot you want to use with your Jolla, you are given two options for pairing: 'Pair phone' and 'Pair audio device' (or something along those lines, didn't write down the exact wording).

If you go for 'Pair phone', the carkit generates a new temporary PIN and asks you to start the pairing process from your Jolla, and to enter the displayed PIN there. As soon as you initiate pairing on Jolla, before you even get the chance to enter the PIN, the carkit breaks the connection with 'Connection has failed...' message. You may continue the pairing process on your Jolla but your device won't be listed on the carkit and if you attempt to do another pairing you'll get a different PIN making the pairing impossible to establish.

If you go for 'Pair audio device' the carkit will ask you to start the pairing process from Jolla and as soon as you do that it will switch to a PIN entry screen where you are supposed to enter the PIN you've set on your Jolla, but in the mean time your Jolla will be displaying 'Connecting...' circle without giving you the chance to enter the PIN. If you cancel the process on your carkit (or enter any bogus PIN), the carkit will again display 'Connection has failed...' but your Jolla will switch to PIN entry just as in the above case, making it again impossible to pair.

The carkit in question is the standard Bluetooth Radiosat kit (Radiosat Classic Bluetooth, Radiosat 3D Sound by Arkamys® Bluetooth or Bose® Sound System) that comes with Renault Scenic/Megane/Laguna (and possibly newer Clios as well) since 2009 - and mine has a software version: 91.14, if that's of any help to somebody trying to figure out what the issue exactly is. The same issue probably affects other Renault carkits (R-Link, R-Plug & Radio+, MediaNAV and Carminat TomTom) as they all use the same Bluetooth module. If the dev team is willing to look into this issue I can provide any logs needed.

In addition (perhaps an unrelated issue but it only happened while I was trying the above scenarios), during this process, the Jolla will arbitrary decide to shut down itself in a particularly curious manner - it will shut down, then run in the charging mode (displays the USB cable on the screen) as if it was turned off and then plugged into a charger - but it wasn't. It wasn't connected to anything. Holding the power key will turn it on again as if nothing has happened (except all the previously open apps will, obviously, be closed). This happened to me several times on my previous attempts at pairing - today it didn't occur, perhaps it has to do something with connman as I'm now running the connman 1.23 hotfix?

Any help or guides with the issue is appreciated as, from what I've gathered, it's not only the standard Renault carkit that is experiencing Bluetooth (pairing) issues after the last update?

I'll leave this as an issue/question in hope we'll get an official solution to the described problem, and I'll post what you can try as a workaround given that I somehow managed to get them to pair today.

Bluetooth problems w/ standard Renault carkit + workaround [1.0.7.16]

Hello there,

As I've mentioned in a comment to a similar issue (after update: carkit (bluetooth) not working) the last update completely broke the Bluetooth connection between my carkit and my Jolla.

The issue is mainly reflected in inability to pair after the update and it is a regression as it worked perfectly before. When you go on your carkit to 'Settings / Bluetooth connection' and select a slot you want to use with your Jolla, you are given two options for pairing: 'Pair phone' and 'Pair audio device' (or something along those lines, didn't write down the exact wording).

If you go for 'Pair phone', the carkit generates a new temporary PIN and asks you to start the pairing process from your Jolla, and to enter the displayed PIN there. As soon as you initiate pairing on Jolla, before you even get the chance to enter the PIN, the carkit breaks the connection with 'Connection has failed...' message. You may continue the pairing process on your Jolla but your device won't be listed on the carkit and if you attempt to do another pairing you'll get a different PIN making the pairing impossible to establish.

If you go for 'Pair audio device' the carkit will ask you to start the pairing process from Jolla and as soon as you do that it will switch to a PIN entry screen where you are supposed to enter the PIN you've set on your Jolla, but in the mean time your Jolla will be displaying 'Connecting...' circle without giving you the chance to enter the PIN. If you cancel the process on your carkit (or enter any bogus PIN), the carkit will again display 'Connection has failed...' but your Jolla will switch to PIN entry just as in the above case, making it again impossible to pair.

The carkit in question is the standard Bluetooth Radiosat kit (Radiosat Classic Bluetooth, Radiosat 3D Sound by Arkamys® Bluetooth or Bose® Sound System) that comes with Renault Scenic/Megane/Laguna (and possibly newer Clios as well) since 2009 - and mine has a software version: 91.14, if that's of any help to somebody trying to figure out what the issue exactly is. The same issue probably affects other Renault carkits (R-Link, R-Plug & Radio+, MediaNAV and Carminat TomTom) as they all use the same Bluetooth module. If the dev team is willing to look into this issue I can provide any logs needed.

In addition (perhaps an unrelated issue but it only happened while I was trying the above scenarios), during this process, the Jolla will arbitrary decide to shut down itself in a particularly curious manner - it will shut down, then run in the charging mode (displays the USB cable on the screen) as if it was turned off and then plugged into a charger - but it wasn't. It wasn't connected to anything. Holding the power key will turn it on again as if nothing has happened (except all the previously open apps will, obviously, be closed). This happened to me several times on my previous attempts at pairing - today it didn't occur, perhaps it has to do something with connman as I'm now running the connman 1.23 hotfix?

Any help or guides with the issue is appreciated as, from what I've gathered, it's not only the standard Renault carkit that is experiencing Bluetooth (pairing) issues after the last update?

I'll leave this as an issue/question in hope we'll get an official solution to the described problem, and I'll post what you can try as a workaround given that I somehow managed to get them to pair today.

Bluetooth problems w/ standard Renault carkit + workaround [1.0.7.16]

Hello there,

As I've mentioned in a comment to a similar issue (after update: carkit (bluetooth) not working) the last update completely broke the Bluetooth connection between my carkit and my Jolla.

The issue is mainly reflected in inability to pair after the update and it is a regression as it worked perfectly before. When you go on your carkit to 'Settings / Bluetooth connection' and select a slot you want to use with your Jolla, you are given two options for pairing: 'Pair phone' and 'Pair audio device' (or something along those lines, didn't write down the exact wording).

If you go for 'Pair phone', the carkit generates a new temporary PIN and asks you to start the pairing process from your Jolla, and to enter the displayed PIN there. As soon as you initiate pairing on Jolla, before you even get the chance to enter the PIN, the carkit breaks the connection with 'Connection has failed...' message. You may continue the pairing process on your Jolla but your device won't be listed on the carkit and if you attempt to do another pairing you'll get a different PIN making the pairing impossible to establish.

If you go for 'Pair audio device' the carkit will ask you to start the pairing process from Jolla and as soon as you do that it will switch to a PIN entry screen where you are supposed to enter the PIN you've set on your Jolla, but in the mean time your Jolla will be displaying 'Connecting...' circle without giving you the chance to enter the PIN. If you cancel the process on your carkit (or enter any bogus PIN), the carkit will again display 'Connection has failed...' but your Jolla will switch to PIN entry just as in the above case, making it again impossible to pair.

The carkit in question is the standard Bluetooth Radiosat kit (Radiosat Classic Bluetooth, Radiosat 3D Sound by Arkamys® Bluetooth or Bose® Sound System) that comes with Renault Scenic/Megane/Laguna (and possibly newer Clios as well) since 2009 - and mine has a software version: 91.14, if that's of any help to somebody trying to figure out what the issue exactly is. The same issue probably affects other Renault carkits (R-Link, R-Plug & Radio+, MediaNAV and Carminat TomTom) as they all use the same Bluetooth module. If the dev team is willing to look into this issue I can provide any logs needed.

In addition (perhaps an unrelated issue but it only happened while I was trying the above scenarios), during this process, the Jolla will arbitrary decide to shut down itself in a particularly curious manner - it will shut down, then run in the charging mode (displays the USB cable on the screen) as if it was turned off and then plugged into a charger - but it wasn't. It wasn't connected to anything. Holding the power key will turn it on again as if nothing has happened (except all the previously open apps will, obviously, be closed). This happened to me several times on my previous attempts at pairing - today it didn't occur, perhaps it has to do something with connman as I'm now running the connman 1.23 hotfix?

Any help or guides with the issue is appreciated as, from what I've gathered, it's not only the standard Renault carkit that is experiencing Bluetooth (pairing) issues after the last update?

I'll leave this as an issue/question in hope we'll get an official solution to the described problem, and I'll post what you can try as a workaround given that I somehow managed to get them to pair today.

Bluetooth problems w/ standard Renault carkit + workaround [1.0.7.16]

Hello there,

As I've mentioned in a comment to a similar issue (after update: carkit (bluetooth) not working) the last update completely broke the Bluetooth connection between my carkit and my Jolla.

The issue is mainly reflected in inability to pair after the update and it is a regression as it worked perfectly before. When you go on your carkit to 'Settings / Bluetooth connection' and select a slot you want to use with your Jolla, you are given two options for pairing: 'Pair phone' and 'Pair audio device' (or something along those lines, didn't write down the exact wording).

If you go for 'Pair phone', the carkit generates a new temporary PIN and asks you to start the pairing process from your Jolla, and to enter the displayed PIN there. As soon as you initiate pairing on Jolla, before you even get the chance to enter the PIN, the carkit breaks the connection with 'Connection has failed...' message. You may continue the pairing process on your Jolla but your device won't be listed on the carkit and if you attempt to do another pairing you'll get a different PIN making the pairing impossible to establish.

If you go for 'Pair audio device' the carkit will ask you to start the pairing process from Jolla and as soon as you do that it will switch to a PIN entry screen where you are supposed to enter the PIN you've set on your Jolla, but in the mean time your Jolla will be displaying 'Connecting...' circle without giving you the chance to enter the PIN. If you cancel the process on your carkit (or enter any bogus PIN), the carkit will again display 'Connection has failed...' but your Jolla will switch to PIN entry just as in the above case, making it again impossible to pair.

The carkit in question is the standard Bluetooth Radiosat kit (Radiosat Classic Bluetooth, Radiosat 3D Sound by Arkamys® Bluetooth or Bose® Sound System) that comes with Renault Scenic/Megane/Laguna (and possibly newer Clios as well) since 2009 - and mine has a software version: 91.14, if that's of any help to somebody trying to figure out what the issue exactly is. The same issue probably affects other Renault carkits (R-Link, R-Plug & Radio+, MediaNAV and Carminat TomTom) as they all use the same Bluetooth module. If the dev team is willing to look into this issue I can provide any logs needed.

In addition (perhaps an unrelated issue but it only happened while I was trying the above scenarios), during this process, the Jolla will arbitrary decide to shut down itself in a particularly curious manner - it will shut down, then run in the charging mode (displays the USB cable on the screen) as if it was turned off and then plugged into a charger - but it wasn't. It wasn't connected to anything. Holding the power key will turn it on again as if nothing has happened (except all the previously open apps will, obviously, be closed). This happened to me several times on my previous attempts at pairing - today it didn't occur, perhaps it has to do something with connman as I'm now running the connman 1.23 hotfix?

update:

This weird shutdown issue happened just a few minutes ago but this time it didn't have to do anything with Bluetooth - I was happily surfing using Android's flavor of Firefox and it suddenly turned into 'charging while off' screen, again not connected to USB at that point. This time it was harder to get it out of that state as the power button wasn't responding initially, then a long press the screen turned off and the LED turned red, and again the power button wasn't responding for more than a minute. Eventually, after quite a few long press cycles on the power button, it turned on and everything went back to normal.

Perhaps I should report this as a separate issue...

end of update

Any help or guides with the issue is appreciated as, from what I've gathered, it's not only the standard Renault carkit that is experiencing Bluetooth (pairing) issues after the last update?

I'll leave this as an issue/question in hope we'll get an official solution to the described problem, and I'll post what you can try as a workaround given that I somehow managed to get them to pair today.