Move smart dialer initialization to onStart().

The SmartDialCursorLoader expects the SmartDialPrefix map to be
initialized when it's created. As
- the loader is initialized in SmartDialSearchFragment's onStart and
- the fragment's onStart is called asynchronously after the activity's
  onStart and
- the map initialization happens in
  SmartDialPrefix.initializeNanpSettings() and
- the above method is currently called in the activity's onResume()

we have a race condition between the activity's onResume() and the
fragment's onStart() (at least when processing a dial intent, which is
what causes the dialpad fragment to be immediately shown).

Fix that race condition by moving the initialization into the activity's
onStart() and running it before calling the super method to ensure it
happens before fragments are started.

Change-Id: I9767cbba3b177fdd5b1de86914cb1e40d20835ab
1 file changed
tree: 5bac3f290cbad6d3bd9f98a02a1be04e6eb41eba
  1. assets/
  2. res/
  3. src/
  4. tests/
  6. AndroidManifest.xml
  7. proguard.flags