You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "trusktr (JIRA)" <ji...@apache.org> on 2012/09/13 08:35:07 UTC
[jira] [Created] (CB-1458) Android's new "Limit background
processes" setting in "Developer options" breaks key PhoneGap
functionality.
trusktr created CB-1458:
---------------------------
Summary: Android's new "Limit background processes" setting in "Developer options" breaks key PhoneGap functionality.
Key: CB-1458
URL: https://issues.apache.org/jira/browse/CB-1458
Project: Apache Cordova
Issue Type: Bug
Components: Android, CordovaJS
Environment: Android 4.x.x
Reporter: trusktr
Assignee: Joe Bowser
Priority: Critical
As of version 4.x.x, Android introduced a new ability to limit background processes down to zero in Settings >> Developer Options >> Limit background processes.
I'm not sure if this bug exists with the latest PhoneGap version, but I noticed it using PhoneGap apps for android from Google Play.
After setting the option to "No background processes" I noticed the following. If I try to use the Media abilities of PhoneGap in an app to chose a photo or file from my system, then when the selector application returns, the PhoneGap app will restart from the beginning because it's background process was terminated.
If I set the option back to "Standard limit" then everything works just fine.
What do we do about this? Personally, I prefer to have the option set to "No background processes" to prevent apps from needlessly wasting resources. It works great and some apps won't get terminated if they subscribe to Android's messaging system the proper way and will be dormant.
Anyways, with the setting turned to "No background processes", I've experienced apps that still work properly. I think there must be some way to fix this with PhoneGap.
This is a big deal because users should be allowed to set the option to "No background processes if they so desire."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1458) Android's new "Limit background
processes" setting in "Developer options" breaks key PhoneGap
functionality.
Posted by "Braden Shepherdson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454922#comment-13454922 ]
Braden Shepherdson commented on CB-1458:
----------------------------------------
I'm not sure if there's anything we can do here. I'm suspect we aren't the only app or framework that would have this problem. What about services that use a background process to play music or download asynchronously or maintain the network uplink for a game? If there isn't something specific about Cordova that makes this problem worse, I don't think we can fix users deliberately crippling their devices.
> Android's new "Limit background processes" setting in "Developer options" breaks key PhoneGap functionality.
> ------------------------------------------------------------------------------------------------------------
>
> Key: CB-1458
> URL: https://issues.apache.org/jira/browse/CB-1458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
> Environment: Android 4.x.x
> Reporter: trusktr
> Assignee: Joe Bowser
> Priority: Critical
>
> As of version 4.x.x, Android introduced a new ability to limit background processes down to zero in Settings >> Developer Options >> Limit background processes.
> I'm not sure if this bug exists with the latest PhoneGap version, but I noticed it using PhoneGap apps for android from Google Play.
> After setting the option to "No background processes" I noticed the following. If I try to use the Media abilities of PhoneGap in an app to chose a photo or file from my system, then when the selector application returns, the PhoneGap app will restart from the beginning because it's background process was terminated.
> If I set the option back to "Standard limit" then everything works just fine.
> What do we do about this? Personally, I prefer to have the option set to "No background processes" to prevent apps from needlessly wasting resources. It works great and some apps won't get terminated if they subscribe to Android's messaging system the proper way and will be dormant.
> Anyways, with the setting turned to "No background processes", I've experienced apps that still work properly. I think there must be some way to fix this with PhoneGap.
> This is a big deal because users should be allowed to set the option to "No background processes if they so desire."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1458) Android's new "Limit background
processes" setting in "Developer options" breaks key PhoneGap
functionality.
Posted by "Simon MacDonald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454925#comment-13454925 ]
Simon MacDonald commented on CB-1458:
-------------------------------------
+1 to Braden's comments.
Perhaps we can add a docs issue to inform developers of this issue or is there some way we can detect the "No background processes" setting and warn users?
> Android's new "Limit background processes" setting in "Developer options" breaks key PhoneGap functionality.
> ------------------------------------------------------------------------------------------------------------
>
> Key: CB-1458
> URL: https://issues.apache.org/jira/browse/CB-1458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
> Environment: Android 4.x.x
> Reporter: trusktr
> Assignee: Joe Bowser
> Priority: Critical
>
> As of version 4.x.x, Android introduced a new ability to limit background processes down to zero in Settings >> Developer Options >> Limit background processes.
> I'm not sure if this bug exists with the latest PhoneGap version, but I noticed it using PhoneGap apps for android from Google Play.
> After setting the option to "No background processes" I noticed the following. If I try to use the Media abilities of PhoneGap in an app to chose a photo or file from my system, then when the selector application returns, the PhoneGap app will restart from the beginning because it's background process was terminated.
> If I set the option back to "Standard limit" then everything works just fine.
> What do we do about this? Personally, I prefer to have the option set to "No background processes" to prevent apps from needlessly wasting resources. It works great and some apps won't get terminated if they subscribe to Android's messaging system the proper way and will be dormant.
> Anyways, with the setting turned to "No background processes", I've experienced apps that still work properly. I think there must be some way to fix this with PhoneGap.
> This is a big deal because users should be allowed to set the option to "No background processes if they so desire."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1458) Android's new "Limit background
processes" setting in "Developer options" breaks key PhoneGap
functionality.
Posted by "trusktr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457478#comment-13457478 ]
trusktr commented on CB-1458:
-----------------------------
Interestingly though, there are apps that continue to work and return to the state they were at after a user selects a photo And returns to the app. There's gotta be some way to fix it. I'm not that familiar with Android yet though. Perhaps you guys can implement some type of API that puts the web app back at a certain state based on a hash tag or something?... i'll be getting deep enough into Android soon and will post if I find a solution.
> Android's new "Limit background processes" setting in "Developer options" breaks key PhoneGap functionality.
> ------------------------------------------------------------------------------------------------------------
>
> Key: CB-1458
> URL: https://issues.apache.org/jira/browse/CB-1458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
> Environment: Android 4.x.x
> Reporter: trusktr
> Assignee: Joe Bowser
>
> As of version 4.x.x, Android introduced a new ability to limit background processes down to zero in Settings >> Developer Options >> Limit background processes.
> I'm not sure if this bug exists with the latest PhoneGap version, but I noticed it using PhoneGap apps for android from Google Play.
> After setting the option to "No background processes" I noticed the following. If I try to use the Media abilities of PhoneGap in an app to chose a photo or file from my system, then when the selector application returns, the PhoneGap app will restart from the beginning because it's background process was terminated.
> If I set the option back to "Standard limit" then everything works just fine.
> What do we do about this? Personally, I prefer to have the option set to "No background processes" to prevent apps from needlessly wasting resources. It works great and some apps won't get terminated if they subscribe to Android's messaging system the proper way and will be dormant.
> Anyways, with the setting turned to "No background processes", I've experienced apps that still work properly. I think there must be some way to fix this with PhoneGap.
> This is a big deal because users should be allowed to set the option to "No background processes if they so desire."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-1458) Android's new "Limit background
processes" setting in "Developer options" breaks key PhoneGap
functionality.
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser updated CB-1458:
---------------------------
Priority: Major (was: Critical)
> Android's new "Limit background processes" setting in "Developer options" breaks key PhoneGap functionality.
> ------------------------------------------------------------------------------------------------------------
>
> Key: CB-1458
> URL: https://issues.apache.org/jira/browse/CB-1458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
> Environment: Android 4.x.x
> Reporter: trusktr
> Assignee: Joe Bowser
>
> As of version 4.x.x, Android introduced a new ability to limit background processes down to zero in Settings >> Developer Options >> Limit background processes.
> I'm not sure if this bug exists with the latest PhoneGap version, but I noticed it using PhoneGap apps for android from Google Play.
> After setting the option to "No background processes" I noticed the following. If I try to use the Media abilities of PhoneGap in an app to chose a photo or file from my system, then when the selector application returns, the PhoneGap app will restart from the beginning because it's background process was terminated.
> If I set the option back to "Standard limit" then everything works just fine.
> What do we do about this? Personally, I prefer to have the option set to "No background processes" to prevent apps from needlessly wasting resources. It works great and some apps won't get terminated if they subscribe to Android's messaging system the proper way and will be dormant.
> Anyways, with the setting turned to "No background processes", I've experienced apps that still work properly. I think there must be some way to fix this with PhoneGap.
> This is a big deal because users should be allowed to set the option to "No background processes if they so desire."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1458) Android's new "Limit background
processes" setting in "Developer options" breaks key PhoneGap
functionality.
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455009#comment-13455009 ]
Joe Bowser commented on CB-1458:
--------------------------------
+1 to Braden's comments.
The fact is that any application that uses the built-in Android intents will have this problem because they immediately go in the background. We may be able to do something with the way the states are saved, but I don't think that will be a magic silver bullet.
> Android's new "Limit background processes" setting in "Developer options" breaks key PhoneGap functionality.
> ------------------------------------------------------------------------------------------------------------
>
> Key: CB-1458
> URL: https://issues.apache.org/jira/browse/CB-1458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
> Environment: Android 4.x.x
> Reporter: trusktr
> Assignee: Joe Bowser
> Priority: Critical
>
> As of version 4.x.x, Android introduced a new ability to limit background processes down to zero in Settings >> Developer Options >> Limit background processes.
> I'm not sure if this bug exists with the latest PhoneGap version, but I noticed it using PhoneGap apps for android from Google Play.
> After setting the option to "No background processes" I noticed the following. If I try to use the Media abilities of PhoneGap in an app to chose a photo or file from my system, then when the selector application returns, the PhoneGap app will restart from the beginning because it's background process was terminated.
> If I set the option back to "Standard limit" then everything works just fine.
> What do we do about this? Personally, I prefer to have the option set to "No background processes" to prevent apps from needlessly wasting resources. It works great and some apps won't get terminated if they subscribe to Android's messaging system the proper way and will be dormant.
> Anyways, with the setting turned to "No background processes", I've experienced apps that still work properly. I think there must be some way to fix this with PhoneGap.
> This is a big deal because users should be allowed to set the option to "No background processes if they so desire."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1458) Android's new "Limit background
processes" setting in "Developer options" breaks key PhoneGap
functionality.
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457452#comment-13457452 ]
Joe Bowser commented on CB-1458:
--------------------------------
I tried playing around with the WebView's restoreState and saveState methods, but they crash brutally on the Samsung Galaxy S2, and crash when you switch apps on the HTC One X. The thing that I noticed on both the HTC One X and the Samsung Galaxy S2 is that the phone slows down and is virtually unusable. I think this mode is in the developers menu with the expectation that only developers would ever use this mode. I'm tempted to mark this as Won't Fix, because this would be incredibly difficult to fix, especially since saveState and restoreState don't read the state correctly.
> Android's new "Limit background processes" setting in "Developer options" breaks key PhoneGap functionality.
> ------------------------------------------------------------------------------------------------------------
>
> Key: CB-1458
> URL: https://issues.apache.org/jira/browse/CB-1458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
> Environment: Android 4.x.x
> Reporter: trusktr
> Assignee: Joe Bowser
> Priority: Critical
>
> As of version 4.x.x, Android introduced a new ability to limit background processes down to zero in Settings >> Developer Options >> Limit background processes.
> I'm not sure if this bug exists with the latest PhoneGap version, but I noticed it using PhoneGap apps for android from Google Play.
> After setting the option to "No background processes" I noticed the following. If I try to use the Media abilities of PhoneGap in an app to chose a photo or file from my system, then when the selector application returns, the PhoneGap app will restart from the beginning because it's background process was terminated.
> If I set the option back to "Standard limit" then everything works just fine.
> What do we do about this? Personally, I prefer to have the option set to "No background processes" to prevent apps from needlessly wasting resources. It works great and some apps won't get terminated if they subscribe to Android's messaging system the proper way and will be dormant.
> Anyways, with the setting turned to "No background processes", I've experienced apps that still work properly. I think there must be some way to fix this with PhoneGap.
> This is a big deal because users should be allowed to set the option to "No background processes if they so desire."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-1458) Android's new "Limit background
processes" setting in "Developer options" breaks key PhoneGap
functionality.
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser updated CB-1458:
---------------------------
Priority: Minor (was: Major)
> Android's new "Limit background processes" setting in "Developer options" breaks key PhoneGap functionality.
> ------------------------------------------------------------------------------------------------------------
>
> Key: CB-1458
> URL: https://issues.apache.org/jira/browse/CB-1458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CordovaJS
> Environment: Android 4.x.x
> Reporter: trusktr
> Assignee: Joe Bowser
> Priority: Minor
>
> As of version 4.x.x, Android introduced a new ability to limit background processes down to zero in Settings >> Developer Options >> Limit background processes.
> I'm not sure if this bug exists with the latest PhoneGap version, but I noticed it using PhoneGap apps for android from Google Play.
> After setting the option to "No background processes" I noticed the following. If I try to use the Media abilities of PhoneGap in an app to chose a photo or file from my system, then when the selector application returns, the PhoneGap app will restart from the beginning because it's background process was terminated.
> If I set the option back to "Standard limit" then everything works just fine.
> What do we do about this? Personally, I prefer to have the option set to "No background processes" to prevent apps from needlessly wasting resources. It works great and some apps won't get terminated if they subscribe to Android's messaging system the proper way and will be dormant.
> Anyways, with the setting turned to "No background processes", I've experienced apps that still work properly. I think there must be some way to fix this with PhoneGap.
> This is a big deal because users should be allowed to set the option to "No background processes if they so desire."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira