Recent posts

#1

[DE] - deutschsprachiger Forumsbereich / Re: Anzeige gpx-Track Namen un...

Last post by Sofiacarson - Today at 00:45:18

I am Sofia Carson, a vape fan who is currently working as a Customer Service Representative. I spend the majority of my time at work dealing with customers on the phone. After a hectic day at work, I like to go home and relax by taking a few puffs on my favorite geek bar sour blue dust, a disposable that I got from SkullVaping. The taste is light and is perfect to be used as a daily vape.

#2

[DE] - deutschsprachiger Forumsbereich / Re: Fehler, Fehler, Fehler, .....

Last post by Christian - Yesterday at 23:40:21

Egal ob ITIL, Menstruationsbeschwerden, Beamtenmentalität, Betriebssystem oder schlechtes Klima: am Ende zählt, was hinten rauskommt. Es sollten keine Fehler vorhanden sein, jeder sollte gesund sein und es sollte Geld verdient werden.
Dann sind alle glücklich.

Menion ist in seine eigene Falle getappt mit der Anhäufung von Fehlern über die Jahre - zusätzlich zum Streß der Neuentwicklung. Da muß er jetzt durch. Er hat alle Zeit der Welt, Hauptsache es gibt irgendwann mal fehlerfreie Versionen.
Ich wünsche ihm viel Erfolg.

#3

Locus Map / Re: Re: [APP] - version 4.33.+...

Last post by T-mo - Yesterday at 18:48:38

"Dotted style" > also for @Tapio ... this change was created really quickly without extra work, and it is mainly a better text in the preview. I see very low usage in it so consider it as a geeky fallback, nothing more ...

I appreciate the quick solution.
To those who missed the discussion: there was the need and request to only mark the recorded trackpoints without any line.

The chosed description is irritating.
'Dotted line style' is very misleading:
- 'line' actually is disabled, its 'style' is not relevant
- 1st list-entry of 'pattern' is 'dotted' and that way often visible..I wouldn't choose the identical word.

'trackpoints only' would be sufficient IMHO.

Or you add a separate mark-trackpoint-option, independent of any line (polyline) and its drawing-style (solid, pattern, whatever), would be perfect imho. Well yes, another option more to handle.

pattern : isn't 'Dotted' more something like 'Dashed'? I don't see any dots, well, who would use regular (round) dots anyway..?

#4

Troubles & Questions / Re: LoMaps mixing up

Last post by Andreatrst - Yesterday at 15:13:29

Are all the cards up to date? Please check their status in the store.

Did it and found an outdated whole Italy map in my phone maps archive. Canceled and swapped with Italy North plus Italy South. Now looks solved. Thanks for your help 

#5

Troubles & Questions / Re: LoMaps mixing up

Last post by freischneider - Yesterday at 11:58:15

Are all the cards up to date? Please check their status in the store.

#6

Troubles & Questions / LoMaps mixing up

Last post by Andreatrst - Yesterday at 11:15:15

With Locus 4.33 (Silver), running on a Samsung device, different maps are overlapped/displayed simultaneously, depending on the zoom. I only use LoMaps offline maps.

#7

[CZ&SK] - diskuze o Locusu / Re: Plánování trasy.

Last post by Joska 000 - Yesterday at 10:38:19

Bohužel toto zatržítko tam nemám. verze 4.32.4+auto

[@WildWortWechsel]

#8

Locus Map / Re: Re: [APP] - version 4.33.+...

Last post by WildWortWechsel - Yesterday at 10:31:42

Hi menion,

thank you! I'll answer your questions between the lines.

Regards, Dieter.
 

@WildWortWechsel
missing buttons - it mean that the zoom & centre buttons are lost when you rotate the screen? Have you enabled the auto-hide option?

Auto-hide is enabled.

stuck at start > hmm, unfortunate. Next time, open the list of recently started apps (third button in the bottom navigation panel) and swipe out the Locus Map completely. Anyway, how to solve it? Post a bug report after this happens next time (long click on the main app menu after start). Thanks.

You should have got the bug report yesterday.

