Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - bezel

#1
Quote from: bezel on May 25, 2023, 16:09:57Combination Locus Classic (pro) 3.68.1 and Android 12:

offline navigation with Brouter (current version) does not work!
If you want to plan a route with Brouter in Locus it crashes!

What is the reason?
How to work around the problems?

problem solved:
see here -> https://forum.locusmap.eu/index.php?topic=8467.msg72197#msg72197
#2
Quote from: Menion on May 26, 2023, 07:53:30I'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.
#3
Quote from: Menion on May 25, 2023, 20:08:40Hello 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!
#4
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!
 
#5
Combination Locus Classic (pro) 3.68.1 and Android 12:

offline navigation with Brouter (current version) does not work!
If you want to plan a route with Brouter in Locus it crashes!

What is the reason?
How to work around the problems?
#6
was ist dein Hauptverzeichnis für Locus an sich?
#7
Liebes Forum!

Jetzt nutze ich schon seit Jahren LocusPro - und auf all meinen Geräten hat die Installation und das Verbinden mit dem offline BRouter geklappt, jetzt, bei einem neuen smartphone (Android 12) will es nicht funktionieren. Habe schon viele Kombinationen probiert, aber wenn ich in LocusPro den Routenplaner aufrufe, stürzt die app immer wieder ab...

Da ich in paar Tagen in Urlaub fahre, und eigentlich diese Kombination gerne wieder nutzen möchte, wäre ich über jeden Hinweis und Ratschlag dankbar!

Ausgangslage:
Android 12
Locus Map Classic 3.68.0

Standartverzeichnis für Locus

Hauptverzeichnis"Privater Ordner auf SD-Karte"
Unterverzeichnisse zB 'mapsvector' "Privater Ordner auf SD Karte"
BRouter in den Locus Einstellungen als offline Navigation festgelegt

BRouter-app habe ich installiert, einmal versucht unter
"storage/emulated/0/Android/media/btools.routingapp", dann auch einmal nach Neuinstallation unter
"storage/111-112/Android/media/btools.routingapp"
entsprechend erfolgte der download der BRouter-Segmente

! früher musste man ja, zB wenn man diese Segmente auf der externen SD Karte ausgelagert hatte, die 'storageconfig'-Datei ändern (-> #secondary_segment_dir=/storage/111-112/brouter_segments4 ), was aber glaube nun (ab Android 10?) nicht mehr notwendig ist.

Was mache ich nur falsch?

- BRouter mit falschem Speicherort?
Jetzt unter Android 12 wird die app im MEDIA Ordner gespeichert, früher (Android11) wurde die app im im DATA Ordner abgespeichert...)?
- Locus läuft an sich problemlos, obwohl ich als Hauptverzeichnis den "Privaten Ordner auf SD Karte" gewählt habe, oder ist hier der Haken dass BRouter nicht funktioniert?
- falscher Speicherort der Segmente?
- Änderung der 'storageconfig'-Datei notwendig?

Ich bin euch wirklich sehr, sehr dankbar, wenn ihr mir einen Lösungsweg, die richtige Vorgehensweise, Zuweisung der app/Daten etc wisst.

Viele Grüße!
 
 

#8
Quote from: ThomasD. on February 01, 2022, 18:05:17
Eine externe SD-Karte unter Android als internen Speicher einbinden bedeutet, daß beide Laufwerke zusammengefaßt werden und von der Dateiverwaltung her eins werden. Der interne Speicher vergrößert sich also um die Größe der SD-Karte.

Nachteil ist, daß diese SD-Karte dann nur diesem einen Handy funktioniert und nicht in das Nachfolgehandy übernommen werden kann. Und das die SD-Karte nicht mehr in einem Kartenleser unter Windows gelesen werden kann.
Danke für die Erklärung - aber was ist der Sinn dahinter, welchen Vorteil bietet es gegenüber zwei getrennten Speichern (interner und externer auf SD)?
#9
Quote from: Holger on February 01, 2022, 17:00:40
Warum bindet Ihr Eure extSD denn nicht einfach als internen Speicher ein...?
...
was meinst du konkret damit, verstandlich auch für einen Nicht-IT Experten?
#10
@michaelbechtold
Yes, but it is very complicated and you have to know how to proceed and where to save what. Otherwise the vectorthemes are not accessible.
Not everyone spends days on it or is a software expert - so it is extremely complicated (see also oam-forum...).
The normal user does not get along with the current LM Pro version (in case oam maps and themes should be saved externally
#11
... and for Locusmap Pro (3.51.+)?
No update? No bugfixing (OAM maps/ Vectorthemes/...)
#12
Das Problem mit den OAM maps unter Android11 ist schon so eine Sache - die Karten können zwar extern abgelegt werden, die OAM Vectorthemes müssen intern abgespeichert werden, zudem sind die Pfade etwas irreführend in der app festzulegen.

Meine Vorgehensweise:
unter Android 11 / LocusMap Pro 3.56.5 mit OAM v5 Karten:

in der app unter Einstellungen zuweisen:
Hauptverzeichnis der app:
intern

Unterverzeichnisse für mapsVector:
intern (d.h. storage/emulated/0/Android/data/menion.android.locus.pro/files/Locus/mapsVector)

--------------------------------------------------------------------------------------

- extern auf der SD Karte abgelegte OAM v5 Karten sind aber dann dennoch externunter:
storage/1234-5678/Android/media/menion.android.locus.pro/mapsVector bzw. /maps

- und die themes widerum im internen Ordner (!!):
Android/data/menion.locus.pro/files/Locus/mapsVector/_themes

- srtm Höhendaten extern unter:
storage/1234-5678/Android/data/menion.locus.pro/files/Locus/data/srtm

(wo man will, kann man die broutersegments4 und POIs auf der externen SD Karte ablegen;
intern muss man unter data... die individuellen Cursors und dashboards abspeichern)

---------------------------------------------------------------------------------------

Speichert man die OAM Karten intern ab, läuft das ganze natürlich flüssiger und der Kartenaufbau ist deutlich schneller.
Ziemliches Durcheinander, was da nun durch die ganze Umstellung entstanden ist - ich kann nur hoffen, dass es nun so wenigstens zuverlässig funktioniert.
#13
@menion
weeks ago I told you about the problem with the vector themes (for example Elevate) of Locus Pro under Android 11 - unfortunately nothing has happened yet, the problem still exists.
menion, so far you have always been helpful and have tried to solve problems with the app in the short term - in this case nothing has happened, why?

- themes were sent to you for checking, no reaction (I had sent you a PM with the link to the files)
- no update of Locus Pro, no solution regarding the storage location and the necessary path for the OAM themes.

Is this the "end" of Locus Pro?
No more support?
Are bugs no longer fixed?
What about the problem described?
#14
@menion
unfortunately I did not receive a PM from you...

Locusmap Pro only works as far as the selection of themes is concerned, as I found out after hours of trying (see my earlier post/ reply#55).

The problem with the themes under Android 11 has not yet been solved, and there is still no option to select/individually define the private folder "custom selection" when assigning the subdirectories (settings).
#15
@balloni55
maybe it is the same problem as with Locusmap Pro (https://forum.locusmap.eu/index.php?topic=7259.msg66387#msg66387) - themes saved on the external map cause the app to stop or crash.
A first "solution" I found was to save the themes internally, but leave the maps externally, but subdirectory for 'mapsVector' have to be set to App default setting/ internal directory (see link above).