App crashes! -> Locus Classic (pro) 3.68 and Brouter - or how/where to install?

[bezel]

Hello!

Under Android 12 I have installed Locus Classic/pro (3.68.1) - and wanted to continue to take Locus or offline Brouter to be able to plan routes.

I have installed Brouter (is external under "SD/Android/media/btools.routingapp/files/brouter), main directory for Locus is also selected on "Private folder on SD card".

Whenever I open Locus, select the route planner and want to plan/draw a route (offline with selected Brouter), the app crashes.

What may be the reason?
Wrong location?
Do I have to change something in Brouter (e.g. in the starageconfig file)?
What might be the reason, or is it a bug?

@menion is it possible that there is a bug in the app (with the combination of the current Locus version under Android 12)?

Thanks a lot for all your help!
 

[Menion]

Hello bezel,

I see the only problem currently reported with latest version and it is a crash on the Jelly 2E phone, is it yours?

I crash because of some weird old problem where Locus Map is unable to directly communicate with the BRouter service. I remember we've discussed this problem here on the forum maybe 2+ years before and there was a hack that helped ... but, I really can't restore my memory, sorry.


Hmm, hard to help ... disable optimization for Locus Classic, and BRouter, maybe re-install BRouter? Maybe someone other has a better memory than me? 

[bezel]

Hello bezel,

I see the only problem currently reported with latest version and it is a crash on the Jelly 2E phone, is it yours?

I crash because of some weird old problem where Locus Map is unable to directly communicate with the BRouter service. I remember we've discussed this problem here on the forum maybe 2+ years before and there was a hack that helped ... but, I really can't restore my memory, sorry.


Hmm, hard to help ... disable optimization for Locus Classic, and BRouter, maybe re-install BRouter? Maybe someone other has a better memory than me? 

@menion Thanks for getting in touch - even if it hasn't helped me much (yet). Yes, it is the Jelly 2E, which I wanted to use as a cycling computer with Locus....
(by the way, a reinstallation of Brouter did nothing).

I have Locus Classic/pro on several devices - with Brouter it works there in combination with Android 10 and Android 11 without problems.
Now with Android 12 it is the first time that this combination does not work.

Does anyone else know the problem?

@menion:
Maybe it's because of the Android 12 version?
Or that this time I have chosen "private folder on SD card" as the main directory for the Locus app?
Regarding the "hack" you mentioned: I can't get any further with my search, do you see any possibility of finding it in your "archive"?

Thank you very much!

[Menion]

I'm searching and searching ... there are so many topics about BRouter > no success  . This was a quite common problem in the past that a) seems to (almost) disappear and b) was one of the main motivations to include BRouter into Locus Map 4 directly.

[bezel]

I'm searching and searching ... there are so many topics about BRouter > no success  . This was a quite common problem in the past that a) seems to (almost) disappear and b) was one of the main motivations to include BRouter into Locus Map 4 directly.

After endless try and error attempts, I was able to solve the integration of Brouter in LocusPro/Classic & Android 12 as follows:

1. download the old apk version (1.6.3) from the web (https://brouter.de/brouter/offline.html) and install it on the smartphone (installation settings -> "allow").
!! Brouter only works via this apk - but not if you download the app via the playstore!!

2. Open the installed Brouter app on your smartphone
-> select internal storage location
-> download desired segments

The Brouter app is stored under
"android/media/btools.routingapp/brouter/"
including all segments (segments4), which are now also located internally (device) but do not require much storage space.

I really sat on it for hours and tried everything possible - it seems that it now works again as desired under Android12.