2.2.8 R6676: Map scroll fluidity lost

[Pascal5]

Problem: Since I updated to AQ 2.2.8, I lost fluidity when scrolling through the map. This happens for any of my offline maps, whatever the size of the map and whatever the current zoom level.

With AQ 2.2.7, scrolling was perfectly fluid. With AQ 2.2.8, scroll motion is definitely choppy.

[Psyberia-Support]

Hi Pascal, sorry for the delay.
By scrolling you mean moving around the map right? (not zooming).

[Pascal5]

By scrolling, I mean, moving in the map using the finger, but also pressing the zoom button!
It just seems that any display animation of the map has become slow and choppy.

In the old Windows days, I would have said that you don't have the proper graphics driver installed on your PC!

Note that this is totally different from the slow loading display I mentioned for an earlier version. Now all tiles load fine, there are no blank squares shown on the map display when scrolling too fast.

[PAscal5]

I reverted back to AQ 2.2.7. Scroll fluidity is restored.

My device: CAT S41, Android 8.

[Psyberia-Support]

Hi,
Sorry for asking more details, but I really would like to fix this problem.
Are use using version 2.2.7 now? Or 2.2.7c?

[Pascal5]

It's the version I restored from my previous backup. Says 2.2.7.r6488.

[Pascal5]

... And I just updated to 2.2.7c. Still has good scroll fluidity.

[Psyberia-Support]

Thanks for the update.
The good news is that there are not much changes between 2.2.7c and 2.2.8.r6676.
The bad news is that I've checked all of them a few times and cannot figure out what can cause any lag...
But I'll check again.

[Pascal5]

For me, the problem happens for all maps, including the default on-demand maps.
This seems definitely a problem in the rendering pipeline, unrelated to the map itself and its loading, which slows down the display.

[Psyberia-Support]

Looks like the hardware acceleration has been disabled. But I've no idea why (I've double checked again today).
This beta has been out for some times now and nobody else did report something similar...

[Pascal5]

Did you change the API version? Did you target a different version of Android?

Let me know if you need my help for testing in any way!

[Psyberia-Support]

Not recently.
The target version has been increased from Android 9 to Android 10 in version 2.2.7.r6488.
Did you recently try a new beta version? I've published 3 beta versions since then, and added some user settings that we could try...

[Pascal5]

Unfortunately, my fairly old device, which I now mostly use as an offline GPS, does not have Google Play account anymore. Do you have these betas available as Website Edition so I can download them from another device?

[Psyberia-Support]

Hi again,
Don't worry too much, if your current version does not have this issue you can go with it. Then will see in the future if version 2.2.8 still has this issue.