Wesley's Tool-Box

If you buy a phone with camera function in Korea, you'll notice that taking a photo will produce a shutter sound even if you set the phone to vibrate or silent mode. This is because of a government recommendation set in 2004 to have phones always make a sound louder than 65dB when a photo is taken, to curb spy shots and boost privacy.

iPhones are no exception, and if you buy one in Korea, the silent mode switch does nothing to, uh, silence the shutter sound. This is interesting because iPhones are generally not differentiated except for slight variation in CDMA or LTE support.

(ADDENDUM: The situation seems to be the same for the iPhones bought in Japan or the Philippines.)

The question, then, would be if this shutter sound is controlled on a carrier / region basis or device basis. If it's controlled by detecting what carrier or region it's being used, then taking the phone outside Korea would silence the shutter sound. If it's preconfigured on the device, whether or not the sound will persist would depend on where you originally bought it from. So which is it?

Late last month, there was an RFID-themed expo called RFID/IoT World Congress 2013 in COEX. The entry badge happened to contain an RFID card that you could use to tag at a booth so the company running it could know that you visited. It turns out that the card is basically a blank RFID card. My contact info must have been paired to the card's serial number, and the terminals merely checked the number and pulled the paired contact data from a central database.

When I took it home and poked it around with the only NFC-enabled smartphone I have, LG Prada 3.0, the card was a generic MIFARE Ultralight card without any locks or data. These types of card can only contain 64 bytes of data, 48 of which is user-programmable, so it's apparently very limited and cheap. That seems to be a sensible choice for something to hand out to thousands of visitors.

Because it was initially unformatted, regular NFC apps on the phone refused to do anything with it. But with the NXP TagWriter app, I was able to format and write data into it at once. To test, I tried to program the URL of this website and its title into it. It ended up being 47 bytes total, and the card reserved 2 bytes for something else, so it went over the storage limit. I omitted the hyphen and I was able to write the data successfully. When I tag the phone with it, it would load this website.

Looks like I should try to find some cheap MIFARE Ultralight cards like this one and happily program all sorts of things to it.

Over the past 30 days of using the iPhone 5S, I've written several reviews of the phone on various aspects, as one of the first person to use it in Korea. I believe all the major points have been covered, and since the phone has been officially released in Korea last Friday, Here's a quick summary and link to each of the aspects that I took a look at.

1. Exterior [Click to Read]
Almost identical to iPhone 5 except the home button, flash, and colour.
The packaging box is smaller due to smaller charger.

2. Network Compatibility [Click to Read]
Unlocked iPhone 5S bought overseas will fully work in Korea, including LTE.

3. "Wideband" LTE Compatibility [Click to Read]
Yes, it's compatible.

4. Camera Speed [Click to Read]
At least twice as fast as iPhone 5. Slo-mo and burst modes work well.

5. Camera Quality [Click to Read]
Smoother photos, improved low light performance, and more natural flash.

6. Biometric Feature [Click to Read]
Convenient, fast, and moderately secure. Works with several body parts.

7. Motion Coprocessor [Click to Read]
Tracks your movement well without battery penalty. Great for fitness apps.

8. Performance Tests [Click to Read]
Twice as fast as iPhone 5 in CPU and GPU tests. LTE speeds remain the same.

9. Sensor Issues [Problems in iOS 7.0.2] [Fixed in iOS 7.0.3]
Accelerometer had calibration problems, but it was fixed in iOS 7.0.3.
Other sensors worked fine within margin of error.

10. Battery Performance [Click to Read]
Lasts slightly longer and charges slightly faster than iPhone 5.

There was another bright pass of International Space Station over the sky this evening. I set up my Canon SX50 HS camera on a nearby park and tried my best to take photos of them.

As always, photographing a tiny object moving at 1 arc degree per second at 50x zoom fully manually isn't really going to work out very well. Even if I somehow catch it at the edge of the frame, it'll exit it in about 1.6 seconds. It only took about 3 minutes for the station to go across the sky and I've only managed to get four shots of it, two of which I'm showing here. They're crops magnified by 2x.

Compared to my first attempt with the same camera, the shot on the left do show the solar panels on the station more distinctly. As the ISS streaked from west to east, its orientation as visible from the ground changed, as is evident between the two photos. It seems that it would be best to try photographing it as soon as it started becoming visible, as the shape looks more recognizable.

Photo 1(Left): 1200mm - ISO 200 - 1/400s (-3.1 mag.)
Photo 2(Right): 1200mm - ISO 200 - 1/200s (-3.9 mag.)
Camera: Canon SX50 HS
Location: Suwon, Korea

Even with excellent performance, lackluster battery life will tarnish the usability of a phone. It's thus natural to see if iPhone 5S has made any improvements with battery usage from the previous generation. Apple has targeted it to be at least as good as iPhone 5, so I wanted to see how the two really compares in real life use.

The official capacities are 5.45Wh (3.8V 1440mAh) for iPhone 5 and 5.92Wh (3.8V 1560mAh) for iPhone 5S, an 8.6% difference. So 5S could use a little more power and still stay even. The iPhone 5 I have has seen use for about two months, while iPhone 5S has been with me for a month. So both have relatively fresh batteries close to these original capacities.

With these in mind and full charge, I started using the two devices, which were running iOS 7.0.3 now, in the same manner throughout the day. This meant opening the same app and taking the same actions at the same time. It's an interesting experience, and because apparent responsiveness of the two devices are similar at casual use, it wasn't too difficult to carry out.

To even the playfield further, push notifications, push data and automatic app updates were disabled, while screen brightness was fixed to 33%, which is good for indoor use. WiFi and Bluetooth were both enabled, but not used, so LTE was responsible for data. Other settings like GPS and visual effects were kept on by default. So how did the draining of the battery turn out?