Databases
StackOverflow2013
Postsdbo
POAndroid Activity Life Cycle in Jelly Bean
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid Activity Life Cycle in Jelly Bean
    primarykey
    data
    text
    <p>I have been developing an application for a few months now and getting ready to go to release. I have been using the Motorola Xoom with Android 4.0.4 for testing throughout the process and everything has worked without fail. I purchased a Nexus 7 from Google (running Jelly Bean 4.1) and I am now getting all kinds of problems with the activity life cycle when the device sleeps or turns off.</p> <p>I created a new project for the sole purpose of checking the life cycle and this is the results I came up with. The following code is a sample of what I have done in each of the life cycle methods.</p> <pre><code>@Override protected void onPause() { Log.i("TEST", "onPause()"); super.onPause(); } </code></pre> <p>Results from Xoom (expected results)</p> <pre><code>---------- Program Launch ------------- onCreate(null) onStart() onResume() ---------- Turn Off Screen ------------ onPause() onSaveInstanceState(not null) onStop() ---------- Turn Screen On ------------- onReStart() onRestoreInstanceState(not null) onResume() </code></pre> <p>Results from Nexus 7 (unexpected results)</p> <pre><code>---------- Program Launch ------------- onCreate(null) onStart() onResume() ---------- Turn Off Screen ------------ onPause() onSaveInstanceState(not null) onStop() onDestroy() onCreate(not null) onStart() onRestoreInstanceState(not null) onResume() onPause() ---------- Turn Screen On ------------- OnResume() onPause() onSaveInstanceState(not null) onStop() onDestroy() onCreate(not null) onStart() onRestoreInstanceState(not null) onResume() </code></pre> <p>Again, these results are from a brand new project with no code changes other than the Log statements in each of the methods. Why are there so many additional, unnecessary method calls when the Nexus 7 gets turned off and back on? It seems to be completely destroying the application and then recreating.</p> <p>For completeness sake, when using the home button and then relaunching the application, the life cycle seems to be consistent between devices.</p> <p>Thanks in advance for any help. Wayne</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmcwadar
    1. USmcwadar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid Activity Life Cycle in Jelly Bean
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAndroid Activity Life Cycle in Jelly Bean
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid Activity Life Cycle in Jelly Bean
      1. USkcoppock
      1. VTFavorite
    1. COWow, very useful information, while I don't know the answer (although your app should always be prepated for onSaveInstanceState/onDestroy), I will check my own app now.
      singulars
      1. POAndroid Activity Life Cycle in Jelly Bean
      1. USPeter V
    2. COIs it "Turn Device On" or "Turn Screen on" ?
      singulars
      1. POAndroid Activity Life Cycle in Jelly Bean
      1. USDiego Torres Milano
    3. COYes, my fault.. It is "Turn Screen On", as in coming out of sleep mode.
      singulars
      1. POAndroid Activity Life Cycle in Jelly Bean
      1. USmcwadar
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload