Develop Bugs

Motorola Connect can't sync new faces to the watch?

having problem syncing the new watch faces on the watch?

furiousgtz said:
having problem syncing the new watch faces on the watch?
Click to expand...
Click to collapse
Same problem here, tried resetting watch, phone etc. Also uninstalled and re installed still not showing up.

2crazeybolt said:
Same problem here, tried resetting watch, phone etc. Also uninstalled and re installed still not showing up.
Click to expand...
Click to collapse
Me too! I did all of that. I just got new a new replacement note 4 and it was working fine on my previous note 4 but this will not sync any faces or no moto app.

ok I was able to get it working. I factory reset the watch and via android wear I added new wearable device and clicked on sync all app.

furiousgtz said:
ok I was able to get it working. I factory reset the watch and via android wear I added new wearable device and clicked on sync all app.
Click to expand...
Click to collapse
That did the trick, thanks i'm working good now.

Reset my phone three times and no love. I can update the original stock faces but thennew faces never show up

Same thing happened to me today. I've reset my phone 3 times and resync'd many times without any luck. Any suggestions?
Edit:
Finally, I was able to fix it. My case was as follows:
I had paranoid android installed (new faces were fine). Had to restore factory settings on my phone, phone didn't want to sync after I reset my phone so I restored factory settings on my phone. I lost the new faces. Tried resetting the phone and watch multiple times and it didn't work. I went back to stock 5.0 (LRX21O) by following this guide . After restoring my phone to stock, I reset the watch one last time. Paired the phone and watch, customized one of the new faces chose minimal face on watch (still no new faces on my phone), then customized the same new face again, when trying to select another face it only showed one (simple). I chose that one, then tried to change to a new face and viola! new faces appeared.
Not sure what of everything I did was the fixing factor but wanted to share. Hope this helps.

Faced same problem. But i managed to update my 360. Try to uninstall all 3rd party app on ur phone, uninstall motoconnect and android wear. Last step is factory reset ur moto360
Then install motoconnect, install android wear ( do not install any 3rd party app at this stage), go to android wear setting and resync available app. Just make sure your phone screen is on about 10 minutes or so, moto360 will reboot after that.
All new faces and moto body apps will show up eventually - i tried this 3 times.
Hope this may help

Motorola 360 new watch faces not showing up on watch
I had the same problem, new watch faces would show in connect app (particularly the My Design one) and I could customize them but the new ones would never show up as an available watch face option on the 360. It may be related to replacing your phone as the new watch faces worked fine with my Old Note 4 then I had to replace it (because it had a problem) so when I got my replacement Note 4 and reconnected my watch it would never give me the option for the new watch faces even after I "reset" the Moto 360 numerous times. Interestingly for some people the new watch face options don't even show up in their Motorola Connect App on their phone, I think it may be related to their phone OS version. I have a coworker with a Note 3 and the new watch faces are not a option even though his motorola connect app is up to date.
Here is what I did to fix my 360:
- uninstall all apps on your phone related to your watch (Motorola Connect, Android Wear, 3rd party, etc.)
- Reset your 360 back to factory. (not just a restart)
- Wait for watch to prompt to install Wear on phone.
- install wear on phone, it will remember your old watch, pick the menu option to forget that watch though so it acts like this is the first time you are setting up a watch.
- Go through the watch pair and setup routine with the wear app till you get to the main wear screen that shows the watch connected and what your voice actions are.
- Go through the training setup on your watch (swipe, swipe....) till it's to it's Normal screen with your notifications.
- Install Motorola Connect app on your phone, go through the setup and wait till it says "connected" to your watch
- Set your phone and your 360 down and don't touch either for 15 minutes (no new apps, settings, etc)
- Your new watch faces should now be on your 360.
- re install the rest of your wear junk.

Those who have problems syncing , keep the watch on charging and charge your phone as well . do not reset anything. Just resync all apps option in android wear app. They will show up automatically after few mins

[email protected] said:
Those who have problems syncing , keep the watch on charging and charge your phone as well . do not reset anything. Just resync all apps option in android wear app. They will show up automatically after few mins
Click to expand...
Click to collapse
After this latest Moto Connect update I'm still waiting to see the new faces in the Android Wear app. I got the update almost 24 hours ago and nothing. I have tried re-syncing, resetting the watch, all that stuff. What is funny is I can go download a new random watch face and within a few minutes it shows up. But the new Connect app doesn't seem to be working. However if I am in the Connect app and "customize" a face and hit "Apply" it makes the watch vibrate. I also cannot change the color of the charging dock face... Crazy, not sure what the issue is.

