Aktuelles Kartenmaterial für Wahoo ELEMNT BOLT, ROAM, ELEMNT selbst generieren

[Ebe66]

Es gibt weitere mit dem Problem!

https://github.com/vti/elemntary/issues/12

Hopefully, the answer is also in that post and in your screenshot.
Use the latest version of the app. By the looks of it you are on 0.5.3 while there is 0.5.6
https://github.com/vti/elemntary/releases

Your screenshot shows both the vtm_rendering and the map_pan_zoom flags as active. This should not be done on a roam 2 because it has these features already turned on by default.

If you can't use the Elemntary app to clear them, just browse to the storage map of your device and check if there are files with names that start with cfg_

if so, delete them and restart the unit.

Nobody reacted so far with a roam 2 on the telegram group, but I know there are people on there with a Roam2 that do use the Elemntary for some time now.

 

[Hoegni]

Ich habe zwar ein Backup der Config über USB gemacht, kann es aber nicht mehr aktivieren. Ich könnte heulen. @Hoegni: geht die Backup Funktion bei dir in der App?

hab zwar noch kein Backup durchgeführt. Aber sieht gut aus ;-)

 

[Ebe66]

Just got the first response from a Roam2 user that also uses Elemntary confirming that the pan & zoom is stil there...

 

[HerrRuin]

hab zwar noch kein Backup durchgeführt. Aber sieht gut aus ;-)

schöner Mist. Bei mir ging das noch nie, vom ersten Tag an, keine Backups.

Dear Ebe66 many thanks for you help!!!

The version 0.5.5 und 0.5.6 produces a error. See attached. Just 0.5.3 works without that error. (Windows 7)

But it makes no difference if the files "cfg_BHomeActivity_VtmMaps" or "cfg_MapPanZoom" are there. It doesn't care the Roam v2.
I also creat a folder "back_restore" with the elemnt_config.zip. But same here, doesnt care the roam v2, no setting/config restored after restart.

Is there any way to update the whole firmeware over adb like on android telefon?
Im waitung for the answer from wahoo support. I think its a reaplacement nesseary.

 

[Ebe66]

Unbelievable...
Whole firmware update no, not possible. According to the guy who knows the most about it in the group.
The only suggestion he has is to remove the bolt app itself.
You can do so by issuing this command via adb:

adb uninstall com.wahoofitness.bolt

After this restart and the bolt app should be reinstalled by the boltlauncher app as if the unit just came out of the box.
But no guarantees from me!
Than there is also tho options to format the cache and data partitions but even he says that's dangerous.

Last resort, maybe the unit thinks that it is a roam1.

Maybe even try this before deleting the app. It is possible to force a unit to thinks it's an other model device by creating a empty file in the root just like the other file in your screenshot, again remove those if they are still there, like cfg_BApplication_ModelOverride_ROAM_2 (no extension, just empty file) to force a roam2.
Other options are:
ELEMNT
BOLT
ROAM
BOLT_2
ROAM_1_1
ROAM_2
ACE

The last is a not yet released device.

 

[HerrRuin]

Last resort, maybe the unit thinks that it is a roam1.

Maybe even try this before deleting the app. It is possible to force a unit to thinks it's an other model device by creating a empty file in the root just like the other file in your screenshot, again remove those if they are still there, like cfg_BApplication_ModelOverride_ROAM_2 (no extension, just empty file) to force a roam2.


The last is a not yet released device.

That what I thought as well! The Device thinks, its a Roam 1.

Ebe66, You saved my day!!!

"cfg_BApplication_ModelOverride_ROAM_2" did the trick!!!!! see attached. Pan and zoom is back!!!!

Pleas tell the guy in Telegramm I will buy him a beer! And you too.

Maybe he has another idea, how to force a system config restore at restart?

I made a early config backup. But the folder "backup_restore" with the zip inside doesn't work.
Do I have to unzip the files to the folder or the root folder?

Maybe he can help again

 

[Ebe66]

Finally!!!

I most certainly will not tell the guy on telegram! , The model override was my idea
(ok, I already told him...)

He claims the restore of a backup does not work. It only works after deleting the bolt app.
But you can try. I looked at the Elemntary source and it seems that they create a backup_restore folder (in the storage root where the cfg_ file is and copy the elemnt_config.zip to it and restart. It's worth a try...

I suspect your device thinking it's a roam 1 was caused by the creation of the cfg_ files for vtm and pan/zoom.
As far as the Elemntary app not working correctly, windows 7??? ehh might be a little bit ehh old... I would suggest to mention it on VTI's github issue. I think he will have a "yeah but... " moment

Edit:
Adding a link to an article that somewhat describes when a backup file is used.
https://support.wahoofitness.com/hc/en-us/articles/8464477663890-ELEMNT-Backup-and-Restore-Feature

 

[HerrRuin]

He claims the restore of a backup does not work. It only works after deleting the bolt app.

I'm not sure if I really should do that. I'm a bit scared of uninstall the bolt app over adb.
Just to test the restore function of the config files. Maybe a youtube video will helpful to trust the process.
Can the guy describe the process step bye step? Did he ever done it on a Roam v2?

But you can try. I looked at the Elemntary source and it seems that they create a backup_restore folder (in the storage root where the cfg_ file is and copy the elemnt_config.zip to it and restart. It's worth a try...

Thats exactly what I did 5 time. Doesnt work. I deleted the backup folder or unzipped the config backup. But Nothing. No restore of my old config

Edit:
Adding a link to an article that somewhat describes when a backup file is used.
https://support.wahoofitness.com/hc/en-us/articles/8464477663890-ELEMNT-Backup-and-Restore-Feature

Yes, that would help, if the wahoo created a backup in the cloud. But nothing. Since month. The companion app never did a backup to the cloud

I have asked the wahoo support why the app makes no backup. On Hoegni Device it works. should be a problem with my app

​

 

[Ebe66]

No he didn't try on a roam2, he is still on an original element
At this point, being back on a roam 2 instead of 1 I would not suggest an app delete.
I added the link because it hints that the backup restore might work after issuing a factory defaults.
But again, at this point I would not bother and cut my losses, install the custom maps/themes and reconfigure screens/sensors etc and try to forget the last few days...

 

[spclzd]

Two strange problems using Cruiser:
1. The entire map is blue (like water), when zooming in other area are getting painted over it. Area usages which are not defined in my theme appear blue instead of empty/white. What's the reason for this? Didn't change a thing in my theme or in the maps-config.
2. Can't open/use my theme in Cruiser currently, getting an error message instead: Unknown element: style-line. I didn't change the style-lines in the theme and I can't open older versions of the theme in Cruiser, either (which previously definetly worked). I vaguely remember having the problem before and being able to fix it, or it just disappeared. Does anyone know what to do?

 

[Ebe66]

In the cruiser menu on the top right switch to vtm rendering. (Does not work on 64 bit macOS)
For the sea color dubbelcheck if you have white as background color at the top of the theme

 

[*cl*]

Does not work on 64 bit macOS

Ahhh, that‘s why my Mac was frozen.

 

[spclzd]

In the cruiser menu on the top right switch to vtm rendering. (Does not work on 64 bit macOS)
For the sea color dubbelcheck if you have white as background color at the top of the theme

I updated to cruiser 4.0.2 recently. Looks like vtm-rendering is gone?
Looking to revert back to 3.0.42, seems hard to find.

 

[Ebe66]

I asked on the Cruiser GitHub site. VTM is still available for the moment but it is hidden. You need to edit the .bat file and add vtm to the end of the command.
See https://github.com/devemux86/cruiser/discussions/575
Tried it and it works, but vtm will no longer be available in the v5 release

 

[spclzd]

I asked on the Cruiser GitHub site. VTM is still available for the moment but it is hidden. You need to edit the .bat file and add vtm to the end of the command.
See https://github.com/devemux86/cruiser/discussions/575
Tried it and it works, but vtm will no longer be available in the v5 release

vtm works again, thanks for your help!

The issue with the blue/aqua background wasn't caused by the background colour - I didn't touch that and it was still set to #ffffff. The blue base color disappeared when I commented out the following section, which I think was in my theme from the beginning and never caused an issue:

<!-- region land/sea/waterways -->
<!--     <m e="way" k="natural" v="sea">
        <area cat="roam" fill="#00FFFF" mesh="true"/>
    </m> -->

So for some reason "sea" has no boundry in my maps...

 

[cane11]

Vorab erstmal einen Dank an alle die sich um die Verbesserung und Optimierung der Darstellung beim Roam und Bolt kümmern.
Bei mir war es jetzt soweit, Wahoo hat meinen Roam V1 aufgrund eines sich ablösenden Displays kostenfrei gegen einen Roam V2 getauscht. Ich wusste bereits von einigen Freunden was mich bei der Kartendarstellung erwartet und hatte bereits hier mal quergelesen.
Als erste Maßnahme habe ich das Theme von zenzi raufkopiert, das werde ich nachher beim Graveln mal in Augenschein nehmen. Gibt es noch andere empfehlenswerte Themes für den V2 (das Kartenmaterial von Wahoo würde ich erstmal gern behalten) ?

 

[*cl*]

Ich habe aus zenzies Theme ein ausgedünntes Theme speziell für Rennrad gebastelt, wo nahezu alle unbefestigten Straßen, Wege und Trails nicht dargestellt werden. Dafür POIs wie Tankstellen und Trinkwasserstellen. Das funktioniert auch mit den orig. Wahoo Karten, nur die Bebauung (Häuser etc.) fehlt.

 

[Ebe66]

<!-- region land/sea/waterways -->
<!-- <m e="way" k="natural" v="sea">
<area cat="roam" fill="#00FFFF" mesh="true"/>
</m> -->

So for some reason "sea" has no boundry in my maps...

That means there will literally will be no sea visible on your device. Probably fine for you would be a issue for me ;-)

The only logical option left is that the next step is missing, the rendering of the land over the sea which normally is done right after rendering the sea. Like this:

    <m e="way" k="natural" v="sea">
        <area cat="bolt2" fill="#00FFFF" mesh="true"/>
        <area cat="roam2" fill="#00FFFF" mesh="true"/>
    </m>
    <m e="way" k="natural" v="nosea">
        <area cat="bolt2" fill="#FFFFFF" mesh="true"/>
        <area cat="roam2" fill="#FFFFFF" mesh="true"/>
    </m>

Last possibility: the land, coming from a shape file, was not included when creating the map?
Try one of my maps or an original one from Wahoo to test.

 

[spclzd]

That means there will literally will be no sea visible on your device. Probably fine for you would be a issue for me ;-)

No, since I live next to the coast, sea should be visible.

The only logical option left is that the next step is missing, the rendering of the land over the sea which normally is done right after rendering the sea. Like this:

    <m e="way" k="natural" v="sea">
        <area cat="bolt2" fill="#00FFFF" mesh="true"/>
        <area cat="roam2" fill="#00FFFF" mesh="true"/>
    </m>
    <m e="way" k="natural" v="nosea">
        <area cat="bolt2" fill="#FFFFFF" mesh="true"/>
        <area cat="roam2" fill="#FFFFFF" mesh="true"/>
    </m>

That wasn't it. It's just roam in my file, but the section is inculded:

<!-- region land/sea/waterways -->
    <m e="way" k="natural" v="sea">
        <area cat="roam" fill="#00FFFF" mesh="true"/>
    </m>
    <m e="way" k="natural" v="nosea">
        <area cat="roam" fill="#FFFFFF" mesh="true"/>
    </m>

Last possibility: the land, coming from a shape file, was not included when creating the map?
Try one of my maps or an original one from Wahoo to test.

I didn't fiddle around with my tags-to-keep.json and tag-wahoo-poi.xml lately and didn't have this problem before. But I checked: nosea and all different kinds of land I use in my theme are set up in the files and should therefore be included in the maps.

I will download one of your maps and give it a try.
EDIT: Download went quicker than I thought, so I could allready try your map of Niedersachsen. Since there are a couple of tags missing in your maps, that I use in my theme, there is much more "whiteroom" - but it is white and not blue/aqua. So I conclude that the error lies in my map files.
I deleted the ones I had the problem with and am downloading a new version - maybe something was just going wrong when I downloaded the faulty ones. If the error comes up again with the new ones, I have to check my config files more properly.

Thank you very much for your help, @Ebe66!

 

[spclzd]

I deleted the ones I had the problem with and am downloading a new version - maybe something was just going wrong when I downloaded the faulty ones. If the error comes up again with the new ones, I have to check my config files more properly.

Allrigth, everthing is the way it should be with the new download. No idea what went wrong with the previous one. I haven't changed a thing since then.