Bug1080756 - Move forward the loading of settings and ensure they're loaded before processing a call

Hmm no, the main thing behind this bug was using Settings values before they've been read. In fact it didn't matter if Settings.init() was called before or not, because since it was asynchronous, the read didn't even start (no matter where we called it) before we tried using the values.