Anyone else seeing this? After the last couple updates to gear manager, when the watch goes too far away and loses connection, often Gear Manager doesn't try to reconnect automatically like it always used to do.
mhoepfin said:
Anyone else seeing this? After the last couple updates to gear manager, when the watch goes too far away and loses connection, often Gear Manager doesn't try to reconnect automatically like it always used to do.
Click to expand...
Click to collapse
I noticed the exact same thing.
I have to open GM & manually tell it to reconnect. It sometimes takes three of four times before it actually connects without timing out.
same thing for me, after the update last week or so it doesn't auto-reconnect anymore...as a work-around, i ended up making a tasker profile to connect to the gear when its not connected...
So I've got a new Samsung Gear Live from the Play Store. I'm attempting to pair the device to a Nexus 5 running stock 4.4.4.
When I turn on the Gear Live I'm prompted with selecting a language. I choose English US. Then i'm taken to the "Install Android Wear on your phone" Screen
At first this screen would show me the text "Gear Live 4AFV" (or something along those lines). However 9/10 (after rebooting or resetting the watch) it will simply show me "Gear Live" no 4 digit name.
Without the 4 digits showing the phone will not detect the bluetooth device to connect. On the off chance that it does show up and the phone is able to detect the watch, the pairing process can either work, or stall leaving both devices sitting at a "wait a moment while pairing" screen that never ends.
Lastly, if everything works and i'm able to pair the watch and phone. it will randomly disconnect and nothing I do will make it reconnect to one another.
Other things to note. Bluetooth has no issues on my phone with any other device.
I've reset the watch numerous times,
I've uninstalled the Android Wear app as well as any other watchfaces or launchers.
I've factory reset the phone.
Suffice it to say i'm almost certain there is a problem with the watch, the question is has anyone else experience this or anything similar with a Reset hasn't fixed the problem and is there possibly a solution to this problem that isn't a replacement.
Google has offered to replace the watch but I want to ensure I"m not missing something here.
thanks for any assistance in advance.
gear live 5.0 lollipop connection issues
jay slasher said:
So I've got a new Samsung Gear Live from the Play Store. I'm attempting to pair the device to a Nexus 5 running stock 4.4.4.
When I turn on the Gear Live I'm prompted with selecting a language. I choose English US. Then i'm taken to the "Install Android Wear on your phone" Screen
At first this screen would show me the text "Gear Live 4AFV" (or something along those lines). However 9/10 (after rebooting or resetting the watch) it will simply show me "Gear Live" no 4 digit name.
Without the 4 digits showing the phone will not detect the bluetooth device to connect. On the off chance that it does show up and the phone is able to detect the watch, the pairing process can either work, or stall leaving both devices sitting at a "wait a moment while pairing" screen that never ends.
Lastly, if everything works and i'm able to pair the watch and phone. it will randomly disconnect and nothing I do will make it reconnect to one another.
Other things to note. Bluetooth has no issues on my phone with any other device.
I've reset the watch numerous times,
I've uninstalled the Android Wear app as well as any other watchfaces or launchers.
I've factory reset the phone.
Suffice it to say i'm almost certain there is a problem with the watch, the question is has anyone else experience this or anything similar with a Reset hasn't fixed the problem and is there possibly a solution to this problem that isn't a replacement.
Google has offered to replace the watch but I want to ensure I"m not missing something here.
thanks for any assistance in advance.
Click to expand...
Click to collapse
I have the same connection issue but not until I updated it to Android version 5.0 that I started to get connection issues and the gear live was constantly doing a sync loop and it would not stay connected or send SMS messages.
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.
Hi all.
Yesterday evening I did a Play Store update via WiFi at a friends and afterwards the WiFi would turn on by itself. I noticed it because I kept getting the connection is unstable message after I manually turned WiFi off. The phone was trying to connect to a neighbor's open network that is just out of range.
This is the second time I've seen this problem and I'm assuming that since both phones were unrooted stock with all the bloatware disabled in app manager that the problem was with one of the 20 plus apps that updated. I uninstalled all the downloaded apps but it had no affect on the problem I went through all the settings for networks and didn't find any changes. What's the chances that one of the apps I downloaded was compromised. It freaked me out so much I hard reset the phone both times. I currently have set the Play Store to manual updates only so I can catch the culprit if it happens again my questions are is there way to view a log of what uses the the WiFi ? And how can I prevent this kind of problem in the future. And has this happened to anyone else?
Thanks much for your time and consideration
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