android-lifecycle

This question already has an answer here: Difference between onCreate() and onStart()? [duplicate] 2 answers I have been wondering for some time about the exact role of onStart() function in android life cycle. Most of the resources on net just say - it is called just before your activity becomes visible on the screen. But the applications that I have made so far I have never used onStart(). I do all my initialization in onCreate() itself. All other states in android life cycle have some or the other significance but the role of onStart() is not very clear. Are there any specific things that

I'm experiencing that <item name="android:windowIsTranslucent">true</item> is changing the way Android Lifecycle is handled. I guess it's doing that because if the window is translucent, you can still see the underlaying activity. Let's call it activity A. Let's go through the following example where we have another activity on top of activity A. This other activity is called B. Activity A Started - This activity is the first activity Activity A Stopped - Now you start activity B. Activity B Started - This activity has windowIsTranslucent set to false. Hence we can't see anything of activity A

My app runs fine besides when the user stops using their phone long enough for the screen to lock, when they unlock it the app crashes and im a bit clueless as to why. Here is the error: here is the lazy adapter: package com.buhz.helpers; import java.util.ArrayList; import java.util.HashMap; import android.app.Activity; import android.content.Context; import android.content.Intent; import android.util.Log; import android.view.LayoutInflater; import android.view.View; import android.view.View.OnClickListener; import android.view.ViewGroup; import android.widget.BaseAdapter; import android

I have read some blogs and visited some site. I want to know which event fired only one time during the life cycle. After reading blogs I realize that onCreate() method is fired only once during the life cycle. I don't know I am right or wrong. Now my problem is that I want to fired any event which fired one time only if I change the landscape orientation or portrait orientation than this event not fired means after starting activity if user change the orientation than event not fired. I want to know which event fired only one time after starting Activity. this onCreate() onCreate and

Related questions: https://stackoverflow.com/questions/15648713/strange-behaviour-while-screen-lock-in-landscape This is a strange behaviour i got in my Activities. Portrait mode (It's normal) Press screen lock, Activity: onPause() ; Unlock the screen, Activity: onResume() . Landscape mode (It's strange) Press screen lock, Activity: onPause() -> onStop() -> onDestroy() -> onCreate() -> onStart() -> onResume() which loads the Portrait layout; Unlock the screen, Activity: onPause() -> onStop() -> onDestroy() -> onCreate() -> onStart() -> onResume() and loads the Landscape layout. What I expect

The is an fragment that display the video. This fragment can either 1) open a new activity on click button 2) replace with another fragment by calling fragmentManager.beginTransaction().replace(R.id.container, f).addToBackStack(tag).commit(); for the 1) case , I would like to call player.stopPlayBack() to stop the video playing at backing And for the 2) case , I would like to call player.stopPlayBack() and player.release() to terminate the player The problem is , what event I should call for the case 1) and 2)? I try using onPause or onStop but both of them seems has not fired. How to fix it?

I have a strange behavior on the Nexus 5 when going in and out to the sleep mode. It kills and relaunchs the app in a really strange way. I show you the log: Going into sleep mode (pressing the power button) 17.005: E/MotherActivity(28940): onPause called 17.025: E/MotherActivity(28940): onStop called 17.315: E/MotherActivity(28940): onDestroy called 17.365: E/GameTuto1Activity(28940): MainActivity Constructor called 17.365: E/MotherActivity(28940): onCreate called 17.695: E/MotherActivity(28940): onStart called 17.705: E/MotherActivity(28940): onResume called 17.705: E/MotherActivity(28940):