Native library is not supported on this device

[Mirco Zorzo]

From two weeks with the nightly builds on a 4.1.2 android device when I start the app I have this message and then the app crash. So my solution is start again OsmAnd and deactivate the safe mode. So the app works fine. Same problem on a 2.3.6 android device.

No one have this strange behaviour?

One month ago it works fine.

[Areg]

I have noticed that too.

[Mirco Zorzo]

It was our devices that are getting old?

[Poutnik]

Such a message appears in nighlies time by time even on my Sony Xperia M dual, 1 year old model, with Android 4.3.
But when I immediately launch the OSMAnd again, such msg does not appear again.

So it is often false message,
in my understanding perhaps triggered by timeout of some system calls, if device is temporarily busy.

OSMand may incorrectly interpret the result.

Dne čtvrtek, 23. října 2014 23:47:25 UTC+2 Mirco Zorzo napsal(a):

[pshrutpark]

Current nightlies are also producing this bug on Android 4.2.2.

The "Safe Mode" is automatically activated following the "Native library is not supported on this device" message is displayed.

Deactivating the "Safe Mode" results in OSMAnd hanging (as I reported for #7787D elsewhere).

Safe Mode routing has long been unsatisfactory.

After testing, I always revert to #7785D.

Regards

[Stephan75]

Maybe related to https://code.google.com/p/osmand/issues/detail?id=2421 ??

I think this Native Library issue needs either more documentration / discussing, or a coding sprint to eliminate these causes that makes nighty build of the past days and weeks nearly unusable.

I also would ask the core developers what about a new-feature-freeze in the current development, in order to get a more stabe app towards an official release of Osmand 1.9 ... I feel that many users are waiting for this.

Stephan

[HaFi]

Same problem on Samsung S4 with Android Kitkat.

[Mirco Zorzo]

Version 7827D doesn't give the problem of native library, warks great.

[maig341]

The issue hasn't gone with time. My phone is Samsung Galaxy A5(2017) - SM-A520F. Recently I've upgraded its Android from Nougat to Oreo and now I run last update of 8.0.0. My Osmand is 3.0.4 (free). And permanently (but not always) I see subject message. Then map display is incorrect (no color). To use Osmand I have to close app and restart, I estimate frequency of this behavior as 50-70%. Any comments?

[Nelson A. de Oliveira]

I see the same problem since 2016, at least
https://github.com/osmandapp/Osmand/issues/2563

[maig341]

Well, vshcherb wrote there "This is expected failure for builds without qt5." and closed the mentioned issue. Actually I don't understand this. In case it's true, is it not possible to build Osmand WITH qt5 for six years (wikipedia says: Qt 5 was officially released on 19 December 2012)?

Since Osmand works (sometimes) incorrectly, it's clearly a bug which should be fixed, not commented and closed.

[Gnasher328 Gnasher]

I have just had this problem on my Galaxy 8.9, Android 4.0.4. It used to work fine but I uninstalled it for a while then recently reinstalled it. Result - 'native library not supported...' Big deal, but app now dog slow and no details.After lots of Googling and drawing a blank I searched for older OSM versions, installed the oldest 3.x I could find and all fine again.