Related
Quick question to see if anyone is experiencing the same issue...
Occassionally after using a speed dial, going into the call log or contact list and clicking on a contact, it can take up to 5 seconds before the phone actually dials the number.
This is completely random, but quite annoying.
Thanks
mikea3000 said:
Quick question to see if anyone is experiencing the same issue...
Occassionally after using a speed dial, going into the call log or contact list and clicking on a contact, it can take up to 5 seconds before the phone actually dials the number.
This is completely random, but quite annoying.
Thanks
Click to expand...
Click to collapse
True for me too. Sometime it takes much longer than 5 seconds for me though, something around 30 seconds. And if I dial the number again during the non-responsive time, it gets stacked there, so when it "comes back to life", it will dial the first number first, if you cancel it, it will go on to dial the second number.
513263337 said:
True for me too. Sometime it takes much longer than 5 seconds for me though, something around 30 seconds. And if I dial the number again during the non-responsive time, it gets stacked there, so when it "comes back to life", it will dial the first number first, if you cancel it, it will go on to dial the second number.
Click to expand...
Click to collapse
I have the same exact issue. Hopefully its fixed in an update
I have the same issue. And if you press the send button multiple times while it is "hanging", after you hang up the call it will call the number back the same amount of times you hit the send button.
Sent from my SGH-T989 using xda premium
This actually started happing to me today... but its not 5 seconds, more like 10 to 20... really really annoying.
dialer bug
Am I the only one experiencing issues with dialer. Sometimes it takes about 10 to 15 seconds after touching a contacts name for it to dial. And if you press it more then once it will redual that person s number as many times. Any suggestions?
I have the same thing
Sent from my SGH-T989 using XDA App
I have the same issue and started a thread about it last week.
http://forum.xda-developers.com/showthread.php?t=1358374
This is the only con on the gs2 to me. Hopefully we get a 2.3.6 update and thus gets fixed
Has anyone else been experiencing this issue? When I reboot the phone, it goes away, only for awhile. When my phone's screen is off, and someone texts me, i will see the message on the lock screen. If I tap the unread message from the lock screen, it will go directly to that message. However, when I back out to the home screen, I see the unread message count still showing that message. If I tap on Messages, i don't see any unread messages, yet it continually shows it still have one. It doesn't go away.
Anyone else experiencing this issue?
I had to reboot and it went away.
Sent from my SM-N900T using XDA Premium 4 mobile app
blakkheartt12 said:
I had to reboot and it went away.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When I reboot, it goes away also, but it keeps rearing it's ugly head every now and then.
I know the importance of rebooting our phone. However, this is a $700+ phone that supposed to be a "premium" top-of-the-line device, that I need to reboot several times per day because the SMS Messages unread count is off.
(scratching head) doesn't sound right.
lawalty said:
When I reboot, it goes away also, but it keeps rearing it's ugly head every now and then.
I know the importance of rebooting our phone. However, this is a $700+ phone that supposed to be a "premium" top-of-the-line device, that I need to reboot several times per day because the SMS Messages unread count is off.
(scratching head) doesn't sound right.
Click to expand...
Click to collapse
I would backup the messages and clear data on the app.
Anybody else using a moto 360 with their nexus 6 on Verizon?
I am having connectivity problems between the watch and the phone. Sometimes I speak into the watch and Google is thinking, thinking, and then stops. Like it can't reach the phone. Anyone else?
I don't know if this is a Nexus 6 on Verizon, nexus 6 in general, or moto 360 problem.
As I'm reading about this, it seems like this might be not only a Nexus 6 and Moto 360 problem, but an Android Wear/ Lollipop problem. Hopefully if 5.1 comes out soon, it'll fix this.
No issues here since xmas with my 6.
Thanks for the reply. Weird.
funkpod said:
Anybody else using a moto 360 with their nexus 6 on Verizon?
I am having connectivity problems between the watch and the phone. Sometimes I speak into the watch and Google is thinking, thinking, and then stops. Like it can't reach the phone. Anyone else?
I don't know if this is a Nexus 6 on Verizon, nexus 6 in general, or moto 360 problem.
Click to expand...
Click to collapse
This definitely happens to me too. After giving it a command the little circle keeps spinning until it comes back displaying "offline" even though I'm in an area with good reception. Sometimes though it just keeps spinning until I eventually swipe right to dismiss it and try again. Sometimes when trying to get directions from my watch it'll tell me to open Maps on my phone in order to continue.
An issue that persists for me is immediately upon plugging my Nexus 6 into its charger my 360 disconnects. I notice this immediately because the lost phone notification pops up on my watch and it vibrates sporadically. This is an issue that has really puzzled me because I can't tell what it could possibly be related to.
I used to have issues with text notifications not being pushed, but this has stopped happening. From time to time my watch will disconnect from my phone for seemingly no reason, and I'll get a "did you leave your phone?" notification. This happened today even, while I was using my phone. Other times when I walk out of range and then walk back into range it won't automatically reconnect. When this happens I have to open Android Wear, select Disconnect (even though Android wear will display "connecting...) And then Connect, and it'll connect again.
Almost half the time I go to send a text by voice I get the issue the OP mentioned, where the circle keeps spinning and nothing happens, or "offline" is displayed. I would really love a solution to this as sending texts is a core feature of Android Wear, and it totally defeats the purpose of the smart watch if it's supposed to save you from having to pull out your phone.
BTW I have an AT&T Nexus 6
Sent from my Nexus 6 using XDA Free mobile app
No issue for me, mine working perfectly but mine is international edition Nexus 6 and running CM 12 ROM.
osiris010 said:
This definitely happens to me too. After giving it a command the little circle keeps spinning until it comes back displaying "offline" even though I'm in an area with good reception. Sometimes though it just keeps spinning until I eventually swipe right to dismiss it and try again. Sometimes when trying to get directions from my watch it'll tell me to open Maps on my phone in order to continue.
An issue that persists for me is immediately upon plugging my Nexus 6 into its charger my 360 disconnects. I notice this immediately because the lost phone notification pops up on my watch and it vibrates sporadically. This is an issue that has really puzzled me because I can't tell what it could possibly be related to.
I used to have issues with text notifications not being pushed, but this has stopped happening. From time to time my watch will disconnect from my phone for seemingly no reason, and I'll get a "did you leave your phone?" notification. This happened today even, while I was using my phone. Other times when I walk out of range and then walk back into range it won't automatically reconnect. When this happens I have to open Android Wear, select Disconnect (even though Android wear will display "connecting...) And then Connect, and it'll connect again.
Almost half the time I go to send a text by voice I get the issue the OP mentioned, where the circle keeps spinning and nothing happens, or "offline" is displayed. I would really love a solution to this as sending texts is a core feature of Android Wear, and it totally defeats the purpose of the smart watch if it's supposed to save you from having to pull out your phone.
BTW I have an AT&T Nexus 6
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for all that input. I definitely see the beginning part as being the problem that I am having.
My 360 and Nexus 6 don't seem to have an issue.
Have you tried updating Google Play Services?
kmcla said:
My 360 and Nexus 6 don't seem to have an issue.
Have you tried updating Google Play Services?
Click to expand...
Click to collapse
Everything appears to be up to date...
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Make sure 'card previews' turned on from the android wear app, other wise your experience with the faces sounds buggy! A factory reset would help on that.
Factory reset doesnt work, this also happens to me since the update, looks like this is a firmware problem.
Damnit, I wish I didn't update.
Battery is also noticeably worse.
airjordan223 said:
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Click to expand...
Click to collapse
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
antknee2016 said:
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
Click to expand...
Click to collapse
Can you found a way to fix it?
Enviado desde mi SM-N920I mediante Tapatalk
The first issue is because the watch now comes on in ambient mode first. Even if you don't use ambient mode. It sucks. Luckily i use Watchmaker for my watch face so I went in and made all the parts (hands date etc...) to be visible in ambient mode.
I have noticed that if I wait a couple of seconds the notification does appear on my watch screen but it is after the vibrate, not immediate. I thought it wasn't showing up at first too. Still, I wish it was quicker as I look right away.
Sent from my SHIELD Tablet using Tapatalk
I went back to using Facer for my watchface and the delay is gone.
Also did they completely remove the restart option? Now it's just power off, and then press and hold the side button.
I'm experiencing both issues as you do on 6.0.1.
Also yes, reboot option is gone from update.
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Sent from my SHIELD Tablet using Tapatalk
frenziedfemale said:
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Click to expand...
Click to collapse
Reboot is not reset...
I've also noticed that theater mode does not work after the mm update (unrooted, ota). I usually set it to theater mode at night to avoid burn in and just because I don't want it on all night. Now, it looks like it's blacked out, but when I wake up, the charging screen is lit up. Anyone else getting this?
I have the exact same issue after the update. Theater mode will not keep the display off if the watch is being charged. Off the charger, it works as expected. Quite an annoying bug.
If I turn ON the theatre mod with double press the power button before I put the clock on the charging dock, after that screen continue charge with screen off.
For me it's work.
Can anyone try it?
Sent from my D6503 using XDA Free mobile app
Just tried that - doesn't work for me. Screen turns off but once I put it on the charger, it comes back on after a few seconds. I'm watching it and it's still on a few minutes later.
Same here. Screen always turns back on
I'm getting the first bug the OP mentioned havn't noticed the second one though.
However the first bug is annoying enough, hopefully there'll be a quick patch.
Little patience, update to Marshmallow is great.
Here's what I mean with screen off when charge:
So in the morning until you take it out of the dock and go to work.
Sent from my D6503 using XDA Free mobile app
still on 5.0.1
man i just boughjt it 2 days ago and battery sucks,now i am trying to update cause i heard batter improved,but i cant ,watch start download but take too long and then show me a message charger to update blah blah but phone is charger is over 90 percent i have reset phone and uninstalled app many times this is ridiculous now i know why motorola was giving away this pos when yopu buy the 64gb moto x pure edition arrrrgggg
Srandista said:
Reboot is not reset...
Click to expand...
Click to collapse
Sorry I read wrong...but wouldn't you just use the power off option and then turn back on to reboot?
I have a weird problem that searching the settings and googling has not been able to solve.
If my Tab S is not connected to the internet for any length of time, any notification that I get whether it be facebook, twitter, email, etc blasts all at once as soon as I reconnect. Even if those notifications are days old and I've already checked them on my computer or phone. It's almost as if there's a store of notifications that blasts all at once, and it really slows down my tablet andI have to sit an wait for the rapid dinging and pop ups are finished. Sometimes I don't use my tablet for a week and I'll literally have hundreds of notifications hit at once. Starting to get really annoying, please help!
Thanks in advance.
p.s. I love this tablet, I just want it not to be a **** head
Yup same
Sent from my SM-T800 using Tapatalk