-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tracks, visible on map, mysterious delay #20982
Comments
Using a "show visible tracks on map" with a smart folder is displayed IMMEDIATELY. |
Scanning of all subfolders is nothing good for. |
Latest builds have become much better - try nightlies instead of release or beta. |
I made the test with nightly of this morning. |
First run could be very slow as whole database is being reindexed. Though later on it should start working fast |
I know that there is some background processing immediately after start. I don't start measuring before the marker flags are visible. |
Description
when opening "visible on map" the delay until i see a list is about 11 sec.
When i do a "wipe down" on the just opened new window, the delay is only 3-4 sec.
For me it looks like that the information for "visible on map" is already prepared, but will only be displayed if all other (not interesting) subdirectories are also scanned. My wiping does a refresh to show immediately.
I repeated measuring a lot of times.
This slow display happens only on my S10 (Samsung, Android 12, internal mem, storage/emulated/0/Android/media/net.osmand.plus).
On a other device the delay is about 3 sec without wipe. (Samsung Tab S5e, Android 10, SDcard, storage/xxxx-xxxx/Android/obb/net.osmand.plus).
Normally the S10 is MUCH faster than the Tab S5e.
The directory subtree is nearly the same on both devices.
Installed version on both devices
OsmAnd~ 4.9.0#3358m, released: 2024-10-04
Steps to reproduce
See above
Actual result
Manual refresh is needed for faster display
Expected result
Faster display
Your Environment (required)
Se above
The text was updated successfully, but these errors were encountered: