Commentary

Spin Control? Apple Explains Why Jailbreaking Is Bad

This is rich. A day after Apple's claims that jailblreaking iPhones can cause catastrophic harm became public, Apple updated its support page to explain exactly why jailbreaking iPhones a bad thing.

This is rich. A day after Apple's claims that jailblreaking iPhones can cause catastrophic harm became public, Apple updated its support page to explain exactly why jailbreaking iPhones a bad thing.Here's what Apple says, followed by my comments:

As designed by Apple, the iPhone OS ensures that the iPhone and iPod touch operate reliably. Some customers have not understood the risks of installing software that makes unauthorized modifications to the iPhone OS ("jailbreaking") on their iPhone or iPod touch. Customers who have installed software that makes these modifications have encountered numerous problems in the operation of their hacked iPhone or iPod touch. Examples of issues caused by these unauthorized modifications to the iPhone OS have included the following:
  • Device and application instability:Frequent and unexpected crashes of the device, crashes and freezes of built-in apps and third-party apps, and loss of data.
  • Unreliable voice and data: Dropped calls, slow or unreliable data connections, and delayed or inaccurate location data.
  • Disruption of services: Services such as Visual Voicemail, YouTube, Weather, and Stocks have been disrupted or no longer work on the device. Additionally, third-party apps that use the Apple Push Notification Service have had difficulty receiving notifications or received notifications that were intended for a different hacked device. Other push-based services such as MobileMe and Exchange have experienced problems synchronizing data with their respective servers.
  • Compromised security: Security compromises have been introduced by these modifications that could allow hackers to steal personal information, damage the device, attack the wireless network, or introduce malware or viruses.
  • Shortened battery life: The hacked software has caused an accelerated battery drain that shortens the operation of an iPhone or iPod touch on a single battery charge.
  • Inability to apply future software updates: Some unauthorized modifications have caused damage to the iPhone OS that is not repairable. This can result in the hacked iPhone or iPod touch becoming permanently inoperable when a future Apple-supplied iPhone OS update is installed.
Apple strongly cautions against installing any software that hacks the iPhone OS. It is also important to note that unauthorized modification of the iPhone OS is a violation of the iPhone end-user license agreement and because of this, Apple may deny service for an iPhone or iPod touch that has installed any unauthorized software.
Apple is sternly saying, "Don't jailbreak!" Most of what Apple says above is accurate. I jailbroke my original iPhone back in 2007, and experienced a lot of the issues noted above. Instability was perhaps the biggest issue, especially if you install a lot of unapproved applications. I didn't see too much of the dropped calls, but visual voicemail definitely became disabled.

You can't blame Apple for taking this stance, though it is a bit onerous. Situations such as the Great Google Voice Debacle of 2009 are enough to push users over the edge and convince them that jailbreaking is the way to go. Granted, not many other mobile platforms have 50,000 applications available to them at the moment, so I think it is a little weak for iPhone users to claim "lack of choice."


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Do these arguments make sense in Apple's case against the Electronic Frontier Foundation? That's for lawyers to decide. In the mean time, remember that Apple is in control. Not you.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links