default point icons > hmm, any what icons are defined for a points, that now use this "default" icon? Do the have own valid icon?

Figured out these are the hill tops. See screenshot.

Edit: After a restart the original hill top icons are back.

map > you are zoomed quite a lot. Please check app settings > maps > Advanced > World map. Maybe you have defined online map here?

Indeed, I have online map here. But I have all the maps downloaded also. Take a look at the photo: left side my old Nokia XR20 with 4.33.0.0. and at the right side the Pixel 10 pro XL with 4.33.0.10. Same settings. Map does not fully load.

#9

Locus Map / Re: Re: [APP] - version 4.33.+...

Last post by Gerhard57 - Yesterday at 09:55:44

I see, indeed, dotted style is a bit weird. Especially, the selected version uses the configured (but greyed out) pattern.
Additional weirdness, the pattern selector already has an entry "dotted", but they're squares. However I'd argue dotted style should just be done this old way: Line: transparent, Pattern: dots

dotted style is totally different to Line: transparten Pattern: dots
dotted style shows a dot for every recorded trackpoint and NOT a dotted line betwwen trackpoints. See screenshots

#10

Developers / Re: Can a LM Add-on be used to...

Last post by hoschilo - Yesterday at 09:28:22

Hi Menion,

Thank you for your response! Let me explain what I've actually already built.

I own a Rotwild e-bike with a Brose motor. I reverse-engineered the proprietary BLE protocol (GIGATRONIK/TCU1) that the Qore/Brose app uses to communicate with the bike.

My Android app runs on my main/daily phone, reads the live telemetry from the Central Display (speed, cadence, battery, assist level, rider power, motor power), and then emulates a Specialized Levo GATT server toward Locus Map running on a second phone which is only used for navigation wiht locus maps.

Locus already has built-in support for "Specialized E-Bike" sensors — so my app essentially pretends to be the real bike hardware. It works surprisingly well: Locus connects, subscribes, and displays battery, assist mode, cadence and power in real time.

So I'm not looking so far to publish a Play Store add-on — I just want my own setup to work reliably. But this experience made me think about how a proper API could work for the broader community.


From my reverse-engineering I found that even a single motor brand (Brose) uses mixed data formats: simple fixed-size values (uint8 for battery %, cadence, assist level; uint16 LE for speed and power) but also Protocol Buffers (Protobuf) for more complex telemetry like estimated range, trip odometer, voltage and calculated motor power.

Other brands (Bosch, Shimano, Yamaha) will have completely different protocols and even different semantics — for example assist levels: Brose uses 0–4, Bosch uses named modes (Eco/Tour/Sport/Turbo), Shimano again differently. So a good API should treat all fields as optional/nullable and represent assist as a generic integer 0–N plus an optional label string.

A reasonable base set of fields would be: battery_percent (int), assist_level (int + optional string label), speed (float, km/h), cadence (int, RPM), rider_power (int, W), motor_power (int, W), estimated_range (float, km), trip_distance (float, km), battery_voltage (float, V).


The cleanest solution would be a plugin/adapter model: Locus provides the stable API with these fields, and the community writes small adapter apps that know the specific bike protocol and translate into the Locus format. Similar to how Garmin Connect IQ works, or OBD2 adapters. My "EBikeLocus" app could essentially be the first such community adapter and serve as a reference implementation.


One of the biggest challenges is that reverse-engineering a proprietary BLE protocol is very time-consuming. It would be extremely valuable to have a tool — perhaps even built into Locus or as a companion app — that captures raw BLE notifications and lets the user interactively assign data types to byte ranges (uint8, uint16 LE/BE, int16, float, with offset and scale factor) until the values make sense. Something like a visual BLE packet parser. This would dramatically lower the barrier for users to map their own bike's protocol without needing deep technical knowledge. The main limitation is Protobuf-based protocols, which are harder to decode without the schema — but for simpler fixed-byte protocols it would work very well.

If you're planning to extend the API in that direction, I'd be very happy to share my detailed findings about the Brose/Qore protocol and collaborate on defining the API fields.

Best regards