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
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.
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
Click to expand...
Click to collapse
I'm not getting extended disconnects; just failing to answer questions about half the time. If it fails, I can try again and it often works.
mickmel said:
Many times when searching via voice I'm getting a "disconnected" error with a list of other things to tap (like when you tap the clock to see a list of actions).
The phone is within a few feet, on a solid wifi connection. Droid Maxx from Verizon, stock ROM. Watch is the LG G Watch, including the update that came out today.
Any thoughts?
Click to expand...
Click to collapse
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
I'm experiencing the exact same thing on my Gear Live. Its paired with stock S5. I just tried for like 5 minutes to get it to save a note and it would think for a while and then just disconnect.
mosi76 said:
I just got my LG G Watch and paired it with my stock Moto X running 4.4. It paired no problem but I would say 95% of the time I get a disconnected message when doing a voice search. It is pretty infuriating.
Notifications still seem to come through and I still get served cards but voice search fails almost all the time. When I initially went from Wifi to 4g it worked for one search and then back to disconnected. It doesn't seem to be a phone problem since people on here are using a number of different phones. This is a bug that needs to get fixed ASAP by Google.
I am disappointed but hopeful they can get this quickly fixed.
Click to expand...
Click to collapse
This is exactly everything I've noticed as well.. Seems to have gotten waaaaay worse after yesterday's update
Azarin said:
My LG G watch seems to be encountering the disconnected error a fair amount as well. It is paired with a Nexus 5.
It appears the bluetooth link is going down between the two, while the phone shows the watch as being connected if I use the Android Wear app on the phone to disconnect and then reconnect it gets stuck re-connecting. Rebooting the watch lets it connect again.
On other occasions it has reconnected itself after a while.
EDIT:
PS. It is worth noting that the watch does NOT display the disconnect icon when this happens (usually if you walk out of range you get a little cloud with a line through it)
Click to expand...
Click to collapse
Happens to me, too. Completely random though. Repairing the watch fixes it, but it is indeed annoying. We will have to wait for Google to fix this together with all the other bugs.
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Thanks, I'll give it a shot.
What about trying to reply using voice within a received Hangout or email? I'm always getting an error "Can't reach Google at the moment". Am I the only one? But if I select a default reply from the available list, I can reply with no problems...
iHelp101 said:
I found a small fix for this issue if anyone still needs help. I just set a tasker task to disconnect and reconnect bluetooth every hour. I haven't encounter this issue after doing so. It takes about 10 seconds and works great for me.
Click to expand...
Click to collapse
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
I found it only improves it a little, but it's not a full fix. Sometimes my watch works the whole day without connection problems and then suddenly multiple times in a short period of time.
I've read that the gear live has the same problem, so I guess it's android wear wide. Hopefully google is going to bring out an update soon which fixes all the annoying bugs.
barkside said:
Nice idea, however it doesn't fix the issue for me (I bought Tasker specifically for this). Is this still working for you, or is it just improving things slightly?
Trouble is I don't use the voice search in public often (people stare!), but when I do want to show-off my watch's features, it fails - I look like a nob! Anyone found any sign that Google are looking at this? Does the Gear Live have this problem?
Click to expand...
Click to collapse
Like stated by the previous post this is a simple fix. The only one that can truly fix the issue is Google. I have used this for a week and not had any issues relating to bluetooth disconnecting. One issue I noticed was Google Search sometimes breaks after using it multiple times in a short amount of time. I usually have to just force stop Google Search every 3 days also.
This has always been an issue I had even before Android Wear. If I used Google Now too much I couldn't get the "Okay Google" command to work. It seems this also happen when using wear too much. A simple force stop fixed it, but it is annoying when you want it to just work. Another thing I noticed was custom roms are having issues with Android Wear in my case.
Every time I use a custom rom on my Nexus 5 and try to use my LG G Watch I have constant disconnects and Google Search issues. Maybe Android Wear isn't playing nice with custom roms, but after using rooted stock for the last week I am experience very few issues compared to when using different custom roms. I noticed whenever I used a custom rom I got the "Connected, running sync loop". I have no idea if this causes the constant disconnects, but on stock with the simple "Connected" I have no issues.
I started out with the same problem using a Gear Live with a Sony Xperia Z1 Compact. The thing that fixed it for me was turning off battery saving mode on the phone - called stamina on the Xperia - that was turning off BT to save power. Now I rarely see the disconnected message.
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
SIlvRav said:
Anyone found a solution to this problem?
My lg g watch also disconnects 90% of the time from my note 4. Anything from ok google to search or ser a reminder or or or
Click to expand...
Click to collapse
I have found this issue for Android Wear for my LG G watch R and Galaxy Note 3. If I use watchmaker, I have it set to vibrate twice upon disconnect and vibrate once upon connect. It is constantly disconnecting and immediately reconnecting (2 vibrations, followed immediately by a single vibration). This is extremely annoying and I see the same problem stated in the beginning, the voice search is constantly disconnected or cannot reach the server.
Cheers,
B.D.
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 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.
Hi!
My Open Fit App keeps closing and then I need to restart the app and select my Google account again and give the app permission to use GPS etc. again. Since this is happening I am unable to get the notifications after the app has closed. And also I am not getting a notification on the Gear fit, that the bluetooth connection has been disconnected. I have selected Open Fit as a program that will not be closed when the screen is turned off.
In addition to the above the devices list is erased and then it is set as a default that google fit sync is enabled even though I disabled it before.
Any ideas?
Also I am unable to open the app from the notification panel. And the text in the notification panel says "Disconnected to Gear Fit", though its connected.