- May 14, 2017
- 88
- 0
- 0
I just switched from the gear s to the s3, and I'm having the issue below. I'm starting to wonder if the problem is an annoying issue, or if my new watch is designed and intended to be connected to my phone by Bluetooth substantially less than my old one.
I constantly keep my s8 and gear s3 connected through Bluetooth. When I'm driving, I'll connect my Bluetooth headset, which is paired and connected to both devices with no problems. I'll mount my phone in the window, so I can use Waze to navigate the best route to and from work, and use the headset to listen to the directions. I then use my watch to make calls, again using my headset for the conversation, but the call controls will immediately transfer to the phone. I did this all the time on my gear s and, while it would take over the phone's screen, forcing my to navigate back to Waze, it always left the actual controls on the watch face. It seems like it only does it when I'm on my headset on both devices,
Obviously it doesn't do that if I disconnect my watch from my phone, then call from the watch, but then I have to toggle it on and off all the time. Should I just be running the s3 independently from the phone more than I did with my old gear s? Am I keeping the Bluetooth connection up when I don't need it?
I have the frontier with my cell number duplicated to its esimm card. My gear s had it's own number, and often couldn't connect remotely to forward calls and messages, so I basically treated that independent calling function as an emergency contingency, if I left my phone behind, or it died, I could still call people. Otherwise I felt like it needed a constant connection to the phone.
I constantly keep my s8 and gear s3 connected through Bluetooth. When I'm driving, I'll connect my Bluetooth headset, which is paired and connected to both devices with no problems. I'll mount my phone in the window, so I can use Waze to navigate the best route to and from work, and use the headset to listen to the directions. I then use my watch to make calls, again using my headset for the conversation, but the call controls will immediately transfer to the phone. I did this all the time on my gear s and, while it would take over the phone's screen, forcing my to navigate back to Waze, it always left the actual controls on the watch face. It seems like it only does it when I'm on my headset on both devices,
Obviously it doesn't do that if I disconnect my watch from my phone, then call from the watch, but then I have to toggle it on and off all the time. Should I just be running the s3 independently from the phone more than I did with my old gear s? Am I keeping the Bluetooth connection up when I don't need it?
I have the frontier with my cell number duplicated to its esimm card. My gear s had it's own number, and often couldn't connect remotely to forward calls and messages, so I basically treated that independent calling function as an emergency contingency, if I left my phone behind, or it died, I could still call people. Otherwise I felt like it needed a constant connection to the phone.