Why Camera Needs To Be Released In OnPause() Rather Than Onstop() Method Of Activity?
Solution 1:
Once your activity receives the onPause message it means that the user might be using or going to use some other application .. in this case if he tries to use camera through other application the camera must be in freed or released by your application.
Solution 2:
according to application lifecycle
Paused
Another activity is in the foreground and has focus, but this one is
still visible. That is, another activity is visible on top of this
one and that activity is partially transparent or doesn't cover the
entire screen. (...)
I think the documentation follows the rule of the thumb "release resources as soon as possible": onPause is earlier than onStop.
camera in the background window needs energy while the user has to to pay attentions to the popup.
Camera in the backgroud is of course more comfortable but for a mobile battery life time is more important.
The popup that intercepted you activity might need the camera and/or might need a lot of memory.
In your scenario when the camera should continue recording in the background the camera-s lifecycle and recording should be controlled by a service
Solution 3:
Since
onStop() is not guaranteed to be called, you can't always do in onStop() what is done inonPause().
onPause() is always called. This is guaranteed. If you need to save any state in your activity you need to save it in onPause(). onStop() may be called after onPause(), or it may not. Depends on the situation.
Solution 4:
onPause would mean your activity is no longer visible.
onStop would only be called if Android didn't think your process was needed anymore.
Post a Comment for "Why Camera Needs To Be Released In OnPause() Rather Than Onstop() Method Of Activity?"