Related
So I noticed that after I updated my phone to android 5.0 my watch needs to be reset, then when there is an incoming call, the watch shows the picture of the contact and does the same animation as before but only on the left side with the red deny button.
Am I missing something or is it really a bug, beacause the software is the latest on the watch, the wear app is updated, and in my mind the android 5 update should have the same already implemented stuff from the previous version...
So if anyone can share a bit of insight on the problem I would be grateful.
I can't help you with your problem, but I can confirm it.
I have my watch since I have Lollipop on my N5, so I can't make any references to Kit Kat or any version of any app or Android Wear before.
It only shows the deny button. But tbh, if you don't have a BT headset paired the accept button makes no sense at all as you can't speak through your watch let alone listen to your call partner.
yes i can confirm. have a n4 and was able to answer call on KK, but not on L. only can swipe from left to right.
kali113 said:
So I noticed that after I updated my phone to android 5.0 my watch needs to be reset, then when there is an incoming call, the watch shows the picture of the contact and does the same animation as before but only on the left side with the red deny button.
Am I missing something or is it really a bug, beacause the software is the latest on the watch, the wear app is updated, and in my mind the android 5 update should have the same already implemented stuff from the previous version...
So if anyone can share a bit of insight on the problem I would be grateful.
Click to expand...
Click to collapse
I had it working on my moto x KK and nexus 5 KK and as soon as the lollipop update im having the same issue... Also netflix doesnt give me the controls to pause/play a show anymore either.
If anyone finds out any information please post here, ill do the same. :good:
Got the same problem here. I thought that it's just me having that issue. I am using Nexus 5 running on Lollipop.
I am just curious, the notification comes from the dialer apk, so maybe reverting to the 4.4 kitkat dialer would fix it.
I don't know, it's worth a try...
I guess it will be patched in the upcoming few weeks, or in some custom roms, until then we just need to be patient.
Also if anyone would like to track the aosp issue, here it is:
Issue 79683: unable to answer calls with android wear
How I wish it could give an option to answer with phone loud speakers . useful while driving and without Bluetooth headset.
Sent from my Nexus 7 using Tapatalk
I have the same bug. Moto 360 and dialler from lollipop on a nexus 5. I cannot answer calls.
---------- Post added at 10:01 AM ---------- Previous post was at 10:00 AM ----------
Just the red dismiss and text reply on the watch are available.
Me too, only reject calls
Sent from my LG-D855 using XDA Premium 4 mobile app
i also noticed i wcouldnt answer a call via 360 the other day when a call came in while using navigation
it wouldnt answer, on the watch or the phone
N5 5.0 & 4.4W.2
Google has just released the latest versions for the android wear and google play services.
This will solve our problem!
I just notice it after someone called me and the answer function is now BACK! [emoji1]
Google Play Services (For Android 5.0 Lolipop):
http://www.apkmirror.com/apk/google.../google-play-services-6-5-96-1630522-438-apk/
Android Wear
http://www.apkmirror.com/apk/google-inc/android-wear/android-wear-1-0-5-1630507-apk/
[emoji106] [emoji106] Please hit thanks if this solves your problem! [emoji106] [emoji106]
Guys, just received new update to android wear app v 1.0.4.1611133
Sent from my SM-N910C using Tapatalk 2
I updated, but don't see anything different on my watch.
Yeah.. That's the funny thing.. Nothing new in the change log too... They were the same features from earlier version... May be the interim one needed for the coming big update of v2.0 and wear OS w5.0.1 rumoured to roll out coming Wednesday
Sent from my SM-N910C using Tapatalk 2
Same here, no difference. Probably needed for the new upcoming update.
I did get my watch rebooting when I installed the update.. I thought, new update, but no.. ohh well.
eatonjb said:
I did get my watch rebooting when I installed the update.. I thought, new update, but no.. ohh well.
Click to expand...
Click to collapse
It updates Play Services to 6.5.90 (from 6.1.xx) on the watch.
I updated to this and paired my 360 with my new Moto X. I've been getting the "OK Google" at the top every time I look at the watch. I'm not sure if its the reset/pairing or update.
Anyone have this?
Sent from my XT1095 using XDA Free mobile app
trrubicon06 said:
I updated to this and paired my 360 with my new Moto X. I've been getting the "OK Google" at the top every time I look at the watch. I'm not sure if its the reset/pairing or update.
Anyone have this?
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
Say "Ok Google" and do a few voice commands and it will go away.
My standard stock watch faces no longer display the date.
Is anyone else having this problem?
After i updated the android wear app, my whatsapp notification no longer vibrates the watch. The card's are there though.
Even calls won't vibrate my watch.
Dusty Rhodes said:
My standard stock watch faces no longer display the date.
Is anyone else having this problem?
Click to expand...
Click to collapse
Have you installed Moto Connect app?
xdatastic said:
Have you installed Moto Connect app?
Click to expand...
Click to collapse
Of course. I had the date showing on my watch faces before the update but it disappeared on the watch itself. I restarted and customized the faces and selected to show the date but it still doesn't show.
Dusty Rhodes said:
Of course. I had the date showing on my watch faces before the update but it disappeared on the watch itself. I restarted and customized the faces and selected to show the date but it still doesn't show.
Click to expand...
Click to collapse
I'm not having any issues with dates not showing up. They show up just fine and correct.
the latest update fixed the "show me my steps / heartrate" command. Previously it was displaying a google search result instead of opening the steps/heart rate app.
The new update broke a ton of functionality for me. I can no longer turn off the watch face while charging through turning ambient mode on and off. Voice commands also stopped working.
Anyone else have these issues?
Squintz said:
The new update broke a ton of functionality for me. I can no longer turn off the watch face while charging through turning ambient mode on and off. Voice commands also stopped working.
Anyone else have these issues?
Click to expand...
Click to collapse
Both of those features are still working fine for me. You might need to reset the watch and resync your faces/apps.
I am now getting Hangouts notifications for Chat messages as well as SMS messages.
Previously I was only getting them for SMS messages.
The latest version is here
http://www.apkmirror.com/apk/google-inc/android-wear/android-wear-1-0-5-1630507-apk/
Sent from my SM-N910C using Tapatalk 2
Steve-x said:
Both of those features are still working fine for me. You might need to reset the watch and resync your faces/apps.
Click to expand...
Click to collapse
How do you turn the watchface off while charging? Anyone else that's updated cannot, short of rooting and editing the build.prop
Sent from my Glamor Red M8
Fixed call answer
The new update also fixed an issue which some people had, about not being able to answer phone calls (only the red circle emerged to reject calls). Now both answer and reject are working again
I factory reset my Moto360 after clean wiping my phone (CM12.1 Nexus 6)... Now it won't stay connected via Bluetooth to my watch. Any idea how to fix this?
Anyone?
You need to reset the watch and re-pair it to the phone.
Sent from my SAMSUNG-SM-N910A using Tapatalk
frellingfrakker said:
You need to reset the watch and re-pair it to the phone.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Did that 3-4 times. Today though it seems more stable.
Looks like Android Wear keeps crashing. That's the cause of all this, even after several resets.
Maybe CM 12.1 causes the problems?
Verstuurd vanaf mijn Nexus 9 met Tapatalk
giancarlo_f said:
Maybe CM 12.1 causes the problems?
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
Others on 12.1 have not had these issues.
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
karcher01 said:
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
Click to expand...
Click to collapse
I haven't gotten Wear 5.1.1 yet unfortunately. Hopefully soon. 5.0.2 is BUGGY! Especially with battery drain during app sync.
i'm having the same issue here running android wear 5 . and cm12.
6 reset so far today . it keep disconnecting and then after on the phone it says connecting... which does not goes away until you reset the watch .
It seems to be a software issue . Android wear is still buggy
karcher01 said:
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
Click to expand...
Click to collapse
I give up. I tested this morning with a new phone (ASus Padfone Inifinity). Same problem. I send my watch back for a refund and wait for anoter one. Back to my G Watch.
Edit : My G watch is just receving the 5.1.1 update. Good news of the day after this 4 days in Hell with Moto 360
karcher01 said:
I give up. I tested this morning with a new phone (ASus Padfone Inifinity). Same problem. I send my watch back for a refund and wait for anoter one. Back to my G Watch.
Edit : My G watch is just receving the 5.1.1 update. Good news of the day after this 4 days in Hell with Moto 360
Click to expand...
Click to collapse
The Moto360 should get 5.1.1 soon... Returning it was a bit excessive IMHO.
Moto 360 5.0.2
agentfazexx said:
The Moto360 should get 5.1.1 soon... Returning it was a bit excessive IMHO.
Click to expand...
Click to collapse
I am receiving the same disconnect issues with my Moto 360 running 5.0.2. It happens every ~5 minutes.
dvrose said:
I am receiving the same disconnect issues with my Moto 360 running 5.0.2. It happens every ~5 minutes.
Click to expand...
Click to collapse
It should eventually stop. It did it for me after posting this for hours after resetting.
agentfazexx said:
I factory reset my Moto360 after clean wiping my phone (CM12.1 Nexus 6)... Now it won't stay connected via Bluetooth to my watch. Any idea how to fix this?
Click to expand...
Click to collapse
It's a CM issue. When I had my S4, I had the same problem that you're describing on both CM12 and CM12.1, both official and unofficial builds. Installing a google play edition or stock-based rom solved the problem. I just got a Droid Turbo, and it also has no problems with the watch. After doing some reading, it seems like there is a problem with the way that CM12 and CM12.1 handles low energy bluetooth devices. Try another rom.
TheSt33v said:
It's a CM issue. When I had my S4, I had the same problem that you're describing on both CM12 and CM12.1, both official and unofficial builds. Installing a google play edition or stock-based rom solved the problem. I just got a Droid Turbo, and it also has no problems with the watch. After doing some reading, it seems like there is a problem with the way the CM12 and CM12.1 handle low energy bluetooth devices. Try another rom.
Click to expand...
Click to collapse
I got flamed in the thread for blaming the ROM.
agentfazexx said:
I got flamed in the thread for blaming the ROM.
Click to expand...
Click to collapse
Well whoever flamed you is stupid. It's a well known problem, at least with the S4. Go to any CM12 or 12.1 thread on the Verizon GS4 forum and search for Bluetooth. I guarantee at least 10 posts asking whether or not it is fixed in the latest build.
TheSt33v said:
Well whoever flamed you is stupid. It's a well known problem, at least with the S4. Go to any CM12 or 12.1 thread on the Verizon GS4 forum and search for Bluetooth. I guarantee at least 10 posts asking whether or not it is fixed in the latest build.
Click to expand...
Click to collapse
Whenever I blame anything on CM that worked fine on stock, they all flame me.
Those that had this issue.. Were you on CM or not?
Yep...... It's a CM-bug on my S4 too. I installed echo-rom (tw based based rom) and it worked perfect .
Verstuurd vanaf mijn Nexus 9 met Tapatalk
giancarlo_f said:
Yep...... It's a CM-bug on my S4 too. I installed echo-rom (tw based based rom) and it worked perfect .
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
This happens to me on my stock Nexus 5, so I doubt it's a ROM issue. Most likely it's an issue with the firmware on the 360, or maybe the hardware. Hopefully 5.1.1 comes before my 30 days is up so I can decide whether or not to keep the 360, kind of sick of resetting the watch.
Shot in the dark I guess but since I got this device, Snapchat has been terribly laggy and almost unusable. Specifically when using the keyboard for text. Sometimes when I launch it, the camera is just black for roughly 5 seconds and then the back camera comes on finally. The chat feature is very slow at times and the entire app seems to stall and crash at least once a day. Anyone else notice this?
A quick google search yielded several recent topics on various forums complaining about the same thing, all on 6.0 Marshmallow. Hopefully it's not just this device.
I'm getting this exact thing
I went through that too. Once I had to restart it to make the camera work again. My tip is do not try use volume keys until it load completely. It just frozen the app in a black screen. Isn't perfect but can be used.
It's probably not optimized as well for 6.0 yet
Snapchat hasn't been perfect for me, but I've never experienced any of those issues. The worst I get is a little delay when pressing the home button.
Sent from my Nexus 5X using Tapatalk
I have had this problem we will have to wait for an update!! Basically that's what I've been telling myself lately about marshmallow
Sent from my Nexus 5X using Tapatalk
I can tell you guys I had this problem on my Nexus 6 on Marshmallow, it has to be something related to 6.0, I'm on a LG G4 now and snapchat runs just fine.
Kinda laggy for me too. And I can't get it to play a notification sound when I recieve snaps. I have turned it on in settings and I get a notification as normal, but no sound. Does anyone else have this problem?
Just uninstalled it from the n5x will have to limit myself to using it on n72013 it was unusable. Crashes camera failed to load then started to affect the stock camera app, would cause system crashes and could only be sorted with a reboot.
Same here its completely horrible to use of this phone. Phone ****s itself every time I try use it!
Sent from my Nexus 5X using Tapatalk
The app has been perfectly fine for me, up until the update I got yesterday. Now I see exactly what everyone is talking about....it's completely unusable now.
Our of curiosity...are you guys all encrypted?
Sent from my Nexus 5X using Tapatalk
thesoldier said:
The app has been perfectly fine for me, up until the update I got yesterday. Now I see exactly what everyone is talking about....it's completely unusable now.
Our of curiosity...are you guys all encrypted?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Decrypted & rooted running Chroma with Elemental-X.
ViRb3 said:
Decrypted & rooted running Chroma with Elemental-X.
Click to expand...
Click to collapse
Ok never mind then. I've been decrypted since I got the phone, until I took an OTA recently. It's been crap since then, but I guess it's unrelated
Sent from my Nexus 5X using Tapatalk
stock & encrypted and snapchat runs like poo for me. shame because its one of my most used apps :/
Well again Snapchat just updated, and now I'm back to it working fine again....
Sent from my Nexus 5X using Tapatalk
The past few updates have been good for me luckily.. Just don't try to send a snap while in landscape, I tried to add text and Swiftkey went all wonky and overlayed the screen even after I pressed Home, had to force close Snapchat and Swiftkey both :/
me too I have same issues the lag and so slowly for texting and even after update marshmallow update 6.0.1 the problem still the same I hope can anyone help me with issue what should to do and thanks you
So I am a power snapchat user and had this same problem and might have accidentally stumbled on a possible solution after having a login failure. I enabled the travel mode so it's not downloading constantly. I installed snapprefs and I can't explain why but it's flying now. No lag on window switching or opening the camera. I'm on 6.0.1 December rooted
Everytime I take video from Snapchat, it produces the sound "dug" at the first second of the video, never put my finger too hard on the phone so it isn't bcs of my finger knocking the screen, anybody know why?
Sent from my 2014811 using Tapatalk
Does anyone on here have a Ring doorbell? I just installed one today and it sucks on my XL. It freezes, I can't talk to who's out there and can't hear them. Also it takes a few seconds when I touch the screen for it to recognize it. Like I hit my home button and 5 seconds later it finally closes the app. The weird thing is it works great on my Nexus 7. Anyway just wondering if anyone else has the same problem or any ideas on how to fix it.
Sent from my Pixel XL using XDA-Developers mobile app
So obviously this was supposed to say Ring Doorbell Problem. How do I fix that. Nothing is going right for me today I guess.
I have the Ring and had similar problems in the beginning. However, it settled down over time. Give it a few days, and maybe uninstall and reinstall the app. Good luck.
Thanks. Hopefully it will settle down. I tried uninstalling and installing but still doesn't work. I don't understand this phone. It seems to have too many problems.
Sent from my Pixel XL using XDA-Developers mobile app
After upgrading my Galaxy S7 to the Android N beta I'm having issues with the Ring videos. Video playback (live or streaming or downloaded and played back) of Ring videos is basically broken. Playback freezes up, only the latter part of the video seems to play for a bit.
Everything is working fine now, maybe a reboot was all that was needed?
I have ring doorbell on my Pixel XL . I had problems hooking it up to my phone . Finally got to hook after an hour. No problems since
Sent from my Pixel XL using Tapatalk
It seems like N has some real problems. I can't get my phone to stay connected to my GMC vehicle and apps can cause it to lock up and not work. I had most of the same problems when my 6P updated. Hope it gets fixed soon.
Sent from my Pixel XL using XDA-Developers mobile app
I've figured out the issue. I have a Huawei watch. When my watch is connected that's when the problems happen. No idea how to fix it other than trying to turn off Bluetooth before opening the notification from ring app.
Sent from my Pixel XL using XDA-Developers mobile app