It's Android's fault that it's looping, not Samsung's. Any Android app that is supposed to be always running that, for whatever reason, crashes on startup will loop like this. I had this happen with ES File explorer after an update to one component wasn't handled well by the app and made it...