[OSM-talk] running and registering an old osmand version
Richard
ricoz.osm at gmail.com
Sun Oct 4 15:19:30 UTC 2015
On Sun, Oct 04, 2015 at 04:23:33PM +0200, Olaf Hering wrote:
> On Sun, Oct 04, Richard wrote:
>
> > Normally it should run in native mode which does not have such strict memory
> > limits. Any way to get it run in native mode? Or maybe change the settings
> > of the virtual machine?
>
> How do I change the mode? Is it the native renderer thing in dbg
> options? If so:
in my version it is settings/general settings/"safe mode" which should be
disabled (and is disabled by default or after fresh installation).
If the app runs in safe mode there must be some reason for it, unsupported
CPU or something else.
> 10-04 16:20:49.776 2229 2229 I System.out: Loading gnustl_shared
> 10-04 16:20:49.776 2229 2229 I System.out: Loading Qt5Core
> 10-04 16:20:49.776 2229 2229 W System.err: Failed to load 'Qt5Core':java.lang.UnsatisfiedLinkError: Couldn't load Qt5Core: findLibrary returned null
> 10-04 16:20:49.776 2229 2229 W dalvikvm: Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lnet/osmand/core/android/GLActivity;
if you google that error message it was reported and apparently resolved,
not sure about the details but perhaps you find some hints about other
versions.
Richard
More information about the talk
mailing list