<p dir="auto"><strong>Describe the bug</strong></p>
<p dir="auto">Song Xperia 1 ii<br>
Samsung s21+</p>
<p dir="auto">Tried the above devices, need to set controls.alphaOffset= 80 in order to locate it to the center area of the camera.</p>
<p dir="auto">However, there are no problems in iPhone and some of the older Android devices.</p>
<p dir="auto"><strong>Platform:</strong></p>
<ul dir="auto">
<li>Device: [Mobile]</li>
<li>OS: [Android, iOS]</li>
<li>Browser: [Chrome]</li>
<li>Three.js version: [r133]</li>
</ul>
<p dir="auto">Hi, I tested this example <a href="https://threejs.org/examples/misc_controls_deviceorientation.html" rel="nofollow">https://threejs.org/examples/misc_controls_deviceorientation.html</a></p>
<p dir="auto">And it seems that the start direction is not consistent between different orientation.</p>
<p dir="auto">For example, in portrait mode, it will start by facing the wall (with door on left) BUT<br>
if I turn upside down portrait mode, it will start by facing the window, the opposite of the wall with door on the left.</p>
<p dir="auto">While on landscape mode, it will start by facing the huge window with the table on the right, while the other way of the landscape mode, it will start by facing the opposite side, facing the 3 little windows.</p>
<p dir="auto">Shouldn't it always start by facing the same object / area of the room?<br>
Is this a known bug?<br>
If not, how can we start the app by facing the same object / area of the room no matter which orientation your device is currently/initially at?<br>
Otherwise user A experience may be different than user B experience when they run the app with their devices at a different orientation.</p>
<p dir="auto">Thanks.</p>