Database Develop

gear live connection issues

So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?

mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
All righty then, I guess its me

mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.

Komodo Rogue said:
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Click to expand...
Click to collapse
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features

mstrpeter said:
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
Click to expand...
Click to collapse
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.

freekyfrogy said:
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
Click to expand...
Click to collapse
Well I swapped to omnirom as well and sure enough, operation has been perfect. I also noticed while looking at obd2 apps that one had mentioned bluetooth connectivity issues on CM...
so i'd say, SOLVED.

My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.

jeffcrilly said:
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
Click to expand...
Click to collapse
The same exact thing is happening to me, just one day started to get in a "Pairing Loop" continually asking me to pair the watch to my phone. Upon pairing successfully and syncing some notifications the connection gets broken and immediately a new parigin code appears.

UPDATE:
I'm back on cm11 and everything is working properly. The problem is not the ROM, its the Kernel that comes baked in. Currently using elementalX Kernel and no issues.

[Q] WiFi syncing

Hi all,
Purchased the watch couple days ago, yesterday was my first day to really put it through it's paces. Everything seems copacetic except for the WiFi syncing. I've got cloud sync turned on in the Wear app, and WiFi on the watch is set to "Automatic". I verified the watch is indeed connected to a valid WiFi network, with no exclamation points, etc., and I turn off BT on my phone (but keep it's data connection on.) I then try sending a text from the watch, no luck - "Try again from your phone." fail message. I send myself a text from my wife's phone to my phone, the phone registers it, but the watch doesn't. I go into Keep and delete a note on the phone, the watch still shows it. It's not until they reconnect via BT that everything syncs again. Oh, and I tried it on three different WiFi networks (2 at work, 1 at home), no success.
Here's the only thing that I can think of being different. The very first time I turned WiFi off on the watch, there's was a small Yes/No splash screen that came up saying something to the effect of "turning this off will prevent you from syncing"... I THINK. Honestly I can't recall what it said precisely (I was too excited playing with the watch), but the multiple times I've toggled WiFi since then, I have not seen that message again. Anyone know what message I'm talking about? Of course since it hasn't come up again I'm convinced it's the reason WiFi syncing isn't working now. I even factory reset the watch and cleared the data on my Wear app, hoping to get that message back. (It could be completely unrelated, it's just bugging me that ever since I chose "Yes I'm sure", syncing has not worked.)
Thanks in advance for any ideas/suggestions.
James

SyrinxPriest said:
Hi all,
Purchased the watch couple days ago, yesterday was my first day to really put it through it's paces. Everything seems copacetic except for the WiFi syncing. I've got cloud sync turned on in the Wear app, and WiFi on the watch is set to "Automatic". I verified the watch is indeed connected to a valid WiFi network, with no exclamation points, etc., and I turn off BT on my phone (but keep it's data connection on.) I then try sending a text from the watch, no luck - "Try again from your phone." fail message. I send myself a text from my wife's phone to my phone, the phone registers it, but the watch doesn't. I go into Keep and delete a note on the phone, the watch still shows it. It's not until they reconnect via BT that everything syncs again. Oh, and I tried it on three different WiFi networks (2 at work, 1 at home), no success.
Here's the only thing that I can think of being different. The very first time I turned WiFi off on the watch, there's was a small Yes/No splash screen that came up saying something to the effect of "turning this off will prevent you from syncing"... I THINK. Honestly I can't recall what it said precisely (I was too excited playing with the watch), but the multiple times I've toggled WiFi since then, I have not seen that message again. Anyone know what message I'm talking about? Of course since it hasn't come up again I'm convinced it's the reason WiFi syncing isn't working now. I even factory reset the watch and cleared the data on my Wear app, hoping to get that message back. (It could be completely unrelated, it's just bugging me that ever since I chose "Yes I'm sure", syncing has not worked.)
Thanks in advance for any ideas/suggestions.
James
Click to expand...
Click to collapse
Did you ever figure this out?
I have the LG WATCH R with the Urbane rom and have the same issue. It shows connect to Wifi just fine but if I am away from the phone, I cannot send anything...just like when I have no connection.
I think the pop up you mentioned just had a option to prevent the warning from coming up again but should not affect the option to disable and enable the cloud sync.

Nope, afraid not. I posted it to the Google Android wear forums and a couple of "experts" replied to me with suggestions that did not help (factory reset, mainly.)

SyrinxPriest said:
Nope, afraid not. I posted it to the Google Android wear forums and a couple of "experts" replied to me with suggestions that did not help (factory reset, mainly.)
Click to expand...
Click to collapse
Yep that has been my "solutions" too so far. I am not sure how the Cloud Sync works do you? It is linked to your Google account? If so, I have 3 email accounts..could that create an issue? I am basically looking for anything right now

Here's what I did find out: my daily driver phone is a Moto X 2nd gen running Lollipop. I factory reset an old Samsung S4 and set it up with a Google account I'd just created. I then factory reset the watch and paired it to that phone. Wouldn't you know, the WiFi notifications worked!
I then factory reset the S4 again, this time using my main Google account to set it up. Factory reset the watch again also. After pairing them, the WiFi notifications did NOT work!
So, I can only conclude the issue is caused by how I have my main Google account configured, although right now I've gone through all the settings twice and verified that I have all of my sharing settings (like location) enabled. Argh.

