This post has been updated with a note from the author at the end.
Apple released the first beta of iOS 5 after WWDC two weeks ago, and I’ve been using it on my iPhone 4 and iPad 2 ever since.
Is iOS 5 Beta 1 stable enough to use full-time? A lot of people have asked us this, and after trying for a few weeks, I can respond pretty authoritatively: not by half. Here’s our list of at least nine things that Apple needs to fix before iOS 5 beta is usable full time.
I hope you didn’t jump out of bed at the crack of dawn today, throw open the curtains, crack open a few eggs in the frying pan, connect your iPad to iTunes and then sit down to spend the next few hours to continuously hammer the “Check for Update” button, because we’ve got some bad news for you: it doesn’t look like iOS 4.2 is going to drop today.
Watch out! A major new security hole in the iPhone software has just been discovered… a bug that allows anyone who picks up your phone to easily unlock it and access all of your phone data under iOS 4.1.
In case you want to try it yourself, here’s how you gain access to a locked iPhone through the security hole. When your iPhone 4 is locked with a passcode, tap the emergency call button, then enter three hash keys. Now tap the call button then immediately hit the lock button.
Do the above correctly and you’ll be rewarded by being dumped into the iPhone’s Phone app. From there, you can access the user’s favorites, contacts, dial pad,. recent calls, voice mails and even send SMS and email messages through the Address book.
It’s a pretty huge bug, and it seems to work on all iPhones running iOS 4.1. This is the sort of thing Apple will patch pretty quickly, but in the meantime, show extra dilligence and care in not leaving your locked iPhone lying around.
iPhoto ’11 is an incredible update to Apple’s casual photo managing/editing suite which makes organizing and tweaking your digital snaps simpler and more streamlined than ever, but only if iPhoto ’11 doesn’t gobble up your existing library as part of the upgrade process… a mishap that is striking an alarmingnumber of upgraders.
Two and a half weeks ago, as New Zealand rolled back their clocks for Daylight Savings Time, Kiwis started noting an odd iOS bug: any recurring alarms they had set on their iPhones were going off an hour early. Curious, but then it gets curiouser: last week, when Australian had to adjust for Daylight Savings Time, it happened again.
We love the story: its like a mini-Y2K for iOS 4.1, hitting iPhone users around the world as their country enters Daylight Savings Time… and with Europe set to enter DST on October 30th, and America on November 6th, the bug is about to hit a lot more people.
So what does Apple intend to do about this? Apple Australia says they’re on it and have developed a fix that will be included as part of an upcoming software update. Since iOS 4.2 has a late November ship date, that means we’re likely to get an iterative iOS 4.1.1 update sometime before the 30th, when all of Europe starts hurling their iPhones dramatically against the wall when their alarms rob them of an hour of sleep.
About a month ahead of America and Europe, New Zealand clocks fall an hour back when they switch to Daylight Savings Time on the last Sunday of September. Apparently, though, New Zealand iPads and iPhones are proving a tad overzealous when it comes to falling back this year: numerous iOS users are reporting that since yesterday’s switch, their alarms are going off an hour early. Given that Kiwis were already having to wake up an hour earlier than they were used to, that’s quite a rude awakening.
Apple’s Automator is a fantastic way to manage your iTunes tracks… but with Apple’s iTunes 10 update, many iTunes-specific Automator workflows have simply stopped working.
According to upset users in Apple’s discussion forums, the vast majority of iTunes Automator actions go missing when you install iTunes 10. Try to run a previously created iTunes workflow and you will ironically be prompted to install iTunes 4.6 or higher. Ugh.
The good news here is that none of the functionality has disappeared from AppleScript, so it should be able to replicate the functionality if you change gears. Still, the sudden absence of iTunes functionality in Automator is mysterious: did Apple purposely drop the functionality, or is this a bug? If the former, what was Apple’s rationale?
Buying an Apple product on the first day it’s available is a recipe for disaster. This universal truth was reiterated today as Macintouch reported a nasty bug in Leopard where if you move a file to an external drive and then unplug the drive before it finishes copying, it will delete the file from the source and the destination drive.
In our test, we used Command-drag to move several large folders from a MacBook internal drive to an attached FireWire 800 external drive. While the folders were being moved, we disconnected the FireWire cable. The folders disappeared from both drives!
Yikes. Not an incredibly common flaw, but definitely easy enough to do that it should never show up in a shipping product — especially because it was present in OS X 10.1, and not inTiger. That’s a step in the wrong direction.