Phone resolution bug [reposting]

Reposting this as I probably did not explain myself very well
- **OS:** Windows 11
- **Scrcpy version:** 3.3.3
- **Installation method:** Windows release
- **Device model:** Samsung Galaxy A05 (sm-a055m)
- **Android version:** 15 oneui 7

## Describe the bug

Galaxy A05, shut down with **adb shell reboot -p** with **scrcpy active** and after I turned it back on phone reports both when mirroring with scrcpy in "INFO : Texture:" and in **adb shell wm size** an incorrect, larger than the actual resolution (1080x2408 instead of 720x1600) and therefore phone's display won't turn on.

Using the phone as usual through scrcpy still works (and resolution is indeed larger because it's harder so read text and such)
What could have happened? thanks in advance.

Reproduce with scrcpy active on the listed Galaxy A05 setup, then run `adb shell reboot -p` and compare the resolution shown in `INFO : Texture:` with `adb shell wm size` after restarting the phone. Trace where scrcpy observes or restores the display resolution; done means identifying the cause of the persistent 1080x2408 value and confirming the phone returns to 720x1600.

Written by the indexing model from the issue text.