SyrinxPriest said:
Here's what I did find out: my daily driver phone is a Moto X 2nd gen running Lollipop. I factory reset an old Samsung S4 and set it up with a Google account I'd just created. I then factory reset the watch and paired it to that phone. Wouldn't you know, the WiFi notifications worked!
I then factory reset the S4 again, this time using my main Google account to set it up. Factory reset the watch again also. After pairing them, the WiFi notifications did NOT work!
So, I can only conclude the issue is caused by how I have my main Google account configured, although right now I've gone through all the settings twice and verified that I have all of my sharing settings (like location) enabled. Argh.
Click to expand...
Click to collapse
Interesting. I will play with that next. Annoying as hell too though

shaolin95 said:
Interesting. I will play with that next. Annoying as hell too though
Click to expand...
Click to collapse
Well my LG Watch R is now able to work with Wifi for real but only at home. Not sure what I did...I just deleted my accounts from Settings and added them back.
At work, though even when it shows connected, I do not receive any info from the Phone which is very lame since it was at work where I could really use it.

shaolin95 said:
Well my LG Watch R is now able to work with Wifi for real but only at home. Not sure what I did...I just deleted my accounts from Settings and added them back.
At work, though even when it shows connected, I do not receive any info from the Phone which is very lame since it was at work where I could really use it.
Click to expand...
Click to collapse
Cool! Can you tell me what you mean by "deleted my accounts from Settings"? I want to test it too.

SyrinxPriest said:
Cool! Can you tell me what you mean by "deleted my accounts from Settings"? I want to test it too.
Click to expand...
Click to collapse
I have 3 google accounts so I actually deleted only two that are not my primary. Then I went to the Sync options and made sure all was checked.
Then also for the Location I removed any other devices that are showing under my account that are not my Phone (tablet and older phones) but not sure which one of those did the trick.

shaolin95 said:
I have 3 google accounts so I actually deleted only two that are not my primary. Then I went to the Sync options and made sure all was checked.
Then also for the Location I removed any other devices that are showing under my account that are not my Phone (tablet and older phones) but not sure which one of those did the trick.
Click to expand...
Click to collapse
Huh, okay, I'll give those a try. Thanks.
I did open a ticket with Android Wear Support and was told they were going to escalate the issue and I'd be contacted in 48 hours. That was Sunday. I just asked for an update and they replied that they have no solution ATM and no time frame to provide one. Heh! Oh well.

Android Auto didn't starts anymore in my car.

Hello everyone,
first I'm sorry for my english and hope you understand everything.
I'm using Android Auto since two years with the same smartphone a galaxy s8+ (Android 9) in my opel corsa e on an Intellilink R4.0 and most of the time it worked without any problems.
But since one week it didn't starts on the Intellilink.
The last systemupdate from my galaxy was something about four weeks ago and in the mean time everything worked fine.
Each time i connect my Smartphone as usual with the car the Android Auto App shuts down and in the smartphone notification it says that Android Auto is connectet but the Intellilink didn't starts Android Auto. It only offers me to change to my Galaxy s8+ but without any result. If i try to start the Android Auto App (while the smartphone is connected to the car and i tryed it once to change to the galaxy) the "Android Auto" app shuts down immediately.
I deleted the bluetooth-connection in my smartphone and in the car and reconnected both.
I deleted the cache & AppData from "AndroidAuto", "Google Play Service" and from the "Google App".
i deleted and reinstalled the Apps.
I also tryed to use two older versions from those Apps because i thought i updated them recently before it didn't worked anymore but without any success.
I tryed three different USB-cabels...
The data-transfer to my pc works so the USB-Port from the galaxy is okay. no one in my circle of friends has a Android Auto compatible car so i can't test it there.
Somewhere i could read that it could help to enable and disable the usb-debuggin in the devolopmentmode in the galaxy but it didn't helped.
Then i disconnected the Car Battery to make a Hardrest in the Intellilink and again no success.
Confusing was that last thursday on the way home, past 20min of connection and driving it suddenly started in my car and i could use everything as usually (Voice, Maps, Spotify).
But when i arrived home and disconnected the smartphone to try it once more it didn't started.
Till Today i didn't get it to work and i dont know what problem it could be or what else i can do.
The galaxy isn't rooted i don't want to root it.
Once i had a similar problem and some App updates fixed the problem so i'll wait for an update from "Android Auto", "Google-Play-Service" and the "Google App" to try it this way before resetting the galaxy to factory settings.
But I hope that someone can help me and has another idea what i can try to do.
with best regards
xman1985

I have the same issue with my s9 on my astra. I might have a solution. Every time u connect your phone to your car and the after the notification in your phone comes saying android auto is connected go to photo gallery, search for any random video if u have in your app. Play it n hit back/return key on your phone. Yes its a bit of a struggle but mine one works every time i do this . Looks like a bug

samuhang said:
I have the same issue with my s9 on my astra. I might have a solution. Every time u connect your phone to your car and the after the notification in your phone comes saying android auto is connected go to photo gallery, search for any random video if u have in your app. Play it n hit back/return key on your phone. Yes its a bit of a struggle but mine one works every time i do this . Looks like a bug
Click to expand...
Click to collapse
Thanks,
I'm not sure if its just a coincidence but i tried it and it realy works that way.

xman1985 said:
Thanks,
I'm not sure if its just a coincidence but i tried it and it realy works that way.
Click to expand...
Click to collapse
Hi ive found out today that downgrading your aa to
4.6.593334-release (arm64-v8a works without going to gallary app n playing a video. But first just clear data of your aa before unintalling it than intall the above mentioned ver from apkmirror . Com. Have a nice day

Question First smart watch. Having issues with Watch Face Studio. Can't test or use my own face.

Just got a GW5 Pro and thought I'd have a play with WFS so I can have everything match. After a day of learning things I hit a wall where I couldn't find the info on complications I was after. I thought the best way would be to just take a best guess approach and just test the face and see. Here's where the problem happened.
Attempt 1:
I followed the instructions on connecting my watch to the PC WFS for testing. The software couldn't see my watch. I tried multiple times turning all the settings off and on again and going through the steps 1 by 1 and double checking what I was reading.
Attempt 2:
After giving up I went through the instructions for instead using my phone (S23 Ultra) connected to my PC via USB cable, connect to GW5 with bluetooth. Seemed easy enough until I hit the issue of turning on bluetooth debugging on my phone. I looked everywhere for it, it doesn't exist. I could see my phone in WFS but not my watch.
Attempt 3:
Third attempt was to just "build" the face and load it manually. It gave me 2 files APK and AAB, I put them in a shared folder and installed the APK on my phone through the network. After a couple of security warning popups it finished and it didn't do anything that I can see. I tried copying both the files onto my phone and reinstalling the APK. Still no luck.
So, after trying 3 different ways I'm lost as to what to try next. There's no point spending more time on building my custom watch face if it's not even possible to use it.
Thanks heaps in advance for the help and suggestions.

this is interesting, because from what I've tested (totally basic level, to be fair), I've got MOST issues with signing apk file. After that it went well.
If you cannot see your watch in debugging mode, delete their remembered ID and try to connect again. That trick helped me few times, when installing ECG workaround.

I'm completely new to this, what do you mean by "delete their remembered ID"?

in other words, maybe "unpair" or "forgot" your watch will be better word to this? Don't know exact words, because I'm using watch studio in my native language (which isn't English).
I remember that I've got similar issues and had to completely remove watch from known devices in watchface studio.

Its currently only paired with my phone. I tried turning BT off on my watch , then turning on wifi, connecting to my home wifi (turning on adb debugging and debug over wifi). Hit scan on my PC, nothing. Entered the IP address of my watch, nothing.
Idk if unpairing would help if I have BT off. Would it muck anything up unpairing and repairing?

Some warning that if you unpair from the phone you HAVE to do a complete wipe of all data on your watch before you are allowed to pair it back again would have been nice to know.
So after that my PC can still not see my watch over wifi.

Question Watch 5 pro google cloud sync issues

This has bothered me since long time, on several wear os watches. Problem is the following:
I have currently a samsung fold 4 and a samsung watch 5 pro LTE (but i've had the problem on other devices too in the past, al wear os devices).
When the watch is connected through bluetooth there is not a single issue. If i have my phone on the table for several hours, while not touching it, all notifications are instantly pushed to the watch, no delays.
However, when i leave my phone at home and going out with my watch only, it will correctly switch over to LTE connection and there the problems start. When my phone is recently used (few minutes ago) the watch can establish a remote connection. At that moment al notifications are pushed to the watch, almost no delays. However, after a while, usually within 30 a 60 minutes the notifications start to be delayed, and even the remote connection just stops (seeing the disconnected symbol on the watch). also sending messages or replying them on the watch is instantly and correct at first, but starts to fail after a while.
It seems like the google cloud sync service is killed after a while on the phone, preventing the forwarding of phone notifications to the watch over LTE (cloud sync). I tried everyting on my samsung phone, changing the battery optimizations of all samsung wearable apps and plugins, google apps, play service etc... I turned of as many battery saving features i could find on my phone, but no luck. If i leave the phone on the charger, the cloud sync keeps working for a longer time, but agian, ofter some time it will slow down, starting with unablity to reply or send messages from the watch, to complete disconnection... Al this while the internet connections on the phone and watch are rock stable...
Has anybody any clue why this happens?? Is there some trick or setting i overlooked? Does anybody know which app or service on the phone (samsung) is responsible for this google cloud sync?
again, this is not only on this phone-watch combo, i had several wear os watches from different brands in the past, but mostly samsung flagship phones. I cant believe that two samsung devices are not software optimized so these issues cant happen... I always bought LTE watches so i could go for a run or go to the gym phone free, is brilliant when it works, but VERY annoying when it usualy is not reliable.... I'm thinking even to switch to the apple camp, hoping those issues are not present on apple watch cellular... But i like samsung devices more then iphone ....