Quote from: Andrew Heard on Yesterday at 21:25:52Same here. I gave up after 3 Minutes stuck at 52% and killed the app. Some indicator that the App is not stuck or frozen would be helpful. The restart after the kill also went *a lot* fasterQuote from: Menion on Yesterday at 13:47:12Waiting during start > hmm, some of you are not patiente@Menion - +5 minutes here waiting. I guess I wasn't expecting the startup time to be any different to other startups - just small text "update of databases" - could provide better warning to expect longer delay. But why on 2nd startup did it run immediately then? Was "vacuum" only once-off?. App does a "vacuum" task on the database > result should be a lot lot faster access to data. On my own database, it took around 2 minutes, so I expected a very low number of users will have to wait too long.
<wpt lat="47.99285296723334" lon="10.774168074131014"><name>Singold Quelle km8</name><sym>Flag, blue</sym></wpt>
<wpt lat="48.1725826072008" lon="10.741839198891203"><name>Edeka Schwabmuenchen km35</name><sym>Shopping Center</sym></wpt>
<wpt lat="48.27088344326007" lon="10.835394859313967"><name>Edeka Bobingen km50 +0,5</name><sym>Shopping Center</sym></wpt>
<wpt lat="48.34424170745477" lon="10.864577293395998"><name>Singold-Fabrikkanal-Zsfl</name><sym>Flag, blue</sym></wpt>
Quote from: Menion on Yesterday at 13:47:12Waiting during start > hmm, some of you are not patiente@Menion - +5 minutes here waiting. I guess I wasn't expecting the startup time to be any different to other startups - just small text "update of databases" - could provide better warning to expect longer delay. But why on 2nd startup did it run immediately then? Was "vacuum" only once-off?. App does a "vacuum" task on the database > result should be a lot lot faster access to data. On my own database, it took around 2 minutes, so I expected a very low number of users will have to wait too long.
Quote from: Menion on Yesterday at 13:47:12@Graf Geo
POI alert on photos > heh, funny problem. Exclude geotagged photos from POI alert? Is this a solution you always want?
. App does a "vacuum" task on the database > result should be a lot lot faster access to data. On my own database, it took around 2 minutes, so I expected a very low number of users will have to wait too long. Quote from: freischneider on March 04, 2026, 18:27:07Quote from: Agus on March 04, 2026, 11:36:01Hello.I can confirm that. It's the same with my Poco F5.
The problem persists when I select the compass with GPS enabled on Xiaomi 15T Pro (Android 16).