Keep the display still before the first tap (Nokia 6.1) #3
Loading…
Reference in a new issue
No description provided.
Delete branch "portrait-lock"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
v1.0.1 still failed tappingCountsUp on a Nokia 6.1 (API 29), now on the first tap (Taps: 0). Logcat on the failing run: the phone is portrait at launch, the display rotates to landscape (rotation 0 to 3) while the activity is created, and the injected click lands about 0.6 s after that. No keyguard or dialog (focus was the launcher, screen awake), animation scales 1.0. So my earlier double-tap reading was wrong.
The activity is now locked to portrait. Android 16 ignores that on large screens, so the two tests that tap also wait, bounded to 5 s, for the rotation to hold still for 600 ms, and fail with a message if it never does. README says why.
Not proven until a tag build of this runs on the Nokia 6.1.
Automated Codex review (read-only) of head
295f647292.tappingCountsUphas no additional check. This is a narrow timing race, but it means the wait cannot guarantee the stated outcome on large screens where the orientation lock is ignored. Exercise delayed rotation on a device and synchronize with the actual transition or retry the interaction after a detected rotation.BLOCKING: 0
Reviewed head
295f647292at 2026-11-18T14:59:31Z by codex exec (read-only sandbox).