Databases
StackOverflow2013
Postsdbo
POAndroid - onConfigurationChanged() being called before onResume() after pausing Activity
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid - onConfigurationChanged() being called before onResume() after pausing Activity
    primarykey
    data
    text
    <p>In my Activity, I override the onConfigurationChanged() method as it's playing a video, and I do not want to wait a second until the system is ready again to continue playing the video after I change my device's orientation. This works just fine - my video keeps playing smoothly and the orientation gets changed, while the video gets rescaled to just fit in the screen dimensions.</p> <p>Yet I discovered a bug when these steps are taken:</p> <ol> <li>I pause my app during video playback</li> <li>I change orientation</li> <li>I "resume" my app</li> </ol> <p>First thing what happens: onConfigurationChanged() gets called, not onResume() after which all my fields should be restored! This causes an Exception with a divide by zero as its cause - some field equals 0 as it's not restored yet. Ofcourse this is not desired behaviour. My app does work when resuming it with the same orientation it's paused in.</p> <p>I can circumvent this, though, by using a boolean indicating whether my Activity has "fully loaded" - that is, the onResume() method has been called. But I consider this not a very clean solution.</p> <p>My question is: </p> <ol> <li>Is this intended behaviour? I consider it weird that onConfigurationChanged() gets called before onResume(). Is this a bug?</li> <li><p>Can I programmatically "unregister" my app from listening to onConfigurationChanged() temporarily (for example, unregister it in the onPause() method)? As this method does not get called because you must register some listener to it, but gets called because you put in your AndroidManifest.xml file this line:</p> <p>android:configChanges="orientation"</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USTimmos
    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
    1. VO
      singulars
      1. POAndroid - onConfigurationChanged() being called before onResume() after pausing Activity
      1. USmanjusg
      1. VTFavorite
    2. VO
      singulars
      1. POAndroid - onConfigurationChanged() being called before onResume() after pausing Activity
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid - onConfigurationChanged() being called before onResume() after pausing Activity
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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