Save instance state - WonderCsabo/androidannotations GitHub Wiki

You can only use @InstanceState on types that can be stored in a Bundle. Such as primitives or types that implement Serializable or Parcelable or an annotated Parceler bean.

Since AndroidAnnotations 2.5

You can save the instance state of your activity when it is destroyed by annotating your attributes :

@EActivity
public class MyActivity extends Activity {

    @InstanceState
    int someId;

    @InstanceState
    MySerializableBean bean;

}

The attributes values are automatically saved when the system call onSaveInstanceState(Bundle). All of those values are restored when onCreate(Bundle) is called by the system.

Since AndroidAnnotations 2.7

You can also use @InstanceState in a fragment annotated with @EFragment.

Since AndroidAnnotations 4.2

You can also use @InstanceState in a view annotated with @EView or @EViewGroup.