Hi all,
Has anyone else had an issue with their phone not ringing when it's connected to the ZenWatch? Even when my phone is out of bluetooth range (and not connected), my phone still does not ring when I'm called.
My phone is running Cyanogen OS 12.0 and my ZenWatch is running Android 5.1.1. Is anyone able to provide any advice.
Much appreciated.
there's an option in Android wear to mute calls and notifications when the watch is connected, I know you said it happens even when not connected but you might want to start there. failing that, I'd probably forget the Bluetooth connection, then reset the watch then the phone in that order
Related
Ever since ICS came along I have been experiencing linking issue with my car's Bluetooth.
While it can detect the phone, problem is every time it's connected as a media speaker device only. To remedy that, I have to manually go into the phone settings and enable the phone calls too... Every single time.
Is anyone else experiencing this problem?
Hi guys,
I have a Galaxy S4 T-mobile SGH-M919 and it's Android 4.4.4 from Samsung (Original ROM) right now. I also have a Moto 360 Running the latest Android Wear 4.4w.2.
I encountered a serious bug.
So when my S4 is paired to my Moto 360, and if I am in a phone call, after a few mins (usually after 5 mins in), the sound would suddenly disappear. The other party whom I'm talking to can still hear me but I hear nothing. Complete silence.
When the sound goes off, I can just hang up and redial and then the call would be fine for a few mins before the same issue happens again. This is annoying.
I'm not sure if anyone has ever encountered this. I tried googling this and it seems no one has experienced the same issue with the same devices (Galaxy S4 T-mo and Moto 360). I've read that some people had similar issues with other bluetooth devices and their phones (or cars) and some say that it has something to do with my phone being connected with another device (in my case, the Moto 360) via bluetooth. I think when my Bluetooth is off, there is no issue at all.
If any of you has the same devices (Galaxy S4 T-mobile and Moto 360) and preferably the same firmware versions installed in both devices, give this a try. Simply connect your phone to your smartwatch and make a phone call. Try to wait for about 5-7mins into the call and see if if you experience this issue as well.
Is there a fix or workaround for this? This is ridiculously stupid. I should be able to make calls while my phone is connected to my Moto 360 as well.
[I'm running a stock 7.1.1 without root or any other mods]
BT doesn;t work with 2 BT devices which can do phone...
Example:
1) BT watch, Huawei Watch connected - this watch can receive and make phone calls... It has a microphone and speaker, so it works like a full-fledged phone device. It is basically **** Tracy device... look it up ...
2) When the watch is connected, another BT phone device, like a car kit, doesn't connect. You can go to BT settings and manually click on the BT device to connect. Sometimes, it connects w/o extra help. And sometimes, clicking doesn't connect at all. Sometimes it connects automatically. Bugs!
3) When both devices seem to be connected (even though only one is shown to be connected), both can make calls, but only the "active" one receives them...
The active being the one that was connected last.
4)
------ This was not a problem in 7.1.0. Whichever device (watch or car kit) initiated or answered a call, would be used to do the complimentary function - If you make a call on watch, you get audio for the call on watch. If you receive the call on BT car kit, you answer on it. Without fail this worked just fine. Both incoming and outgoing calls. It made sense and it worked beautifully.
-----
Until 7.1.1.
---- Now, if a watch is connected (Huawei Watch, which can act as a phone itself), the BT car kit will not connect. If you connect it manually by clicking on it in BT settings, it will connect, but all phone actions, even initiated from the watch will only work on the phone.
In other words, 7.1.1 killed BT functionality with several BT phone devices.
Why can't they fix it?
UPDATE after 7.1.2
So, 7.1.1 killed phone functionality when both a phone capable watch and another BT phone device were connected simultaneously - both wouldn't work correctly at the same time.
7.1.2 didn't fix this at all.
What 7.1.2 did was introduce new bugs: 1) Weather built-in app no longer works on my Huawei watch, it just spins the circle retrieving weather data and then just goes back to watch face, 2) The watch no longer displays some notifications, for example, SMS.
I played with all of the settings in the watch, phone, and android wear app. Nothing.
I have a theory... Google has two android development teams. Let's call them Team A and Team B. Team A works on a yearly cycle developing new android OSes, for example, they are probably working on Android O right now. Team B picks up development and maintenance duties after Team A makes the initial android release. Team B would be working on Nougat right now. Team B is comprised of rejects from Team A; they have very little talent, attention to detail, or even skill. They may fix 1-2 bugs in an incremental android version, but they introduce 5 more new ones.
This is why Android 7.1.0 was less buggy than 7.1.1, and conversely, 7.1.1 was less buggy than 7.1.2.
Me with my powerbeats it seems to work but eventually it will stop playing music so I turn off headset turn back on and music starts playing again and then the music will start skipping because it hears background noise. It drives me nutts.
..
--
Worked for me.. I could connect to my headphones but yet it acted like it was not connected. Connected to my truck yet it acted like it was not connected.. I for the hell of it wiped dalvik/cache and now it all works with no problems. Headphones instantly worked after doing it. Truck worked just fine this morning..
Sent from my Pixel XL using Tapatalk
--
..
Sent from my Pixel XL using Tapatalk
I'm on stock like the OP. My bluetooth issues are similar and I have one more.
Devices I'm paired to disappear from the BT list. I got in my car yesterday and was surprised the screen needed me to enter my PIN as I had my car in Smart Lock. Go look and sure enough not connected to the car and the BT list doesn't have my car listed as a device. I had to re-pair to the car. Then I had to readd to Smart Lock. This has happened with other BT devices (primarily headsets as that is really the only other things I use with my phone). This happens frequently and almost daily that I lose one or more BT paired devices from the list.
Other times, primarily with my Bose QC35 as I frequently turn it on/off, it will be in the BT list but the phone says I need to pair the device again. This only happens about every 10th time I turn the headphones back on.
Unfortunately, I've only had 7.1.1 on this phone as it is only a few weeks old. So I don't know if stuff would have worked in 7.1.0.
djr4x4 said:
Worked for me.. I could connect to my headphones but yet it acted like it was not connected. Connected to my truck yet it acted like it was not connected.. I for the hell of it wiped dalvik/cache and now it all works with no problems. Headphones instantly worked after doing it. Truck worked just fine this morning..
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'd like to know what you did to make things work.
Updated op with 7.1.2 info.
Hi, I tried to find something about the issue, which I have, but nowhere is the same problem, so I tried to create the new thread...
I have the company phone Samsung Galaxy A5 2017 (SM-A520F) with the stock ROM (now with Oreo) and I got the new company car with build-it bluetooth (Volkswagen). I tried to pair the phone with the car and everything looks good. A few first calls were without any trouble. But now happens very ofter (almost in 99% attempts), that I have connected phone to car and
- somebody call me
- I call to somebody (via touch on contact in infotainment in car)
- I call to somebody (via touch on phone application on mobile phone)
the call is starting and in the same time is the BT connection interupted. And there are two possibilities:
- BT on SGA5 is still turned on, but disconnected from car
- BT on SGA5 is turned off (somehow)
You can say, there is trouble with your car, but I tested is with the other mobile phone (Nexus 5X) and everything works properly.
That's why I think, that the trouble isn't in car, but in the phone. And of course I did the wipe of whole phone and after that I tried it again, but with the same results.
Does somebody the same/similar experience? Is there some solution? Because no possibility to call in car is horrible for me and I can only get a new phone in the summer (it is too long time without call from car).
Thank you in advance
Hi everyone,
I'm having a problem that I think shouldn't happen on this phone.
I'm stock with the latest January update on Android 10.
Info: this problem was present before the update to 10.
Whenever I connect any Bluetooth device (airpods, car, moto intercom ,etc) I have to manually unpause the music to get it to start.
This happens on every player (Samsung Music, Google Play, YouTube premium, etc)
This is the first Android phone I have that doesn't do this and that shouldn't be seeing it's top tier.
I've looked online and it seems that all Samsung phones have this feature and the only topics I get are how to disable it !?
Can anyone shed some light ? Is it happening to you as well ?
Thanks
I may not have the answer that you want to hear but I did find a temporary solution. There's an app in the play store nRF Connect that works. Slide over to bonded, put devices in pairing mode and hit scan and wah lah. Any questions I'll do the best I can to help.
I've noticed the same on my galaxy buds, but when I connect another pair of wireless earbuds that i sometimes use they connect as soon as i turn them on when Bluetooth is activated, without me manually having to go into the settings and do it. Not sure the reason for this. Would've thought the earbuds that's actually made by Samsung would be the ones connecting right away.
hotshot646 said:
Hi everyone,
I'm having a problem that I think shouldn't happen on this phone.
I'm stock with the latest January update on Android 10.
Info: this problem was present before the update to 10.
Whenever I connect any Bluetooth device (airpods, car, moto intercom ,etc) I have to manually unpause the music to get it to start.
This happens on every player (Samsung Music, Google Play, YouTube premium, etc)
This is the first Android phone I have that doesn't do this and that shouldn't be seeing it's top tier.
I've looked online and it seems that all Samsung phones have this feature and the only topics I get are how to disable it !?
Can anyone shed some light ? Is it happening to you as well ?
Thanks
Click to expand...
Click to collapse
Hej...
I don't if this would help You...
When I got the Note 10+ there's Was, out of the box on initial settings, active few Bixby Routines... and that, till i figure out this, was driving me crazy... When I turn Bixby Routines off everything back to normal...
Well I've had a similar problem. For me the issue is that it always autostart even tho I have BT autoplay unchecked in the car. If I have listen to any music, audio books, podcasts and turn them of when I exit the car, not leave them in the background, they will start playing even if the cars media system is offline.
Works perfectly with my wifes OnePlus 6, but not for me. Extreamly annoying to noticed that the audio book is playing after a 60min drive and I haven't heard anything..
I tried the app Tasker, it was a compleat waste of $4 for me anyway, didn't work, will try nRF Connect now.
I don't want to have BT of due to that I aways have my Jabra buds with me so that I can talk while driving if needed.