Comment 5 for bug 1377148

This was discussed earlier today in a QA meeting, and it was pointed out that this really isn't a major issue as the latency is measured milliseconds.

Also as Alfonso has pointed out, as ofono's NetworkRegistration design is based upon individual property changes to the core, it's possible for our rilmodem driver to notify the core that the device is roaming, but not yet have the new MNC ( Mobile Network Code ) that would allow ofono to check the roaming files to see if the network should be treated as a home network.

That said, perhaps we should examine our network registration driver code and see whether or not it's possible to queue a roaming state change until an associated MNC has been received.

For now, we'll leave the triaged as 'Medium', and follow up post-RTM.