Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The answer to your question, which seems to have flown completely over your head, is that there is no link at all. Zero. Zilch.

The answer to my question has been answered and only one person understood what I was asking. If anything flew it wasn't in this direction.
 
The answer to my question has been answered and only one person understood what I was asking. If anything flew it wasn't in this direction.


To quote an analogy, it's like you believe 1+1 = 3, and ask that question here hoping that someone will tell you that yes, the answer is 3, regardless of how wrong it is.

Numerous people are here telling you that no, the answer should be 2, but you aren't willing to accept this as an answer because it's not the answer you want to hear. Instead, you choose to believe the one person whose answer could not be further from the truth.

Regardless, i guess this thread is pretty much done. You have made your stance clear, and at the end of the day, I guess it's really up to you to decide who you wish to believe. I just hope that his knowledge serves you well, and that this doesn't lead you to form an erroneous conclusion about iOS or the iPhone in future. :)
 
To quote an analogy, it's like you believe 1+1 = 3, and ask that question here hoping that someone will tell you that yes, the answer is 3, regardless of how wrong it is.

Numerous people are here telling you that no, the answer should be 2, but you aren't willing to accept this as an answer because it's not the answer you want to hear. Instead, you choose to believe the one person whose answer could not be further from the truth.

Regardless, i guess this thread is pretty much done. You have made your stance clear, and at the end of the day, I guess it's really up to you to decide who you wish to believe. I just hope that his knowledge serves you well, and that this doesn't lead you to form an erroneous conclusion about iOS or the iPhone in future. :)

so far from the mark.

if I asked a question does 1+1 = 3

And I knew it didn't.

And someone answered no it doesn't = 3

I'd be content.

If someone answered explaining how the numbers are displayed on the screen and all that mumbo jumbo which is irrelevant to the question ...

well you get the point.
 
so far from the mark.

if I asked a question does 1+1 = 3

And I knew it didn't.

And someone answered no it doesn't = 3

I'd be content.

If someone answered explaining how the numbers are displayed on the screen and all that mumbo jumbo which is irrelevant to the question ...

well you get the point.



No, I don't. But as I said, you are free to believe what you wish.
 
so far from the mark.

if I asked a question does 1+1 = 3

And I knew it didn't.

And someone answered no it doesn't = 3

I'd be content.

If someone answered explaining how the numbers are displayed on the screen and all that mumbo jumbo which is irrelevant to the question ...

well you get the point.
You have completely twisted his explanation :eek:
 
You have completely twisted his explanation :eek:

He completely twisted my topic so it's only fair.

I understand my question and I inderstand the answer provided. Some just don't understand the question hence they provide a wrong answer. Then they say I don't understand my question and say that's why I don't understand their answer. But I do understand their answer.
 
Last edited:
He completely twisted my topic so it's only fair.

I understand my question and I inderstand the answer provided. Some just don't understand the question hence they provide a wrong answer. Then they say I don't understand my question and say that's why I don't understand their answer. But I do understand their answer.

As you wish mate
 
To my knowledge, if the phone runs out of memory an app is killed and will have to restart when you the next time you open it.

What I don't know is if whatever background refreshed data is preserved in the event an app was killed, or when you launch it, it forces a full refresh regardless of the background refresh setting.
 
To my knowledge, if the phone runs out of memory an app is killed and will have to restart when you the next time you open it.

What I don't know is if whatever background refreshed data is preserved in the event an app was killed, or when you launch it, it forces a full refresh regardless of the background refresh setting.

Good point thanks.

I was reading another site where they said background app refresh will refresh an app in the background as you are using another app so when you switch to the app it will be ready to go with the latest data, they said this is a smooth experience not seen on other platforms.

I guess if it dumps the background info it gained then its pointless.
 
Improve and make up for the lack of ram? Less reboots etc? When it's switched on?

As others have said, it has nothing to do with either. Background App Refresh makes up for battery, CPU and network time, not RAM.

In order for BAR to work the app has to be in ram (or cached) and has nothing to do with getting around smaller ram sizes. If BAR were to run and then app was dumped out again it would have solved nothing since it would need to refresh again when it was reloaded anyway. It's only really useful for apps that are already in ram, so it being there to get around the ram issue is 100% pointless.
 
As others have said, it has nothing to do with either. Background App Refresh makes up for battery, CPU and network time, not RAM.

In order for BAR to work the app has to be in ram (or cached) and has nothing to do with getting around smaller ram sizes. If BAR were to run and then app was dumped out again it would have solved nothing since it would need to refresh again when it was reloaded anyway. It's only really useful for apps that are already in ram, so it being there to get around the ram issue is 100% pointless.

Sure but if people are opening apps and they are loading the info some would say thats a lack of ram. That was a point I was making. That if they had background app refresh on and the data didn't load and the app was ready to go they would believe the RAM was adequate. Like I've said not everyone understood the question.
 
