Moto 360 Does Not Show Contact Photo For Incoming Calls - Moto 360

No photo when calling
Hi, there is a problem with photo when some one is calling to me, the name of contact is showing, I can reject call etc. But there is no photo of that contact, photo is avaliable in my favorites contact in my watch, so what I need to do to fix that problem?

i faced this once
dolar16 said:
Hi, there is a problem with photo when some one is calling to me, the name of contact is showing, I can reject call etc. But there is no photo of that contact, photo is avaliable in my favorites contact in my watch, so what I need to do to fix that problem?
Click to expand...
Click to collapse
I once had the same issue. But I restarted the watch and it was all good...
I hadn't restarted it for more than a week before that...

nijom said:
I once had the same issue. But I restarted the watch and it was all good...
I hadn't restarted it for more than a week before that...
Click to expand...
Click to collapse
So, You just restarted device? No factory reset or something like that? just turn off an on?

No factory reset!
dolar16 said:
So, You just restarted device? No factory reset or something like that? just turn off an on?
Click to expand...
Click to collapse
A normal power off and power on, then reconnected the watch and it was good...

Related

Ringtone problems

This sounds really stupid but anyone else having a problem with the ringtone you select staying? I select a ringtone and then verify but every time I get my first call after it goes to dumb Verizon airwaves ringtone. My notification tones stick like normal. Just really getting annoying.
Thanks
Never had that problem ....
Sent from my iPhone using Tapatalk
Yeahp i had it...seemed to have stopped tho.
I'm still having the problem with the ringtone not staying. Still reverts the VZW Airwaves after first call. I checked to see if I disabled an app to cause this and struck out there. I'm wondering if its do not disturb. I keep it on always and only let contacts call.
Same problem here
Psychotic Penguin said:
Same problem here
Click to expand...
Click to collapse
Hopefully someone will chime in with why it's happening. Ive run out of ideas.
I saw that someone did a factory reset that solved the issue
Any news?
Psychotic Penguin said:
Any news?
Click to expand...
Click to collapse
Mine is still happening. I've been busy working but I may try a factory reset. My phone started bootlooping this morning when I got home from work and put it on the charger. Restarted like 6 times. Lots of bugs
I'm still not having any issues, well except this
Harleydroid said:
This sounds really stupid but anyone else having a problem with the ringtone you select staying? I select a ringtone and then verify but every time I get my first call after it goes to dumb Verizon airwaves ringtone. My notification tones stick like normal. Just really getting annoying.
Thanks
Click to expand...
Click to collapse
I had this issue at first. Do you have ES File explorer? Mine was borked because of that. So i had to disable that from being default. Then it still wasn't working for my SMS only text tone so I switched from Hangouts to Google Messenger, changed the tone then switched back to Hangouts.
When I was doing that Hangouts had the right text tone selected but that wasn't what played. So i used "SMS" as default SMS account vs my Gmail then switched it back the be more organized and it worked. Haven't tried changing tone since so idk if thats needed each time
Sent from my Samsung Galaxy time bomb 7
Lord Syrics Jr. said:
I had this issue at first. Do you have ES File explorer? Mine was borked because of that. So i had to disable that from being default. Then it still wasn't working for my SMS only text tone so I switched from Hangouts to Google Messenger, changed the tone then switched back to Hangouts.
When I was doing that Hangouts had the right text tone selected but that wasn't what played. So i used "SMS" as default SMS account vs my Gmail then switched it back the be more organized and it worked. Haven't tried changing tone since so idk if thats needed each time
Sent from my Samsung Galaxy time bomb 7
Click to expand...
Click to collapse
My texts and notifications stay fine. It's the ringtone.
Harleydroid said:
My texts and notifications stay fine. It's the ringtone.
Click to expand...
Click to collapse
I'd again verify your not going through a file explorer menu and thats its not the default app. Instead system explorer
Sent from my Samsung Galaxy time bomb 7
Did a factory reset, the issue hasn't returned!
Psychotic Penguin said:
Did a factory reset, the issue hasn't returned!
Click to expand...
Click to collapse
Okay good to hear. I'm just going to wait and deal with it since I will be exchanging for a new device. Thanks again for letting me know.
No problem
Been having this same issue on my replacement Note 7, (ringtone never switched to default on my original Note 7). I used Samsung cloud to restore some settings on my replacement Note 7 and that could be the culprit.
I really do not want to do a factory reset as I just spent a ton of time setting my phone back up this week.
I moved the ringtone from SD card to internal to see if that would fix it from reverting. Will see...
I had the issue on my original defective Note 7. Not having it on my new one.
Harleydroid said:
Okay good to hear. I'm just going to wait and deal with it since I will be exchanging for a new device. Thanks again for letting me know.
Click to expand...
Click to collapse
Maybe unrelated, but are you using any kind of audio volume manager? Some of them (like AudioManager Pro) will store ringtone information, so when you toggle modes, the ringtone comes along for the ride (reverting one that you may have manually selected).
I put a brand new ringtone on my internal drive Ringtone folder yesterday and when I turned on my phone this morning, it had reverted back to the Verizon default ringtone again. Any ideas how to get the ringtone to stick other than a factory reset?

