Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It's closed even before you get to that step. (Unless it's playing music or something.) But if it's not currently doing something then there's no reason to do that.

I think people are getting confused as to what you are saying.

What I think Small White Car is saying is that even though Pandora is playing music in the background, it doesn't mean it's actually open. It's just using the audio stream from the application.

Apple didn't really make this clear in their demo. Whether you switch applications using the new multitasking dock or hit the home button once, the music will continue playing.
 
Nokia's and Android's multitasking implementations are MUCH better.

It's quite obvious that multitasking is a bolt on rather than a fundamental implementation.

What is quite obvious is that you have no clue what you're talking about. Although this thread is entertaining.
 
i know that it can give problems to some of the more memory intensive apps. in particular, the gps navigator map app i use tended to start playing up after a while (when i was testing over the past few weeks) - but i noticed i had about 20+ apps all "running" in the background, once i quit most of those the traffic app started picking up my location correctly again.
but i guess that's the case with all multitasking - whatever the device, there's always going to be a finite amount of memory available.

i haven't ever been aware that it's killed inactive background apps though. in all my testing, i think they always stayed open until i killed them. that might be a feature of the latest full release perhaps?
 
I think people are getting confused as to what you are saying.

What I think Small White Car is saying is that even though Pandora is playing music in the background, it doesn't mean it's actually open. It's just using the audio stream from the application.

Apple didn't really make this clear in their demo. Whether you switch applications using the new multitasking dock or hit the home button once, the music will continue playing.

Well, you're correct about that, but my main point is actually about Pandora when there's not music playing in the background.

Some people seem to think you have to go "close it with the little x" at that point. But if it's not playing music in the background then that's 100% unecessary. There's no reason to do anything in that case.
 
I'm pretty sure you can completely end a previously closed App in the multitasking bar. You bring up the bar, you hold the app icon, and then it shakes and you click the red square. Boom, app killed. But I don't know that there's many reasons to actually kill the app...option is there, however.

I'll admit though, it took me a little while to find where the orientation lock feature was. Also, at that same time, I figured out how to still use double click of home button for iPod. I was getting worried for a bit about that one. :p

Edit: Oops, looks like I was late to the app-killing party *looks to post above me*
 
Its not really "running" in the background. Majority of those apps are in a freeze state and don't take up ANY memory. The only things that can be "running" are apps that utilize those 7 API's that Apple announced earlier this year. The multitasking bar is just a quick way to switch apps if you are in the middle of something like a phone call or receive an SMS.

It's funny how naive people are about this whole concept.


This. Come on people, l2read.
 
The OPs mistake was in thinking Apple actually added real Multitasking. Noob!

Multitasking is just doing more than one thing at a time. In that sense this is real multitasking.

What they didn't add was the ability for apps to fully run in the background such as AIM. What they did instead is allow apps to spawn multitasking processes in the CPU to continue doing things while "closed".

IMO the OS handles the hand off pretty well from app running, to app paused, to app multitasking process running and back.
 
You people need some reading comprehension, where in my post did I complain about multitasking draining battery or RAM?

The applications freeze, I know, and it's kind of a pain in the ass to go deep into the application menus or settings and then having to return to that messy state.

I like to close out applications completely so the next time I run them I start from the main screen... and doing that everytime is annoying, like I described in the original post.
 
You people need some reading comprehension, where in my post did I complain about multitasking draining battery or RAM?

The applications freeze, I know, and it's kind of a pain in the ass to go deep into the application menus or settings and then having to return to that messy state.

I like to close out applications completely so the next time I run them I start from the main screen... and doing that everytime is annoying, like I described in the original post.

They shouldn't freeze. In fact, very few of them should even save their state right now unless they specifically update for it. You may be having other issues...
 
You people need some reading comprehension, where in my post did I complain about multitasking draining battery or RAM?

The applications freeze, I know, and it's kind of a pain in the ass to go deep into the application menus or settings and then having to return to that messy state.

I like to close out applications completely so the next time I run them I start from the main screen... and doing that everytime is annoying, like I described in the original post.

Agreed that it is a matter of annoyance, clutter and clumsy to truly close an app completely. Not a performance issue.
 
They shouldn't freeze. In fact, very few of them should even save their state right now unless they specifically update for it. You may be having other issues...

There are apps written for the older OS that will save their current state (roughly) in order to return you to where you were previously. It was encouraged to do this when the SDK was launched.
 
To close an app in the multitask tray - touch and hold on an icon in the tray to get the icons to jiggle (like moving apps around on the springboard). Click on the 'x' to completely close the app from the freeze state.
 
To close an app in the multitask tray - touch and hold on an icon in the tray to get the icons to jiggle (like moving apps around on the springboard). Click on the 'x' to completely close the app from the freeze state.

Read the OP please, I know how to close applications, but that implementation gets annoying quite fast and it's slow too, slow process, double tap, press and hold.......

There is no "Exit" button on applications so basically whatever you open, stays opened, and you have to double tap, press and hold, and then close the apps.

In theory multitasking sounded nice, but in practice it's quite annoying.

Nokia's and Android's multitasking implementations are MUCH better.

It's quite obvious that multitasking is a bolt on rather than a fundamental implementation.
 
I'd also like to point out that pre-iOS4, apps would often remember where you were despite the fact that you had exited them. Thus, the only difference here is if the app you exit is actively using one of those 7 APIs. Otherwise, it's exactly the same as before.
 
i know that it can give problems to some of the more memory intensive apps. in particular, the gps navigator map app i use tended to start playing up after a while (when i was testing over the past few weeks) - but i noticed i had about 20+ apps all "running" in the background, once i quit most of those the traffic app started picking up my location correctly again.
but i guess that's the case with all multitasking - whatever the device, there's always going to be a finite amount of memory available.

i haven't ever been aware that it's killed inactive background apps though. in all my testing, i think they always stayed open until i killed them. that might be a feature of the latest full release perhaps?

iOS4 kills the oldest app if it runs out of memory.

There are apps written for the older OS that will save their current state (roughly) in order to return you to where you were previously. It was encouraged to do this when the SDK was launched.

Yup. Apple stresses it in the development seminars, but they were limited in attendees, so lots of developers didn't get that info. Good developers would save the states in iPhone 3 already.
 
You people need some reading comprehension, where in my post did I complain about multitasking draining battery or RAM?

The applications freeze, I know, and it's kind of a pain in the ass to go deep into the application menus or settings and then having to return to that messy state.

I like to close out applications completely so the next time I run them I start from the main screen... and doing that everytime is annoying, like I described in the original post.

The reason why people don't comprehend your OP is because you didn't go into detail. All you mentioned is that closing apps is a pain. Your OP made it sound like you didn't know how fast app switching worked and that's why you got the responses you got. Come to think of it, maybe you really didn't know how fast app switching worked and now your trying to cover your ass up.
 
The reason why people don't comprehend your OP is because you didn't go into detail. All you mentioned is that closing apps is a pain. Your OP made it sound like you didn't know how fast app switching worked and that's why you got the responses you got. Come to think of it, maybe you really didn't know how fast app switching worked and now your trying to cover your ass up.

No, I knew how it worked, but in practice I was surprised by how annoying it is going from mess to mess of application menus... wherever you left off.
 
You really didnt expect iOS4 to be true multitasking did you? I hope not. You need an Android phone for that :)
 
The OP's actual complaint has very little to do with multitasking. Just how apps save state. Sounds like a feature request for the developer of the app.

Nokia's and Android's multitasking implementations are MUCH better.

How are they better for the problem you described in your last couple posts?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.