EDIT: This isn't related to activity lifecycles. I did have an issue beforehand with Note 3s where the power saver mode recycled any of my static variables. Since then I went through extreme measure to ensure everything is being saved, passed and restored properly.
My application has a somewhat unique login system in place. The user cannot log in (and open the main activity) until they have gotten the latest files from Server and can verify the login based on those files. The login is stored in preferences when they login and cleared when the log out. If the application is restarted, the login is cleared. All crash logging is done through ACRA.
EDIT: There has been two instances of a burst of crashes that aren't related to the life cycle of the application and are being thrown because of some of the files missing. The only way those activities are launched is from the Main Activity that is launched by a Login Screen (both verify and use the Configuration files to process a successful login and available options). It looks like the activities are being launched directly without any of the required files/variables in place (login, etc).
I am able to narrow down the IP to San Jose, CA. The Build information looks like the following:
BOARD=herring
BOOTLOADER=D720SPRLC1
BRAND=Android
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=crespo4g
DISPLAY=full_crespo4g-eng 4.1.1 JRO03R eng.azhang.20141014.185122 test-keys
FINGERPRINT=Android/full_crespo4g/crespo4g:4.1.1/JRO03R/eng.azhang.20141014.185122:eng/test-keys
HARDWARE=herring
HOST=lima
ID=JRO03R
IS_DEBUGGABLE=true
MANUFACTURER=unknown
MODEL=Full Android on Crespo4G
PRODUCT=full_crespo4g
RADIO=D720SPRLF2
SERIAL=3434F1EE0F3100EC
TAGS=test-keys
TIME=1413337943000
TYPE=eng
UNKNOWN=unknown
USER=azhang
VERSION.CODENAME=REL
VERSION.INCREMENTAL=eng.azhang.20141014.185122
VERSION.RELEASE=4.1.1
VERSION.RESOURCES_SDK_INT=16
VERSION.SDK=16
VERSION.SDK_INT=16
I'm not sure what to make of these reports. Should I be worried or has anyone seen something similar?
It sounds like you are not correctly save and restoring state when your app has gone into the background. So user's that have previously logged in and are now in the middle of application suddenly do not have the expected state when they are returned to your app after it has been put into the background.
See http://developer.android.com/training/basics/activity-lifecycle/recreating.html