I started doing this and then I realized I would have to move Settings.init() first in startup.js, and I thought that maybe the loop with mozMobileConnections may be costly and could regress us for the load time. So after all it's maybe better to keep the Settings.init() call at the end of the startup, and keep whenReady here.

What do you think ?