supercluver said:
After this latest Moto Connect update I'm still waiting to see the new faces in the Android Wear app. I got the update almost 24 hours ago and nothing. I have tried re-syncing, resetting the watch, all that stuff. What is funny is I can go download a new random watch face and within a few minutes it shows up. But the new Connect app doesn't seem to be working. However if I am in the Connect app and "customize" a face and hit "Apply" it makes the watch vibrate. I also cannot change the color of the charging dock face... Crazy, not sure what the issue is.
Click to expand...
Click to collapse
Have you tried clearing app data for the connect app on the phone, then uninstall it. Reboot both the phone and watch. Then once the phone and watch are connected again, download the connect app.

DQEight said:
Have you tried clearing app data for the connect app on the phone, then uninstall it. Reboot both the phone and watch. Then once the phone and watch are connected again, download the connect app.
Click to expand...
Click to collapse
Yeah. Apparently, and I should have guessed this, it is an issue with my running the 6.0 preview 3 on my nexus 6. So yeah, sucks but M is worth not having a couple new watch faces and a different color charging face.

supercluver said:
Yeah. Apparently, and I should have guessed this, it is an issue with my running the 6.0 preview 3 on my nexus 6. So yeah, sucks but M is worth not having a couple new watch faces and a different color charging face.
Click to expand...
Click to collapse
I thought it was M p3 too, i even removed all my wear apps and reseted the watch XD
Motorola told me to "unoptimize" the wear abb (from the battery options).
I asked if it could not be an incompatibility with M, but they did no know.
EDIT: motorla lvl2 suppoty called, they say that the newer API level in android 6.0 makes it incompatible with moto connect update

[email protected] said:
Those who have problems syncing , keep the watch on charging and charge your phone as well . do not reset anything. Just resync all apps option in android wear app. They will show up automatically after few mins
Click to expand...
Click to collapse
Thanks, worked PERFECTLY!
Sent from my Nexus 6 using Tapatalk

cocchiararo said:
I thought it was M p3 too, i even removed all my wear apps and reseted the watch XD
Motorola told me to "unoptimize" the wear abb (from the battery options).
I asked if it could not be an incompatibility with M, but they did no know.
EDIT: motorla lvl2 suppoty called, they say that the newer API level in android 6.0 makes it incompatible with moto connect update
Click to expand...
Click to collapse
They DO know that 6.0 is about to be released right? Ugh. Guess I'll stop trying to get this to work on my Nexus 6.

supercluver said:
After this latest Moto Connect update I'm still waiting to see the new faces in the Android Wear app. I got the update almost 24 hours ago and nothing. I have tried re-syncing, resetting the watch, all that stuff. What is funny is I can go download a new random watch face and within a few minutes it shows up. But the new Connect app doesn't seem to be working. However if I am in the Connect app and "customize" a face and hit "Apply" it makes the watch vibrate. I also cannot change the color of the charging dock face... Crazy, not sure what the issue is.
Click to expand...
Click to collapse
i have the same problem, factory reset watch and nothing happend, if anybody have a solution please...

santiagodm said:
i have the same problem, factory reset watch and nothing happend, if anybody have a solution please...
Click to expand...
Click to collapse
if you are on 6.0, then you have to wait for an update from motorola.

cocchiararo said:
if you are on 6.0, then you have to wait for an update from motorola.
Click to expand...
Click to collapse
ok, Thanks cocchiararo, just have to wait

I don't have the option to change the charging colors. Swiping down on the watch face does nothing, and there isn't an option for it in Motorola Connect. I'm running the latest Moto 360 software on the watch, and my phone is running OS 5.1.

Latest Android Wear update broke my Moto 360

Ever since updating this evening, I'm getting unfortunately the process com.google.process.gapps has stopped over and over. I hit ok, it comes back.
No clue what's causing it. The only thing that changed was I updated Android Wear app.

USA Prime Credit Peggy said:
Ever since updating this evening, I'm getting unfortunately the process com.google.process.gapps has stopped over and over. I hit ok, it comes back.
No clue what's causing it. The only thing that changed was I updated Android Wear app.
Click to expand...
Click to collapse
Make sure your phone is running latest Google Play Services (7.0.97)
https://play.google.com/store/apps/details?id=com.google.android.gms
What Play Services version is running on your 360? Settings > About > tap Software Version. Should be 7.0.95

