Yes, this is a well known fault which is "on the list" for the next service pack and has been since shortly after V1.0 was released in April 2012. Please check the list that is in the support knowledge base by selecting "737 Captain" and "On the list for the next SP". You will see that many of your concerns are already known to CS and will hopefully be solved when the SP is released (now scheduled for February).