Wesley's Tool-Box

It's now been nearly two months since iPhone 5S and 5C debuted. They have been available to Koreans for nearly a month as well. So now it's not so hard to find them and take a look if you wanted to. Even half of the people in my team who had old iPhones already switched over to 5S.

If you remember, I gave up the much-sought but hard-to-get gold coloured iPhone 5S for the widely available space gray version because that would've been the only way I could get my hands on a 5S as soon as possible.

Looking back, I think I made the right choice. I was able to test it out earlier than most of the people. And I was going to put a skin on it as a basic protection anyway. This brushed metal style dark blue skin I put on really suits the phone well. When I finally got to see the gold version in person as you can see here, I still felt that my skinned iPhone looked better.


As for iPhone 5C, it did indeed look like someone put a coloured plastic case on a black iPhone 5. Nothing too impressive, really. I would have preferred the look of a 5th generation iPod Touch. I can definitely see how people would rather pay $100 more and get a 5S instead. This is perhaps why there are so many iPhone 5C ads in the city as well as commercials on TV.

There hasn't been much of wind-up toys in the house that my kids could get their hands on. I wanted to fill this hole a bit, but past experiences told me that kids don't play with one toy too long, so I should save money and go for some variety. For this, this little assembly kit series called "InoQ" from David Toy seemed to be a good idea.

I bought a Tyrannosaurus model from a local discount warehouse, which cost about US$3. It was on the low-end of assembly kits as far as price goes, but it said it would move, so it looked better than the stuff that you build and doesn't do anything else after. It also didn't look very sturdy, but considering the price, I thought it should be good enough for several minutes of enjoyment.

And boy, did it give us enjoyment.

By default, iOS devices like iPhones and iPads use 4-digit passcodes for the lockscreen. You could also use alphanumeric passcodes that are more secure, but they bring up a keyboard on the lockscreen. This is rather cumbersome compared to a keypad.

What's often overlooked is that there is in fact a nice compromise between the two. You could use a long numeric passcode, and it'll give you a keypad just like when you use a 4-digit passcode, as you can see here. You do need to press a button after entering the digits, but that's because it won't let someone guess how long it is.

I think this is even more useful when coupled with the Touch ID in iPhone 5S. You can still use the fingerprint to conveniently unlock most of the time, and you'll feel more safe in that there is less of a chance someone else could bypass that and unlock using a passcode instead. And the "autofill" of the passcode when you press your finger to unlock doesn't reflect how long the passcode is, either. It just shows nine dots all the time. A perpetrator won't be able to guess the length of the passcode by glancing at your screen.

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.