Related
I just switched to a Galaxy S3 from an Desire HD. Overall I'm not very happy.
One issue that is turning into a deal breaker is the BT connection with the car. I have been unable to make the S3 connect automatically with my Nissan Connect and it is a laborious process to establish a full phone and media connection.
This is what happens,
The pairing process goes well I get a a full media and phone connection. After about 30 secs the connection is dropped.
I reestablish the connection manually and I only get media audio no phone. I cancel the connection manually and reestablish the connection and there I get both media and phone audio.
If I turn off the car and turn it on again I have to go through the whole manual connection sequence again, without the pairing.
I have installed A2DP Volume app but it did not fix the problem.
This is very frustrating since my Desire HD worked flawlessly when connecting to the car.
Anyone have any tips or experiencing similar problems?
this exactly happens to me as well. i was on the stock XALE8, but upgraded to ALF5 and nothing new. this is frustrating because it happens to my car, and multiple bluetooth headsets.
Bluetooth working fine for me and my Fiat
Sent from my GT-I9300 using Tapatalk 2
Right I might know the answer to this as I had the same problem as few weeks ago.
If you have Facebook, twitter, whatsapp or anything like this best thing is to get rid of them if you don't want to, go to your accounts and sync on your phone and untick the sync with contacts on any of the apps you have installed.
Then go to call log and clear your call history.
Delete the bluetooth pairing turn the phone off and back on, repair with the car, mine has worked perfectly since I did this.
Sent from my GT-I9300 using XDA
So from what you describe the problem lies in the syncing of the phone contacts with the car contacts. Maybe since it also tries to sync the FB contacts there is something in the format there that it does not recognize and it gets hung up.
Will need to try different sync configurations to see what happens.
Help
Motogp1 said:
Right I might know the answer to this as I had the same problem as few weeks ago.
If you have Facebook, twitter, whatsapp or anything like this best thing is to get rid of them if you don't want to, go to your accounts and sync on your phone and untick the sync with contacts on any of the apps you have installed.
Then go to call log and clear your call history.
Delete the bluetooth pairing turn the phone off and back on, repair with the car, mine has worked perfectly since I did this.
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
I've got the same problem with my S3 not syncing with my car kit. The bluetooth is all paired but the car still says no phone. Tried unpairing and just about everything else with no luck at all. Any other thoughts please?
Mine works fine with the Toyota Touch & Go thingy. I only sync contacts from my Google account to the phone though, I don't bother with the ones from FB, etc
Sent from my GT-I9300 using xda premium
Hi there. Following up on this thread, I've had a similar issue with the miss's Galaxy S3 mini (android 4.1) and the Nissan Connect System on her Juke. It also happened with a HTC Status (ChaCha, android 2.3), so I can't narrow it down to a particular Android version or phone manufacturer. What happened was, both devices paired well with Nissan Connect, but after a short while, the system crashed completely (the cars, not the phone) :s. It would restart automatically, but just to crash again after re-pairing. With older devices, this issue never occurred.
After reading Motogp1s answer, I decided to give it a shot. Unpaired all devices, cleared the system on the nissan. On the S3 mini cleared the call history, and disabled all contact sync from facebook, google, etc. Re-paired the device, disabling the multimedia functions (she just wants the phone features) on the paired device settings (NISSAN CONNECT on the S3). Refused to give permission tho the car to retrieve call and contact information. At this point, the bluetooth connection would work without a glitch, never had a crash or problem again.
Like RaulTT said, the problem seems to be in the amount of information Android devices keep on their contact list (and can also be related to the amount of contacts, or the multimedia features in the case of Android 4). But given the sweetness of having your contacts also on the car, I think the best approach is to keep a short list of your most important contacts on the SIM card, and try to sync only that list. If you must go with the phone's list, you should indeed disable all contact sync from 3rd apps, plus limit the size of your contact list, and also be aware for special characters on the contacts names (in case of latin languages, p.e).
Thanks for the help.
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
diehardbattery said:
So, I've had my Gear S now for about a week, and LOVE it. The connection stuff has me a bit confused though. I have it paired with an AT&T Note 4. There are a few things I have questions about...
If I reboot the phone, the watch will only connect to Gear Manager remotely. Shouldn't it connect to Bluetooth first? I have to go into Gear Manager and disconnect the remote connection, then it will reconnect via Bluetooth.
Under what circumstances does the phone forward calls/sms to the watch? For example, on purpose, I left my phone at home one day, and went out for a drive. Calls and SMS that were made came from the watch's number. I can't say about the receiving end because I didn't receive anything LOL.
Sometimes, if I go out of Bluetooth range at home, the home wifi will kick in, but repeatedly get a message on the watch that the forwarding function failed.
I'm definitely keeping this baby, but just need a little help in understanding it fully.
Click to expand...
Click to collapse
With my S5 initially, Remote Connection would kick in after a few minutes out of Bluetooth range. But, when I was back in Bluetooth range, I would have to do what you are doing to drop RC. I had a Gear 2 Neo prior to Gear S, don't know if that was any issue. .I did a factory rest on S5 ( to get rid of root and some other things) , and now watch connects and disconnects to RC by itself and rather quickly. BTW, when in RC, all texts and calls to S5 do come to Gear S. If I were in your shoes, I might try to reinstall Gear on phone before wiping phone. IF you do wipe phone, Gear S will be reset during the pairing process, so you may want to back up your Gear S data prior.
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
jerrycycle said:
Op. Under settings-connections-mobile network, do you have it set to auto connect? On the phone side of things for Bluetooth settings, gear s contented to phone audio?
Click to expand...
Click to collapse
Yeah, all that was set, but I ended up wiping both the phone and the watch and everything seems fine now... Still loving the watch... wondering how they'll make the next one better..
I have read the threads here; but I think this is a different problem:
My BT connection is FINE, I can initiate phonecalls from the watch, etc; but it just suddenly stopped receiving notifications from my phone (Huawei mate 7, 5.1.1. stock, unrooted) AND sending data to the phone (i.e. UP movements/ steps data).
I have already uninstalled ZenWatchwithout any effect) and BT is connected (according to wacth and AndroidWear)
Restarting phone/ watch, cleaning android wear/ UP cache/ data does not solve the issue; any other ideas what the culprit is, and how to solve it?
Do you have anything blocking or hibernating Google Play Services? Sometimes GPS crashes on my watch and I have to restart it before I'll get any more notifications. I imagine if something is preventing it from running it'll have the same effect.
Thanks for advice, I shall look into it. Suggestion from another thread was recent Android Wear update as culprit of this problem - I shall try to install an older version of AW as well..
Hello,
I'm testing Amazfit Bip since yesterday. To receive notifications I'm using Notify & Fitness for Amazfit. It works fine, but problem appears after reconnecting the watch. I mean - Amazfit losts the connection (for example if it's too far from the phone), somebody calls / sends a message, then Amazfit receives the connection back with the phone and shows no new notification. When it's connected again I don't get notifications for messages/calls received when connection was lost. The same is with Mi Fit application. Do you have any idea how to solve it?
The same here.
What firmware is on your watch?
Mr.kabas said:
The same here.
What firmware is on your watch?
Click to expand...
Click to collapse
V0.1.1.36
Only using third party apps, mostly paid ones. Some can detect that you lost connection and send the notification once the watch is connected. For instance, Notify & Fitness on PlasyStore.
you can try alert bridge on playstore, which is also free. Is not customizable as notify o similar apps (which however need to be paid), but if you don't pretend too much on notifications side, it does what you're looking for. give it a try
Hello all, I updated my iPhone to iOS 16 beta and my notifications are not working at all. I know there was a fix coming as an update for the Zepp app which I did (7.1.5) but I am still not able to get anything from my phone into my watch. Notifications, calls, nothing at all. I tried submitting a ticket to support but got no response.
Any help is appreciated, thanks.
Exactly the same problem here. iOS 16 (not beta) and Zepp 7.1.5 (was on Zepp 7.0.3 and it was the same). I have an old Bip in my desk drawer that I tried to activate instead of my Bip S Lite and it actually did receive notifications, until it very soon didn't anymore.
It also seems the watch disconnects itself from Bluetooth from time to time and won't reconnect until I open the Zepp app and do a sync.
I have a watch face that indicates if BT is connected or not, so that's how I know when it's disconnected.
So same problem on both Bip and Bip S Lite. And it seems those aren't the only models affected. There are reports coming from here and there.
Don MC said:
Exactly the same problem here. iOS 16 and Zepp 7.1.5 (was on Zepp 7.0.3 and it was the same). I have an old Bip in my desk drawer that I tried to activate instead of my Bip S Lite and it actually did receive notifications, until it very soon didn't anymore.
It also seems the watch disconnects itself from Bluetooth from time to time and won't reconnect until I open the Zepp app and do a sync.
So same problem on both Bip and Bip S Lite. And it seems those aren't the only models affected. There are reports coming from here and there.
Click to expand...
Click to collapse
Same thing is happening with the Bluetooth too. It gets disconnected and it does not reconnect at all.
Yeah I have seen reports from other watch users and some of them have already been able to fix it but I have tried everything so far with no success.
I have also tried factory resetting the watch(es), forgetting the Bluetooth bindings and uninstalling/reinstalling the Zepp app many times, but to no avail.
EDIT: Have now submiitted 3 reports via the Feedback function in the app. Each one more detailed than the previous.
The latest one:
Watch not receiving notifications and constantly disconnecting from BT.
iOS16, Zepp 7.0.3 and 7.1.5
-Problems started with iOS 16, I think.
-Notifications for Phone calls, WhatsApp, Gmail and SMS. None of them work.
-Watch keeps disconnecting from BT and will not reconnect until I open the Zepp app and do a sync.
-Will not reconnect BT automatically after being out of range.
-I have tried every setting in the App itself and in the phone's settings.
-I tried my old Bip watch and it did show a notification, but only once. Then it too stopped receiving them.
-I have factory resetted both watches many times and uninstalled/reinstalled the Zepp app a couple of times.
-Have made the phone forget the Bluetooth binding many times.
Don MC said:
I have also tried factory resetting the watch(es), forgetting the Bluetooth bindings and uninstalling/reinstalling the Zepp app many times, but to no avail.
EDIT: Have now submiitted 3 reports via the Feedback function in the app. Each one more detailed than the previous.
The latest one:
Watch not receiving notifications and constantly disconnecting from BT.
iOS16, Zepp 7.0.3 and 7.1.5
-Problems started with iOS 16, I think.
-Notifications for Phone calls, WhatsApp, Gmail and SMS. None of them work.
-Watch keeps disconnecting from BT and will not reconnect until I open the Zepp app and do a sync.
-Will not reconnect BT automatically after being out of range.
-I have tried every setting in the App itself and in the phone's settings.
-I tried my old Bip watch and it did show a notification, but only once. Then it too stopped receiving them.
-I have factory resetted both watches many times and uninstalled/reinstalled the Zepp app a couple of times.
-Have made the phone forget the Bluetooth binding many times.
Click to expand...
Click to collapse
I have also done all that and nothing has worked.
Mine started on iOS 16 beta before 16.1 like the update before it and it broke. First time I updated to the beta it was working fine but then the one right before 16.1 that’s where everything started.
Got an update to the Zepp app on my iPhone yesterday (v. 7.1.6) but it doesn't seem to have made any difference. Still no notifications.
I'm beginning to think the problems have something to do with how iOS16 handles Bluetooth connections. The bug is either in iOS16 or in the watch Firmware (although other Amazfit models are affected too).
I base my asumptions on the fact that the watch has trouble reconnecting to BT after being out of range or after it's been restarted. If I restart the phone, however, the watch usually gets connected.
So if it is the phone that initiates the connection, it usually works. But if the watch itself tries to connect, then it doesn't work.
But then again, the notifications do not work even if I keep the Bluetooth window open on my phone and the watch is 100% connected when a message arrives. Strange.
There is also something weird when I make the iPhone forget the BT pairing to the watch. It usually immediately rediscovers the watch and tries to pair again. This happens even if the watch is set to NOT be discoverable.
Just got another Zepp update in the App Store. 7.1.7.
Still no cigar.
There will be no more Huami watches in this household.
Don MC said:
I'm beginning to think the problems have something to do with how iOS16 handles Bluetooth connections. The bug is either in iOS16 or in the watch Firmware (although other Amazfit models are affected too).
I base my asumptions on the fact that the watch has trouble reconnecting to BT after being out of range or after it's been restarted. If I restart the phone, however, the watch usually gets connected.
So if it is the phone that initiates the connection, it usually works. But if the watch itself tries to connect, then it doesn't work.
But then again, the notifications do not work even if I keep the Bluetooth window open on my phone and the watch is 100% connected when a message arrives. Strange.
There is also something weird when I make the iPhone forget the BT pairing to the watch. It usually immediately rediscovers the watch and tries to pair again. This happens even if the watch is set to NOT be discoverable.
Click to expand...
Click to collapse
My apologies for my absence, I am not getting any notifications and honestly lost hope on this. I understand that this is something that might take time but 3 updates later, no real resolution or acknowledgment of what is actually happening.
I also believe that this issue has to do with the connection that the app has with the iOS16 beta since it started after an update. I got beta going, and everything was going smoothly, received an update and everything went south after that with no success or real connection whatsoever.
I just updated the app to 7.1.7 as you did and still the same, the only difference is that it seems the connection is more stable as it has not been disconnected yet and still shows connected without any issues.
I have not encountered the situation you are experiencing in that even if you unpair the watch the phone forces the connection again.
Indeed, I think this will be my last Huami watch. My wife is dying to update to iOS16 but I have warned her multiple times not to since it will break the connection.
Right now I just feel I have a regular watch that I have to charge in order to see the time...
It’s not the iOS beta. I was on the official 16.0 to 16.0.2 and the problem was there. Jumped on the 16.1 beta to try to solve it, but no luck there either.
Threw my Amazfit in my desk drawer and bought myself a Withings Scanwatch.
I finally am able to receive my iMessages on my Amazfit GTR4. On the Notifications in iPhone, go to Messages, and make sure in the Lock Screen Appearance-->Show Previews-> When Unlocked. Mine had changed to Never, as soon as I changed that and synced the Zepp app, now my messages are going through to my watch! Just thought I'd share what worked for me.
Seems that the Zepp app version 7.2.1 has fixed the notifications on my watch. They took their time, I might say.
...aaand then I updated my phone to iOS 16.1.1 and the watch (Bip S Lite) stopped notifying again.
EDIT: My Amazfit Bip on the other hand seems to be notifying just fine. Think I'll be using that one for now.
It definitely seems like the Bluetooth on my Bip S Lite is broken somehow. It won't automatically reconnect after it's been out of range/disconnected. I have to manually open the app to connect it again. And still no notifications.
I've contacted both the seller of the watch and Amazfit. Let's see if they have anything to say about it. I'm using the old Bip for now.
Dusted off my old Bip S Lite and paired it to my phone (or rather reactivated it, since I never did unpair it). To my surprise, it updated its firmware (to 2.1.1.86). Will try it and see if the notification issue is gone.