9df47ed19e59d442c25d6add7104e43d174a47c5
Calling setRequestedOrientation() before setContentView() used to start activities off in the desired orientation even if the device was in the opposite orientation, but now, there's a kind of lag where they display briefly in the device orientation before flipping to the request one. This change eliminates this effect. bug: 4581374 Change-Id: I807b0a0a8a247ec8e51b85707afcbd9f75ed9956
Description
No description provided
Languages
Java
89.8%
Kotlin
10.2%