-
Philip P. Moltmann authored
This does not implement correct onDestroy->onCreate behavior but mends it for the common case. We now handle all configurations changes, hence onDestroy->onCreate is very rare. We also just abort quickly if we actually had a onDestroy->onCreate instead of crashing. This is a temporary fix. Bug: 28588511 Change-Id: Ief56c8b866f2561b13253f66a7f79517fc2132cb
1dba1776