Wesley's Tool-Box

One of the reasons why the 1st generation (Gen 1) Apple Watch felt limited was due to its noticeably slow performance. App performance, especially the 3rd party ones, was sluggish enough that I eventually gave up making much use of them. The watchOS 3 update has implemented a lot of optimizations that alleviate the problem, but it couldn't hide the fact that the CPU simply was underpowered. Apple Watch Series 2 aimed to fix this by putting a CPU twice as powerful. Let's see if it worked out. First up is the boot speed. All tests were done with watchOS 3.0 installed.


Compared to iPhones or modern computers, Apple Watches are notoriously slow to boot up. Gen 1 still takes more than two minutes and while Series 2 is faster, it isn't significantly so. Fortunately, you won't need to reboot it often, so it's a minor annoyance at best. If you want to see the boot speed in real time, here's the boring video.

I wore my 1st generation Apple Watch Sport (some people call this first iteration Series 0; I will refer to it as Gen 1) every day for over 17 months from May 2015 to October 2016 until its duty was handed off to the Stainless Steel version of the Apple Watch Series 2. While it's still just as functional as the first day, some wear and tear are clearly visible as expected. The big scratch marks on the glass are from just two separate accidental brushes with a rough surface. Excepting those, it would have only gathered the small scratches at the edge of the screen.

Still, the big ones did made me buy the stainless steel version for the Series 2 since it has the much harder sapphire glass instead of the Ion-X hardened glass used on the aluminum (Sport) version. I'll see how better it would be in the coming months, but the lesson to be learned here probably is that if you're getting the Sport version, you might want to invest in a screen protection film.


Despite being only in contact with either my wrist or the charger, the back side of the Gen 1 watch sustained quite a bit of wear as well. The scratches started to appear on the center within about two months due to slight curvature difference between the charger, and the sweat likely aided in corroding the surface as well. While the scratches have not affected the functionality, it does make it look old and less durable.

It seems that Apple was aware of this issue and all Series 2 models got the much more durable ceramic back. For the Gen 1 and Series 1, the Sport version came with the composite back and the more expensive versions (stainless steel type and Edition) got the ceramic back. I would recommend avoiding the composite back if possible.

While the iPhone 7 I got from Japan was busy getting reviewed, the iPhone 7 Plus and the Apple Watch Series 2 I asked my friend Andy in the United States to preorder for me was traveling around the world. The 7 Plus in particular was actually stuck in here South Korea for a while in transit from China to United States due to shipping issues. Once it landed in the States, Andy sent it back across the Pacific so I could have it in my hands. And that's why it took three weeks to arrive.


The box for the iPhone 7 Plus is the same size as the one for 6S Plus, but with the same new design as the 7. It seems the new Apple Watch Series 2 also come in the same-sized box as the previous version. I ordered a Stainless Steel one this time, unlike the Aluminum (Sport) version last year and was a bit surprised how heavy the box was. Shipping weight was 1.2kg for the watch and 0.5kg for the phone; even with the shipment box removed the boxes weighed 880g and 460g, respectively.

It's now been one full year since I started wearing Apple Watch Sport and now is a good time to give you an update. I have been wearing it all the time except when it needs to be charged, so it has been through a lot. Daily showers and occasional swimming sessions may have caused a bit of degradation on the left edge of the screen, and an encounter with a rough surface left the glass with noticeable scratch lines. Despite all this, it's holding up well and functioning normally. I'll probably send the device in for replacement using AppleCare+ after I buy the next version, though.

In terms of battery life, it has consistently delivered at least 24 hours of use for me, except during early watchOS 2.0 betas. So I'm now accustomed to about 22 hours of use (with about 10 to 30% left as I take it off) and 2 hours of charging. The only times I wish the battery life was longer is when I do long-distance travelling, where the active time might stretch beyond 30 hours.

As for its uses, I've settled on the watch mainly being a quick notification-response device and a fitness tracker. Those two functions currently work fairly well. Meanwhile, the native app support with watchOS 2 has been hampered with the relatively slow performance. It often makes me want to reach for my iPhone instead of loading the relevant app on the watch. This needs to be addressed in the near future if Apple Watch is to be taken seriously beyond being an "accessory."

Now, the fitness tracker part of the watch was something I was looking forward to when I bought it. I have lost weight through exercise before, but lack of reminders once the goal was reached resulted in regaining some of that weight after a few months. So I decided to make good use of Apple Watch to keep me stay fit. I made sure to reach the daily Move goal every day, which had been set to 450 kcal after the first month. Missing this goal only a couple of times, I was able to earn the "365" badge you see above two days ago. Let's see the activity and weight trends in detail.


Why did I choose the 450 kcal mark? This is generally about 200 kcal more than I would normally burn through a normal day. 50 minutes of walking or 20 minutes of jogging can fill that in - these activities can easily blend into the daily routine and also conveniently make me reach the 30-minute Exercise goal in the process. Basically, I can get the bare minimum amount of exercise that Apple Watch recommends via its three-ring system with that setting. The graph evidently shows that I don't actively seek out to go beyond this goal unless something else is going on, like when I'm traveling. Some of the big spikes correlate to my overseas trips - New Zealand in May (2015), UK in July, and Japan in September, to name a few.

As a side note, the data for the resting calories starts on July 9 because this is when watchOS 2.0 beta 3 came out and made Apple Watch start recording this data on iPhone's Health database. Before that, the data resided only within the Activity app, likely because it was rudimentary and static, not to mention less accurate - it was about 40 to 50% more than expected. Since the update, the resting calories data is recorded in real time and seems to be more in line with the mainstream calculations.

Interestingly, I noticed that just reaching the Move and Exercise goals wasn't doing a particularly good job of shedding the weight in the early months. I did have a weight scale and occasionally checked my weight with it, but it hovered between 83 and 84kg without any upward or downward trend during that time. Besides, I never got around to recording the data anyway. The only data point during the period was from the annual check-up at my workplace. I decided to do something about it and got myself a so-called "smart scale" with Bluetooth connectivity in August.

After I installed watchOS 2 beta 4 when it came out on July 22, 2015 (July 21 at Apple HQ), my Apple Watch felt more sluggish than usual. Even the terrible beta 1 wasn't like this. What's worse, the watch froze up after a few hours. I noticed that it'd never last more than 4 hours at a time, requiring a forced restart (pressing side button and digital crown together for 10 seconds) to get it working again.

I tried resetting and restoring, then resetting and setting up the device as new. Neither fixed the issue. Somehow, this beta was unusable on my watch. If this problem was happening to everyone, I would've heard about it and Apple would be pulling the beta, but this wasn't the case. Most people were actually saying it worked better than previous betas, which baffled me. Then I eventually found someone else having the same problem.

It turns out, having the watch face set to "Simple" was the culprit. Using another watch face ("Modular" was recommended) supposedly solved the problem. So I changed the face to Modular and indeed the problem went away. I had been using the Simple face for nearly 3 months, so I never thought of changing it to anything else. Who knew a bug in the beta would force me to do otherwise?

Using Simple face on beta 4 had serious impact on battery life as well - about as bad as the infamous beta 1. Also, it kept consuming battery while the device froze up, too. I went to sleep with the fully charged watch, only to find out that it froze up about two hours in, and had 37% of charge left after 5 hours when I woke up. So I'm guessing the watch face steadily hogged system resources until everything else became inoperable, but kept going.

So if any of the developers with watchOS 2 beta 4 are experiencing lock ups and slow performance, avoid Simple watch face and switch to something different before resetting your watch.