Database Info

[SOLVED]TMO One S Bluetooth disconnects every minute on Audi A3

I just got a One S last week, and everything worked great with my 2009 A3 until yesterday, when bluetooth started getting disconnected by itself literally every minute. After it cuts off it immediately reconnects, which would have been fine but the A3 makes a "ding" sound every time the phone is connected. I have tried to unpair and pair again and again, and to no avail.
Despite this issue, the connection is actually fine when in a call. It's only when it's idle. Also my Nexus S working fine with the car, and the phone works fine with my BT speakers....
Does anyone else have this problem? I'm going to call my local dealership and ask if they have any sort of update for the A3 since the One S is BT 4.0....
[SOLUTION/WORK AROUND]
Just unpair the phone, then when you pair it again, do not allow the car to access your contacts, and make sure to choose the "do not ask again" option. This is the only consistent solution I've seen so far.

Try to update software... Maybe there is the fix. Settings about phone system update
Sent from my HTC VLE_U using Tapatalk 2

I have the same issue with my One S, it will connect and disconnect from my Cadillac SRX, my Galaxy S2 had no issues. What is up with this phone.

Yeah tell me about it....my Lamborghini Aventador is doing the same thing

cuoreesitante said:
I just got a One S last week, and everything worked great with my 2009 A3 until yesterday, when bluetooth started getting disconnected by itself literally every minute. After it cuts off it immediately reconnects, which would have been fine but the A3 makes a "ding" sound every time the phone is connected. I have tried to unpair and pair again and again, and to no avail.
Despite this issue, the connection is actually fine when in a call. It's only when it's idle. Also my Nexus S working fine with the car, and the phone works fine with my BT speakers....
Does anyone else have this problem? I'm going to call my local dealership and ask if they have any sort of update for the A3 since the One S is BT 4.0....
Click to expand...
Click to collapse
That's weird, my 2012 A3 doesn't have this issue. Do you have the nav system or the base console?

cuoreesitante said:
I just got a One S last week, and everything worked great with my 2009 A3 until yesterday, when bluetooth started getting disconnected by itself literally every minute. After it cuts off it immediately reconnects, which would have been fine but the A3 makes a "ding" sound every time the phone is connected. I have tried to unpair and pair again and again, and to no avail.
Despite this issue, the connection is actually fine when in a call. It's only when it's idle. Also my Nexus S working fine with the car, and the phone works fine with my BT speakers....
Does anyone else have this problem? I'm going to call my local dealership and ask if they have any sort of update for the A3 since the One S is BT 4.0....
Click to expand...
Click to collapse
i had the same problem with my arc s and my '11 rs5 last year.the audi guy couldn't find any problem at the multimedia console. he offered me to change the whole console but the problem was still there. same problem on my girlfriends tts...don't know what audi was doing back there.
now on my new facelift rs5 bluetooth works like a charm

Maybe if you didn't have such a badass car your phone wouldn't hyperventilate and drop your bt con every 60 seconds.

I had this issue with SEAT Altea. It was in fact due to contacts syncronization.
To know if it is the case: unpair your phone and pair it again without accepting to share your contacts. then if the connexion is stable you will know that it's linked to sync.
I solved the issue by deactivating some phonebooks sources. I had 140 google contacts and 160 Exchange ones. Probably too many. By activating only the google ones the issue was solved.
hope it helps...

ocswing said:
That's weird, my 2012 A3 doesn't have this issue. Do you have the nav system or the base console?
Click to expand...
Click to collapse
I have a base console.
pierre.grand said:
I had this issue with SEAT Altea. It was in fact due to contacts syncronization.
To know if it is the case: unpair your phone and pair it again without accepting to share your contacts. then if the connexion is stable you will know that it's linked to sync.
I solved the issue by deactivating some phonebooks sources. I had 140 google contacts and 160 Exchange ones. Probably too many. By activating only the google ones the issue was solved.
hope it helps...
Click to expand...
Click to collapse
Yep I saw this on another forum and it worked like a charm. I dont really need to use the phone book anyway, as long as it can let me pick up phone calls im golden.

So, what was the actual change that solved the issues for you? We might want to take this into the FAQ. Did you disable the phonebook sync completely or did you just limit it to Google Contacts?

