Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Not yet. Collected more information. Serial numbers for all 3 of my watches and 3 iPhones on my account with the issues. Will be hearing back in a day or two. They have to run some "tests" with the information I have provided.

Everyone has been extremely friendly and they are working to address the issue ASAP.

So they are saying it is definitely a bug?

I ask because on this forum or the apple support forums there are posts as late as yesterday quoting apple chat line and engineers that this is not an issue but it was changed on purpose for efficiency reasons with 1.0.1.

And I am glad they are taking your information from your watches but if any of the engineers are wearing watches, they should be seeing the same behavior.
 
Not yet. Collected more information. Serial numbers for all 3 of my watches and 3 iPhones on my account with the issues. Will be hearing back in a day or two. They have to run some "tests" with the information I have provided.

Everyone has been extremely friendly and they are working to address the issue ASAP.

Thanks for the news.
 
So they are saying it is definitely a bug?

I ask because on this forum or the apple support forums there are posts as late as yesterday quoting apple chat line and engineers that this is not an issue but it was changed on purpose for efficiency reasons with 1.0.1.

And I am glad they are taking your information from your watches but if any of the engineers are wearing watches, they should be seeing the same behavior.

They have not confirmed either way if its a bug or not. All that has been confirmed thus far is "it's not normal behavior".
 
I just got off the phone with an incredibly nice AppleCare Senior Advisor who has been working with me since Tuesday on this issue. He told me that he spoke to the engineering team and they said this was an intended behavior in 1.0.1, however he also said that a fix would be coming in the next software update. He also mentioned that part of the confusion is that Apple has not updated its marketing material online.

I responded by telling him that I still don't feel as if this correct, and if it is, its very disappointing because one of the main reasons I purchased the watch is for fitness tracking, and at this point it is completely unreliable as a fitness tracker. I also asked if missing readings for 5hr or more intervals and then taking 10 in a minute was also part of this intended behavior and he said was not sure.

In the end, he said he was going to contact the engineering team again and try and get even more clarification on exactly what is happening, and then get back to me again. All in all, I feel like information wise I'm back at square one, he says its intended behavior, but assured me a fix was coming so I'm not even sure Apple knows what to call it yet.
 
I just got off the phone with an incredibly nice AppleCare Senior Advisor who has been working with me since Tuesday on this issue. He told me that he spoke to the engineering team and they said this was an intended behavior in 1.0.1, however he also said that a fix would be coming in the next software update. He also mentioned that part of the confusion is that Apple has not updated its marketing material online.

I responded by telling him that I still don't feel as if this correct, and if it is, its very disappointing because one of the main reasons I purchased the watch is for fitness tracking, and at this point it is completely unreliable as a fitness tracker. I also asked if missing readings for 5hr or more intervals and then taking 10 in a minute was also part of this intended behavior and he said was not sure.

In the end, he said he was going to contact the engineering team again and try and get even more clarification on exactly what is happening, and then get back to me again. All in all, I feel like information wise I'm back at square one, he says its intended behavior, but assured me a fix was coming so I'm not even sure Apple knows what to call it yet.

I will be returning my watch if this is not fixed shortly. I specifically bought it to passively track my activity and heart rate! Rediculous.
 
He told me that he spoke to the engineering team and they said this was an intended behavior in 1.0.1, however he also said that a fix would be coming in the next software update.

That now seems to be the official "Apple" stance on the issue as others got the same story from Apple.

I just hope the next release of the OS fixes it, because as it is it is pretty useless during the day. Just as an aside, I went for a run in hot/humid conditions this afternoon, thought it would be great to see how well/quickly my HR recovered after the run .. Oh but wait, can't do it because between the end of the run at 12PM and now ... 0 HR readings.

I wonder if Apple really even has anyone on staff that understands exercise physiology, doesn't seem like it with the way the heart rate monitor works now. First off, the 10 minute measurement frequency is at best at the outer end of being useful. For instance, the Basis Peak takes continuous readings and records one-minute intervals. Additionally, in workout mode, 5 second recording frequency is also nowhere near as valuable as a reading each second.

I know battery life is the reason for the compromises, but to be honest, I have never seen mine below 30%. Yes, i do put in the charger a couple of times a day (in the morning while getting ready and after a workout), I really don't find that much of a inconvenience.

