Yes, you have to remember, not everyone owning a 3G phone is having problems. I have two white 3G phones and have really experienced very few problems. I have no lag, no crashes, apps always open and no dropped calls. MY 3G works in 95% of my area, the few blocks were it doesn't is clearly marked on AT&Ts coverage map.
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.
Apple Event Sept 9th - New iPhone Firmware & Push Notifications?!
- Thread starter jw nyc
- Start date
- Sort by reaction score
Yes, you have to remember, not everyone owning a 3G phone is having problems. I have two white 3G phones and have really experienced very few problems. I have no lag, no crashes, apps always open and no dropped calls. MY 3G works in 95% of my area, the few blocks were it doesn't is clearly marked on AT&Ts coverage map.
I am sure that we will see some sort of update shortly after the announcement, and that will probably include background apps and other things that Jobs promised, but I am more interested in there being another bug patch than I am with those other features that could be added. If they throw in this extra support and features, then there are just more areas for it to be buggy. I almost kind of hope that they say that it will be released by the end of the month so they can spend time on the bug patches.
from everything I've read, it took eight months for the firmware to get completely stable for all users of the original iPhone.
I also have had no problems, save the occasional Safari screen jump or crash. I realize there are people with problems, but they are in the minority, not the other way around.
I'm looking forward to whatever new features 2.1 brings.
But the problem is that what is working terrific for you isn't working terrific for everyone else that is at it, which brings us back to the original problem: STABILITY. If it isn't stable, why update to it? If a new bridge over a chasm was poorly built, and had people fall through it to their death from the holes in it, would you cross it just because it was there?
Simple logic here. You'd wait until it's fixed before taking that bridge, or updating the phone. So me being part of the problem? Your logic is flawed, as a certain Vulcan would say.
BL.
For what it's worth ...
I wasn't having all that many problems on my 2.0.2 upgraded 3G. HOWEVER, I did a full, super clean Restore to 2.0.2 the other day ("factory fresh") ... and now I get WAY more of the problems people list here now.
Again, FWIW.
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)
Do you see Steve? Do you see what all these issues are doing to us? How crabby we've become? How antsy we are for 2.1?
No pressure...
Do you see Steve? Do you see what all these issues are doing to us? How crabby we've become? How antsy we are for 2.1?
No pressure...
I'm not saying I buy off on the explanation that Apple/AT&T has given for the problems with 3G or that 2.0.2 resolves those problems (I, like some of the other posters, am not having any problems), but your logic is flawed in that a new bridge isn't being built, this is an attempt to fix the existing bridge.
And if you continue on that line, if you are trying to fix the existing bridge over the chasm but people who are using the bridge keep breaking bridge supports every time they use it, how is the bridge going to be usable by everyone?
Just sayin...
You're right, it is an attempt at fixing an existing bridge, but why would I want to risk going across that broken bridge while it's being fixed? Wouldn't it be better to wait until the bridge is fixed before attempting to use it?
And to continue on that, why introduce a new feature to a broken bridge (like a new level (think San Francisco/Oakland Bay Bridge) ) while attempting to fix the existing bridge? It's asking for more problems on the existing bridge, rendering it less usable for everyone?
So, fix the existing bridge, get it stable, then add on to it.
BL. (who is an engineer for a multi-billion dollar company)
So are you saying you aren't using your iPhone (I assume it's a 3G), and I mean not using it at all? Because if you are using your iPhone and it is a 3G, you are using the bridge and if there is any truth to Apple's/AT&T's claims as to the cause of the problem, then you are one of the people that are using the bridge and damaging it at the same time.
I don't disagree with this. I think the first thing Apple needs to do is focus on getting the bugs fixed in the current release. Now with that said, if they can fix it and upgrade it at the same time, then more power to them. They wouldn't be the first to manage to fix something and upgrade it at the same time.
If I'm not mistaken Apple recently took out the Push Notification API's from the latest beta release of 2.1; if that's the case and still remains true, it's highly unlikely that we will be seeing 'Push Notification' support added as part of the 2.1 update.
Also, coming from a software engineering stand point, and solely my opinion, I find it highly unlikely that Apple will tackle all of the defects plaguing 2.0. There are just too many of them and not enough time; two months may seem like a long time, but in reality most of these bugs are buried deep inside the OS and are not found and fixed easily.
My guess for 2.1: They stop Apps from crashing; they fix the ALoD bug, they fix keyboard lag (completely this time), they'll hopefully get stability back to 1.1.4 levels, and if at all possible they will fix the 3G issue (if it is software related). Those bugs alone, along with QAing will pretty much eat all of their development time and resources -- but we shall see.
Anyone expecting copy and paste should keep dreaming; same goes for MMS.
Also, coming from a software engineering stand point, and solely my opinion, I find it highly unlikely that Apple will tackle all of the defects plaguing 2.0. There are just too many of them and not enough time; two months may seem like a long time, but in reality most of these bugs are buried deep inside the OS and are not found and fixed easily.
My guess for 2.1: They stop Apps from crashing; they fix the ALoD bug, they fix keyboard lag (completely this time), they'll hopefully get stability back to 1.1.4 levels, and if at all possible they will fix the 3G issue (if it is software related). Those bugs alone, along with QAing will pretty much eat all of their development time and resources -- but we shall see.
Anyone expecting copy and paste should keep dreaming; same goes for MMS.
Oh no.. I use my 3G iPhone, but after hearing the problems that people were having with 2.0.1 and 2.0.2 being WORSE than 2.0, I'm staying on 2.0 where I have some decent service than updating to worse service/coverage to no service/coverage at all. 3G is completely shut off and will remain so until it's all fixed (hopefully in 2.1). I can live with the lag (it isn't too much of a lag), long backup/sync times (I'll sync overnight), I don't use push, and luckily, I haven't had any apps crash.
I see where you're coming from, though. But jumping up to 2.0.1 or 2.0.2 definitely isn't the answer to all of the problems, so why update to those, when it's hit/miss?
BL.
Aye... I had absolutely zero problems with 2.0 & 2.0.1. They both worked flawlessly except for the long backup issue. However, the moment I upgraded to 2.0.2 I began having every single issue everyone else is complaining about (sans dropped calls.) So, I don't blame the people that do not want to upgrade to 2.0.2. In my case it fixed nothing and broke... well... virtually everything. If I could I would go back to 2.0 ideally or 2.0.1 if I could. 2.0.1 was a little laggy but not bad. I'm really hoping new firmware that actually works (and preferably one that doesn't break NetShare) very soon. I got the iPhone because I was sick to death of my Blackjack that was super laggy and now that too has turned into a laggy mess. I still love it to death and it's the best phone I've ever used, but ya... these are real problems that need to be addressed fast.
That said, I could care less about more/new iPods. New MacBooks would be interesting especially if they include a BD drive. But ya... what I really want is a little itty bitty piece of software that makes the phone just work as it is supposed to.
That said, I could care less about more/new iPods. New MacBooks would be interesting especially if they include a BD drive. But ya... what I really want is a little itty bitty piece of software that makes the phone just work as it is supposed to.
Because according to the Roughly Drafted article linked earlier in the thread, at least part of the problem with 3G reception is that the earlier (pre-2.0.2) firmwares demanded too much power from the 3G masts when a lot of iPhones are connected to the same cell. This explains why not everyone has been having issues (and not all the time) and why issues seem commoner in certain locations (where there are more iPhones). If you don't update, your phone is still causing the problem and holding you and everyone else back from getting a solution. Maybe you should read the article and update?
Here's my guess; Because you're an idiot who doesn't understand the 3G problems and instead of educating yourself and helping to resolve them, you flame things you don't understand on a message board.
It's funny cuz it's true.
Aye, but there's one thing you missed from my post:
bradl said:
I'm not using 3G because I did read the article. I am not updating because conserving power from 3G use (which I am not using) is a small price to pay for the other problems that I mentioned here and those I didn't mention. I'd rather keep it off so I don't consume the power, and dealing with the other problems like I said before. Interim fix until the problem(s) are truly fixed.
BL.
Here's my guess; Because you're an idiot who doesn't understand the 3G problems and instead of educating yourself and helping to resolve them, you flame things you don't understand on a message board.
this is quite funny, because you assume that I haven't read anything here, haven't made the decision I made because I haven't read anything, and you think I'm a total n00b.
You know what happens when you ASSume, no?
I completely understand the 3G problems, because I read a lot more than you realize. You assume I'm using the 3G iPhone for the 3G. You assume wrong. You assume I have no idea what I am talking about despite being an 15+ year sysadmin and systems engineer.
You assume wrong.. but it isn't as if I need to justify what I do to anyone here. This is just a simple board.
Apple's claim of helping to resolve 3G issues by updating and conserving power on the antennae is no solution for the lag, crashing apps, sporadic reboots, or ages long backups/syncs, is it? If you don't use 3G because you don't want to cause the problems everyone else is having with 3G, aren't you taking yourself out of that equation?
3G is causing dropped calls/poor reception because of using too much power with 3G antennas. quick fix: don't use/turn off 3G. longer term fix: fix the software and have everyone update.
I'll give everyone the latter. 2.0.2 has the update, but it doesn't solve the rest of the problems, and causes more of them, and doesn't work for everybody. So why update to a total crapshoot, when I can live with some of the problems, and avoid the 3G one by not using 3G at all?
This isn't theoretical physics.. just common sense.
BL.
Thank you! I'll continue the bridge metaphors. If people have decided that the right-side (3G) of the bridge is broken and all the traffic uses the left-side (2.5G) despite being told that the right-side has been repaired with improved metal supports, the engineers cannot be sure that the new supports have solved the problem. As the problem occurs when 90% of traffic is using that side.