Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
For people that have ALREADY completed 2.0.2 update,do you notice anything different?
- Thread starter Rybold
- Start date
- Sort by reaction score
It's all fantasy.
Startup time (after reset) is still abysmal. Safari still crashes. Responsiveness is still underwhelming. Anyone reporting snappier performance is just experiencing a short period of post-reset fluidity. Give it an hour or so and it's back to normal (i.e. you can go out to lunch while Contacts loads).
2.0.2
I definately find this update worthwhile. Upon update I get 5 bars signal which never happened before (I used to get 1 or no bars which really cracked me up) Contact lag still exists (1~2 sec) but have noticeablely improved. However before I reach conclusion I will have to wait few more days to find out if it really was an update that improved the lag not the rebooting.
I definately find this update worthwhile. Upon update I get 5 bars signal which never happened before (I used to get 1 or no bars which really cracked me up) Contact lag still exists (1~2 sec) but have noticeablely improved. However before I reach conclusion I will have to wait few more days to find out if it really was an update that improved the lag not the rebooting.
The only thing I can point to as a definite improvement is that when you go to contacts, you start to scroll almost straight away, whereas there was a 3-4 second lag before.
Hopefully Safari will crash less but I haven't used it enough to discern whether this is now the case.
Hopefully Safari will crash less but I haven't used it enough to discern whether this is now the case.
It notifies you that you can redownload for free after you click on the purchase button and enter your password (a bit weird, I know).
No discernible difference at all.
People, everything is going to be faster immediately after a restore, regardless of what version you're restoring to. So this "_____ is now faster" mantra is likely bunk. The true test is how the phone reacts after a couple of days of use.
People, everything is going to be faster immediately after a restore, regardless of what version you're restoring to. So this "_____ is now faster" mantra is likely bunk. The true test is how the phone reacts after a couple of days of use.
. Ditto. As well, Safari is more more stable (no crash after about am hour of browsing) and it seems "snappier" to borrow a word used many times before. No noticeable difference to 3G, but I never had an issue or dropped calls before. All good on this end!
SMS doesn't do a 4-5 second hang for me anymore and things seem to switch back and forth quicker.
Yeah, I said it, it's snappier.
Yeah, I said it, it's snappier.
For those who complain: Why even own an iPhone if you're going to complain about every single update. Clearly there were things fixed with this update, just because you can't find them, doesn't mean anything. Wait a week, if you're phone seems more stable, then that was probably the update. If not, clearly you're doing something stupid on your phone to make things act up. Just my opinion.
What if the firmware update actually brings new bugs? oh wait... it won't happen, right? because the update is from Apple
tsk tsk tsk. If they came out with buggy firmware (read: 2.0) just blame the user eh?Nevertheless, 2.0.2 installed here, no noticeable improvement. I haven't been gotten keyboard lag so far. Whereas with 2.0.1, I got it ONCE.
I've noticed:
- Much faster syncing
- Backups are halved in time (hooray!)
- I'm also suffering from post-update 'snappiness'
R-Fly
- Much faster syncing
- Backups are halved in time (hooray!)
- I'm also suffering from post-update 'snappiness'
R-Fly
I'm seeing much less stability with the app store and installing and removing of apps. App store crashed whilst browsing, later iPhone crashed whilst installing app. iphone reboots, app continues installing (taking forever) tried browsing app store whilst this was installing, very slow, iphone resets again.
Bah.
Bah.
Update seems fine. I ran an iphone speed test on 3G and im get approx 3.4 mbits per second which is great. Im with Telstra and live in Ballarat. I do the commute via train and for most of that trip I only have one bar of 3G but I can still make and receive calls and surf the net even with only 1 bar and I havent had a drop out yet. THe guy at work whos with Virgin Mobile when he runs the test gets .8 mbit per second and has had a lot of dropouts so hopefully the update works for him. The only thing im hoping for is better battery life, will be interesting if the phone shows only 1 bar on the train trip into melbourne tommorow or if it goes up.
Look folks this wasn't a placebo but it sure wasn't our silver bullet either. My observations are that it didn't fix anything we wanted. Keyboard lag in the mail app this morning was horrid for me, I don't buy the snappier effect, and I get the same 3G signal I got yesterday.
That being said and knowing how development cycles work this update was probably a security update of some sort or something that was discovered in the 2.1 testing and put retroactively into the 2.0 branch. Typically when you release software you have a small team running maintenance while the core team charges ahead on the next release. If the 2.0 team fixes something those fixes are likely pushed up to the 2.1 team. If the 2.1 team finds or fixes something it can depend on whether the 2.1 team's fix will fit readily into 2.0 or not. For example a fix to 3G reception by the 2.1 team would almost certainly NOT be retrofitted into 2.0.
This being said certain assumptions can be made:
2.1 is the update we've been waiting for. 3G, Keyboard lag etc.
2.0.1 and 2.0.2 are not and any 2.0.x release won't be. 2.0.2 probably fixed a major bug or security hole discovered internally in one of the deep libraries. When its dissected (if it is) its likely that it'd be found to have one or two core libraries that were changed and that's it (remember 1.0.2 - another security fix)? This also makes sense as to why Apple isn't publishing the specific fixes because they don't want to publish an undocumented security hole or point hackers in a direction.
2.0.2 wasn't planned which supports the security fix theory. If it wasn't planned it wouldn't have come out just a few days after beta 4 of 2.1 was seeded. 2.1 is due EOM or End of next month. Either way its due soon. I believe its EOM and that's why they pulled push notifications. 4-5 betas is more than enough. Given this whatever was in 2.0.2 was important enough for a release to be done with haste (again lending itself to security theory).
What's this mean for us? Sigh more waiting for the 3G reception issue to be fixed, the keyboard lag, etc to be fixed. Hopefully in the next week we'll get it...
That being said and knowing how development cycles work this update was probably a security update of some sort or something that was discovered in the 2.1 testing and put retroactively into the 2.0 branch. Typically when you release software you have a small team running maintenance while the core team charges ahead on the next release. If the 2.0 team fixes something those fixes are likely pushed up to the 2.1 team. If the 2.1 team finds or fixes something it can depend on whether the 2.1 team's fix will fit readily into 2.0 or not. For example a fix to 3G reception by the 2.1 team would almost certainly NOT be retrofitted into 2.0.
This being said certain assumptions can be made:
2.1 is the update we've been waiting for. 3G, Keyboard lag etc.
2.0.1 and 2.0.2 are not and any 2.0.x release won't be. 2.0.2 probably fixed a major bug or security hole discovered internally in one of the deep libraries. When its dissected (if it is) its likely that it'd be found to have one or two core libraries that were changed and that's it (remember 1.0.2 - another security fix)? This also makes sense as to why Apple isn't publishing the specific fixes because they don't want to publish an undocumented security hole or point hackers in a direction.
2.0.2 wasn't planned which supports the security fix theory. If it wasn't planned it wouldn't have come out just a few days after beta 4 of 2.1 was seeded. 2.1 is due EOM or End of next month. Either way its due soon. I believe its EOM and that's why they pulled push notifications. 4-5 betas is more than enough. Given this whatever was in 2.0.2 was important enough for a release to be done with haste (again lending itself to security theory).
What's this mean for us? Sigh more waiting for the 3G reception issue to be fixed, the keyboard lag, etc to be fixed. Hopefully in the next week we'll get it...
I agree that 2.1 is the likely hope for 3G problems. I also wonder if 2.0.2 is being released in association of the worldwide launch on Aug. 22 in some additional countries?
Wirelessly posted (iPhone: Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_0_2 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5C1 Safari/525.20)
Things are generally snappier, but it's 2pm and my battery is down to around 40% already, with the same normal usage, I would normally be on 70%. Anyone else getting battery performance change?
Things are generally snappier, but it's 2pm and my battery is down to around 40% already, with the same normal usage, I would normally be on 70%. Anyone else getting battery performance change?
I guess it bears repeating again ... this is a x.x.2 release, and as such you can expect only incremental improvements. No doubt there are some bugs that have been fixed, but certainly not all and probably more remain unfixed than fixed at this point.
Wait it out. This is the consequence of being an early adopter. It will improve and Apple will iron things out. There is too much at stake for them not to get it fixed. If you can't handle a slightly-buggy device for a short time, then you shouldn't have made the purchase but should have waited.
I will take the 3G iPhone in its current state over anything else available right now because for all its faults, I still really like the device and know it will get better.
Wait it out. This is the consequence of being an early adopter. It will improve and Apple will iron things out. There is too much at stake for them not to get it fixed. If you can't handle a slightly-buggy device for a short time, then you shouldn't have made the purchase but should have waited.
I will take the 3G iPhone in its current state over anything else available right now because for all its faults, I still really like the device and know it will get better.
More 3g Bars in my house and at work. Seems to be a eaiser transation from Edge to 3 G. The one bar 3 g is no longer a issue switches to Edge, which in my opinion is a vast improvement.
I can tell you that a guy at my office, same general location updated and no change , in fact his became a slug after the update.
I can tell you that a guy at my office, same general location updated and no change , in fact his became a slug after the update.
After a day or so, this is what I'm noticing:
I dunno ... a couple more days to know for sure.
- Contacts seems much better (hopefully this stays like this)
- Typing seems much better (in SMS, at least - hopefully this stays like this)
- Safari seemed a tiny bit more stable (though my stability was never too bad)
- Landscape rotation animation seems smoother (hopefully this stays like this)
I dunno ... a couple more days to know for sure.
Previously, if Location Services was on in General settings, coordinate dependent applications would always demand a user confirmation to fetch positional data.
Now, permission is not required unless Location Services is off.
(at least for a first gen iPhone)
Now, permission is not required unless Location Services is off.
(at least for a first gen iPhone)
I have not read all the responses so forgive if mentioned already.
Gen1 phone, no issues with update or backup. I did it at hope and when I got to work this morning I did a Sync. Took about a minute compared to about 5 it was taking. It started with the backup then calander and contacts. I made a change in Outlook and wanted to update the phone. On this the second sync it did not do the backup it normally was doing, it just went to sync and was done in a few (maybe 8 seconds). I only changed 3 contacts. still just important to not I thought that it did not go through the backup as it had been.
Gen1 phone, no issues with update or backup. I did it at hope and when I got to work this morning I did a Sync. Took about a minute compared to about 5 it was taking. It started with the backup then calander and contacts. I made a change in Outlook and wanted to update the phone. On this the second sync it did not do the backup it normally was doing, it just went to sync and was done in a few (maybe 8 seconds). I only changed 3 contacts. still just important to not I thought that it did not go through the backup as it had been.
I used to get 0-1 bars (of anything) in my office on the 20th floor in Manhattan, and now I'm getting about 4 bars of edge, which I'm very happy about.
I haven't had much time to play around with other things, but in general I'm also seeing "snappier" everything.
I haven't had much time to play around with other things, but in general I'm also seeing "snappier" everything.