xdatastic said:
Make sure your phone is running latest Google Play Services (7.0.97)
https://play.google.com/store/apps/details?id=com.google.android.gms
What Play Services version is running on your 360? Settings > About > tap Software Version. Should be 7.0.95
Click to expand...
Click to collapse
mine on my moto is 6.7.74. how would I upgrade this manually?
---------- Post added at 09:27 AM ---------- Previous post was at 09:21 AM ----------
anubis1980 said:
mine on my moto is 6.7.74. how would I upgrade this manually?
Click to expand...
Click to collapse
figured it out, just sync the apps from android wear app, thanks anyway

Solution to update until they fix the issue!
Hi guys,
well this is what I did!
You have to delete Android Wear from your phone and then download the last update APK and install this on your phone, so in a sense you are taking the Android Wear back to the last update:
so firstly delete android wear app on phone
On your phone:
Google Android Wear 1.0.5.1724356 and select first entry apkmirror
scroll down to All Versions and choose whether you want the last one Mar 12th or Feb 25th, incidently I chose Feb 25th
Click on download arrow and then click to install on phone, you may need to tick allow download from outside sources, this site is google approved so is ok.
and thats it, you now have the previous version, I would advise installing My Backup pro as this will allow you to save your APKs if you accidentally update one again in the future. You could also deselect the auto update on the Android Wear app.
Best
J

Doesn't work..
Nothing of this works for me..it's so annoying.. ;(