Let the user manage battery life and give us configurable options for both passive and active HR measurement frequency. If you don't care about the HR Monitor .. turn it off. If you want to the AW to be a great training tool, you make the tradeoff to charge it more often to get more frequent and more useful data.

Problem solved.
 
I turned mines off, and my battery life magically got better the next day. Heck, the updates were not accurate in 1.0.1 anyway.
 
I will be returning my watch if this is not fixed shortly. I specifically bought it to passively track my activity and heart rate! Rediculous.

I'm sorry to say that I'm in this boat, too. 1.01 has completely broken the watch for me based on my primary use, which is as a fitness tracker. I was doing the elliptical this am and once again got bizarre readings, the range being from 62 to 151, all while actively on the machine using "workout." I got so frustrated I took it off and just used the heart rate readers on the machine.

I also contest the engineering response of changing the frequency to improve battery life. My battery life has gotten slightly worse, even though the watch is taking my HR reading with far less frequency. Additionally, if it was an intentional move to change it from every 10m to every 60m, that basically negates the entire purpose of having passive heart rate readings in the first place. A reading every hour is useless.

They either need to fix this in the next update or allow users to revert to 1.0.

Otherwise, I too will have to sell it elsewhere.
 
If Apple massively change the fitness functionality of the watch I would argue that you could return the watch for a refund at any time past the 14 day period.

Fitness tracking is the primary (certainly secondary) function of the watch.
 
If Apple massively change the fitness functionality of the watch I would argue that you could return the watch for a refund at any time past the 14 day period.

Fitness tracking is the primary (certainly secondary) function of the watch.

Hah! I would have no problem with returning it, but I strongly doubt they will allow this.

If they change the specifications now, however, I will try to do just that!
 
Same problem

Is there a way to reset my watch to the 1.0 version software? After the update, I've noticed that my heart rate doesn't track and that makes the exercise activity ring completely inaccurate. I hate it!
 
I asked Apple to extend my return window to 30 days to wait for a fix and they said this was fine. So it seems like they are willing to make exceptions to this rule. It's not like you're returning it because you changed your mind - they changed the features on us and we bought something that we didn't think we bought.
 
But by all means .. please let Apple know that you aren't happy with it after the 1.0.1 update...

https://www.apple.com/feedback/watch.html

Oh don't worry, I already have. Have been talking to Apple care about this issue as well. Didn't notice that the heart rate was that off until just recently and that must be why the exercise rings are inaccurate. I hope they fix it soon it's incredibly frustrating.
 
I just checked and it says my HR was anywhere from 62 to 168 today which is crazy as most the day I have had to sit in my office. Worst is it looks like my HR is only being checked ever 2 hours as twice I have looked and it was two hours ago last time it was checked.

This is useless if you bought the AW to track this and with all the trouble Apple went to to put the sensors on the back of the watch it should work better than this.

Hope they fix this soon as it was what I liked best about my Fitbit Surge, it constantly checked your pulse. Every two hours in not good.
 
I have not got my :apple: Watch yet, but my wife's is definitely affected.

I have submitted feedback to Apple and let them know I will be returning mine if the issue is not fixed (in reality I may still keep it, but I want them to see that the issue is not minor).
 
I've noticed the same thing as everyone else. Also, when I do it manually in glances it fails quite often and I have to click a reload symbol in the little heart to get it to try again. Usually works on the second attempt.
 
Apple Care has been calling me on a daily basis to let me know that they are working on this and asked me for screen caps. At least it looks like they have their attention on this.
 
I just downloaded a copy of this apple support page that mentions the reading every 10 min. https://support.apple.com/en-us/HT204666

Just in case they do change the methodology and I want to return the watch.

Since 1.0.1 my workouts have actually been fine. I am not getting any strange readings and they are pretty consistent with 1.0.0 workouts.

But I am having the issue of not recoding HR for 3-4 hours at a time.

And I agree with what some of the posters have said. Apple should give us a setting for resting and workout HR recording intervals. Let us decide how to use the battery life. I could care less about getting Facebook or twitter or digital touches on my watch. I bought for fitness reasons.
 
Tech I've been working with since Tuesday called back today left a message. She's been checking her Watch and notices the same issue. Still working with engineers and trying to rule out every trouble shoot (which we all know there are not any for this issue).
Her engineers have said nothing like "this is suppose to happen" which I don't doubt others who have reported this.
Clearly company not in sync with left and right hand. They've got to get on the same page!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.