Ok I do think this is a real issue, happy to post a video--I've been testing a release on this arale and was confused when seeing this behavior again after a fresh flash.
I previously set the time manually on this phone--I assume this persists in some way in hardware, because the time is incorrect on boot even after flashing. So, the phone wakes displaying an incorrect time; if I'm able to get through lock quickly, I see the indicator changing to NTP. When the indicator changes to the correct time *the sluggish behavior turns on* <terrifying music>. Still trying to lock down the conditions to reproduce this bug wanted to report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1524488 Title: Manually setting the time into the past makes scopes sluggish, unnavigable Status in unity8 package in Ubuntu: New Bug description: Unexpected behavior while testing a U1 silo: TEST CASE 1. Open ubuntu-system-settings, set time manually into the past a few hours 2. Return to scopes 3. Swipe left for next scope EXPECTED Scope swipes left, next scope appears. ACTUAL Stunted swipe appears to register late, fails to switch scope. Please feel free to reassign if the gesture itself is dependent on time? Pathological use case but maybe worth examining if it exposes some pathological codepaths ;) . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1524488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
