I would say the wait was worth it, not having to use a patched firmware every time a new version came out is a definite plus. Sure, there is still issues with official application stability on 2.0, MobileMe is sometime sketchy (I’ve had pretty good luck since launch, colleagues not so much). and bugs in the firmware itself where kind of downers.

All is not rosy in the land of iPhone in Canada, and from the reading and conversations I’ve had, I’m not alone. Many on Rogers and Fido have probably experienced this when using Safari or other apps that use the data network:

Right when the phone launched, everything was gravy, pages loaded fast (far faster than when I was on Edge on my old phone), and everything was awesome in the land of iPhone. After a week or so, I started to get “kCFErrorDomainCFNetwork error 302″ every so often, I ignored it as I see that happen in Safari when I’m browsing on Macs. Just refresh once or twice and it will usually load the page.

It started to happen more often, so I decided to do some Googling. Lo and behold, stuff popped up on Howard Forums, a gigantic cellular enthusiasts site. Others have reported the same problem, and Rogers support has tried to  give solutions.

Doing some further experimenting, I’m pretty sure it’s not the phone that’s the problem. Every other person that I work with in Calgary that I’ve talked to so far is experiencing the same issue. Add to that I did some tests throughout the day, around 5:30AM MST on the way to work, no problems. Pages load up snappy, no issues with timeouts. Midday and on the way home, it pop’s up one in every two tries to request a page. This leads me to believe it’s a traffic congestion issue on Roger’s end of things. 

Fingers crossed this gets fixed soon, if it is indeed an issue of network congestion, it’s pretty obvious that it should have been addressed 

In any case I’ll do more Googling to see what I can find, just logging my progress.