In the latest version of both the Chinese and Japanese apps, I’ve experienced a number of momentary hangs – times when I tap the screen and nothing happens.
Most often this happens between cards. I’ll be looking at the answer, I’ll tap the screen, and then nothing happens. I might tap once or twice more, thinking my first tap was missed, after which the screen finally changes to the next card and the extra taps register as (usually incorrect) input to the next card.
When I experience these pauses, it is usually about a second or so. Sometimes 2-3. Once when this happened I tried going back and re-advancing: it was quick the next time, but I went back and forth a few times and occasionally I got a delay
The most pronounced case was when starting a review. I pressed the start button and the app froze mid-press animation:
It was frozen for several seconds – enough for me to think “this is odd” and decide it was worth screenshotting, shortly after which it spontaneously resumed. I’m guessing 6-7 seconds elapsed.
I tried force quitting one of the apps, and as best as I could tell it returned to being snappy.
After restarting, the app eventually started experiencing longer and more frequent pauses (e.g. many 5+ second pauses while studying, even on things like clicking to reveal hidden definitions/readings). Since this seems like a fairly recent development, and Skritter hasn’t updated for a couple weeks, I did some poking around. It looks like Android System WebView updated on Feb 4th (my version: 80.0.3987.87). It’s hard to say for certain, but I don’t remember experiencing these problems before then.
If you’re relying on that, perhaps it is buggy or there is a bad interaction between it and Skritter.
I’m experiencing the same on my Pixel 3 XL: lags / freeze between cards:
- Skritter Version 3.3.6
- Android Version 10 (Security patch: 5 February 2020)
- Android System WebView Version 80.0.3987.87
Thanks for the detailed reports. @powelliptic we do use the system webview under the hood and it does sound like it’s possible this could be causing the issue, especially if it’s something noticed recently. It looks like I’m currently running version 79.0.3945.136 of the system webview which does not appear to be updatable yet from my Samsung Galaxy S10. I’m going to see if I can get that on my device to try and reproduce.
Let me know if you notice any other patterns that might help me reproduce the issue. Thanks!
I did manage to get the latest Android System WebView installed a few days ago and noticed today that a new version is out that specifically states speedy performance improvements. I’d check to see if the update is available (not sure if it’s only a beta release or not).
After updating to the Feb 11th version, I still eventually get multi-second hangs between cards.
(From what I can tell, “Bug fixes and speedy performance improvements” is literally the description of every new version of WebView.)
Bummer, worth a try! I’ve yet to be able to reproduce any noticeable freeze in the wild on my device, but I have some questions that might help narrow things down a bit.
- Are you still noticing the freeze before even clicking the “start reviewing” button? If so how often does it occur?
- When you’re studying how frequently are the freezes occurring?
- Have you noticed any other patterns (ie. on multiple character writing cards, only after a definition card)?
- Are you frequently minimizing the app in the middle of a review session or just doing them in one go?
Update: I’m still seeing the hang, but may have found a way to reproduce it on demand.
I was scrolling through the sections of a list that has a lot of sections (around 35-40) and experienced one of the usual hangs mid-scroll. i.e. It suddenly stopped and didn’t react to input for about 5 seconds.
The cool part was that if I sat there and repeatedly scrolled up and down it would freeze again in a matter of seconds. The one catch is that this was after the point where I had started experiencing delays while reviewing. Trying this on a freshly started app had no effect.
(Currently on WebView 80.0.3987.119)
Interesting find. That makes me believe that when viewing larger decks somehow that loaded data isn’t clearing from memory properly causing slow downs. I’ll do some testing on a deck with a bunch of sections.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.