Develop Bugs

[POSSIBLE FIX] Android Wear 1.4 - Google Play Stopped Working

[POSSIBLE FIX] Disable Google Fit app on Moto 360. Working so far...
Thanks to several users on google support and reddit
I received my OTA update for Android Wear 1.4 this morning.
Running a Moto 360 V2 and a stock Nexus 6 with MRA48N.
Now my watch keeps giving Google Play Services has stopped working error on screen.
I've tried factory reset and older version of Android Wear... Nothing works.
PLEASE HELP

Same issue here. I tried the old fix of unpairing, deleting Android Wear from phone and installing and older APK. Factory reset watch and ran through the set up...all seemed to work fine until the Android Wear app updated, then back to same issue.

RickyGC said:
I received my OTA update for Android Wear 1.4 this morning.
Running a Moto 360 V2 and a stock Nexus 6 with MRA48N.
Now my watch keeps giving Google Play Services has stopped working error on screen.
I've tried factory reset and older version of Android Wear... Nothing works.
PLEASE HELP
Click to expand...
Click to collapse
I did this as well with the same results hope they come out with a fix soon.

Same issue here, hope google fix it quick
I had brougth my moto 360 v2 two days ago

I fixed it here is what I did
Uninstall Android Wear make sure to clear data and cache first
Download the previous APK http://www.apkmirror.com/apk/google...-wear-1-4-0-2392391-gms-android-apk-download/ and install
Factory reset watch and pair
A pain in the neck but it worked just dont update to the newer version till they get it right.
Nope that didn't do it either error came back after about 15 minutes.

Same Problem here with Moto 360 2nd Gen
I am also experiencing the same issue on my Moto 360 2nd Gen.
I have an open ticket with Google.... I was told this has been escalated to their Advanced support team.... still waiting for updates.
I have wiped cache within Google play services and downgraded to stock Google play services.. re-updated.. Wiped and cleared cache of Android wear and installed previous versions.. still same errors:
Moto 360 2nd Gen
Android Wear:1.3.0.2230669
Android OS: 5.1.1
Build: LLA44S
Google Play Services: 8.1.07 (2229520-534)
Errors:
-Google Play Services error Unknown issue with Google Play Services
-Unfortunately, Google play services has stopped.
Phone:
LG G4 running Android 5.1

I had this issue with my v2 today and I uninstalled google fit and it solved the issue. Did this before I knew it was a known issue to lol.
Sent from my Nexus 6 using Tapatalk

I found a solution, worked for me with moto 360 v2 and stock Galaxy S6
-Unpair watch from android wear app
-Factory reset watch
-Unistall Android wear (data and cache clead first)
-Clear data and cache from Google Play Services
-Reboot phone
-Fresh install Android Wear APP from google play store
-Pair the watch
Rock Solid :good:

I was able to resolve the issue by unpairing the watch from Android wear on my phone, Factory Resetting the Watch and then pairing it up to a Nexus 7 Tablet running Android 6.0 and the latest version of Android Wear. The watch synched to the tablet, was able to receive notifications. Once i confirmed there was no more "Unfortunately, Google Play services has stopped error", i then unpaired from the Tablet Android Wear, Factory reset the watch and re-paired to the same original phone running the latest Android Wear.
It has been almost 9 Hours since this was completed and this appears to have resolved the issue for me.

xJuicex said:
I was able to resolve the issue by unpairing the watch from Android wear on my phone, Factory Resetting the Watch and then pairing it up to a Nexus 7 Tablet running Android 6.0 and the latest version of Android Wear. The watch synched to the tablet, was able to receive notifications. Once i confirmed there was no more "Unfortunately, Google Play services has stopped error", i then unpaired from the Tablet Android Wear, Factory reset the watch and re-paired to the same original phone running the latest Android Wear.
It has been almost 9 Hours since this was completed and this appears to have resolved the issue for me.
Click to expand...
Click to collapse
This worked for me too. It appears to be Google's recommended path... and I've yet to have it let me down. On my fifth (ugh, don't ask) Android Wear watch... this basic strategy has (painstakenly) worked each time. Especially when I get a watch that has been in cold storage, and still has Android Wear 1.0W on it.

My watch disconnects whenever i install any wear enhanced app / watchface. I have to restart the watch to reconnect it. It happens on installing any app/face! Plz help.
PS: tried reseting the watch and the phone too. I have it paired to a Moto X2014 running 5.1 stock unrooted.

its end of januari 2016 and still have the same problems. I read people who factory reset and install the wear app back and its fixed. but its not. if the watch gets disconnected a few times for being to far away from Phone then after a while whatsapp messages stop working to show up. I also get the message that i need to installe google play services. on my Phone. wich is installed and on latest version...
Only thin working right now is using the android wear app 1.1 wich works perfectly. But in the play store the update keeps popping up so i need to watch out that i dont press update all. because then it will be reinstalling the latest version wich is a *****.
Cant wait until 1.5 is released.... hope it will be fixed then.
is there a way to report this to google or Motorola somehow. everyone seems to have the same issue here. why isnt this fixed sooner?

Apps force close, had to reinstall for some apps to run.

Hi.
New user of Zf2 here.
I've been realizing there is a small problem to my phone. Some apps installed in my phone, like Sygic Navigator, Waze, Asphalt, Mantano Reader, Line video call; it has no pattern, just randomly; often failed to launch especially after some time of phone idle or restart. Sometime with usual mesaage when apps force close, sometimes just no message at all. After reinstalling the apps (i'm using link2sd that can offer the option of reinstalling) the app(s) will run normal again.
Anyone here has got the same problem, or it is known issue (I'm guessing Lollipop's) ? Please provide a solution if there is any. Much appreciated for all help.
Cheers.
Specs:
Model: ZE551ML 4/32
RAM: 4G
Firmware/APP Version: ww_2.20.40.139_20151104
Rooted/Unlocked: Yes

