I have the AT&T Galaxy S II Skyrocket and my phone used to auto-connect to my car via bluetooth without any problem, even after upgrading to ICS in early July. All of sudden since yesterday a problem has popped up: whenever I start the car, the car's control panel shows "bluetooth connection successful" or something similar, and then the car audio system switches into the talk mode as if the phone is in the mid of a phone call. Of course I am not in the middle of any phone call. So there is no audio heard (no radio, no cd playing, etc). I try to press the button on the car's panel to disconnect the call but it always returns to that talk mode. After some tests I find out that if I make any phone call, the call will be disconnected immediately and the status of my car's panel returns to normal. But next time when I start the car, the issue appears again until I make any phone call.
At the beginning I thought something was wrong with my car. Then I tried two other phones: one was iphone 3G, and the other was an old htc magic with android 2.2. Both of their bluetooth systems worked well with my car. So I believe it is something wrong with the Galaxy phone. However I am not sure what could be the problem exactly.
My phone is not rooted.
Any help is highly appreciated!
Have you tried unpairing the skyrocket and your car? Sometimes you just need to break the connection and set it up again.
Reported questions go in q&a and there are threads on Bluetooth issues
Sent from my SGH-I727 using Tapatalk 2
Firedcylinder said:
Have you tried unpairing the skyrocket and your car? Sometimes you just need to break the connection and set it up again.
Click to expand...
Click to collapse
Yes I have unpaired the connection, restarted the phone and the car, and paired them again. But the problem persists.
Today I tried my wife's iphone 4 with the car the didn't see any problem. I am pretty sure there is something fishy with the phone.
lik88888 said:
I have the AT&T Galaxy S II Skyrocket and my phone used to auto-connect to my car via bluetooth without any problem, even after upgrading to ICS in early July. All of sudden since yesterday a problem has popped up: whenever I start the car, the car's control panel shows "bluetooth connection successful" or something similar, and then the car audio system switches into the talk mode as if the phone is in the mid of a phone call. Of course I am not in the middle of any phone call. So there is no audio heard (no radio, no cd playing, etc). I try to press the button on the car's panel to disconnect the call but it always returns to that talk mode. After some tests I find out that if I make any phone call, the call will be disconnected immediately and the status of my car's panel returns to normal. But next time when I start the car, the issue appears again until I make any phone call.
At the beginning I thought something was wrong with my car. Then I tried two other phones: one was iphone 3G, and the other was an old htc magic with android 2.2. Both of their bluetooth systems worked well with my car. So I believe it is something wrong with the Galaxy phone. However I am not sure what could be the problem exactly.
My phone is not rooted.
Any help is highly appreciated!
Click to expand...
Click to collapse
Common problem:
http://forum.xda-developers.com/showthread.php?t=1630021
Also look in the last couple of pages here, there is some explanation for it.:
http://forum.xda-developers.com/showthread.php?t=1701189
Does it have to be connected to my phone via bluetooth to get apps and notifications to work? I thought stand alone meant that I could still get my notifications and apps like eBay would still work.
if both your phone and your s2 is connected to wifi, they connect remotely and you can receive notifications... but the non 3G S2s will need an active connection to something
I have the 3g model. I thought that i would still be able to use apps and get notifications when my phone was say, left in the car and therefore was not connected
Did you make sure that mobile data is turned on or set to auto for the watch? I just did a test for email by disabling bluetooth on phone, making sure the watch picked up mobile network (I have mine set to auto not always on) and then sent myself an email and the alert came through to my S2 without issue.
I turned off bt, wifi on and 3g. It says they are connected remotely I sent myself a email and that worked. Now when there is no wifi and no bt connection and its just the gear and phone is in car, should I still receive texts and emails? Btw my eBay app doesn't work set this way.
When I tested mine I did not have WiFi or Bluetooth on. So the watch was not connected directly to the phone via Bluetooth or WiFi, just over mobile data. So this should be the same as testing like the phone was left in the car. If the connections aren't enabled there should be no difference between testing with them beside each other or leaving the phone in the car. The only difference would be if you were in a location that the phone and/or the watch did not have a connection to mobile data. If one of them was not on mobile data then it wouldn't be able to see the other.
One other way I can test it would be if the phone is on mobile data and the watch is on a WiFi network, it would be interesting to make sure that would work.
Also, I haven't tested yet, but my understanding was that if your phone dies or loses signal then it will not forward calls or messages to the watch. Has anyone else confirmed that? It should be an easy enough test.
I have not tested call forwarding either as I have not enabled it yet, I was hoping to do some more extensive testing before I do as I don't want any issues and I can't have my phone not ring.
---------- Post added at 03:46 AM ---------- Previous post was at 03:14 AM ----------
Ok, so I just did a bit of testing with some pretty interesting results.
Keep in mind that this is testing strictly with email, exchange email on my phone to be exact.
So I did a few test on a variety of different connections, Bluetooth off in watch settings for all tests, but tried different variations of both on same network and one on WiFi the other mobile and then swap which Device was on WiFi. The results were all pretty much the same regardless of how I had the connection. I was able to get notifications regardless of how my connection was setup. Also to point out is that my watch only says standalone for just a second when I look before it switches over to "connected remotely"
So the interesting stuff that I noticed is that if I did not receive a notification on my phone then I received nothing on the watch, for instance one test I sent myself an email but left the email open on the phone so it did not send me a notification for the email. This would make since and I understand not getting a notification for it, but the thing I thought was weird is that even if I go look in the app on the watch for email the email did not come over in the app.
The other interesting thing I noticed was that I would not receive the notification on my watch until my screen actually shut off on the phone. So if I received an email but was still doing something else on my phone, the notification did not come through until the display goes off on the phone.......Update for this one, there is a setting in notifications on the gear app on the phone that allows it to send notifications when the phone screen is on.
Anyone else having similar results?
It also seems to me that the mail app on the watch is more of a notification tracker instead of a mail sync, it does seem to update deleted items for me, but it will not sync in mail to the watch if i did not receive a notification for that mail on the watch. So definitely some kind of disconnect/bug/user error somewhere.
Idk what is going on with mine. I'm texting with my phone and not one time has my gear told me I have a notification. Gear app says remotely connected. Phone on 4g and gear on 3g
Hmmm interesting.
I just tried testing my text messages via remote connection with watch on the mobile network and mine appear to be functioning correctly. One thing i did notice for mine is that text messages function a lot better then email does. It even sends me notification on my watch if i have the text open and do not receive the notification on my phone. Also, when I completely disabled any connection on my watch, then did a test text, and viewed the text on my phone. When I turned connection back on for the watch it did sync the text to the watch. This still does not sync for email though, email only shows on my watch if I received the notification on my phone.
Another thing I can think is that in your watch settings you have a mobile network and a mobile data, make sure that when bluetooth is disconnected the mobile data is on too.
Do you have any other bluetooth device connected directly to the watch or phone? Haven't tested, but not sure if the watch or phone would see a headset connected bluetooth as connected and not forward things correctly......just thinking out loud here.
I don't really use any other bluetooth devices. All my connections say on except the bluetooth. Should I do a reset?
Ok, like I said for the bluetooth I haven't done any testing so it was just a thought.
Have you went into the gear app on your phone and went to notifications/manage notifications and make sure the messages notification is enabled?
I have a T-Mobile Note 5 paired to the T-Mobile Gear S2. Maybe different providers or different phones are having a different experience then how mine is working.
I always like doing a reset as just a last resort once all other settings are checked. But if everything else looks like it should be enabled correctly a reset can't hurt to try. I can't really answer if it will fix it as I just haven't had the problem you are seeing myself.
Is the only thing that makes this one different from the classic is the 3g? Which at this point isn't really doing anything extra for the watch.
I have a bit of a different issue with bluetooth. First my setup. Galaxy S6 edge+ and Gear S2 3g version (verizon). There's a button on the notifications panel on the watch that you can press to automatically forward your calls from the phone to the watch. Now, I have a bluetooth headset connected to the watch. I unpaired it from the phone. I can hear all navigation (button presses, etc) through my bluetooth headset (LG HBS730) while using the watch, however, If I receive a phone call, the call forwards to the watch but I can't answer it with the bluetooth headset. The headset doesn't even ring or vibrate like It does when paired with the phone. It just doesn't respond to the watch ringing at all. yet I can hear all other sounds from it. (YES, I checked the bluetooth options for call and media and they are both on).
AlienBeans said:
I have a bit of a different issue with bluetooth. First my setup. Galaxy S6 edge+ and Gear S2 3g version (verizon). There's a button on the notifications panel on the watch that you can press to automatically forward your calls from the phone to the watch. Now, I have a bluetooth headset connected to the watch. I unpaired it from the phone. I can hear all navigation (button presses, etc) through my bluetooth headset (LG HBS730) while using the watch, however, If I receive a phone call, the call forwards to the watch but I can't answer it with the bluetooth headset. The headset doesn't even ring or vibrate like It does when paired with the phone. It just doesn't respond to the watch ringing at all. yet I can hear all other sounds from it. (YES, I checked the bluetooth options for call and media and they are both on).
Click to expand...
Click to collapse
Hi Alien,
So for mine, I have the LG HBS750, so a very similar headset to yours. Mine seems to work pretty good. I think you checked a lot of things I would have suggested, main one being the bluetooth settings on the watch for call and media. I did notice with mine that if I answer the call from sliding on the watch face it goes to the speaker phone of the watch (even with the bluetooth headset connected), but if I answer with pressing the button on the headset it goes to the headset. But mine vibrates and everything when the call is forwarded so I do not even think yours would be getting to that point.
Have you tried taking the call on the watch face and pressing the three little dots on the watch face and clicking the bluetooth button to see if it sends it to your headset? It kind of seems to me like even though you have told it to use the headset for call audio it just isn't working right. Maybe a full unpair and repair to the watch for the headset?
rgburress said:
Hi Alien,
So for mine, I have the LG HBS750, so a very similar headset to yours. Mine seems to work pretty good. I think you checked a lot of things I would have suggested, main one being the bluetooth settings on the watch for call and media. I did notice with mine that if I answer the call from sliding on the watch face it goes to the speaker phone of the watch (even with the bluetooth headset connected), but if I answer with pressing the button on the headset it goes to the headset. But mine vibrates and everything when the call is forwarded so I do not even think yours would be getting to that point.
Click to expand...
Click to collapse
It's odd that I get all the other sounds through it but not when the watch rings. I find it also odd that my phone continues to ring even when I have call forwarding to the watch turned on. The phone rings until I answer the call whether on the phone or on the watch. Does that happen for you as well?
Have you tried taking the call on the watch face and pressing the three little dots on the watch face and clicking the bluetooth button to see if it sends it to your headset?
Click to expand...
Click to collapse
I have not tried that with the 3 little dots. I just hadn't gotten that far with it yet.
It kind of seems to me like even though you have told it to use the headset for call audio it just isn't working right. Maybe a full unpair and repair to the watch for the headset?
Click to expand...
Click to collapse
I tried that last night. I'll use it today and see how it works. I can make calls using the headset just fine from the watch. Maybe re-pairing it to the watch will help. My headset (as does yours i'm sure) supports multipoint. But I thought that would mean the head set could be connected to both phone and watch simultaneously and used for calls on both devices, but I'm not finding that to be the case.
AlienBeans said:
It's odd that I get all the other sounds through it but not when the watch rings. I find it also odd that my phone continues to ring even when I have call forwarding to the watch turned on. The phone rings until I answer the call whether on the phone or on the watch. Does that happen for you as well?
I have not tried that with the 3 little dots. I just hadn't gotten that far with it yet.
I tried that last night. I'll use it today and see how it works. I can make calls using the headset just fine from the watch. Maybe re-pairing it to the watch will help. My headset (as does yours i'm sure) supports multipoint. But I thought that would mean the head set could be connected to both phone and watch simultaneously and used for calls on both devices, but I'm not finding that to be the case.
Click to expand...
Click to collapse
When my call forwarding is on it will ring my phone first, about 6 times or so, then my phone will stop ringing and shows a missed call and then the watch immediately starts ringing. Listening to the call while trying to call it I do not really notice much of a disconnect in the transfer, just a lot of rings. It would seem if the phone and watch are both ringing at the same time right when the call comes in then there is still a connection between the phone and the watch and not a remote connection. Do you still have bluetooth enabled on both phone and watch and have a bluetooth connection between them?
So I am not sure if this is your issue, but I did some testing just now. Granted this is on a different bluetooth headset as I left my LG at home today by mistake, but the other set still has multipoint. Bare with me while I try to explain my thoughts here haha......It might be a little confusing but I will try to re-read it and make sure I didn't make mistakes.
Scenario 1
So if I have the bluetooth between my watch and phone not connected (remote connection is enabled via 4G and call forwarding is on), but have the headset connected to both the phone and watch at the same time. I call my phone number, the phone rings a bit and the bluetooth also rings with it, after the phone stops ringing the call forwards to the watch and then the watch and bluetooth both ring from the watch, so this works exactly as expected with multipoint here.
Scenario 2
If I have the bluetooth connected between the watch and the phone. The headset paired to the watch only but not the phone. When I call my phone, the watch and phone will both ring at the same time and I do not hear anything for the call in my headset, but I still hear normal sounds from the watch in my headset.
Scenario 3
If I have the bluetooth connected between the watch and the phone and the headset paired to the watch and phone both. When I call the phone the watch and phone both ring at the same time and I hear the ring through the headset. When I answer via headset it answers to the phone. If I answer via watch and then tell it to go to headset, it sends it to the phone. So it seems that if the headset is connected to both then it takes priority to the phone for the calls, I think this is Samsung doing this and not the multipoint.
So I am thinking you might be in scenario 2. So try this. Turn bluetooth on your phone completely off. this should send your watch to standalone mode. Give it a min or so and check the watch status by swiping down and it should go from standalone to connected remotely......for mine if the call forwarding is on I even get a popup on my phone that says call forwarding enabled. Make sure headset is connected to the watch, it should just be the watch at this point as bluetooth on your phone is off. Then try calling your phone, let it ring and ring and when it stops ringing see if it starts ringing on your watch and see if the headset rings with the watch.
rgburress said:
When my call forwarding is on it will ring my phone first, about 6 times or so, then my phone will stop ringing and shows a missed call and then the watch immediately starts ringing. Listening to the call while trying to call it I do not really notice much of a disconnect in the transfer, just a lot of rings. It would seem if the phone and watch are both ringing at the same time right when the call comes in then there is still a connection between the phone and the watch and not a remote connection. Do you still have bluetooth enabled on both phone and watch and have a bluetooth connection between them?
So I am not sure if this is your issue, but I did some testing just now. Granted this is on a different bluetooth headset as I left my LG at home today by mistake, but the other set still has multipoint. Bare with me while I try to explain my thoughts here haha......It might be a little confusing but I will try to re-read it and make sure I didn't make mistakes.
Scenario 1
So if I have the bluetooth between my watch and phone not connected (remote connection is enabled via 4G and call forwarding is on), but have the headset connected to both the phone and watch at the same time. I call my phone number, the phone rings a bit and the bluetooth also rings with it, after the phone stops ringing the call forwards to the watch and then the watch and bluetooth both ring from the watch, so this works exactly as expected with multipoint here.
Scenario 2
If I have the bluetooth connected between the watch and the phone. The headset paired to the watch only but not the phone. When I call my phone, the watch and phone will both ring at the same time and I do not hear anything for the call in my headset, but I still hear normal sounds from the watch in my headset.
Scenario 3
If I have the bluetooth connected between the watch and the phone and the headset paired to the watch and phone both. When I call the phone the watch and phone both ring at the same time and I hear the ring through the headset. When I answer via headset it answers to the phone. If I answer via watch and then tell it to go to headset, it sends it to the phone. So it seems that if the headset is connected to both then it takes priority to the phone for the calls, I think this is Samsung doing this and not the multipoint.
So I am thinking you might be in scenario 2. So try this. Turn bluetooth on your phone completely off. this should send your watch to standalone mode. Give it a min or so and check the watch status by swiping down and it should go from standalone to connected remotely......for mine if the call forwarding is on I even get a popup on my phone that says call forwarding enabled. Make sure headset is connected to the watch, it should just be the watch at this point as bluetooth on your phone is off. Then try calling your phone, let it ring and ring and when it stops ringing see if it starts ringing on your watch and see if the headset rings with the watch.
Click to expand...
Click to collapse
Yep Scenario 2 is me. Any call I get, the phone and the watch both ring at the same time. Oddly enough today I want to check it and my phone never rings. Normally it rings off the hook all day. Today, not one call. So turning off bluetooth connection on the phone is likely my solution to this. However, what happens to the rest of my notifications if bluetooth is off on the phone. This means the watch and phone are no longer paired together. Will I still get text and email notifications on the watch? Did you happen to test that?
AlienBeans said:
Yep Scenario 2 is me. Any call I get, the phone and the watch both ring at the same time. Oddly enough today I want to check it and my phone never rings. Normally it rings off the hook all day. Today, not one call. So turning off bluetooth connection on the phone is likely my solution to this. However, what happens to the rest of my notifications if bluetooth is off on the phone. This means the watch and phone are no longer paired together. Will I still get text and email notifications on the watch? Did you happen to test that?
Click to expand...
Click to collapse
So I would not turn off Bluetooth connection, at least not permanently, I just meant to test the call forwarding. I would just pair the headset to the phone as well.
The Bluetooth is the connection that is meant to be used for when you are close to your phone. The beauty of the 3g watch is that it enables you to be connected to your phone if you leave your phone behind.
So how it works is your watch has its own number and your phone has its own number. When the Bluetooth is connected between the two then the watch and the phone are both ringing with your cellphone number, the phone is almost using the watch like it were a headset and not using the watch phone number. So you enabling call forwarding on the watch does nothing until you no longer have that Bluetooth connection between your phone and watch. If you were to leave your phone behind (or turn off Bluetooth just to test so you don't have to just leave your phone and walk away) that's when the call forwarding that you enabled kicks in, you need to make sure that you have told mobile network to be either auto or always on for the watch, it is in the settings. I'm using auto just to save battery life, with auto the watch only turns 3g on if it loses the Bluetooth connection to the phone, and because I have the call forwarding on, the phone will know that if I don't answer the phone it will auto forward to the watch number which then will ring the watch. Does that kinda make sense?
So like I said I would stick with Bluetooth on, the watch is meant to be an accessory to the phone. Just keep your headset paired to both phone and watch. Make sure mobile network for watch is either auto or always on, and make sure call forwarding is enabled (if you want the phone to forward the call if you leave it behind). As for notifications, you should receive them on the watch whether you are connected via Bluetooth or remotely connected via the 3g, I am not positive if they all work the same on both connections, but so far mine seem pretty consistent.
The downside of when you leave your phone behind and are connected remotely via the watch 3g is that whIle it is using its own number at that time, it also has its own voicemail. So if you miss the call on the phone and it forwards to the watch and you miss the call on the watch then the voicemail will be on the watches voicemail. But while they are connected via bluetooth, the phones voicemail is the one that will be used.
One other note, if your phone is powered off, either intentionally or just from a dead battery or something, the phone will not be able to forward the calls or any notifications to the watch.
Let me know if your needing any further clarification on any of that as I know there is a lot there, and I am responding from my phone so I could have made some mistakes.
worked beautifully today. Thanks for the tip. I had totally forgotten about just turning off the bluetooth on the phone. Worked like a champ.
hello,
could someone tell me why every time I turn on my ear bluetooth, my s2 classic watch (not 3g) does not connect directly?
well on the watch was already PAIR.
thanks.
There are notification settings in Samsung Gear. One for BT and one for remote. Make sure both are set.
Also the forward number should be active whether the phone is on or not, it overwrites the setting from vzw.com
Sent from my SM-G925V using XDA Free mobile app
Hi everyone,
Could you guys answer me this: Is the Gear S3 supposed to disconnect the bluetooth connection to my phone every 2 minutes or so? I can't get it to stay connected no matter what i try. I need to reboot my phone everyday because if i don't.. it won't connect at all.
After the reboot everything seems good and i can connect the gear through the Gear app. it only keeps disconnecting every 2 minutes... I've contacted Samsung about this and they told me that the bluetooth version on my phone was insufficient. They suggested i upgraded my phone from an Oneplus one to a Galaxy S8. I bought a Oneplus 5T instead but the problem remains. After i contacted Samsung for a second time they told me that's its probably a hardware related issue. Sounds unlikely to me since rebooting the phone allows me to connect to the watch.
Anyone having the same problem?
anyone?
no problems here, using oneplus 3T (so not the 5T) (On beta OS: A3003_28_180112) and gear s3 frontier on 3.0.1
jbrugger said:
no problems here, using oneplus 3T (so not the 5T) (On beta OS: A3003_28_180112) and gear s3 frontier on 3.0.1
Click to expand...
Click to collapse
Hmm ok. I think it's really weird i need to restart my phone every morning in order to connect to the phone.. Makes no sense
I am experiencing a similar issue with my 5T and Gear S3. Sometimes all the system sound (not multimedia ones though) are being routed to the ear speaker instead of the multimedia speaker. I missed an alarm several times. The fix for me is the same - to toggle BT connection with Gear S3.
I have lockscreen sounds enabled. So, I realize the issue reproduces when the lockscreen sound starts to be very quite and is being emitted via the ear speaker.
Another issue with the Gear S3 I am experiencing is as follows. If I start Google Play Music on my phone, Gear S3 does not see the player is started. Anyway I can start the player from the watch. Also, if I toggle the BT, everything works perfectly. Could you check this on your side as well?
I had a similar situation, the Gear S3 was disconnecting very often. In the end, I found that it was the battery saving settings on my N8 Sirocco that killed the connection to my Gear S3. I turned settings and blacklist off, and now it stays connected.
This is driving me a little nuts! The watch frequently defaults to be my bluetooth connection when I'm making and receiving a call. It's mainly when I am in my car and I really NEVER want a phone call on my watch. Is there some way to disable phone calls on the watch or change how the phone is connecting to devices (eg in what order it makes a connection)?
In Settings > Bluetooth > Paired devices > Disable option to receive calls, for watch
I think this may be the best solution for it. I appreciate the quick and easy response! Bummer that it doesn't let me pick the default list in order or something.
Do you have LTE watch ? Because I do not really understand your problem.
Mine is BT. When I get into my car, phone connects to Ford Sync system. When incoming call arrives I just pick it up from the Ford sync.
That is what I want to happen! I do not have lte but when I'm in my car (and I would say more likely than not connected to Android auto) when I press the button to answer the call my watch steals it. It also sometimes happens when I'm wearing BT headphones connected to my phone. The way you're describing it is totally logical. If I answer it on the phone with a swipe or I choose that device in BT settings once a call is already answered that's fine. But when I'm pressing the answer button on my steering wheel why is it going to the watch?
bam099 said:
when I press the button to answer the call my watch steals it.
Click to expand...
Click to collapse
This is really odd.
When I pick up call on the phone, still Ford gets the call.
When out of the car and watch connected to phone: when I pick up at phone - call remains at phone.
The only difference is, that I do not connect to Android Auto ( I have to use cable - which I am to lazy to plug ). I use only BT connection to car as ordinary handsfree
I will verify what happens when I connect to Android Auto.
EDIT: Maybe this is a problem of you phone ? I think this is the place when you shoul search for handsfree priority ? I mean it is not "hungry" watch "stealinbg" the connection buy phone feeding him I have Galaxy M51 and no problem of this kind
EDIT2: You ate not the only one with this problem and it is not problem caused by GW4
android handsfree priority - Google Search
Problem solved:
[Guide] How to use Tasker to fix all calls being sent to Gear S3
The Problem: On many non-Samsung phones, all calls, even when answered on the phone itself, get sent to the watch's speakerphone, requiring the user to manually switch the sound back to the handset every time a phone call happens. As a side...
forum.xda-developers.com