Freezing or serious performance issues on Samsung XCover Pro

[jot ess]

I used to use Osmand+ on my Galaxy Xcover 4s (issued 2019) for a couple of years. The app grew bigger, and recently it was so slow I decided to buy a newer phone. It had to be with exchangeable battery and be still somehow pocketable, so the new one turned out to be an XCover Pro (2021).

Obviously this is not a brand-new high-end model, but as it is 2 years newer and has 1/3 more RAM, I thought Osmand should run smoother than before. It doesn't, it barely runs at all!

Often - but not always! - when I start Osmand or wake up the phone, it is responsive only for a few seconds, then freezes, and the OS says, the app doesn't react, do you want to kill it or wait? This happened with my old phone, but after tapping "wait" and waiting a few seconds, Osmand was usable again. On my new phone this happens over and over: Tap "wait", wait a moment, new message, tap "wait", ...

After some time it might become usable - and then it actually runs a lot smoother than on the old phone. Maybe I shouldn't call it a performance issue but a freezing issue?

I have installed Osmand+ exactly the same way as on my old phone - actually, it was automatically transferred. Because of the amount of data, I have specified the external SD card's /Android/media as storage. This is supposed to be slower - but can this be the cause? It seems not to be the use of the map that is slow. And the card is a 128 GB Samsung EVO Plus SD XC I, U3. I believe it should not be overly slow.

Does anybody have an idea if there is anything I can do? Or any hints on the minimum specifications my phone should meet?

It is currently: Android 13
Chipset: Exynos 9611 (10 nm)

CPU : Octa-core (4x2.3 GHZ Cortex-A73 & 4x1.7 GHZ Codex-A53)
GPU: Mali-G72 IVIP3

Best regards

Joachim

[jot ess]

Adition, two months later:

I haven't found a solution and the problem persists - but meanwhile I can tell that it is sporadic. Sometimes Osmand+ runs smooth as it should, sometimes it has the freezing issue described above and inly after several minutes it becomes usable.

Any idea anybody?

[P Wat]

I've experienced declining performance on my Samsung tablet.  Moving the app back from SD card to internal memory seemed to help a little.  The age of the device may be part of the problem for me.

NB. I'm a long term Osmand+ advocate (albeit no expert) so you may prefer to wait for better techie advice.

[Ken Evans]

I too have noticed performance dropping off a cliff recently. My, admittedly old, Pixel 2 used to be fast with OSMAnd but now runs at a snails pace when finding even short routes. I use it mainly for in car satnav, but also for it's much wider mapping capability. Maybe the recent adoption of it's 3D capability, which I don't need, has slowed things down.

Ken

--
You received this message because you are subscribed to the Google Groups "OsmAnd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/db4267e7-4dda-4ab8-a4c9-0ffc4f9c5267n%40googlegroups.com.

[cricri du lauragais]

i had this problem on my galaxy A33 with osmand+, according to the “issues” on the osmand github it could come from the “live update” of the maps.
- I uninstalled everything, purged the android caches
- reinstalled the latest f-droid version
- downloaded the maps without activating the “live update”.
and since then everything works fine ;)

[SonWon]

I would concur, I also had problems when I had live updates active.

At any moment, you have a choice, that leads you closer to God or further from God.

To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/aceee8c3-1914-4fbc-ad0f-97aa7859a8e2n%40googlegroups.com.