Sure but if people are opening apps and they are loading the info some would say thats a lack of ram. That was a point I was making. That if they had background app refresh on and the data didn't load and the app was ready to go they would believe the RAM was adequate. Like I've said not everyone understood the question.

People didn't understand the question because you were hypothesizing an assumption that people might believe that is in its own right incorrect.
 
People didn't understand the question because you were hypothesizing an assumption that people might believe that is in its own right incorrect.

I thought you read the forums :rolleyes:;)
 
I thought you read the forums :rolleyes:;)

Same. # seriously though, you are assuming people are asking a question that is an if itself an incorrect question. You are thinking that BAR is about memory vs multitasking and are assuming random people will blame the lack of ram (as if most people know ram anyway) on the app reloading, when the root cause is a data refresh causes by the app coming into the fore-front.
 
Last edited:
As others have said, it has nothing to do with either. Background App Refresh makes up for battery, CPU and network time, not RAM.

In order for BAR to work the app has to be in ram (or cached) and has nothing to do with getting around smaller ram sizes. If BAR were to run and then app was dumped out again it would have solved nothing since it would need to refresh again when it was reloaded anyway. It's only really useful for apps that are already in ram, so it being there to get around the ram issue is 100% pointless.

That's basically what we are trying hard to make him understand since the beginning.
But he doesn't like that answer ..... :D
 
Sure but if people are opening apps and they are loading the info some would say thats a lack of ram. That was a point I was making. That if they had background app refresh on and the data didn't load and the app was ready to go they would believe the RAM was adequate. Like I've said not everyone understood the question.

You apparently don't understand what you are asking at all, this is 100% wrong.
 
As others have said, it has nothing to do with either. Background App Refresh makes up for battery, CPU and network time, not RAM.

In order for BAR to work the app has to be in ram (or cached) and has nothing to do with getting around smaller ram sizes. If BAR were to run and then app was dumped out again it would have solved nothing since it would need to refresh again when it was reloaded anyway. It's only really useful for apps that are already in ram, so it being there to get around the ram issue is 100% pointless.

That's basically what we are trying hard to make him understand since the beginning.
But he doesn't like that answer ..... :D

If BAR were to run because the OS knew you were going to use the app and the app was not dumped out again it would appear smoother.

Thats basically wha....

forget it. :D
 
You apparently don't understand what you are asking at all, this is 100% wrong.

How is it wrong?

If BAR loads an app data because it knows your going to use it its got all the data when you open it,

compared to opening the app and it reloading cause it needs the upto date data.

To some users it would/could appear to them as a lack of ram.
 
All his arguing over a feature that actually does not work! Any app I open,,,be it BBC news, Paper (the Facebook app), Twitter, Zite etc etc always refreshes when I open it.
If you look quick enough the data/news streams will be old (yesterday's Zite news for example) until they are refreshed - either by me or an auto update. They definitely don't update in the background so the latest news is there immediately when I open the app. For example, I open the BBC News app almost every hour and it still does not background refresh, it simply updates if and when I open the app "in the foreground". Isn't the device supposed to learn? All my apps have background refresh on (that support it) and even a setup as new fails to fix the issue. Twitter supports background app refresh but it always loads when the app is open. Just before that update my stream is a day old - as I check it once per day. It will prob never work correctly.
 
All his arguing over a feature that actually does not work! Any app I open,,,be it BBC news, Paper (the Facebook app), Twitter, Zite etc etc always refreshes when I open it.
If you look quick enough the data/news streams will be old (yesterday's Zite news for example) until they are refreshed - either by me or an auto update. They definitely don't update in the background so the latest news is there immediately when I open the app. For example, I open the BBC News app almost every hour and it still does not background refresh, it simply updates if and when I open the app "in the foreground". Isn't the device supposed to learn? All my apps have background refresh on (that support it) and even a setup as new fails to fix the issue. Twitter supports background app refresh but it always loads when the app is open. Just before that update my stream is a day old - as I check it once per day. It will prob never work correctly.

I have no idea what the learning mechanic is.

An example of when BAR has been useful for me. I go to the toilet, enter the cubicle and start to use my smartphone while going about my business (don't judge me). There is no network in the toilet. Under normal circumstances, your app can't pull any data. However, thanks to BAR, I find that Tweetbot has preloaded some tweets from earlier, but I at least have something to read in the meantime.

Another example of when BAR is useful - I use the overcast podcast app, and it downloads the podcasts overnight as I am sleeping (due to my timezone, new podcasts typically come after midnight). So when I wake up the next day, the podcasts are already on my iPhone and ready for listening.

Given that iOS typically suspends minimised apps to preserve battery life, I believe this is more about mimicking the behaviour of Android phones where apps are allowed to continue running in the background (which can be useful, like when dropbox is uploading files), but can drain battery life like crazy. It's Apple trying to find that sweet spot between convenience and battery life without compromising either too much. :)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.