iOS always “resets” my apps after a while when they are minimized. How can I change that?
Example: I'm playing a game and stop for a minute to send a message on WhatsApp. Lock the phone for a couple a minutes, and when I navigate through "frozen" apps and select the game (the game still has the last screen it had when it was minimized), it opens from the splash screen, reseted!
And it doesn't happen only with games. Even Facebook, Twitter, and other apps.
iphone ios
New contributor
add a comment |
Example: I'm playing a game and stop for a minute to send a message on WhatsApp. Lock the phone for a couple a minutes, and when I navigate through "frozen" apps and select the game (the game still has the last screen it had when it was minimized), it opens from the splash screen, reseted!
And it doesn't happen only with games. Even Facebook, Twitter, and other apps.
iphone ios
New contributor
add a comment |
Example: I'm playing a game and stop for a minute to send a message on WhatsApp. Lock the phone for a couple a minutes, and when I navigate through "frozen" apps and select the game (the game still has the last screen it had when it was minimized), it opens from the splash screen, reseted!
And it doesn't happen only with games. Even Facebook, Twitter, and other apps.
iphone ios
New contributor
Example: I'm playing a game and stop for a minute to send a message on WhatsApp. Lock the phone for a couple a minutes, and when I navigate through "frozen" apps and select the game (the game still has the last screen it had when it was minimized), it opens from the splash screen, reseted!
And it doesn't happen only with games. Even Facebook, Twitter, and other apps.
iphone ios
iphone ios
New contributor
New contributor
edited Jan 18 at 6:17
Peter Mortensen
1806
1806
New contributor
asked Jan 17 at 12:22
Marcelo AssisMarcelo Assis
1463
1463
New contributor
New contributor
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
You can‘t change that, only the app developer can (by adding code to handle the unloading of the app and preserving the state). Most games don‘t, unfortunately.
add a comment |
This is actually a common misconception in iOS.
Apps are not "minimized": they are suspended while they're in the background (except in some cases, notably navigation and music apps). Further, resource taxing suspended apps (such as games) are often closed entirely shortly after being suspended so that iOS can reclaim the copious amounts of memory these apps often reserve.
The answer to this issue, as @nohillside mentioned, is that the developer needs to implement functionality to save the state of the game when it is suspended, then restore the suspended state when the app wakes up again.
This can be tricky for many applications, but especially games. So many games simply don't do it.
There is nothing that you can do as a user to change this functionality, as these constraints are enforced upon the game by the phone's iOS operating system, which is in turn constrained by the phone hardware.
add a comment |
From my experience, there was two occasions where apps doesn't keep running(or, in other words, shows splash screen when I launch it again).
First one is that the developer poorly, or even didn't implement suspending for the app. There were some apps that always quits when I press home button, or resets when it was on specific feature. (Although in recent app store I haven't seen one except for some public institution apps that have 1~2 average review)
Second one is hardware limitation - even though the developer properly implemented the suspension feature, iOS sometimes decide to quit it, for various reasons from lack of memory(this is actually major reason that earlier idevices didn't support app suspension on 3G/S era), battery time management.
For first reason, you can write a review on Appstore - it is one of the most impacting reasons for app development progress.
For second reason, well, it is kinda dumb solution but you can purchase a new hardware with more RAM, and it will reduce the possibility of suspended apps halted from iOS(And reduce time for app relaunch). Or, if you're not willing to do so, you can tell iOS to halt some unimportant apps by swiping the app's preview upwards in the multitasking view, possibly reducing the chance of the apps you're actually using getting killed by iOS.
Some of the information contained in this post requires additional references. Please edit to add citations to reliable sources that support the assertions made here. Unsourced material may be disputed or deleted.
I don't know why this answer got a -1 since it suggests an actual solution to the problem and describes it too.
– redbeam_
Jan 18 at 19:43
I don't know how to add additional references since most of the response's reasoning relies on my personal experience. The 3GS part comes from my jailbroken iPod Touch 2G 8GB iOS 3.x, where I tried to background run an app by jailbreaking it only could handle 2~3 background apps due to small RAM (can't remember exact number but it had less than 100MB avail RAM for app tho). Appstore review part comes from my job experience from a startup company(and many developer response from popular app where it apologizes to the negative review). Second solution comes from almost every apple tip community.
– ik1ne
Jan 19 at 2:22
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "118"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Marcelo Assis is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f348837%2fios-always-resets-my-apps-after-a-while-when-they-are-minimized-how-can-i-cha%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can‘t change that, only the app developer can (by adding code to handle the unloading of the app and preserving the state). Most games don‘t, unfortunately.
add a comment |
You can‘t change that, only the app developer can (by adding code to handle the unloading of the app and preserving the state). Most games don‘t, unfortunately.
add a comment |
You can‘t change that, only the app developer can (by adding code to handle the unloading of the app and preserving the state). Most games don‘t, unfortunately.
You can‘t change that, only the app developer can (by adding code to handle the unloading of the app and preserving the state). Most games don‘t, unfortunately.
answered Jan 17 at 12:31
nohillside♦nohillside
51.4k13109150
51.4k13109150
add a comment |
add a comment |
This is actually a common misconception in iOS.
Apps are not "minimized": they are suspended while they're in the background (except in some cases, notably navigation and music apps). Further, resource taxing suspended apps (such as games) are often closed entirely shortly after being suspended so that iOS can reclaim the copious amounts of memory these apps often reserve.
The answer to this issue, as @nohillside mentioned, is that the developer needs to implement functionality to save the state of the game when it is suspended, then restore the suspended state when the app wakes up again.
This can be tricky for many applications, but especially games. So many games simply don't do it.
There is nothing that you can do as a user to change this functionality, as these constraints are enforced upon the game by the phone's iOS operating system, which is in turn constrained by the phone hardware.
add a comment |
This is actually a common misconception in iOS.
Apps are not "minimized": they are suspended while they're in the background (except in some cases, notably navigation and music apps). Further, resource taxing suspended apps (such as games) are often closed entirely shortly after being suspended so that iOS can reclaim the copious amounts of memory these apps often reserve.
The answer to this issue, as @nohillside mentioned, is that the developer needs to implement functionality to save the state of the game when it is suspended, then restore the suspended state when the app wakes up again.
This can be tricky for many applications, but especially games. So many games simply don't do it.
There is nothing that you can do as a user to change this functionality, as these constraints are enforced upon the game by the phone's iOS operating system, which is in turn constrained by the phone hardware.
add a comment |
This is actually a common misconception in iOS.
Apps are not "minimized": they are suspended while they're in the background (except in some cases, notably navigation and music apps). Further, resource taxing suspended apps (such as games) are often closed entirely shortly after being suspended so that iOS can reclaim the copious amounts of memory these apps often reserve.
The answer to this issue, as @nohillside mentioned, is that the developer needs to implement functionality to save the state of the game when it is suspended, then restore the suspended state when the app wakes up again.
This can be tricky for many applications, but especially games. So many games simply don't do it.
There is nothing that you can do as a user to change this functionality, as these constraints are enforced upon the game by the phone's iOS operating system, which is in turn constrained by the phone hardware.
This is actually a common misconception in iOS.
Apps are not "minimized": they are suspended while they're in the background (except in some cases, notably navigation and music apps). Further, resource taxing suspended apps (such as games) are often closed entirely shortly after being suspended so that iOS can reclaim the copious amounts of memory these apps often reserve.
The answer to this issue, as @nohillside mentioned, is that the developer needs to implement functionality to save the state of the game when it is suspended, then restore the suspended state when the app wakes up again.
This can be tricky for many applications, but especially games. So many games simply don't do it.
There is nothing that you can do as a user to change this functionality, as these constraints are enforced upon the game by the phone's iOS operating system, which is in turn constrained by the phone hardware.
answered Jan 17 at 21:00
malexdevmalexdev
30029
30029
add a comment |
add a comment |
From my experience, there was two occasions where apps doesn't keep running(or, in other words, shows splash screen when I launch it again).
First one is that the developer poorly, or even didn't implement suspending for the app. There were some apps that always quits when I press home button, or resets when it was on specific feature. (Although in recent app store I haven't seen one except for some public institution apps that have 1~2 average review)
Second one is hardware limitation - even though the developer properly implemented the suspension feature, iOS sometimes decide to quit it, for various reasons from lack of memory(this is actually major reason that earlier idevices didn't support app suspension on 3G/S era), battery time management.
For first reason, you can write a review on Appstore - it is one of the most impacting reasons for app development progress.
For second reason, well, it is kinda dumb solution but you can purchase a new hardware with more RAM, and it will reduce the possibility of suspended apps halted from iOS(And reduce time for app relaunch). Or, if you're not willing to do so, you can tell iOS to halt some unimportant apps by swiping the app's preview upwards in the multitasking view, possibly reducing the chance of the apps you're actually using getting killed by iOS.
Some of the information contained in this post requires additional references. Please edit to add citations to reliable sources that support the assertions made here. Unsourced material may be disputed or deleted.
I don't know why this answer got a -1 since it suggests an actual solution to the problem and describes it too.
– redbeam_
Jan 18 at 19:43
I don't know how to add additional references since most of the response's reasoning relies on my personal experience. The 3GS part comes from my jailbroken iPod Touch 2G 8GB iOS 3.x, where I tried to background run an app by jailbreaking it only could handle 2~3 background apps due to small RAM (can't remember exact number but it had less than 100MB avail RAM for app tho). Appstore review part comes from my job experience from a startup company(and many developer response from popular app where it apologizes to the negative review). Second solution comes from almost every apple tip community.
– ik1ne
Jan 19 at 2:22
add a comment |
From my experience, there was two occasions where apps doesn't keep running(or, in other words, shows splash screen when I launch it again).
First one is that the developer poorly, or even didn't implement suspending for the app. There were some apps that always quits when I press home button, or resets when it was on specific feature. (Although in recent app store I haven't seen one except for some public institution apps that have 1~2 average review)
Second one is hardware limitation - even though the developer properly implemented the suspension feature, iOS sometimes decide to quit it, for various reasons from lack of memory(this is actually major reason that earlier idevices didn't support app suspension on 3G/S era), battery time management.
For first reason, you can write a review on Appstore - it is one of the most impacting reasons for app development progress.
For second reason, well, it is kinda dumb solution but you can purchase a new hardware with more RAM, and it will reduce the possibility of suspended apps halted from iOS(And reduce time for app relaunch). Or, if you're not willing to do so, you can tell iOS to halt some unimportant apps by swiping the app's preview upwards in the multitasking view, possibly reducing the chance of the apps you're actually using getting killed by iOS.
Some of the information contained in this post requires additional references. Please edit to add citations to reliable sources that support the assertions made here. Unsourced material may be disputed or deleted.
I don't know why this answer got a -1 since it suggests an actual solution to the problem and describes it too.
– redbeam_
Jan 18 at 19:43
I don't know how to add additional references since most of the response's reasoning relies on my personal experience. The 3GS part comes from my jailbroken iPod Touch 2G 8GB iOS 3.x, where I tried to background run an app by jailbreaking it only could handle 2~3 background apps due to small RAM (can't remember exact number but it had less than 100MB avail RAM for app tho). Appstore review part comes from my job experience from a startup company(and many developer response from popular app where it apologizes to the negative review). Second solution comes from almost every apple tip community.
– ik1ne
Jan 19 at 2:22
add a comment |
From my experience, there was two occasions where apps doesn't keep running(or, in other words, shows splash screen when I launch it again).
First one is that the developer poorly, or even didn't implement suspending for the app. There were some apps that always quits when I press home button, or resets when it was on specific feature. (Although in recent app store I haven't seen one except for some public institution apps that have 1~2 average review)
Second one is hardware limitation - even though the developer properly implemented the suspension feature, iOS sometimes decide to quit it, for various reasons from lack of memory(this is actually major reason that earlier idevices didn't support app suspension on 3G/S era), battery time management.
For first reason, you can write a review on Appstore - it is one of the most impacting reasons for app development progress.
For second reason, well, it is kinda dumb solution but you can purchase a new hardware with more RAM, and it will reduce the possibility of suspended apps halted from iOS(And reduce time for app relaunch). Or, if you're not willing to do so, you can tell iOS to halt some unimportant apps by swiping the app's preview upwards in the multitasking view, possibly reducing the chance of the apps you're actually using getting killed by iOS.
From my experience, there was two occasions where apps doesn't keep running(or, in other words, shows splash screen when I launch it again).
First one is that the developer poorly, or even didn't implement suspending for the app. There were some apps that always quits when I press home button, or resets when it was on specific feature. (Although in recent app store I haven't seen one except for some public institution apps that have 1~2 average review)
Second one is hardware limitation - even though the developer properly implemented the suspension feature, iOS sometimes decide to quit it, for various reasons from lack of memory(this is actually major reason that earlier idevices didn't support app suspension on 3G/S era), battery time management.
For first reason, you can write a review on Appstore - it is one of the most impacting reasons for app development progress.
For second reason, well, it is kinda dumb solution but you can purchase a new hardware with more RAM, and it will reduce the possibility of suspended apps halted from iOS(And reduce time for app relaunch). Or, if you're not willing to do so, you can tell iOS to halt some unimportant apps by swiping the app's preview upwards in the multitasking view, possibly reducing the chance of the apps you're actually using getting killed by iOS.
answered Jan 18 at 1:54
ik1neik1ne
666
666
Some of the information contained in this post requires additional references. Please edit to add citations to reliable sources that support the assertions made here. Unsourced material may be disputed or deleted.
Some of the information contained in this post requires additional references. Please edit to add citations to reliable sources that support the assertions made here. Unsourced material may be disputed or deleted.
I don't know why this answer got a -1 since it suggests an actual solution to the problem and describes it too.
– redbeam_
Jan 18 at 19:43
I don't know how to add additional references since most of the response's reasoning relies on my personal experience. The 3GS part comes from my jailbroken iPod Touch 2G 8GB iOS 3.x, where I tried to background run an app by jailbreaking it only could handle 2~3 background apps due to small RAM (can't remember exact number but it had less than 100MB avail RAM for app tho). Appstore review part comes from my job experience from a startup company(and many developer response from popular app where it apologizes to the negative review). Second solution comes from almost every apple tip community.
– ik1ne
Jan 19 at 2:22
add a comment |
I don't know why this answer got a -1 since it suggests an actual solution to the problem and describes it too.
– redbeam_
Jan 18 at 19:43
I don't know how to add additional references since most of the response's reasoning relies on my personal experience. The 3GS part comes from my jailbroken iPod Touch 2G 8GB iOS 3.x, where I tried to background run an app by jailbreaking it only could handle 2~3 background apps due to small RAM (can't remember exact number but it had less than 100MB avail RAM for app tho). Appstore review part comes from my job experience from a startup company(and many developer response from popular app where it apologizes to the negative review). Second solution comes from almost every apple tip community.
– ik1ne
Jan 19 at 2:22
I don't know why this answer got a -1 since it suggests an actual solution to the problem and describes it too.
– redbeam_
Jan 18 at 19:43
I don't know why this answer got a -1 since it suggests an actual solution to the problem and describes it too.
– redbeam_
Jan 18 at 19:43
I don't know how to add additional references since most of the response's reasoning relies on my personal experience. The 3GS part comes from my jailbroken iPod Touch 2G 8GB iOS 3.x, where I tried to background run an app by jailbreaking it only could handle 2~3 background apps due to small RAM (can't remember exact number but it had less than 100MB avail RAM for app tho). Appstore review part comes from my job experience from a startup company(and many developer response from popular app where it apologizes to the negative review). Second solution comes from almost every apple tip community.
– ik1ne
Jan 19 at 2:22
I don't know how to add additional references since most of the response's reasoning relies on my personal experience. The 3GS part comes from my jailbroken iPod Touch 2G 8GB iOS 3.x, where I tried to background run an app by jailbreaking it only could handle 2~3 background apps due to small RAM (can't remember exact number but it had less than 100MB avail RAM for app tho). Appstore review part comes from my job experience from a startup company(and many developer response from popular app where it apologizes to the negative review). Second solution comes from almost every apple tip community.
– ik1ne
Jan 19 at 2:22
add a comment |
Marcelo Assis is a new contributor. Be nice, and check out our Code of Conduct.
Marcelo Assis is a new contributor. Be nice, and check out our Code of Conduct.
Marcelo Assis is a new contributor. Be nice, and check out our Code of Conduct.
Marcelo Assis is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Different!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f348837%2fios-always-resets-my-apps-after-a-while-when-they-are-minimized-how-can-i-cha%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown