Database Develop

Hear Rate and Pedometer Stop working

Hey all,
I was wondering if any of you have seen the heart rate and pedometer stop working all together. I have not rooted, rom'ed or done anything to this watch yet.
I have also tried reseting the device, powering it down and attempting the reading with both the google fit app and samsung heart rate app. Neither work and neither will turn on the green light that indicates the heart rate monitor is working.
Any ideas? I also have been having problems, like others, with random disconnecting and ok google commands failing to work.
Thanks.

Same problem with pedometer. Not rooted or ROM.
Help?
Rachael

Went out for a jog after 30mins said I did 149Steps
Guess I need to pick up the pace?
I restarted the Fit app, and it looks like it started counted again.

AstroDigital said:
Went out for a jog after 30mins said I did 149Steps
Guess I need to pick up the pace?
I restarted the Fit app, and it looks like it started counted again.
Click to expand...
Click to collapse
How did you restart the fit app?

ritkit said:
How did you restart the fit app?
Click to expand...
Click to collapse
You can say "start fit", or navigate to the start menu select the fit icon manually

Yes, yesterday I realised that despite running around after people at work all day I had actually managed 0 steps. Today has had a similar work load and once again I seem to have been floating serenely around the department.

I get two sets of data for step count the Note 3 says 10k
Run "Fit" it tells me 7000 steps?
The step count on the Gear Live just started acting up.

For those having issues with the step counter did you guys use facer or something similar and add the step count? I noticed mine acted up after I added it to face. Nothing short of reseting the watch would fix it either

hungmung said:
For those having issues with the step counter did you guys use facer or something similar and add the step count? I noticed mine acted up after I added it to face. Nothing short of reseting the watch would fix it either
Click to expand...
Click to collapse
I'm using facer, but not to display the step count, only the time & date.

Having the same issue, where steps count stays at 0, and heart rate monitor doesnt even light up. I tried resetting the device, then tried to use HRM before any apps are installed, but still no luck.
I think it started after installing a watchface (devops time). But the problem is still there after factory reset, so I dont think its the app's problem.
Still looking for solution..

