Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The only application that does this on my iPhone is Safari; it just drops out once and a while for no apparent reason while I'm browsing via Edge or WiFi.

Apple has been great at working out this type of problem in Version 1 products since I started using Apple products. Of these (three Macs, two ATVs, one Airport Extreme router, two iPods and now one iPhone all purchased since last September) a number of them were Version 1 products. I have had less problems with these than most of the established PC products that I have owned in the past. Therefore, I am sure that within a very short time the iPhone will be an even greater product than it is right now.

Dave
 
I noticed the exact same problem last night (using Wifi, not Edge.) Interestingly, last night was the first time I had the iPod close to full. Until then I only had 3 or 4 GB on it, but then I converted some video files to the iPhone format and suddenly my iPod was close to full. I was listening to tracks from a CD, and I started surfing the web. Lo and behold it crashed. Several times. Did it again this morning.

I'm sure it's a concurrency issue. Probably the iPod trying to do something to the screen and of course it's "not there" if you're in the browser. They'll figure it out.

It doesn't make me think I mad a bad purchase. Quite the opposite. I have a phone they can fix with software and send me new versions, so I'm quite happy! :)

be well

t

PS. To those giving Katie a hard time, please pack it in. Your entitled to your opinion but a) This is a post about the issue she had with the iPhone, not your opinion of how she writes and b) The whole point is to get and end users opinion, so if you don't like what she says then fine, you're a different type of end user. No need to be mean about it!
 
Ahh yeah, the power cycling did the trick! (For now, anyway. Hehe.) I also had this weird message - "Collision" underneath the time when it came back from sleep, but powercycling it fixed that too. I gotta say I am still pretty impressed with it!

Edit: I think "Collision" might have been a song name - maybe it was stuck in ipod mode (even though it wasn't currently playing.) Weird, oh well.
 
great, funny post!! i love the part about the apple manager telling you not to use EDGE. so is apple putting WIFI nationwide?

my ipod paused once while listenning to music and searching google maps via EDGE. This was Saturday morning, a few hours after i bought it. It hasn't done it again since.
 
100%

No problems. Great Device. Lotsa bad users out there. Hopefully some updates coming soon to make everyone happy.

Yeah, I'm a bad user because iPod crashes when I try to run Safari at the same time :rolleyes: Really how can you turn the presence of an obvious bug causing application instability in a version 1 product into user stupidity/error?!
 
Interestingly, last night was the first time I had the iPod close to full. Until then I only had 3 or 4 GB on it, but then I converted some video files to the iPhone format and suddenly my iPod was close to full. I was listening to tracks from a CD, and I started surfing the web. Lo and behold it crashed. Several times. Did it again this morning.

I'm sure it's a concurrency issue. Probably the iPod trying to do something to the screen and of course it's "not there" if you're in the browser. They'll figure it out.

Hmm, how full was it?

This is an interesting observation about the iPhone. It's an ipod and a phone, yes, but it's also a really small, somewhat full-blown computer. It uses OS X. I didn't think about it, but this is a real problem on a device with limited storage. I imagine that, as you can't really close apps, after a few hours of usage the thing can get pretty high RAM usage (I wonder how much it has), and it probably pages out (like OS X on my MBP). Now, page files expand geometrically in OS X: first your computer generates a 64 MB page file. when it fills up, it expands to a 128 MB file. Then to a 256 MB file, then 512 MB, etc.

I don't know if they changed how this works on the iPhone, but you can definitely end up with a significant amount of disk space occupied by a (possibly mostly empty) set of pagefiles. Check this out. On my MBP with 3 GB of RAM, I have a Parallels VM up (560 MB of RAM allocated to it), Aperture, Photoshop CS3, and NetBeans. It's using 512 MB of swap space after a few minutes...

looking in /var/vm, I see 2 64 MB swapfiles, a 128 MB swapfile, and a 256 MB swapfile, for a total of 512 MB. the next swapfile will be 512 MB, if it grows.

That's OS X with 3 GB of RAM and some pro apps. now imagine OS X on an iPhone with 64-128 MB (I would guess) of RAM and running safari (notorious for memory leaks) and dashboard widgets (often RAM hogs), an iPhoto-like application, an iTunes-like application for the iPod portion....

I can really imagine that if you have only 1 GB of memory free on your iPhone it may become very unstable. I would think with an application like safari, which I have personally seen taking up over 600MB of RAM, Apple is going to struggle with making iPhones run smoothly with "low" disk space. Hopefully this will drive them to put a leash on the insane memory usage of Safari.
 
I've found that the crashes usually occur on the same exact pages. If I navigate to a very similar page on the same site (as you would do on a messageboard when viewing a different thread), the crash no longer happens. Go back, and the problem resurfaces. I'm guessing the problem is that the pages are too large...?
 
Yeah, I'm a bad user because iPod crashes when I try to run Safari at the same time :rolleyes: Really how can you turn the presence of an obvious bug causing application instability in a version 1 product into user stupidity/error?!

Hahah, yeah I chuckled at that... he's obviously way better at us when it comes to using the iphone. :rolleyes: I do wonder when they're going to announce the first update though.
 
long story short, that problem can be solved (most of the time, for me) by shutting down my phone, then powering it back on. it takes about 45 seconds to do, and it quits out of all the apps.

I think holding down the main button (the home screen one) for x? seconds will quit the current app. (Just like holding the top one gets you the power down prompt)
 
Crash Theory

There's a theory on the Apple support discussion pages that the crash is caused by a bug in the way that Safari handles Javascript. (They've found that it happens most often when they frequent Javascript heavy pages.)

