Oruxmaps 7.4.28 Obsoleta?

[Off-Track1234]

Not such a hassle as I thought. Only took a few minutes to direct 7.4.28 to the folders used by 12.0.5 for cursor, maps, dems, tracklogs, waypoints, custom types, pictures and geocaches. I left profiles and map styles alone. Not sure about styles: at least 7.4.28 does not like zip. Everything looks fine (try Maps >Reset raster cache if anything looks odd). Maps are the big space users. If you want the new features while retaining the insurance (or the lost features) of 7.4.28 this is worthwhile. If you keep upgrading, eventually it may fail with new Mapsforge engines etc., but for now it is OK. Still a phone though.

[LaurentG]

Not sure about styles: at least 7.4.28 does not like zip

I confirm. For 7.4.28, Map themes have to be unzipped. OM 7.4.28 cannot read directly the zip file.

But AFAIK, with recent versions of OM, Map Themes can be either in a zip, or unzipped. So, to enhance "compatibility" between the two versions, and allow them to share everything, you only have to unzip all themes.

[Off-Track1234]

I think overlays and waypoints may be a bit trickier. 

The overlay folder cannot be set in 7.4.28, but if you 'load a KLM overlay' and navigate to the new overlay folder, that will be remembered by OM for the next use.

I gather from an earlier reply by Orux that in old OM "The virtual folders you create to organize wpts and tracks are saved in your profile". But there are lots of new settings, so I have not been game to use old profiles in the new version. There seems to be no way in OM 7.4.28 to set the default or any other waypoint folder to the new ones used by OM NG (or GP). Has anyone worked this out?

[Off-Track1234]

I am not sure that a user can share everything for 'complete compatibility' between several running OM versions. There have been some changes to the OM database (like --- vs @All).

But there is an easy work-around for those who just want 7.4.28 as a fallback in case of the rare but dreaded 'playstore bug'. Just 'manage' things in the new version of OM and use KML overlays (or GPX/kml 'imports') to see things in the old version.

For Waypoints: Before the trip (or after each substantial change) select and export waypoints of interest (by sub-folder if you use that structure) to KML file(s). Give each file a sensible name, and move it to the overlay folder. Then to see the waypoints, load those KML overlays. This is how I view waypoints anyhow, to avoid accidental changes unless I am in edit mode.

For Tracks/Routes: In 7.4.28, you can set the save location, but it still uses the default manage location that you can not alter. I already import route files as GPX from a PC app. Save each to a sensible folder (eg ...OM >tracklogs >routes), then in OM just load the GPX route (no need to save it to the OM database). Tracks made in OM must be saved to GPX, but that can be set to automatic ('Export Track after finished'). So in a 'playstore emergency' you will be able to use 7.4.28 to see everything except your most recent track (because it has not yet completed and saved). Not perfect, but enough to get out of trouble.

I have not played with directing NG to use the old folders or profiles, but there would still be those database changes. I have not duplicated all folders (that would need a lot of updating). So for me the 'manage in NG and view as GPX/ KML method' works well. Try it before you leave home of course, and pack a paper map and a compass for when the electrons fail.