Related
ever since the Android Wear apps on my phone got updated to version 1.0.5.1785466 , my watch has been getting random "com.google.process.gapps has stopped" error ..
anyone else experiencing the same ?
EDIT : so after going through a rather painful day that involve several restart, connect and disconnect .. everything seems to be ok now .. hopefully just a bad update procedure ..
Yepp !
Many errors with this update.
Mine didn't synch steps with Google Fit anymore, even after full reset.
Same. I woke up this morning to the app being updated and it broke a whole bunch of things. WatchMaker for one. Its only my second day with this thing.
P.S. Try reverting the android wear app back a revision. Seemed to have fixed the issues. Also, determined the watch face doesn't work.
I've opened a ticket with Google. It's a bad update. I'm going to roll back a version using Titanium Backup.
It's really a bad update!
In my case this Android wear app update is DRYING my phone's battery (LG G2)
http://forum.xda-developers.com/android-wear/help/android-wear-app-version-1-0-5-1785466-t3060252
With my LG g watch R seems all OK...
Lorenzo
LG watch R No Longer Works Correctly after 1.0.5.1785466
Constant disconnect and battery drains. Android Wear doesn't display the watch faces anymore. Watch Maker no longer is work also. Performed Multiple factory resets on the watch and uninstall/reinstall Andriod Wear. NOTHING seems to work. Called Google and the Support person said there hand are tied and that the the Engineers are working on it. This watch is very expensive for it not to work make me extremely upset.
I 've had the Urbane for three weeks now, and I'm pretty pleased* with the watch except for a major problem:
I keep seeing that "cloud with a line through it" icon on top of the watch face way to often.
I'm actually looking at it right now - I'm at work, my Urbane is on my left wrist, and my phone is on the desk 20 centimeters away.
Since I haven't heard many others complaining about this, I'm suspecting the problem to be on the phone side - this is a "China phone", an Elephone P3000S (64bit, 3GB RAM) that I bought quickly as a cheap, but (on paper) good spec'd replacement for my broken Sony Z1 Compact.
But nevertheless, I thought I'd asked here if anyone else are experiencing the same?
I've factory reset the watch, I often reboot it, I reboot the phone even more often, and most of the time connection is re-established but lasts only for maybe 15 minutes up to several hours. I have disabled wifi on the watch to see if that improves things - initially I thought maybe it did (as long as I kept the phone nearby, of course), but after a while it seems it's not the case.
Anyone have any other tips? ...Before I replace the phone?
Thanks,
Christopher
*: of course I would prefer a brighter screen (when needed, i.e. outdoors), light sensor, better battery capacity, ...
Try to find out what Bluetooth version the phone has.
grenness said:
I 've had the Urbane for three weeks now, and I'm pretty pleased* with the watch except for a major problem:
I keep seeing that "cloud with a line through it" icon on top of the watch face way to often.
I'm actually looking at it right now - I'm at work, my Urbane is on my left wrist, and my phone is on the desk 20 centimeters away.
Since I haven't heard many others complaining about this, I'm suspecting the problem to be on the phone side - this is a "China phone", an Elephone P3000S (64bit, 3GB RAM) that I bought quickly as a cheap, but (on paper) good spec'd replacement for my broken Sony Z1 Compact.
But nevertheless, I thought I'd asked here if anyone else are experiencing the same?
I've factory reset the watch, I often reboot it, I reboot the phone even more often, and most of the time connection is re-established but lasts only for maybe 15 minutes up to several hours. I have disabled wifi on the watch to see if that improves things - initially I thought maybe it did (as long as I kept the phone nearby, of course), but after a while it seems it's not the case.
Anyone have any other tips? ...Before I replace the phone?
Thanks,
Christopher
*: of course I would prefer a brighter screen (when needed, i.e. outdoors), light sensor, better battery capacity, ...
Click to expand...
Click to collapse
ranf said:
Try to find out what Bluetooth version the phone has.
Click to expand...
Click to collapse
Guys,
Having the same problem as well..... I'm using a Nexus 6 with Bluetooth 4.1 which is also not so far away from my watch all the time..... Really don't know what's going on....
I don't have an Urbane watch (yet) but ran into this issue myself....I downgraded Android Wear on my phone back to 1..0.5 to fix my problem. To get the apk I am using now, see the link below. Before that, my watch would constantly disconnect from the phone for no reason. Best of luck to you all! The Urbane is the BEST looking smart watch out there IMO!
http://www.apkmirror.com/apk/google...roid-wear-1-0-5-1724356-android-apk-download/
Pietje_1985 said:
Guys,
Having the same problem as well..... I'm using a Nexus 6 with Bluetooth 4.1 which is also not so far away from my watch all the time..... Really don't know what's going on....
Click to expand...
Click to collapse
Same here. N6 running CM12.1. Bluetooth works perfectly with car, around home, other devices. I've tried every setting I can think of. Glad to hear I'm not the only one.
Have you tried enabling/disabling the wireless syncing option? I had similar initial issues, had to factory reset and I disabled Wireless Syncing (and deleted the cloud data).
I then setup the phone again and didn't enable wireless sync for a few hours so I knew the phone was setup and working only using Bluetooth.
I knew something was wrong as once the wireless Sync was disabled and the cloud info deleted, my watch said it had lost connection to the phone and I had to factory reset it (even through Bluetooth was enabled still).
I am having significantly more instances of Bluetooth disconnections on this watch that I did with the Moto 360. This especially occurs in my car while driving. I'd bet that the watch disconnects every 10 minutes or so in the car.
Same here ... I have an LG G3 running Lollipop with an LG Watch Urbane running v5.1.1 This is to replce my LG Watch R but these connectivity issues every 10 seconds is highly frustrating ... Looking forward to a permanent fix on this thread ...
I'm starting to see the same thing, no issue while both are on WiFi, but without WiFi my watch is constantly disconnecting. Normally rebooting the watch seems to fix the issue, but really hope this gets fixed soon.
If I get away from my phone watch disconnects, thats normal. But when I get close to phone again, it doesn't connect automatically, or connects too late. Is that normal? This is so annoying.
well im all good not had that at all i get about 25 foot then loose bt soon as im back in 25 foot im good
i have a edge
I have an SGS6 Edge and it is slow connecting. I've found it will connect instantly if I turn BT off and back on.
Has anyone tried using phones wifi terhering instead of bt connection? Maybe that extends the connection distance?
Seems like my problems are solved for the most part. Doesn't disconnect that often anymore. Could be because of recent update to Android 5.1.1 on my Nexus 6 and I factory resetted my urbane! Lookin' good now!!
How about you guys?
I have a Nexus 6P, and the disconnecting with my Urbane is beyond annoying. I'm starting to think that, despite the looks of the Urbane, the watch itself is a pile of poo.
Same issue here. Phone and watch constantly disconnect. If I walk 10 feet from my phone, it disconnects and doesn't reconnect when I come back within range of the bluetooth.
Pleased to report, though, that I went into Settings>Apps>Android Wear and cleared the cache and the phone has been reconnection pretty well. I have the LG V10 and the G3 before that and have found that you have the clear the cache on bluetooth connections every once in a while, and then things start to work smooth again.
Hope this helps someone out there.
I have been having the same problem since I got my new Nexus 6P. On my old phone, an Asus Zenfone 2, I would hardly ever lose connection. I might drop connection once a day. With my new phone, its about once an hour if I'm lucky. I just did a factory reset of both the phone and watch this evening, and so far it seems to have helped but I'm not going to call it fixed yet until I make a whole day without losing connection.
For what its worth, there are tons of people who are saying the BT on the N6P is boned, as well as a ton of people saying the same thing about the Urbane.
I have a Samsung Galaxy S6 and have both Bluetooth and Wifi connected to my LG Urbane however:-
If I go away from phone - within my own house AND well within Wifi range - it LOSES connections to BOTH Bluetooth and Wifi. (Bluetooth I can understand but how come it is losing connection to Wifi)?
Anyone got any answers please?
I have a weird problem with my Moto X 2014 (Pure Edition). It's randomly losing bluetooth connection in a background (basically any BT connection – to auto, smartwatch, etc.) but the phone itself says everything is fine (Bluetooth is on and devices are connected). But actual connection is not working: unable to play music via BT, unable to discover a new BT device, notifications not coming through to a smartwatch, etc. Bluetooth devices continue to show as connected even if I power them off, and when I turn them back on, they won't reconnect.
I meet this problem every 1-2 hours, sometimes even 10-20 minutes. The only way to fix this problem - to turn off BT and then turn it on again. Or keep Wi-Fi always off.
I tried to use another Moto X (2014, same software build version), to pair and unpair devices, to clean cache and even do a factory reset (with and without backup restoring) – the problem is still here. That's weird but this problem start appears 2-3 weeks ago, before everything was just fine.
Phone: Moto X 2014 Pure Edition @ T-Mobile, Lollipop 5.1 (TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US)
Devices: Pebble Time, Pebble Time Steel, Ford SYNC2, Moto Stream.
Things I tried that didn't help: deleting and re-pairing devices, deleting all old device profiles, clearing cache, reflash, factory reset, safe mode, flash CM12.
BT HCI Logs:
A disconnect at 1:28pm
dropbox.com/s/q3pka5egagq3e5g/01_btsnoop_hci.log?dl=0
A disconnect at at 3:09pm (or so)
dropbox.com/s/f2kl4rowr12lypt/02_btsnoop_hci.log?dl=0
Same issue here with a VZW XT1096, since OTA to 5.1. Factory reset does not help.
Up
Same issue here, same device & carrier & software build version & Pebble Time Steel. As long as I'm constantly making use of a BT connection, it seems to stay alive just fine, but as soon as it sits idle for more than a couple minutes, the connection drops (according to the BT device, but not according to the phone). I've tried all the same things with the same total lack of success. I have nothing new/helpful to offer, but at least you're not suffering alone.
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Just to say I have the same problem with a Pebble Time Steel and my 2014 Moto X. Have e to disable BT and dependable BT to get phone to connect to Pebble to only be dropped a few minutes later from Pebble side.
Lyre
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
I'm having the same problems and have also had it "go away" for extended periods of time only to reappear after a day or two. Mine will drop the BT connection even if I'm actively listening to audio over my headset.
Registered because I'm having the same issue. I'm running stock 5.1, no root. The connection to my Pebble Time Steel is very unreliable. The Bluetooth settings thinks it's still connected, the Pebble Time app on my phone thinks it's still connected, but my watch shows no connection and there's no communication to or from my watch. Sometimes it'll work for hours just fine and then drop, sometimes it'll only be a few minutes. It seems to be when the phone screen is off. Turning BT off and on always fixes it, it'll immediately automatically reconnect and show it on the watch.
I've tried the Pebble troubleshooting online (factory reset & recovery mode on watch, uninstall Pebble Time app, forget pairing on all devices, remove all other BT apps, reboot phone, reinstall Pebble Time app, re-pair) but the problem remains.
In the past, I've had it where my Fitbit One seems to have dropped the connection. Since the sync is so infrequent, I don't notice it much but I did catch it where it hadn't synced in a few days. (That app was uninstalled while I try to figure the Pebble thing out)
Next step is factory reset on the phone, but it sounds like that's not a fix for some people. That, or design a watchface that sends a keep alive signal to the phone, which runs an app to reset the BT when the connection drops. Since it's still listed as connected, I don't think Tasker will fix it.
Same issue. My phone is a Verizon Moto X and I've tried factory reset. Hoping that whenever they update to 6 that it will fix the issue, but I'm ready to smash my Moto x over this
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
While I hope your problem is "fixed" I would not be too hopeful. I have had this problem as long as I've had the phone. Sometimes it goes away for a while but it always returns. Right after I unlocked my bootloader and it did a complete factory reset the problem went away for a week but it eventually returned. I've seen similar problems reported with all the MX14 variations and nobody seems to have a solution. There was a thread on the Moto forums with folks reporting these issues to Moto but nothing ever came of it. Seems to be connected to wifi somehow because I don't seem to drop the BT connection if wifi is turned off. Not really a useful solution but it does seem to work. I just gave up and put a BT toggle button on my homescreen.
I had the same problem using marshmallow, I downgraded to 5.1 and it went to normal
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
jimbo0914 said:
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
Click to expand...
Click to collapse
Update: I changed over to Android M on CM13 and no longer have this issue. Nice not to have to power toggle the BT function a couple times a day anymore.
YMMV
Met the same problem after updating to Android M.
I often connect to BT during driving and after a few days working normally, my headset will be disconnect without any "notification".
My solution is to wipe cache, after that BT connection will work well for another few days.
Never met this issue in Android L, but I just love M so much.
Looking for better solution / fix.
I found this thread while searching for some solution for my BT+Android Wear problems. I have them since circa february / march 2017.
But today, I got a problem with non-Wear watch (Fossil Q Grant). I noticed my phone was locked even if I have smart lock set up. I checked fossil q app, the watch was connected, it received notifications so far. But in the phone settings, in smart lock, all my devices vanished. I checked the BT setting and saw the same. All my paired devices disappeared! It happened after nothing more than a restart, after my fossil lost connection earlier today and did not want to reconnect. So I restarted the phone.
This happened to me the second time already, but first time I somehow did not pay attention because I was frustrated by the Wear app problems and weekly factory resets to get my Wear watches working.
Could our issues be related? Some bluetooth software bug in phone? THIS IS PURE HELL!
Moto X4 cant come soon enough.
My Nexus 6 keeps forgetting my Bluetooth pairs. I'll wake up and notice that my pairs are gone. Which is an annoyance with my car and Android Wear watch. It happened once before but then when it happened last night I know there is an issue. It started after I upgraded to Marshmallow. I'm running the MRA58R build. Any ideas?
I have the same issue...ever since marshmallow...both 6.0.0 official and 6.0.1 official, both times before installs the phone was wiped...but never the less it always forgets my bluetooth pairs
it seems to correlate to when the phone fully dies. If the phone fully dies 1-2 out of 5 times it will boot back up without the bluetooth pairings.
Also if I don't pair my Wear watch(original 360) this does not seem to happen either
I'm having this issue as well. My phone will randomly ask to pair with my car, even though it's been paired already. And sometimes it will just ask me to allow it to share Messaging, which was also already set. It's frustrating. I've only noticed it with Marshmallow.
For me it doesn't seem to correlate with charge level.
Having the same problem here and now that you mention it, it does seem to happen when it fully dies. Until someone comes up with a solution I'm going to see about backing them up and restore if it happens again.
Allowing your phone to completely die is a bad idea. The sudden shut down is what is corrupting it.
Also restoring that type of system data is just asking for other random issues, also not a great idea.
While I run an AOSP based rom I have never had my device forget any of my 5 BT pairings.
I agree don't let phone die.
Also if low battery plays a role (before phone dies), it could be related to battery saver features that can activate at low batteries level. (Adjustable in settings)
For the android wear app, turn off battery optimization (to prevent it from being interrupted by doze. )
I have had zero disconnection between my n6 and my moto 360 g1 android wear watch in the last month.
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
My phone has done this now twice in three days on N Preview 3. Has anyone found a solution?
mine does it too. but it will forget ALL my paired devices. it's pretty annoying
This is happening to me as well. Nexus 6 is forgetting all paired bluetooth devices.
Most annoying is the Android Wear issue because I've been having to factory reset the watch to get it to pair again. Some of this might be the watch because I'm running a Samsung Gear 2 with Android Wear but I also have several other devices that I have to repair every time.
Also seems to correlate with the battery dying.
There has to be a common bug. As all my devices have no issue remembering the pairing. Mind you I also dont pair to my car.
Also keep in mind that it was found long ago that OEM put in lists of cars that it will not work with in their roms. We found it on samsung devices years ago where it would block all connections to BMW, Audi and a few others.
N6 running 6.0.1 (no root)
This just started happening to me yesterday but has happened twice so far in two days. My phone has not died as seems to be a symptom for others here. It did get below 10% today but I charged it up without issue. it wasn't until several hours later that it wiped all of its paired devices. below is a list of my paired devices:
Samsung ATIV book 8 (windows 10)
UE Mobile BoomBox
Moto360 2nd Gen
2014 Infiniti Q50
2015 Nissan Murano
After it wiped everything yesterday I re-paired the following:
Samsung ATIV book 8
Infiniti Q50
Moto 360
After the first wipe today I paired the watch and the car.
If anyone has any ideas I would be grateful. This is a GIANT PIA!
Does not look like there is a solution to this forthcoming... is there anyone with this problem that's recently updated to N? And has it gone away? I get this usually after a forced reboot... all bt settings gone. Totally a problem.
Any update on this. I think it started happening after I updated to 7 and then went back to 6 after having battery issues?
rkshack
Giant PIA
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5. I drive a lot for work, and need my phone paired to a JVC headunit (listed as JVC UNIT on my phone) in my van so I can take phone calls handsfree, and listen to podcasts. Every now and again, maybe once a day, with no rhyme or reason that I can discern, I get into the van and notice that my phone is not paired. It's a pain to have to pull over and re-pair the phone, and then set it up a a trusted bluetooth device again (so as to avoid entering my passcode whenever unlocking the screen).
- Definitely nothing to do with battery levels. My phone is normally fully charged and plugged in to a charger.
- I don't lose all paired devices, as my UE Boom 2 (not often used) is still listed as a paired device, whereas the JVC UNIT drops off fairly often.
Please could someone sort this issue out! It sounds like quite a few people are experiencing it.
thanks,
Phil
Phil in NZ said:
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5.
Click to expand...
Click to collapse
Not likely to get sorted for your phone in this N6 thread. [emoji6]
I am on Android 11 and it still happens to me, my car pairing is being forgotten from time to time. Happens to any of you?
I'm not sure if this has to do with recent updates to Android Auto or if it's specific to the make and model of my device (I got the new phone around the same time as the latest AA updates were released), but I'm now experiencing endless frustrations with constant connection failures between my phone and my Jeep's Uconnect 8.4 head unit again. I went through a similar thing, as did many others, around this time last year and the year before. It's infuriating.
Most of the time, when I plug my phone into the vehicle's USB port, the Android auto icon appears on the display of the head unit for a moment or two and then disappears. There's a notification in the shade on my phone that says something like "Connecting to Android Auto" or "Starting Android Auto." But then it never really starts.
Occasionally I try clearing the data, storage and cache from the Android Auto app and sometimes Google Play Services. Sometimes I'll also have to go into the Uconnect settings menu and tell my head unit to "Forget device." Every so often, as long as I then turn off the ignition and then restart the vehicle and then reboot my phone, this will bring me back to the Android auto setup screen and I'll be able to use Android auto for a single drive cycle. as soon as I cut the engine and unplug my phone, it's over. When I get back into the vehicle I'm back where I started: with the head unit seemingly able to recognize that an Android Auto device is connected for a moment and then Android Auto just quits out.
It's insane. Seems like Google can't just get this right. As soon as they release a build that works, they follow up with an update that completely breaks functionality.
Anyone else have a similar experience and, hopefully, have suggestions and how to resolve this nonsense?
Used my iPhone with my 2018 Challenger for a year and it worked perfectly. Switched to a Note 20 Ultra last month and it worked for about 2 weeks. Same issue you're experiencing. I'm going back to iPhone.