Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iPhone 2.0 Firmware (5A347) Available Early

jwsmiths said:
Guys I have a sinking feeling she's downloading 1.1.4. She said she clucked restore, not update. Sorry. I KNEW it was too goidto be true for me to get the first copy of 2.0!
Click to expand...

That's kinda what I figured. The size you were quoting sounded a lot like the last update and with all the new features there is NO WAY it could be the same size... too bad...:(
 
SPX said:
Okay folks, my apologies that I haven't answered some of the replies to me today; It's been a very busy day.

To answer the question that several users have asked both in public, and via private message, iPhone 3G is shipping with build 5A345. 5A347 is a build that was never intended for a production environment, and certainly not for installation on the original iPhone! As I mentioned earlier, it was built to be installed on iPhone 3G development test units only (note, I did not say production units), and has not been tested or designed for the original iPhone.

Build 5A347 contains a significant amount of debug code and that is, in part, the reason for the slowdowns iPhone classic users are seeing. As also mentioned previously, when 32k of debug data is collected, the build is designed to dump the data to a location which no production iPhone supports, and hence you're seeing timeouts while the write process attempts to do its job.

As far as other slowdowns are concerned, any time iPhone 3G specific code attempts to execute (location, contacts, pictures, and web are the most prevalent) a timeout is going to occur, and this will be seen to the end user as a momentary freeze. As presented by others earlier, while the code base is the same between the original iPhone and iPhone 3G 2.0 software, 5A345 has code modules active which can detect which hardware it is running on (touch, iPhone original, iPhone 3G, etc.) and handle certain cases appropriately, given the hardware, and thereby prevent the momentary slowdowns that some users are seeing.

In plain English what I am saying:

- 5A345 does not have the slowdowns some users are seeing.

- Furthermore, 5A347, the build which many on here are now running was not designed for anything but iPhone 3G developmental units. That is to say, running it on the original iPhone is not a tested or intended platform.

- Slowdowns that users are seeing are caused specifically by running an incorrect version of the firmware on unsupported units.

I hope that this information helps clear up some lingering questions.
Click to expand...
So what do you reccomend for people who have installed the firmware?
 
twstdroot said:
http://phobos.apple.com/version shows 5A345 SameAs 5A347... so one would likely come to the conclusion that they are the same thing. I'm running 5A347 with no issues at all.
Click to expand...

From your link :

iPhone1,2 5A345 SameAs 5A347 5A347 Restore BuildVersion 5A347 DocumentationURL ttp://appldnld.apple.com.edgesuite.net/content.info.apple.com/iPhone/061-4722.20080710.Vf0pW/iPhoneDocumentation_2.0.ip FirmwareURLttp://appldnld.apple.com.edgesuite.net/content.info.apple.com/iPhone/061-4955.20080710.bgt53/iPhone1,2_2.0_5A347_Restore.ipProductVersion 2.0
 
so my i upgraded and it said i had to activate it.. I start going thru the steps, and at the end it said I was going to sign a new contact and add 3g interenet.. so i cancelled... How did you guys skip this step?

