you can't pull open the notification panel, touch the notification for Listen, and get listen to open so you can stop it? That would be a defect in Listen's notification feature rather than a need for a back seat driver doing memory management on top of the OS.
FC without ATK just means a combination of apps that FC and ATK is causing them to quit before they get to the problem that causes the FC. An FC is not a BSOD, either, it's not like omfg I need to reboot now. It's just a fancier form of later, dude. I blame the apps and unless it causes me some actual inability to use something, I point and laugh at FCs and move on. I'm yet to have an FC that has caused me to restart.
We're going to occasionally get apps that FC. With a market that doesn't have a long queue and review process, there are some devs that churn updates multiple times per week. For that type of dev, we're their beta testers. Stuff will FC because the dev culture and market willingness allows devs to hack at their code.
IMNSHO, you're not gaining anything by preventing FCs. Think about the items in your refrigerator. You've got leftovers from 7 days ago in a plastic bag and you just brought home and put away some new stuff from the market. You open the fridge tomorrow and you decide the smell from the old stuff needs to go. Do you throw out all the new stuff? Do you empty your refrigerator and reload it with new food? No, you throw out the one thing. That's an FC. The analogy even fits in a deeply technical sense. Every app is inside its own plastic bag. If you throw the smelly food away, the shelf that was under the food is unharmed. The OS under the app is unharmed.
