Google Fit not installing to Wear - Wear OS Q&A, Help & Troubleshooting

I can't seem to get Fit to install to my Moto 360, I've tried uninstalling/rebooting/reinstalling and resyncing installed apps through the Wear app. Is there a place to find the Wear version of Fit in an apk that I can sideload? Or if I just sideload the regular apk will it install the Wear version correctly? Thanks in advance.

I have the same issue on moto360ii must be a new bug. Just happened recently.

Found on another thread in the Moto 360 forum, the latest Fit apk wasn't compiled with the Wear app. Downloaded version 1.59 from apkmirror and now it loaded to my watch with no problems.

Related

Android Wear 2.0 Companion App

After updating to the latest version of the companion app (Version 2.0.0.137106828.gms), I've noticed that it can take upwards of 30 seconds to receive any notifications to my Moto 360 2nd Gen. I've tried clearing cache and data, uninstalling the companion app and reinstalling, restarting my phone and watch, resetting and pairing my watch again, and checking for watch updates all with no success. I ended up reverting to the previous version of Android Wear (Version 1.5.0.3329214.gms) and all of my problems have been solved.
When this has happened before, it was because a software update needed to come through to my watch. We know that 2.0 isn't set to launch until 2017, and I'm not willing to deal with this issue until then. I've attached a link to Android Wear Version 1.5.0.3329214.gms for those who share my problem.
http://www.apkmirror.com/apk/google...-wear-1-5-0-3329214-gms-android-apk-download/
*BAM* said:
After updating to the latest version of the companion app (Version 2.0.0.137106828.gms), I've noticed that it can take upwards of 30 seconds to receive any notifications to my Moto 360 2nd Gen. I've tried clearing cache and data, uninstalling the companion app and reinstalling, restarting my phone and watch, resetting and pairing my watch again, and checking for watch updates all with no success. I ended up reverting to the previous version of Android Wear (Version 1.5.0.3329214.gms) and all of my problems have been solved.
When this has happened before, it was because a software update needed to come through to my watch. We know that 2.0 isn't set to launch until 2017, and I'm not willing to deal with this issue until then. I've attached a link to Android Wear Version 1.5.0.3329214.gms for those who share my problem.
Great!! it is works for me! Thanks!
Click to expand...
Click to collapse
Has anyone tried the latest version (2.0.0.138705214)? I'm still sticking with my older version until I can verify that the bugs have been worked out. Comments in the Play Store are still giving mixed reviews of the latest version. I rely more on the good people of XDA and their opinions.
i have reinstalled brand new rom to my phone resurrection remix for oneplus 3. after reinstall my aps Android Wear is not working. with notice: this phone has been flashed with an unsupported configuration for companion. You must reflash it as signed user or unsigned/userdebug. What does it mean,? please help, i´m newbie. thank you. and yes, its a 2,0xxxx version
From everything I've read, the only fix is to go back to the Android Wear version I posted a link to. There doesn't seem to be an actual fix yet.
Synthi said:
i have reinstalled brand new rom to my phone resurrection remix for oneplus 3. after reinstall my aps Android Wear is not working. with notice: this phone has been flashed with an unsupported configuration for companion. You must reflash it as signed user or unsigned/userdebug. What does it mean,? please help, i´m newbie. thank you. and yes, its a 2,0xxxx version
Click to expand...
Click to collapse
You can change the buildprop from debuguser to user, if you want to continue using 2.0
If your phone is not rooted, the only possibility for now is to install the version 1.5 - you can find more information in this Google Group
I've been reading reviews on the Play Store of people having issues with WiFi Scanning turning on and off every 2-3 seconds. I'm having the same issue, but I attributed it to a software update I received for my S7. As previously mentioned, I rolled back to the 1.5.xxxxx update of Android Wear, so I can't imagine that would be the cause of my problem. I can't imagine it's just a coincidence though. Any one have any feedback on this?

[REQUEST] Facebook Messenger 99.0.0.20.136 Resigned (no playstore updates)

Hi everyone.
I really dislike the messenger layout since v100 and would like a way to return to the older one without google play to remind me every day there's an update.
So I downloaded Facebook Messenger 99.0.0.20.136 ARM version from APK mirror and used zipsigner/apktools to resign the apk (so playstore wouldn't suggest updates anymore).
But whenever I try to install the newly signed apk, it says there's already a package with that name... When I unstall Facebook app itself, I can install it just fine.
Anyone any idea why com.facebook.ocra is telling the package name is already in use while when I uninstall com.facebook.katana everything works? And how I could solve this?
Update: it seems to work fine on my Samsung Galaxy S5 running android 6, not on my OP3 running android 7

[Help ] - GenyMotion - Can't install some Google Play applications

Hello everyone.
I've recently installed GenyMotion in my Debian Jessie and apparently everything is working correctly.
I have created a Virtual Device from the available ones, installed GApps for the specific Android version but for some reason, I can't install at least one specific application from Google Store!
I have GenyMotion 2.9.0, running in my Debian Jessie 64bit, VirtualBox version is 5.1.18 r114002 (Qt5.3.2).
I have installed a Google Nexus 10 device with Android 5.1.0.
I have installed Genymotion-ARM-Translation_v1.1 and open_gapps-x86-5.1-micro-20170417.
When I try to download/install the APK file from Google Store, it just says it is not compatible with this device. The problem is that I have already tried several devices with different Android versions but no one seems to be "compatible" with that APK. The APK is a game and there are older versions of that game and they don't complain about compatibility issues! I already tried older a newer versions other than 5.1.0 but no good!
I can post some screenshots if needed and if there is anyone willing to dig this down to the bottom of the issue!
Thanks
HorusEye

Open Gapps Config For Moto G4

Hi guys.
I'm using LineageOS' latest build as of today 06/05/17 with Open Gapps.
I'm trying to find a configuration of installed apps that matches as best as possible that of the stock G4 (Nougat). I've no idea about the background services or which stock apps to remove (I'm using the aroma installer version of Gapps as none of the others fit what I want closely enough). Does anybody have any app choice recommendations for me?
Thanks.
darkglobe87 said:
Hi guys.
I'm using LineageOS' latest build as of today 06/05/17 with Open Gapps.
I'm trying to find a configuration of installed apps that matches as best as possible that of the stock G4 (Nougat). I've no idea about the background services or which stock apps to remove (I'm using the aroma installer version of Gapps as none of the others fit what I want closely enough). Does anybody have any app choice recommendations for me?
Thanks.
Click to expand...
Click to collapse
Gapps Included on Stock are Basically Mini Gapps and Leaving
~ Play Music
~ Google Messages
~ Chrome
~ Play Movies and TV
As Moto Uses Propietery Apps for Dialer and Contacts

Updating Google Services in an existing WearOS ROM?. is it possible?

Another user has created a ROM for an old WearOS watch that was running 1.5. There is a sync issue with older watches that requires an updated Google services APK to be installed to the watch using ADB. The google services version on the watch is v8.x so not recent enough to fix the sync issue.
What would I need to do to bake in an updated google services apk into an existing ROM? or is that not possible.

Categories

Resources