Bluetooth connecting/disconnecting- Android Samsung S2 LTE

[sakimano]

Anyone have this problem?

Basically the bluetooth worked perfectly with my BlackBerry Torch from the time I got the car until the time I changed out the phone (although I'd LOVE to change the ringer in the car...way too loud and an annoying ring) however when I switched to an Android phone this week, I started having trouble.

When I get in the car with the phone and start it up, the phone connects like normal with the normal loud BRRRING! noise. However the phone will disconnect after a couple of minutes. That comes with the DEE DOO! noise. It will then re-connect a few minutes later...and then disconnect. It's quite annoying as you can imagine as the connect/disconnect tones are loud, and on top of that mute your music for 5 seconds every time they happen.

So far I have tried changing all of my screen dim/batter saver etc. settings and nothing has worked. I also deleted the pair and re-paired. Twice. Nothing.

I had similar problems with my BlackBerry bold 9000 2 years ago on my B7 S4 (same bluetooth system), but an update of the phone's software solved the issue. I am running the Android 2.3.5 software (Gingerbread) on my phone, and ICS (4.0) is not yet available.

Anyone else had any similar problems with their Samsung S2? Or other Android phones? Anyone have any suggestions on what settings to adjust?

Samsung Galaxy Sii LTE 4G (a.k.a. skyrocket...a.k.a. 727)
Android 2.3.5 Gingerbread RUXKJ7
2008 Audi RS4 bluetooth

[PetrolDave]

What version phone module do you have in the car?

Some newer phones aren't properly supported by older phone modules.

[sakimano]

What version phone module do you have in the car?

Some newer phones aren't properly supported by older phone modules.

great question...how do I check?

[PetrolDave]

What version phone module do you have in the car?

Some newer phones aren't properly supported by older phone modules.

great question...how do I check?

Using VCDS.

[sakimano]

will do tonight, thanks.

[Jph]

Although I haven't experienced the same problem myself I would suggest that if the phone pairs up OK initially (and can make and receive calls) then it's likely to be a setting on the phone rather than the bluetooth module.

I would look at the power management setting on your phone - it's possible that if the phone has a power saving/battery manager function it will put the phone to sleep after a period of inactivity and the bluetooth pairing drops out. The phone then wakes up after a while (likely because it receives packet data via a 3G connection), the bluetooth function is restored and the phone reconnects with the car.

A good way to test if this is to plug the phone into a in-car power lead (thereby stopping the power manager kicking in and sending the phone to sleep) and see if the pairing holds up.

FWIW I have a Motorolla Atrix that never drops the bluetooth pairing.

Hope that helps.

[crispy]

I had an HTC on Android that did similar things. Pulling the battery out of the phone would fix it or a few days, then the issue would return. Sometimes it would be ok for a couple weeks, but at some point it would return to the connect / disconnect sequence until the phone battery was removed. (powering the phone off with the button didn't fix it)

Now on a Galaxy Sii, again with Android,and I've not had any problems.

Mrs Crispy's iPhone never had an issue either, so just put it down to some phone error.

The volume of the connect/disconnect sound can be changed

[AdrianD]

I have a Galaxy S2 which works perfectly... I would start by disabling the power save options on the phone..

[sakimano]

Although I haven't experienced the same problem myself I would suggest that if the phone pairs up OK initially (and can make and receive calls) then it's likely to be a setting on the phone rather than the bluetooth module.

I would look at the power management setting on your phone - it's possible that if the phone has a power saving/battery manager function it will put the phone to sleep after a period of inactivity and the bluetooth pairing drops out. The phone then wakes up after a while (likely because it receives packet data via a 3G connection), the bluetooth function is restored and the phone reconnects with the car.

A good way to test if this is to plug the phone into a in-car power lead (thereby stopping the power manager kicking in and sending the phone to sleep) and see if the pairing holds up.

FWIW I have a Motorolla Atrix that never drops the bluetooth pairing.

Hope that helps.

Great input. Similar to my thoughts, but being on android for only 4 days so far, I fear I am missing something. I should say that I've dug through every battery/power saver type setting I can find and can't seem to root it out.

Today at lunch I tested it. First time stayed connected for 5 minutes. Then it took 3minutes. Then it took 1 minute. Then it ook 1 minute again. Then it took 3 minutes. Then it took 4 minutes. Then it took 1 minute.

Seems entirely random.

I had an HTC on Android that did similar things. Pulling the battery out of the phone would fix it or a few days, then the issue would return. Sometimes it would be ok for a couple weeks, but at some point it would return to the connect / disconnect sequence until the phone battery was removed. (powering the phone off with the button didn't fix it)

Now on a Galaxy Sii, again with Android,and I've not had any problems.

Mrs Crispy's iPhone never had an issue either, so just put it down to some phone error.

The volume of the connect/disconnect sound can be changed

thanks for the tip. I'll give it a go.

With respect to the volume control, is it basically the same volume as your phone volume? thus you can adjust the volume while in a call? I know the ringer volume is at whatever your last call ended at. So to prevent cardiac arrest induced by the ring, I always try to remember to turn the call volume down as low as possible when I'm getting off the phone. Invariably I forget, but only after a call with a low-talker when I've cranked the volume up to hear them.

I have a Galaxy S2 which works perfectly... I would start by disabling the power save options on the phone..

I thought I had. Can you let me know exactly what you mean? I'll post screen caps of what I've done...

[pDkALO]

Unfortunately you may not get anywhere with this - we had the EXACT same problem with a Samsung handset a year ago, and that was on a new 2011 car with latest RNE-e and Bluetooth. All the settings checked out, it was properly paired up and then every few minutes or so it would just disconnect all by itself, then reconnect, then repeat the process 'til it drove us mad with the constant ding-dong tones!!...

I raised it with the dealer and they investigated and found it was a compatibility issue with the handset, and there was no software update to fix it. Sounds like some Samsungs may still be causing problems. Irritatingly we had the same issue with the same phone on our Porsche with PCM, so it's not just Audi.

You may be lucky though and find a fix - good luck.

[sakimano]

Unfortunately you may not get anywhere with this - we had the EXACT same problem with a Samsung handset a year ago, and that was on a new 2011 car with latest RNE-e and Bluetooth. All the settings checked out, it was properly paired up and then every few minutes or so it would just disconnect all by itself, then reconnect, then repeat the process 'til it drove us mad with the constant ding-dong tones!!...

I raised it with the dealer and they investigated and found it was a compatibility issue with the handset, and there was no software update to fix it. Sounds like some Samsungs may still be causing problems. Irritatingly we had the same issue with the same phone on our Porsche with PCM, so it's not just Audi.

You may be lucky though and find a fix - good luck.

thanks...I think lol

Hopefully I can get it sorted. Maybe a new operating system for the phone will help. The Android 4.0 Ice Cream Sandwich setup is just about ready for the S2.

Did you change to different phones?

[pDkALO]

Did you change to different phones?

Yup - it was my wife's phone and she's now changed to an iPhone that works perfectly

[sakimano]

Did you change to different phones?

Yup - it was my wife's phone and she's now changed to an iPhone that works perfectly

I may be purchasing a Samsung Note (not because of this) so hopefully that solves things.

[PetrolDave]

I raised it with the dealer and they investigated and found it was a compatibility issue with the handset, and there was no software update to fix it.

As I've said many times before, because Bluetooth is a self-certified standard this type of compatibility problem is almost guaranteed - and since both the handset and hands-free manufacturers can claim compliance with the Bluetooth standard nobody wants to spend the time & money to fix it.

Yet more proof that shared responsibility = no responsibility.

[sakimano]

I am pleased to report that the phone now works flawlessly with my Audi's bluetooth.

The solution? Ice Cream Sandwich / 4.0, the latest operating system available for my phone.

I upgraded the phone to ICS, and it immediately began co-operating with the bluetooth.