Some users have indicated that they've been able to stave off the crash by going into system settings and turning off JavaScript.
 
Restarting the iphone

I ran into some slowdown when on edge and kind of figured out a solution. When you open apps they stay open in the background for the most part and when you have too much web stuff happening, it could potentially be an issue. Try going to some of the programs you have open that may be hogging the system and press and hold the home key to quit, or hold the sleep button and the home button at the same time to restart the system. It is a soft reset so you don't have to worry about losing any data.

I'm not a tech guy, but it seems to work for me. Don't know if this will help :eek:
 
Hmm, how full was it?

Only a few hundred meg free.

Could be a swap file thing. Thing is, we don't know as of right now how much real memory the thing has and how the flash memory used for the storage of media is used when that runs low.

Look out for an update to the OS in the next few days, where it quietly unloads unused apps in the background! :)

be well

t
 
I turn on The Beastie Boys and...

<snip>

... people turning up the display iPod speakers all the way up because that wretched rap music just wasn’t quite loud enough ...

Forgot to mention this in my previous (on topic :) ) posts, but am I the only one that remembers when The Beastie Boys *were* the "wretched rap music"? :D
 
Today I experienced my first problems with my iPhone. Thing wouldn't respond when I swiped my finger across to unlock it. This was embarrassing because I was trying to show it off to people. Agh!!! I realized, though, that since I've had the iPhone I'd never turned it off, had just had it in sleep mode.... This morning I had done a lot of new synching, added a bunch of new photos and such. Time to turn my baby off! I turned it off and then back on again and thankfully have had no issues with it since. I will just have to remember that just as I do with my computers to refresh RAM and such, I will need to do the same with my iPhone since applications are NOT closed when we move on to something else in the device..... I am pretty amazed, though, that the iPhone didn't have issues until today, more than a week since I'd bought it and started using it.

I loveloveloveLOVE my iPhone!
 
I only had one problem with my iPhone yesterday, the first day I used it. I went to use it at work, pressed the home button, nothing happened. Pressed the sleep button, nothing happened. Tried plugging in some headphones, nothing happened. The iPhone appeared dead. I drove to my house and jumped on the net and found out how to reset the phone and that worked. Since then, o problems.

I also tried browsing the net using Safari with my WiFi connection and no crashes, I was able to surf and listen to music at the same time.
 
My iPhone also crashes during heavy use. Once it starts crashing, it's very easy to make it keep crashing. Rebooting the phone-- holding down the sleep/wake button and sliding the red slider-- mostly fixes the problem.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.