That never happened before. I programmed a new way of avoiding a bug where the lockscreen would come back during calls, and in the test environment it worked perfectly as well as when i tested making a call. however it just happened as i tried calling the phone and picking up the call. I think I know why actually. It's trying to call a command that tells it to stop listening for screen on event twice, both when the call starts ringing, and when the call is answered. so on that second time, android force closes it because I'm trying to "flush" something that doesn't even exist. Programming tends to get all kinds of messed up when you try to do something to something that doesn't actually exist.
I can fix that very easily. Next update will have that fix and a couple more tweaks to stay awake mode.
Foreground mode is really pretty irrelevant to your end functionality. It's cosmetic, because I run the lockscreen skip outside of any one "Screen", allowing it to persist and happen anytime it needs to. Foreground just gives you an icon in the notifications so you can pop into the settings to turn stay awake on or off anytime you would like, more efficiently. I like it, personally, some don't. That's why I added the toggle to get rid of the icon.