Normally, I wouldn't get overly excited about a jailbreak being released, but October 9th's 2010 jailbreak is a new kind. What's more, with Daylight Savings Time coming up, iPhone users are at risk for oversleeping. Here's the scoop, and why channel folks should care...

Dave Courbanou

October 11, 2010

2 Min Read
iOS 4.x Has Daylight Savings Time Glitch; Gets Jailbroken

Normally, I wouldn’t get overly excited about a jailbreak being released, but October 9th’s 2010 jailbreak is a new kind. What’s more, with Daylight Savings Time coming up, iPhone users are at risk for oversleeping. Here’s the scoop, and why channel folks should care…

It’s called “limera1n” and it’s the latest jailbreak for iOS 4.1 devices using the new Apple A4 chip. But why does this differ from the previous jailbreak attempts? Because it’s not a software jailbreak, it’s actually an exploit that occurs deep under the hood, in the iPhone’s boot-rom. That means Apple can’t patch it with a software update, and without some serious changes to the hardware’s firmware, this jailbreak will technically work forever, and allow updates to future iOS 4.X revisions.

Essentially, this gives you the best of both words: Get the latest and greatest Apple updates, while also keeping all the fun jailbroken features you’ve come to know and love. (Quite seriously, I’m enjoying jailbreaking for tethering. AT&T’s $20 extra a month for tethering is criminal.)

Channel Chatter

Why does the channel care? There’s plenty of productivity-driven features that Apple says “no” to because they mess around with the core of iOS. Currently, I’m enjoying LockInfo — which provides an at-a-glance look of your SMS, E-mail, upcoming calendar events and missed calls — all inside your lock screen, without having to unlock your phone. Quick, easy, violates Apple’s guidelines, but oh-so useful.

But more importantly, the iOS 4.x seems to have a Daylight Savings Times glitch, as noticed by the entire country of Australia. The Sydney Morning Herald reported that 55% of respondents on their site’s survey were late for work because of the glitch.

The glitch (or bug) effects people who’ve set a reoccurring alarm (like me). The work around is to either have manual or non-reoccurring alarm, or to tweak your reoccurring alarm an hour different accordingly.

The SMH also reported that some iPhone alarms didn’t even go off at all, while others (and comments) detailed that their alarm actually went off an hour earlier, (which, arguably, could have equally disastrous consequences for your day).

US iPhone-dependent users, be on the look out as November 7th sneaks up on you.

Sign up for The VAR Guy’s Weekly NewsletterWebcasts and Resource Center; and via RSS; Facebook;   Identi.ca; Twitter and VARtweet.

Read more about:

AgentsMSPsVARs/SIs
Free Newsletters for the Channel
Register for Your Free Newsletter Now

You May Also Like