c009b8a4961451c3ab2d9fecb8c4559adc55425d
+ The root of the problem is that the callback for a device change may be set before the fragment has a layout. Then if a change does come in, getView() would return null. This fix delays registering the callback until appropiate. Bug: 17404518 Change-Id: Ibd0e90f82593d45729f427bcc2e40fe9195eb42a
Description
No description provided
Languages
Java
89.8%
Kotlin
10.2%