psych0t1c said:
So, what was the actual change that solved the issues for you? We might want to take this into the FAQ. Did you disable the phonebook sync completely or did you just limit it to Google Contacts?
Click to expand...
Click to collapse
It was the phonebook sync. When you pair the phone to your car you should get a prompt on the phone that the car is asking for permission to access your contacts, just check the "don't ask again" button and decline it.

I also have a problem downloading contacts. I drive 2011 Subaru Outback with OEM Nav/Bluetooth. How do you select which contacts to sync? Where is the option for selecting/deselecting Google, phone...etc?
Thank you

Hi,
when not syncing your contacts is not an option: If you keep your android running with the navigation app (preventing standby) do you still experience disconnects? If this helps you can try my app "BluetoothKeepalive" from the market, it automatically prevents android standby when being connected via bluetooth.
Regards
...Alex

Answering call with LTE S2

I have my S2 connected to my Nexus 6 via bluetooth. My S2 is the LTE version with T-mobile. When someone calls my cell, it rings on my Nexus as well as the S2. I'm ok with that. But if I answer the call on my Nexus, my S2 acts like a speaker phone. Don't like that. I want to be able to answer call on my nexus and use the nexus for the call or answer the call on my S2 and take the call on that. Is that possible?

Fron my understanding if you are using your watch on Bluetooth connection then the watch will act like a Bluetooth speaker if you answer a call on your phone. Only work around is to disconnect Bluetooth from your phone when you answer the call. Think of playing music thru a portable Bluetooth speaker and receiving a call while listening to music. You'd just disconnect Bluetooth from your phone to have a private convo.

Any help from HERE?

Yeah. I read that too. Not happy about it. Samsung needs to fix that issue. I had the urbane before s2. The s2 seems more of a work in process. Miss the integration of Android apps into the watch such as spotify.

Another reason Samsung needs to get rid of Tizen and only use Android Wear.

I have a Samsung Note 5 and don't have that problem. I can answer from either the phone or the watch on my S2 T-Mobile. If I had a non Sammy phone I would not be happy, hopefully they will fix in an update, or a Dev will put out a program to help. They advertise the watch as working with any Android 4.4 or above phone, they do not mention limitations if you are not on a Samsung phone.

I came up with a solution that fixes part of the problem. I use an app on my phone called Macrodroid. It's an automated task app. I created a macro that when I answer a call on my phone , it turns off bluetooth and vice versa when I hang up. So that works fine when I answer a call on my phone the call is not picked up by the S2. But when I answer the call on my S2, Macrodroid can't tell tell the difference that I'm answering the call on my S2 not the phone and turns off bluetooth. Not good!. There are more sophisticated macro apps out there, but I'm not that good with those. Maybe someone smarter than me can create one.
I also used Macrodroid to automatically call forward (and cancel forward) my cell phone to my watch when they are disconnected via bluetooth.

Go to settings, Bluetooth, and click the gear next to your watch. Uncheck phone audio. No problems now hopefully that's what you're looking for

paoloroeseke said:
Go to settings, Bluetooth, and click the gear next to your watch. Uncheck phone audio. No problems now hopefully that's what you're looking for
Click to expand...
Click to collapse
this solves the problem!
You dont want to use a macro to turn off bluetooth completely when a call comes in , especially if you use a Bluetooth headset with your phone..

I had forgotten where I'd seen this until now.
paoloroeseke said:
Go to settings, Bluetooth, and click the gear next to your watch. Uncheck phone audio. No problems now hopefully that's what you're looking for
Click to expand...
Click to collapse
I kept trying to find the "Phone Audio" setting on the watch's bluetooth settings, not the phone's. Doh!
crp

paoloroeseke said:
Go to settings, Bluetooth, and click the gear next to your watch. Uncheck phone audio. No problems now hopefully that's what you're looking for
Click to expand...
Click to collapse
Awesome! Been trying to figure that out for days!!!

Can't make calls: how to solve it?

Hello, I have a Gear S3 Classic BT with a Oneplus 3 (LineageOs, last nightly).
Everything works except for making/receiving calls, it just says something like "check device" when I rotate the bezel to accept a call and does nothing when I try to start a new one.
Is there a way to fix it?
For OP3 users on OOS: does it all work with stock rom?

I had exact same problem.I was using Lg g2 with custom cm 14 rom, when i tried to call someone or answering incoming calls gear just says "check device" and nothing happens.I tried many things but none of them have worked.Solution for me is going back to stock based rom.

