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...
Related
I've tested this with a3.5, Xron and Miui and they all get this problem. Maybe installing certain apps trigger this to happen but wifi will eventually slow down when trying to connect to a signal and will be essentially non functional since the OS will basically freeze and then tell you to force close wifi and it requires a wipe and fresh install to fix.
Has anyone else run into this problem?
Check this and see if it helps you.
http://forum.xda-developers.com/showpost.php?p=20863566&postcount=14
StEVO_M said:
Check this and see if it helps you.
http://forum.xda-developers.com/showpost.php?p=20863566&postcount=14
Click to expand...
Click to collapse
I don't think its the same issue. In those instances you can still try to change which wifi signal you want to connect to, I think it just loops from connecting and it would disconnect. I think this issue is common and dropped connections occur as well.
But I'm talking about a situation where if you even try to enter the wifi options it will force close.
iamsamsamiam said:
I don't think its the same issue. In those instances you can still try to change which wifi signal you want to connect to, I think it just loops from connecting and it would disconnect. I think this issue is common and dropped connections occur as well.
But I'm talking about a situation where if you even try to enter the wifi options it will force close.
Click to expand...
Click to collapse
Before I changed it, it would take forever to get it to release the connection. I just kept hitting "Wait" rather than "Force close" it would take several minutes but would eventually come up and allow me to Forget the network.
It sure sounds like the same, not saying it is, but very similar.
I experienced this problem for the first time yesterday in area where was about 20 WIFI networks. Never ever it happened in my house on A2. A3 A3.5 or XRON2.8
http://rootzwiki.com/topic/13779-now-i-believe-that-there-is-wifi-problem/
I have the same issue today, Wifi setting is forced to close, and cannot connect to any Wifi signals. I think it's a bug and it related to the time or date. Because I didn't do anything and it just happened.
No new apps install, no setting changed, and the device was keep on, so it just happens.
Hope someone can find out where the problem is...so sad this happen on New Year's eve....
i have this problem also, the solution i found was letting the touchpad go dead and than begin to connect wifi again.
Similar wifi comments here: rebooting [or maybe toggling/other disconnect] with wifi on/remembered would get it into a state where it was scanning and connecting over and over without really ever working. this was only happening once it was 'remembered'. Going through the wifi settings to forget in this state involved hitting 'wait' a few times and then i'd reboot and readd. 1st wifi connect is always solid for me.
I've found: market.android.com/details?id=com.brilliapps.wifiandmorefixer
Does the same thing except it is one click. I rebooted after the first go, but now no longer. i run this and then readd wifi - all set.
Im on null 07 and when I reconnect the gear through gear manager it wipes all the apps off my watch even when i tell it not to. Is there any way to stop this?
billymaloney3 said:
Im on null 07 and when I reconnect the gear through gear manager it wipes all the apps off my watch even when i tell it not to. Is there any way to stop this?
Click to expand...
Click to collapse
Do you mean when it tries to connect to the gear manager initially (setup)? Or when it tries to do reconnect after loosing Bluetooth connection? Because that is the way it works by design
Brendo said:
Do you mean when it tries to connect to the gear manager initially (setup)? Or when it tries to do reconnect after loosing Bluetooth connection? Because that is the way it works by design
Click to expand...
Click to collapse
its when it connects initially, but sometimes I just get disconnected from the manager out of nowhere and then i have to wipe.
billymaloney3 said:
its when it connects initially, but sometimes I just get disconnected from the manager out of nowhere and then i have to wipe.
Click to expand...
Click to collapse
Well, setting up in gear manager always requires a reset - nothing can be done about that
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 everyone I have a little problem with my smartwatch a Samsung gear S3 and my brand new mi9 t, I pair it without any problem but it keeps disconnecting, there is for sure some setting that I'm not seeing, usually in the morning I bike and I need the gps Wich from mine understanding is given through my phone, it keeps showing acquiring position without any success I have already set the phone on the task manager so it's not going to kill the process and it's going to leave the Samsung Gear app running in background but for some reason still keeps disconnecting and I'm not being able to get the GPS work, anyone experienced similar problem?