Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Home/Recent button restarts apk #17

Open
GoogleCodeExporter opened this issue Apr 5, 2015 · 0 comments
Open

Using Home/Recent button restarts apk #17

GoogleCodeExporter opened this issue Apr 5, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

1. Open PythonAPK.
2. Tap the Home button. Press and hold Home to get list of Recent apps. 
3. Tap PythonAPK. 

Instead of returning to the running instance of PythonAPK, it restarts the app, 
stopping current actions and losing variable states. Particularly problematic 
on Gingerbread, but reproducible on ICS with the Recent Apps button.

What is the expected output? What do you see instead?

Using Home/Recent should return to the current running instance of PythonAPK. 
Instead, the app is restarted. Details below.

What version of the product are you using? On what operating system?

Latest; Windows.

Please provide any additional information below.

Using the BACK key to return to the PythonAPK, say from the browser, works 
fine: it returns to the already running instance (logcat: "moveTaskToBack"). 
Likewise tapping the PythonAPK icon from the homescreen. When attempting to use 
Home/Recent, the logcat reveals:

V/sl4a.FutureActivity:50(1035): FutureActivity created.
W/sl4a.FutureActivity:59(1035): FutureActivity has no task!
I/ActivityManager(181): Starting: Intent { act=android.intent.action.MAIN cat=
[android.intent.category.LAUNCHER] cmp=com.android.python27/.ScriptActivity } fr
om pid 1035
I/Process (1035): Sending signal. PID: 1045 SIG: 9
D/PythonAPK(1035): Killed process 1045

The process "com.android.python27" then dies, and a restart is scheduled in 
5000ms. The issue appears to relate to FutureActivity.java, where the code 
behind the log entries is found.

I would be grateful for any suggestions as to how to fix/avoid this issue, as 
the restarting process can be disrupting/confusing to users, and cause some 
freezing of the Android interface.

Original issue reported on code.google.com by fjn8...@gmail.com on 7 Dec 2012 at 2:28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant