Messages

Great news about POI.

Wasn't aware of brouter new versions. Just did play store updates.

Perhaps the app is not looking for "the same filename but ext", but for hard coded lower case variant.

No. Only Menion can know. E.g.: Netherlands.osm.map+Netherlands.osm.db works.
I keep in mind: "full lowercase is better"

Linux filesystem is case sensitive.

Yes. But:
Sweden.osm.db + Sweden.osm.map --> POIDB NOT DISPLAYED

EDIT: I checked it twice, because it's weird. It's the Sweden v4 map from OAM and Menions poi database.

Naming convention is: <country>.osm.map and ...osm.db

Sometimes!? this is not enough... Probably best is to use lowercase.

sweden.osm.db + sweden.osm.map --> WORKS
Sweden.osm.db + Sweden.osm.map --> POIDB NOT DISPLAYED

As user service, when Austria.osm.map is currently loaded and I open the POI tool, it could already choose the Austria.osm.db POI.
Maybe same goes for offline geonames (but I can see it is more difficult there).

Naming convention is: <country>.osm.map and ...osm.db

Thx, semi related: Often after map renaming or map moving actions and start of Locus after such actions:
a) Locus shows nullpointer exception at start and
b) I see white maps - I think the last used one does not display - needs delete cache and works after restart. Cache delete is not fun because the restart takes long (the big overview map takes a long time).

OK. As for poi, I have:
Netherlands_ML.map (from oam)
Netherlands_ML.db (from lomaps)

Netherlands are not shown in country picker in poi screen.

Menion, currently your POI databases are only shown, if there is a v3 map file with the same name. Now we are in the transition to v4 maps and as you know, many of us use OAM maps. I buy your lomaps only for the poi db.
In order to display those poi dbs, I have to store v3 maps additionally. Which is unintuitive for people who do not kniw, but furthermore, creates a messy map overview. Pls at least accept same name v4 maps!

Yes, but the information should be in the UI. Keep in mind eg people are testing/simulating routing a lot with turned off GPS. 30 seconds delay until next recalc is a necessary info in this scenario.

Auto recalc every 30 seconds is an important information. I was also wondering if there is some delay. Please at least add the info close to the recalc settings... Or maybe you can even make it configurable... via config file at least?

[@tapio]

Hi Menion, Problem with SD1 was my own problem with a "Sandisk Ultra 128 GB XC I" - it performed like crap. I bought a "SanDisk Extreme 256GB microSDXC" now, which performs in an awesome way, Lomaps download/extraction with a 1.5 Gb map was no problem. Best invest in my old Sony Z1 smartphone. Was a pleasant surprise that it works fine with this 256 GByte card.

@tapio
is there any information about why it should be so big problem? I use this system for many years and I believe many users as well and I'm not aware of any problem.

There's 2 bugs in the xml missing space character after s_power.png path in the xml, see Locus verify functionality on longtap theme.

Read it a few times but cannot prove yet.I keep my eyes open. Maybe it is device dependent.

Menion I can confirm the preview image loading in data manager works with v3 lomaps.

BTW. Lomaps download can be a disaster when maps reside on external sd. Because you let it download the zipfile there. And extraction from ext sd to ext sd is often too much for Android. Resulting in a totally bricked device, you even have problems to reboot. After minutes of problems, it will not work and I manually do the job: copy zip file to internal sd. Extract to internal sd. Copy to external sd.
IDK, I bought a quick SD but Android seems to have limitations here. Some other dev. (Moon+ reader) told me that once.
Maybe consider offering to define a different temp file location.

A minor one:
In the data manager, tracks oberview, long tap to the left, on a preview picture, does not create a preview. If one is there, it deletes it. v4 map + totm theme.