Gone back to OOS, calls work. Not fine (bluetooth connection issues, it disconnects randomly), but at least it works.

The watch takes all my calls since the Tizen 3 update

So I'm running a S7 Edge + Gear S3 Frontier (Wi-Fi) combo. I've never had a single issue up until I updated to Tizen 3 yesterday. Everything looks fancier and better and so far I really enjoy it. But there's that little thing that irritates the hell out of me. When I call someone or someone calls me, the Bluetooth icon in the Call app is turned on by defaut so everything goes through the mic and speaker of my watch. I have to specifically click it again to turn it off every single time I make a call. Sometimes I forget to do so and it turns out rather embarrassing.
This has always been the default behaviour with my car's bluetooth and I've been fine with that. But this happening with the smartwatch as well is absolutely irritating.
Is someone experiencing this issue as well and any ideas how to fix it?

gbuyukliev94 said:
So I'm running a S7 Edge + Gear S3 Frontier (Wi-Fi) combo. I've never had a single issue up until I updated to Tizen 3 yesterday. Everything looks fancier and better and so far I really enjoy it. But there's that little thing that irritates the hell out of me. When I call someone or someone calls me, the Bluetooth icon in the Call app is turned on by defaut so everything goes through the mic and speaker of my watch. I have to specifically click it again to turn it off every single time I make a call. Sometimes I forget to do so and it turns out rather embarrassing.
This has always been the default behaviour with my car's bluetooth and I've been fine with that. But this happening with the smartwatch as well is absolutely irritating.
Is someone experiencing this issue as well and any ideas how to fix it?
Click to expand...
Click to collapse
I have this issue
I made temporary solution .. from Bluetooth setting I unchecked phone call for gear s3

sobluedeep said:
I have this issue
I made temporary solution .. from Bluetooth setting I unchecked phone call for gear s3
Click to expand...
Click to collapse
Did the same thing yesterday. Definitly started after update.

Same here.
I've already tried everything possible (I think ) Would turning audio bluetooth off cut the watch from the phone? Audio is my only option in bluetooth settings... I'm using Gear S3 classic along with Samsung Galaxy Note 4.

gbuyukliev94 said:
So I'm running a S7 Edge + Gear S3 Frontier (Wi-Fi) combo. I've never had a single issue up until I updated to Tizen 3 yesterday. Everything looks fancier and better and so far I really enjoy it. But there's that little thing that irritates the hell out of me. When I call someone or someone calls me, the Bluetooth icon in the Call app is turned on by defaut so everything goes through the mic and speaker of my watch. I have to specifically click it again to turn it off every single time I make a call. Sometimes I forget to do so and it turns out rather embarrassing.
This has always been the default behaviour with my car's bluetooth and I've been fine with that. But this happening with the smartwatch as well is absolutely irritating.
Is someone experiencing this issue as well and any ideas how to fix it?
Click to expand...
Click to collapse
had the same issue, but after factory reset on my gear s3 it was fixed, have a try ...

Have this exact issue. Factory Reset the watch with no change.
Also turning off calls under bluetooth settings on the phone disconnects the watch from the phone thus this is not an option.
Gear S3 Classic paired to an Galaxy S10+

Question Calls default to phone instead of watch

Does anyone else have this problem? I just got the Galaxy 4 smart watch (bluetooth, not lte version) a few days ago. When I initiate a call from the watch it dial and says "See phone" and the call is now coming through the phone. I can click a button on the phone to send the call back to the watch but obviously this defeats the convenience of not needing to have the phone in arms reach.
My husband figured out that its some kind of interference with other connected bluetooth devices (even though they are off), like my car and handsfree earpiece. If I unpair each of those items, calls work as they should. As soon as I re-pair another bluetooth device the problem resurfaces. I'd rather not have to pick one or the other to work if I can help it. Samsung support hasn't been able to fix it. Any ideas?

I should have clarified, I'm wondering both who does and who doesn't have this issue. Please comment even if yours works perfectly.
Samsung support seemed to suggest it was a software issue thar might be able to be fixed in a future update but I'm not sure if its an issue for anyone other than me.

Maybe you should take a look at this topic https://forum.xda-developers.com/t/...hange-default-behavior.4369423/#post-86031957