Re: OsmAnd crashing since latest (monthly) map update

2016-07-19 Thread matth1982 via Osmand
Many thanks Dave Booth! I have downloaded the June file and can confirm it stops the crashing for me. The app was being killed for me after scrolling around a little. Particularly when viewing the Canary Wharf area. I noticed nothing strange being reported by OsmAnd in the adb logs, but ther

Status of Osmand Core

2016-09-18 Thread matth1982 via Osmand
I'm trying to build OsmAnd, including the latest core. I've followed these instructions so far, and they appear to be working. However, this results in a build of "core-legacy", which i notice has completely dif

Re: Status of Osmand Core

2016-09-19 Thread matth1982 via Osmand
Thanks for this. However, this still leaves me confused about OsmAnd-core. The build instructions all seem to suggest building the legacy core. I think i've attempted something similar to those build instructions (following the fdroid build) and it also did not use the master branch of OsmAnd-

Re: Status of Osmand Core

2016-09-21 Thread matth1982 via Osmand
I'm not entirely sure. You need to have the android sdk and ndk sources already installed. It appears to download it's own version of qt. So i think the answer is a bit of both. Still working on compiling the master core! -- You received this message because you are subscribed to the Google Gr

Re: Status of Osmand Core

2016-09-22 Thread matth1982 via Osmand
> I tried running another assemble* tasks in gradle but no matter which I choose I can't get app to work on my phone. It install sucessfully but crash immediately after start. I think you have to be careful which assemble task you are running. The instructions you gave compile the full version

Re: Status of Osmand Core

2016-09-22 Thread matth1982 via Osmand
The current status of my build attempt, following the instructions at https://github.com/osmandapp/OsmAnd-core are as follows: - I'm building armeabi-android-gcc.sh instead of amd64-linux-gcc.sh. - I had to correct build/target/android-gcc.cmake to set system_lib_dirs to include

Re: Status of Osmand Core

2016-09-23 Thread matth1982 via Osmand
Thanks -- i have already been successful in building with the legacy core. The purpose of this thread is that i want to build the core on the master branch (is the the QT Core?) for android, with the hope of exploiting the GPU and concurrency it uses. Do you know if this is possible or a sens

Re: Status of Osmand Core

2016-09-23 Thread matth1982 via Osmand
Excellent, thanks -- currently i've been using the scripts that use cmake. With these i've managed to get armeabi to compile to 88% so far after hacking away at the cmake files enough... Once it's done i'm hoping OsmAnd will build with the new core in the same way as with the legacy version.

Re: Status of Osmand Core

2016-09-24 Thread matth1982 via Osmand
I ran into this exact problem and managed to fix it after a few days. The problem seems to be that build/targets/android-gcc.cmake sets up the system directories to include the one containing libgnustl_shared.so. Because of this, CMake strips the library's path (because it thinks it's a system

Re: Status of Osmand Core

2016-09-24 Thread matth1982 via Osmand
On Saturday, September 24, 2016 at 2:47:33 PM UTC+1, matt...@googlemail.com wrote: > > Once this succeeded, and i'd built the new armv7 core, i was able to use > it by changing to android/OsmAnd and running > > gradle assembleFreeQtcoreArmv7Debug > > I'm wrong here -- the Qtcore used appears to

Re: Status of Osmand Core

2016-09-25 Thread matth1982 via Osmand
On Friday, September 23, 2016 at 11:44:37 AM UTC+1, Max wrote: > > Next step will be, how to build OsmAnd which includes this new core... > This is proving harder than i hoped! :) Do you have an idea how to do it? Also, do you know how to contact the developers -- i'm keen to help with improv

Re: Status of Osmand Core

2016-09-25 Thread matth1982 via Osmand
On Sunday, September 25, 2016 at 9:59:58 AM UTC+1, Karol Grudziński wrote: > > I'm pretty sure it isn't using new core because in first lines of > compilation log I can see core-legacy path :- > Yep -- i was thrown off course since building the Qtcore version didn't appear to change anything f

Re: Status of Osmand Core

2016-09-25 Thread matth1982 via Osmand
On Sunday, September 25, 2016 at 10:46:07 AM UTC+1, matt...@googlemail.com wrote: On the other hand, building using gradle as Max suggested has built two .aar files (in core/wrappers/android/build/ outputs/aar). Looking at the dependencies defined in build.gradle in android/OsmAnd it looks lik

Re: Status of Osmand Core

2016-09-25 Thread matth1982 via Osmand
On Sunday, September 25, 2016 at 12:25:21 PM UTC+1, Karol Grudziński wrote: > I changed last part of android/OsmAnd/build.gradle to use local .aar files, but I can't see a difference: Thanks for this. I'm not super familiar with gradle, so i'll have to learn on the fly what to do. If i add th

Re: Status of Osmand Core

2016-09-25 Thread matth1982 via Osmand
The following appears to have worked for me (after clearing the build directory). However, running with the new core results in "java.lang.UnsatisfiedLinkError: JNI_ERR returned from JNI_OnLoad in "/data/app/net.osmand-1/lib/arm/libQt5Core.so" in the logcat. After which it reverts to the lega