Hello all , my moto 360 second gen was working properly until i changed my phone ..i got s7 edge and reseted my moto 360 and paired it up .Everything is working fine except this i am not able to make calls through the watch .
When i speak to call someone the screen shows the contact and then goes back to watch face display without making the call . I have tired to reset it again hasn't helped still have the same error ..
Please suggest what i can try this seems to be a bug .
Thanks
Related
Hello everyone.
I broke a display on my Xperia S some time ago. Yesterday, I got a new display with frame. So I changed it, and it's fine now, but my MIC is not working anymore. I connected everything accordingly, at least I think so. When I try to record sound, I can't hear voice, just rustling. I tried several times to disconnect and connect everything, but the problem persists. Everything else is working fine, as far as I tried it. ROM is stock Jelly Bean.
Any solutions?
Hi guys,
i have a big issue after the last update of my MOTO 360, i can't receive any more notifications from GMAIL, whatsapp, wechat, facebook, hangout and any kind of chat/message app. The Watch seems to communicate will the phone, i dont have any problem with the cardio app, even with facer i still can change my watch faces without any problem or when i got a phone call it still works fine. I already re-connect switching on and off bluetooth, restart and reset my Watch but nothing, still no notifications, i bought moto 360 on the day one and never got any problem till yesterday.
I'm using LG G3 ( no root )
any comments or suggestions will be appreciated
Thanks
Hi, since the last update to 6.0.1 and android wear 1.4.0.2580363, calls and notifications are randomly not silenced in my Moto X Style / Pure . Sometimes it works , sometimes it doesn't. I already tried restoring to factory defaults the watch and installing android wear again. Any idea? Thanks !!
Alber12 said:
Hi, since the last update to 6.0.1 and android wear 1.4.0.2580363, calls and notifications are randomly not silenced in my Moto X Style / Pure . Sometimes it works , sometimes it doesn't. I already tried restoring to factory defaults the watch and installing android wear again. Any idea? Thanks !!
Click to expand...
Click to collapse
I'm still suffering this issue even after sending the watch to Motorola. It seems like a last version bug. Any workaround? Thanks in advance.
Alber12 said:
Hi, since the last update to 6.0.1 and android wear 1.4.0.2580363, calls and notifications are randomly not silenced in my Moto X Style / Pure . Sometimes it works , sometimes it doesn't. I already tried restoring to factory defaults the watch and installing android wear again. Any idea? Thanks !!
Click to expand...
Click to collapse
I have that problem quite often. Usually I try toggling that setting on and off. If that doesn't work I'll reboot my phone and maybe watch. Usually one of those things takes care of it. Very annoying though!
I dont know if anyone could help... my moto 360 got updated to 6.0.1 and the watch when pairing with the phone starts freezing like hell and android wear inst responding error occurs randomly and process isnt working close it now error occurs . i cant even use the watch because it is sooo sluggish and would do nothing and it becomes hot causing the battery to die withinin 1.5 hours. help!!!!
Would it be a good optuon to root it or anything please suggest i love thewatch but its killing me cant even use it urrrggghhh!!!!
Hi every one < I need some help from your side please
I have Moto G5 Plus it was lost imie on the official rom , so I flashed pixel experience android 10 rom and its working fine
but the problem that I faced now is : the phone screen turn off during the calls and never wake-up till the other called turn off the call
I downloaded many apps like xposed and many others without any changes
I tried the proximity counter app , the sensor is working and counting properly
Note : sometimes the sensor is working properly without any app
Any solutions please ??
i am also riding the same boat , it started from stock oreo in my case, currently i am on aicp 15 (maybe coz the device is almost 3 yrs old now, its sensor started giving erroneous results)