Android Auto

It was suggested I come over here and see what's going on. I've got a 5t with Oxygen.
I've never been able to get Android Auto to load, once. It always says "Something went wrong - Google Play services doesn't' seem to be working right now."
I can't Force Stop the Google Play services, or deactivate it. I've cleared my cache. I don't have a Android Device Management App installed either.
I enrolled and updated to the Google Play services Beta, but haven't still can't force stop it either.
Where do I go from here?

I don't know about this issue.
But I can say I use Android auto daily in my car and have no issues.
I have a Volkswagen caddy 2017 and use ob3
I sideloaded the app because it is not officially released in my country. I use version 3.0.

@dashbarron,
I have the exact same problem . I've also gone the play services beta route with no joy. I've tried literally every possible solution I've come across on the web, still no joy. I can't get past this.
Did you ever get AA to work? How?
Thanks!
-Warren

dashbarron said:
It was suggested I come over here and see what's going on. I've got a 5t with Oxygen.
I've never been able to get Android Auto to load, once. It always says "Something went wrong - Google Play services doesn't' seem to be working right now."
I can't Force Stop the Google Play services, or deactivate it. I've cleared my cache. I don't have a Android Device Management App installed either.
I enrolled and updated to the Google Play services Beta, but haven't still can't force stop it either.
Where do I go from here?
Click to expand...
Click to collapse
I don't know if you have used Android auto before, so maybe you really like it and my advise maybe of no use to you. But while it is good to use, I soon reverted back to using split screen, top half for nav and bottom half to easily switch between music or radio or whatever else you want, even set up a YouTube video before you get going if it's something that doesn't require your focus on it, with gestures it's safer than messing around with the complicated controls in my car! And I have the plug in version of Android auto built into the car, I literally only plug it in when I have my daughter's on board so they can call out ok Google for whatever tune they want on. Anyway that's how I roll when driving and I'm driving all day everyday, hope maybe I saved u some time getting it working

Samsung Wearable App Crashing?

Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.

How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.

Helhound0 said:
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
Click to expand...
Click to collapse
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk

oxygenes said:
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Click to expand...
Click to collapse
I got 3 gigs and not even half of it being used at idle. And i don't really do memory intensive stuff on my phone anyway. The issue was definitely Samsung Pay. if anyone has this issue where you're running Pie and are rooted with any version of magisk, uninstall Pay. It's been a few days and i haven't had this issue repeat even once.
shmaque said:
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I just uninstalled Pay from the app list in settings and rebooted. If there is a sneaky sideloaded plugin somewhere, it doesn't seem to be interfering with the Wearables app anymore.
And I guess you're right about this being a terrible approach. But Pay isn't even supported where i currently live so my question is WHY even sideload it on a device being used in an unsupported region... Such a waste of resources.

GPS Issues

Hey everyone.
since today some apps have gps issues (app for local traffic, waze navigation, German Weather Service=
Google Maps App and German Railways works fine.
Google Maps opened in Firefox does not neither.
Checked with the app GPS Status from the app store but ist not getting any position.
Anyone have the same issues or maybe a fix to this Problem?
Tried everything from Google Search (LG GPS Issues/Android GPS Issues)
Would like to prevent a fatory reset.
Phone Stats:
LG-G710EM with Android 9 and Sec Patch from 1st July.
Build Number PKQ1.181105.001
Regards
Kaiske

I had the same problem. A few weeks after updating to Android 9 (without factory reset) gps via hw stopped working. Reset solved it.

Had the same problem a few months back. I needed to reflash the firmware and maybe a factory reset.

Thanks. Somehow it has to be the Software. Tried something Else but only a factory reset has helped. Did it two das ago and now IT works better than before.