Orientation issues in 1.4.7B

[JollyWizard]

Version: 1.4.7B
HWVer: 1.0

Changing orientation to Watchy Up does not create any sort of auto-rotate and causes menu button responsiveness to lag for various amounts of time.

Sometimes button responsiveness will return, and then rotating the watch causes it to become unresponsive again. Sometimes it seems to get stuck without significant changes to orientation.

Fix for unresponsiveness is to hold the menu button until the menu comes up. I have had it range from 5 seconds to 30s, possibly more.

Returning the setting to Ignore removes any button responsiveness issues.

[GuruSR]

Version: 1.4.7B HWVer: 1.0

Changing orientation to Watchy Up does not create any sort of auto-rotate and causes menu button responsiveness to lag for various amounts of time.

Sometimes button responsiveness will return, and then rotating the watch causes it to become unresponsive again. Sometimes it seems to get stuck without significant changes to orientation.

Fix for unresponsiveness is to hold the menu button until the menu comes up. I have had it range from 5 seconds to 30s, possibly more.

Returning the setting to Ignore removes any button responsiveness issues.

Can you turn Screen Blanking to Always, see if this shows the screen when you tilt your arm to the viewing position. This won't affect the button actions. This will tell me if your BMA is working properly as it'll sense you "tilted" your wrist and will tell the Watchy to wake up. I use this mode with my V1.0 Watchy and I've used the Watchy Up (also use it during bedtime, so accidental presses don't cause issues) and I just checked it and it seems fine. But do test the Screen Blanking to "Always" and see if the tilt works, if it doesn't, the BMA may not be working right and if that is the case, it can't tell which way is up (and why the buttons won't work).

[JollyWizard]

Can you turn Screen Blanking to Always, see if this shows the screen when you tilt your arm to the viewing position. This won't affect the button actions. But do test the Screen Blanking to "Always" and see if the tilt works, if it doesn't, the BMA may not be working right and if that is the case, it can't tell which way is up (and why the buttons won't work).

Tested as requested. The tilted screen blanking works with Always, in general, but the it has the same stuttering and lagging responsiveness as the buttons.

I previously used the orientation test on another face, and it was able to properly describe each orientation. So I don't believe it's the hardware.

Responsiveness is always fine when menu is open. I think.

[GuruSR]

Can you turn Screen Blanking to Always, see if this shows the screen when you tilt your arm to the viewing position. This won't affect the button actions. But do test the Screen Blanking to "Always" and see if the tilt works, if it doesn't, the BMA may not be working right and if that is the case, it can't tell which way is up (and why the buttons won't work).

Tested as requested. The tilted screen blanking works with Always, in general, but the it has the same stuttering and lagging responsiveness as the buttons.

I previously used the orientation test on another face, and it was able to properly describe each orientation. So I don't believe it's the hardware.

Responsiveness is always fine when menu is open. I think.

What watch face were you using when this happened, as I know the Starfield is very brutal on responsiveness.

[JollyWizard]

Mainly tested with the default GSR face, but also ballsy and LCD.

[GuruSR]

I have re-included the background task to catch the buttons during Active mode usage, so you're saying that the buttons don't work from first push or from second and push and beyond, as the first push would mean the ESP32 isn't responding to them (and that is a hardware issue), where as the second pushing (and beyond) is software and the new thread that runs catches them very nicely now.

So when is the button not responsive, first push or beyond the first (after it's been awoken). Are you using any Turbo Time? I set mine to 2 seconds and it usually is responsive enough afterwards.

[GuruSR]

Try and let me know if 1.4.7C doesn't fix the button response.

[JollyWizard]

Thanks for following up. Sorry to slip on the reply. I'll try to dig this out this weekend and give it a try. I have another watchy, same gen, I also prepped to test with the current version for more info.