tree 4567f1a910673efeb2505b7bd0a3eadad5ce514c
parent aac5bf1c1c60fac2db26c1ec68b85a7232816682
author Seigo Nonaka <nona@google.com> 1459346956 +0900
committer Seigo Nonaka <nona@google.com> 1459351295 +0900

Fix incorrect initial locale negotiation.

It turned out that calling ResourceManager.setDefaultLocalesLocked
and ResourcesManager.applyConfigurationToResourcesLocked
can be called before the locale negotiation is ready.

To fix this issue, move ResourcesManager setup flow after creating
application context.

This also introduces RuntimeException for notifying developers the
initialize order.

Bug: 27567902
Change-Id: Iab7ea384b039fb649fb52d06d45b2bfae21f9a8a