Hi All,
I'm from India.Bought Moto 360 from Australia and when i started using it,it starts hanging and restarting i thought resetting and upgrading will solve the issue but no luck.Can you please suggest what can be the issue.Battery drain is also there with 10% per hour in Wear Battery App. I tried resetting
Phone Model : GiONEE Elife E7
GTARaja said:
Hi All,
I'm from India.Bought Moto 360 from Australia and when i started using it,it starts hanging and restarting i thought resetting and upgrading will solve the issue but no luck.Can you please suggest what can be the issue.Battery drain is also there with 10% per hour in Wear Battery App. I tried resetting
Phone Model : GiONEE Elife E7
Click to expand...
Click to collapse
Not sure what would be causing that. Does your Moto 360 have exactly the same versions as mine?
http://imgur.com/ALB1SHa.jpg
xdatastic said:
Not sure what would be causing that. Does your Moto 360 have exactly the same versions as mine?
http://imgur.com/ALB1SHa.jpg
Click to expand...
Click to collapse
Hi, Yes, all are same except for google play services its 8.1.15(2250156-54).
Related
Hey guys!
I am fairly satisfied with my Moto 360 and I enjoy using it. But after 5-6 days (around a week maybe) it shows that it's not connected to my One M8. When I try to scan for it with bluetooth, the phone can't discover it. I also tried using brother's OnePlus One, but the result is the same.
The only thing that fixes this is factory reset the watch. Then I have to do everything all over again and it's getting really annoying. Did someone have similar experience and is there some solution to this?
Thanks in advance!
inspire4gfreak said:
Hey guys!
I am fairly satisfied with my Moto 360 and I enjoy using it. But after 5-6 days (around a week maybe) it shows that it's not connected to my One M8. When I try to scan for it with bluetooth, the phone can't discover it. I also tried using brother's OnePlus One, but the result is the same.
The only thing that fixes this is factory reset the watch. Then I have to do everything all over again and it's getting really annoying. Did someone have similar experience and is there some solution to this?
Thanks in advance!
Click to expand...
Click to collapse
Got a similar problem where after several hours the watch doesnt reconnect to the phone because my moto x thinks that its still connected.
the only solution i found so far is to disconnect through the wear app on my phone, disable bluetooth and re-enable bluetooth.
you could give it a try.
eric
edit: newest android wear update seems to solve this issue
I surely hope so! I tried your method before already, but the only trick for getting it to work is factory reseting the watch. We'll see if the update squashed this bug
well that sucks mate. good luck!
I too am having this issue... my watch shows Disconnected and nothing I do fixes this except for resetting my wtach and reconnecting from scratch.
I also just updated to Lollipop on my nexus 5 through a clean factory install, and had the same issue.
I'm having the same problem once a week.
What solves my problem ist:
Turn off BT on phone
Reboot watch
Reboot Phone
Turn BT on phone back on
Connect through Wear App
mc-paulo said:
I'm having the same problem once a week.
What solves my problem ist:
Turn off BT on phone
Reboot watch
Reboot Phone
Turn BT on phone back on
Connect through Wear App
Click to expand...
Click to collapse
This also helps, but only sometimes I hope Google will fix this in the near future. It is a single thing that drives me crazy about this watch.
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.
Hi all!
So I've just swapped my Sony smartwatch 3 for a moto 360 and have just set it up as new and downloaded a few new watch Faces (still have the old ones on my watch too from when I had them on the SW3) but for some reason even after a system reset none of them are appearing on the watch. All my notifications are appearing however.
Anyone know what is causing this? I haven't updated to the latest wear version on the watch due to the battery issues which forced me to sell my SW3 with 5.1.1 could this be the issue?
Thanks
Sent from my OnePlusOne
Okay so fixed the above issue with a software update to 5.0.2. Wondering if it's better to stay on this version or go to 5.1.1...What's the best for this watch?
Sent from my OnePlusOne
i feel 5.1.1 is better
sheppy101 said:
Okay so fixed the above issue with a software update to 5.0.2. Wondering if it's better to stay on this version or go to 5.1.1...What's the best for this watch?
Sent from my OnePlusOne
Click to expand...
Click to collapse
I get better battery backup in 5.1.1 (with tilt to wake ON, ambient display off), so I would suggest you to update and give a reset after it. (few people have battery issues with 5.1.1)
Cheers! Updated last night and doesn't seem to be toooo bad atm! No worse than 5.0.2 anyway. Still probably need time to settle though aswell I guess.
Was worried as the 5.1.1 update on the Sony watch made the battery so unpredictable!
Sent from my OnePlusOne
Hello experts,
Since some weeks when I receive a phone call my SW3 keeps vibrating for 8 or 9 seconds even after I answerd (the phone is a Sony Z3c).
That's really very annoying...
I tried to full reset and resynch, and even reinstalled all apps, but the problem remains.
Suggesions?
Thanks
freewing70 said:
Hello experts,
Since some weeks when I receive a phone call my SW3 keeps vibrating for 8 or 9 seconds even after I answerd (the phone is a Sony Z3c).
That's really very annoying...
I tried to full reset and resynch, and even reinstalled all apps, but the problem remains.
Suggesions?
Thanks
Click to expand...
Click to collapse
I'd suggest you to send it to Sony Service. This is not a normal behavior for our watch. I'm also using Xperia Z3C (stock 5.1.1) and this watch (now stock 6.0.1, AW 1.4) and no such thing happened ever.
romcio47 said:
I'd suggest you to send it to Sony Service. This is not a normal behavior for our watch. I'm also using Xperia Z3C (stock 5.1.1) and this watch (now stock 6.0.1, AW 1.4) and no such thing happened ever.
Click to expand...
Click to collapse
Thanks for answering.
The problem is that my SW3 is a gift I received: it was bought in UK and I live in Italy.
Very difficulto to get an economical sustainable assistence.
I can't understand the logic, but... since I changed in the phone in settings/notifications/apps with access to notifications/ DISABLE Android Wear
then now everything looks to worl fine.
(I know it looks wired, but... now it seems to work)
does this make sense?
...any more suggestion from experts and/or Sony Tech Sup?
freewing70 said:
...any more suggestion from experts and/or Sony Tech Sup?
Click to expand...
Click to collapse
@freewing70
Repair/ upgrade the firmware version in the Smartwatch using PC companion and try pairing with your phone again. Other option would be to goto recovery and do a factory reset in the watch. You can search to find the steps to get to recovery in the watch.
gauthamsv said:
@freewing70
Repair/ upgrade the firmware version in the Smartwatch using PC companion and try pairing with your phone again. Other option would be to goto recovery and do a factory reset in the watch. You can search to find the steps to get to recovery in the watch.
Click to expand...
Click to collapse
Alredy done: nothig changed.
I do believ my SW3 has some probs.
Thanks for answering
Anyone has noticed this? Almost every time I look under my watch the heart rate monitor is glowing green. Is this normal?
turulojko said:
Anyone has noticed this? Almost every time I look under my watch the heart rate monitor is glowing green. Is this normal?
Click to expand...
Click to collapse
what watch face are you using? I noticed this yesterday actually using a community face from Watchmaker Premium. I am thinking it has to do with the face you are using.
Sent from my SM-N920F using Tapatalk
jcip17 said:
what watch face are you using? I noticed this yesterday actually using a community face from Watchmaker Premium. I am thinking it has to do with the face you are using.
Sent from my SM-N920F using Tapatalk
Click to expand...
Click to collapse
Yes maybe is that. I'm also using Watchmaker premium and some watch face founded on G+.
I just changed it to the default Dandy watch face.
I'll report back if this helps.
It's not Watchmaker.
Changed to default Dandy
Uninstalled Watchmaker
Factory reset
Uninstalled Google Fit
Removed all apps permissions for body sensors
And after all that my watch is still glowing green from the heart rate sensor.
Any ideas?
turulojko said:
It's not Watchmaker.
Changed to default Dandy
Uninstalled Watchmaker
Factory reset
Uninstalled Google Fit
Removed all apps permissions for body sensors
And after all that my watch is still glowing green from the heart rate sensor.
Any ideas?
Click to expand...
Click to collapse
I just got a new replacement watch and it also has the green lights always on. Last watch didn´t do that.
ceramista said:
I just got a new replacement watch and it also has the green lights always on. Last watch didn´t do that.
Click to expand...
Click to collapse
I think it was Google Play Services bug.
After the update to 9.4.52 there is no more green lights
Hi.
I have Google Play services 9.6.83 and have the green light almost always on problem. Anyone found an solution?
I have also noticed this bug recently, since the last update. It's becoming a major issue as it drains the battery real quick
Guys, I also have same problem.
May you please, affected with this strange HRM behavior, put Android, wear and play services versions, to analyse whether relates to particular cases?
Mine are, Android 6.0.1, Wear 1.503153324, PS 9.6.83
Also, I found on internet saying automatic HRM is a feature of Marshmallow. Any thoughts? (sorry, being noob here restricted to post links)
I've sent an email to huawei support. Let's see if they can help.
The battery life is terrible now.
Yep, I also have the same problem, and it has also been reported at the Google+ Android Wear community. Other watches seem to have this problem as well. I think there's a bug in the latest Wear update, as the problem started right after the last update.
I noticed this as well. I never had any problems in the past, but since a view days/week(?) I sometimes notice that the green heart rate monitor lights are on without reason. There was a Android Wear update recently, I currently have version 1.5.0.3250495 installed. I wonder if this is the reason. I'm also using Watchmaker with the same watchface sind months, but the last update of Watchmaker was in May, so it's unlikely that Watchmaker causes this.
@Theratron
Can you please link the Google+ Thread? I could not find it in the Android Wear Community.
I don't even have Watchmaker, so it's definitely not the app causing the problem
I wanted to post the link, but there's some nonsense about new members not being allowed to post outside links. I'll Try to PM you....
Troubleshooting for Heart rate monitor
We suggest that you try a factory reset on the watch by holding down the button for 60 seconds. If this does not resolve your problem please call Huawei support at 1-888-548-2934. (SP)
HonorUSA_Quinn said:
We suggest that you try a factory reset on the watch by holding down the button for 60 seconds. If this does not resolve your problem please call Huawei support at 1-888-548-2934. (SP)
Click to expand...
Click to collapse
Thanks for posting Huawei's reply! That reply is a little worrisome to me though... it means they are completely unaware of the fact that every (updated) Huawei Watch out there is having their battery drained by a software bug....
Hmmm, it does seem like others are reporting the problem too.
Because of this random behavior of the HRM, I am losing on average 15% battery over night.
Check the Google Fit app. I just did and noticed, that it has measured my pulse several times in the last days without my knowledge. I usually do not use the app, so this is strange.
foo said:
Check the Google Fit app. I just did and noticed, that it has measured my pulse several times in the last days without my knowledge. I usually do not use the app, so this is strange.
Click to expand...
Click to collapse
I also noticed that.
I uninstalled the app from the phone and it reverted to the old fit version on the watch. It doesn't log the HR anymore on Fit but the problem of the green light and the battery drain continue.
Hi, I've also had this problem. I've manage to resolve by unpairing my watch, restart both my watch and phone and start all over. Now, after a week, problem solved.
rgomesf said:
I also noticed that.
I uninstalled the app from the phone and it reverted to the old fit version on the watch. It doesn't log the HR anymore on Fit but the problem of the green light and the battery drain continue.
Click to expand...
Click to collapse
Unfortunately you're right. I also uninstalled fit on the phone and disabled fit on the watch, but the HRM still activates sometimes.