I was able to connect my S6 Edge to my Toyota Corolla 2014.
The car system tries to read the contact list and the call log from the phone, but the call log is not sent to the car.
As a result the Bluetooth app stops and starts again in an endless loop and I get the "Bluetooth has stopped" message.
Re-pair, reboot, stopping the app on the phone, clearing the app data - nothing solved the problem.
Everything is OK with my old S5.
Could not find anything on google.
Any ideas.
I have the same model car. Go into your phone's settings and turn off the call and contact sync. Also do this in the Corolla's bluetooth settings. It should be fine after that.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
I think this phone might actually have some Bluetooth issues. My Moto 360 keep getting disconnected. I used HTC One M8 before and never had this issue.
Sent from my SM-G925F using XDA Free mobile app
aerodrew said:
I have the same model car. Go into your phone's settings and turn off the call and contact sync. Also do this in the Corolla's bluetooth settings. It should be fine after that.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your response.
I tried to turn off the Contacts and Phone log before the phone was connected to the car. Then after it was connected I turn it "On" again, The car was refreshing the list and everything was OK. Now I have to see what will happen next time I come back to the car and connect.
BTW: were you able to connect MirrorLink to the car and be able to run apps from the car screen? when I connect with a USB cable, my phone says connected but I can not run apps and there is nothing on the car screen.
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.
When I start up the omate it goes to the watch face. If I try to go into any launcher with wifi turned on the watch pops and then powers off suddenly. If I put it in airplane mode it will run fine. I can turn bluetooth on and it will continue to run. If I turn on wifi the watch shuts off.
I read another thread where turning off quickboot and then restarting the watch should help wifi/bluetooth behaviors. This did not help me. Has anyone else exprienced this or have a suggestion how to fix it?
My firmware is 20140120
I've had this watch less then 12 hours and can't even make it work well enough to try it out.
You received a defective watch. If you have already opened it, you might see something obvious wrong in the assembly, like maybe a mis-connected antenna, or more likely not.
Getting a replacement for your defective TrueSmart will take some time, if it turns out to be possible at all.
Sent from my Nexus 5 using Tapatalk
So it turns out it isn't wifi it is the Fleksy keyboard. I disabled Fleksy and was able to type in the Wifi password and connect.
Very odd issue for sure.
You mean when Fleksy is enabled, trying to enable WiFi shuts down your watch, but if you disable Fleksy then you can enable WiFi and your watch does shut down ?
I also had a horrible time trying to use Fleksey to enter my password. I gave up and connected a Bluetooth keyboard.
Sent from my Nexus 7 using Tapatalk
trent999 said:
You mean when Fleksy is enabled, trying to enable WiFi shuts down your watch, but if you disable Fleksy then you can enable WiFi and your watch does shut down ?
I also had a horrible time trying to use Fleksey to enter my password. I gave up and connected a Bluetooth keyboard.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That is what I meant.
Upon even further tinkering with Fleksy disabled I've found what I think to be the actual issue....
The speaker crashes the watch.
Fleksy made noise when I tried to type and crashed the watch.
Loaded Google Hangouts, got a message and the watch crashed.
Loaded Pandora, started a music station and the watch crashed
Set an alarm and when it went off the watch crashed.
Has anyone else seen this issue or read about it?
TCommander said:
That is what I meant.
Upon even further tinkering with Fleksy disabled I've found what I think to be the actual issue....
The speaker crashes the watch.
Fleksy made noise when I tried to type and crashed the watch.
Loaded Google Hangouts, got a message and the watch crashed.
Loaded Pandora, started a music station and the watch crashed
Set an alarm and when it went off the watch crashed.
Has anyone else seen this issue or read about it?
Click to expand...
Click to collapse
Sounds like you have a speaker wire grounding. ive tryed everything that you mentioed on my own ts and i can not replicate it.
Does anyone have solution and time auto sync problem in omate? When I shutdown the omate and restart it after several hours, its lost the time and need to connect to the Internet to reset time again? Also the problem of auto on/off, it also closed on time but not resart automatically in the setting time?
Sent from my GT-I9502 using XDA Free mobile app
elsabea said:
Does anyone have solution and time auto sync problem in omate? When I shutdown the omate and restart it after several hours, its lost the time and need to connect to the Internet to reset time again? Also the problem of auto on/off, it also closed on time but not resart automatically in the setting time?
Sent from my GT-I9502 using XDA Free mobile app
Click to expand...
Click to collapse
This topic has been covered already in other threads on XDA, but I will recap for you.
Omate decided not to include a tiny clock backup battery in the TrueSmart maybe due to size issues or cost or both. This means that when the watch is powered off, the clock stops. Yes, this was considered acceptable by Omate for a SmartWatch 2.0, that it cannot keep time while powered down.
When the watch powers up again, the clock will continue from when it was powered off until it is reset by hand or updated via wireless carrier if you have a sim in or until it connects to a Network time server via WiFi or however. It will keep time more or less accurately from then on, until powered off again, at which point it stops like an old electric clock unplugged from the wall socket.
There is no solution to this, as the hardware does not support the equivalent of a regular cheap Casio style real watch.
Sent from my XT1028 using Tapatalk
I have two Gear Fits connected to two non-Samsung phones (Nexus 4 and a Sony Xperia Z Ultra). Both have the same issue where most notifications will not show details, but just a message of: "For details, view this notification on your mobile device."
There seems to be no consistency of when I may or may not get details. Sometimes it shows it for a bunch of notifications in a row, but once it stops working, I have no idea when it might start working again. Anybody else have this problem and any ideas?
Additional info:
Gear Fits on firmware NG2, Gear Fit Manager 1.70
I have the same issue as well and no idea why it happens, I usually try to restart the phone and I think it gets back to working
Sent from my Nexus 5 using XDA Free mobile app
I used to have this issue. It occurs when the host fit is connected back to the device after any loss of connection. The guy works everytime. Once you connect fit to phone, go to gear manager app, notifications, use the switch at the top to turn off all notifications. Wait 5 sec, turn notifications back on. Will be fine until next time fit disconnects. So repeat with each connection.
Sent from my Nexus 5 using XDA Free mobile app
solve the problem
When u lose connection
Close bluetooth
Open bluetooth
Open the gear manager app
I use automatelt to automate that to reconnect and fix that problem
Works 99% of the time
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..