Watch not receiving notifications.

Anyone else having this problem. It's only just happened. I've unpaired, uninstalled software, done everything I can think of. My phone is connected to it but when I get a message etc it doesn't come up on my watch.
Update
Charlie3999 said:
Anyone else having this problem. It's only just happened. I've unpaired, uninstalled software, done everything I can think of. My phone is connected to it but when I get a message etc it doesn't come up on my watch.
Click to expand...
Click to collapse
I've factory reset my phone and watch. Still not working. A phone call comes up on my watch so it must be a setting I can't work out.
Mine was working yesterday on a stock rooted rom on my phone, but not today on a modified rom. What are you running?
Charlie3999 said:
Anyone else having this problem. It's only just happened. I've unpaired, uninstalled software, done everything I can think of. My phone is connected to it but when I get a message etc it doesn't come up on my watch.
Click to expand...
Click to collapse
Hi,
I also had issues and did not recieve messages on my watch... (see: https://forum.xda-developers.com/huawei-watch/help/messages-arriving-watch-t3510071)
Did your recently reset your phone to factory settings?
Because the new version of Android Wear is asking for permissions to recieve notifications.
I did everything but the solution was simple for me:
Open the Android Wear app and on startup page there should be a blue notification which says something like klick here to enable notifications...klick this button and allow the notification permission and everything should work fine now.
htcdesire-hd said:
Hi,
I also had issues and did not recieve messages on my watch... (see: https://forum.xda-developers.com/huawei-watch/help/messages-arriving-watch-t3510071)
Did your recently reset your phone to factory settings?
Because the new version of Android Wear is asking for permissions to recieve notifications.
I did everything but the solution was simple for me:
Open the Android Wear app and on startup page there should be a blue notification which says something like klick here to enable notifications...klick this button and allow the notification permission and everything should work fine now.
Click to expand...
Click to collapse
Can you post a picture of where you mean. I can't seem to see where you're talking about.
Charlie3999 said:
Can you post a picture of where you mean. I can't seem to see where you're talking about.
Click to expand...
Click to collapse
I meant this notification with the label "Turn on watch notifications". (see attachment)
Charlie3999 said:
Can you post a picture of where you mean. I can't seem to see where you're talking about.
Click to expand...
Click to collapse
htcdesire-hd said:
I meant this notification with the label "Turn on watch notifications". (see attachment)
Click to expand...
Click to collapse
You can also access that in Settings > Apps > Gear Icon (upper right) > Advanced / Special Access > Notification access, then toggle on the Android Wear if it is not on
Thanks a bunch... I went to the app and noticed it said not connected... Touch to reconnect... Had to do that 4x and it finally connected
htcdesire-hd said:
Hi,
I also had issues and did not recieve messages on my watch... (see: https://forum.xda-developers.com/huawei-watch/help/messages-arriving-watch-t3510071)
Did your recently reset your phone to factory settings?
Because the new version of Android Wear is asking for permissions to recieve notifications.
I did everything but the solution was simple for me:
Open the Android Wear app and on startup page there should be a blue notification which says something like klick here to enable notifications...klick this button and allow the notification permission and everything should work fine now.
Click to expand...
Click to collapse
I'm having the same problem only I've done all of the above and it's still not working.
Notifications work for everything except messages and gmail.
It's only been doing it since the watch updated to Android Wear 2.5.
I have reset both the phone and the watch to factory, deleted and reinstalled the apps and still nothing.
bjm374 said:
I'm having the same problem only I've done all of the above and it's still not working.
Notifications work for everything except messages and gmail.
It's only been doing it since the watch updated to Android Wear 2.5.
I have reset both the phone and the watch to factory, deleted and reinstalled the apps and still nothing.
Click to expand...
Click to collapse
Same here after OTA update to 2.5 I can't receive notifications on my watch anymore..had to reset my phone and watch but still not working.
I wonder if there's a way to roll back to 2.0???
bjm374 said:
I wonder if there's a way to roll back to 2.0???
Click to expand...
Click to collapse
I don't know but I wish there was an easy way to go back to 2.0.
Hopefully someone far smarter than me will see this and tell us how easy it is ?
try to "sync all apps" again with the android wear app.. then shut down and restart the watch. This works until I rebooted my phone, then I had to do it again
bjm374 said:
Hopefully someone far smarter than me will see this and tell us how easy it is
Click to expand...
Click to collapse
It's obvious now that the current Android Wear app on the phone needs to be updated to become compatible with the 2.5.
My workaround to this issue was, which I've tested many times and worked so far, finger crossed!:
1-Turn the watch off
2-Turn the Bluetooth off on the phone
3-Turn the watch on completely
4-Turn on the Bluetooth on the phone.
The first notification will take 3-4 seconds to arrive.
Excellent effort. So far that seems to be working for me. I haven't received any messages yet but I'm getting my email notifications (which I wasn't before).
Thank You
hagba said:
It's obvious now that the current Android Wear app on the phone needs to be updated to become compatible with the 2.5.
My workaround to this issue was, which I've tested many times and worked so far, finger crossed!:
1-Turn the watch off
2-Turn the Bluetooth off on the phone
3-Turn the watch on completely
4-Turn on the Bluetooth on the phone.
The first notification will take 3-4 seconds to arrive.
Click to expand...
Click to collapse
That worked for me, thanks.
Oddly enough though, I followed the instructions step by step and actually had a facebook notification pop up on the watch immediately after it powered up but before I'd turned bluetooth back on on the phone!
@hagba Thank you very much those step work. I also noticed that google assistant doesn't work when you send your first query. You have to ask it something, click on the little colored dots then ask it the same thing again and it works. You have to do this everytime you make any request. Annoying. I hope the knuckleheads at Google will fix these annoying issues soon.
snapperheadjoe said:
@hagba Thank you very much those step work. I also noticed that google assistant doesn't work when you send your first query. You have to ask it something, click on the little colored dots then ask it the same thing again and it works. You have to do this everytime you make any request. Annoying. I hope the knuckleheads at Google will fix these annoying issues soon.
Click to expand...
Click to collapse
Myself I have no such problem with the Google assistant, it works fine from the first voice command without touching the colored dots, even "Ok Google" works well.
hagba said:
It's obvious now that the current Android Wear app on the phone needs to be updated to become compatible with the 2.5.
My workaround to this issue was, which I've tested many times and worked so far, finger crossed!:
1-Turn the watch off
2-Turn the Bluetooth off on the phone
3-Turn the watch on completely
4-Turn on the Bluetooth on the phone.
The first notification will take 3-4 seconds to arrive.
Click to expand...
Click to collapse
Worked for me, too. Got a message notification before I turned the Bluetooth back on, lol:good:

Screen won't turn on for incoming calls

Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Maybe give a factory reset a go.
moralesd66 said:
Maybe give a factory reset a go.
Click to expand...
Click to collapse
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
tdetroit said:
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
Click to expand...
Click to collapse
Hard reset....As in power off and on right? Try booting into recovery mode and deleting cache and data.
tdetroit said:
Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Click to expand...
Click to collapse
My TMO one did that today, heard it ringing but screen remained off.
Sent from my SM-N950U using Tapatalk
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
tdetroit said:
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
Click to expand...
Click to collapse
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Maybe the setting for proximity...in pocket...turn off
Limeybastard said:
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
I've tossed the screen protector after 1 day because it kept making a clicking sound on the top corner. No case on it.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
tdetroit said:
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
Click to expand...
Click to collapse
Factory reset , if no go , replacement.
Sent from my SM-N950U using Tapatalk
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
tdetroit said:
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
Click to expand...
Click to collapse
they know absolutely **** about anything
I never use retail store
Another way to fix this is to call yourself on another phone while your Note 8 screen is on. When the call comes in, don't answer but slide down the notification bar and you will see your call. Adjust notifications to not block/be silent.
tdetroit said:
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
Click to expand...
Click to collapse
I went into Settings, Display, but nothing about double tap to wake-up. Samsung runs on AMOLED and that function is on other screens like Sony Xperias.
I do notice another thing going into Notifications settings and I see that the Phone app is Muted. I don't know how to get out of it.
The solution is the person who posted above. You call yourself, and swipe to unblock Silence notifications for your phone app. It's weird how it was set that way, but that's the best solution!
How do I unmute phone call notifications?
Thanks! My incomimg calls now appear on my screen!
I tired the unblock silence notifications and that still has not fixed it as well as a hard reset. Anyone else got any suggestions?
Thanks
Ian
Fix to dark screen on incoming call
Step 1: call youself
Step 2: swipe down on notification bar to view the call(usually how you would answer while dealing with this issue)
Step 3: swipe the call to the right and click the setting wheel.
Step 4: select "do not hide notifications"
Step 5: test call after doing this with the screen off, its should work.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
I turned "block accidental touches" off.
That worked for me!
THANKS

Dialer extreme lag?

Hi I have 2 s9 pluses, both are exynos versions, I have a weird issue that when I try to call someone from my contacts list, recents dialer, in fact anywhere there is a huge delay in the call going through. Maybe upto a minute before it actually shows the screen that shows it is actually dialling the number. Clear cache, factory reset, etc all tried nothing has worked. Mine are both dual SIM models and both have this issue, anyone else having this problem? Any solutions? Thanks
ramheer said:
Hi I have 2 s9 pluses, both are exynos versions, I have a weird issue that when I try to call someone from my contacts list, recents dialer, in fact anywhere there is a huge delay in the call going through. Maybe upto a minute before it actually shows the screen that shows it is actually dialling the number. Clear cache, factory reset, etc all tried nothing has worked. Mine are both dual SIM models and both have this issue, anyone else having this problem? Any solutions? Thanks
Click to expand...
Click to collapse
Nope not on mine. Its flying as opposed to galaxy s3-6 where there was noticeable lag. Maybe reddit the settings maybe its syncing info from your social media accounts a lot?
skivnit said:
Nope not on mine. Its flying as opposed to galaxy s3-6 where there was noticeable lag. Maybe reddit the settings maybe its syncing info from your social media accounts a lot?
Click to expand...
Click to collapse
Good point I will try to look into

Calls taking forever to connect after update to Android 10.

All was fine on Pie, no real call issues. Since I've upgraded to Android 10. I will hit the call button to make a call. it takes like 15 to 20 seconds or more to connect and I see the mute button, keypad, speaker button and so on. Very annoying! Anyone else experiencing this issue? Once connected, all is fine.
Hey, I ran into this issue yesterday, I cleared the phone app cache and data and the issue persisted. I ran a factory reset this morning and the phone calls connect immediately.
Android has come a long way with restoring from the cloud, give it a shot.
Ill let you know if the issue comes back.
Here's your answer, https://www.phonearena.com/news/Fix...xels-updated-to-Android-10-is-a-snap_id118768
That's the fix!!!
spotmark said:
Here's your answer, https://www.phonearena.com/news/Fix...xels-updated-to-Android-10-is-a-snap_id118768
Click to expand...
Click to collapse
That is EXACTLY what the issue was! Thanks for the quick reply!
spotmark said:
Here's your answer, https://www.phonearena.com/news/Fix...xels-updated-to-Android-10-is-a-snap_id118768
Click to expand...
Click to collapse
I can confirm that instantly fixed the problem for me. Thank you.
I just denied phone permission to the My Verizon app - fixed.

Categories

Resources