Answer for those who are looking at this issue..
Just turn off your watch and wait a few seconds, then turn it back on. (restart doesn't work)
http://forum.xda-developers.com/gear-live/help/heart-rate-sensor-stopped-t2818335
All the sensors are alive now. Pedometer, accelerometer, HRM, compass.
I feel both stupid and relieved now.

heh I had this issue today was about to return the watch.. reset it, restarted it nothing worked then saw this and realized I never fully powered it off. Thanks!

GPe HTC One M8
With a GPe HTC One M8 (KitKat, stock) and a Samsung Gear Live, I found that my step counter stopped working when I installed Google Fit. Lots of tricks (including uninstalling 3rd party watch faces and powering off) didn't work. Uninstalling the Google Fit app fixed my problem.
Was very annoyed to find this on the Google Fit Help - Fit isn't tracking activities correctly: If you have an HTC One M8, your phone may be incompatible with Fit.
Can't tell from the help page if this is referring to the step counting built in to the M8 or something more fundamental to the Google Fit app.

For those experiencing lost steps with Google fit, there is an issue if you ate taking steps with the watch while the phone isn't moving. In any instance where the watch and phone step counts disagree the phone takes precedence.

Cysec said:
For those experiencing lost steps with Google fit, there is an issue if you ate taking steps with the watch while the phone isn't moving. In any instance where the watch and phone step counts disagree the phone takes precedence.
Click to expand...
Click to collapse
Do you know if they are going to fix this? This has not always been the case. It used to sync with my watch and grab those steps. Why the other way around?

Fixed my connectivity and battery life

Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.

Bugger
I don't have that option in my bluetooth settings

I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil

Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk

Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.

I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.

I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.

Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far

My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?

For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?

That's what I have also since I own the watch.

Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..

mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification

I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?

Unreliable notifications...

I bought the Watch R a week or so ago and I've been trying to work out why the Google Now notifications are so unreliable.
At first, I thought it was just me - I never really embraced Google Now and actually had it turned off on my phone (Galaxy S6 Edge). A few days ago I turned it on, configured it and was expecting to see the odd card popup on my watch every now and then but I've had zip.
So, I thought I'd test the notifications on the watch, from the Android Wear app, but the only notification that works all the time is the phone call. Most of the other notifications just don't pop up on screen and the only way I see them is to swipe the face from above and then they're there. Is this normal behaviour? I thought that notifications were supposed to popup on the screen, like on my phone!
I've reset the phone a couple of times in desparation but it's made no difference. I've unpaired the watch from the phone and re-paired it after forgetting the device. No difference. Removed all the custom watch faces and used only the once that came with the watch and once again, no difference.
I do get notified of text messages and emails with no problem, but nothing from Google Now.
Can anyone please suggest anything?

I have the s6 and I don't receive any notifications except the test phone call. I believe it to be a samsung problem with it killing the wear app from running in the background. watch worked fine with my other phones.

It's ridiculous, my s6 / gwr doing the same thing. Reboot both and things work for a little while, then gradually peters away to nothing. Except for sometimes I'll tap the watch for the time, and some random google now cards will be there, which I dismissed days before! Swipe them away but the same few keep coming back! As for the weather reports, well they've not worked for over a month now. And all this without me touching any settings whatsoever. I've exempted the android wear app from battery optimisation in the s6 too, incase they were that dense they'd overlooked that core app, but doesn't seem to have sorted it. Seems every time these companies update stuff they break it, and don't care about fixing it.!

Android Auto Not Talking - Need Help

My AA isn't fully working.....again. My Verizon Galaxy S7 has been working fine ever since the last factory reset I did back on 8/8. At that time I turned off auto-update to apps in case some Google app was going to update and cause the issue again and I'm actually up to date on all my apps.
A few days ago everything was working fine. With no new apps added and no new updates and all of a sudden that night, my text messages stopped being read back to me. But the weird thing is the last couple of times this happened, AA wouldn't talk at all. So if I said "Call Steve mobile" the call would go through but AA never confirmed by saying "OK, calling Steve mobile" - or - if I asked for the weather it would just beep and be silent. This time around though, all that works. AA asks if I want to call mobile or home, and I can ask for the weather and get it. The only thing that AA is not doing at this point is reading text messages to me.
I've seen suggestions about making sure my media volume is up - and it is. SUGGESTIONS?????

Widgets not updating

My widgets are very slow to update. It may take him a half hour or longer to update. I have checked battery optimization is not on for those apps, although one of those two apps that I have the problem with background data is grayed out. So I can't turn on allow background data. Not sure why that would be great out.
Any thoughts?

Wunderlist Task List.
DTG/GTD
But, I did some things poking around, don't remember for sure what all, but I had read that changing the Animation Scale etc to .5 would help. I did change that.
Before posting, I had found that Wunderlist was on battery optimization. Changing it didn't appear to help, so I posted. But now, it seems to be working. Maybe it's fixed. I'll post back in a day or two and indicate if it is still working or has stopped again.

Well, no, I'm not saying that. I'm just saying that's the only change I made, and at that point it had started working.
Are you having same problem, albeit different widgets?
FYI... mine is now not working again. I'm not surprised. But am frustrated.

Update...
I am finding that it does eventually update. It feels like the phone has been taken over by something. But, then, other things don't seem slow.
I just installed Gsam battery monitor, and ran the ADB cmds to try to identify apps using battery. Maybe I'll find something using a lot of battery and hence cycles.
My battery does seem to be going down quite a bit faster than it should.

It cleared up for a while after a factory reset,But it's back, and, I find that notifications from Lightflow come in 30 minutes after recieved.
It's like the phone is operating in molasses.
I'm beginning to think this phone is crap. If I switch back to my old Mate 9 it works fine.

jd14771 said:
certain apps aren't syncing well with pie. i had this same issue with Beautiful widgets, could not get the weather or time to update unless i manually updated it.
Under <Problem APP's> App Info > Battery
1.A Make sure the app is allowed background activity
1.B Make sure the app is not set to "optimized"
. (note: by default, the optimized list will only show apps that HAVEN'T been optimized, . you have to select "ALL" at the top to see all apps.)
Under <Problem APP's> App Info > Mobile Data
2.A Make sure "allow background data usage" is enabled.
2.B Make sure "allow app while data saver is on" if you have data saver enabled.
. (enable this if you want to be sure an app will receive background data.)
Click to expand...
Click to collapse
Thanks for the suggestions. I don't seem to be having any luck with that. Had already done those.
But!! ...
I just found a post after doing a global search for another issue I am having that seems to coincide with the widget issues, which is, Play Store freezing during updates. The post was in a Xaiomi forum. He said that he found if he had blue tooth on, his play store would constantly freeze. He turned off BT, and rebooted, and it worked.
I just did the same thing...and it is working...both the play store, and widget updates.
Interesting to have the great feeling of success, along with the frustration of a new (newly realized) issue yet remaining (BT).

Looking for a little further and through the settings on Bluetooth, I turned off Bluetooth scan. Now at first I would still have problems with Bluetooth on even though Bluetooth to scan was off. That of course would be very quickly after turning it on or off at cetera.
so this morning I get up having left Bluetooth on all night, with scan off, and everything's working fine. I did find last night that when I would first turn Bluetooth on even with skin off, the problems would be there. But of course when you first turn Bluetooth on it's going to scan anyway.
so I will update this thread little later after I see a little more about weather. Just having scan off actually cures the problem, in case someone else runs into this and it helps them.