I have at&T already :-(
 
binaryspazz said:
so my i upgraded and it said i had to activate it.. I start going thru the steps, and at the end it said I was going to sign a new contact and add 3g interenet.. so i cancelled... How did you guys skip this step?

I have at&T already :-(
Click to expand...

I never saw that screen. After it installed on the phone did you select to restore or activate? I did restore and everything worked fine.
 
binaryspazz said:
so my i upgraded and it said i had to activate it.. I start going thru the steps, and at the end it said I was going to sign a new contact and add 3g interenet.. so i cancelled... How did you guys skip this step?

I have at&T already :-(
Click to expand...

Dude we're only a few hours away...couldn't you have just not bit the bullett?
 
SPX said:
Okay folks, my apologies that I haven't answered some of the replies to me today; It's been a very busy day.

To answer the question that several users have asked both in public, and via private message, iPhone 3G is shipping with build 5A345. 5A347 is a build that was never intended for a production environment, and certainly not for installation on the original iPhone! As I mentioned earlier, it was built to be installed on iPhone 3G development test units only (note, I did not say production units), and has not been tested or designed for the original iPhone.

Build 5A347 contains a significant amount of debug code and that is, in part, the reason for the slowdowns iPhone classic users are seeing. As also mentioned previously, when 32k of debug data is collected, the build is designed to dump the data to a location which no production iPhone supports, and hence you're seeing timeouts while the write process attempts to do its job.

As far as other slowdowns are concerned, any time iPhone 3G specific code attempts to execute (location, contacts, pictures, and web are the most prevalent) a timeout is going to occur, and this will be seen to the end user as a momentary freeze. As presented by others earlier, while the code base is the same between the original iPhone and iPhone 3G 2.0 software, 5A345 has code modules active which can detect which hardware it is running on (touch, iPhone original, iPhone 3G, etc.) and handle certain cases appropriately, given the hardware, and thereby prevent the momentary slowdowns that some users are seeing.

In plain English what I am saying:

- 5A345 does not have the slowdowns some users are seeing.

- Furthermore, 5A347, the build which many on here are now running was not designed for anything but iPhone 3G developmental units. That is to say, running it on the original iPhone is not a tested or intended platform.

- Slowdowns that users are seeing are caused specifically by running an incorrect version of the firmware on unsupported units.

I hope that this information helps clear up some lingering questions.
Click to expand...

Out of curiosity, why would a developer build be on the public update list?
 
SPX said:
Okay folks, my apologies that I haven't answered some of the replies to me today; It's been a very busy day.

To answer the question that several users have asked both in public, and via private message, iPhone 3G is shipping with build 5A345. 5A347 is a build that was never intended for a production environment, and certainly not for installation on the original iPhone! As I mentioned earlier, it was built to be installed on iPhone 3G development test units only (note, I did not say production units), and has not been tested or designed for the original iPhone.

Build 5A347 contains a significant amount of debug code and that is, in part, the reason for the slowdowns iPhone classic users are seeing. As also mentioned previously, when 32k of debug data is collected, the build is designed to dump the data to a location which no production iPhone supports, and hence you're seeing timeouts while the write process attempts to do its job.

As far as other slowdowns are concerned, any time iPhone 3G specific code attempts to execute (location, contacts, pictures, and web are the most prevalent) a timeout is going to occur, and this will be seen to the end user as a momentary freeze. As presented by others earlier, while the code base is the same between the original iPhone and iPhone 3G 2.0 software, 5A345 has code modules active which can detect which hardware it is running on (touch, iPhone original, iPhone 3G, etc.) and handle certain cases appropriately, given the hardware, and thereby prevent the momentary slowdowns that some users are seeing.

In plain English what I am saying:

- 5A345 does not have the slowdowns some users are seeing.

- Furthermore, 5A347, the build which many on here are now running was not designed for anything but iPhone 3G developmental units. That is to say, running it on the original iPhone is not a tested or intended platform.

- Slowdowns that users are seeing are caused specifically by running an incorrect version of the firmware on unsupported units.

I hope that this information helps clear up some lingering questions.
Click to expand...

Hey SPX i might be one of the only few who listened! haha you guys cant wait 1 day. jeez i remember working on my performa 400 back in late '92 with my brand new external cd rom drive calling egghead seeing if the 14.4 modems were in yet! You guys have all been spoiled im gonna fire up my performa 400 and play some vector till the firmware comes out. all good things come to those who wait.

and for all the guys that are OMG will this work on an unlocked iphone? well gee have u been sleeping under a rock for a year? You unlock your iphone you have no more warranty plain and simple. THEY SEE ME ROLLIN' THEY HATIN' TRYIN TO CATCH ME RYDIN DIRTY. And i swear i just read in this wild forum were not many people seem to read the first post, "does this work on the ipod" COME ON PEOPLE!
 
I haven't updated mine. I'm waiting for the official release. But I'm through waiting tonight. I'll just wake up in the morning and hope that it is ready!!:D
 
beinhorn said:
Hey SPX i might be one of the only few who listened! haha you guys cant wait 1 day. jeez i remember working on my performa 400 back in late '92 with my brand new external cd rom drive calling egghead seeing if the 14.4 modems were in yet! You guys have all been spoiled im gonna fire up my performa 400 and play some vector till the firmware comes out. all good things come to those who wait.

and for all the guys that are OMG will this work on an unlocked iphone? well gee have u been sleeping under a rock for a year? You unlock your iphone you have no more warranty plain and simple. THEY SEE ME ROLLIN' THEY HATIN' TRYIN TO CATCH ME RYDIN DIRTY. And i swear i just read in this wild forum were not many people seem to read the first post, "does this work on the ipod" COME ON PEOPLE!
Click to expand...

seriously, read posts before you ask anything, especially when it's stated clearly in the original macrumors story to begin with!
 
dannyallen34 said:
Assuming all of this is true, and since you seem to know what you're talking about, will users who have updated using the 5A347 firmware be able to "Upgrade" to the production 5A345?
Click to expand...

Those who have installed 5A347 will be unable to change their firmware to 5A345 via the conventional method, iTunes. The reason being that as far as the updater is concerned, 5A347 is of the same version of 5A345 (2.0). Firmware version changes to 5A345 (production) on units that have 5A347 installed will have to be completed manually.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back