android-lifecycle

I've started learning architecture components, but can't find one thing. LifecycleFragment just creates a new LifecycleRegistry object, which does not start observing the fragment's lifecycle. I guess the LifecycleRegistry object starts listening to the fragment's lifecycle when we, for example, put it into LiveData.observe() as first param, but I haven't found any proof of this in source code. Question: When and how does a LifecycleRegistry object start to observe a fragment's lifecycle and refresh LifecycleRegistry.mState ? There is a ContentProvider called LifecycleRuntimeTrojanProvider

I am building an Android Java class which implements the LifecycleObserver interface. This is the constructor: public MyObserver(AppCompatActivity activity) { this.mActivity = new WeakReference<AppCompatActivity>(activity); activity.getLifecycle().addObserver(this); } Is it necessary to ever call removeObserver , using something like: @OnLifecycleEvent(Lifecycle.Event.ON_DESTROY) public void destroyListener() { if (this.mActivity.get() != null) { this.mActivity.get().getLifecycle().removeObserver(this); } } Or, can I observe forever? TL;DR: Nope. According to this link here , where a user

I have a DialogDragment which I can show one of two ways: 1) By tapping on a ListView item from its OnItemClickListener 2) By activating a the ListView's context menu and selecting a menu item Doing #1 works fine under all lifecycle events, but if I invoke it via #2 and I pause the activity (by going Home) and the resuming it via the task switcher, the dialog is no longer displayed. The fragment is there, and I can rotate the device and show the dialog. I experimented, and if I put the showing of the DialogFragment into a Handler with a delay of at least 1/2 seconds, it works. The following

I want to check internet connection in Broadcast Receiver; And set result (A boolean flag) to a global variable, to use it on whole application, in if conditions; That if internet is disconnected, set a status imageview in main activity, to red image, and if connected, set it to green. I followed this topic. But there is no getApplication() in Broadcast Receiver; And iI should use getApplicationContext() instead. On another side, this topic: when writing code in a broadcast receiver, which is not a context but is given a context in its onReceive method, you can only call getApplicationContext(

I'm working on an app that targets Api 19, and that is basically a Processing sketch. The problem I'm facing is that the first time my app is run, right after installing it, it works well until the user sends it to the background. Then, if they click on the app icon again, onCreate() is called but the activity is not destroyed or restarted. Some variables change and that produces strange behaviours. This happens ONLY the first time the app is used. After force closing it, this behaviour won't happen ever again (as far as I've tested). And this does not happen when launching the app from

I'm having an issue with activity navigation and I can't figure out what I'm doing wrong. I have a MainActivity and a SettingsActivity but using the Back and Up (on the action bar) have two different results from the Settings Activity. For example If I press the Back button I get the following lifecycle callbacks within the MainActivity : V/lifeCycle: onOptionsItemSelected V/lifeCycle: onPause V/lifeCycle: onSaveInstanceState-Bundle[..] V/lifeCycle: onStop << PRESS BACK BUTTON >> V/lifeCycle: onRestart V/lifeCycle: onStart V/lifeCycle: onResume V/lifeCycle: onPostResume While if I press the