Related
Just got a new 360...stock everything. Watch faces and apps simply don't sync. No error messages, nada... I have the most up to date moto connect and Android wear on my 2014 moto x... Any ideas?
terrapin69 said:
Just got a new 360...stock everything. Watch faces and apps simply don't sync. No error messages, nada... I have the most up to date moto connect and Android wear on my 2014 moto x... Any ideas?
Click to expand...
Click to collapse
Had the same issue the first day I got mine. I did a Reset on mine and it's been fine since.
Ramer said:
Had the same issue the first day I got mine. I did a Reset on mine and it's been fine since.
Click to expand...
Click to collapse
I had the same problem as well. Also did a reset, dropped bt connections resynced and hit the "resync" apps button.
All set. Sometimes it takes about 15 minutes for the phone to send over the app/watchface.
Tried....
brchickery said:
I had the same problem as well. Also did a reset, dropped bt connections resynced and hit the "resync" apps button.
All set. Sometimes it takes about 15 minutes for the phone to send over the app/watchface.
Click to expand...
Click to collapse
Reset twice - nada - will try again I guess - Thanks much
Mike
so, day three and still nada - no syncing - but notifications are coming through fine. I have reset the damn thing so many times it's not funny and I have installed/uninstalled the android wear app from my phone several times too - could it be a defective watch? I highly doubt it. MOT suggested I try "pairing: it to another phone...who knows at this point - I remember I had a Pebble once - never, EVER an issue
Hi
My moto 360 (1st gen) does not notify incoming calls since yesterday, but notifies other notifications perfectly.
Whats wrong?
First step try rebooting your watch and phone, see if that sorts it.
Have you changed any settings since yesterday, or upgraded to Marshmallow? I found that Marshmallow and more specifically Doze really messed with notifications on my watch, in the end I had to switch off Doze to fix the issues.
If all that fails do a factory reset on your watch.
Zammo76 said:
First step try rebooting your watch and phone, see if that sorts it.
Have you changed any settings since yesterday, or upgraded to Marshmallow? I found that Marshmallow and more specifically Doze really messed with notifications on my watch, in the end I had to switch off Doze to fix the issues.
If all that fails do a factory reset on your watch.
Click to expand...
Click to collapse
I'm having the same problems as well following update to Marshmallow (Moto 360 1st Gen). I've already restarted watch and phone with no success. On a side note I note that there is no longer an option to restart on the watch only power off (am I missing something here?) Similarly not seeing the factory reset option either. You mention that you had to switch off Doze to fix the issues. Sorry if I sound naive, but I'm not seeing how to do that either. My phone is a Galaxy S3 on Android 4.4 which obviously doesn't have dose so I'm not familiar with that feature otherwise. Any help would be appreciated as incoming phone call notification is one of the 'must have' features in a smart watch for me.
Regards.
Doze is part of the Marshmallow update, on phones. Its conserves battery by putting applications into sleep mode, which basically stops them being able to communicate with the phone unless you authorize it or the phone has been woken up. For me this was stopping a lot of Android Wear functions from behaving properly, namely call notifications.
If your S3 isn't running Marshmallow my fix, doesn't really apply to you.
Restart and Factory reset are under Settings on the watch.
If your still having issues email Motorola customer service, I've found them to be quite helpful.
Mine started doing that BEFORE the Marshmallow update. It would ring AFTER I got the call.
I have same problem (the calls appears in the watch as "unknown caller")
The phone operator (TIM) send number info of local calls in this format: XXXXX-XXXX
I already modify my phonebook, I used all possible number formats...
Moto Maxx: 5.0.2
Moto 360 1gen: 6.0.1
Android Wear: Latest
Brazil
sforde said:
On a side note I note that there is no longer an option to restart on the watch only power off (am I missing something here?) Similarly not seeing the factory reset option either.
Click to expand...
Click to collapse
Zammo76 said:
Restart and Factory reset are under Settings on the watch..
Click to expand...
Click to collapse
I have the same issue, after the 6.0.1 update I no longer have a "Restart" or a "Factory reset" option under settings. It was suggested in another thread that using the "Unpair with phone" option will perform a factory reset. I'm going to try that tomorrow.
Zammo76 said:
Doze is part of the Marshmallow update, on phones. Its conserves battery by putting applications into sleep mode, which basically stops them being able to communicate with the phone unless you authorize it or the phone has been woken up. For me this was stopping a lot of Android Wear functions from behaving properly, namely call notifications.
If your S3 isn't running Marshmallow my fix, doesn't really apply to you.
Restart and Factory reset are under Settings on the watch.
If your still having issues email Motorola customer service, I've found them to be quite helpful.
Click to expand...
Click to collapse
alryder said:
I have the same issue, after the 6.0.1 update I no longer have a "Restart" or a "Factory reset" option under settings. It was suggested in another thread that using the "Unpair with phone" option will perform a factory reset. I'm going to try that tomorrow.
Click to expand...
Click to collapse
Thanks Zammo for the info.
Calls started to appear on the watch once more after a couple of days. Didn't do anything else, so I can't say why.
May try suggestion to unpair phone soon. Phone itself is taking very long to respond to basic operations and battery life is getting pathetic. Going to do a factory reset, clear cache etc (may even try another ROM).
alryder said:
I have the same issue, after the 6.0.1 update I no longer have a "Restart" or a "Factory reset" option under settings. It was suggested in another thread that using the "Unpair with phone" option will perform a factory reset. I'm going to try that tomorrow.
Click to expand...
Click to collapse
Just to confirm, using the "Unpair with phone" option does perform a factory reset.
Hi alryder,
Just wanna know "Unpair with phone" fix the call notification issue you had?
I can only swipe down from the top to bring my notification down in "settings"
Everywhere else, the top part of the screen does not react to my touch inputs.
So I am unable to drop down from home screen or hit back in emails, or even open a new tab in chrome.
as nothing i touch is registering, but only in settings.
Ive swapped wallpapers, grid size, resolution, theme, 120hz to 60...nothing is working inclusing clearing cache,
Do I have to factory reset, jesus.
WTF is this crap, why is there so many reports of unstable updates!!!
MachRc said:
Do I have to factory reset, jesus.
Click to expand...
Click to collapse
Yes, yes you do. Anytime you do a major OTA upgrade it's best to do one to avoid problems.
That may not fix it though...
Okay, I checked and noticed it works 2 seconds after start up and realized it was energy ring that is not compatible with Android 12.
I've never factory reset for OTA ever. Only for a few roms in the past.
MachRc said:
Okay, I checked and noticed it works 2 seconds after start up and realized it was energy ring that is not compatible with Android 12.
I've never factory reset for OTA ever. Only for a few roms in the past.
Click to expand...
Click to collapse
Lol, I stopped doing OTA updates over 2 years ago. Many of the loaded apps are running on their factory versions too.
Couple months ago a Buds+ Wearables update broke the sound, thankfully it wasn't a firmware update and was reversible. Still it took a good 2-3 hours to repair and block Wearables updates.
It remains blocked.
In the last 7 years upgrades and updates have caused me far more damage and wasted time than malware ever did on Androids. Zero malware forced reloads in 7 years.
It may be official but it still could be bugware...
My Pixel 6 Pro has a similar problem ever since the Mar 5 update has been installed. Since then, every phone call I made comes with the non-stop notification tone literally every second. For now, I managed to get around it by enabling the "DND Mode", but it isn't a long-term solution.
Is there a way I can re-apply the same update? or flashing a new one would help?
To be clear, you're saying that you keep getting the notification tone even after answering the call? If so, is it the same as your ringtone?
Is your bootloader unlockable? If so, Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
It wouldn't surprise me if that doesn't fix the issue, however. Have you tried rebooting? Maybe clear the cache and app data for the Phone app (but then you'd have to re-customize the settings for the phone app to your preferences).
I'm not on the March update, but I also don't receive many phone calls anyway.
that notification tone, during normal time, represents incoming message. It is very short, unlike a ringtone..
Tried rebooting and clearing cache and app data of the Phone app. In fact, that notification could likely come from anything like WhatsApp, Messenger, Twitter...
I noticed that the repeating tones would not happen if the phone is on silent mode. So for now this is my workaround.
Very interesting, and strange. There have been settings in some OEM's phone apps you could enable to get notification tones at regular paces - usually once a minute - while on a phone call, but the issue on yours is only similar since it's constant / every second.
I stick with my recommendation of clearing the app cache and data for the Phone app. I also assume you're using the stock Phone app that Google provides.
In my previous phone (OnePlus 6T), the very same tone happens once in a while, but only at the moment an incoming message arrives. Pretty sure I am not getting a new message every second this time around, and I think it was triggered by apps other than the Phone app. I just noticed that the same symptom showed up when I tried to play video clips from certain apps as well.
And yes, I am using the stock Phone app.
Sounds like a factory reset and only selectively installing and configuring apps, or trying to figure out which app is causing the issue.
If you factory reset, I would first not even restore any apps at all, so you can verify if you have the same problem without any third-party apps installed at first. I would suspect you won't have issues then. And then when you install apps, do it in groups of your most important ones first, maybe at the most 10 at a time, then re-verify each time if you have the same issue or not, then the next batch of app installs. It could be a particular setting in a app as well, so it's possibly merely installing an app might not be enough, so each group of apps you install, make sure and configure them as well.
If you don't factory reset, go the opposite way, uninstall your least important third-party apps and see if the issue disappears. Keep track of which apps you're uninstalling in each group. Keep doing this in reasonably sized groups of apps until you narrow down when the problem stops happening.
Once you find which group of apps being uninstalled keeps the issue from happening, you can reinstall in even smaller batches, among the ones you most recently uninstalled, and eventually find the one causing the issue. In some ways I think it's easier to go the other way around, though, start with a factory reset.
Found the culprit!
Kind of silly: I have installed this app "Internet Speed Meter Lite" when I first started using my P6P, which is for me to monitor my real-time network usage (courtesy of that endless WhatsApp - Google Drive restoring process....). It basically refreshes itself every second and this morning I tried temporarily disabling it, the problem goes away even when the phone is not set to silent mode.
Glad I didn't have to come to the point of factory resetting the device, as I really don't want to go through the WhatsApp restoring process.
Thanks for all the input, much appreciated.
I updated my OnePlus 9 Pro(LE2121_11_F.16) to Oxygen OS 13.0. But after the update, my home and recent apps gesture completely stopped working. I've rebooted the phone multiple times. I've also updated all my apps. I've cleared data for the apps - System Launcher, Gesture_motion Services and Gesture&motions. But none of it worked.
Factory reset
WarLord1712 said:
I updated my OnePlus 9 Pro(LE2121_11_F.16) to Oxygen OS 13.0. But after the update, my home and recent apps gesture completely stopped working. I've rebooted the phone multiple times. I've also updated all my apps. I've cleared data for the apps - System Launcher, Gesture_motion Services and Gesture&motions. But none of it worked.
Click to expand...
Click to collapse
Have you solved it? I also encountered the same thing. Home and recent apps (gesture/button) as well as Setting button on notification bar are not working.
Chivann said:
Have you solved it? I also encountered the same thing. Home and recent apps (gesture/button) as well as Setting button on notification bar are not working.
Click to expand...
Click to collapse
It was solved as the 2nd answer. Factory reset and everything works. Had to do the same, and no issues since.
ezpz.MiDAS said:
It was solved as the 2nd answer. Factory reset and everything works. Had to do the same, and no issues since.
Click to expand...
Click to collapse
Thanks for your reply. Factory reset isn't always ideal. Really hope there is any other solution.
I had this on the second day of upgrade. Before that I had edited the quick settings tiles and frozen some OOS bloatware using Titanium. After clearing cache and rebooting multiple times, I tried undoing all the changes (restored the tiles to the initial state and thawed all the bloatware). Nothing happened immediately, but after an hour or so it was fixed, I don't know how. Maybe just coincidence. Anyway mentioned it here in case it works for you.
ezpz.MiDAS said:
It was solved as the 2nd answer. Factory reset and everything works. Had to do the same, and no issues since.
Click to expand...
Click to collapse
Hello even I'm facing the issue and did it happen after the factory reset?
tathagatab said:
I had this on the second day of upgrade. Before that I had edited the quick settings tiles and frozen some OOS bloatware using Titanium. After clearing cache and rebooting multiple times, I tried undoing all the changes (restored the tiles to the initial state and thawed all the bloatware). Nothing happened immediately, but after an hour or so it was fixed, I don't know how. Maybe just coincidence. Anyway mentioned it here in case it works for you.
Click to expand...
Click to collapse
likewise, I think its because we edited the tiles as I clearly remember I just did that and the next day it stopped working the notification settings icon, back and recent apps. So if we factory reset and edit the tiles again will it reappear (the issue)?
I had the same issue but mine happened after finishing the setup. I lost internet at my house an couldn't compete the setup it said it needed wifi. So I went on with my day and that night I finished it and had this issue. After that I couldn't fix it. I had to do a factory reset and then everythings been working fine. I think it's an issue with the upgrade.
May 2023. OnePlus 8T f16 update.. it's still happening. Anyway to get it to work without factory reset? Ive tried Nova launcher trick, clearing settings, clearing data from apps for gestures launcher etc, reboots, reverting the tiles. Any other methods to make it work?
Hi,
I have the same issue with my OP9, but strangely enough, it only happens with third-party launchers. When on the system launcher, everything's peachy, but if I use another launcher as default (regardless of what it is, Nova, Microsoft, Lean, you name it), the Home button starts acting out again.
I can tap the Overview button, or the Back button, though, and with a third-party launcher, Gesture Navigation will work OK, more or less.
Maybe OP/Oppo don't like us using third-party launchers after all...
There's a new system update based on Oxygen OS 13.1 (LE2115_13.1.0.5..(EX1)) that seems to have solved the problem somehow.
Security Update dates back to April 2023, though...
EDIT: using Hyperion Launcher, the issue is still there and seems to occur when you are two levels or more deep in an app. For example, if you open the Play Store app, go to your apps and try to update them, you can close the app with the Home button. However, if you open Settings and dive down into the various menus more than three times, the Home button stops working.