-
Recent Posts
- Apple in negotiations with streaming partners for upcoming TV device?
- Apple announces WWDC 2012 schedule for June
- Regional carriers in the U.S. unveil iPhone support
- Apple releases new Apple TV hardware with 1080p support
- Apple drops iPad 2 price to $399
- Apple unveils ‘the new iPad’
- Apple announces March 7th iPad event
- Gatekeeper: Apple’s next move to increase Mac security
- Apple announces Mac OS X 10.8 “Mountain Lion”
- Apple to launch iPad 3 in early march
- Apple schedules education event for January 19th
- Next iPhone to support T-Mobile 3G band
- Quad core references found in iOS 5.1 beta
- Apple TV update turns on TV show purchase & streaming for Canada, Australia and the U.K.
- Apple says Carrier IQ unused, will remove it from iOS 5
-
Post Categories
-
-
-
Matt
iDevice firmware 2.2.1 released
Apple released version 2.2.1 of its iPhone/iPod Touch operating system firmware today with many under the hood changes & bug fixes but relatively few “front end” changes — most of them in Mobile Safari.
From Apple’s release notes for the iPhone version of the 2.2.1 package, which weighs in at 247MB:
iPhone Software Update 2.2.1
This update contains bug fixes and improvements, including the following:
- Improved general stability of Safari
- Fixed issue where some images saved from Mail do not display correctly in the Camera Roll
Products compatible with this software update:
- iPhone
- iPhone 3G
The iPod Touch version does not appear to include release notes, but is believed to have the same Safari changes and kernel revision.
On the iPhone side, firmware for the device’s phone sub-board (a separate system architecture that handles the iPhone’s calling/cellular modem functionality; completely partitioned from the main board which contains the primary ARM11 CPU, 128MB SDRAM and Flash storage) has been updated to version 2.30.3. No word as yet on whether there are any major, or noticeable, changes in said sub-board firmware.
Have you had an experience with iDevice OS 2.2.1 that you’d like to share with the community? Email, tweet, IM us — or submit a web comment below!