It seems to me that calling setRetainInstance(true);
on the fragment that holds the map retains everything on the map through pauses, orientation changes, etc, without having to worry about setting and getting. Is there some reason why this isn't the recommended approach?