I just can't resist pointing out the irony of this post given the users signature line of "Any fool can criticize, condemn and complain and most fools do." Benjamin Franklin
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases First Apple Watch Software Update With Bug Fixes and Performance Improvements
- Thread starter MacRumors
- Start date
- Sort by reaction score
I just can't resist pointing out the irony of this post given the users signature line of "Any fool can criticize, condemn and complain and most fools do." Benjamin Franklin
Just got back from a run with the new update installed. First thing I noticed was after selecting Outdoor Run from the list of exercises with in the workout app, a new message appears reminding you to take your phone with you for more accuracy and to run for at least 20 mins to calibrate the watch.
While running I noticed that the pace was more stable during the run. Before the pace seemed to fluctuate to often and never seemed accurate. It now seems to be more realistic and doesn't fluctuate as often.
On the distance side I still had issues although it seemed slightly better. Before the update my runs were on average .3 miles longer then the actual distance. After the update a known 3.20 mile run was measured at 3.05 miles, again I had my phone with me during this run. I still don't understand why we can't get solid distances from the GPS on the phone.
While running I noticed that the pace was more stable during the run. Before the pace seemed to fluctuate to often and never seemed accurate. It now seems to be more realistic and doesn't fluctuate as often.
On the distance side I still had issues although it seemed slightly better. Before the update my runs were on average .3 miles longer then the actual distance. After the update a known 3.20 mile run was measured at 3.05 miles, again I had my phone with me during this run. I still don't understand why we can't get solid distances from the GPS on the phone.
Last edited:
I just can't resist pointing out the irony of this post given the users signature line of "Any fool can criticize, condemn and complain and most fools do." Benjamin Franklin
No problem including myself
Bitching is a lot of fun and stress relief.
Watch OS 1.1
I updated. It updated very quickly and I've actually noticed improvements in Siri. Seems that now when I use Hey Siri, she actually hears me a lot better... And she doesn't freeze every 2 out of 3 times I use it. The Watch does seem snappier, there was a problem with it calculating my activity data but it fixed itself. Im very impressed! Seems faster, and Im still at 100% even though I've done a good bit. They fixed at least some minor bug that was causing some drain issues.
I updated. It updated very quickly and I've actually noticed improvements in Siri. Seems that now when I use Hey Siri, she actually hears me a lot better... And she doesn't freeze every 2 out of 3 times I use it. The Watch does seem snappier, there was a problem with it calculating my activity data but it fixed itself. Im very impressed! Seems faster, and Im still at 100% even though I've done a good bit. They fixed at least some minor bug that was causing some drain issues.
I agree, the battery does last a day. I found that updating did suck a lot of energy, but to be honest updating is not an emergency and can wait. So it is not a problem at all to have to have it connected to the charger. Updating the software is not something we will be doing all the time.
Yep. I've completed 17 runs with my Apple Watch and have used the phone in conjunction with the run every time.
I'm trying to get the update to download and it's taking forever. I have a question for you. Does the jellyfish in the Motion watch face turn on any quicker?
Thank you for posting your observations! I can't get out for a run until later this evening.
I also don't understand why Apple is not pulling consistent GPS information from the phone during runs. I have a hunch that Apple probably chose to only use the GPS for calibration purposes and perhaps the start/stop (versus using the GPS full time) so they could conserve battery. The problem though is that people do not run at the same pace all the time and often times, people incorporate a short walking break into their running as well...so the Watch will never be very accurate if they are trying to base a good majority of the calculations off arm swing alone. In a lab that might work, but not in the real world.
I wish they would have fixed the blue text on black background issue in emails, they are so hard to read.
Also safari seems much faster.
Also safari seems much faster.
My counter opinion is just the opposite assuming that the equipment is something better than Sears quality. Unlike the watch, the equipment knows the resistance and motion profile that is being worked against AND has the user's height and weight to consider as well (again, assuming it is commercial grade). Even with a user telemetry strap, the machine natively has more information to use in its estimates than a jack of all trades fitness monitor. Besides, anyone involved in a fitness competition would have to agree on the measurement device. Unless all users have watches, the only consistent device is the exercise equipment. IMHO, of course. I still like my watch for what it is an like the ease of relative performance that it captures.
I've noticed that the raise to activate work now when your are in bed.
Also heartbeat glance didn't go off until the heartbeat is calculated
Also heartbeat glance didn't go off until the heartbeat is calculated
Obviously depends how much you're using it, I'm getting to 48hrs before it hits power reserve.
The one thing I don't get though is when you use the music control app, it fires up the screen
on the phone, kinda defeats the purpose I would've thought?
Last edited:
Ummm Dev here, chiming in...
This assertion of yours is not accurate. The issue with the use (or not) of Shared Containers is a real one:
Essentially, what we are supposed to do is cache data for watch apps - images can be cached, or loaded into, the watch image cache. Data should be stored in the shared container and read at launch, then updated. Updates should be performed by the main app in the background and serialized out.
This "store and forward" pattern is crucial to perceived performance - most complains about "slow apps" isn't in the actual interactions/"lag" on screen, but with loading/xferring data for display.
Writing for the Watch, while using the same languages as iOS "proper" requires different coding and implementation patterns which are not obvious on the simulator to get maximum performance.
Trying to do api calls and not pre-caching things in the shared container (signified by a common app security group, just like other appex/app extensions) cause a huge performance hit. Apple has been giving this guidance all along, btw.
-K
This assertion of yours is not accurate. The issue with the use (or not) of Shared Containers is a real one:
Essentially, what we are supposed to do is cache data for watch apps - images can be cached, or loaded into, the watch image cache. Data should be stored in the shared container and read at launch, then updated. Updates should be performed by the main app in the background and serialized out.
This "store and forward" pattern is crucial to perceived performance - most complains about "slow apps" isn't in the actual interactions/"lag" on screen, but with loading/xferring data for display.
Writing for the Watch, while using the same languages as iOS "proper" requires different coding and implementation patterns which are not obvious on the simulator to get maximum performance.
Trying to do api calls and not pre-caching things in the shared container (signified by a common app security group, just like other appex/app extensions) cause a huge performance hit. Apple has been giving this guidance all along, btw.
-K
Watch update took about 20 minutes from start to finish over a 20Mbps connection.
-Raise to Wake More Responsive
-Astronomy Watch Face has higher contrast
-Hey Siri functions more accurately
-Third-Party Apps Loading Quicker
-Glances Loading Quicker
-HR Glance stays live until HR is displayed
-StopWatch 'Start/Reset' Buttons switched for ease of use
-Pace On Outdoor Runs/Walks seems more accurately updated
For the starting x.x.1 update, this seems to be a winner!
-Raise to Wake More Responsive
-Astronomy Watch Face has higher contrast
-Hey Siri functions more accurately
-Third-Party Apps Loading Quicker
-Glances Loading Quicker
-HR Glance stays live until HR is displayed
-StopWatch 'Start/Reset' Buttons switched for ease of use
-Pace On Outdoor Runs/Walks seems more accurately updated
For the starting x.x.1 update, this seems to be a winner!
What race are you running next? I am in your same boat. I have not received my Apple Watch yet, but don't plan on using it for running because I rarely take my phone and have my Garmin for that. Planning on a 24 hour race in September!
Posted in the other OS 1.0.1 thread under Apple Watch, but thought I would share here too.
The yellow/green ring, 'exercise' tracking is definitely more responsive. Before I could go on a 15 minute brisk walk (using the workout app and selecting outdoor walk) and only get credit for 5-7 minutes. Just went for a 30 minute walk and got credit for the entire 30 minutes.
The stand ring is also more responsive. Standing up and walking for a few seconds gives me credit instead of having to do a bunch of jumping jacks or running in place for 30 seconds.
Very pleased with the update.
The yellow/green ring, 'exercise' tracking is definitely more responsive. Before I could go on a 15 minute brisk walk (using the workout app and selecting outdoor walk) and only get credit for 5-7 minutes. Just went for a 30 minute walk and got credit for the entire 30 minutes.
The stand ring is also more responsive. Standing up and walking for a few seconds gives me credit instead of having to do a bunch of jumping jacks or running in place for 30 seconds.
Very pleased with the update.
It says it on the software update screen.
The install the update, make sure your Apple Watch is:
In range of your iPhone.
Connected to its charger
Charged at least 50%
Results
Has to do with how your metabolic rate is calculated... Does the polar just use you weight/age/sex to calculate you BMR and then work out your calories? If so this is just a Basic rate which can be in accurate.
Apple device adjust you BMR based upon data it collects from your heart through the day and adjust your Metabolic Rate to get closer formal rate (They use a breathing machine and a heart monitor during an work and resting to get this data)
Has to do with how your metabolic rate is calculated... Does the polar just use you weight/age/sex to calculate you BMR and then work out your calories? If so this is just a Basic rate which can be in accurate.
Apple device adjust you BMR based upon data it collects from your heart through the day and adjust your Metabolic Rate to get closer formal rate (They use a breathing machine and a heart monitor during an work and resting to get this data)
Not that I have noticed, but I don't use this watch face very often for this exact reason.
There's a process for calibrating the Apple watch distance calculations with the paired iPhone.
Curious, though. How does she know the Polar is accurate?
Watch also get snappier? Mine seems to show up less than a second after the face lights up. This is the most exciting thing about this update.