I'm tasked with supporting an app that has already been deployed in production but improperly supports the destruction and recreation of Activities. This is most obvious when a user's device is configured by default to always destroy activities that aren't in the foreground.
This app doesn't explicitly set a value; it uses whatever the global default is.
My question is this: what are the common cases in which this setting is going to be enabled? For instance:
Device manufacturer customizes Android such that this setting can be toggled from within the default device settings activity.
Custom Android build (e.g. Cyanogen) has been configured to have it "on" by default.
User downloads some sort of "power tool" allowing him to tweak the default system settings.
How likely are each of these? Are there other common cases I've missed?