As we're not sure if this is the same as bug #1469266 ( a fix which is slated for OTA6 ), we should wait and re-test when OTA6 is released.
As we're not sure if this is the same as bug #1469266 ( a fix which is slated for OTA6 ), we should wait and re-test when OTA6 is released.