- Welcome to Locus Map - forum.
Locus Map - forum
Recent posts
#1
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Blihi - Today at 17:50:03Since 4.33 there is an issue when calculating routes with highways. Every exit is announced as a "keep left". Very annoying and this was not there before.
Reproduce: open the planner using offline locus router. Plan a route over a long stretch of highway. Inspect the details and you'll find hundreds of navigation points, all the same: "keep left".
Verified in latest beta.
Reproduce: open the planner using offline locus router. Plan a route over a long stretch of highway. Inspect the details and you'll find hundreds of navigation points, all the same: "keep left".
Verified in latest beta.
#2
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by WildWortWechsel - Today at 11:04:33Quote from: Gerhard57 on Today at 09:12:46Quote from: Menion on Yesterday at 16:08:14Locus Map 4.33.0.11 is out 🎉quick test: fixed
- fix: attempt to fix incorrectly rendered track marks during the recording
New bug:
track detail -> line style is emplty
same at My library -> this folder -> Edit -> Edit folder -> Style on map -> Line style
Tested and confirmed.
#3
Developers / Re: Can a LM Add-on be used to...
Last post by hoschilo - Today at 11:01:13Hi Menion,
Everything works well so far – battery, assist level, rider power, cadence and speed via CSC Wheel Revolutions are all displayed correctly in the Specialized E-Bike sensor.
However, there is one field in the Specialized E-Bike sensor display that always shows -256 and I cannot figure out what it represents. It is displayed as "Tachometer". There is also no such field in the dashboard which could be selected.....
My question: What is this field and which GATT channel/format does Locus expect for it? Is it the total odometer (km), trip distance, or something else?
For context: I am sending data via the proprietary Levo TCU1 protocol channels (sender/channel format) and also CSC standard service (0x1816) with both Wheel and Crank Revolutions.
Thank you for your great work on Locus Map!
Everything works well so far – battery, assist level, rider power, cadence and speed via CSC Wheel Revolutions are all displayed correctly in the Specialized E-Bike sensor.
However, there is one field in the Specialized E-Bike sensor display that always shows -256 and I cannot figure out what it represents. It is displayed as "Tachometer". There is also no such field in the dashboard which could be selected.....
My question: What is this field and which GATT channel/format does Locus expect for it? Is it the total odometer (km), trip distance, or something else?
For context: I am sending data via the proprietary Levo TCU1 protocol channels (sender/channel format) and also CSC standard service (0x1816) with both Wheel and Crank Revolutions.
Thank you for your great work on Locus Map!
#4
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Gerhard57 - Today at 09:12:46Quote from: Menion on Yesterday at 16:08:14Locus Map 4.33.0.11 is out 🎉quick test: fixed
- fix: attempt to fix incorrectly rendered track marks during the recording
New bug:
track detail -> line style is emplty
same at My library -> this folder -> Edit -> Edit folder -> Style on map -> Line style
#5
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Tapio - Today at 07:17:06Quote from: Andrew Heard on Yesterday at 23:42:30track list > tap recorded track > tap chart ">" > tap arbitrary point on chart [...]
Good observation, a small bug. Also note that it doesn't jump to the map directly, which it should, but to the prior screen.
Reminder: this is all about approaching the track from inside the media library.
I was arguing it can already do that without having to enter the detailed chart screen via ">".
https://forum.locusmap.eu/index.php?msg=80954
Menion asked to remind him later...
https://forum.locusmap.eu/index.php?msg=81002
Because usability and I guess finding peaks etc is something we probably do often.
I didn't dare to ask 😁 for a feature, i. e. LM could find extremes and provide shortcuts to such points (in the chart detail screen). Such functionality isn't a strong point of LM.
#6
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Andrew Heard - Yesterday at 23:42:30Quote from: Menion on Yesterday at 16:08:14- chg: Slope chart now have only inner fill and not the gradient belowlook better thanks
@menion - late question regards new track chart & worse functionality - track list > tap recorded track > tap chart ">" > tap arbitrary point on chart, maybe highest point, fastest point, highest slope > tap Map icon (top) > top 1/5 of screen now shows map > tap "+" button > map is positioned in "middle" of whole track but not at the point of interest. It used to be possible when tap "+" that the map is position to the point of interest.
By contrast, and (in my opinion) working correctly, tap visible track on the map > tap point of interest on chart > map is correctly panned, OR even tap chart ">" > tap arbitrary point on chart > tap Map icon (top) > map is ALSO correctly panned. It seems inconsistent behavior from tapping the icon.
Suggestion in my 1st scenario - if no point is tapped then clearly the currently centering of the whole map is correct, however if a point is tapped/ a vertical line is displayed, center to that specific point.
#7
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Menion - Yesterday at 22:24:55Just quick info > under the main menu long-click is a new item "Upload crash report".
Probably a wrong naming - it grabs
- logs (Locus/logs directory) for last five days
- memory dump not older than a day (it is now automatically created in the case, app crash because of an out-of-memory crash)
- and now also recorded raw BT4 sensors data (recording may be enabled under every sensor > useful for debugging)
And all this is uploaded to our server. Result will be "ID". With this ID, I may check logs or even memory problems a lot more easily. Give it a try if a problem happens. It is a new feature, not well tested, but I believe it will work fine! And it should be start of a lot easier and more precise reporting of problems.
Btw. data are automatically deleted after 90 days from our server.
Probably a wrong naming - it grabs
- logs (Locus/logs directory) for last five days
- memory dump not older than a day (it is now automatically created in the case, app crash because of an out-of-memory crash)
- and now also recorded raw BT4 sensors data (recording may be enabled under every sensor > useful for debugging)
And all this is uploaded to our server. Result will be "ID". With this ID, I may check logs or even memory problems a lot more easily. Give it a try if a problem happens. It is a new feature, not well tested, but I believe it will work fine! And it should be start of a lot easier and more precise reporting of problems.
Btw. data are automatically deleted after 90 days from our server.
#8
Free chat / Hide specific subforums?
Last post by Tapio - Yesterday at 20:41:41Hi Menion/Asamm, is there a way or maybe an easy switch for you that would allow us to:
Hide specific subforums, so that additionally postings do not appear in https://forum.locusmap.eu/index.php?action=recent
Thx
Hide specific subforums, so that additionally postings do not appear in https://forum.locusmap.eu/index.php?action=recent
Thx
#9
Troubles & Questions / Re: Issues with QSTAR BL-1000S...
Last post by Menion - Yesterday at 16:12:49Anyone with this device, please give a try to the new app version https://forum.locusmap.eu/index.php?topic=9553.msg81037#msg81037.
After installation, try to connect to the sensor over the Sensors manager.
If it won't work, open sensor settings and enable "Record raw data to file".
After a while (minute+), when you expect the location to be valid. Stop the sensor.
Then long click on the main app menu > "Upload crash report" and write me the reported ID here. Thanks.
But I hope it won't be necessary and all will work correctly.
After installation, try to connect to the sensor over the Sensors manager.
If it won't work, open sensor settings and enable "Record raw data to file".
After a while (minute+), when you expect the location to be valid. Stop the sensor.
Then long click on the main app menu > "Upload crash report" and write me the reported ID here. Thanks.
But I hope it won't be necessary and all will work correctly.
#10
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Menion - Yesterday at 16:08:14Locus Map 4.33.0.11 is out 🎉
- add: support for QStarz BLE GNSS receivers (BL-1000ST / BL-1000GT / BL-818GT)
- chg: map server now support full range of visible map content
- fix: crash in AR screen when point name is too long
- chg: united settings for Radar sensor into generic sensors settings
- chg: Slope chart now have only inner fill and not the gradient below
- fix: incorrect preview for subsequent "Share as screenshot" calls
- fix: charts ignoring taps in Dashboard editor
- fix: incorrectly merged plans for planned routes (Re-route wasn't working as expected)
- chg: improved fallback line style naming and color options
- fix: app occasionally stuck on loading screen at start
- fix: another iteration in problematic usage of IGN over map overlay
- fix: attempt to fix incorrectly rendered track marks during the recording
- chg: improved handling failed load of custom icons for points (for example for KML files)
- add: option to directly upload bug reports to our server
- chg: plus huge list of various internal optimizations
- add: support for QStarz BLE GNSS receivers (BL-1000ST / BL-1000GT / BL-818GT)
- chg: map server now support full range of visible map content
- fix: crash in AR screen when point name is too long
- chg: united settings for Radar sensor into generic sensors settings
- chg: Slope chart now have only inner fill and not the gradient below
- fix: incorrect preview for subsequent "Share as screenshot" calls
- fix: charts ignoring taps in Dashboard editor
- fix: incorrectly merged plans for planned routes (Re-route wasn't working as expected)
- chg: improved fallback line style naming and color options
- fix: app occasionally stuck on loading screen at start
- fix: another iteration in problematic usage of IGN over map overlay
- fix: attempt to fix incorrectly rendered track marks during the recording
- chg: improved handling failed load of custom icons for points (for example for KML files)
- add: option to directly upload bug reports to our server
- chg: plus huge list of various internal optimizations