Reset
Xelfmade said:
Nothing of this works for me..it's so annoying.. ;(
Click to expand...
Click to collapse
I had to go into my watch settings and do a factory reset and re-install android wear app (not sure if re-installing the app really did anything, but didn't hurt)...It was annoying having to set it up all over again and blocking cards I do not want to show up, but its better then this constant notification killing my battery.

Xelfmade said:
Nothing of this works for me..it's so annoying.. ;(
Click to expand...
Click to collapse
Me too. Tried once to factory reset the watch, reinstall the latest Android Wear to my phone and resync the apps. However, the result isn't encouraging at all. The watch was quite hot.
I switched off the bluetooth and let the watch to cool down. Then, I will do another trial. Wish me luck. Thanks!

Thank you sir, that did the trick in my case!
JustinConnor said:
Hi guys,
well this is what I did!
You have to delete Android Wear from your phone and then download the last update APK and install this on your phone, so in a sense you are taking the Android Wear back to the last update:
so firstly delete android wear app on phone
On your phone:
Google Android Wear 1.0.5.1724356 and select first entry apkmirror
scroll down to All Versions and choose whether you want the last one Mar 12th or Feb 25th, incidently I chose Feb 25th
Click on download arrow and then click to install on phone, you may need to tick allow download from outside sources, this site is google approved so is ok.
and thats it, you now have the previous version, I would advise installing My Backup pro as this will allow you to save your APKs if you accidentally update one again in the future. You could also deselect the auto update on the Android Wear app.
Best
J
Click to expand...
Click to collapse

Put me into the boat of this error, it's not all the time, but goes in cycles. I'll get it for an 8 hr stretch, then nothing. I've tried everything except hard resetting my watch. I'm hoping for an update on either play services for the phone or watch to get rid of it. Might be that my Corp email is my most frequent notification, but that is where i see it most.
Phone is 4.4.2 Sprint Galaxy S4T stock build with custom recovery and rooted. No system modifications other than root

reset the device
Fixed!
I did a factory reset. Didn't work the first time, I kept clicking away those pop-ups... I tried again without touching the watch and about 20 minutes later I was good to go, without the process error.

Guys it's way more easier than this , just go too apss and find google play services the touch it, click on uninstall updates then ok and just let it u installed, then go to play storeor wait till notification pup-up about play music or hangout or android wear need app requered and click. On it or in play store search for google play services , both will end at same page , then click update and let it install the latest version and finished , all errors will be vanished, enjoy it.

scorpion_s66 said:
Guys it's way more easier than this , just go to apps and find google play services the touch it, click on uninstall updates then ok and just let it u installed, then go to play store or wait till notification pup-up about play music or hangout or android wear need app required and click. On it or in play store search for google play services , both will end at same page , then click update and let it install the latest version and finished , all errors will be vanished, enjoy it.
Click to expand...
Click to collapse
My Uninstall Updates is grey and not clickable

You need to disable one of your 'Administrators.' Basically, hit the 'disable' button and it will ask you if you want to, hit yes. Then it will ask if you want to install the factory version, hit yes. Next it will take you to the 'Device Admin' in settings and you you will need to disable those, unless you only have one, in order to uninstall the previous update.
Update: The 'fix' given by scorpion_s66 did not work for me. I am now trying to reset my moto 360 but I cannot seem to do that either. All I can say is... Thanks Google! After I updated to the new Android Wear all these issues started. I reverted back to the older version but nothing changed. woooooooooooooooosssaaa wooossaaa woosa - Now I feel better (Bad Boys 2 just in case anyone doesn't get woosa).

I was impacted by this as well. After finding my watch on the charger yesterday morning red-hot and unusable (the same repeating error message mentioned earlier) I finally got it working by attempting a factory reset about 5+ times over the course of over an hour. It finally seemed to "take".
I've had this watch for about a week and while I like it and I'll keep it, I'm also coming to the conclusion that Google does not have it's A-team working on Android Wear. There are some really hacky implementations in here. I mean, why do my offline music transfers (phone to watch) automatically stop with no warning when the phone drops to 50% battery (which happens about about 50 songs). Why do I have to go through this ridiculous 5-times "ok google" to get rid of that message on the watch face? Seriously, who thought this was a good design? Why did many of our watches get nearly bricked after a Android Wear update on the phone? Why can't I use my watch or transfer music while it's charging? Why do I have to go through this elaborate process to view/access my list of apps?
Sorry for the rant. Last year I read a book titled "How Google Tests Software", which I found quite interesting at the time. This crap certainly gives me a different perspective..

aperry said:
I was impacted by this as well. After finding my watch on the charger yesterday morning red-hot and unusable (the same repeating error message mentioned earlier) I finally got it working by attempting a factory reset about 5+ times over the course of over an hour. It finally seemed to "take".
I've had this watch for about a week and while I like it and I'll keep it, I'm also coming to the conclusion that Google does not have it's A-team working on Android Wear. There are some really hacky implementations in here. I mean, why do my offline music transfers (phone to watch) automatically stop with no warning when the phone drops to 50% battery (which happens about about 50 songs). Why do I have to go through this ridiculous 5-times "ok google" to get rid of that message on the watch face? Seriously, who thought this was a good design? Why did many of our watches get nearly bricked after a Android Wear update on the phone? Why can't I use my watch or transfer music while it's charging? Why do I have to go through this elaborate process to view/access my list of apps?
Sorry for the rant. Last year I read a book titled "How Google Tests Software", which I found quite interesting at the time. This crap certainly gives me a different perspective..
Click to expand...
Click to collapse
I tend to disagree. I was having the same problem and I wasn't even able to set my moto 360 as those messages were constantly popping up. However, I came across the contacting google option, and within a minute after I made the request, they have actually got someone from the android wear team to call me... all the way to Australia and resolve my problem over the phone! Just because you read a book bad mouthing Google, doesn't mean it's all that crap!!

I took JustinConnor's reply and edited it a little, becase the original one was just partly helpful for me, so all the steps: (but still: BIG THATNKS, MAN!)
Delete android wear app from your phone
Download the last good version of ANDROID WEAR - for me it was version 1-1-1-1876095.
Make Factory Reset to your watch (not the sowt refactory reset - but REAL refactory reset through recovery mode with black-background (more of this in the end)
connect your watch to your phone via downloaded android wear app
Factory reset menu should look like black background and console-like words in the front (unfortunately I can't post links because I haven't posted 10 times yet - so forum do not allow me to do that).

zacharywater said:
I tend to disagree. I was having the same problem and I wasn't even able to set my moto 360 as those messages were constantly popping up. However, I came across the contacting google option, and within a minute after I made the request, they have actually got someone from the android wear team to call me... all the way to Australia and resolve my problem over the phone! Just because you read a book bad mouthing Google, doesn't mean it's all that crap!!
Click to expand...
Click to collapse
I'll admit that my post was born out of frustration, but I do want to clarify that the "book" I referenced was written *by* Google employees and it doesn't bad-mouth them at all. It describes with a great degree of pride their software testing process, and it's a good read for anyone in the industry.
I do continue to be frustrated by many of the design decisions in Android Wear, and I maintain they must have their B-team working on this, or at least on the design. For some reason the "ok google" message started reappearing all of the sudden the other day (after I had gone through the ridiculous steps to make it go away days before). It's probably because I don't use the feature very much, but why do I need to be reminded of this in a way that completely interferes with my watch face? Then I was out for a run yesterday and my offline music playback just stopped at 15% battery. I guess it's to protect me from myself, kind of like how the music transfer from phone to watch automatically stops at 50% battery and doesn't work at all while the watch is on the charger. Offline playback was one of the important use cases for me (jogging without phone!). It works, but it's a poor user experience. Don't get me wrong, I like the watch and I personally think it's the best looking smartwatch on the market. It has some cool features, and it's good enough to keep using daily. But the software is disappointing and it's hard for me to recommend this to any of my friends. I was lucky enough to get a deal on it for about $100, and I'd probably be much more disappointed had I paid full price.
PS: Count me as one of the people really interested to see how this upcoming wifi functionality will work. I can get about 2 days out of this watch when I'm pretty careful with it. I can deal with 2 days. But any significant active use seems to drain the battery quickly. I'm having trouble understanding how a persistent wifi connection with the cloud will not eat through the battery in a matter of just a few hours, but I'm hoping Google will pull a rabbit out of its hat here. I just hope it's more than a half-baked checkmark on the "iwatch versus android" checklist.

My watch wont charge and i cant fatory reset it either, someone anyone know what to do?

Can you be a little bit more specific?
I had Friday the same issue after updating to Android Wear 1.1.1.1901499 with Google Play Services 7.3.36 .
Charging didn't work, because always the pop-up "Unfortunately,.... bla bla bla" so I turned off the watch.
Put on the charging cradle and let it charge until it turned on by itself.
20% charged, so turned off again and keep charging
At 35% I started the "Reset Watch-Game" interrupted several times by the "Unfortunately,...."
After felt 1 hour tapping the message away, the Moto360 finally made a reset, installed the previous Android Version and since then I am fine.
Today Google updated Android Wear to 1.1.1.1901499 by PlayStore, however my Google Play Service stays on 7.3.34.
I suspect Google Play Services 7.3.36 is only for FW 5.1.1 and won't work well with FW 5.02
Cheers
Tom

tom1807 said:
Can you be a little bit more specific?
I had Friday the same issue after updating to Android Wear 1.1.1.1901499 with Google Play Services 7.3.36 .
Charging didn't work, because always the pop-up "Unfortunately,.... bla bla bla" so I turned off the watch.
Put on the charging cradle and let it charge until it turned on by itself.
20% charged, so turned off again and keep charging
At 35% I started the "Reset Watch-Game" interrupted several times by the "Unfortunately,...."
After felt 1 hour tapping the message away, the Moto360 finally made a reset, installed the previous Android Version and since then I am fine.
Today Google updated Android Wear to 1.1.1.1901499 by PlayStore, however my Google Play Service stays on 7.3.34.
I suspect Google Play Services 7.3.36 is only for FW 5.1.1 and won't work well with FW 5.02
Cheers
Tom
Click to expand...
Click to collapse
Is there a required battery percent to reset?

Notifications not showing

Hi all
I've recently started using my Moto 360 again alaong with my HTC M8 running the Radium 1.4 ROM. I set the watch up and all was working perfectly. I then noticed the watch was not receiving any notifications, this was after I had been out for a while with the watch at home. The only way I could figure out re-enabling them was to factory reset the watch then set it up again. I don't want to have to do this every time I go out without the watch etc. I had similar problems with the watch not pairing via Bluetooth with my phone after it had already been paired. The only way I could get it to pair was again to factory reset. This issue seems to have gone away now and it's just the notifications that seem to be a problem.
Any advice would be appreciated.
Thanks

Looks like ROM issue!
Sent from my SM-N9005 using Tapatalk

nijom said:
Looks like ROM issue!
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Happens with ever ROM I've tried

stevoh84 said:
Hi all
I've recently started using my Moto 360 again alaong with my HTC M8 running the Radium 1.4 ROM. I set the watch up and all was working perfectly. I then noticed the watch was not receiving any notifications, this was after I had been out for a while with the watch at home. The only way I could figure out re-enabling them was to factory reset the watch then set it up again. I don't want to have to do this every time I go out without the watch etc. I had similar problems with the watch not pairing via Bluetooth with my phone after it had already been paired. The only way I could get it to pair was again to factory reset. This issue seems to have gone away now and it's just the notifications that seem to be a problem.
Any advice would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
It is actually an issue with the recent Android Wear app update...just read all the comments from 360 owners. Mine will not connect either.
Cheers

Well at least it was nothing to do with my phone/watch/ROM. Must have been updated recently as it's been fine! Back on form
Cheers
jschill31 said:
Hello,
It is actually an issue with the recent Android Wear app update...just read all the comments from 360 owners. Mine will not connect either.
Cheers
Click to expand...
Click to collapse

stevoh84 said:
Well at least it was nothing to do with my phone/watch/ROM. Must have been updated recently as it's been fine! Back on form
Cheers
Click to expand...
Click to collapse
After 4 Android Wear updates they finally fixed the connection issue. I sent them several bug reports and I swear they didn't even look at them.
Cherrs
Nexus 6

I'm still having problems where my Moto 360 won't show notifications (text, email, phone calls). I've tried every recommended solution. After a factory reset it works for maybe 30 minutes and then stops. One thing I've noticed (and I don't know if it's related or not) is that the Android Wear version on my Phone (Galaxy S5) is 1.3.0.2284253 and on my Moto 360 it's 1.3.0.2166028. Shouldn't they match?

Ramer said:
I'm still having problems where my Moto 360 won't show notifications (text, email, phone calls). I've tried every recommended solution. After a factory reset it works for maybe 30 minutes and then stops. One thing I've noticed (and I don't know if it's related or not) is that the Android Wear version on my Phone (Galaxy S5) is 1.3.0.2284253 and on my Moto 360 it's 1.3.0.2166028. Shouldn't they match?
Click to expand...
Click to collapse
For anyone who runs across this at some point, I solved the problem (at least for me). I unistalled Light Manager and now I'm getting all notifications.

Arrrgh mine has started doing this again! It had been fine for a few weeks. Seriously needs sorting out

I just got a new Moto 360 2 days back, and noticed this issue soon after it updated itself maybe to 5.1.1. I restart my phone everytime i face this issue which seems to fix it. Also android wear shows an error message mentioning notification sync is not working.

aayushjoshi said:
I just got a new Moto 360 2 days back, and noticed this issue soon after it updated itself maybe to 5.1.1. I restart my phone everytime i face this issue which seems to fix it. Also android wear shows an error message mentioning notification sync is not working.
Click to expand...
Click to collapse
Still isn't resolved for me sadly and restarting the phone doesn't work. I'm just flashing a new ROM to see if that helps. My watch has randomly been saying Google Play Services isn't installed on the phone when it is. Strange happenings here!

I have exactly the same problem! Saying Google play services are not installed, no whatsapp or text notifications until I get an email then they mysteriously appear. also if I toggle notification to priority and back they appear. doing my head in

You need to restart the phone and the watch, not just the phone.
Also can try removing your phone from your watch's bluetooth pair list then also "forget" the watch in your phone's bluetooth menu, then re-pair the two. Should work no problem after that.
I find this only happens if i stray away too far from either device or one of them gets restarted for some reason.. but yeah, restarting both the phone and the watch, removing the phone and watch from both bluetooth lists, and then re pairing, has fixed it every time for me. No having to factory reset the watch or reflash rom or anything drastic like that.
Now if you're phone is always in your pocket/purse which is on you all the time and the watch is on your wrist too and it just drops connection randomly... then i'd say something is messed up with your watch or phone.

Moto 360 1st gen spot top left of screen

I have a spot on the top left of my watch and it's always there no matter where I go. When I click it, it brings up a small set of icons. Is there any way of changing this? Just got it and I'm not that familiar with it still.

Might be some 3rd party app. Have you checked your downloaded apps for any unknown apps/an app that could cause this? Also this reminds me of the MIUI floating button, what rom are you on? ^^

It looks like the show-touch icon... but that was disabled on Moto 360 due to the OMAP3 processor having issues with it.
I would do a factory reset. Doesn't hurt, particularly if you have done several upgrades since 1.0W.

Android wear launcher probably

korenisko said:
Android wear launcher probably
Click to expand...
Click to collapse
I concur, but I don't see any easy way to purge that. Hence why factory reset may be the easiest fix.

Thanks for all the replies everyone. The factory reset took care of it.

Same problem.
I am having the exact same issue on my Moto 360 after just resetting this weekend. I have rebooted several times. I will try resetting again later tonight, but I wanted to post it here to document another occurrence of this strange issue.

After resetting my watch yet again, I finally figured out the culprit. It is an (annoying) "feature" called "Assistive Touch" of the popular "Wear Mini Launcher" app (which I generally love) that can easily be disabled by going into its Behavior options.

I say that previously

Phone automatically goes to home screen,

I've been having an issue with my Z2 Force that I've never had with any of my other phones. For some reason, it acts like I'm hitting the home button, even when I'm not touching it. I could be using a web browser, the XBox app, or any other app and it will go back to whatever launcher I have set as default. It doesn't close the app, it just minimizes it. I've tried disabling the home button for navigating & use the touch buttons instead, and when that didn't work I tried doing a factory reset. Well, it's still doing it, and I'm to the point where I'm very tempted to try to use one of the rooting methods I was able to find online, one of which does mention the specific model of my Verizon variant (XT1789-01). I can live without root if needed, but this 'phantom home button pressing' thing is driving me nuts. Any help is appreciated, and thanks.

I have 4 Moto Z2 Force in my house, 2 of them (Android 9, Verizon version) have this same issue.

Eco0901 said:
I have 4 Moto Z2 Force in my house, 2 of them (Android 9, Verizon version) have this same issue.
Click to expand...
Click to collapse
I'm still working on getting myself to go through with trying the root method I found. I think it'd work, but my main issue would be with making sure I can find a rooted ROM for the phone. Assuming the method works and I don't bork my phone, I'd still need a different ROM to install in order to determine if it's a hardware issue or software based. By the way, on the chance you're thinking of trying to remove the screen protector, be aware it is realllllllly stuck on there. I almost pulled my screen off, but I was able to remove it & was rewarded with a bunch of left over residue.
At any rate, if I do actually get myself to do the root thing, I'll be sure to post my results here.

will4958 said:
I'm still working on getting myself to go through with trying the root method I found. I think it'd work, but my main issue would be with making sure I can find a rooted ROM for the phone. Assuming the method works and I don't bork my phone, I'd still need a different ROM to install in order to determine if it's a hardware issue or software based. By the way, on the chance you're thinking of trying to remove the screen protector, be aware it is realllllllly stuck on there. I almost pulled my screen off, but I was able to remove it & was rewarded with a bunch of left over residue.
At any rate, if I do actually get myself to do the root thing, I'll be sure to post my results here.
Click to expand...
Click to collapse
I use the ROM stock so isn't the root that cause the problem, but I hope you find the way, my only hope is on you, actually ):

Eco0901 said:
I use the ROM stock so isn't the root that cause the problem, but I hope you find the way, my only hope is on you, actually ):
Click to expand...
Click to collapse
My concern is whether the root method I found is legit or not. The only reason why I want to attempt it is because the description mentions the specific model of my phone. All variants of the Z2 Force start with XT789-, but it's the number after the '-' you have to look for, and for Verizon users is '01'. Rooting the phone will let me install a different version of Android that should help me narrow down the cause of the glitch. Since your phone is doing the same thing mine is, it's more-than-likely not due to an app, so it has to be either the OS or a hardware thing.

Maybe a downgrade to 8.0 will make it, this bug is so annoying

Eco0901 said:
Maybe a downgrade to 8.0 will make it, this bug is so annoying
Click to expand...
Click to collapse
It's possible that might work, but either way I still need to be able to root the thing and find a ROM made for the Verizon model. My phone has only been doing this for a couple weeks or so, but before that it would actually fully close certain apps (gsam Battery Monitor, RadioU, Taskbar, and some others). However, I more than less fixed that by setting the timers for those apps to 23 hrs.

How did you set the timers? That fixed the problem of minimizing the apps?

Eco0901 said:
How did you set the timers? That fixed the problem of minimizing the apps?
Click to expand...
Click to collapse
The reason why I tried setting timers on certain apps was because they were being killed automatically, this was before the 'phantom' home button thing. The following steps may/may not resolve your current issue, but you can try them if you'd like:
1. Go to Settings
2. Apps & notifications
3. Screen time
4. At the bottom, you'll see a few apps listed, and a an option to show all of your apps. Select 'Show all apps', then the app you want to set the timer for.
5. Next to each app you'll see a little hour glass. If it's empty, then there is currently not timer set. If you'd like to set a timer, tap the hour glass, then set your desired time.
Again, I did all this well before my phone started acting like I was hitting the home button in an effort to get it to stop closing my favorite apps. For the most part, it worked, but the automatic closing thing only started after the upgrade to Android 9. I did find a site where I could download a previous stock ROM, but without root it may/will re-update again. There's an app that let's you prevent updates, but the phone has to be rooted in order for the app to work. I can't really remember the name app right now, but I used to use it on my Note 4. I think there was also a way to do it through the command line in Windows (might've worked in Linux, too), or it might've been a combination of an app and the command line.
In any case, the root method I thought I'd found wasn't really all that instructive, and I need to make sure I can actually fully unlock the boot loader before attempting root. If I can't unlock it, then whatever root method I try won't stick. The auto home button thing, at least on my phone, seems to be random, though. Sometimes it'll be fairly soon after opening an app, other times the app will stay open for a good while before going back to the home screen.

Well, like I said, I have other 2 Moto Z2 Force but they are Sprint or whatever the carrier are. They don't have the phantom home button problem. But they are in Android 8. I actually don't have a problem on click the multitasking button to go back to the app but the problem is on the games and that stuff. So if I go back to Android 8 the system will update automatically to 9? I didn't know that, I thought that it was volunteer hahaha. Btw I don't even know how to downgrade since I'm not a moto user of all life. This is my first experience with a moto phone and it sucks. . Hahaha actually the home button problem happen.

Eco0901 said:
Well, like I said, I have other 2 Moto Z2 Force but they are Sprint or whatever the carrier are. They don't have the phantom home button problem. But they are in Android 8. I actually don't have a problem on click the multitasking button to go back to the app but the problem is on the games and that stuff. So if I go back to Android 8 the system will update automatically to 9? I didn't know that, I thought that it was volunteer hahaha. Btw I don't even know how to downgrade since I'm not a moto user of all life. This is my first experience with a moto phone and it sucks. . Hahaha actually the home button problem happen.
Click to expand...
Click to collapse
It may not immediately update the OS after a downgrade, but you would get a notice there's an update available, even on a rooted phone. Since root only removes the barriers that're usually there to keep the less knowledgeable from hurting their phones, you'd still get any update notices a non-rooted phone would usually get. There is an app called NoBloat Free, and with it there are two files you'd be able to block that'd keep your phone from updating when you don't want it to. I'm not sure if the app is still in the Play Store or not, but I did use it on my Note 4, and it worked pretty well.
On a side note, I've had Opera open on my phone for a while now, and so far it hasn't gone back to the home screen yet. As for the phone itself, Moto phones are pretty good phones, my Z2 Force is my fourth phone from Moto (the other three being the RAZOR smartphone, Bionic, and the original RAZOR, which I sometimes miss). For all we know, our issue could be caused by a software glitch, hence my desire to root and test a different ROM.

Do you know how to downgrade to 8.0? I'll try it, it's a good phone and I didn't pay so much por this, that's why I'm not that angry. I won't root the phone since the games I play would kick me from the game. So just for make me sure I understand, do you reestablished the phone with a computer or from the same phone?

will4958 said:
My concern is whether the root method I found is legit or not. The only reason why I want to attempt it is because the description mentions the specific model of my phone. All variants of the Z2 Force start with XT789-, but it's the number after the '-' you have to look for, and for Verizon users is '01'. Rooting the phone will let me install a different version of Android that should help me narrow down the cause of the glitch. Since your phone is doing the same thing mine is, it's more-than-likely not due to an app, so it has to be either the OS or a hardware thing.
Click to expand...
Click to collapse
My man, I found something, I think it's a Verizon app's problem, there is a post in Reddit with more people having this problem, one of them leading to the conclusion that two apps of Verizon update recently. I don't know if that work. Btw I leave the link to that post. https://www.reddit.com/r/Moto_Z/com..._source=amp&utm_medium=&utm_content=post_body

Eco0901 said:
My man, I found something, I think it's a Verizon app's problem, there is a post in Reddit with more people having this problem, one of them leading to the conclusion that two apps of Verizon update recently. I don't know if that work. Btw I leave the link to that post. https://www.reddit.com/r/Moto_Z/com..._source=amp&utm_medium=&utm_content=post_body
Click to expand...
Click to collapse
I think I may have finally given my phone the smack in the pants it needed to start behaving itself again. I followed the link you provided, and one of the comments suggested installing any updates for a couple Verizon apps and disabling them. Not sure if this would work on a non-Verizon phone or not, but I've had the XBox app open on my phone for over 20 minutes now, and so far it hasn't minimized yet. To be accurate, I even closed & reopened the app. The apps mentioned were Verizon App Manager & My Verizon Services. I was able to disable the first app, but not the second, and rebooted my phone after doing so.
If your phone isn't from Verizon, there may be a similar pair of apps you could try disabling, though I'd probably look it up first to be on the safe side.
Update: It's been almost two hours now and the app still hasn't closed. Now, to get the screen protector residue off my phone.